PDA

View Full Version : [HOWTO] Comprehensive Firmware Flashing Guide for N9

Pages : [1] 2 3 4 5 6

itsnotabigtruck
2012-02-29, 22:46
MOD EDIT: Flasher tools site is currently down; official mirror is located here (http://skeiron.org/tablets-dev/maemo-dev-env-downloads/)

Navifirm has restricted access so get images from here (http://mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696)

Mirror (http://skeiron.org/firmware/N9/40.2012.21.3/) for PR1.3 images if above is not working

COMPREHENSIVE FIRMWARE FLASHING GUIDE
for the NOKIA N9

"Reflashing" your phone with the original Nokia firmware can solve many problems and is necessary in a number of circumstances, but a lack of documentation has resulted in a lot of misinformation and confusion. Hopefully, this guide will demystify the process and help bring ailing N9s back to life. :)

Warning: Improperly using flasher could damage your phone and void your warranty. However, following these directions precisely to use flasher to install "stock" Nokia firmware images is quite safe, and can fix problems that would otherwise require warranty service. In any case, flashing your phone is at your own risk. Do not use this guide if you aren't somewhat familiar with the command prompt/terminal on your operating system. While many users have experienced success with this process, it is not officially recommended by Nokia in any way. Read the entire guide before you start.

Warning: Installation of generic firmware images on certain carrier-branded phones seems to be blocked - if you're currently running a carrier-branded firmware image, it's recommended to wait for more details.

Warning: Do not modify the product code of your N9. Doing so is not necessary to replace your phone's firmware, and some programs for changing the code could cause problems (namely NSS Pro).

SELECTING A FIRMWARE IMAGE (N9 SPECIFIC)

Main firmware images for the Nokia N9 are divided up into "variants" by regions of the world. Except for carrier-branded variants and the 003 (China) firmware, these images are more or less the same.

001 - Europe (1), Latin/South America, South Africa
003 - China
005 - Asia/Pacific (incl. Australia/New Zealand, excl. China)
006 - Middle East
009 - Europe (2)
2xx, 3xx, 4xx - "Country Variant" and carrier-branded images

Downgrades of firmware are normally blocked by the phone. Whether something is a "downgrade" is determined by comparing the entire version strings of the old and new firmware versions, which include the variant code, from left to right. As a result, the variant code must be the same or higher unless you also upgrade the firmware version at the same time. For example:

PR 1.1 variant 009 to PR 1.1 variant 003: Blocked
PR 1.1 variant 003 to PR 1.1 variant 009: Allowed
PR 1.1 variant 009 to PR 1.2 variant 001: Allowed
PR 1.1.1 variant 006 to PR 1.2 variant 005: Allowed
PR 1.2 variant 001 to PR 1.1 variant 001: Blocked

Additionally, there is a content image ("eMMC image") for most countries/regions that can be used to reset the user data on the phone and restore the wallpaper/music/map files that originally shipped with it. It is possible to "mix and match" any content image with any main firmware image, which is useful for installing your home country's maps on an imported N9. If you don't require preinstalled maps, or if Nokia doesn't produce a content image for your country (e.g. US and Canada), you can save time by using the content image for product code 059J1Z5 ("rest of world"), which doesn't include map files.

When downloading firmware images, it doesn't matter which color or capacity (16/64 GB) you select - the files are the same for all models.

Nokia recommends always using the latest firmware image for your phone's product code (printed on the SIM card tray). This is the safest option. However, you may wish to change to a different variant than what shipped with the phone for the following reasons:

Receiving updates sooner - new firmware versions are normally released for the 001 variant first
Removing carrier branding - installing 00x variant firmware makes your subsidized N9 act just like an unlocked one
Switching away from 003 (China) firmware - firmware images for N9s shipped in China lack Western online service integration (Twitter, Facebook, Skype, Dropbox) and include the Chinese IM service QQ instead

Use the following steps to retrieve the appropriate firmware files for your phone:

On Windows:

Make sure Server is set to Nokia Care Suite.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release you wish to install.

10.2011.34.1 = PR1.0
20.2011.40.4 = PR1.1
22.2011.44.2 = PR1.1.1 (Middle East only)
30.2012.7.1 = PR1.2
40.2012.21.3 = PR1.3

Select the appropriate product code in the Variants list. In most cases, you should use the product code printed on the SIM tray.
Click Unmark All, then scroll to the bottom of the Files section. Tick the boxes for the two files starting with DFL61_HARMATTAN.

On Linux:

Install WINE using your Linux distro's packages.
Select Option > Server > Nokia Care Suit [sic] in the menu.
Find Nokia N9 (RM-696) in the Products list, then select the firmware release and variant you wish to install (see above).

Any OS:

Go to Nokia Firmwares (http://www.btusers.com.ar/nan/nokia/) (unofficial firmware download site) and search for Nokia N9. Click CHECK! toward the right-hand side.
Click the link for the firmware release you wish to install (see above).
Click the link for the file starting with DFL61_HARMATTAN.

Unlike NaviFirm+, this website cannot retrieve content/eMMC images.

All of the procedures described below will destroy some or all of the data on your phone, so you should be sure to back up anything you care about first. This includes contacts, messages, game saves, music, .deb packages, etc. You can do this either through the built-in backup feature or manually using developer mode.

PREPARE TO FLASH

If your phone has a low battery charge (less than 50%), plug it in and let it charge for a while. Then, make sure your phone is disconnected from any USB cables (including USB chargers). Power off the phone.

On Windows, open a Command Prompt with Administrator permissions (with UAC, right-click Command Prompt and select Run as administrator). On Linux, open a root shell (sudo -i/su). Change to the directory containing the firmware images you downloaded.

On Windows, run set PATH="C:\Program Files\Nokia\Flasher;%PATH%" in order to add Flasher to the system path.

FLASH THE PHONE

Run the following command, then connect the phone to your PC.

flasher -i

The current firmware version of your phone should appear. It is now time to flash.

Use the following list to determine which of the steps below you need to use to accomplish a particular task:

Upgrade operating system: Replace operating system
Recover from damaged OS install: Replace operating system
"Unbrick" phone: Replace operating system or Comprehensive reset
Reset back to a "clean slate": Comprehensive reset
De-brand phone: Comprehensive reset
Prepare for enabling open mode: Comprehensive reset
Disable open mode: Comprehensive reset
Prepare for selling, recycling, or destroying phone: Zeroize device
Clear data before returning phone for warranty service (if possible): Zeroize device
Reset device lock code: Zeroize device

Note that you should replace main.bin and emmc.bin in the commands with the actual names of the image files you are flashing.

Replace operating system (preserves user data)

The following command will replace your phone's operating system with the supplied firmware image. All applications will be removed, but music/documents/maps/etc. will be kept. This is equivalent to updating/restoring your phone using the Nokia Software Updater (NSU) utility.

flasher -f -F main.bin

Comprehensive reset (destroys user data)

The following commands will remove all data from your phone and restore it to factory state. The provided content files (sample music, wallpaper, etc.) will be restored.

flasher -f -F main.bin
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

Zeroize device (destroys user data)

The following commands will securely erase your phone such that no data can be recovered later, then restore the operating system and provided content.

Warning: The secure erase feature has not been audited by a 3rd party. Do not rely on it to protect all traces of highly sensitive information from a well-funded attacker. The first part will take a very long time - let it run overnight.

flasher -f -F main.bin --erase-user-data=secure
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

RECOVERING FROM FLASH ERRORS

Note: If you did not receive any errors, you can skip this section.

In some cases, the new firmware image includes cellular modem (CMT) firmware that is older than what is already installed. This has typically happened when flashing N9s running 003 (China) firmware with other firmware variants. If you received an error about flashing the CMT, obtain the image for the firmware that was previously installed, then run:

flasher -f -F old_main.bin --flash-only=cmt

If you previously upgraded your phone "over the air" (through SSU) and now receive a Downgrade disallowed error when flashing, try flashing an image with a higher variant code. For example, if you experienced the error with variant 001, try using variant 005 instead.

REBOOT INTO THE NEW OPERATING SYSTEM

The phone is now ready to leave flashing mode:

flasher -R

Use the power/lock button to boot your phone into the new system. Your N9 is now ready to use!

Fuzzillogic
2012-02-29, 23:24
You can combine clearing the device, flashing the main and emmc in one go:
flasher -f -F main.bin -F emmc.bin --erase-user-data

itsnotabigtruck
2012-02-29, 23:27
You can combine clearing the device, flashing the main and emmc in one go:
flasher -f -F main.bin -F emmc.bin --erase-user-data

You don't want the --erase-user-data normally - that's why it's only in the "zeroize" steps. You're right though - combining them works too.

youmeego
2012-03-01, 00:28
there is a complete guide to flash n9 on windows7 in youtube( it is in spanish).

DarkSkies
2012-03-01, 02:28
Well done, itsnotabigtruck. Many people will surely find this guide useful if not life saving!

gpollano
2012-03-01, 18:04
Thanks itsnotabigtruck ;)

When you say:
Warning: Installation of generic firmware images on certain carrier-branded phones seems to be blocked - if you're currently running a carrier-branded firmware image, it's recommended to wait for more details.

What's the meaning of "blocked"?

My N9 is branded (Nokia N9 of Argentina, "Personal" brand).
One of my goals is to get "Vanillla" Meego Experience. My branded N9 can not use WiFi-spot, has a horrible startup animation, and has some other limitations.

I'm planning to flash LTA firmware on it. Are you aware of any trouble?
Anyone has any experience on something similar?

Etchelon
2012-03-01, 18:37
there is a complete guide to flash n9 on windows7 in youtube( it is in spanish).

itsnotabigtruck
2012-03-01, 18:40
@gpollano I saw a post somewhere here from someone having trouble debranding an Australian N9, but can't seem to find it now. I added that warning to be cautious - I know a number of people have successfully debranded their phones going to PR1.1 at least.

Try doing the comprehensive reset and see if it works. If it doesn't, I expect it to simply refuse to install the image.

javid
2012-03-01, 20:26
@itsnotabigtruck thankyou for taking the time to write this up
In your opinion is this safer than using some other application based flashing utility?
Do you know if NSU will allow me to use pre-downloaded files?
Whats the difference between nokia care and prod external in navifirm? (do you use + or regular navifirm?)
The reason i ask - i miyself have a N8-00 and my wife has the better phone - N9-00:)
She's currently where the internet is painfully slow - or non-existent.
So - right now - she is at PR1.0 - and now that 1.2 has come out - i need to update her twice - which means i need to risk the flashing twice...
Also - where do the files to be flashed need to be located? same folder as flasher?
And since i have your attention - if for some reason the internet is working well when i start an OTA instead- and the internet disappears mid download - will it hurt the phone or will i just need to start again when the internet returns?

martycollinsesq
2012-03-01, 20:55
Bravo! Update to 1.2 from NSU went fine.

itsnotabigtruck
2012-03-01, 21:44
@itsnotabigtruck thankyou for taking the time to write this up
In your opinion is this safer than using some other application based flashing utility?
Do you know if NSU will allow me to use pre-downloaded files?
Whats the difference between nokia care and prod external in navifirm? (do you use + or regular navifirm?)
The reason i ask - i miyself have a N8-00 and my wife has the better phone - N9-00:)
She's currently where the internet is painfully slow - or non-existent.
So - right now - she is at PR1.0 - and now that 1.2 has come out - i need to update her twice - which means i need to risk the flashing twice...
Also - where do the files to be flashed need to be located? same folder as flasher?
And since i have your attention - if for some reason the internet is working well when i start an OTA instead- and the internet disappears mid download - will it hurt the phone or will i just need to start again when the internet returns?

Production External is what NSU uses to download firmware images; Nokia Care Suite is similar but has more files, including the eMMC content images.

You can indeed use NAVIFIRM to pre-download the firmware images - that's how I originally upgraded to PR1.1. Note that you need to download all the files listed under Production External for your phone's exact product code, then copy them into the right place. I don't remember off-hand exactly where the "right place" is, but it's some hidden directory somewhere.

The updater on the phone downloads everything before beginning the OS upgrade, so you don't need to worry about connection dropouts. However, it's a little buggy, and I had to reboot the phone in order to begin the download again after getting stuck.

Edit: Drop the files in C:\Users\<username>\AppData\Local\Nokia\NSU3\NOSSU2\variants\Products \rm-696

javid
2012-03-01, 22:13
Production External is what NSU uses to download firmware images; Nokia Care Suite is similar but has more files, including the eMMC content images.

You can indeed use NAVIFIRM to pre-download the firmware images - that's how I originally upgraded to PR1.1. Note that you need to download all the files listed under Production External for your phone's exact product code, then copy them into the right place. I don't remember off-hand exactly where the "right place" is, but it's some hidden directory somewhere.

The updater on the phone downloads everything before beginning the OS upgrade, so you don't need to worry about connection dropouts. However, it's a little buggy, and I had to reboot the phone in order to begin the download again after getting stuck.

Edit: Drop the files in C:\Users\<username>\AppData\Local\Nokia\NSU3\NOSSU2\variants\Products \rm-696

that is certainly obscure!
that is the location for Winflasher, correct?

munozferna
2012-03-01, 22:22

itsnotabigtruck
2012-03-01, 23:22
that is certainly obscure!
that is the location for Winflasher, correct?

Nope - it's for Nokia Software Updater (NSU). Flasher loads firmware images from wherever you tell it to. :)

ulex54
2012-03-02, 14:02
i changed my product code to get update 1.2 with nsu. At the end of installation it gave error about usb connection and nsu couldnt recover the phone as well. So i flashed same files with flasher with any probs. But it gave warning at start of phone about warranty.

i can go back my original 1.1 with error at the end of installation about

and phone starts but it gives a simcard problem and never recognizes it after some trying time.

Im at 1.2 again with warning at the start. What can i do?

P.s : i cant change my product code after first flash. How can i go local mode in this situation to change product code back or sth else.

if i go back 1.1 and connects it in suite mode. nss sees the product code but, because of cant get to local mode, it cant be changed.

waiting for help...

itsnotabigtruck
2012-03-02, 14:16
Which variant are you trying to upgrade from, and which are you trying to flash?

flasher -f -F pr12-main.bin --flash-only=nolo,kernel,rootfs
flasher -f -F pr11-main.bin --flash-only=cmt
flasher -f -F pr12-emmc.bin

(pr11-main.bin is the old firmware, pr12-main.bin is the new firmware)

youmeego
2012-03-02, 14:28
what is the purpose of changing n9 product code? especially when we can flash our n9 with other country variant firmware with the same or higher legacy number(number after PR)

ulex54
2012-03-02, 14:37
original variant is 059M4z8. i changed it to 059J214 (both are turkey code)

And flashed it to 059J214 1.2 image.

flasher -i command says its still 1.1

The flasher codes that you've given me, i will try them now.

ulex54
2012-03-02, 14:49
-first with success.

-second failed with these;

bb5 rdc cert read failed (11 times)
cmt rfs failed
pipe 2 finishing in error state with status 1

do i need to do third one?

ulex54
2012-03-02, 16:14
from your codes. i understand that the only problem was cmt. So i flashed back to 1.1 and got cmt from 1.2 . so it did the trick.

BrianFellOver
2012-03-03, 09:55
what is the purpose of changing n9 product code? especially when we can flash our n9 with other country variant firmware with the same or higher legacy number(number after PR)

The only reason that I can see is to force an OTA or NSU update when your firmware is an older version and new firmware exists for the other product code.

However, I agree that it is far easier to use Navifirm, download the firmware and use Flasher - no stuffing around with changing product codes.

youmeego
2012-03-03, 10:01

itsnotabigtruck
2012-03-03, 14:43
The only reason that I can see is to force an OTA or NSU update when your firmware is an older version and new firmware exists for the other product code.

However, I agree that it is far easier to use Navifirm, download the firmware and use Flasher - no stuffing around with changing product codes.

As far as I know, changing the product code doesn't even help with doing an SSU (OTA upgrade) - that's based entirely on which variant firmware is already installed on the phone at the time.

That means there's no reason to change the product code unless you really want to use Nokia Software Updater, and that seems to cause problems on its own. :/

kb61
2012-03-03, 17:41
im trying to flash my n9 but when i write flasher -i an error message appears telling me the following:

ERROR: ReadFile(65540) GetOverlappedResult() error 1167 timeout 4975ms
Unable to detect flashing interface: standing by for device reboot.
Found device RM-696, hardware revision 1603
NOLO-version 2.3.6

and then it tells me what my firmware version is, shall i then just go on or do i have to worry about anything??

Soppa
2012-03-03, 18:05
I think this should be a sticky.

jalyst
2012-03-03, 18:31
I think this should be a sticky.

Reported your post & in doing so asked the mods to sticky it.
(The more up-to-date Google Docs version)
This is probably the best flashing/updating guide I've seen yet.

Thank-you!

rdelfin
2012-03-03, 19:56
im trying to flash my n9 but when i write flasher -i an error message appears telling me the following:

ERROR: ReadFile(65540) GetOverlappedResult() error 1167 timeout 4975ms
Unable to detect flashing interface: standing by for device reboot.
Found device RM-696, hardware revision 1603
NOLO-version 2.3.6

and then it tells me what my firmware version is, shall i then just go on or do i have to worry about anything??

thx for your help :) I experienced the very same symptoms, and proceeded with flashing anyway, and everything went fine for me (proceed at your own risk).

nicodonte
2012-03-03, 20:31
Thanks itsnotabigtruck ;)

When you say:

What's the meaning of "blocked"?

My N9 is branded (Nokia N9 of Argentina, "Personal" brand).
One of my goals is to get "Vanillla" Meego Experience. My branded N9 can not use WiFi-spot, has a horrible startup animation, and has some other limitations.

I'm planning to flash LTA firmware on it. Are you aware of any trouble?
Anyone has any experience on something similar?

No problem to flash with a Claro branded N9 from Argentina, no blocked at all, firmware update without any problem.

kb61
2012-03-03, 20:42
I experienced the very same symptoms, and proceeded with flashing anyway, and everything went fine for me (proceed at your own risk).

thx worked

patocr
2012-03-03, 21:07
i seriously cannot make it work.
i have the .bin file... but cannot get the flasher to flash.
tried on windows with no luck, and mac... dunno what im doing wrong...
in mac im missing the SUDO command, don't know how to put it in...
plz, help?

i tried everything.....
1) phone off, disconnected
2) phone on, disconnected
3) phone off, connected
4) phone on, connected

tibere86
2012-03-03, 21:11
Thank you for great instructions itsnotabigtruck. I have successfully updated my Singapore N9 to N.European Generic PR1.2.

m.h.e.r
2012-03-03, 23:20
My N9 has PR 1.1.1 (22.2011.44-2.335.4_PR_335)
can i flash with any verson of PR 1.2 ?
if yes, which one is the best choice?

2012-03-03, 23:30
@itsnotabigtruck

Thanks so much for the guide. Worked well. Was able to flash and then do the OTA to 1.2.

patocr
2012-03-03, 23:42
GRRRRRR
can't flash it!!!! how do i make any os to recognize the device on flasher? im tired of trying, of turning on, and off, and on, and off... it won't get it.

guzz46
2012-03-03, 23:52
If you are using Linux you don't need to use NaviFirmEx in wine to download the Firmware, you can use this Perl Firmware downloader script in the following thread.

itsnotabigtruck
2012-03-04, 00:03
GRRRRRR
can't flash it!!!! how do i make any os to recognize the device on flasher? im tired of trying, of turning on, and off, and on, and off... it won't get it.

It's probably because you aren't running it as root. It looks like OS X does include sudo - did you try using it?

If you are using Linux you don't need to use NaviFirmEx in wine to download the Firmware, you can use this Perl Firmware downloader script in the following thread.

Yep - I didn't mention it in the post because it isn't able to download eMMC images like NaviFirmEx can. However, I'll bug admiral0 about adding that and include it.

Also, @mods: Thanks for stickying this!

patocr
2012-03-04, 01:55
It's probably because you aren't running it as root. It looks like OS X does include sudo - did you try using it?

Yep - I didn't mention it in the post because it isn't able to download eMMC images like NaviFirmEx can. However, I'll bug admiral0 about adding that and include it.

Also, @mods: Thanks for stickying this!

as i said before, dont know how to use it, missing the command 4 it.

patocr
2012-03-04, 02:39
i did..... sudo -i, then pass...... then flasher -f -F image.bin -R
connect phone being OFF, nothing
power on while connected.
i hear a "TICK" and a menu shows up saying "not enough power in usb to charge"... then... "enter usb charge mode"........
i really, really, really, really, dont get it.

i used to flash my 5230 several times, i cannot make this to read up my device, neither i use win or mac.

i am frustrated as ive been 4 hours trying. im done.

itsnotabigtruck
2012-03-04, 02:45
i did..... sudo -i, then pass...... then flasher -f -F image.bin -R
connect phone being OFF, nothing
power on while connected.
i hear a "TICK" and a menu shows up saying "not enough power in usb to charge"... then... "enter usb charge mode"........
i really, really, really, really, dont get it.

i used to flash my 5230 several times, i cannot make this to read up my device, neither i use win or mac.

i am frustrated as ive been 4 hours trying. im done.

Don't give up! You're almost there, you just need to charge up your N9 further before it will let you flash. Make sure to use the charger that came with the N9 to ensure that it gets enough power (not every wall charger or USB port will do).

Once it's charged past 50% or so, power it back off and get ready to flash.

My N9 has PR 1.1.1 (22.2011.44-2.335.4_PR_335)
can i flash with any verson of PR 1.2 ?
if yes, which one is the best choice?

You usually can't go wrong with 001 - but if you want to stick with the firmware intended for the Middle East use 006 instead.

patocr
2012-03-04, 02:50
Don't give up! You're almost there, you just need to charge up your N9 further before it will let you flash. Make sure to use the charger that came with the N9 to ensure that it gets enough power (not every wall charger or USB port will do).

Once it's charged past 50% or so, power it back off and get ready to flash.

its charged 80%...... it's been like that all the afternoon. i even let it charge like 3 hours, its 100% now.

the same happens.......

GKFNR"!?$I!=RKOPFAOPFAO;FPSAKFOPA#######!!!!!!!!!!!! itsnotabigtruck 2012-03-04, 03:01 its charged 80%...... it's been like that all the afternoon. i even let it charge like 3 hours, its 100% now. the same happens....... GKFNR"!?$I!=RKOPFAOPFAO;FPSAKFOPA#######!!!!!!!!!!!!

Try putting the phone into Sync and Connect mode, then do flasher -i. Once that successfully connects to the phone, then do the actual flash. It doesn't look like you were following the guide (though in theory it should work either way).

patocr
2012-03-04, 03:12
same.... dont recog phone

tibere86
2012-03-04, 06:03
same.... dont recog phone

Keep trying. It took me about 8 disconnect/reconnect USB attempts for the flasher to finally recognize my N9.

rdelfin
2012-03-04, 06:48
Patocr, are you usign the USB original cable that came with the phone?
Be aware that not all USB cables are created equal and if you're using a generic cable or one from another device, that could explain why your phone is not being recognized.

patocr
2012-03-04, 09:02
im using the original cable.... i also tried with my other nokia cable, the one i used to flash several phones.

Anyway, the only time a pc recognized it, was a month b4 when i tried to reflash the pone to my actual version, and it couldn't because ota timestamp was newer than navifirm's one.

Still.... all day trying, no luck.
fk m

edit: not good.
now my phone wont charge up to 100%.
everytime i connect the phone in the usb i get the msg that usb has not enough power to charge the phone.
i can't even get close to a flashing point.
im exhausted.
im done, im selling.

javid
2012-03-04, 14:12
@patocr just from a different standpoint -
have you tried an alternate USB port? (im sure you have but in case you havnt - and i see you keep mentioning that your pc says it cant charge...)
Some usb ports just cant supply enough initial current - inrush - so might not work - especially on laptops and those for desktops that arent connected directly to the motherboard - in my experience.
Does Nokia Link or NSU see your phone on the same usb ports?
Also for charging alone - try charging directly from a wall charger - see if that helps.

patocr
2012-03-04, 15:14
i tried it. all.
i have a imac. so ports are ports, i have 4, tried it all.
i have another desktop pc, the same. i have a notebook, the same.

its like a bug, everytime i connect to a pc now i get that msg. and after, states that i can charge. with wall charger, its okay.

Nsu see's it, but keeps saying my phone is connected through usb, were it isnt.
i want to trow it to the trash.

i cannot use fb or twiter nor im getting the update, nor i cant reflash to correct bugs. i feel like i have the most expensive phone and cant use it.

SUCKS BIG.

thenutflush
2012-03-05, 04:31
Have been trying to get Fenix mail and some Settings to launch since PR1.2 update. Tried NSU and Flasher to no avail.

Does Flasher actually write over all system files? (i.e. format the phone then re-install the firmware) Cuz it's not really working the way I envision it would.

patocr
2012-03-05, 23:27
HOLY **** CRAP!
i made it work...... i managed to get a windows pc with XP, and using an old cable, i got it working.

now flashing (from argentinian personal n9 pr1.1 to hispanic 1.2)
hope it works good.

will edit when it ends.

EDIT: GREAT THX

javid
2012-03-06, 02:09
@patocr - good to see you wont be selling now!
hows that pr1.2??

martycollinsesq
2012-03-06, 02:39
Bravo! Update to 1.2 from NSU went fine.

Another Bravo for the guide. Gotta back that arse up now cause I had quicktweak on my N9 when I did the update to 1.2:confused:; now I need to flash to factory state:eek:. Into the deep I go, relatively unafraid, thanks to community support;).

_Routser
2012-03-07, 02:43
I Hope someone can help here.

Today my phone went sluggish and I rebooted it, but it got stuck into a reboot loop, tried to revive it with Nokia link with no results.

Now I managed to flash it with my Mac following the instructions in this thread, flashing went fine but the phone is still in the loop, it goes barely to the point where i should enter pin before rebooting...

Any suggestions? Or is it to Nokia Care with me :(

itsnotabigtruck
2012-03-07, 02:46
I Hope someone can help here.

Today my phone went sluggish and I rebooted it, but it got stuck into a reboot loop, tried to revive it with Nokia link with no results.

Now I managed to flash it with my Mac following the instructions in this thread, flashing went fine but the phone is still in the loop, it goes barely to the point where i should enter pin before rebooting...

Any suggestions? Or is it to Nokia Care with me :(

What if you try zeroizing it? (remember, this = all data destroyed)

_Routser
2012-03-07, 03:11
What if you try zeroizing it? (remember, this = all data destroyed)

Trying it now, as I am on Mac, did I understand correctly that I can't get the emmc? But the first command line should probably do the trick (if anything does), so i just leave this out?

flasher -f -F main.bin -F emmc.bin --flash-only=mmc

Now to the tedious process of getting it back the way it was..

lavo
2012-03-07, 03:48
Does anyone have an alternative site for the Mac flasher program? Its seems to be borked from the official download site on the first page.

ronmakaay
2012-03-07, 07:51
Hi there,
this is so far the best guide i have found, but I need some little help before I flash my phone
insdie the log files of the firmware my phone version that I get from NaviFirm+:
059L698: N9 RM-696 Country Variant Australia AU Black 16GB V1
Log Files:
simlock_maemo__deB_allowed2_3gstandard_bb5_multi_a sic0.bin
simlock_maemo__deB_allowed2_3gstandard_bb5_multi_a sic1.bin
But I found this 2 .bin files, and I don't know if this will lock the SIM of my phone and then I will be in troubles well I guess.
So if any can tell me something about it, this .bin files can be exclude from the flash installation or they must also be also included in the installation??
Can any buddy help me, I’m so noob
:p

itsnotabigtruck
2012-03-07, 18:13
Hi there,
this is so far the best guide i have found, but I need some little help before I flash my phone
insdie the log files of the firmware my phone version that I get from NaviFirm+:
059L698: N9 RM-696 Country Variant Australia AU Black 16GB V1
Log Files:
simlock_maemo__deB_allowed2_3gstandard_bb5_multi_a sic0.bin
simlock_maemo__deB_allowed2_3gstandard_bb5_multi_a sic1.bin
But I found this 2 .bin files, and I don't know if this will lock the SIM of my phone and then I will be in troubles well I guess.
So if any can tell me something about it, this .bin files can be exclude from the flash installation or they must also be also included in the installation??
Can any buddy help me, I’m so noob
:p

They won't lock your phone, but they also aren't needed for flashing. flasher only cares about the two huge .bin files starting with DFL61.

charlysoft
2012-03-07, 23:32
No problem to flash with a Claro branded N9 from Argentina, no blocked at all, firmware update without any problem.

Sorry my english.

would have trouble doing it to LTA or Global version ?

tnks

tiiagoFernandez
2012-03-08, 00:49
Hey.. I have a
N9 RM-696 Country Variant Sweden SE Black 16Gweden SE Black 16GB
Can i flash it to
RM-696 NDT CENTRAL EUROPE BLACK 16G
?

Im running PR 1.2
The legacys are 339 to 001 respectivly...
Thanks for the help

itsnotabigtruck
2012-03-08, 04:31
Sorry my english.

would have trouble doing it to LTA or Global version ?

tnks

The LTA version actually is the global version, so go ahead.

Hey.. I have a
N9 RM-696 Country Variant Sweden SE Black 16Gweden SE Black 16GB
Can i flash it to
RM-696 NDT CENTRAL EUROPE BLACK 16G
?

Im running PR 1.2
The legacys are 339 to 001 respectivly...
Thanks for the help

The firmware for that variant was actually released this week, but if you want to flash it to 001, that should work too. :)

tiiagoFernandez
2012-03-08, 12:08
How can i do it if imm running pr 1.2 legacy 339 and want to flash to legacy Global 001

tiiagoFernandez
2012-03-08, 12:37
Im gonna wait till PR 1.3 comes out, then change my variant :)

Gonna reflash with original for now.
Thanks

gabrielharrison
2012-03-08, 13:03
Which variant are you trying to upgrade from, and which are you trying to flash?

flasher -f -F pr12-main.bin --flash-only=nolo,kernel,rootfs
flasher -f -F pr11-main.bin --flash-only=cmt
flasher -f -F pr12-emmc.bin

(pr11-main.bin is the old firmware, pr12-main.bin is the new firmware)

If I do this on my phone the flashing works with no errors but bricks the phone any idea why?

Gabriel

tiiagoFernandez
2012-03-08, 14:06
Im gonna wait till PR 1.3 comes out, then change my variant :)

Gonna reflash with original for now.
Thanks

Sucess on reflashing with the same system and variant and rest of the world emmc.
When another firmware update comes out im gonna flash it to Global.

ssjmec
2012-03-09, 15:10
Does anyone know, I tried the zeroize device. Though my phone works, at boot it still displays the warning that I have modified the device software making the warranty void etc. how do I fix this? I cant use security code with this sh*t

EDIT: Before I zeroize, this is already present. I just thought it can fix it but it didnt.

gabrielharrison
2012-03-09, 15:48
Does anyone know, I tried the zeroize device. Though my phone works, at boot it still displays the warning that I have modified the device software making the warranty void etc. how do I fix this? I cant use security code with this sh*t

What firmware variant and versions were you using and what is the product number of your phone?

Were any errors reported by the flasher?

ssjmec
2012-03-09, 16:16
What firmware variant and versions were you using and what is the product number of your phone?

Were any errors reported by the flasher?

PR1.2 for product code 059J232. Actually I have a long story.

When I was still on PR1.1, I did a device clear (Settings>reset>clear device) then I reflashed with PR1.1. I am able to flash the device safely with the same file before, but that time it failed, I think it became corrupted, but dont know how?:confused: Anyway, after the failed flash, my phone still boots but with errors (no signal, cant display the about product) So I just downloaded the PR1.2 for my variant. then flashed the phone. This is the first time the warning showed, and the phone auto shuts off. So I tried to reflash the PR1.1 of my variant, (the same, corrupted file. but I wasn't aware yet that it is corrupted) again, it failed to flash. but when I start my phone, it still boots but I know theres wrong (again, the mobile network and about product) I tried to use the flash only cmt of pr1.2 on my pr1.1 and it fixed the mobile network and about product issue. so my phone functions well on PR1.1. I tried to update to pr1.2 OTA. It was successful, I can see on my about product that I am running pr1.2. everything is okay but one thing, every time I boot my device, the same warning shows(warning, you have modified device software etc etc) for about 10 secs, before it actually boot. That is the time I tried to zeroize device. I downloaded pr1.2 for my variant on navifirm but still, same problem.

gabrielharrison
2012-03-09, 16:27
PR1.2 for product code 059J232. Actually I have a long story.

When I was still on PR1.1, I did a device clear (Settings>reset>clear device) then I reflashed with PR1.1. I am able to flash the device safely with the same file before, but that time it failed, I think it became corrupted, but dont know how?:confused: Anyway, after the failed flash, my phone still boots but with errors (no signal, cant display the about product) So I just downloaded the PR1.2 for my variant. then flashed the phone. This is the first time the warning showed, and the phone auto shuts off. So I tried to reflash the PR1.1 of my variant, (the same, corrupted file. but I wasn't aware yet that it is corrupted) again, it failed to flash. but when I start my phone, it still boots but I know theres wrong (again, the mobile network and about product) I tried to use the flash only cmt of pr1.2 on my pr1.1 and it fixed the mobile network and about product issue. so my phone functions well on PR1.1. I tried to update to pr1.2 OTA. It was successful, I can see on my about product that I am running pr1.2. everything is okay but one thing, every time I boot my device, the same warning shows(warning, you have modified device software etc etc) for about 10 secs, before it actually boot. That is the time I tried to zeroize device. I downloaded pr1.2 for my variant on navifirm but still, same problem.

Looks like you have the same problem as me. See this thread http://talk.maemo.org/showthread.php?t=82877

lancewex
2012-03-09, 23:35
The instructions twice say to click the boxes for the TWO files stariting with DFL61_HARMATTAN. For all of them I only see one file starting with that. Using NaviFirmEx. What am I doing wrong?

itsnotabigtruck
2012-03-10, 00:04
Looks like you have the same problem as me. See this thread http://talk.maemo.org/showthread.php?t=82877

This is an incredibly strange problem.

Are you sure the flash was 100% successful with PR1.2? It sounds like parts of the system simply aren't being flashed, period.

If you don't mind screwing up your phone again, what happens if you flash with the -v option (upload all the output)?

The instructions twice say to click the boxes for the TWO files stariting with DFL61_HARMATTAN. For all of them I only see one file starting with that. Using NaviFirmEx. What am I doing wrong?

You didn't select "Nokia Care Suit" in the menu (re-check the directions).

thenutflush
2012-03-10, 06:53
Have been trying to get Fenix mail and some Settings to launch since PR1.2 update. Tried NSU and Flasher to no avail.

Does Flasher actually write over all system files? (i.e. format the phone then re-install the firmware) Cuz it's not really working the way I envision it would.

gabrielharrison
2012-03-10, 08:03
This is an incredibly strange problem.

Are you sure the flash was 100% successful with PR1.2? It sounds like parts of the system simply aren't being flashed, period.

If you don't mind screwing up your phone again, what happens if you flash with the -v option (upload all the output)?

Here is the verbose output. I had to clip it a bit because it was too big for the forum. Let me know if you want the full output and I'll put it on my site.

I looks like I may have screwed things when I tried to change my Product Code from Malaysia to Northern Europe when I first got the phone. None of the certs match my product revision "RM-696 rev. 059K". From a bit of googling the 059K should be a number more like 1601.

Any advice on how to find the correct revision and how to change it?

----------------------

C:\program files\Nokia\Flasher>rem Zeroize with North Europe PR1.2

C:\program files\Nokia\Flasher>flasher.exe -v -f -F fw\059K0X6\DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_001-OEM1-958_ARM.bin -F fw\059K0X6\DFL61_HARMATTAN_30.2012.07-1.NORTHERNEUROPE_EMMC_NORTHERNEUROPE.bin
flasher 3.12.1 (Oct 6 2011) Harmattan
[ 0.000000] WARNING: This tool is intended for professional use only. Using it may result in permanently damaging your device or losing the warranty.

SW version in image: <none>
Image 'mmc', size 1627169 kB
Version DFL61_HARMATTAN_30.2012.07-1.NORTHERNEUROPE
SW version in image: DFL61_HARMATTAN_30.2012.07-1_PR_001
Image 'cert-sw', size 1408 bytes
Valid for RM-696: 0101, 0102, 0103, 0104, 0105, 0106
Version (null)
Image 'cert-sw', size 1408 bytes
Valid for RM-696: 0207, 0208
Version (null)
Image 'cert-sw', size 1408 bytes
Valid for RM-696: 0301, 0302, 0303, 0304, 0305, 0306
Version (null)
Image 'cert-sw', size 1408 bytes
Valid for RM-696: 0401, 0402, 0403, 0404, 0405, 0406
Version (null)

[CLIPPED]

Image 'cert-sw', size 1408 bytes
Valid for RM-696: 1507, 1508, 1509, 1510, 1601, 1602, 1603, 1604, 1605, 1701, 1702, 1703, 1704, 1705, 1801, 1802, 1803, 1804, 1805
Version (null)
Image 'cert-sw', size 1408 bytes
Valid for RM-696: 1901, 1902, 1903, 1904, 1905, 2001, 2002, 2003, 2004, 2005, 2101, 2102, 2103, 2104, 2105, 2201, 2202, 2203, 2204, 2205
Version (null)
Image 'kernel', size 2714 kB
Version 2.6.32-20115101+0m7
Image 'rootfs', size 1163796 kB
Version DFL61_HARMATTAN_30.2012.07-1_PR_001
Image 'cmt-2nd', size 97280 bytes
Valid for RM-660
Valid for RM-680
Version (null)
Image 'cmt-2nd', size 97280 bytes
Valid for RM-690
Version (null)
Image 'cmt-2nd', size 97280 bytes
Valid for RM-696
Version (null)
Image 'cmt-2nd', size 97280 bytes
Valid for RM-716
Version (null)
Image 'cmt-2nd', size 97280 bytes
Valid for RX-71
Version (null)
Image 'cmt-algo', size 808192 bytes
Valid for RM-660
Valid for RM-680
Version (null)

[CLIPPED]

Image 'secondary', size 96768 bytes
Valid for RM-696: 1503, 1504, 1505, 1506
Version 2.3.6+0m7
Image 'secondary', size 96768 bytes
Valid for RM-696: 1507, 1508, 1509, 1510, 1601, 1602, 1603, 1604, 1605, 1701, 1702, 1703, 1704, 1705, 1801, 1802, 1803, 1804, 1805
Version 2.3.6+0m7
Image 'secondary', size 96768 bytes
Valid for RM-696: 1901, 1902, 1903, 1904, 1905, 2001, 2002, 2003, 2004, 2005, 2101, 2102, 2103, 2104, 2105, 2201, 2202, 2203, 2204, 2205
Version 2.3.6+0m7
Image '1st', size 26496 bytes
Valid for RM-680: 916
Version 2.3.6+0m7
Image '1st', size 26368 bytes
Valid for RM-680: 922
Version 2.3.6+0m7
Image '1st', size 13312 bytes
Valid for RX-71: 000
Version 2.3.6+0m7
Image '1st', size 26368 bytes
Valid for RX-71: 166
Version 2.3.6+0m7
Image 'ape-algo', size 7096 kB
Version (null)
[ 0.890625] Ping attempt 1 (250 ms)
[ 0.906250] Server application: 1.7.2
[ 0.921875] Found product RM-696 rev. 059K
[ 0.921875] Server implements softupd protocol version 1.8
[ 0.921875] Image SW version DFL61_HARMATTAN_30.2012.07-1_PR_001
[ 0.921875] Image cert-sw not present for this HW (RM-696 rev. 059K)
[ 0.921875] Image xloader not present for this HW (RM-696 rev. 059K)
[ 0.921875] Image secondary not present for this HW (RM-696 rev. 059K)
[ 0.937500] Image moslo not present
[ 0.937500] This rootfs is for eMMC
[ 0.937500] Image tar skipped
[ 0.937500] Image config skipped
[ 0.937500]
Battery level 40 %, continuing.
[572.562500]
image [state progress transfer flash speed]
[572.562500] ---------------------------------------------------------------------
[572.562500] [x] cmt-2nd [finished 100 % 95 / 95 kB[572.562500] NA ]
[572.562500] [x] cmt-algo [finished 100 % 789 / 789 kB[572.562500] NA ]
[572.562500] [x] cmt-mcusw [finished 100 % 6050 / 6050 kB[572.562500] 3024 kB/s]
[572.562500] [x] kernel [finished 100 % 2714 / 2714 kB[572.562500] 1182 kB/s]
[572.562500] [x] rootfs [finished 100 % 1163796 / 1163796 kB[572.562500] 4573 kB/s]
[572.562500] [x] mmc [finished 100 % 1627169 / 1627169 kB[572.562500] 5502 kB/s]
[572.562500] Updating SW release
[572.687500] Success

Z3tor
2012-03-10, 10:35
Thanks for making this great guide !

lastmilefire
2012-03-10, 19:02
HELP !!!

I flashed my phone from malaysian version to european version, and I got the apparently common CMT error ???

I see the apparently easy solution of reinstalling the native firmware app. However Where do I find the native firmware at ???

itsnotabigtruck
2012-03-11, 07:26
Here is the verbose output. I had to clip it a bit because it was too big for the forum. Let me know if you want the full output and I'll put it on my site.

I looks like I may have screwed things when I tried to change my Product Code from Malaysia to Northern Europe when I first got the phone. None of the certs match my product revision "RM-696 rev. 059K". From a bit of googling the 059K should be a number more like 1601.

Any advice on how to find the correct revision and how to change it?

----------------------

<snip>
[ 0.921875] Image cert-sw not present for this HW (RM-696 rev. 059K)
[ 0.921875] Image xloader not present for this HW (RM-696 rev. 059K)
[ 0.921875] Image secondary not present for this HW (RM-696 rev. 059K)
<snip>

That explains everything - your guess is right on the dot.

If you can figure out what your hardware variant code is, use whatever you tried to change your product code with to set it to xxxx00 (where xxxx is the HW variant). If you flash back to PR1.1 you might be able to figure out which HW variant your phone is using sysinfoclient -a.

This is why changing the product code is ill-advised - remember, there's no need to do so before flashing!

justie
2012-03-11, 12:03
Im gonna try to reflash my device. In the directions it states that i shld change the main.bin & eMMC.bin to the image names im supposed to flash to. does this mean i shld change the main.bin image name to smth like
DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_005-OEM1-958_ARM.bin
? Thanks for all the help guys :)

gabrielharrison
2012-03-11, 12:53
HELP !!!

I flashed my phone from malaysian version to european version, and I got the apparently common CMT error ???

I see the apparently easy solution of reinstalling the native firmware app. However Where do I find the native firmware at ???

What is your phone product code and what version of the EU firmware did you use?

gabrielharrison
2012-03-11, 12:59
That explains everything - your guess is right on the dot.

If you can figure out what your hardware variant code is, use whatever you tried to change your product code with to set it to xxxx00 (where xxxx is the HW variant). If you flash back to PR1.1 you might be able to figure out which HW variant your phone is using sysinfoclient -a.

This is why changing the product code is ill-advised - remember, there's no need to do so before flashing!

Thanks, totally agree about changing the product code. The only advantage it has is enabling OTA and NSU for future updates to the new product code.

sysinfoclient -a isn't revealing anything. May have to ask a friend at Nokia for a favour but am going to look at some of the certs on the phone first.

justie
2012-03-11, 14:04

For the english users :) just found it as a recommended link from spanish video

ssjmec
2012-03-11, 14:41
I looks like I may have screwed things when I tried to change my Product Code from Malaysia to Northern Europe when I first got the phone.

I do think this is the reason. because I did change my product code to northern europe, too, before having this issue. Using NSS. because I thought I need to change the product code before installing other variant

lastmilefire
2012-03-11, 14:58
What is your phone product code and what version of the EU firmware did you use?

My phone is the black 64gb malaysian phone- 059j238 and I tried to flash it with 30.2012.7.1

I had just received the 1.2 update on it last week too. Only reason I was trying to do the flash was because I was trying to get facebook and twitter on my notifications screen :(

You can email directly at lastmilefire@gmail.com if you would like.
thanks again

lastmilefire
2012-03-11, 19:40
okay screw this... how the hell do i just get my phone back to the same Fn crap it was before ? I have been trying to do this for 3 days now and I cant get anywhere. please please someone help me

gabrielharrison
2012-03-12, 15:17
My phone is the black 64gb malaysian phone- 059j238 and I tried to flash it with 30.2012.7.1

I had just received the 1.2 update on it last week too. Only reason I was trying to do the flash was because I was trying to get facebook and twitter on my notifications screen :(

You can email directly at lastmilefire@gmail.com if you would like.
thanks again

What error are you getting?

gaggar
2012-03-13, 22:51
N9: Diffrence between flashing with firmware vs restore factory settings?

Hey guys!! Please - I need some help.

What is the difference in the effect of
restoring factory settings vs flashing the device with firmware?

My n9 (already updatet to pr1.2 OTA) is running kinda slow and having a few bugs,
that aparently isnt "normal" bugs.
(for instance I cant:
get my google acount for gtalk to work in acounts)

Furthermore I can read in several forums that it's better
to update your device via flash/firmware
instead of OTA or NSU... how can that be?

But I hope that "clearing" the device will help
radically with the speed issue +hopefully repair some of the bugs..

Hope you can help me.

I miss my good old smooth working and fast N9 !!

BTW...Great instructions!!! Maybe I should try this flashing thing.. not THAT big of a computer-geek thoug :-)

gpollano
2012-03-13, 23:31
Thanks for the instructions again itsnotabigtruck!

I was able to flash my branded N9 (Personal Argentina) with neutral (LTA) firmware. The process was very striaghtforward and simple.

Now I have WiFi Spot, Skype, and "vanilla start up screen" among others things.

Just for the record, I download de main.bin form Production External and the emmc.bin from Nokia Care Suit. It just works ok.

Cheers and happy flashing.

fedespi
2012-03-14, 01:09
Thanks for the instructions again itsnotabigtruck!

I was able to flash my branded N9 (Personal Argentina) with neutral (LTA) firmware. The process was very striaghtforward and simple.

Now I have WiFi Spot, Skype, and "vanilla start up screen" among others things.

Just for the record, I download de main.bin form Production External and the emmc.bin from Nokia Care Suit. It just works ok.

Cheers and happy flashing.

Hi, just a question, why did you choose to download the main.bin file from Production External and emmc.bin from Nokia Care Suit?

itsnotabigtruck
2012-03-14, 01:17
Hi, just a question, why did you choose to download the main.bin file from Production External and emmc.bin from Nokia Care Suit?

It shouldn't matter, in any case - the files are the same between the two, the difference is how many files are available.

tiiagoFernandez
2012-03-14, 11:45
I noticed that i have 5 ou 6 RSS feeds, but only 2 appear on the events view.. although all of them are selected :/
And im getting N9 freezes/crashes in messaging app

Im thinking that the reflash didnt work that well x.x

Prestige
2012-03-14, 18:49
Hi guys..Just bought my N9..
I want to flash p.r 1.2 but i dont know what firmware should i choose as in Navifirm i cant find my product code..
My N9 is from Switzerland..
Should i choose a neutral as mentioned above..?

tiiagoFernandez
2012-03-15, 19:46
It shouldn't matter, in any case - the files are the same between the two, the difference is how many files are available.

Hey..
I have a question, with area code "339 country variant" wich system can i reflash it with?
Already tried 001 and 005 with no sucess.
Running PR 1.2

automagic68
2012-03-17, 07:29
I'm trying to flash on Windows 7, I installed the flasher and I set the path. When I ran flasher -i command I get the error "'flasher' is not recognized as an internal or external command, operable program or batch file." Did anyone else run into this problem?

gabrielharrison
2012-03-17, 07:59
Hi guys..Just bought my N9..
I want to flash p.r 1.2 but i dont know what firmware should i choose as in Navifirm i cant find my product code..
My N9 is from Switzerland..
Should i choose a neutral as mentioned above..?

Out of interest, why do you want to flash it? Is PR1.2 not available to you using Over The Air or Nokia Updater?

What is you product code and currect software version?

user/zero
2012-03-17, 08:09
When I ran flasher -i command I get the error "'flasher' is not recognized as an internal or external command, operable program or batch file."

You must first run cmd.exe with administrative privileges. Just type cmd.exe at the Start menu, right-click and select Run as Administrator (or whatever it's called). Then
cd C:\Program Files\Nokia\Flasher (the path to your installation folder, could be different)
flasher.exe <options>

Prestige
2012-03-17, 14:55
Out of interest, why do you want to flash it? Is PR1.2 not available to you using Over The Air or Nokia Updater?

What is you product code and currect software version?

I bought my n9 5 days ago and instantly upgraded to p.r 1.1 OTA..
However p.r 1.2 is not available yet..
My product code is 059L5H1 and i'm in greece..

itsnotabigtruck
2012-03-17, 16:17
I bought my n9 5 days ago and instantly upgraded to p.r 1.1 OTA..
However p.r 1.2 is not available yet..
My product code is 059L5H1 and i'm in greece..

If you're not sure, just pick 059J1Z5, which is a totally generic region 001 image and eMMC.

I'm trying to flash on Windows 7, I installed the flasher and I set the path. When I ran flasher -i command I get the error "'flasher' is not recognized as an internal or external command, operable program or batch file." Did anyone else run into this problem?

Did you install flasher to somewhere other than the default location? You might have to correct the path. Also, make sure you're getting the set command exactly. :)

HEROEdelREVES
2012-03-17, 17:46
Can anyone tell if WinFlasher_3.12.1.exe it's compatible with x64? i have Windows 7 Home Premium 64 bits. But WinFlasher 3.12 says in the Description " installation package for Windows 7, XP and Vista (x86, 32-bit)".
I wanna flash my black N9 to get PR 1.2
Thanks.

2012-03-17, 18:02
yes its compatible

Prestige
2012-03-17, 18:50
[QUOTE=itsnotabigtruck;1180720]If you're not sure, just pick 059J1Z5, which is a totally generic region 001 image and eMMC.

Ok so i download the NDT 16GB BLACK 059J1Z5 image(only the last 2 files) and i proceed..
When i turn off my phone it says drivers of the device can not be found..
What do i do now?I am running windows 7 64 bit..

HEROEdelREVES
2012-03-18, 18:29
I've updated my phone thanks this thread many thanks all of you. I mean ALL of you because i've read a lot of the pages and i could update my N9 safety.
So, thank you.

cuteshark
2012-03-21, 20:05
why i can not flash from pr1.2 PR_339.03.1 Sweden to PR

cuteshark
2012-03-21, 21:08
i have N9 pr1.2 with sweden firmware PR_339.03.1 but when i try to flash with Vietnam firmware PR_454.1 and same version (not downgrade). it wont let me to. i dont know why, i though PR_454.1 is higher than PR_339.03.1...please help me with that

rainisto
2012-03-22, 10:32
i have N9 pr1.2 with sweden firmware PR_339.03.1 but when i try to flash with Vietnam firmware PR_454.1 and same version (not downgrade). it wont let me to. i dont know why, i though PR_454.1 is higher than PR_339.03.1...please help me with that

Its a downgrade because of timestamps, explained in here http://forum.meego.com/showpost.php?p=39647&postcount=201

So if you really want vietman firmware, you need to wait for possible next pr vanilla release and only flash on top of that one. You will always fail from sweden to vietnam in PR1.2.

herr_oigg
2012-03-22, 12:39
I've got to ask this question.
My N9 is locked to operator let's call it "A". As far as I know it's not branded, but to be honest, I don't have access to miscrosim from operator "A" to check it (no signs of operator "A" when powered without any SIM).
I bought unlock code, but I'm unable to enter it (http://talk.maemo.org/showthread.php?t=83172).
I want to use it with SIM from operator "B". I've checked, phone powers off immediately with SIM "B" inserted.
Will any type of flashing ("comprehensive reset" or "zeroize device") remove lock to operator "A". I'm asking this because image bin files are accompanied by strange files called "simlock*.bin".

And also this guide is amazing. All crucial info about flashing in one elegant place :)

cuteshark
2012-03-22, 13:32
Its a downgrade because of timestamps, explained in here http://forum.meego.com/showpost.php?p=39647&postcount=201

So if you really want vietman firmware, you need to wait for possible next pr vanilla release and only flash on top of that one. You will always fail from sweden to vietnam in PR1.2.

Thank you so much for you answer. Now i think i understand :-) and again, can you more detail about "the next pr vanila" ...you meant tne pr 1.3? Or i still can flash with another variant of pr 1.2 released after sweden (for example Australia variant?)

Nosph3ratu
2012-03-23, 08:13
Comprehensive reset (destroys user data)

The following commands will remove all data from your phone and restore it to factory state. The provided content files (sample music, wallpaper, etc.) will be restored.

flasher -f -F main.bin
flasher -f -F main.bin -F emmc.bin --flash-only=mmc

@itsnotabigtruck: Thanks for the detailed guide.

I'm intending to do a comprehensive reset as my twitter notifications aren't working. I've read that a "clear device" resolves the issue but since I'm going back to factory I might as well do it properly since I'm also experiencing some lag. I previously updated to PR1.2 through NSU (Does this do the same thing?)

In your commands above what is the purpose of the first line? From my understanding the second line accomplishes the comprehensive reset and the first line is just flashing the rootFS. If I am flashing the rootFS and the emmc in the second line the first line seems a bit pointless. Unless I am missing something and there is a benefit?

herr_oigg
2012-03-23, 14:04
@itsnotabigtruck: Thanks for the detailed guide.

I'm intending to do a comprehensive reset as my twitter notifications aren't working. I've read that a "clear device" resolves the issue but since I'm going back to factory I might as well do it properly since I'm also experiencing some lag. I previously updated to PR1.2 through NSU (Does this do the same thing?)

In your commands above what is the purpose of the first line? From my understanding the second line accomplishes the comprehensive reset and the first line is just flashing the rootFS. If I am flashing the rootFS and the emmc in the second line the first line seems a bit pointless. Unless I am missing something and there is a benefit?

As far as I understand first line flashes the rootfs.
In second line first image is used to tell the flasher how to flash specific device (?) and only flash /home directory (flash-only=mmc parameter).
I can be wrong.

Nosph3ratu
2012-03-23, 19:36
As far as I understand first line flashes the rootfs.
In second line first image is used to tell the flasher how to flash specific device (?) and only flash /home directory (flash-only=mmc parameter).
I can be wrong.

Thanks herr_oigg, but I'm still a bit confused. This would make more sense to me...

flasher -f -F main.bin
flasher -f -F emmc.bin --flash-only=mmc

OR just...

flasher -f -F main.bin -F emmc.bin --flash-only=mmc

I've checked the usage and understand the "-f", "-F" and "--flash-only=mmc" parameters its just the first line in that throws me. I'm unfamiliar with Nokia flasher so I'd rather ask before going ahead with it. I've got some time before I try as NaviFirm is taking forever to download the files...

herr_oigg
2012-03-23, 20:41
You can combine clearing the device, flashing the main and emmc in one go:
flasher -f -F main.bin -F emmc.bin --erase-user-data

@Nosph3ratu
You can combine commands in flasher.
In your case you can forget about flash-only parameter in combined command, so it should be like:

flasher -f -F main.bin -F emmc.bin

Correct me if I'm wrong...

Nosph3ratu
2012-03-23, 20:55
Yeah I've seen that post as its just after the guide, that makes more sense to me.

I just wanted to find out if there's a reason why @itsnotabigtruck added the first line or was it just a typo?

Either way I'll give it a shot once NaviFirm completes the download and doesnt get stuck again :rolleyes:

ulex54
2012-03-25, 11:11
i've updated my n9 to 1.2 through OTA. After reboot it gave me the warranty error again. I pressed volume keys a few times and it passed the screen. Gave an another error, i said okey. After that phone booted and running without problem. Phone got all 1.2 features but it says on about section its version is 20.20... like 1.1 . When ever i reboot the phone it gives warranty error. How do i fix this.

I flashed the phone many times before it came by OTA. Because of the warranty error i flashed back to 1.1 getting cmt from 1.2 .

jpfsn
2012-03-25, 16:30
Hi,
I am reflashing an N9 with the same firmware version (Singapore 005) due to a 'boot loop' problem. :o

I get the Flasher to recognise the device; but when I try to start the flash I get "Error: Unknown argument" and a list of flasher options.
Does anyone know what I am doing wrong, or the cause of the error?

Many thanks!

itsnotabigtruck
2012-03-25, 22:12
Hi,
I am reflashing an N9 with the same firmware version (Singapore 005) due to a 'boot loop' problem. :o

I get the Flasher to recognise the device; but when I try to start the flash I get "Error: Unknown argument" and a list of flasher options.
Does anyone know what I am doing wrong, or the cause of the error?

Many thanks!

That means it doesn't like the parameters you entered for the command. What was the command you used?

Remember to put double quotes around a filename if it has spaces in it.

jpfsn
2012-03-25, 22:33
Remember to put double quotes around a filename if it has spaces in it.

Heck, I didn't put the double quotes around the filename! :eek: I had a marathon 6 hours playing around, because I initially downloaded the incorrect firmware version; there were two identical file names, both for the right variant Singapore 005 - but I found out that the first was infact European. In all the frustration, I guessed that maybe the "quotes" were not required. Many thanks for the tip!! I will try again tomorrow and see how it goes. :)

finite_space
2012-03-26, 16:27
I'm a native New Zealander working and living in China, where I bought my N9...

Love the phone but feed up with the region lock to China when going to the apps store or anything related.

Will changing the code from China's to Aus/Nz help with this matter in any way.

Tried contact nokia support via e-mail... but simply got the typical '"can not" when enquiring how I can access Apps in English.

itsnotabigtruck
2012-03-26, 16:31
I'm a native New Zealander working and living in China, where I bought my N9...

Love the phone but feed up with the region lock to China when going to the apps store or anything related.

Will changing the code from China's to Aus/Nz help with this matter in any way.

Tried contact nokia support via e-mail... but simply got the typical '"can not" when enquiring how I can access Apps in English.

It's probably based on your IP address, so it's likely not to work - but you might as well give it a shot.

Don't change the product code - just flash it with 005 (Asia-Pacific) firmware and see if it works. This will get rid of QQ/etc. and add Twitter/Facebook/Dropbox, also.

sat_help
2012-03-27, 00:01
My English Is not go0o0d..sory about that...

My orginal phone product Is 059l6b8 from United Arab ( n9 16g black ) And I flashed with
DFL61_HARMATTAN_30.2012.07-1.523.2_PR_LEGACY_523_ARM_RM-696_PRD_signed

DFL61_HARMATTAN_30.2012.07-1.SEAP_EMMC_SEAP.bin

Australia Flash File

And My phone is dead ...just Vibra and screen is Black....

My Phone informashion From Win Flasher is

C:\Program Files\Nokia\Flasher>flasher -i
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1.523.2_PR_523
Success

I can flash with australian flash file but again i cant flash with Orginal products code Flash file.....

What should I do
tnx

sat_help
2012-03-27, 01:44
i am waiting........

hourt.lim
2012-03-27, 04:29
After having read the Comprehensive Firmware Flashing Guide several times, I have to say thank you very much to "itsnotabigtruck". Although, I've tried the the basic flash. I've recently posted about resetting the terminal password. Would flashing "Zeroize" help me in resetting everything on the device so that I can change my password as well? Sorry for the repeat in post.

itsnotabigtruck
2012-03-27, 04:34
After having read the Comprehensive Firmware Flashing Guide several times, I have to say thank you very much to "itsnotabigtruck". Although, I've tried the the basic flash. I've recently posted about resetting the terminal password. Would flashing "Zeroize" help me in resetting everything on the device so that I can change my password as well? Sorry for the repeat in post.

The "basic flash" ought to be enough to reset your root password, if that's the problem. You don't need to zeroize or wipe the entire phone.

hourt.lim
2012-03-27, 04:42
The "basic flash" ought to be enough to reset your root password, if that's the problem. You don't need to zeroize or wipe the entire phone.

Ran the basic flash although it didn't reset the password. When I attempt to devel-su, and enter password, says incorrect password. Any suggestions?

hourt.lim
2012-03-27, 05:21
Ran the flash again and it worked. Reset the root password. Thanks again:D

finite_space
2012-03-27, 05:36
It's probably based on your IP address, so it's likely not to work - but you might as well give it a shot.

Don't change the product code - just flash it with 005 (Asia-Pacific) firmware and see if it works. This will get rid of QQ/etc. and add Twitter/Facebook/Dropbox, also.

Perhaps a VPN app for N9 would be a thought worth considering... anyone??:)

sat_help
2012-03-27, 08:05
My English Is not go0o0d..sory about that...

My orginal phone product Is 059l6b8 from United Arab ( n9 16g black ) And I flashed with

And My phone is dead ...just Vibra and screen is Black....

My Phone informashion From Win Flasher is

I can flash with australian flash file but again i cant flash with Orginal products code Flash file.....

What should I do
tnx

ijamking
2012-03-27, 09:58
to complicated for beginner..mayb it simple for advance user like u all.if this flasher can use like install or update n9..i think that is Paradise of meego..by the way u all make meego very special then other phone.real phone..meego.

sat_help
2012-03-27, 10:56
C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_30.2012.07-1.523.2_PR_
LEGACY_523_ARM_RM-696_PRD_signed.bin -F DFL61_HARMATTAN_30.2012.07-1.SEAP_EMMC_S
EAP.bin -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_30.2012.07-1.523.2_PR_523
Image moslo not present
Image tar skipped
Image config skipped

Battery level 97 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3057 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1238 kB/s]
[x] rootfs [finished 100 % 1163844 / 1163844 kB 9643 kB/s]
[x] mmc [finished 100 % 1946649 / 1946649 kB 10326 kB/s]
Updating SW release
Success

C:\Program Files\Nokia\Flasher>

this is Flash log...
my phone product is 059L6B8...but i flashed with austalia Flash file... now my phone is dead. just a vibra..
How can I flash the phone with the main product ؟

ulex54
2012-03-27, 16:01
i've updated my n9 to 1.2 through OTA. After reboot it gave me the warranty error again. I pressed volume keys a few times and it passed the screen. Gave an another error, i said okey. After that phone booted and running without problem. Phone got all 1.2 features but it says on about section its version is 20.20... like 1.1 . When ever i reboot the phone it gives warranty error. How do i fix this.

note:I flashed the phone many times before it came by OTA. Because of the warranty error i flashed back to 1.1 getting cmt from 1.2 .

sixracer
2012-03-27, 18:51
Was flashing with Navifirm to get dual boot to Android. Android is working but now when i boot to Meego I have no signal and it prompts me for passwords for all my accounts. What did I do wrong?

ulex54
2012-03-27, 20:12
i've updated my n9 to 1.2 through OTA. After reboot it gave me the warranty error again. I pressed volume keys a few times and it passed the screen. Gave an another error, i said okey. After that phone booted and running without problem. Phone got all 1.2 features but it says on about section its version is 20.20... like 1.1 . When ever i reboot the phone it gives warranty error. How do i fix this.

note:I flashed the phone many times before it came by OTA. Because of the warranty error i flashed back to 1.1 getting cmt from 1.2 .

it was all about nss pro changing hw version while changing product code. So you need to do change hw version to original number and flash again. Thanks to gabrielharrison

Artisn
2012-03-27, 22:39
Well, i seem not to be the luckiest out of all. I tried to Zeroize the device. Apparently, i succeeded - the 64gb device is zero-dead :(.
When ran the command, it told me something like battery level and "it'll take a while". When the "while" went over 1/2 hour, i decided that something in a process went wrong, and disconnected the device.
since then, no matter, what sintax or operands i use flashing it, it would return approx this screen:

Microsoft Windows [Version 6.1.7601]

C:\Windows\system32>cd C:\Program Files\Nokia\Flasher

C:\Program Files\Nokia\Flasher>flasher -f -F DFL61_HARMATTAN_30.2012.07-1_PR_LEG
ACY_001-OEM1-958_ARM.bin
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 16502 kB/s)
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_30.2012.07-1_PR_001
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 91 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[f] cmt-mcusw [finishing 0 % 6050 / 6050 kB 2992 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2992 kB/s]
[f] rootfs [writing 0 % 97280 / 1163796 kB 9307 kB/s]
Fetching error list:
SU_GET_PARAMETER_REQ timed out.
SU_FINISH_UPDATE_REQ timed out.

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>flasher -f -F DFL61_HARMATTAN_30.2012.07-1_PR_LEG
ACY_001-OEM1-958_ARM.bin
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 18195 kB/s)
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_30.2012.07-1_PR_001
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 92 %, continuing.
SU_SET_PARAMETER_REQ timed out.
ERROR: Unable to set CMT verify mode
ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>

Can anyone help me?

dumpystig
2012-03-27, 22:51
See if this will work -

Artisn
2012-03-27, 23:18
See if this will work -

Sorry. Although it carries some hints about keeping files at one place, i don't think meego's .bin file is that much all over the place :)

dumpystig
2012-03-27, 23:23
No prob.

Let us know if/how you sort your N9.

Artisn
2012-03-27, 23:50
whenever i get to table of progress, cmt-mcusw line never completes and rootfs line never gets over 4 or 5% before the whole process stalls.
Might it be that i partially damaged my devices memory?
~2 weeks ago using the same flasher/image/flasher i got it going after bricking due to use of "nokia software updater".

dumpystig
2012-03-27, 23:55
Not sure what/if anything may be damaged but something is definitely corrupted. If you have tried several times and are still unsuccessful then I reckon you've nothing to lose by trying the method in the vid I linked to.

Artisn
2012-03-28, 00:17
Sorry to still emphasize - Phoenix is symbian targetted s/w. although it's for nokia devices, N9 cannot really be considered such. Elop clearly stated so.

dumpystig
2012-03-28, 06:45
No disrespect, but F uck Elop.

I have used this method successfully on my N8, E7 and N9 with no problems whatsoever. And it's easier than the method at page 1 in this thread.

If you presently have a N9-brick then you have nothing to lose by trying this...

rabso
2012-03-28, 07:13
Firstly I want to say a massive thanks to itsnotabigtruck for the great howto.

Before i update my phone I am hoping that my few questions can be answered by someone who knows a little more than me.

I have an Australian carrier branded phone so I know i want to use a 005 firmware

I know the guide says "Click Unmark All, then scroll to the bottom of the Files section. Tick the boxes for the two files starting with DFL61_HARMATTAN."

I am wondering what the other files are for and do i actually need them?

There are some BIN files
xxx.......keyidentifiers32
ape_hwc_xxxx
ape_cc_xxx
cmt_hwc_xxxx
cmt_cc_xxx
simlock_maemo_xxxx (2 of these files)
RM696_xxxxxxx_signature

And a few other files ending in pcx, vpl, xml and dcp

I have seen some quides/videos where people use all of the files and some (Like this guide) which says they are not needed.

If I want to keep my carrier customisation should i ignore the EMMC file or is it best to use the newer non carrier branded PR1.2 EMMC file when updating from an old PR1.x?

When my carrier releases PR1.2 i am guessing that it will be possible to replace the generic 005 firmware with PR1.2 firmware from my carrier as it will not be a downgrade?

Thanks!

Artisn
2012-03-28, 10:33
Phew! :o
The Phoenix raised my brick from ashes.
Thanks dumpystig!

sat_help
2012-03-28, 14:05
Why I Can Not Flash My Device With Orginal Product Code ?

C:\Program Files\Nokia\Flasher>flasher.exe -c -F DFL61_HARMATTAN_30.2012.07-1.33
3.2_PR_LEGACY_333_ARM_RM-696_PRD_signed.bin -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Using 1st image to detect HW
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 63
e7 d5 29 d1 d7 5e 26 bc 94 04 a5 46 ea 8f 7e 68
64 30 3e 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
HW variant: HS
Found matching 1st (916)
Sending 1st image (26496 bytes)... done.
Sending HWID query... Received 11 bytes from 1st
Got HWID: RM-696:1603
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 63
e7 d5 29 d1 d7 5e 26 bc 94 04 a5 46 ea 8f 7e 68
64 30 3e 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
Sending 2nd image (26112 bytes)... done.
Sending ping... pong.
Sending ape-algo (7273344 bytes)... done.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_30.2012.07-1.333.2_PR_333
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 100 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[_] cert-sw [init 0 % 0 / 0 kB NA ]
[ ] cmt-2nd [pending 0 % 0 / 0 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 10: Security failure

image [state progress transfer flash speed]
---------------------------------------------------------------------
[f] cert-sw [init 0 % 1 / 1 kB NA ]
[ ] cmt-2nd [pending 0 % 0 / 0 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
Progress bar initialization failed
[Pipe 0] Finishing in error state with status 10
========================================

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>

dumpystig
2012-03-28, 16:54
Phew! :o
The Phoenix raised my brick from ashes.
Thanks dumpystig!

No prob, glad it worked for you. Maybe others will give it a try if in the same boat.

Now enjoy your resurected N9 again ;)

And it is a Nokia :D

gbrm
2012-03-29, 01:37
Hello. It's great to see this post. I have a N9 from Vodafone Australia (059L488). I have read a few of these discussions around the web, but not entirely clear on a response to my question below. Hence am posting to see if someone can help.

What's the best variant to update to, without any carrier dependency and being future-proof for firmware updates as they are released from Nokia?

Appreciate all help.

dumpystig
2012-03-30, 23:14
Either Australian or Global, although I'm not sure of eithers pecking order regarding updates.

But you can always flash again to get the newest release...

gbrm
2012-03-30, 23:21
Thank you for your response. I am fairly new to this, but excited with this phone after trying N800/810 years ago. Can you please share more details on either one, as I see a number of entries in the variant list, and don't wish to brick this device. Especially, as it cautions against doing so in the guide on first page. Have a great day.

dumpystig
2012-03-30, 23:54
OK, first off look at this >

Open up NaviFirm+, in Products scroll to N9 and click to open. In Releases click on 30.2012.7.1. Above Variants click 'Export PC List' to expand all variants. Then take a look around and see what you think may benefit you, maybe google for extra info.

***Whatever F/W version you decide to use can be changed in the future.*** Incorrect - see next post below

Just remember that this could possibly brick your phone, but I have used it multiple times on my N8, E7 and N9 without any problems.

Abiove all make sure you do exactly as instructed in the vid. If you are still unsure and have questions then let me know.

Good luck :)

itsnotabigtruck
2012-03-31, 00:16
<snip>

Whatever F/W version you decide to use can be changed in the future.

<snip>

Not quite, and that has to be the cause of at least half the problems flashing. It's not permitted to lower the variant code when flashing the same firmware version. If gbrm flashes the PR1.2 Asia Pacific (005) firmware, it won't be possible to flash the PR1.2 Europe-1 (001) firmware later. However, it's possible to go in the opposite direction.

Also, there's a lot of product codes, but only 5 generic variants and 5 generic firmware images. I would strongly recommend using variant 001 whenever upgrading to a new version - downloading the images for 059J1Z5 is a safe bet. Telling people to just pick a product code is asking for trouble.

It would be nice if people would stop asking the same questions over and over...much of this thread is "which image should I flash"?

dumpystig
2012-03-31, 00:25
Right, I stand corrected - thanks for the valuable info.

And apologies for my misleading details in the above post

gbrm
2012-03-31, 01:05
Thank you, both of you for the detail information. I did search a number of discussion groups, and was left very confused, which prompted me to post here. Sorry for posting if it had been already raised before. Unfortunately, I did not learn it during my search online.

Now, I am not tech savvy but pretty good with following instructions - it is clear now that the best option is to go to 001 firmware. I've checked out the video, and plan to update this weekend through phoenix or win flash method. Hopefully, it will all go well. I have been waiting for Nokia to come back, and hoping N9 will be great after spending quite a bit of money on N800 and N810 when they were originally released, and not being satisfied with the experience. Those devices are gathering dust now!.

Thank you again, and have a great day. Cheers.

gbrm
2012-04-04, 23:48
Update - I seem to have a problem installing Phoenix. Tried a few times but no luck. It says to connect Nokia dongle or something along those lines. On re-install, it stalls on launch. Shall read up more and try again. Thanks.

itsnotabigtruck
2012-04-05, 03:49
Update - I seem to have a problem installing Phoenix. Tried a few times but no luck. It says to connect Nokia dongle or something along those lines. On re-install, it stalls on launch. Shall read up more and try again. Thanks.

Unless you absolutely need Phoenix, you're probably better off with flasher, which is free and legit. In order to use Phoenix, you'll need to find a cracked version, as ordinarily it requires the dongle to run. :(

gbrm
2012-04-06, 10:28
Thanks mate for the info. That explains why I was not having much luck...

Luckily, I got the update automatically from the carrier Vodafone this morning, and so far all looks good. Pretty timely, as this was one of the initiatives for the weekend for me. Appreciate both of your help, again, and shall use this learning and method for the next release. Cheers...

revdns
2012-04-07, 06:42
Hi, I'm the new.
My name is Grzegorz.
I have got my Nokia N9 for a week.

I upgrade from PR 1.1 to PR 1.2, and I dont strongly like this!
The status panel of IM is black...
SMS are get very big font (i repair it but not at all)...

So I've decided to change firmware to PR 1.1, but

Where is the blocker? At boot loader?
It's any chace to disable this?

Maybe update of content rom files (date/version)? from PR 1.1 to PR 1.3?

Anyone have idea?

P.S. Sorry for my English!

rainisto
2012-04-08, 17:05
Hi, I'm the new.
My name is Grzegorz.
I have got my Nokia N9 for a week.

Hi, My Name is Jonni. Please stop cross-posting the same question to 5+ new threads.

Downgrade functionality is for Nokia internals only, and NOT offered to end users. If you want some old obsoleted functionality or themes in your latest PR release, then just ask someone to copy files for you from older pr release (or extract them yourself from the .bin) and customize latest PR release yourself.

Mugs
2012-04-08, 17:30
Well done, itsnotabigtruck. Many people will surely find this guide useful if not life saving!

Yes! great instructions, worked a treat. Took the fear out of flashing the device, didn't destroy my data (I took the "Replace Operating system" option).

Only thing to note is that it's not entirely clear when/ if you need to turn on the N9 once you have issued the Flasher -i command. It took me a couple of goes, and Windows (as it has a habit of doing) started popping up all these unhelpful "installing device driver" messages. I never had to turn on the device with power button, but I did have to unplug it from my laptop once to get it going - the USB cable and Flasher software together seem to boot and then reboot the device. Somehow, it does work, and it seems that Windows needs to do the "installing device driver" thing before the Flasher recognises (and then reboots) your N9.

Appreciate the instructions! cheers

Mugs
2012-04-08, 17:32
p.s. Flashing took about 5 mins

Manskali
2012-04-10, 17:46
Is flashing PR1.2 with the instructions on the first page same as reupdating phone via Nokia Software Updater?

juanipacher
2012-04-11, 17:53
I have this problem to flash? you modify the kernel to install the version of nitdroid and installing an application on android my phone was shut and every time I turn that warning screen appears I lost the guarantee of nokia and off ... when I want flash I feel the following: e tried several things but nothing to run, I hope your help ...

http://a4.sphotos.ak.fbcdn.net/hphotos-ak-ash4/469381_2974552125802_1017692094_o.jpg

skribzy
2012-04-12, 08:08
massive thanks @itsnotabigtruck.

I have to own up to being a total noob with all things Nokia. I was on some random swiss county variant and my desire to get PR1.2 finally outweighed my patience!

Followed the guide in tandem with the english youtube link (found further back in the thread) and all went smoothly.

Thanks V much for taking the time to help folks like myself. Hopefully having changed to a more generic Northern Europe firmware I will get the updates in a timely fashion from now on!

RTA
2012-04-13, 21:45
I just bought a nokia n9 and it was the Chinese version variant 003. So I decided to flash it to a generic fw. I am fairly new to this so I was looking at many tutorials before i found this thread. Anyway it flashed just the cmt didn't complete (but I know know how to fix that) and I got all the western apps like Facebook, youtube etc. Then i tried to go into the ovi store bought it wasn't responding so I did a restore/clean and when it rebooted it never got past the spinning circle on the boot screen.

Know i tried to re flash it using the standard methods winfflash etc, tried use nokias updater, tried many different fw because the original isn't working now. Now because it successfully updated to pr1.2 before it got stuck at the boot screen every time I try to flash it it gives me the You cant downgrade error.

coderus
2012-04-16, 12:07
flash with ape + emmc, you should rewrite device fully.
also use --erase-user-data=secure

uli_china
2012-04-24, 15:55
If I run (Version 059J250, version checked in SIM tray)
flasher -a DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_003-OEM1-958_ARM.bin -k zImage –flash-only=kernel -f -R
I get the following response:
ERROR: ReadFile(65540) GetOverlappedResult() error 1167 timeout 4975 ms

Using flasher 3.12.1, no simlock, no device lock

Same happens if I run :
flasher -F DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_003-OEM1-958_ARM.bin –flash-only=kernel -f -R

What I’m doing wrong? :-(

_Routser
2012-04-25, 23:46
I was clearing my N9 (the manual way through settings) and it stuck to "clearing device" - stage for a while, next time i looked at it, it seemed as it had stuck for good and i rebooted it, after Nokia logo the "loading circle" just keeps going on the screen. Flashed succesfully, zeroized it etc but still stuck on same place..

Any suggestions? Help would be greatly appreciated.

Ps. flashing on Mac so i don't have the emmc, don't know if it has anything to do with it.

EDIT: After running out of power and reflashing it started to work, carry on..

buenavista62
2012-04-30, 23:16
You have saved my life, really.

koe
2012-05-01, 05:05
_Routser
flash again, don't know what else can be done.

emam damon
2012-05-05, 04:34
hey mates,how can i downgrade my n9?

amaziN9
2012-05-14, 00:44

amaziN9
2012-05-14, 01:14
i attached my device to pc, when its connected its only vibra then stuck on nokia logo, can i flash it?, and the flasher cant see my device to, :(

albu
2012-05-14, 14:29
Hi Guys,

great guide and discussion. I've read all the messages in this forum and I am about to flash my Nokia N9. Since this will be my first time I just wanted to double check something:

I have an N9 16gb black - device code 059L7Z9, most likely this version here: N9 RM-696 PTK Centertel (Orange PL) PL (black) v1 16GB

Until now there hasn't been a PR 1.2 update. I've waited three months, asked Orange client support (phone and forums) and no concrete answers, so I had enough ignoring and will flash a firmware so I can get my phone updated.

As there is no firmware for my device, I am assuming the best choice for my phone will be:

RM-696 NDT CENTRAL EUROPE BLACK 16GB (059J203)

Am I making the right choice here or should I choose another version?

Thanks for the reassurance.

Best

Albu

herr_oigg
2012-05-15, 06:54
Hi Guys,

great guide and discussion. I've read all the messages in this forum and I am about to flash my Nokia N9. Since this will be my first time I just wanted to double check something:

I have an N9 16gb black - device code 059L7Z9, most likely this version here: N9 RM-696 PTK Centertel (Orange PL) PL (black) v1 16GB

Until now there hasn't been a PR 1.2 update. I've waited three months, asked Orange client support (phone and forums) and no concrete answers, so I had enough ignoring and will flash a firmware so I can get my phone updated.

As there is no firmware for my device, I am assuming the best choice for my phone will be:

RM-696 NDT CENTRAL EUROPE BLACK 16GB (059J203)

Am I making the right choice here or should I choose another version?

Thanks for the reassurance.

Best

Albu

Hi there Polish user of N9 :)
I had the same problem. Tired of waiting for OTA update flashed my device with 059J1Z5.
IMO Central Europe release should be okay. If you compare images under NaviFirm, the only difference is in eMMC image. I've flashed my N9 with 059J1Z5 and then manually downloaded maps in Maps app.
Good luck and remember to flash also the eMMC image. It saves a lot of problems.

albu
2012-05-15, 13:41
More a Portuguese in Poland user :) Thanks for the advice! I will get down to business and do a "Comprehensive reset (destroys user data)". I will let you know the results :)

Thanks!

albu
2012-05-16, 17:06
Just a quick update. I've just flashed my Nokia N9 with the RM-696 NDT CENTRAL EUROPE BLACK 16GB (059J203) and everything is working smoothly. It took than less than 20 minutes :)

ibrakalifa
2012-05-16, 17:39

be relax, cos its easy, try again and pray, :D

albu
2012-05-17, 06:13
Just a quick update. I've just flashed my Nokia N9 with the RM-696 NDT CENTRAL EUROPE BLACK 16GB (059J203) and everything is working smoothly. It took than less than 20 minutes :)

Maybe I was celebrating too soon. Everything is working fine, except now I can't get 3G coverage. The phone only works is GSM mode (calls, sms and internet). If I change to 3G I can' get access to the network, so no possibility of making / receiving calls, sms, fast internet. And it's the same in the "double mode"

Would appreciate help.

ibrakalifa
2012-05-17, 07:04
flash cmt only from your old fw file

albu
2012-05-17, 08:40
flash cmt only from your old fw file

In Navifirm I get 14 files for the firmware and there are 2 with CMT on the title:

RM696_059L7Z9_cmt_ccc_v2.bin
RM696_059L7Z9_cmt_hwct_v2.bin

I should flash both these files only, from my previous FW, right?

Sorry for the basic questions, Noob here :|

Thanks

herr_oigg
2012-05-17, 21:55
In Navifirm I get 14 files for the firmware and there are 2 with CMT on the title:

RM696_059L7Z9_cmt_ccc_v2.bin
RM696_059L7Z9_cmt_hwct_v2.bin

I should flash both these files only, from my previous FW, right?

Sorry for the basic questions, Noob here :|

Thanks

I think it's better to use normal flash image with flash-only=cmt option. Of course I can be wrong.
Your problem is very interesting. Are you sure that flashing process ended without any errors?
Can it be that flashing branded locked phone with generic image caused this situation?
I followed steps from this thread and my N9 works great. The only difference is that my device doesn't have simlock (was removed with code).

albu
2012-05-18, 07:32
I think it's better to use normal flash image with flash-only=cmt option. Of course I can be wrong.
Your problem is very interesting. Are you sure that flashing process ended without any errors?
Can it be that flashing branded locked phone with generic image caused this situation?
I followed steps from this thread and my N9 works great. The only difference is that my device doesn't have simlock (was removed with code).

I don't know what happened but suddenly the phone got 3G coverage and now everything seems to be working fine - phone calls, sms, fast internet. Double mode also works fine. Strange but weird :)

The only logic explanation seems that, by coincidence, at that same time, Orange here in Warsaw had some problems in the network causing this issue. So it was never the phone. I don't know. But I am happy that everything is fine.

The flash went fine, no errors as you can see from the image I saved
http://dl.dropbox.com/u/8221269/n9_flash_console.JPG

So I will give the phone some more days before declaring "flash done". But everything seems good.

Thanks a lot for all the input.

Albu

MINKIN2
2012-05-23, 22:46
Hi guys,

Forgive me having to ask for help, but I am stuck trying to find the correct image for my phone. I am trying to Zeroize my n9 as needed in my thread (http://talk.maemo.org/showthread.php?t=84331) but I cannot seem to find an image compatible to flash with. Currently the handset is stuck on the nolo screen

My model is: RM-696 NDT SINGAPORE BLACK 64GB 059J239

Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_006

However there is no 30.2012.07-1_PR_006 for my device origin that I can see and other firmwares keep giving me the downgrade error.

As you may have read in my thread, there is a warranty issue and I would be looking at the possibility of returning this, can anyone help with providing the location of a suitable image?

MINKIN2
2012-05-24, 21:06
Sorry to bump again guys, but I am still trying to find a compatible firmware for my n9.

I hate to sound whiny, but I do have the warranty issue still pending with my screen fault and ATM I am stumped? I understand that I have to use a higher firmware version but can't find it

Here is the last attempt of flashing... (hopefully an eagle eyed user may spot) something?)

C:\Program Files\Nokia\Flasher>flasher -i
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_006
Success

C:\Program Files\Nokia\Flasher>flasher -f -F DFL61_HARMATTAN_30.2012.07-1_PR_LEG
ACY_001-OEM1-958_ARM.bin --erase-user-data=secure
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_006
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 20274 kB/s)
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8

Battery level 71 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_30.2012.07-1_PR_001
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 71 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[_] cert-sw [init 0 % 0 / 0 kB NA ]
[ ] cmt-2nd [pending 0 % 0 / 0 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 10: Security failure

image [state progress transfer flash speed]
---------------------------------------------------------------------
[f] cert-sw [init 0 % 1 / 1 kB NA ]
[ ] cmt-2nd [pending 0 % 0 / 0 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
[Pipe 0] Finishing in error state with status 10
========================================

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>

EDIT: Finally, found an image

Battery level 81 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3003 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 1232 kB/s]
[x] rootfs [finished 100 % 966666 / 966666 kB 10434 kB/s]
Updating SW release
Success

:D :D :D :D :D
You would not believe how many images I have tried.

Dragonaut
2012-05-28, 21:07
Thank you for a really excellent guide! However, i'm having a problem.

I own a swedish (339) N9 and since i re-flashed it (due to some problems with the gallery). It looses the 3G connection from time to time. The flash itself worked perfectly. No error messages or nothing. Before the lest flash i didn't have that problem at all. I've tried to perform the "--flash-only=cmt" flash using the older image. But that doesn't work. It won't flash. And it seems strange to me that this problem appears now. I mean, i updated to 1.2 NSU when it was released without any problems. Does anybody have any idea how i could solve this?

Thnx

luigialt
2012-06-01, 04:22
Hello all. I have looked in many forums and tried so many times to unbrick my N9, but haven't been successful.
My problem started when I issued the "Clear Device" option (my phone was perfectly ok before this, I just wanted to clear personal information). I left the phone working and when i checked back after 30 mins or so, all I could see is "Nokia" on a black screen, nothing happened, so I turned off and on the phone several times, until I realized something was wrong, my phone wasn't working, and I needed to flash it. I had never flashed it before.
I used navifirm to get the firmware for my actual product code (059L698) and winflash to flash it. I have tried on 3 different computers (32bit and 64bit), and downloaded the firmware file twice on different computers. It didn't work.

I haven't found any solution or similar error anywhere. I have also tried several other firmwares (with higher variants, mine es 299) and in all those cases I got the downgrade error

This is the error sequence I get.

////////////////////////////////

Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1.299.1_PR_299
Sending ape-algo image (7102 kB)...
100% (7102 of 7102 kB, avg. 17668 kB/s)
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_30.2012.07-1.299.1_PR_299
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 92 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[_] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[ ] cmt-algo [pending 0 % 0 / 0 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[_] kernel [writing 37 % 2048 / 2714 kB 3069 kB/s]
[_] rootfs [writing 0 % 1024 / 1163575 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3166 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2483 kB/s]
[f] rootfs [writing 0 % 2048 / 1163575 kB NA ]
Fetching error list:
========================================
mmc: handle_buffer failed in lzo decompress (-1)
[Pipe 4] Finishing in error state with status 1
========================================

ERROR: Failed to flash images
Status: 4

///////////////////////////

Any help would be greatly appreciated. Thanks

gaggar
2012-06-03, 18:30
HELP NEEDED!

all of the sudden my phone acted crazy today. freedez and lost all signal.. when rebooting it wrote something like "something is wrong with your sim-card"... however my simcard worked fine in my N8. I tried flashin, but the signalproblem is still there... when restarting an errormessage shows: """"There was an error. Can not connect to the network. Please contact a Nokia Care service shop"""..

Any suggestions?

geneven
2012-06-03, 18:44
Does any one know for a fact whether reflashing/using open-mode voids the warranty or not? I've read many conflicting opinions on this all over the place.

Would it be obvious to Nokia that these modifications has taken place?

If you want to know FOR A FACT whether anything with legal ramifications is true, you need to interview several lawyers who have tried a case involving same and see what they say. Of course, you will need to pay full fees involved.

If you would like to know with less certainty than that, consider the following.

Thousands of users have flashed their devices and not one has ever reported problems with Nokia care or reported here that anyone from Nokia has ever told them that flashing voided their warranty.

Overclocking is a separate issue, and there have been specific warnings from Nokia that overclocking voids the warranty. I have not seen any written claims from users that state that Nokia has told them their problem won't be fixed becaused they overclocked, but it could happen, in theory.

gaggar
2012-06-04, 18:55
Yesterday my N9 started acting wierd...
suddently it:
lost all signal
camera coudn't launch
restarted by itself.

Once it had sartet up it wrote something like "there is something wrong with your sim-card" /
at other times is says "an error has occured cannot connect to network - Contact Nokia store"

I tried using my simcard in another phone - and it workes fine - so it's not the simcard causing this, i think.

Then i figured that it could be a software problem, så first i tried to:

Restore Settings, do the following:

Open “Settings”
Tap “Reset”
Choose “Restore Settings”
Tap “Yes” to confirm the process.

Still got the message "there is something wrong with your sim-card".

then i tried:

To Clear Device, do the following:

Open “Settings”
Tap “Reset”
Choose “Clear Device”
Tap “Yes” to confirm the process.

still got the same message once starting up.

Finally i tried to flash it following the steps in this guide...i used the """""""Flasher -f -F rootfs.bin -F emmc.bin -R"""""""" thing..

Microsoft Windows XP [version 5.1.2600]

C:\Programmer\Nokia\Flasher>Flasher -f -F pr1.2.bin -F emmc.bin -R
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Found device RM-696, hardware revision 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 16238 kB/s)
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_30.2012.07-1_PR_001
Image moslo not present
Image tar skipped
Image config skipped

Battery level 20 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[_] cmt-algo [init 100 % 789 / 789 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2401 kB/s]
[_] rootfs [writing 3 % 39936 / 1163796 kB 8053 kB/s]
[ ] mmc [pending 0 % 0 / 0 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[f] cmt-algo [init 0 % 789 / 789 kB NA ]
[-] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2401 kB/s]
[x] rootfs [finished 100 % 1163796 / 1163796 kB 9780 kB/s]
[x] mmc [finished 100 % 1627169 / 1627169 kB 9369 kB/s]
Fetching error list:
========================================
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 6] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Programmer\Nokia\Flasher>

My phone is a black 64GB bought in denmark - product code 059J187

ibrakalifa
2012-06-04, 19:06
try different computer? I have flashed my device many times and always success, :confused:

gaggar
2012-06-04, 19:44
try different computer? I have flashed my device many times and always success, :confused:

try a different computer???.....4 which reason?

skyleth
2012-06-12, 11:03
I've just bought a second hand cyan n9 and i want to flash it to get it cleaned. its product code is 059L5H1: N9 RM-696 Country Variant Switzerland CH Cyan 16GB V1_COLOR but the latest firmware on navifirm for it is 20.2011.40.4 which i'm guessing is not pr1.2. which firm should i flash? GLOBAL CYAN SWAP (059K3R5) or i can flash any other 16gb firm as portuguese version (i'm from spain)

thank you

sukhraj
2012-06-25, 07:27
Yesterday my N9 started acting wierd...
suddently it:
lost all signal
camera coudn't launch
restarted by itself.

Once it had sartet up it wrote something like "there is something wrong with your sim-card" /
at other times is says "an error has occured cannot connect to network - Contact Nokia store"

I tried using my simcard in another phone - and it workes fine - so it's not the simcard causing this, i think.

Then i figured that it could be a software problem, så first i tried to:

Restore Settings, do the following:

Open “Settings”
Tap “Reset”
Choose “Restore Settings”
Tap “Yes” to confirm the process.

Still got the message "there is something wrong with your sim-card".

then i tried:

To Clear Device, do the following:

Open “Settings”
Tap “Reset”
Choose “Clear Device”
Tap “Yes” to confirm the process.

still got the same message once starting up.

Finally i tried to flash it following the steps in this guide...i used the """""""Flasher -f -F rootfs.bin -F emmc.bin -R"""""""" thing..

Microsoft Windows XP [version 5.1.2600]

C:\Programmer\Nokia\Flasher>Flasher -f -F pr1.2.bin -F emmc.bin -R
flasher 3.12.1 (Oct 6 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Found device RM-696, hardware revision 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 16238 kB/s)
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1501
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_30.2012.07-1_PR_001
Image moslo not present
Image tar skipped
Image config skipped

Battery level 20 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[_] cmt-algo [init 100 % 789 / 789 kB NA ]
[ ] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2401 kB/s]
[_] rootfs [writing 3 % 39936 / 1163796 kB 8053 kB/s]
[ ] mmc [pending 0 % 0 / 0 kB NA ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[f] cmt-algo [init 0 % 789 / 789 kB NA ]
[-] cmt-mcusw [pending 0 % 0 / 0 kB NA ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2401 kB/s]
[x] rootfs [finished 100 % 1163796 / 1163796 kB 9780 kB/s]
[x] mmc [finished 100 % 1627169 / 1627169 kB 9369 kB/s]
Fetching error list:
========================================
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 6] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Programmer\Nokia\Flasher>

My phone is a black 64GB bought in denmark - product code 059J187

I have the same problem!! You had any luck yet???:(

Kabouik
2012-06-29, 00:25
My N9 got stuck into a reboot loop when I added a line into a .conf file for adding support to an non-us external keyboard. I don't know what I did wrong, as the line I added seems correct considering the tutorial, but anyway, since then, reboot loop.

I tried to reach step #7 here (http://wiki.meego.com/N950/Fixing_MALF_state), but no way. Maemoflasher cannot find the phone, so I cannot do anything. Any idea?

Here are the symptoms I detailed in the topic about the tweak I tried:

My N9 is not detected when I plug it with the USB cable, so no way to use the flasher. The N9 keeps rebooting when I plug it and force it to turn on with a long press on the power button. If I don't do anything, it will just stay off. In both cases, maemoflasher will not find any suitable device to flash. The USB icon only appears for about one second, but no device detected. After a while and several reboot, I get this warning message stating that too many reboots have occurred, and that the phone should be updated with Nokia Software Updater, or sent to the Nokia Care. (Software problem (xsession/mthemedaemon): too many reboots).

I'm starting to worry now. I'll start to freak out in approximately four minutes.

It is kind of very very urgent for me. I'm leaving on saturday morning and I will need a phone where I'm going (as well as maps). I have a spare N900 if I can't figure out how to fix the N9, but I would have to configure it and build a microsim adapter. I know I shouldn't have played with a .conf file as I knew I would need a working phone shortly, that was stupid. But honestly I really did not think that this line would brick the phone, especially because people have done it before me and I am sure I edited the file just as they did. :/

Kabouik
2012-06-29, 00:37
I finally managed to get the phone to be detected by the computer by using another USB cable (which is strange, as the USB icon appeared briefly on the N9 with the oher cable). However, Maemoflasher still does not detect anything, either in Windows (Seven 64) or in a Linux virtual machine.

 Got it working, and solved the reboot loop by restoring the .conf file. Yeepee.

drvar
2012-06-29, 12:48
Thank you, very simple guide! Succseeded at first try :D

zhaqq
2012-07-01, 14:57
Hello Everyone,

I'm new in TMO. I'm a student and I'm a real greenhorn. Please be patient:)
Recently, I had a problems with my device:
1) Cannot install apps from store
2) Cannot install .deb files
3) Cannot update apps at Settings>Applications>Manage applications>Updates
4) Cannot uninstall apps from homescreen
5) Cannot uninstall apps from Settings>Applications>Manage applications>Applications
http://imageshack.us/photo/my-images/38/screen30jun12213453.png/
In summary, I couldn't install/uninstall any file even in terminal command line. Possibly due to a missing file.

I came across this thread(Thank You), I decided to flash my device, I wanted to do a Comprehensive reset so I used the following commands:
2) cd "c:\Program Files\Nokia\Flasher"
3) flasher -i
<Plug in device(switched off, battery almost full)>
3) Here, I've tried 3 different combinations of commands that was mentioned in this thread(I read the whole thread), all of them worked, here is one of them.

i) flasher -F DFL61_HARMATTAN_30.2012.07-1.262.2_PR_LEGACY_262_ARM_RM-696_PRD_signed.bin -F DFL61_HARMATTAN_30.2012.07-1.SEAP_EMMC_SEAP.bin -f -R
http://imageshack.us/photo/my-images/69/flashzafir.png/
This was successful. I'm able to install/uninstall files.

But now I have another problem:
I get a disclaimer screen with exclamation mark in a triangle everytime when I (re)boot. I believe this voids my warranty.:(
http://imageshack.us/photo/my-images/228/p1030997i.jpg/

I had a chat with a TMO member on twitter, explained my problem. I reflashed again using other combinations, afraid that I typed in the wrong commands previously and also in hope that the disclaimer screen would disappear:
ii) flasher -f -F DFL61_HARMATTAN_30.2012.07-1.262.2_PR_LEGACY_262_ARM_RM-696_PRD_signed.bin -F DFL61_HARMATTAN_30.2012.07-1.SEAP_EMMC_SEAP.bin --flash-only=mmc
iii) flasher -f -F DFL61_HARMATTAN_30.2012.07-1.262.2_PR_LEGACY_262_ARM_RM-696_PRD_signed.bin -F DFL61_HARMATTAN_30.2012.07-1.SEAP_EMMC_SEAP.bin

Device was successfully flashed, but the disclaimer screen still appeared. I think I've might made a mistake, can you guys give me some possible pointers to overcome the disclaimer problem. Thank you.

My device:
1) Is a Nokia N9 Black 64gb
2) Carrier branded (262) by StarHub(Singapore)
3) PR1.2

Tools I used:
1) NaviFirm+ 1.7
2) WinFlasher 3.12.1
4) Nokia N9
5) USB to MicroUSB cable
6) Laptop running Win7 64bit

Images used:
1) DFL61_HARMATTAN_30.2012.07-1.262.2_PR_LEGACY_262_ARM_RM-696_PRD_signed.bin
2) DFL61_HARMATTAN_30.2012.07-1.SEAP_EMMC_SEAP.bin

PS: Sorry for the long post!

2012-07-01, 15:24
just do a simple flash to solve the issue:

2. cd "c:\program files\nokia\flasher"
3. flasher -F DFL61_HARMATTAN_30.2012.07-1.262.2_PR_LEGACY_262_ARM_RM-696_PRD_signed.bin -f -R
4. insert the device only after typing the above command and when it says waiting for suitable device/phonenet
5. make sure your phone is turned off before plugging it in.

Edit: I've changed the command abit pls read again before flashing

zhaqq
2012-07-01, 16:36
just do a simple flash to solve the issue:

2. cd "c:\program files\nokia\flasher"
3. flasher -F DFL61_HARMATTAN_30.2012.07-1.262.2_PR_LEGACY_262_ARM_RM-696_PRD_signed.bin -f -R
4. insert the device only after typing the above command and when it says waiting for suitable device/phonenet
5. make sure your phone is turned off before plugging it in.

Edit: I've changed the command abit pls read again before flashing

Thank you for the reply, I just reflashed using your instructions, and the "Disclaimer" screen is still there :(

2012-07-01, 16:41
that's surprising...the warning screen is an indication of open mode...have you installed another kernel or sth that could have caused open mode?

zhaqq
2012-07-01, 16:57
that's surprising...the warning screen is an indication of open mode...have you installed another kernel or sth that could have caused open mode?

Nope, I've never installed any other kernel before. Btw, this is my first time flashing a mobile device:). I flashed only 2 images from NiviFirm+:
1) DFL61_HARMATTAN_30.2012.07-1.262.2_PR_LEGACY_262_ARM_RM-696_PRD_signed.bin
2) DFL61_HARMATTAN_30.2012.07-1.SEAP_EMMC_SEAP.bin

2012-07-01, 17:06
could you post the cmd screenshot of what you did and the output?

zhaqq
2012-07-01, 17:22
could you post 4he cmd screenshot of what you did and the output?

http://imageshack.us/photo/my-images/69/flashzafir.png/
http://imageshack.us/photo/my-images/69/flashzafir.png/

That's the only screenshot of one of the flashes I did, All of the flashes I did looked the same.

2012-07-01, 17:36
the only thing i can think of at this moment is your phone was switched on before attempting to flash...switch it off and enter the commands before plugging it in...also try flashing kernel only of the rootfs.bin file...

buenavista62
2012-07-05, 15:42
Do I need to download the emmc.bin too if I only want to replace the operating system (update)?

itsnotabigtruck
2012-07-05, 17:18
Do I need to download the emmc.bin too if I only want to replace the operating system (update)?

Nope - the main .bin file is enough. :)

hennye
2012-07-08, 09:31
Can I flash the 059L711 from telenor no to north europe 059J1Z8 pr1.3? I really dont understand that variant thing.

theking2
2012-07-08, 13:16
I believe it is very important to point out that the flasher is not working (Suitable USB Interface not found) on Windows 7 64bit.

Please remark the prerequisites in this guide to assist other users.

2012-07-08, 13:24
I believe it is very important to point out that the flasher is not working (Suitable USB Interface not found) on Windows 7 64bit.

Please remark the prerequisites in this guide to assist other users.

that's total and utter nonsense...did you try it out??? i've been flashing since pr1.0 till date and it works...don't spread disinformation unless you are very sure of things...

don.edri
2012-07-09, 09:10
Hi, this may be a silly question, but I've been mentally preparing myself for flashing pr 1.3 since OTA update did not show up for my variant yet, and here's the thing. I've read that one should consider "clean flash" as a good start for pr 1.3 - would that be something like "Comprehensive reset " procedure as described in the first post? On the other hand, will flashing just the .bin file be any worse in terms of performance - I understand it will wipe e.g. faster N9 that I have installed anyway. so is there any benefit to do a "clean flash"?

mapl
2012-07-11, 11:36
What's the command to just flash a dual boot kernel?

Nekron
2012-07-11, 11:52
A bit off topic but has relevance for flashing: http://talk.maemo.org/showthread.php?p=1235946#post1235946

Maybe someone has the same issue?

min0me
2012-07-11, 19:28
Hello,

Just a query, the phone locked up after some issues with the Nokia Drive software, it crashed (after a very hard day, just went blank) and then rebooted and now is stuck on the Nokia screen so i would class it as "bricked".

If i do a flash of just the OS, would i loose my contacts/sms also? I'm not so bothered about settings or applications i do have a backup at work, but its not recent.

if it would, is there a way to "backup" in the state its in or am i doomed?

regards,

jpfsn
2012-07-11, 21:12
If i do a flash of just the OS, would i loose my contacts/sms also? I'm not so bothered about settings or applications i do have a backup at work, but its not recent.

Flashing just the OS with the file ending OEM1-958_ARM.bin will leave your personal data intact. That includes SMS, contacts, photos, music etc.

min0me
2012-07-12, 09:36
Flashing just the OS with the file ending OEM1-958_ARM.bin will leave your personal data intact. That includes SMS, contacts, photos, music etc.

Thank you, i can comfirm that it left my contacts/sms in tact and saved some of my settings and all my other content

turbovomit
2012-07-13, 15:08
where can i find the last pr 1.3 ?
I don't have it in navifirm...and my n9 is in reboot loop with pr 1.3 on it.
First post talk about a image of the Pr.3 , so where can i find it ? can somebody send it to my mail ?

turbovomit
2012-07-14, 07:34
so, if i'm on pr1.3 , can i flash my n9 with the old pr1.2 ? i think i can't so what can i do ?

2012-07-14, 07:54
so, if i'm on pr1.3 , can i flash my n9 with the old pr1.2 ? i think i can't so what can i do ?

turbovomit
2012-07-14, 08:00
ok, so what can i do ?
where is the DFL61_HARMATTAN_40.2012.21-3_PR_001 ???

2012-07-14, 08:22
if u want a version without maps go to navifirm and download 059h2m6...

fusionbites
2012-07-14, 08:34

then is it possible to upgrade to pr 1.3 flash firmware if i'm using 1.2 right now? until now haven receive any updates for the pr 1.3. nw my phone running pr 1.2 flash firmware.

topet2k12001
2012-07-15, 17:49
Hi Friends,

New and proud owner of a Nokia N9 from the Philippines here. :)

I made a video tutorial of the Wiki Article: http://wiki.maemo.org/Flashing_N9, same as what I have done for some of the Wiki Articles (N900 Flashing, NITDroid for N900, Preparation of Windows 7 64-bit for flashing with N900). It's my way of contributing to this community as I have no programming background.

Here is the link to the video - http://youtu.be/u5Qp92WttU4. To the OP, hope you won't mind if this gets added to the Wiki Article? Thanks. :)

Hellano
2012-07-16, 11:42
So, my N9 is rebooting continuously. Do not cross the "NOKIA" logo.
Trying to flash, I got this error:

ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3379 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[x] kernel [finished 100 % 2714 / 2714 kB 2005 kB/s]
[f] rootfs [init 0 % 32768 / 1170282 kB NA ]
Fetching error list:
========================================
Update content failed to verify against cert: SW certificate not updated
mmc: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs /tmp/sudmmceXeOt9/internal0p2'
mmc: Could not remove mount directory /tmp/sudmmceXeOt9/mnt: No such file or directory
[Pipe 4] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

I'm on DFL61_HARMATTAN_40.2012.21-3_PR_001, trying to flash the same.

What could this rootfs fail be, and how to avoid it?

Thanks anyway.

MeeNu
2012-07-20, 16:40
@itsnotabigtruck
Thanks alot..man i owe u....just realised last night i was trying to flash my PR 1.3 with 1.1 :p

U always come up with the best....Thanks alot!

efion
2012-07-25, 03:42
I got a bootloop because of editing meegotouchhome file.
So what flashing method i've to use?
Replace OS, Comprehensive or Zeroize?
Thanks

2012-07-25, 03:50
I got a bootloop because of editing meegotouchhome file.
So what flashing method i've to use?
Replace OS, Comprehensive or Zeroize?
Thanks

replace os if you don't know how to recover your phone...

efion
2012-07-25, 03:53
replace os if you don't know how to recover your phone...

Okay so, replace OS flashing will recover the meegotouchhome files, right?

2012-07-25, 05:10
Okay so, replace OS flashing will recover the meegotouchhome files, right?

Yes.......

amirgetss
2012-07-25, 08:18
http://img193.imageshack.us/img193/2117/problemsc.png (http://imageshack.us/photo/my-images/193/problemsc.png/)

What should i do? :(((

2012-07-25, 08:34

Mitrigol
2012-07-25, 09:28
@amirgetss

Seems the firmware installed on your N9 is DFL61_HARMATTAN_40.2012.21-3_PR006

And you are trying to flash firmware DFL61_HARMATTAN_40.2012.21-3_PR005

It is not possible to downagrade firmware version once installed.
How the phone know if you try to downgrade?

It look at the PR_00x at the end of the firmware name.

So you'll have to flash a firmware with at least DFL61_HARMATTAN_40.2012.21-3_PR006 in the name and not below.

2012-07-27, 21:32
does nitriod work on new PR1.3 if yes can u suggest how can i do that ty

2012-07-31, 13:47
does nitriod work on new PR1.3 if yes can u suggest how can i do that ty

head over to forum.nitdroid.com and you'll find all the instructions...

_Routser
2012-07-31, 22:23
I uninstalled gtalk a moment ago, and the phone got stuck on "Device is malfunctioning" screen, would like to flash but can´t get to Nokia firmwares page (seems to be partially down)

Would anyone have an alternative link to pr1.3 firmware image for mac?

E: I do have the 1.2 firmware image but I guess I can't use that in any way?

nishkarsh
2012-08-01, 12:04
I have 059L9X6, it's a Vietnam model, PR 1.2

In Navifirm Plus for PR 1.3 release: 40.2012.21.3, there is no variant for 059L9X6.

I want to flash it with 059J236, which is India Variant.

Can I flash my 059L9X6 (as per the sim tray) with 059J236???

2012-08-01, 12:08
I have 059L9X6, it's a Vietnam model, PR 1.2

In Navifirm Plus for PR 1.3 release: 40.2012.21.3, there is no variant for 059L9X6.

I want to flash it with 059J236, which is India Variant.

Can I flash my 059L9X6 (as per the sim tray) with 059J236???

If you are flashing from PR1.2, you can flash to any PR1.3 variant...Recommended would be one with a 001 PR_LEGACY usually reserved for European and Global FWs... IIRC India Variant should be 005 or sth like that...Flash with a 001 variant then download whichever maps you want...That's the main difference...

2012-08-01, 12:11
I uninstalled gtalk a moment ago, and the phone got stuck on "Device is malfunctioning" screen, would like to flash but can´t get to Nokia firmwares page (seems to be partially down)

Would anyone have an alternative link to pr1.3 firmware image for mac?

E: I do have the 1.2 firmware image but I guess I can't use that in any way?

nishkarsh
2012-08-01, 12:39
If you are flashing from PR1.2, you can flash to any PR1.3 variant...Recommended would be one with a 001 PR_LEGACY usually reserved for European and Global FWs... IIRC India Variant should be 005 or sth like that...Flash with a 001 variant then download whichever maps you want...That's the main difference...

Had a Nokia N900 before this, just love the community support.
An hour ago, i was afraid when there was no update visible on my N9, now am relieved.
Thnx a ton.

Jairtzinio
2012-08-01, 17:53
My N9 has product code 059l9x6 variant Vietnam,
i would like to flash it with pr 1.3 which firmware would you guys recommend, is their anyone with same one that has tried at least?

i know there is some risk involved but if someone has tried a different one id like feedback.

nishkarsh
2012-08-01, 18:06
My N9 has product code 059l9x6 variant Vietnam,
i would like to flash it with pr 1.3 which firmware would you guys recommend, is their anyone with same one that has tried at least?

i know there is some risk involved but if someone has tried a different one id like feedback.

thedead1440 suggested it will work. will try and report back by tomorrow.

Jairtzinio
2012-08-01, 18:10
thedead1440 suggested it will work. will try and report back by tomorrow.

Arie
2012-08-01, 18:26
thedead1440 suggested it will work. will try and report back by tomorrow.

If you're going from 1.2 --> 1.3 it will.

Jairtzinio
2012-08-01, 18:32
If you're going from 1.2 --> 1.3 it will.

im more concerned about stability, do you think it will be fine on those terms?:confused:

Arie
2012-08-01, 18:43
im more concerned about stability, do you think it will be fine on those terms?:confused:

I went from a PR1.2 pr005 to a pr1.3 pr001

It's more stable and better than the pr005 I was running.

patlak
2012-08-01, 18:47
I went from a PR1.2 pr005 to a pr1.3 pr001

It's more stable and better than the pr005 I was running.

My N9 seems to have a Vietnam country version firmware, PR1.2. Will there be any issues flashing to vanilla PR1.3?

Arie
2012-08-01, 18:53
My N9 seems to have a Vietnam country version firmware, PR1.2. Will there be any issues flashing to vanilla PR1.3?

I personally prefer vanilla no matter where I am... That's just me though...

patlak
2012-08-01, 18:56
I personally prefer vanilla no matter where I am... That's just me though...

Chocolate is good too, but in this case I'd prefer vanilla ;) So, there won't be any issues flashing such a country version firmware to vanilla?

Jairtzinio
2012-08-01, 19:07
I personally prefer vanilla no matter where I am... That's just me though...

can you tell me which one you chose?
was it from navifirm?:confused:

im still trying to decide?

patlak
2012-08-01, 19:20
can you tell me which one you chose?
was it from navifirm?:confused:

im still trying to decide?

Jairtzinio
2012-08-01, 19:44

so you did use navifirm?

which firmware did you get?:confused:

patlak
2012-08-01, 19:57
Balkan, N9 64GB black 40.2012.21.3

Jairtzinio
2012-08-02, 03:03
after flashing i added all my music, then i opened the music app and it says library updating and it doesnt stop.

i added something it didnt like huh?

nishkarsh
2012-08-02, 12:03

worked for me.
using vanilla n9 now.
:D

amirgetss
2012-08-02, 16:44
@amirgetss

Seems the firmware installed on your N9 is DFL61_HARMATTAN_40.2012.21-3_PR006

And you are trying to flash firmware DFL61_HARMATTAN_40.2012.21-3_PR005

It is not possible to downagrade firmware version once installed.
How the phone know if you try to downgrade?

It look at the PR_00x at the end of the firmware name.

So you'll have to flash a firmware with at least DFL61_HARMATTAN_40.2012.21-3_PR006 in the name and not below.

thanks bro, i was able to notice it just now, sorry for the late reply, im downloading 009 variant as of the moment and im gonna flash it later, hope it works :)