We have moved to a new Sailfish OS Forum. Please start new discussions there.
3

Jolla phone won't boot during filesystem checks before 1.1.7.28 update

asked 2015-09-01 10:22:21 +0200

Nielo84 gravatar image

Problem occurred during the filesystem optimizations (before the real 1.1.7.28 update)

After pressing the second time on the button "starting optimizations" the phone rebooted and after a few seconds the phone gives a black screen with only a white notification light (not flashing).

i'm waiting for several hours (> 6 hours), however the phone still not give any sign of life. removing battery and power up the phone manually give the same black screen with only a white notification light.

What should be the following step to do now (contact Jolla inc.???) or something else?? Waiting for an answer?

edit retag flag offensive close delete

Comments

Same problem here, in a couple of tries the phone boot,but then freeze itself and put the scrren in black,with the notification led in very fast intermitent red light. Put the battery off and do not start the phone,and without touching it,it tried to boot, didnt success and started to reboot itself until put the battery off again.

niuran ( 2015-09-01 14:37:02 +0200 )edit

The update procedure seems not clearly described. I ended up in the same state as the previous commenter, which was not what I expected when I allow it to prepare an update. I assumed that this would do reversible things, not start an update that could fail for some reason.

I put my phone on a power plug, allowed to proceed with 'preparations' and left it overnight. Now it will not come back to life. Battery was at 25% (and charging) when I started. Could it be that charging stopped during some stage, draining the battery and doing something nasty? What to do next?

Michiel L ( 2015-09-02 09:50:32 +0200 )edit

Same here. I'm stuck with a black screen and white led since at least 10 hours now. I need my phone tomorrow, so I'm going ahead with recovery mode -> reset :-(

ilpianista ( 2015-09-03 00:19:49 +0200 )edit

2 Answers

Sort by » oldest newest most voted
0

answered 2015-09-02 09:54:13 +0200

Michiel L gravatar image

A reasonable option seems to try recovery mode:

https://jolla.zendesk.com/hc/en-us/articles/204709607-How-do-I-use-the-Recovery-Mode-

If there is something with btrfs, then that will show and can be prepared.

edit flag offensive delete publish link more

Comments

1

I recovered the device, wanted to process the update on a clean phone and again ... the device got stuck again. So I had to recover again.

Then I reread the release notes for the umphth time, and saw that there were updates to Android compatibility which I did not have installed because I do not want that attack surface. I did an experiment, installed Android compatibility and the upgrade did work. Could it be that the mix between software (not) installed from the store and the update could cause a crisis every time? I'm curious to hear if others that did not have Android compatibility installed did have more luck, or it was just coincidence...

Michiel L ( 2015-09-03 08:46:17 +0200 )edit
0

answered 2015-10-13 14:52:50 +0200

Michiel L gravatar image

I just tried to update another clean (no Android compatibility installed) device, and the same thing happens. So apparently it is a hard requirement before the update to temporarily install Android ... Can this be fixed?

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

Question tools

Follow
1 follower

Stats

Asked: 2015-09-01 10:22:21 +0200

Seen: 239 times

Last updated: Oct 13 '15