[solved] Mx4 - Installer blocked at "waiting for recovery mode"

advocatux

@Slayne the proper revision number format is 3 not version_3 (in that example)

I think it's better to go directly to 16.04 RC than to 15.04 stable now.

Put your phone in fastboot mode, plug it to your computer, and run ubuntu-device-flash --server=https://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/rc --revision=9 --bootstrap --wipe

Let's see if that works, and if it doesn't, report back

Edit to fix the revision number format. Sorry

advocatux

This is just for general information: the recovery images are here http://cdimage.ubports.com/devices/

Slayne

Ok, thx for your time, i report back.

When i copy/paste your last command line, i got the response :
invalid argument for flag `--revision' (expected int): strconv.ParseInt: parsing "version-9": invalid syntax
I tried without the "--revision=version-9". I got this :
sudo ubuntu-device-flash --server=https://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/rc --bootstrap --wipe
2018/08/20 12:25:59 Device is |arale|
2018/08/20 12:26:00 Flashing version 9 from ubports-touch/16.04/rc channel and server https://system-image.ubports.com to device arale
376.66 MB / 376.66 MB [====================================] 100.00 % 1.70 MB/s
/home/slayne/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz
/home/slayne/.cache/ubuntuimages/pool/device-c746103f205781974a7b89aff29cdf3dd450879f119f672d3a6f62b67ed783c5.tar.xz
2018/08/20 12:29:55 Can't flash recovery image

I went pretty well until the last line !
On the phone on recovery mode, i read "image is not a boot image".

We're getting close, i hope.

advocatux

@slayne about point 1, yes my bad, I thought that's the proper number format (as seeing here http://system-image.ubports.com/ubports-touch/16.04/rc/arale/) but it's just the number! Anyway, without any version number it should default to the latest version available.

About point 2, I've never tried to play with recovery images directly so maybe we should wait to someone with more experience with it

@UniSuperBox are you there?

Slayne

Well, no luck this afternoon.

I flashed 3 differents recovery.img for Arale found on the web, with none i could access to a functionnal recovery mode.

I tried to push files with fastboot mode, every time it ends with "image is not a boot image", 15.04 or 16.04, the same.

To try different recovery : sudo fastboot flash recovery recovery.img
Phone verified with : adb devices
I tried:
sudo ubuntu-device-flash --server https://system-image.ubports.com touch --channel ubports-touch/15.04/stable --bootstrap
sudo ubuntu-device-flash --server=https://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/rc --bootstrap --wipe
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable --wipe

Well, im stucked... So frustrating !

advocatux

@slayne I've found a cached page [*] with "old" Ubuntu Touch instructions and it seems you need to run the command twice, one with --bootstrap and then without that option

[*] https://webcache.googleusercontent.com/search?q=cache:A95HHIsDW_YJ:https://docs.ubuntu.com/phone/en/devices/installing-ubuntu-for-devices+&cd=1&hl=en&ct=clnk&gl=es

arubislander

@advocatux said in Mx4 - Installer blocked at "waiting for recovery mode":

it seems you need to run the command twice, one with --bootstrap and then without that option

I guess so are referring to this part of the instructions:

"Tip: The --bootstrap option is normally only used when installing Ubuntu the first time. It requires that the device is booted to the bootloader. After Ubuntu is installed, one uses the ubuntu-device-flash command (without the --bootstrap option) while the device is booted to Ubuntu."

What the above means is that the --bootstrap is only necessary to install to a device booted into the bootloader the first time that Ubuntu Touch is installed on said device. When there is already a version of Ubuntu Touch on the device and the device is booted normally, then the --bootloader option should no longer be used.

If the --bootloader option succeeded, then there is no need to run the command again without the option.

advocatux

Here's the main part, adapted to UBports.

Power the device off with the Power button.
Reboot into the bootloader by pressing the correct physical button combination for your device
Install Ubuntu using your selected channel. (I'm going to use 16.04 RC for this example, but anyone can change rc for other option)
Run ubuntu-device-flash touch --channel=ubports-touch/16.04/rc --bootstrap
Interesting [*]: the original command in that cached page doesn't add the device model or the server, it should be auto-detected hmm you could try that and if it doesn't work, add the device & server parameters
Tip: The --bootstrap option is normally only used when installing Ubuntu the first time. It requires that the device is booted to the bootloader. After Ubuntu is installed, one uses the ubuntu-device-flash command (without the --bootstrap option) while the device is booted to Ubuntu.
Wait until the reboot is done. In most cases no input from you is required.
The process takes some time. First, an appropriate image is downloaded to ~/.cache/ubuntuimages.
Tip: Occasionally delete the cache of downloaded images (in ~/.cache/ubuntuimages) to free up disk space with: ubuntu-device-flash --clean-cache touch.

Then, the parts of the images are deployed to the device. Ubuntu is deployed to the devices as a “recovery” image. Then, the device boots from the recovery image and installs Ubuntu as the normal OS. Finally, the device boots into Ubuntu for devices.

[*] Just as an example, this is the original command and its output in that page:

$ ubuntu-device-flash touch --channel=ubuntu-touch/stable/ubuntu --bootstrap
2015/02/16 09:50:12 Expecting the device to be in the bootloader... waiting
2015/02/16 09:50:12 Device is |mako|
2015/02/16 09:50:12 Flashing version 1 from ubuntu-touch/stable/ubuntu channel and server https://system-image.ubuntu.com to device mako

advocatux

@arubislander thank you, I was preparing a more detail answer to what I said

arubislander

@advocatux I saw that right after I pressed submit

advocatux

@arubislander no problem, it's better to have extra instructions than none

arubislander

@advocatux said in Mx4 - Installer blocked at "waiting for recovery mode":

Interesting [*]: the original command in that cached page doesn't add the device model or the server, it should be auto-detected hmm you could try that and if it doesn't work, add the device & server parameters

When server is omitted, then the Canonical servers are used by default. Since these are no longer up (I think?) I would expect the command to fail without it.

advocatux

@arubislander yes, probably, but I really don't know. Maybe that tool is exactly the same as in Canonical times or maybe it has been adapted for UBports like other tools?

Just in case, the full command adapted for MX4, 16.04 RC, and UBports scenario is:
ubuntu-device-flash --server=https://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/rc --bootstrap

and then, once again without the --bootstrap option

advocatux

Ah, this point is also important before doing anything else:

Warning: If your device is encrypted you must perform a full factory reset before installing ubuntu. This also will delete all data from the device, including apps and other data. You may want to create a backup first

Slayne

Thanks for your time.

Once again, whatever i do, all commands made by terminal on my labtop finish with :
"2018/08/20 19:05:37 Can't flash recovery image"

Sooooo frustrating.

Edit - I follow with interest this conversation about installing UBports without cable but with terminal and then i realise that on my all-new Ubuntu touch legacy installation, i dont have access to the ubuntu store and then i have no terminal...

advocatux

@slayne have you tried to install the Terminal app (vivid version) from here https://open-store.io/app/com.ubuntu.terminal?

Slayne

@advocatux It doesnt work.

But is doesnt matter because I UPGRADED MY MX4 TO UBPORTS !!! Finally !

As i thought, the main problem was the buggy recovery mode.
I tried :
sudo adb devices
75HABLM26VFN no permissions (verify udev rules); see [http://developer.android.com/tools/device.html]

(note : all these commands were made while phone on "recovery mode")

This "no permissions" was the key.

Then i did :
slayne@slayne-PcAsus:~$ sudo adb kill-server
slayne@slayne-PcAsus:~$ sudo adb start-server

daemon not running. starting it now on port 5037 *
daemon started successfully *
slayne@slayne-PcAsus:~$ adb devices
List of devices attached
75HABLM26VFN recovery

That "recovery" instead of "no permissions" seemed pretty good.

I retried one of the last commands i did yesterday :
slayne@slayne-PcAsus:~$ sudo ubuntu-device-flash --server=https://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/rc

2018/08/21 09:56:51 Device is |arale|
2018/08/21 09:56:51 Flashing version 9 from ubports-touch/16.04/rc channel and server https://system-image.ubports.com to device arale
2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/ubports-touch/16.04/rc/arale/version-9.tar.xz to device
2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/ubports-touch/16.04/rc/arale/version-9.tar.xz to device
2018/08/21 09:56:52 Start pushing /home/slayne/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2018/08/21 09:56:52 Done pushing /home/slayne/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2018/08/21 09:57:03 Start pushing /home/slayne/.cache/ubuntuimages/pool/device-c746103f205781974a7b89aff29cdf3dd450879f119f672d3a6f62b67ed783c5.tar.xz to device
2018/08/21 09:57:03 Start pushing /home/slayne/.cache/ubuntuimages/pool/ubports-dfcbe0416dc5dddaa398eff83a60d883c0d693dd1b1958e2fd9b61a02771e4ee.tar.xz to device
2018/08/21 09:57:35 Done pushing /home/slayne/.cache/ubuntuimages/pool/device-c746103f205781974a7b89aff29cdf3dd450879f119f672d3a6f62b67ed783c5.tar.xz to device
2018/08/21 09:59:27 Done pushing /home/slayne/.cache/ubuntuimages/pool/ubports-dfcbe0416dc5dddaa398eff83a60d883c0d693dd1b1958e2fd9b61a02771e4ee.tar.xz to device
2018/08/21 09:59:27 Created ubuntu_command: /home/slayne/.cache/ubuntuimages/ubuntu_commands324087129
2018/08/21 09:59:27 Rebooting into recovery to flash

AND IT WORKED !!

Thanks everydoby for your time and your help. Now im in.

advocatux

@slayne yay kudos!! Enjoy your new UT phone!!

Lakotaubp

@slayne double yey well done

halucigenia

@advocatux How would I go about installing terminal app from there on my MX4 Ubuntu Touch without functional USB?