Ask / Submit
4

Warning! - Phone bricked after updates

asked 2014-10-04 13:48:29 +0300

ninepine gravatar image

updated 2014-10-04 15:20:19 +0300

ssahla gravatar image

Not really a question but a warning. (Although answers on how to solve are welcome).

A whole series of updates appeared in openrepos.net this morning showing "Jolla" as the source so I applied a few (Update for Maps and Browser) and now find my phone is bricked. Some of the updates said "QT5"

Browser and Maps wouldn't load after the update and when I rebooted the phone wouldn't start..

When I try and boot the Jolla logo appears and then the screen goes blank.

Will I have to return to Jolla or is there a way to do a reset please?

edit retag flag offensive close delete

4 Answers

Sort by » oldest newest most voted
2

answered 2014-10-04 13:59:58 +0300

peter-berlin gravatar image

... i had the same problems 14 days ago and made a short instruction in a german forum:

http://www.pocketpc.ch/jolla/218231-anleitung-selbsthilfe-jolla-laesst-mehr-starten.html

http://www.pocketpc.ch/jolla/218231-anleitung-selbsthilfe-jolla-laesst-mehr-starten.html#post2048560

edit flag offensive delete publish link more

Comments

Thanks for the links Peter. From these I found https://together.jolla.com/question/22079/howto-all-pc-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/#post-id-22127 and have used option 5 in Jolla Recovery to do a "Try btrfs recovery if your device is in bootloop". Unfortunately this doesn't fix it.

it looks like I will have to use Jolla Recovery to do a Factory reset. ;(

ninepine ( 2014-10-04 15:46:52 +0300 )edit

... same to me - factory reset was necessary :-((

peter-berlin ( 2014-10-04 22:20:30 +0300 )edit

Thanks Peter. Yes a factory reset was necessary - a warning to all!

ninepine ( 2014-10-04 23:33:11 +0300 )edit

Every update I've got Jolla updates through Openrepos just before the official update is out. It worked for me every time but I won't be updating anymore through Openrepos.

BonoNL ( 2014-10-05 13:22:09 +0300 )edit
2

answered 2014-10-05 21:30:57 +0300

Basil gravatar image

@ninepine did you manually changed software release version, before that happened(I.e. executed ssu re X.XX.XXX with any version in terminal)?

edit flag offensive delete publish link more

Comments

Yes. I was getting a problem with updates after a crash. One of the answers here on together advised to do this because the ssu version was "latest".

ninepine ( 2014-10-05 23:57:53 +0300 )edit
4

instead of 'latest', it is better to use known stable release version as @nthn suggested with his answer. Anyway, warehouse updated, so it will not show non-openrepos updates to users.

Basil ( 2014-10-06 00:00:27 +0300 )edit
1

answered 2014-10-04 15:07:10 +0300

ssahla gravatar image

https://together.jolla.com/question/22079/howto-all-pc-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/

edit flag offensive delete publish link more

Comments

Thanks. Yes this fixes it but I've had to do a factory reset and am reinstalling all my apps settings and data. :(

ninepine ( 2014-10-04 23:32:32 +0300 )edit

Good that you got your phone working, too bad you need to go through all the reinstalling... But you really shouldn't update Jolla apps / components through Openrepos, that may screw up your system (as you've learned). My guess is those updates you installed require Sailfish update 9, which is not out yet. Those updates will come through the official channel when update 9 is out.

ssahla ( 2014-10-04 23:41:34 +0300 )edit

@ssahla, the problem in not in openrepos, since source of packages was 'jolla' repository. If jolla released partial non-functional update, same brick will occure with pkcon update command. That could happen if @ninepine either manually switched software version, to recieve beta update, or jolla-stuff did occasionally pushed beta packages to stable repository.

Basil ( 2014-10-05 21:23:50 +0300 )edit
0

answered 2014-10-05 22:15:20 +0300

nthn gravatar image

Something somehow has probably caused your device to look to the 'latest' repository for updates, rather than the '1.0.8.19' repository. I've had that problem (in a different way) and managed to get it fixed by entering 'ssu re 1.0.7.16' (at the time, now it would be 'ssu re 1.0.8.19') in the terminal. I assume this 'latest' repository sometimes has updates that aren't yet functional. Of course, this won't help for you anymore, but it could be of help for others who suddenly notice lots of package updates appearing even though the update isn't out yet.

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

Question tools

Follow
3 followers

Stats

Asked: 2014-10-04 13:48:29 +0300

Seen: 1,490 times

Last updated: Oct 05 '14