# Jolla Phone failed to update and started rebooting in loop

Today is 10.10.2017. About 2 hours ago my Jolla phone notified that it had a new system update. I downloaded the update and started the update process. After some time I looked at the phone and it said the update had failed. The text was not scary - it said I could retry the upgrade later. There was one button and I clicked that. The phone started rebooting is a loop.

I see a Jolla text for maybe 20 seconds after which it flashes black. Then the text comes back for another 20 seconds.

Do I have any way to fix the phone?

edit retag close delete

Sort by » oldest newest most voted

here you have a solution https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-to-use-Recovery-Mode

I think you should try option 5 which is "try btrfs if your device is in boot loop". if it doesn't work you should make backup and then factory reset.

more

Option 5 did not help. I backed up the data and reset the device. I wonder how many system updates I need to install :-/ Thank you for helping me out!

( 2017-10-10 22:35:14 +0200 )edit

Had the same experience with a Jolla 1 that had been unused for some months. Recovery shell and /var/log/systemupdate.log, problems start with line:

Oct 15 12:55:11 Sailfish ssud[6544]: /usr/bin/ssud: error while loading shared libraries: libsystemd-journal.so.0: cannot open shared object file: No such file or directory


ldd /usr/bin/ssu shows that indeed some systemd shared libraries are missing. A root explanation could be the last lines of /var/log/zypp/history :

# 2017-10-15 09:55:10 harbour-callrecorder-0.6.2-1.armv7hl remove failed
# rpm output:
# Stopping service...
# Failed to get D-Bus connection: No such file or directory
# error: %preun(harbour-callrecorder-0.6.2-1.armv7hl) scriptlet failed, exit status 1
# error: harbour-callrecorder-0.6.2-1.armv7hl: erase failed


Okay, at least my bootloop might have been caused by me not removing callrecorder. I guess I've successfully updated the phone multiple times with it installed before, but it caught me in the end.

Are there any log files / other data that could be of any use for any common good? I'll probably play around with the recovery shell and see if I can make it boot manually before resetting, as the device is not in use.

more