Firmware update bricking problem

[spike228]

Okay so like a few of you have done, I have also bricked my N95 through the V12 firmware update and I am still in the process of sending my phone to Nokia to have them reflash it. I followed the given instructions extremely carefully but the update still failed.

I just want some information from the people who have also bricked their phone as well as information from people who updated without any problem. I am determined to find out what the hell the cause of the problem is, so in a future firmware update, it doesn't happen again.

What operating system were you running? What version of symbian were you updating from? What precautions did you take prior to installation?

Here is my info if anyone was wondering.

OS: Windows Vista Ultimate
Updating from V10 to V12
Precautions, made sure phone was charged...hell was even plugged into the wall.

This is my first Nokia phone (and first phone that I have blown $600+ on for that matter) and it has left a VERY bitter taste in my mouth. I certainly hope this isn't a problem on Nokia's end. For the record, I only had the phone for a full 36 hours before all hell came crashing down.

edit: just a little clarification, my phone turns on and stay on a blank black screen with the back light constantly on. the keypad stays lit and nothing happens.

[HairyCanary]

I was running XP Pro, updating from v11 to v12, and my phone was plugged into the wall as well. I also made sure I was running the latest versions of NSU, etc. and did my research here first, reading up on what's supposed to happen and what not to do.

It all went very smoothly. Like you, I'd only had my phone for a minute. I didn't feel 100% sure about what I was doing because it was all new and I was a bit nervous about the potential of one small mistake having a catastrophic effect, but I did my homework and followed the prompts and all was well.

[spike228]

I was originally suspecting the problem to be windows Vista or updating from V10 of the firmware.

Thanks for the info. The more info people provide, the better I can narrow down the problem. I've done quite a bit of research and I've only noticed these 2 things to repeat in a pattern but I don't have enough results to really declare anything.

[HairyCanary]

I agree - in the course of my reading I think I recall seeing Vista as a common theme in problematic updates - don't recall anything about v10 (but then again, I wasn't looking for that). It will be interesting to see if a more discernible pattern emerges.

[gadgetman]

If you can connect the phone to your PC, and see BB5 loader as the device with the phone connected, then the handset isnt bricked.

It's only classed as bricked when it will not power on at all.

Right, main causes of bricking are connecting to a PC using a USB hub. Connect DIRECTLY to the PC, NEVER use a hub!

Next is PC speed. Shut down EVERYTHING you dont need to run. Only leave NSU and your net security apps running - ensuring NSU is granted net access should your firewall block it.

Then we come to net speeds/stability. If you have an unstable or slow net speed this *may* mean the files NSU downloads become corrupted. Try to do updates at low net peek times.

[spike228]

The phone turns on but will not read as anything. I have it connected directly to a USB 2.0 port.

[gadgetman]

Did you wait until NSU reproted an issue, or panic when it went blank and remove the cable?

It can take upto 20 minutes between going blank, and NSU completing the update.

No matter how often you do an update, you'll heart will always stop until it powers back on again!

[spike228]

NSU gave an error message saying that the connection to the phone was lost and that I should pull the battery and plug it back in.

[Xenomorph]

Originally Posted by spike228

NSU gave an error message saying that the connection to the phone was lost and that I should pull the battery and plug it back in.

Same thing happened to me when updating my secondary phone, an 6110 Navigator (whatta piece of crap!). I must have plugged and unplugged the darn thing a dozen times (in the meanwhile, the screen was lit up, frozen white) and repeated the update procedure. Eventually, the phone started, but everything (personal settings, gallery, contacts and messages) were as before with the exception that, when checking FW version, it listed it as the updated one.

I'm stongly starting to believe that, along with the appalling aftersales repair services, Nokia has begun not giving a **** about online support aswell...

[beruslee]

Hi, mine had the same problem. During the firmware update, the connection was lost and the message asked to pull the battery & plug it back in. But the worst thing is, the system never boot up. Got a blank screen. Tried Call + '3'+ '*' while pressing the power button. Nothing happened.