August 15 devel channel update renders your device unable

advocatux

@domubpkm no, there isn't.

It's not an stupid idea at all but I don't have the technical knowledge about how recovery works in detail, maybe someone with that sort of expertise will reply later.

Off the top of my head, the first problem I see is the (possible) lack of space, but on the other hand I've seen custom android recoveries with much more tools than stock android recoveries, so...

Edit: thinking a bit more about it, the main problem is how to have a keyboard on-screen for input. It would has to be a list of pre-formatted commands or something like that

Lakotaubp

Just to clarify etc on getting round this issue.
1 Stay on RC or don't update your dev device with todays update, or revert to RC in system settings.
2 Wait till next dev update is released with issue fixed.
3 Update to that and all should be ok.
Is this correct

advocatux

@lakotaubp going to RC is the fastest and easier way to have a running device again, and keep it on the save side.

If whoever is hit by this issue want to run a lower devel version, that's feasible too but I think the RC way is more user friendly for now.

Edit: I forgot to say yes, that's correct

advocatux

Some people has asked me in private how to stay in the devel channel, so I think it's better if I post the command here

ubuntu-device-flash --server=http://system-image.ubports.com touch --device=codename --channel=ubports-touch/16.04/devel --revision=version_number

Change codename for the proper one for your device. See here https://devices.ubuntu-touch.io/ the codenames list
version_number means a version number that is not affected by this issue. See the latest good one (that's the previous version to the one affected) for your device here http://system-image.ubports.com/ubports-touch/16.04/devel/

Edit: the issue has been fixed now (https://github.com/ubports/ubuntu-touch/issues/821#issuecomment-413356669) so you can use the latest version_number.

Lakotaubp

Just had new update 430 land for OPO

advocatux

@lakotaubp if you feel adventurous...

Lakotaubp

@advocatux white screen of blue circle doom after 5 min. Looks like OPO stuffed up

truscellino

Hi all,
I don't understand how to re-install another version... I don't think developer mode is enabled on my machine and I can't enable it any more due to the white screen of death we are seeing... so I can't see the solution?
Thanks, Marc

Lakotaubp

@truscellino have just put my OPO back to 428 on the dev channel following the instructions given above by @advocatux using ubuntu-device-flash. You need adb on your pc/laptop and can install ubuntu-device -flash with sudo apt install ubuntu-device-flash. Make sure you have the correct device code name (bacon in my case) and update version that was ok for your device (428 for OPO). So connect your device to pc/laptop start adb then for me it was
ubuntu-device-flash --server=https://system-image.ubports.com touch --device=bacon --channel=ubports-touch/16.04/devel --revision=428
hit enter and let it run. Good luck. Only up now as daft enough to try an update this late at night. Let us know how you get on back tomorrow.

truscellino

OK sorry I got there finally... back in 16.04/rc now. My main problem was not to succeed in rebooting into recovery mode...
Thank you for quick response, very much appreciated!

Nikfrager

Thanks to @advocatux I could flash the old image to my Moto G2 Titan. The command is
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --revision=121
I had success and my device is fine again.

advocatux

@nikfrager \o/

Lakotaubp

@advocatux Welcome back 431 works on my OPO!

advocatux

@lakotaubp kudos!

BTW I see @Nikfrager has added the verbose parameter. Good idea.

If anyone want to know about all the ubuntu-device-flash parameters available, see
http://manpages.ubuntu.com/manpages/xenial/man1/ubuntu-device-flash.1.html

Edit: fixed the wrong link (sorry)

Lakotaubp

Nexus5 also ok on 532