Ask / Submit
3

OS upgrade probably failed

asked 2017-08-30 01:52:15 +0300

objectifnul gravatar image

Hi, juste like previous upgrades, 2.1.1.26 upgrade is apparently going to fail: the progress bar stopped at about 80% after 30 minutes. One hour later, nothing has changed. Should I wait more ?

edit retag flag offensive close delete

Comments

1

Didn't wait more than two hours => Recovery mode and reset. So I visited Finland (and some parts of Sweden):

1.0.4.20 Ojijärvi

1.1.2.16 Yliaavanlampi

1.1.7.28 Björnträsket

1.1.9.30 Eineheminlampi

2.0.0.10 Saimaa

2.1.1.26 Jämsänjoki

Phew. As all patches were removed before upgrade, as well as problematic apps (call recorder, phonehook), I'm suspecting one of my usual apps was guilty this time and previous times. Unfortunately, I didn't find out which one.

objectifnul ( 2017-08-30 03:51:21 +0300 )edit

It's always nice to reminice what the UI looked like in previous releases whaen doing that :)

I have had to go the whole route a few times when an upgrade fails, it's a no problem really as long as you just have some time to do it.

juiceme ( 2017-08-30 07:37:20 +0300 )edit

@objectifnul so you have succesfully updated from 2.0.0.10 to 2.1.1.26? From the version history I guess you too have a JP01.

I'masking because of this I'm holding the update:

https://together.jolla.com/question/164682/cant-update-to-211/?answer=164714#post-id-164714

c.la ( 2017-08-30 10:02:24 +0300 )edit

JP01 should update directly from 2.0.0 to 2.1.1. JollaC might not.

jovirkku ( 2017-08-30 11:57:28 +0300 )edit

Update looked like going ok, took really long over an hour, after restart at first it looked ok, but not wifi, no networking, giving the error "no networking available, reboot", nothing helps, no networking, no usable phone. in CSD everything woth networking, usb, bluetooth, wifi they fail.. Leaves noting much that factory reset and a day of work. Bit disappointed.

Update: I removed the keyboard other half and my phone just started ok, bit confused here now

filipb92 ( 2017-08-30 12:19:24 +0300 )edit

4 Answers

Sort by » oldest newest most voted
4

answered 2017-08-30 14:33:22 +0300

jovirkku gravatar image

updated 2017-08-30 14:35:45 +0300

Anyone facing an OS update failure and willing to help us, please read the following support article. We would appreciate getting some logs from your device. They would help us figuring out what went wrong.

https://jolla.zendesk.com/hc/en-us/articles/205601317-Failure-with-OS-update-Collecting-logs-and-completing-the-update

/var/log/systemupdate.log
/var/log/systemboot.log
/var/log/zypp/history

Should you prefer delivering your logs to us in private, consider filing a ticket at Jolla customer support and attaching your logs there.
Do not forget to tell us which device you have, the OS version before the update, detailed steps leading to the failure and if you had some changes in your system (apps etc.) originating from outside of Jolla Store.

edit flag offensive delete publish link more

Comments

Would like to help. Unfortunately, I was in an emergency, as my three years old Jolla isn't a geek toy, it's my everyday phone. So, recovery mode was my quickest option. Vital data were backed up before of course, so no real harm. This doesn't include system logs: lost at sea...

objectifnul ( 2017-09-10 23:14:20 +0300 )edit
2

answered 2017-08-30 12:48:59 +0300

Lutwolf gravatar image

After two days of failing updates I tried it via terminal (devel-su, ssu release 2.1.1.26, version --dup), and it worked like charm. I do not know why it worked that way, but maybe that helps a little bit... cheers

edit flag offensive delete publish link more

Comments

Will do so next time ;-)

objectifnul ( 2017-08-30 13:28:13 +0300 )edit

Thanks for the hint! Coming from 2.1.1.23 all my attempts to update failed miserably. That did the trick.

Jordi ( 2017-09-12 22:23:01 +0300 )edit
2

answered 2017-09-01 00:40:02 +0300

richie gravatar image

updated 2017-09-01 00:41:46 +0300

I have managed to recover from the black screen after attempting the 2.1.1.26 update without having to reset.

I followed Jolla Care's links to the recovery shell and spent time backing up to SD card, https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-to-use-Recovery-Mode

then thought I may as well have a go fixing it, before resetting. I used this post

https://together.jolla.com/question/22079/howto-all-computer-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/?answer=45710#post-id-45710

to mount storage and chroot in. Setup networking, DNS /etc/resolv.conf, set date to avoid SSL errors, downloaded zypper (it wasn't installed) from Mer archive http://forum.jollausers.com/jolla-phone/installing-packages-with-zypper-from-mer-project/

In the shell the latest logs in /var/log/ showed harbour-callrecorder errors. So I first of all deleted the executable and everything I could find related to harbour-callrecorder.

I disabled all openrepos repos and then refreshed repos using ssu. Some errors appeared during repo refresh - from memory - d-bus errors, and it disabled some other repos.

zypper refresh, then zypper update. It attempted to update 200 packages, most were okay, some complained about chroot, but once finished, I rebooted and my Jolla came back to life! I then went in to the terminal and as root did version --dup and it installed some more packages, reboot and all still working, I've avoided a reset.

edit flag offensive delete publish link more
0

answered 2017-08-30 11:29:05 +0300

mastal gravatar image

You are lucky - your upgrade failed, in my case I got info update get errors - reboot and that was end.
I have two JP01 and on both I had the same issue: factory reset and install all updates. I did upgrades from different versions so I think issue is on latest 2.1.1.26.

edit flag offensive delete publish link more

Comments

I had the same problem on my Jolla 1. I found later that I had to remove also call recorder, thank's god I made a backup!

Ali Sajid Rehman ( 2017-08-30 13:40:46 +0300 )edit

I guess I should have read the release notes... I also have call recorder and a failed update.

evk ( 2017-08-30 13:49:17 +0300 )edit

I always removed it, but this time I forgot! Never update the phone in the night!

Ali Sajid Rehman ( 2017-08-30 13:52:29 +0300 )edit
1

Having Call Recorder installed does not cause any SailfishOS update issue, having its demon (background task) running while updating SFOS does!

So it is sufficient just to stop Call Recorder completely, before updating SFOS (did that for the last two SFOS updates, worked well).

olf ( 2017-08-30 22:16:17 +0300 )edit

Would be nice if kinks like these could be fixed.

evk ( 2017-08-31 13:29:13 +0300 )edit
Login/Signup to Answer

Question tools

Follow
3 followers

Stats

Asked: 2017-08-30 01:52:15 +0300

Seen: 914 times

Last updated: Sep 01 '17