Hi John
Make sure the nokia firmware are in C:\Program Files\Nokia\Phoenix\Products\RM-505
It took a few restart's of Jaf to to get it to recognise the new files.
Also pressing the power on button at the right button took a few goes.
Persistence is the key 😉
Cheers David
Fats wrote:Holy crap this worked!!Everyone that managed to brick their phone using JAF to debrand then NSU to update needs to check this out.
I used NAVIFIRM to download the v11 firmware set.
I had to fiddle with JAF because it didn't automatically pick up the correct ROMs, so I had to select them manually as follows:MCU Flash file: C:\Temp\N97\firmware\RM-505_11.0.021_prd.core.C00
PPM Flash file: C:\Temp\N97\firmware\RM-505_11.0.021_prd.rofs2.V01
CNT Flash file: C:\Temp\N97\firmware\RM-505_11.0.021_C01_prd.rofs3.fpsx
APE Variant file: C:\Temp\N97\firmware\RM505_507_11.0.021_uda1_001.uda.fpsxSelect Maunal Flash, Dead USB, Factory Set and Normal mode and hit flash.
My N97 is now working again. I'm guessing it's on the right firmware because that's what I flashed, what's the *# code to check?
TYVM for the heads-up, andonevris.
Thank you so much mate for making this is so much easier & step by step.
I was trolling the forums for hours trying to find .ini files and all this crap...but anyways...
My ressurection goes fine until it gets to the "Pooling Phone" bit. The screen goes all LCD liney, then stops.
Then, JAF says something along the lines of:
"Did your phone turn back on, Yes No?"
when I click "No" cos it didn't back come back on, it just says "Done!" and finishes.
Though its not actually done, as the phone doesnt turn back on or do anything.
So I try it all again, but then click...YES
But when I click "Yes" JAF thinks for a while then says...
"Phone not found...
Second try...
MCUSW: (null)
APESW: (null)
VariantSW: (null)
Prodcode:
Setting test mode...
Failed! Aborting!
Done!"
It doesn't turn on or anything.
And JAF has finished.
All the while my laptop keeps making the "Ba-dum" noise of a USB being plugged in & out so it must have done something good?!
Does anyone have any ideas of what to do when it stops after Pooling?
Or tips as to why this might be happening?
Any help would be appreciated cos im sure if I take it to a Nokia Care Centre they'll whinge and chastise me....
Even if you email me its all good I don't mind i'd just like my phone to be working again after all this unpleasantness...
thanks again guys
jmcgrath wrote:Folks,I'm struggling here so please help.
When trying to locate the MCU file it is only letting me select CMT files. I can select the PPM, CNT and APE files without any problems.
I have also copied the jaf 1.98.64 ini files and I can see the N97 option but it does not seem to pick it up.
Any suggestions?
Thanks,
John
Yes I had the same issue - took me a couple of tries to discover if you simply type the path to the C00 file it'll accept it no problem.
Hope this helps
Woooooop Woooooop Wooooooop !!!!!
I managed to get my N97 working again.
A huge thank you to everyone, especially Fats and davwil. It was Dave's final comment of putting the FW files in a RM-505 folder that made the difference I think. I just had them sitting in the products folder. As soon as I did that JAF picked them up, everything was green and the re-flashing worked first time.
So thanks again everyone. I have to go now before the tears of joy short out me keyboard.
John
Just wanted to say thanks to the guys that have posted in here. You've saved my bacon (and my phone). Now working again thankfully. 😊
One thing I have noticed is that I no longer have a start up tone when I power on the phone. I think I missed out the media pack file when I flashed the handset :redface: Is it possible to just follow the procedure again but only select the media pack file to correct this?
Nokion, you better just flash it again, but with NSU. Should be easy.
Mike.mp wrote:Nokion, you better just flash it again, but with NSU. Should be easy.
After my previous encounter this afternoon I'm pretty wary of using NSU again. Perhaps I'll just go through the flashing process again.
Its up to you, but it wont harm phone now 😊 Take easy way, and IF it won't work, you already know how to fix it.
Thanks a lot guys, I managed to get mine flashed and unbricked! I recommend copying over the latest .ini files from jaf version 1.98.64 and then you can just select 'use .INI' option and select the correct model, it then sorts all the firmware files out (provided they are in the C:\Program Files\Nokia\Phoenix\Products\RM-505). Then its just a case of timing, to turn the device on when it says. Took a few attempts.
All good. Thanks again everyone! 😊
It was a real pleasure to share the pain. 😎
Now I would like to know why the NSU update broke the phone quite so badly.
Is it only vodafone N97's that have had this problem or is it more wide spread?
Cheers David
Mike.mp wrote:Its up to you, but it wont harm phone now 😊 Take easy way, and IF it won't work, you already know how to fix it.
Fair point. I've done it now and the tone has returned. Still not getting any widgets though but that's not an issue really.
davwil, I think someone in this thread stated it happened to their 3 handset too.
Hi, My N97 is not bricked, but i am trying to install the last firmware.
I have followed the instructions above, but I am start with the phone turned on, and DEAD USB option unselected.
It re-boots the phone, and gets as far as stage 2, and the stops. I turn on the phone and it as if nothing has changed.
What am i doing wrong?
JAF version 1.98.62
Detected PKEY: 9000D75A
Card life counter: 99.99%
P-key nokia module version 01.02
FBUS INTERFACE NOT CONNECTED!!!
USB Cable Driver version: 7.1.16.0
Changing mode...Done!
Detected P-KEY: 9000D75A
P-key nokia module version 01.02
Init usb communication...
Reading product code...
Product Code: 0585262
Searching for JAF saved location of ini...
Checking path: C:\Program Files\Nokia\Phoenix\Products\RM-505\
Searching for default location of ini...
Checking path: \Products\RM-505\
Searching for JAF saved location of ini...
Checking path: C:\Program Files\Nokia\Phoenix\Products\RM-505\
Scanning ini files...
Searching for default location of ini...
Checking path: \Products\RM-505\
Checking path: C:\Program Files\Nokia\Phoenix\Products\RM-505\
FILES SET FOR FLASHING:
MCU Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-505\RM-505_11.0.021_prd.core.C00
PPM Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-505\RM-505_11.0.021_prd.rofs2.V01
CNT Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-505\RM-505_11.0.021_C01_prd.rofs3.fpsx
APE Variant file: C:\Program Files\Nokia\Phoenix\Products\RM-505\RM505_507_11.0.021_uda1_001.uda.fpsx
Languages in ppm: English,German,Russian,Bulgarian,Romanian,Ukrainian
Backing up CRT...
Detected P-KEY: 9000D75A
P-key nokia module version 01.02
Init usb communication...
Reading IMEI...
C:\Program Files\ODEON\JAF\ProgData\354225031224293_CRT_backup_21527.pm
Done!
Backup CRT OK!
Detected P-KEY: 9000D75A
P-key nokia module version 01.02
Init usb communication...
Searching for phone...Found
Reading SW version...ICPR72_09w17.3 10.0.012
Reading battery value...4065 mV
Init usb flashing...
Reading flashid...
CMT: 004000EC <=> SAMSUNG (SEC) -> KAT00F00RA
APE: 00000000 <=> Flash -> not detected
Verifing ADL communication... Status byte 7
Rebooting to flash mode...
Waiting for the phone to reboot...
Searching for phone...
Sending RAW loader...
Using 009.008.003
Elf2flash 09.11.000
CMT RAW loader...
Patching RAW boot step1...
Patching RAW boot step2...
Patching RAW boot step3...
Sending RAW Loader...
....................Loader Sent!
Stage 2 starting...............
its ok i sorted it. It turns out you have to break your phone first, before you can upgrade lol.
So i changed the prod-code, used the nokia updator to break it, then JAF fixed it.
Winner. Cheers for the info guys.
291 wrote:Thanks a lot guys, I managed to get mine flashed and unbricked! I recommend copying over the latest .ini files from jaf version 1.98.64 and then you can just select 'use .INI' option and select the correct model, it then sorts all the firmware files out (provided they are in the C:\Program Files\Nokia\Phoenix\Products\RM-505). Then its just a case of timing, to turn the device on when it says. Took a few attempts.
All good. Thanks again everyone! 😊
What or where are these .INI files?
I've installed/copied whatever the latest JAF 1.98.64 .ini's over.
So when I click "use ini" yes, the N97 is listed.
Then it searches the folder and says there's nothing there.
Um, yes there is, there's the 14 files I downloaded off Navifirm.
I can paste them manually doing in order such as MCU, PPM, CNT whatever
but then it gets to "Pooling" and stops.
Whats happening?
If Nokia Care can't fix this phone i'm going to throw it off my local bridge.
I didn't pay $1000 to have a paperweight thanks to their suggested Software Upgrader that breaks your phone.
MrAaronVenn wrote:What or where are these .INI files?
I've installed/copied whatever the latest JAF 1.98.64 .ini's over.
So when I click "use ini" yes, the N97 is listed.Then it searches the folder and says there's nothing there.
Um, yes there is, there's the 14 files I downloaded off Navifirm.I can paste them manually doing in order such as MCU, PPM, CNT whatever
but then it gets to "Pooling" and stops.Whats happening?
If Nokia Care can't fix this phone i'm going to throw it off my local bridge.
I didn't pay $1000 to have a paperweight thanks to their suggested Software Upgrader that breaks your phone.
I had the same issue after downloading the files through Navifirm, jaf just wouldn't find them. I then downloaded the image using phoenix and jaf then picked up the previous files, very bizarre.
Incidentally I probably wouldn't have had to use jaf if the damn NSU didn't hang halfway through the flashing process, damn you nokia and thank you jaf 😊 .
Please don't throw your phone in the river - recycle it responsibly - as it contains some nasty chemicals for which the fish or ducks will not thank you for. Or better yet give it to some one else.
or
You could read the instructions at http://dailymobile.se/forum/index.php?topic=1792.0 which talks about the need to download the navifirm tool which will download the necessary n97 firmware to your desktop pc.
Cheers David
The method that worked for me was to not use the 'use ini' function and just do it all manually. Make sure that you have all the correct boxes checked and try again. It may take a few goes as mine didn't work first, second or third time.
Maybe you could post your log up on here and someone might take a look at it for you?
MrAaronVenn I was having the same problem, but when I had the FW files in the products folder under C:\Program Files\Nokia\Phoenix\Products. When I created the RM-505 folder under products (C:\Program Files\Nokia\Phoenix\Products\RM-505) and then copied the FW files in there everything worked first time.
I hope that helps.
John
LJS wrote:
Incidentally I probably wouldn't have had to use jaf if the damn NSU didn't hang halfway through the flashing process, damn you nokia and thank you jaf 😊 .
Hear Hear!
Boo Hiss NSU for ruining everything
my past 9 phones that i've updated that way have been fine.
Why'd it have the ruin the good one?
If you download the latest version of JAF and extract the inis from the zip to the jaf installation folder then N97 will appear in the "Use INI" list. As long as the firmware is on the correct location ( phoenix/products/RM-505 ) then you shouldn't need to select any files.
NSU worked just fine for me. I changed code with NSS and flashed with NSU srtaight away. No problems at all. I got my phone from Nokia shop in London.
Mike.mp wrote:NSU worked just fine for me. I changed code with NSS and flashed with NSU srtaight away. No problems at all. I got my phone from Nokia shop in London.
The problem seems to be going from a branded uk variant to a non one. As yours is a generic uk model it should be fine.
Yes, I've done everything that everyone has suggested.
MY problem is it gets to Pooling then fails....
As I said on page 3...
"My ressurection goes fine until it gets to the "Pooling Phone" bit. The screen goes all LCD liney, then stops.
Then, JAF says something along the lines of:
"Did your phone turn back on, Yes No?"
when I click "No" cos it didn't back come back on, it just says "Done!" and finishes.
Though its not actually done, as the phone doesnt turn back on or do anything.
So I try it all again, but then click...YES
But when I click "Yes" JAF thinks for a while then says...
"Phone not found...
Second try...
MCUSW: (null)
APESW: (null)
VariantSW: (null)
Prodcode:
Setting test mode...
Failed! Aborting!
Done!"
It doesn't turn on or anything.
And JAF has finished.
I've done the files manually. The .ini file option is there
ie: N97 is listed. It looks for the folders
both Phoenix\Products\RM-505 and the other Nokia folder
I downloaded everything from Navifirm
Basically, I've done everything correctly just the minute it gets to
"POOLING" it doesn't work. Trying again makes no difference.
But don't worry I threw it at the Nokia Care people and told them to fix it.
If they can't, then no I won't throw it in the river as someone pleaded me not to, I will just smash it repeatedly with a mallet for wasting $1000 on it.
MCUSW: (null)
APESW: (null)
VariantSW: (null)
Can't be sure as it was 1am when I did mine but im sure mine had some files listed for this. If I recall rightly when I selected "Use Ini" and choose the correct handset all the MCU lights etc came on green.
did you untick the CRT-308 box?
I'm glad that most of you guys have now resurrected your phones, I must say that I panicked a bit and contacted Voda straight away. My new one has now arrived.
Does anyone know if using the latest version of NSS (which I used sucessfully to debrand my old N95 and N95 8GBs), instead of JAF causes less problems?
I do want the updated firmware, but I think I'll hang about a bit. I don't really fancy breaking my new one just to resurrect it, if that makes sense?
I used JAF to debrand it because I thought that NSS, which I have used on my N95's and N96's, didn't work on the N97.
I was also planning on not doing the update right away, but it was soooo buggy I felt that I had no choice. Then again I was not planning on getting an N97 until they had been out for at least 4 months so that there would have been 1 or 2 updates already out, but I hated my N96 so much that in the end I couldn't stand it.
I am amazed that I could re-flash it when it was in that condition as I recently had the same problem with a N96 and the local Nokia service center told me that they couldn't do it either. Yesterday was definitely a good day!
grimmy58 wrote:I'm glad that most of you guys have now resurrected your phones, I must say that I panicked a bit and contacted Voda straight away. My new one has now arrived.Does anyone know if using the latest version of NSS (which I used sucessfully to debrand my old N95 and N95 8GBs), instead of JAF causes less problems?
I do want the updated firmware, but I think I'll hang about a bit. I don't really fancy breaking my new one just to resurrect it, if that makes sense?
Makes no diffeence the issue seems to be with the firmware downloaded by NSU.
Whether NSU only downloads parts of the firmware needed for the upgrade and not the full flash im not sure. Not even sure if this was intentional by Nokia.
jmcgrath - From my (limited) googling I understand that there is a new version NSS that works with S60 5th series. (please don't take my word for this, I don't want to be responsible for anyone's brick).
I just wondered if anyone had experience with the new version, but from what Unplugged says it is the fault of the NSU.
Is there any way to install it without using the NSU? possibly this Naviman software? Just a thought.
cheers,
Grim.
NSS worked fine for me.
I used it as it actually seemed to "read" my product code as opposed to JAF which just read blank text boxes.
The result is the same product code is changed and then NSU kills it ( after saying its been successfully updated )
Unplugged wrote:MCUSW: (null)
APESW: (null)
VariantSW: (null)Can't be sure as it was 1am when I did mine but im sure mine had some files listed for this. If I recall rightly when I selected "Use Ini" and choose the correct handset all the MCU lights etc came on green.
did you untick the CRT-308 box?
I did untick the CRT-308 box as anytime you do it with it on it pops up saying
something like "No No, can't 308 it"
And when I did it manually, yeah each button was green, even the Ape Variant, all with their individual files.
It would only stop at Pooling as after that it wouldn't do anything else.