Ask / Submit

1.1.4 bricked phone

asked 2015-05-04 23:01:49 +0200

mattikbk gravatar image

My daughter's phone announced system update tonight and she installed the update. When started, the phone shows just a background image and responds only to sweep from top and bottom. Top sweep blanks the display and bottom sweep shows the events view, but only briefly. So it seems like the phone is waiting for pin code input, but it does not display a keypad to input anything. She has disabled all pin code queries.

edit retag flag offensive close delete



At least you have a background image. Mine is totally black. OTOH SSH is working as well as wifi, so i can login…

Blizzz ( 2015-05-05 00:06:59 +0200 )edit

Same exact thing happened. This is so frustrating, what's the point of the beta channel ? :(

oz ( 2015-05-05 10:51:31 +0200 )edit

Funny, i also had a black screen. only when the power cable was connected i could see it was on because of the led. then i turned it off and on again and presto everything was fine again. though it then said it had not yet installed the update. even though i did tell it to install it before

mlatu ( 2015-05-05 20:19:27 +0200 )edit

3 Answers

Sort by » oldest newest most voted

answered 2015-05-04 23:41:41 +0200

juiceme gravatar image

updated 2015-05-04 23:53:12 +0200

That looks exactly like what happened to me when I first updated to 1.1.4, altough it was the first developer preview version then.

I suspect the problem was caused by unbalabced BTRFS filesystem, in hindsight I should have done BTRFS balancing before the update...

Pretty much the only thing to do is to boot the device in maintanance mode and restore device to factory settings. You will unfortunately lose all settings and user contact so I hope you have taken a recent backup and stored that to SD card. (Just taking backup and not transferring it out-of-device will lose your data)

In case you have not transferred your backup, or even not taken the backup, it is still possible to make a backup via maintanance console but it is not a straightaway process; it is something probably a non-linux-knowledgeable user cannot do by just following simple directions.

--- edit ---

Here's the link on how to use the maintanance mode;

edit flag offensive delete publish link more



I was able to boot my device into recovery mode, then using the shell I was able to mount the main phone partitions and chroot in and then using zypper dup I was able to get everything recovered again :-) (Had to do some ip forwarding to get internet access to the chroot as well).

Before doing the update I also ssh'd a backup of /home/nemo (using tar) off the phone just in case.

It wasn't super easy or clean, but it's a way to deal with this if anyone else is affected by it.

(Of note, for some reason version --dup seemed to (?) hang, so I version --verify'd (which said things were wrong), and then zypper dup'd, and then when i version --verify'd again it was all good :-) )

bruce_one ( 2015-05-06 09:24:49 +0200 )edit

@bruce_one, that is a good way to recover from the problems but just as I said, it is not easy for linux-beginners.

It is fairly difficult to write a step-by-step guide detailing how to do it, fixing the device from repair mode console requires pretty much that you adapt to the situation which is different each time :)

juiceme ( 2015-05-06 11:20:25 +0200 )edit

@bruce_one: Can you write down in plain English what you did please? I bricked my phone too trying to install this update, but I'm just a normal user, not a Linux expert. I can use Terminal with clear instructions and have a basic understanding of file system etc., but "mount the main phone partitions and chroot in and then using zypper dup" could as well be Swahili backwards - I'd understand the same amount.

I have a Mac and figured out how to get to the Recovery Mode menu in Terminal through a USB connection, if that helps.

Olle Jolle ( 2015-06-15 02:17:17 +0200 )edit

answered 2015-05-05 12:22:18 +0200

mattikbk gravatar image

I solved the situation by resetting the device to factory settings and running the updates. I also used the recovery mode to backup some files from the phone, since there were no bakcups.

edit flag offensive delete publish link more

answered 2015-05-05 18:55:45 +0200

Camil B gravatar image

updated 2015-05-05 18:56:29 +0200

The same happened to me. The solution was version --dup, which I ran as root through SSH.

Apparently the phone got somehow stuck between versions. pkcon didn't help, but I found this post which mentioned version --dup, used repeatedly:

I only needed to run it once though. The phone was updated and booted properly. Everything was fine.

edit flag offensive delete publish link more


Good for you. In my case the phone wasn't accessible via SSH, so I had no access to these commands.

mattikbk ( 2015-05-05 20:43:19 +0200 )edit

so even if the release is now official it still breaks the phone? does that occur on all the devices or just some?

Dragomir ( 2015-05-06 09:49:03 +0200 )edit

This occurs only on very few devices. I had no problems with my own phone, which is in the beta program.

mattikbk ( 2015-05-06 09:53:39 +0200 )edit

i survived it!!! :) it worked fine for me

Dragomir ( 2015-05-06 13:15:00 +0200 )edit

I'm getting normal releases as a normal user. I updated late because I'm in China and my Internet connection isn't stable, downloading the update often failed. When download finally succeeded and I tried to install it, it broke my phone. Completely unusable now. :-(

For a company that controls both hardware and software on these devices, this should simply not happen.

Olle Jolle ( 2015-06-15 02:45:14 +0200 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2015-05-04 23:01:49 +0200

Seen: 935 times

Last updated: May 05 '15