asked 2018-09-13 10:12:30 +0300
I downloaded the latest sailfish x update (2.2.1.18) yesterday, applied it this morning, saw the progress indicator advance to completion - and now nothing more has happened for several hours.
What am I supposed to do to recover my phone?
answered 2018-09-13 10:52:12 +0300
The problem seems to be that, once finished, the upgrade process fails to reboot into the freshly upgraded OS as it should, but stays frozen.
wait a bit to make sure that the proceihas finished writing/flushing everything
(two hours is way more than enough. A couple of minutes is safe already)
hold the "power" and "volume-up" pressed at the same time (at least 3 sec)
(this will force the smartphone to reboot into your freshly upgraded OS)
Like for a few other users, when reaching 100%, the upgrade process stops and freezes instead of rebooting into the fresh new system as it should.
I did take a few step to investigate:
but it doesn't show on the network
(I've set mine up to to automatically default to "dev mode")
in fact it's not showing up as a usb-network device at all.
it shows up as a Linux File-CD Gadget
(a type of hybrid device that both shsows up as flash (e.g.: /dev/sde) and as an emulated CD-ROM drive (e.g.: /dev/sg1) )
LOLWUT?!?
forcing the reboot manually (power + volume up) brings everything back to normal and boots into the brand new 2.2.1.18
Seems to me that it's linked to something on the Qualcom SoC ('s firmware ?) going bonkers instead of performing the necessary reboot.
answered 2018-09-13 10:50:42 +0300
Thanks, that's what I thought I was supposed to NOT do. But I have done it, following your encouragement, and it seems to boot just fine.
Thank you very much!
Mine did the same, but after force reboot, booted to the old version and is now suggesting again to install the new version? Now sure how long it was in that position though? EDIT: copied pic and vids to safety via USB, then rebooted and plugged it to another charger and did the upgrade again => this time went OK! (strange!?!) The uptime before the first attempt was NOT long - maybe 1,5 hours after power on this morning
ehakkarainen ( 2018-09-14 09:48:06 +0300 )editAsked: 2018-09-13 10:12:30 +0300
Seen: 1,013 times
Last updated: Sep 13 '18
...it is of course really a problem since I now no longer have a working phone. Should I try some hard re-set (not sure how, without being able to remove the battery). Just wait longer? It's well over two hours now.
wcr ( 2018-09-13 10:37:43 +0300 )editmaintain "power" + "volume up" until the device reboots
DrYak ( 2018-09-13 10:46:53 +0300 )editI had the same bug! I updated 2 devices (mine and my wifes). Mine I updated on battery power, and it hangs on the updatebar after filling it up for about 30 min with no change, then I "resterted the hard way" (powerbutton and volume + button). After that the phone booted 2 times up first bootup ended on the Sony logo, then automatic restart and booted up as usual. No problems since then. the second phone i updated with charger plugged in. Worked without any hard restart. Strange...
Raymaen ( 2018-09-13 13:42:08 +0300 )editthe 2 reboots is normal:
DrYak ( 2018-09-13 14:54:31 +0300 )editthe upgrade process needs to flash a few blobs around
(copy stuff around from the
/dev/sailfish/rootpartition where it un-packed the upgrade RPMs to the multitude of/dev/mmcblk0p{n} device used for this purlose on Android phones)(my bet is on the boot/recovery boot images, we'll have to ask jolla devs).
That's what is going in this short "logo-only" boot.
as Jolla insist on recommending that user only install upgrade while on charger (for obvious power stability reasons) I suspect they internally only test in this configuration.
Whereas we used it differently (on battery (hey, looks you like to live dangerously) or on USB connection (Heu, looks liks I enjoy snooping) ), in non tested configurations. And thus have triggered bugs.
Actually to be more precise, I saw the double reboot as well, and I was connected to the charger (no, I do not like to live dangerously).
wcr ( 2018-09-13 15:33:05 +0300 )edit