I have black US version of N97. I was trying to update firmware on it through Nokia Software Updater, but during the beginning of the update process Windows XP (SP3) started installing flash drivers or some sort and had an issue with them. Next thing I know my N97 has white screen and everything is locked up. I knew it was bricked at that point... So, I took ou the SIM card and the battery for hours. The result is that now my phone does not even power on. There is no white screen. The only way to get something out of it is to hook it up to recharge and then press power button - it vibrates for a moment, but the screen remains black and this happens only when you plug the recharge cable through power outlet.
I tried to follow the guide on how to fick my bricked N97, but there is a big issue - my PC does not detect it. I uninstalled everything Nokia related from my PC, all drivers, all all all folders... Then I reinstalled Ovi 1.1 (which had all the right drivers) but my phone is still not detected....
Nokia USB Flashing Generic and Nokia USB Flashing are detected. When I run the flash program (after Navifirm and JEF emulator use) and it checks for communication links and etc... it simply doesn't find my phone!
So, is it super-bricked beyond user repair???
P.S. What is odd is that you would think that if Windows didn't have the right drivers installed, the flashing processes wouldn't have (or shouldn't have...) started.
unless you changed the product code to get the new firmware it should be covered by nokia warrenty just give them a call, but if you fiddled with the product code then you are in the brown stuff mate but im sure one of the members will have the answer.
ps. have a dig around the forums just search for "bricked" and im sure you will find a post of someone who has had the exact symptons you are having and a answer sorry i cant be of more help best of luck.
Try a hard reset using these instructions:-
http://mynokiablog.com/2009/07/18/how-to-hard-reset-your-nokia-n97/
Known as the Vulcan Death Grip I believe.
Thanks for help.
Hard reset method did not work... I do have warranty and I doubt I changed any codes (since I can't get it to flash). I would just hate to wait 2 more weeks for the repair process...
Oh cool! I was messing with hard reset buttons while USB was connected and some things got turned on, some ROM driver worked. The flashing process began, but in the end of the process I got this message:
Prodcode:
Setting test mode...
Failed! Aborting!
Done!
Failed? I turned the phone back on and BAM - it works and it got the latest firmware on it!
So, does that mean I just voided my warranty by changing product code and wasted $20 for extra warranty?
Umm.. what product code did you change it to?
Did you go from a 507 (NAM) to a normal 505?
ouch.. that would defintely screw it up..
Oh no, I chose 507 NAM Black NAM Version... like the very default black NAM without any country name next to it...
I also had CRT 308 ticked and some people said to have unticked...
What about that end message with FAILED in it? It said FAILED after testing, so maybe flashing didn't fail.
The real question I am asking is this - should I try to RE-flash it or just enjoy the phone (its working without any problems right now).
umm.. which product code were you before the 507 NAM Black version? If it is the same before and after.. then you really didnt change the product code as such..??
bchliu wrote:umm.. which product code were you before the 507 NAM Black version? If it is the same before and after.. then you really didnt change the product code as such..??
I don't know... I mean its a US version, and I read in several places online that its the NAM - NAM version, which is what I chose. I know all calling and other features work, no instability, perfect driver-esque... connection without any issues. 😊
BTW, is it smart to uninstall default apps? There are things I don't need, but uh... it has some API Brdges and oddballs app. names that sound like system stuff and you never know what is linked to what and next thing you know things could be borked. Or not?