Rating: Handset won’t reboot after update
We’re not quite sure exactly how we managed this, but GoMobile News has accidentally managed to ‘brick’ our Nokia Lumia 800 Windows Phone 7.5 (Mango) handset. ['Bricking' is the technical jargon for ruining the handsets firmware so that it won't function. In other words, the device is about as useful as a brick.] The Lumia 800 just won’t reboot and gets stuck at the point where the word ‘Nokia’ is displayed on the screen. The trouble started after we had performed an update which took the handset to the very latest version of WP7 for the Lumia – Update 7.10.8773.98. It worked for a while until the handset ran out of juice. When we tried to recharge the handset it just got stuck.GoMobile News did notice at the time of the firmware upgrade that the handset got quite hot to hold. Which isn’t a good sign.
Anway, if your Lumia handset locks up, what do you do? After all, unlike traditional Nokias there’s no battery that you can take out to perform a ‘hard’ reboot.
The answer is that you hold down the handset’s power button for at least eight seconds and then it will switch off.
With the Lumia 800 Mango (which is officially Update 7.10.7720.68) phone out of action, GoMobile News surfed the Net and found advice on how to restore the handset to the previous (and hopefully working) version of its firmware.
With the handset switched off, press and hold down the power and camera buttons simultaneously.
This will put the handset into a slave mode where the screen shows an image of the phone being connected to a computer via USB.
Which is what you do. Connect the handset up to a computer – in our case a Windows PC and run the host software which is Zune.
When Zune detects the handset’s presence, it will offer to restore the handset to the previous version of its software (before the problematic update).
We selected this option bad sadly the restoration failed and gave us a error code reference number which we foolishly forgot to write down.
The reason this procedure failed was that, once again, in order for the firmware update to succeed, the handset needed to reboot. But it got stuck again and the whole thing failed.
GoMobile News suspects the reason the restoration process failed was that we’d performed not one but two updates in order to reach Update 7.10.7720.68).
See our original story ‘ Latest Windows Phone W7 Mango update confuses’ here. We suspect the problem actually lies in the penultimate update.
So there we have it. A W7 Mango handset which is currently useless.
All we’ve got to do now is work out who we send the handset back to. Orange – which supplied it to us, or Nokia directly?
And, more to the point, did we invalidate its warranty by performing the firmware update ourselves?