@WLBI - I'm in!

Thank you SO much for that info. I've no idea why neither the boot menu, nor the installer, wouldn't wipe the cache.

Hi all!

I'm Ronnie (ronnietucker) and I'm the founder and editor of Full Circle Magazine (http://fullcirclemagazine.org). Now in its tenth year, FCM (as we fondly call it) is a free PDF magazine for all things Ubuntu. Including Touch.

I also do artwork. Both real world (pencil, watercolour, etc.) and digital (GIMP, MyPaint, etc.) and I'm hoping to install the UBports Touch on my M10 FHD.

If there's anything I can do to help just let me know.

Got the answer via the Telegram group.

It's the desktop root password it's looking for.

Doh! I kept thinking it was a password for the phone it needed.

I'm not entirely sure what the problem is, or where it lies, but it's definitely something to do with webapps. Any app that uses the web (browser, dekko, etc.) all crash when in a monitor connected convergence state.

Convergence with just a mouse/keyboard is fine. Adding a monitor is when problems begin...

This happens in both r1 and I think was prevalent (but not as bad) in OTA-15.

Got the answer via the Telegram group.

It's the desktop root password it's looking for.

Doh! I kept thinking it was a password for the phone it needed.

I'm trying to flash my MX4 with the UBports Installer app.

I've got the MX4 hooked up. Selected MX4 fom the menu. The app agrees that it is an MX4. I click to install, but I get a popup that says 'Password needed to continue'.

What's the password?

Weird. I just tried this just now (BQ M10 FHD) and got the error message:

E: Couldn't download packages: e2fsprogs libcryptsetup4
Failed to create container

Apparently it's a bug: https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1672231

@WLBI - I'm in!

Thank you SO much for that info. I've no idea why neither the boot menu, nor the installer, wouldn't wipe the cache.

I mentioned this in the 'testing the images' thread, but thought it might be best to start a new thread for this.

I've downloaded the IMG file, got the device into fastboot and I run the command (in a desktop terminal):

sudo ubuntu-device-flash --server=https://system-image.ubports.com/ touch --channel=ubports-touch/legacy --bootstrap --recovery-image=/home/ronnie/Downloads/Linux\ Distros/UBports\ M10/recovery-frieza.img

My output is:

NOTE: I've highlighted in bold where it says the cache formatting failed. I even tried formatting the cache in the boot menu. Still no install.

2017/05/27 13:09:18 Expecting the device to be in the bootloader... waiting
2017/05/27 13:10:02 Device is |frieza|
2017/05/27 13:10:03 Flashing version 4 from ubports-touch/legacy channel and server https://system-image.ubports.com/ to device frieza
2017/05/27 13:10:06 Cache formatting was not successful, flashing may fail, check your partitions on device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/pool/ubports-2fa71268a7de2699e17a1d60f518020e9a26036a57e5add22388cd572f781a66.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/ubports-touch/legacy/frieza/version-4.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/pool/device-6d8854a9ee3fd34df55940ae6e19a6968b14418a7fd01fbf1e17624d0129ef23.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/ubports-touch/legacy/frieza/version-4.tar.xz to device
2017/05/27 13:10:46 Done pushing /home/ronnie/.cache/ubuntuimages/pool/device-6d8854a9ee3fd34df55940ae6e19a6968b14418a7fd01fbf1e17624d0129ef23.tar.xz to device
2017/05/27 13:11:21 Done pushing /home/ronnie/.cache/ubuntuimages/pool/ubports-2fa71268a7de2699e17a1d60f518020e9a26036a57e5add22388cd572f781a66.tar.xz to device
2017/05/27 13:11:21 Created ubuntu_command: /home/ronnie/.cache/ubuntuimages/ubuntu_commands662566973
2017/05/27 13:11:21 Rebooting into recovery to flash

The device never reboots. It sits as shown below (in the photo) forever. I left it for over 3hrs (while I went out and did stuff) came back and it was still sitting there.

When I choose to reboot the system it does reboot, but I'm back in a fresh install of OTA-15.

Decided to try the magic-device-tool to see if that'd make any difference. Nope!

Pretty much the same output (below) as flashing via terminal.

=======

Created filesystem with 11/51296 inodes and 6651/204800 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
FAILED (remote: unknown command)
finished. total time: 0.002s
Creating filesystem with parameters:
Size: 4194304000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 16000
Label:
Blocks: 1024000
Block groups: 32
Reserved block group size: 255
Created filesystem with 11/256000 inodes and 34123/1024000 blocks
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.002s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.253s
Please wait

2017/05/27 21:13:42 Device is |frieza|
2017/05/27 21:13:42 Flashing version 5 from ubports-touch/legacy channel and server http://system-image.ubports.com to device frieza
2017/05/27 21:14:06 Cache formatting was not successful, flashing may fail, check your partitions on device
2017/05/27 21:14:17 Start pushing /home/ronnie/.cache/ubuntuimages/ubports-touch/legacy/frieza/version-5.tar.xz to device
2017/05/27 21:14:17 Start pushing /home/ronnie/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/05/27 21:14:17 Start pushing /home/ronnie/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/05/27 21:14:17 Start pushing /home/ronnie/.cache/ubuntuimages/pool/ubports-f683ce0eac8665810600110821a12e5ad615e5d509507c90cea46a0f254adc23.tar.xz to device
2017/05/27 21:14:17 Start pushing /home/ronnie/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/05/27 21:14:17 Start pushing /home/ronnie/.cache/ubuntuimages/pool/device-6d8854a9ee3fd34df55940ae6e19a6968b14418a7fd01fbf1e17624d0129ef23.tar.xz to device
2017/05/27 21:14:17 Done pushing /home/ronnie/.cache/ubuntuimages/ubports-touch/legacy/frieza/version-5.tar.xz to device
2017/05/27 21:14:18 Done pushing /home/ronnie/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/05/27 21:14:18 Done pushing /home/ronnie/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/05/27 21:14:18 Done pushing /home/ronnie/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/05/27 21:14:44 Done pushing /home/ronnie/.cache/ubuntuimages/pool/device-6d8854a9ee3fd34df55940ae6e19a6968b14418a7fd01fbf1e17624d0129ef23.tar.xz to device
2017/05/27 21:15:20 Done pushing /home/ronnie/.cache/ubuntuimages/pool/ubports-f683ce0eac8665810600110821a12e5ad615e5d509507c90cea46a0f254adc23.tar.xz to device
2017/05/27 21:15:20 Created ubuntu_command: /home/ronnie/.cache/ubuntuimages/ubuntu_commands360842843
2017/05/27 21:15:21 Rebooting into recovery to flash

Wait until it reboots on its own!
Do not reboot manually!

Cleaning up..

Exiting script. Bye Bye

======

And, from there, even after waiting for 25 minutes I see the infamous yellow 'Installing Ubuntu update' text.

If I choose 'reboot system now' it boots up, again, back to a fresh install of OTA-15!

@NeoTheThird said in Convergence:

I can reproduce it on the M10 HD.

I created a bug here: https://bugs.launchpad.net/ubports-meta/+bug/1693311

Can someone try on devices other than the tablets and report his experience please?

Same with M10 FHD.

@NeoTheThird Terminal output for this flash:

ronnie@ronnie-desktop ~ $ sudo ubuntu-device-flash --server=https://system-image.ubports.com/ touch --channel=ubports-touch/legacy --bootstrap --recovery-image=/home/ronnie/Downloads/Linux\ Distros/UBports\ M10/recovery-frieza.img
[sudo] password for ronnie:
2017/05/27 13:09:18 Expecting the device to be in the bootloader... waiting
2017/05/27 13:10:02 Device is |frieza|
2017/05/27 13:10:03 Flashing version 4 from ubports-touch/legacy channel and server https://system-image.ubports.com/ to device frieza
2017/05/27 13:10:06 Cache formatting was not successful, flashing may fail, check your partitions on device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/pool/ubports-2fa71268a7de2699e17a1d60f518020e9a26036a57e5add22388cd572f781a66.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/ubports-touch/legacy/frieza/version-4.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/05/27 13:10:18 Start pushing /home/ronnie/.cache/ubuntuimages/pool/device-6d8854a9ee3fd34df55940ae6e19a6968b14418a7fd01fbf1e17624d0129ef23.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/05/27 13:10:18 Done pushing /home/ronnie/.cache/ubuntuimages/ubports-touch/legacy/frieza/version-4.tar.xz to device
2017/05/27 13:10:46 Done pushing /home/ronnie/.cache/ubuntuimages/pool/device-6d8854a9ee3fd34df55940ae6e19a6968b14418a7fd01fbf1e17624d0129ef23.tar.xz to device
2017/05/27 13:11:21 Done pushing /home/ronnie/.cache/ubuntuimages/pool/ubports-2fa71268a7de2699e17a1d60f518020e9a26036a57e5add22388cd572f781a66.tar.xz to device
2017/05/27 13:11:21 Created ubuntu_command: /home/ronnie/.cache/ubuntuimages/ubuntu_commands662566973
2017/05/27 13:11:21 Rebooting into recovery to flash

... but hangs with the yellow text (on the M10 FHD) saying: Installing Ubuntu update

After several minutes I reboot and I'm back in OTA15. Weird!

@NeoTheThird I don't I'm afraid.

I'm trying to flash it again. I've wiped the cache before flashing this time, but I think I might end up the same as @WLBI as I can see the dreaded 'Installing Ubuntu update' in yellow at the bottom of the screen.

I'll keep the terminal logs this time though.