August 15 devel channel update renders your device unable
domubpkm last edited by advocatux
For me the last update of this morning on OPO DEVEL starts up ''Welcome to 16.04...'' even if there is already 16.04 on the phone and obstructs to the start of the phone. The update asks wifi but no wifi displaid. Isn't it ? Is it possible to avoid to reflash ?
shapley last edited by
Happened for me too...rolled back to 16.04r/c
@domubpkm can you change your post title to something like "August, 15 devel channel update renders your device unable" because this issue is happening in all devices. Sorry if I'm asking you too many things today :)
Now, if you need a working device again, I think one of the best routes is to go to the 16.04 RC channel.
You need to have «developer mode» still on in your device. Connect using an usb cable and
adbto your device (
adb shell), and once you are in , run
sudo system-image-cli -vvvv --switch 16.04/rc
Then wait for a while (you'll know when it's done because the CLI will return to the system prompt, and your device will reboot) and you should have a working device again.
Edit to add that this process doesn't delete any of your data
Lakotaubp last edited by
@domubpkm Yes roll back to RC seems to very the advice. Only just picking this up lots more on Telegram supergroup.
I updated my OPO this morning to 248 and didn't see this welcome message so is it 249 thats the problem
@domubpkm thank you for changing the title, and thank you for your patience :)
@advocatux Done, change the title of the post. For solving the problem, i must wait at least tomorow to get my ubuntu computer back ! I have only a windows 10 netbook with me....
Thanks very much !
@domubpkm lol we posted at the same time
@domubpkm I don't know about windows netbooks but maybe you can install adb in it?
@advocatux It's can wait.. It's not fully vital. It's not my main phone. My main phone has Vidid 15.04 r3 for the moment.. Because it's a real lack for me (and others maybe) not to have a fully operational dekko : I'm conscious of the big efforts of the developpers on dekko.
@domubpkm I'm reading the fresh bug report now (https://github.com/ubports/ubuntu-touch/issues/821). Maybe you can try that workaround that works in FP2 at least, before doing anything else
killerbee last edited by
@advocatux Workaround doesnt work for my BQ10 FHD, but fallback to rc channel does
@killerbee yeah, it seems the workaround doesn't work for Pro 5, Arale, and Frieza (those are the devices reported for now).
@advocatux I hit the phone against the wall, nothing happen for me ! 🙂
Marathon2422 last edited by
I think someone is trying to convince you Devs that you need that "edge" LOL
@marathon2422 good point XD (but I'm just a user)
@advocatux I don't now if i said something unrealistic or infeasible : i don't think there is a command prompt, something similar as TERMINAL in UBPORTS RECOVERY. Isn't it ? If the system freeze, don't you think it would be a good idea to be able to lauch commands lines so as to unfreeze a phone without another computer ? Or to have a mechanism to change the channel (in this case devel to rc ?). If it is stupid idea, sorry....
@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 last edited by
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
@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 :)