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

[Bug] Brand new Jolla bricked while downloading essential apps and fw upgrade

asked 2015-01-22 02:34:39 +0300

HtheB gravatar image

updated 2015-01-27 18:57:36 +0300

r0kk3rz gravatar image

I just received a new Jolla, so it was on the lowest firmware. the phone was downloading the Jolla essential apps, but I also started the "Firmware upgrade download". In other words: everything was downloading at once. (It was still downloading the Firmware, it was kinda like at 10%, so it wasn't upgrading yet ofcourse)

But then, the device gave me "Jolla store errors". So I rebooted the device. After the reboot, the phone bricked: Jolla logo on startup, then a black screen. The phone is actually still on, because if you try to power on again, it will actually turn off (a red LED at the bottom will show up, like when it's turning off the phone)

What do I have to do now? Any idea?

edit retag flag offensive close delete



Have a look here for information on recovery of your device; https://together.jolla.com/question/22079/howto-all-computer-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/


Edz ( 2015-01-22 03:21:48 +0300 )edit

Yeah I already tried, it gives me the following error: Flashed recovery image is too old and does not support phone clearing.

I already followed this: https://jolla.zendesk.com/hc/en-us/articles/202208763#31 But still the same problem.

I just find out that this guy had the same problem like me but there is no solution on it :( https://together.jolla.com/question/74278/black-screen-after-switching-on/

HtheB ( 2015-01-22 03:25:10 +0300 )edit

Sounds like a job for care@jolla :(

Edz ( 2015-01-22 03:44:28 +0300 )edit

Ugh.. But I just received it! :'(

HtheB ( 2015-01-22 03:52:37 +0300 )edit

Check out the final remarks from the guy who posted; https://together.jolla.com/question/74278/black-screen-after-switching-on/

"My Jolla lives!" - seems he had to repeat the process twice before the phone recovered.

Edz ( 2015-01-22 04:02:26 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2015-01-28 01:53:40 +0300

HtheB gravatar image

updated 2015-09-11 20:03:30 +0300

The only way I could fix my Jolla, was to restore the whole firmware in it using the 'dd' command in the shell (within the recovery mode).

Now that my phone is fixed, I think Jolla should really look for what causes this... because there could be some n00bs out there who doesn't want to make use of shells and commands....

Please Jolla, fix this very important bug....!

Here is a README file on how to fix it!!

edit flag offensive delete publish link more



Shipping phones with current FW images would help^^

chemist ( 2015-01-28 02:45:46 +0300 )edit

Thank you HtheB you really helped here.

I'm so disappointed that this bug still exists after such a long time and will easily cause a brick.

Waxberry ( 2015-09-11 21:05:11 +0300 )edit

As far as I know, it should be fixed by now. But if you're still on a lower firmware (like after a factory reset), the bug of course re-appear :( Glad that it worked out for you! :)

HtheB ( 2015-09-11 21:08:26 +0300 )edit

answered 2015-01-28 01:45:11 +0300

Odorobo gravatar image

Man, i had the very same trouble. Here is how i solved it:


Don't despair, you will be able to fix it.

edit flag offensive delete publish link more

answered 2015-01-27 18:11:05 +0300

weberik gravatar image

same thing happened to me, it solved it in recovery mode. first i removed the battery for a few minutes. then i went in recovery mode and tried kinda every option, i think what solved the problem was the filesystem recovery (option 5)

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

Question tools

1 follower


Asked: 2015-01-22 02:34:39 +0300

Seen: 869 times

Last updated: Sep 11 '15