We have moved to a new Sailfish OS Forum. Please start new discussions there.
4 Upgrade problem

asked 2014-10-22 23:41:10 +0200

ninepine gravatar image

Having downloaded and started the upgrade started to run and I left it for some time to complete. I now have a blank screen and blue light. The blue light is because the phone is on charge (as recommended)

Is it safe to try and reboot? (I am upgrading from 1.08.21 and had plenty of spare memory)

edit retag flag offensive close delete



To find out if it's ok or not, some hunting for the reason for this might be good... Did you have any others than Jolla Store apps installed? How about any of the Google Play services? Did you have anything else special maybe just in your phone? (other issues, for example)

simo ( 2014-10-22 23:59:15 +0200 )edit

It is safe to short press the power button to see if the screen turns on. Don't long press it.

xfade ( 2014-10-23 00:00:32 +0200 )edit

Yes I have Google Play services and the Play store installed. Also Amazon store and Warehouse. A touch on the power button does nothing. Any ideas please @simo

ninepine ( 2014-10-23 00:05:19 +0200 )edit

Having the same problem here although after the "Sailfish" install image disappeared, I got over excited and plugged in the USB. After that, it appeared as though the phone had powered off so like a fool I tried to power it on (long press).

Anyhow, now when I try to boot the phone the normal Jolla booting logo pops up for a few seconds and then the phone powers off.

Does anyone have any advice ?

JollaTides ( 2014-10-23 00:05:28 +0200 )edit

Do you (both) find anything useful from the link below? (recovery menu as the last option)

simo ( 2014-10-23 00:12:25 +0200 )edit

3 Answers

Sort by » oldest newest most voted

answered 2014-10-23 00:07:46 +0200

simo gravatar image

This might help you both/all: https://together.jolla.com/question/59874/release-notes-opt-in-upgrade-to-software-version-11038-uitukka/#59874-os-update-process

If not, let's keep up DIT to find the right solutions :)

edit flag offensive delete publish link more


Thanks so much @simo, I read that before attempting the update but unfortunately none of the other options are feasible at this stage so I think I'm going to have to go into recovery (not just for my Jolla!).

If you or anyone else has any other bright ideas I'm all ears! Thanks, Timo

JollaTides ( 2014-10-23 00:19:50 +0200 )edit

OK I removed the battery to go through the recovery mode procedure. When the battery was reinserted the Jolla screen appeared and the phone appeared to boot. When the main screen came up I tried opening Settings but it won't open. The screen also blanks after a few seconds making it difficult to do anything on the screen. It seems from the link you provided that I need to delete /home/nemo/.cache/store-client/os-info and then stop the store process. The problem is doing this when the screen blanks whenever I try and run say file manager. The screen is also showing that an OS update is available.

Do I need to try and access via SSH? If so how do I find the IP to use?

ninepine ( 2014-10-23 00:40:20 +0200 )edit

@ninepine Settings (if you get it open) > System > Developer tools > Enable SSH (give a new password, remember it) and you'll see IP for both WLAN and USB (wlan is much easier to access). However, you can delete it also in the Terminal app, just with smaller keyboard in the phone. That's visible in your launcher when you activate the developer tools, but enable SSH connection as well to give the new root password (deleting might require root access)

@JollaTides How's your memory situation?

simo ( 2014-10-23 00:50:42 +0200 )edit

@ninepine I've decided to leave this to the morning now but will chk back here tomorrow and hopefully we'll find a workaround by then. I've also contacted Jolla in case there's a quick fix and will post here their response. Good luck with it and hope you find a solution in the meantime! :)

EDIT @simo: internal memory had around 3gb so fine :)

JollaTides ( 2014-10-23 00:52:54 +0200 )edit

@JollaTides@simo Thanks for the pointers. I'm going to have to leave this till tomorrow (evening) now too but I'll see if I can connect to the phone via SSH / Wifi in the meantime. Good luck too!

ninepine ( 2014-10-23 00:56:14 +0200 )edit

answered 2014-10-23 09:26:47 +0200

Nieldk gravatar image

Had to factory restore my phone, and then I did incremental update (becomes after factory reset). I updated from and that simply ended with the phone not booting - I could see some conflicting qt5 libraries was the issue FTR. So, now it is on and I have only one (issue) in terminal, pkcon will fail operations (authorization failure) - unless it is run as root ! ?

edit flag offensive delete publish link more


@Nieldk - that's expect, you can also just use 'devel-su -p' and then use pkcon, wasn't it like that already in update 8 ? can't really remember long time ago :)

VDVsx ( 2014-10-23 09:34:38 +0200 )edit

@Nieldk were you running Google services before the upgrade? Just want to see if there is a common theme here. As you can see I'm probably going to have to do a factory reset so further information on the conflicting qt5 libraries and whether you had to do anything to overcome that issue would be really helpful please.

ninepine ( 2014-10-23 09:35:13 +0200 )edit

@VDVsx In pkcon would run as nemo. (for me at least). @ninepine Google services I suppose was present (from Jolla android support, not the hack for Google Play). There were a bunch of conflicting Qt libraries (not sure if I can get the log again since I reset the device). I know for a fact that I didnt create my 'own' Qt libraries. But it might very well be some from warehouse. I had several apps from openrepos installed, but removed those that I kind of suspect would cause issues (patch manager and patches being the biggest concern that I know could cause issues)

Nieldk ( 2014-10-23 09:40:12 +0200 )edit

@Nieldk in could worked because you had warehouse installed (it addes policy for nemo user allowing it to use packagekit). After factory reset, there is no warehouse and it's policy, so pkcon fails.

Basil ( 2014-10-23 17:02:28 +0200 )edit

answered 2014-10-23 16:38:34 +0200

As recovery mode is not recommended for Sailfish versions 1.0.8.XX according to this page: https://jolla.zendesk.com/hc/en-us/articles/202208763-How-do-I-use-the-Recovery-Mode-

I have had a response from Jolla stating the only option is for a reset:

"Yes, currently Recovery Mode is somewhat broken for devices with SailfishOS 1.0.8.XX. The only function that works is Device Reset, meaning that all your data will unfortunately be wiped.

In order to get Device Reset to work, you have to follow the recovery mode instructions until you are set up, and you have the Recovery Mode menu visible on your computer's screen.

Then, please follow these instructions:

This script below can be used to run the factory reset on broken Update 8 devices:

Copy attached "recovery-menu" file to your SD card. Please, note that this file is not a .TXT file. If your computer operating system adds .txt to the end of the file, the script will not work.

Insert the SD card into Jolla Enter Recovery Mode (see this article, if needed) Choose option "4) Shell" Type the following command:

mount /dev/mmcblk1p1 /mnt

Then, type the command:

cp /mnt/recovery-menu /usr/bin/recovery-menu

Exit Shell Choose "1) Reset device to factory state" Type "y" to run the factory recovery. If you update your device to Update 9 (or newer), Recovery Mode works again. "


edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2014-10-22 23:41:10 +0200

Seen: 939 times

Last updated: Oct 23 '14