[HOWTO] Comprehensive Firmware Flashing Guide for N9

[polomarko]

did you try flash the german 009 w/ phoenix?

Nope I still haven't flashed with Phoenix yet, right now I'm downloading the files, and after I'll try it. You think I should try directly the german version first?

[rswelter]

Nope I still haven't flashed with Phoenix yet, right now I'm downloading the files, and after I'll try it. You think I should try directly the german version first?

I know downloading the files is painfully slow on phoenix.
if you dont have a 1.3 firmware for your original code then I would try the german 1.3. it depends if you want go with LTA or german is up to you..it were me I would try the upgrade from 1.2 to 1.3.
after you get the downloads
for phoenix: w/ phone swd off and NOT connected
file open product select rm-696
select flashing click product code uncheck detect prod automatically,select your firmware and then click ok.
click deadphone flashing.
w/ phone off plug into usb, may have to wait for phoenix usb drivers loading??
click refurbish.
good luck
if the above doesnt work, try again with your original firmware from sim tray.
post your progress.

[joerg_rw]

[2013-05-08 20:11:20] <juiceme> but sill it bugs me that people will try in vain to flash wrong images with phoenix, and they do not belive when told that it makes no difference whatsoever...
[2013-05-08 20:11:53] <juiceme> they think it's some magic solution, somehow better than the command line flasher
[2013-05-08 20:12:09] <Jonni> yeah it makes no difference at all

FYI: jonni is an (ex-)Nokia employee and Harmattan system developer who knows his stuff. As it happens he's also the guy who helped to make openmode come true. In expression that's an "official" statement of the guys who built N9.

Phoenix might have some twists that care about problems originating from windows OS (or other apps) interfering with flashing process, which maybe are less advanced or missing in flasher-3.12. My recommendation always been to use a linux PC for flashing anyway with flasher-3.12, and that combination is probably less prone to give you any troubles than either of the other methods on any windows PC.

/j

[polomarko]

I know downloading the files is painfully slow on phoenix.
if you dont have a 1.3 firmware for your original code then I would try the german 1.3. it depends if you want go with LTA or german is up to you..it were me I would try the upgrade from 1.2 to 1.3.
after you get the downloads
for phoenix: w/ phone swd off and NOT connected
file open product select rm-696
select flashing click product code uncheck detect prod automatically,select your firmware and then click ok.
click deadphone flashing.
w/ phone off plug into usb, may have to wait for phoenix usb drivers loading??
click refurbish.
good luck
if the above doesnt work, try again with your original firmware from sim tray.
post your progress.

Ok tried to flash with the FW from my Sim tray code and it gives me the "downgrade disallowed", so I tried to flash with the German version that is on the phone at the moment, first it starts normally than it gives the "MCUSW flashing failed" and starts over. If you continue it gives the same error over and over again.
Now I'm really desperate and dont think there is any more hope for the phone

[polomarko]

[2013-05-08 20:11:20] <juiceme> but sill it bugs me that people will try in vain to flash wrong images with phoenix, and they do not belive when told that it makes no difference whatsoever...
[2013-05-08 20:11:53] <juiceme> they think it's some magic solution, somehow better than the command line flasher
[2013-05-08 20:12:09] <Jonni> yeah it makes no difference at all

FYI: jonni is an (ex-)Nokia employee and Harmattan system developer who knows his stuff. As it happens he's also the guy who helped to make openmode come true. In expression that's an "official" statement of the guys who built N9.

Phoenix might have some twists that care about problems originating from windows OS (or other apps) interfering with flashing process, which maybe are less advanced or missing in flasher-3.12. My recommendation always been to use a linux PC for flashing anyway with flasher-3.12, and that combination is probably less prone to give you any troubles than either of the other methods on any windows PC.

/j

Peoples are just trying to find solutions to fix their phones (as I am) so surely will try anything in the hope they will achieve it. When you are desperate there isn't anything you wouldn't do to make things better!

P.s: Do you have any idea on how to fix the problem with my N9?

[rswelter]

Ok tried to flash with the FW from my Sim tray code and it gives me the "downgrade disallowed", so I tried to flash with the German version that is on the phone at the moment, first it starts normally than it gives the "MCUSW flashing failed" and starts over. If you continue it gives the same error over and over again.
Now I'm really desperate and dont think there is any more hope for the phone
I forgot to mention when I did the above I got a similar error message. I disc the phone and turned it back off reconnected (after switching ph off again)and was able to try flashing again. I dont remember all of the messages, but the second time it did work. I think the message said attempting "recovery flashing"

If that doesnt work, its back to winflasher we go:
>Flasher -F germanmain.bin -F germanemmc.bin -f -R

have you tried the above cmd line, just fix the names of the files.

[polomarko]

I forgot to mention when I did the above I got a similar error message. I disc the phone and turned it back off reconnected (after switching ph off again)and was able to try flashing again. I dont remember all of the messages, but the second time it did work. I think the message said attempting "recovery flashing"

If that doesnt work, its back to winflasher we go:
>Flasher -F germanmain.bin -F germanemmc.bin -f -R

have you tried the above cmd line, just fix the names of the files.

Ok, did it find below the output:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

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

C:\Program Files\Nokia\Flasher>flasher -F D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_
PR_LEGACY_009-OEM1-958_ARM.bin -F 61A8E22C_DFL61_HARMATTAN_40.2012.13-7.DACH_EMM
C_DACH.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_40.2012.21-3_PR_009
Image moslo not present
Image tar skipped
Image config skipped

Battery level 40 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 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 ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
[ ] 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 ]
[_] 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 1917 kB/s]
[f] rootfs [pending 0 % 0 / 1170206 kB NA ]
[-] 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 1917 kB/s]
[f] rootfs [pending 0 % 0 / 1170206 kB NA ]
[-] mmc [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
Update content failed to verify against cert: SW certificate not updated
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not remove mount directory /tmp/sudmmcgQKicR/mnt: No such file or dir
ectory
[Pipe 5] Finishing in error state with status 1
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:\Program Files\Nokia\Flasher>

[rswelter]

Ok, did it find below the output:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

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

C:\Program Files\Nokia\Flasher>flasher -F D4A3D2AC_DFL61_HARMATTAN_40.2012.21-3_
PR_LEGACY_009-OEM1-958_ARM.bin -F 61A8E22C_DFL61_HARMATTAN_40.2012.13-7.DACH_EMM
C_DACH.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_40.2012.21-3_PR_009
Image moslo not present
Image tar skipped
Image config skipped

Battery level 40 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 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 ]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 94 / 94 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
[ ] 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 ]
[_] 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 1917 kB/s]
[f] rootfs [pending 0 % 0 / 1170206 kB NA ]
[-] 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 1917 kB/s]
[f] rootfs [pending 0 % 0 / 1170206 kB NA ]
[-] mmc [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
Update content failed to verify against cert: SW certificate not updated
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not remove mount directory /tmp/sudmmcgQKicR/mnt: No such file or dir
ectory
[Pipe 5] Finishing in error state with status 1
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:\Program Files\Nokia\Flasher>

mmc: sfdisk returned status 1
mmc: Could not remove mount directory /tmp/sudmmcgQKicR/mnt: No such file or dir"

check your files both in the same place? MMC is not found. maybe you have bad copy of MMC? you could always find the phoenix copy and paste into the winflasher directory.
I used 059J202 files downloaded from phoenix,

[polomarko]

mmc: sfdisk returned status 1
mmc: Could not remove mount directory /tmp/sudmmcgQKicR/mnt: No such file or dir"

check your files both in the same place? MMC is not found. maybe you have bad copy of MMC? you could always find the phoenix copy and paste into the winflasher directory.
I used 059J202 files downloaded from phoenix,

They are exactly the same files because I have not downloaded those from Phoenix but I downloaded those separately and inserted to the Phoenix folder.

[polomarko]

Now the phone doesn't even start it just gives a big panel saying the you have modified the device software making the warranty permanently void, and that I have to install a Nokia authorized operating system.

[rswelter]

They are exactly the same files because I have not downloaded those from Phoenix but I downloaded those separately and inserted to the Phoenix folder.
try the phoenix files
cmd line looks good no typos.
makes me think maybe bad emmc file? is the file populated? what size is it?

[rswelter]

Now the phone doesn't even start it just gives a big panel saying the you have modified the device software making the warranty permanently void, and that I have to install a Nokia authorized operating system.

I have gotten that message many times.
check out those files or try either phoenix files

[polomarko]

try the phoenix files
cmd line looks good no typos.
makes me think maybe bad emmc file? is the file populated? what size is it?

The emmc file is 1.731.092 kb, means around 1.7 gb. I cant download anything from phoenix, it doesn't give me the option to download any firmware file so that's why I downloaded those directly from mr crab and inserted on the phoenix file.

[rswelter]

The emmc file is 1.731.092 kb, means around 1.7 gb. I cant download anything from phoenix, it doesn't give me the option to download any firmware file so that's why I downloaded those directly from mr crab and inserted on the phoenix file.
checking if phoenix download is working for me

working for me, sure you are following my method.

[polomarko]

checking if phoenix download is working for me

working for me, sure you are following my method.

Yes I followed exactly what you said, but phoenix doesn't give me any download option. Anyway, just closed winflash and opened it again and it flashed all the way through but it gave me the original error:

bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 6] Finishing in error state with status 1
========================================

So we are back at the beginning . . .

[rswelter]

Yes I followed exactly what you said, but phoenix doesn't give me any download option. Anyway, just closed winflash and opened it again and it flashed all the way through but it gave me the original error:

bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 6] Finishing in error state with status 1
========================================

So we are back at the beginning . . .
on phoenix "download package" is under tools..
my ver 2012.24.000.48366

winflasher
Flasher -F germanmain.bin --flash-only=cmt -f

[polomarko]

on phoenix "download package" is under tools..
my ver 2012.24.000.48366

winflasher
Flasher -F germanmain.bin --flash-only=cmt -f

Did it, still the same result:

C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY
_009-OEM1-958_ARM.bin --flash-only=cmt -f
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_40.2012.21-3_PR_009
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 19442 kB/s)
Suitable USB interface (phonet) not found, waiting...
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_40.2012.21-3_PR_009
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 24 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 1] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>

Also on phoenix tools there isn't any option for downloading, the only options are:
Label printing
Options
Smart card activator
Certificate restore
CU-4\terminal current
Consumption
Product code change

Also in the options directory there isn't any option for download

[rswelter]

Did it, still the same result:

C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY
_009-OEM1-958_ARM.bin --flash-only=cmt -f
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_40.2012.21-3_PR_009
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 19442 kB/s)
Suitable USB interface (phonet) not found, waiting...
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_40.2012.21-3_PR_009
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 24 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 1] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>

Also on phoenix tools there isn't any option for downloading, the only options are:
Label printing
Options
Smart card activator
Certificate restore
CU-4\terminal current
Consumption
Product code change

Also in the options directory there isn't any option for download

C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY
_009-OEM1-958_ARM.bin --flash-only=cmt -f
try again with the sim tray main 059K172 the 1.3PR version

any other options if you click options on phoenix? if not try to find my version of phoenix if you want to continue with phoenix

[polomarko]

C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY
_009-OEM1-958_ARM.bin --flash-only=cmt -f
try again with the sim tray main 059K172 the 1.3PR version

any other options if you click options on phoenix? if not try to find my version of phoenix if you want to continue with phoenix

Ok, just did the cmt flash with the fw 1.3 according to the phone sim tray but it still gives me the same error.

C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY
_001-OEM1-958_ARM.bin --flash-only=cmt -f
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_40.2012.21-3_PR_009
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 20872 kB/s)
Suitable USB interface (phonet) not found, waiting...
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_40.2012.21-3_PR_001
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped
Charging battery, 10 % battery level (11 % required). Ctrl-c to exit
Battery level 11 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 ]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Timeout while waiting for the HWBREAK
Could not reboot into cold bootmode
[Pipe 1] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>

What version of phoenix do you have? If phoenix and win flash do the same thing than the result will be the same anyway, whichever program I use. What do you think? Any more ideas on how to proceed? :(

[rainisto]

Didnt have time to read all the previous messages, but you of course have tested to cold flash with -c flag. Phoenix will not help you.

You might be just a lucky one that has bought used device with broken CMT hardware, so you will never get phonecalls to work, but you can use it as wifi device or as spareparts to your next N9 phone that you buy.

[polomarko]

You might be just a lucky one that has bought used device with broken CMT hardware, so you will never get phonecalls to work, but you can use it as wifi device or as spareparts to your next N9 phone that you buy.

So you think there isn't any hope for me anymore?
If this is the case I dont think my next phone will be a N9 . . .

Haven't tried the cold flash actually. How does it change from the normal flash except the c at the end instead of f?

[rainisto]

So you think there isn't any hope for me anymore?
If this is the case I dont think my next phone will be a N9 . . .

Haven't tried the cold flash actually. How does it change from the normal flash except the c at the end instead of f?

Full flash:

sudo flasher -c -f -F main.bin -R

vs flash only firmware and leave cmt dead:

sudo flasher -c -f -F main.bin --flash-only=nolo,kernel,rootfs -R

[polomarko]

Full flash:

sudo flasher -c -f -F main.bin -R

vs flash only firmware and leave cmt dead:

sudo flasher -c -f -F main.bin --flash-only=nolo,kernel,rootfs -R

Ok I'll try right away the full flash. Should I use the sudo command, because I'm on windows not linux and I have only used flasher?

[rswelter]

Ok I'll try right away the full flash. Should I use the sudo command, because I'm on windows not linux and I have only used flasher?
havent tried cold flashing

[peterleinchen]

havent tried cold flashing
What does cold flashing have to do with running a command with higher privileges?

@polomarko
" 'sudo' on linux" -eq " 'run as administrator' on windows", so something you already have done, as flasher runs only with admin privileges on Win.

Just go ahead and follow rainisto's path.
Maybe try a warm flash directly after the cold flash (idk, but heard/read smth like that).

And one more thing:
C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY
_009-OEM1-958_ARM.bin --flash-only=cmt -f
try again with the sim tray main 059K172 the 1.3PR version
C:\Program Files\Nokia\Flasher>flasher -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY
_001-OEM1-958_ARM.bin --flash-only=cmt -f
When trying to flash a cmt from another sw release you need to give the ape-algo from current release, so your command should look like:
flasher -a DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin --flash-only=cmt -f
Otherwise it is pointless, as it would be a normal flashing operation...

[rswelter]

What does cold flashing have to do with running a command with higher privileges?

@polomarko
" 'sudo' on linux" -eq " 'run as administrator' on windows", so something you already have done, as flasher runs only with admin privileges on Win.

Just go ahead and follow rainisto's path.
Maybe try a warm flash directly after the cold flash (idk, but heard/read smth like that).

And one more thing:


When trying to flash a cmt from another sw release you need to give the ape-algo from current release, so your command should look like:
flasher -a DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001[-OEM1-958_ARM.bin --flash-only=cmt -f
Otherwise it is pointless, as it would be a normal flashing operation...
I was not advocating the use of cold flashing in Polomarkos problem. as I said, I have not tried it. though I would like to learn about it. thanks for the input.
ahh I see your last comment, yes I learned that the hard way. I should of mentioned that for the CMT flash.

[tenthnazgul]

I've been trying to flash the N9 in order to reboot it, but after i give the flasher -R command, and plug in the phone, the cmd screen remains at "Suitable USB interface (bootloader/phonenet) not found, waiting..." and remains that way.

The Driver Software Installation on my Windows 7 says "Unidentified Device - Device uplugged"
http://i39.tinypic.com/op8rc3.png

The phone, meanwhile, is charging so its evidently connected.

What could be the problem?

[rswelter]

I've been trying to flash the N9 in order to reboot it, but after i give the flasher -R command, and plug in the phone, the cmd screen remains at "Suitable USB interface (bootloader/phonenet) not found, waiting..." and remains that way.

The Driver Software Installation on my Windows 7 says "Unidentified Device - Device uplugged"
http://i39.tinypic.com/op8rc3.png

The phone, meanwhile, is charging so its evidently connected.

What could be the problem?

was the phone off when you plugged it in?

[tenthnazgul]

I've been trying to flash the N9 in order to reboot it, but after i give the flasher -R command, and plug in the phone, the cmd screen remains at "Suitable USB interface (bootloader/phonenet) not found, waiting..." and remains that way.

The Driver Software Installation on my Windows 7 says "Unidentified Device - Device uplugged"
http://i39.tinypic.com/op8rc3.png

The phone, meanwhile, is charging so its evidently connected.

What could be the problem?

Resolved.
I unplugged it and replugged it a few times, and Windows magically found the updates itself. :rolleyes:

If anyone else is facing the same issue though, these should help:
http://sourceforge.net/projects/libusb-win32/
which i found from here:
http://everythingn9.com/update-pr1-2-nokia-n9/

Alternatively http://www.mitsdrivers.com/pages_n9-drivers.html

[suyog]

Full flash:

sudo flasher -c -f -F main.bin -R

vs flash only firmware and leave cmt dead:

sudo flasher -c -f -F main.bin --flash-only=nolo,kernel,rootfs -R

Could you please tell what you mean by "leave cmt dead" ?
I guess you know a lot about cmt flashing process and what it doesn exactly. I am also facing sim card error issue and when i flashed chinese fw cmt only , I am getting phone to work but only 50% of times. It shows sim error, no IMEI number when it does not.

I used command
flasher -F chinesemain.bin --flash-only=cmt -f

But now there seems to be some more info about ape-algo also.As one more person, Peter has posted.
Can you please clarify more?

[polomarko]

What does cold flashing have to do with running a command with higher privileges?

@polomarko
" 'sudo' on linux" -eq " 'run as administrator' on windows", so something you already have done, as flasher runs only with admin privileges on Win.

Just go ahead and follow rainisto's path.
Maybe try a warm flash directly after the cold flash (idk, but heard/read smth like that).

And one more thing:


When trying to flash a cmt from another sw release you need to give the ape-algo from current release, so your command should look like:
flasher -a DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin --flash-only=cmt -f
Otherwise it is pointless, as it would be a normal flashing operation...

Thank you for your help Peterleinchen. I'll follow your instructions and let you know on the progress.

[latency]

I made a fool out of myself today and ruined my N9. I hade very little battery juice left when I decided to install the Billboard app. During the installation the battery got totally empty and the phone died.

It was then impossible to even start the phone. I managed to charge it by using the Flasher and then stopped the process at 10% of charge to continue charging with the wall charger.

I have my phone set up with dualboot: Nitdroid and MeeGo 1.2
After my incident I can only boot into Nitdroid. Battery is at 50% now so it's not caused by low battery anymore. Something probably got messed up when installing the app and crashing in the midst of the process.
Can I do something to be able to boot into MeeGo or am I doomed to flash my phone?

If I decide to reflash and go all MeeGo 1.3, is it possible to flash from 1.2 to 1.3 in my situation with a dual boot setup? Will the dual boot and Nitdroid disappear in the progress or do I have to do something special.

Edit: Moderators; feel free to move this post into another thread if it's misplaced.

[suyog]

I made a fool out of myself today and ruined my N9. I hade very little battery juice left when I decided to install the Billboard app. During the installation the battery got totally empty and the phone died.

It was then impossible to even start the phone. I managed to charge it by using the Flasher and then stopped the process at 10% of charge to continue charging with the wall charger.

I have my phone set up with dualboot: Nitdroid and MeeGo 1.2
After my incident I can only boot into Nitdroid. Battery is at 50% now so it's not caused by low battery anymore. Something probably got messed up when installing the app and crashing in the midst of the process.
Can I do something to be able to boot into MeeGo or am I doomed to flash my phone?

If I decide to reflash and go all MeeGo 1.3, is it possible to flash from 1.2 to 1.3 in my situation with a dual boot setup? Will the dual boot and Nitdroid disappear in the progress or do I have to do something special.

Edit: Moderators; feel free to move this post into another thread if it's misplaced.

Please check if R&D mode helps you.
http://wiki.maemo.org/N9QTweak#RD_Mode

[peterleinchen]

When trying to flash a cmt from another sw release you need to give the ape-algo from current release, so your command should look like:
flasher -a DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_009-OEM1-958_ARM.bin -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin --flash-only=cmt -f
Otherwise it is pointless, as it would be a normal flashing operation...

Thank you for your help Peterleinchen. I'll follow your instructions and let you know on the progress.

Beware that I am not a flashing guru (like rainisto and others).
And maybe I am/was confused and mixed above with flashing different kernels (as I never needed to flash different cmt).
So maybe wait for a confimation from others.

But for sure I would at first start all over with a total reflash
flasher -F fw009.bin -F emmc.bin -f --erase-user-data=secure
and finally flash above command (without reboot).

[latency]

Please check if R&D mode helps you.
http://wiki.maemo.org/N9QTweak#RD_Mode
Thanks! :) That did the trick. I managed to boot in RD mode and then after doing a reset in the settings I could boot in normal production mode.

Anyway, if I decide to flash my phone to only have Harmattan 1.3, how should I proceed? I guess I have an open kernel since I'm dual booting with Nitdroid and Harmattan 1.2.
Will a flash just remove bootloaders and Nitdroid bringing me a single Harmattan 1.3?

[suyog]

Thanks! :) That did the trick. I managed to boot in RD mode and then after doing a reset in the settings I could boot in normal production mode.

Anyway, if I decide to flash my phone to only have Harmattan 1.3, how should I proceed? I guess I have an open kernel since I'm dual booting with Nitdroid and Harmattan 1.2.
Will a flash just remove bootloaders and Nitdroid bringing me a single Harmattan 1.3?

If you do zerorize flash it should work. Also please note that there is nothing called harmattan 1.3.
MeeGo Harmattan is 1.2 but Nokia has PR 1.3 which is latest.

[latency]

If you do zerorize flash it should work. Also please note that there is nothing called harmattan 1.3.
MeeGo Harmattan is 1.2 but Nokia has PR 1.3 which is latest.
Thank you for your clarification. I will try your solution by zerorizing and flashing my device to PR 1.3.

[snowboarder]

polomarko,

I know it's a long shot but have you tried flashing using a linux system?

SB

[sm0k3]

Hello to all members,i am new user of nokia n9 and i have some questions about reflashing :). In the flasher folder i put only firmware.bin and emmc.bin,or also all the other files from here http://mrcrab.net/nokia/Nokia_N9.html?productType=RM-696&releaseID=7048842309&variantID=7076659064&productCode=059J228&version=40.2012.21.3 ?,i use ''sudo flasher'' command only in linux,for windows i use just ''flasher''? I have to put ''flasher -i'' command before the ''flasher -f -F firmware.bin -F emmc.bin -R'' command? Because the forum of my country said to put only ''flasher -f -F firmware.bin -F emmc.bin -R''.
I just bought my n9 and i can't connect it to my nokia 6600 via bluetooth but both devices can connect to other phones(sony xperia),i tried restore settings and clear device and nothing work thats why i want to reflash it just to be sure :confused:
I'm sorry for the long post and noobish questions but i just want to be sure of what i'm doing :)

[panorton]

Nokia Care Waterford and Nokia.ie have failed to save my N9 which came from china and are not willing to offer any warranty for it in Europe.

[suyog]

Hello to all members,i am new user of nokia n9 and i have some questions about reflashing :). In the flasher folder i put only firmware.bin and emmc.bin,or also all the other files from here http://mrcrab.net/nokia/Nokia_N9.html?productType=RM-696&releaseID=7048842309&variantID=7076659064&productCode=059J228&version=40.2012.21.3 ?,i use ''sudo flasher'' command only in linux,for windows i use just ''flasher''? I have to put ''flasher -i'' command before the ''flasher -f -F firmware.bin -F emmc.bin -R'' command? Because the forum of my country said to put only ''flasher -f -F firmware.bin -F emmc.bin -R''.
I just bought my n9 and i can't connect it to my nokia 6600 via bluetooth but both devices can connect to other phones(sony xperia),i tried restore settings and clear device and nothing work thats why i want to reflash it just to be sure :confused:
I'm sorry for the long post and noobish questions but i just want to be sure of what i'm doing :)

I had similar issue while syncing contacts from Nokia 808 to N9.
I was getting authentication failure in bluetooth connection.
But N9 and 808 was able to connect to other devices,
So I did restore settings on 808 and issue was resolved , so I will suggest you to try that first. Since Bluetooth connection from N9 to other devices is working, you should not flash N9.

[suyog]

Nokia Care Waterford and Nokia.ie have failed to save my N9 which came from china and are not willing to offer any warranty for it in Europe.

That is really bad news. Now can you at least use it in offline mode?
I mean does it show WLAN and Bluetooth mac id in settings?

[panorton]

That is really bad news. Now can you at least use it in offline mode?
I mean does it show WLAN and Bluetooth mac id in settings?
I can't remember. They have it a forthnight and will post it back to me on Monday.

[panorton]

That is really bad news. Now can you at least use it in offline mode?
I mean does it show WLAN and Bluetooth mac id in settings?

Sorry I do remember. It was stuck in a boot loop which would eventually suggest I take it to Nokia care!!

[panorton]

I got the phone back from Nokia and flashed it again with main.bin which is European 09 version. Phone boots saying there is a problem with the sim card. It attempts to boot but loops. I then flashed with old_main flash only cmt and it boots as far as take the tour and stops and boots again as far as the tour. After a while it suggests I repair the phone with Nokia Suite.

[suyog]

I got the phone back from Nokia and flashed it again with main.bin which is European 09 version. Phone boots saying there is a problem with the sim card. It attempts to boot but loops. I then flashed with old_main flash only cmt and it boots as far as take the tour and stops and boots again as far as the tour. After a while it suggests I repair the phone with Nokia Suite.

Can you post output of flashing ?
You can try to flash with german fw and see how it goes. At least if you can flash wit that, it will make your N9 usable as everything else except telephony. Mine is like that now :)

[panorton]

Can you post output of flashing ?
You can try to flash with german fw and see how it goes. At least if you can flash wit that, it will make your N9 usable as everything else except telephony. Mine is like that now :)

Phone now not been found on usb

[panorton]

I restarted the computer and it finds the phone again. I flashed with the Germain firmware and it's the very same.

[panorton]

Progress. When I flash the phone with the German firmware I can start the phone, it takes a while. It has no wifi and there is a problem with sim card message appears at the start. There are no maps but the camera works and the phone stays on. If I then flash the old_main I get back to boot loop. I'm now downloading a new Chineese firmware and I'll use this as an Old_main.bin and do a cmt oly flash. Fingers crossed.

[panorton]

Unfortunately I'm back where I started. Phone boots as far as the Nokia logo and starts all over again. What did I do to deserve this phone.

[suyog]

Unfortunately I'm back where I started. Phone boots as far as the Nokia logo and starts all over again. What did I do to deserve this phone.

Try flashing german fw and then try cmt flash only from fw for product code mentioned on sim tray. If that doesnt help then only use chinese as last resort.
Let me know how it goes.

[panorton]

Try flashing german fw and then try cmt flash only from fw for product code mentioned on sim tray. If that doesnt help then only use chinese as last resort.
Let me know how it goes.

I've done all that time and time again. The phone starts after a main.bin flash. It reports errors pipe 7 I think. I've no mobile network, no wifi no maps. I do have camera and bluetooth. Then I flash old_main.bin which matches the product code and the phone won't start. The product code is Chineese

[panorton]

Sorry for sounding so despondent.

[suyog]

Sorry for sounding so despondent.

I can understand as I also faced same problem and felt very helpless because it is not cheap phone.
Also downloading these huge fw files consumes lots of data.

But Can you try to download UAE fw and check? It have higher version number than german. I am suggesting this because you can at least try to get phone working in such condition that you can see wlan and bluetooth id and no longer sim error while startup.
This will allow you to use it for all functions except telephony.

[panorton]

I can understand as I also faced same problem and felt very helpless because it is not cheap phone.
Also downloading these huge fw files consumes lots of data.

But Can you try to download UAE fw and check? It have higher version number than german. I am suggesting this because you can at least try to get phone working in such condition that you can see wlan and bluetooth id and no longer sim error while startup.
This will allow you to use it for all functions except telephony.

I tried that but it's the very same.

[suyog]

Anyone can help me further to know what is exactly causing this issue?

Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_480
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 18450 kB/s)
Suitable USB interface (phonet) not found, waiting...
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_40.2012.21-3.418.2_PR_418
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 79 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cmt-2nd [finished 100 % 95 / 95 kB NA ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[_] cmt-mcusw [finishing 75 % 6050 / 6050 kB 3390 kB/s]
ERROR: SU_GET_UPDATE_STATUS_REQ terminated with error code 1: Unknown error

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 3390 kB/s]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
MTC_POWER_OFF not received
CMT RFS failed
[Pipe 2] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

[rswelter]

I am just guessing here, but did you have developer mode on before flashing?

[suyog]

I am just guessing here, but did you have developer mode on before flashing?

yes, will that make any difference? Ok, I will try without developer mode on now.

[rswelter]

yes, will that make any difference? Ok, I will try without developer mode on now.

possibly, just like when charge the phone it automatically turns itself on(with developer mode on). my guess is that after the first part of the flashing your phone is turning on and giving you that error message? just a guess mind you, though it is logical. only way to know for sure is to switch it off (developer mode)and try again?

[suyog]

possibly, just like when charge the phone it automatically turns itself on(with developer mode on). my guess is that after the first part of the flashing your phone is turning on and giving you that error message? just a guess mind you, though it is logical. only way to know for sure is to switch it off (developer mode)and try again?

Tried it and no luck.

[rswelter]

Tried it and no luck.
what was the cmd line you were trying to run?

[suyog]

what was the cmd line you were trying to run?

flasher -f -F old_main.bin --flash-only=cmt but I know you will suggest adding -f and end but that won't make any different

[rswelter]

flasher -f -F old_main.bin --flash-only=cmt but I know you will suggest adding -f and end but that won't make any different
does your phone stay in flasher mode when you plug it in to flash?
or does it try to boot up?

[suyog]

It remains in flasher mode.

[joerg_rw]

you're still aware of the general "NO DOWNGRADES" policy enforced on harmattan? Take care so you don't end with <most-recent-release>.<inuktitut-version> which happens to have the highest numeric release.version ID. You couldn't "downgrade" to *any* other version or release, I.E. you'd be locked to that version!

/j

[peterleinchen]

<most-recent-release>.<inuktitut-version>
That's where I am!
Swiss country variant no. 480. Anyone can bid higher? ;)

[suyog]

I am on swiss 480 version now :)
I read somewhere that Nokia guys with some certificates can do downgrade , is it true or downgrade is impossible?

[joerg_rw]

That's where I am!
Swiss country variant no. 480. Anyone can bid higher? ;)

Oh well, I could figure worse terminal stations :-D Swiss variant probably isn't that bad for most of western users. Those depending on asian or arabic or hebrew localisation will curse though.

I heard rumors from "those who should know" that there's actually a hack to allow downgrade.
[2013-05-23 16:48:26] <Jonni> you can actually downgrade back to pr1.0 even without R&D cert, but that exploit has never leaked.
[2013-05-23 16:49:05] <DocScrutinizer05> I'd dare to claim this inability to downgrade been the final nail to coffin of any commercial app development
[2013-05-23 16:49:18] <Jonni> quite usefull if you want to change from 009 variant back to 001 variant :)
[2013-05-23 16:49:43] <DocScrutinizer05> using flasher-3.5 ?
[2013-05-23 16:50:16] <Jonni> flasher 3.12.1'
[2013-05-23 16:50:17] <DocScrutinizer05> or using coldflashing?
[2013-05-23 16:50:33] <Jonni> just using normal flashing :)
Maybe eventually we'll find some gem in the voids of interwebs :-)

/j

[peterleinchen]

Oh well, I could figure worse terminal stations :-D Swiss variant probably isn't that bad for most of western users. Those depending on asian or arabic or hebrew localisation will curse though.True! :D

I heard rumors from "those who should know" that there's actually a hack to allow downgrade.
Maybe eventually we'll find some gem in the voids of interwebs :-)

/j
Heard that also, but I do not believe we will see it in the wilderness
:rolleyes:

[keptn]

Could someone reupload winflasher 3.12.1 cause this one (http://tablets-dev.nokia.com/maemo-dev-env-downloads.php) is broken :D

[thedead1440]

Could someone reupload winflasher 3.12.1 cause this one (http://tablets-dev.nokia.com/maemo-dev-env-downloads.php) is broken :D

http://skeiron.org/tablets-dev/maemo-dev-env-downloads/

[chilango]

Someone can help me. I had flashed on my N9 the software
V 40.2012.21-3_PR_005.
For going to my provider Telcel to unlock my phone i flashed back with the original FW for the Productcode via Nokia Suite (reinstall FW).
It is now
V 40.2012.21-3.420.4_PR_420
The bad think is that my provider Telcel refuse to unlock the phone and even more bad, i have now a crapy FW, Doble Tip to unlock doesnt work (yes its activate in the menu) yesterday it was blocking. Restart wasnt posible. Reflash was the only solution.
Reflash back to V 40.2012.21-3_PR_005 isnt posible (you know its like an disallowed downgrade)
So how can i reflash a good working FW?

In the center of the town some guys offer me to unlock with a flasherbox.
Is it also posible to downgrade the N9 with a flasherbox?

Thanks in advance

[joerg_rw]

Could someone reupload winflasher 3.12.1 cause this one (http://tablets-dev.nokia.com/maemo-dev-env-downloads.php) is broken :D

Broken? no way!

[joerg_rw]

In the center of the town some guys offer me to unlock with a flasherbox.
Is it also posible to downgrade the N9 with a flasherbox?

Thanks in advance

I'd bet on those guys not having the faintest clue about N9 and probably failing epically. Or, even worse, they actually manage to flash CMT to some crappy and incompatible cmt-FW and that's been it then for your N9. Unless one of the guys can show you a unlocked N9 they managed to unlock, I'd friendly say "thanks gentlemen for your offer, but no thanks"

/j

[thedead1440]

chilango,

01:15 <thedead1440> Jonni: this post claims that someone offered to downgrade the N9 with a flasherbox: http://talk.maemo.org/showpost.php?p=1350038&postcount=825 >> is it possible?
01:17 <Jonni> thedead1440: post says that they offer unlock, and only asks about downgrade. bruteforce unlocking is pretty simple, downgrade is not possible with flasherbox.

So you may be able to unlock the phone but not downgrade it.

[chilango]

So i have to looking for an better FW up to 420 right?
For unlock have to make in my next vacations with these guys in Austria ;)

[suyog]

Just to update, my N9 seems to working again. I am not sure if latest Nokia Link update did something.
Though still it is not perfect as it loses network reception and IMEI many times.
But something is better than nothing.

I am curious to know why this is happening, my N9 just refuses to give up :)

[latency]

I recently flashed my N9 to 1.3 and afterwards Facebook won't function. It starts but I can't see any posts or anything. Does anyone have a clue? I updated to Facebook 1.4.0-1 but it didn't make any difference.

[sagarhowal]

Nokia has closed access to navifirm to download firmwares. How do I get the files for flashing?

[thedead1440]

Nokia has closed access to navifirm to download firmwares. How do I get the files for flashing?

First post clearly states to get firmwares from http://mrcrab.net/nokia.html

[AMLJ]

Hello... I've read a few guides on how to reflash the N9... Unfortunately I still can't due to it being "downgraded". Problem is, I upgraded to the last firmware version just a few days ago, so maybe that's the reason...

root@amljdebian:/home/amlj/Downloads/059H2M6_RM-696 NDT 64GB ROW BLACK# flasher -f -F DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 004, device address 048.
Device identifier: 357923041312887 (SN: N/A)
Found device RM-696, hardware revision 1501
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_340
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 21635 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 004, device address 049.
Device identifier: 357923041312887 (SN: N/A)
Raw data transfer EP found at EP2.
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_40.2012.21-3_PR_001
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 58 %, 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:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1341314263)
[Pipe 0] Finishing in error state with status 10
========================================

ERROR: Failed to flash images


I've tried so many different ones, which seem to be very recent, but it still shows it as a downgrade and doesn't work...

Any idea what I should do?

Thanks in advance.

[pallokallo]

had same problems, just use the same fw that is in the phone

http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0923/7081649972/14991FD9_DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin

http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0923/7081658442/9AD624BD_DFL61_HARMATTAN_40.2012.21-3.340.1_EMMC_340.bin

[AMLJ]

had same problems, just use the same fw that is in the phone

http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0923/7081649972/14991FD9_DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin

http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0923/7081658442/9AD624BD_DFL61_HARMATTAN_40.2012.21-3.340.1_EMMC_340.bin

Thanks! Worked like a charm :3

[PIDk]

Recently I had a very strange problem with my N9.

It suddenly succumbed to reboot loop that I wasn't able to fix with R&D mode.

More interesting is my experience with trying to flash it to break reboot loop:

flasher -f -F main.bin
– doesn't help to break reboot loop

flasher -f -F main.bin -F emmc.bin --flash-only=mmc
– fails with error:
...
bb5_rdc_cert_read failed
...
mmc: Could not exec '/sbin/dosfslabel /tmp/sudmmcXXXXXX/internal0p1 "Nokia N9"'
mmc: Unable to remove mount point '/tmp/sudmmcXXXXXX/mnt/home': No such file or directory
mmc: Could not remove mount directory /tmp/sudmmcXXXXXX/mnt: No such file or directory

flasher -f -F main.bin --erase-user-data=secure
– fails with error:
...
bb5_rdc_cert_read failed
ioctl(BLKSECDISCARD) failed for /tmp/sudmmcXXXXXX/internal0: Input/output error

Flashing with Phoenix or old beta flashers didn't help either.

At last I tried command that I didn't saw in any of the flashing manuals:
flasher -f -F main.bin -F emmc.bin

And yes, it worked like a charm! N9 flashed without errors and reboot loop was fixed!

I don't know why all manuals suggest flashing firmware and emmc in different steps but only flashing them in one step solves errors above and breaks reboot loop.

N.B.: My reboot loop wasn't caused by tweaks. Just one night my N9 turned off due to empty battery (though I remember that it was almost full in the evening) and when I tried to turn it on the following morning (after charging it to maximum) N9 stucked in endless reboot lopp. My assumption is that internal eMMC was damaged somehow. Maybe because some program didn't close properly in the evening, drained all the battery during the night and corrupted eMMC when N9 turned itself off due to empty battery.

[danested]

it would be good if this can be merged with the flashing thread

[khan.orak]

that command is in the Second post of the Comprehensive Flashing thread

[PIDk]

that command is in the Second post of the Comprehensive Flashing thread
Nope. It's a different command - it uses "--erase-user-data" flag. And fails.

[adnankamal9]

Hi all, my N9 (I live in Middle East (Saudi Arabia), Nokia N9, 16GB, Cyan) just got switched off and not booting again. It shows the NOKIA logo and again switches off. Though I am new to flashing but I am trying to flash my N9 so that I can keep using this device as my main phone. Problem I am facing now is from the links given in this thread in the first page to download the firmware for N9 are working and the download (around 2GB) is also starting, but after sometime, it gets stuck up and gives the error as "This download has been interrupted", when I am not even touching my computer. And when I press the resume button, the download starts all over again from the start and again after some download it gives the same error and stops. I really like my N9 and would love to continue using it. Please help.

[adnankamal9]

Hi all, my N9 (I live in Middle East (Saudi Arabia), Nokia N9, 16GB, Cyan) just got switched off and not booting again. It shows the NOKIA logo and again switches off. Though I am new to flashing but I am trying to flash my N9 so that I can keep using this device as my main phone. Problem I am facing now is from the links given in this thread in the first page to download the firmware for N9 are working and the download (around 2GB) is also starting, but after sometime, it gets stuck up and gives the error as "This download has been interrupted", when I am not even touching my computer. And when I press the resume button, the download starts all over again from the start and again after some download it gives the same error and stops. I really like my N9 and would love to continue using it. Please help.

Hello all, I just downloaded successfully the image (around 2 GB), but as told the Navifirm+ is not showing anything, so I am guessing we dont need it now. Anyways, when I unzip the image file which is around 2GB, i get many files in it. I understood that we need only two (2) files starting with DFL61_HARMATTAN. Now where should I keep this to get the flasher to identify these files are supposed to be used for flashing? An urgent reply will be really helpful.

[adnankamal9]

I have reached till this stage, but unable to start the flasher due to the below error ...

[Guyver]

I have reached till this stage, but unable to start the flasher due to the below error ...

type cd C:\Program Files\Nokia\Flasher

to go the specific folder

[minimos]

Sorry for asking the obvious but are you really sure that the device battery is fully charged?
It seems like the device has that little energy to start the booting process but then it runs out of juice and turns itself off.

[adnankamal9]

Sorry for asking the obvious but are you really sure that the device battery is fully charged?
It seems like the device has that little energy to start the booting process but then it runs out of juice and turns itself off.

Ya, before switching off, the device had 85%. but again, i charged it for around 2 hrs for no good. :(

[adnankamal9]

type cd C:\Program Files\Nokia\Flasher

to go the specific folder

Thanks for showing the proper way.
And when i open the flasher -i, it gives the image below, but again as soon as i connect my device, it just identifies the SW version of my phone and flasher window disappears and goes back to command window and nothing happens. :(

[pallokallo]

Thanks for showing the proper way.
And when i open the flasher -i, it gives the image below, but again as soon as i connect my device, it just identifies the SW version of my phone and flasher window disappears and goes back to command window and nothing happens. :(

NOthing wrong there when it goes back to the other screen just enter the flashing commands

[sm0k3]

Hello to all members,what's the best browser for n9(including the built in) in terms of speed and smoothness?
I saw those 2 run pretty well
https://www.youtube.com/watch?v=SqemYmFx6ec
https://www.youtube.com/watch?v=yqCO7J1kbPw

[adnankamal9]

NOthing wrong there when it goes back to the other screen just enter the flashing commands

Hi, I've given the command as shown in Fig.1 and my phone showed something in Fig.2. After this the phone again switches off and nothing happens again. Any idea where I am getting wrong?

[topet2k12001]

There's a video tutorial that I uploaded in YouTube, which is linked in the Wiki Page: http://wiki.maemo.org/Flashing_N9#Tutorial

The video I recorded was for flashing in Linux (i.e. Ubuntu), but they're practically the same as in MS Windows. Only practical difference is in Linux you have to add the word "sudo" at the beginning of each flasher command (just don't type "sudo" when using MS Windows).

[turbovomit]

Hey, navifirmex don't work, unofficial nokia firmware is dead, where can i download the files ????

[thedead1440]

Hey, navifirmex don't work, unofficial nokia firmware is dead, where can i download the files ????

http://skeiron.org/firmware/N9/40.2012.21.3/

[rswelter]

http://skeiron.org/firmware/N9/40.2012.21.3/

someone has been busy, that's a great source.

[brkn]

someone has been busy, that's a great source.

:D
10 chars

[adnankamal9]

Thank you everyone, my N9 is alive again. :) ... Thanks to all who gave help and also to the person who created this Comprehensive Flashing guide.

[minimos]

Thank you everyone, my N9 is alive again. :) ... Thanks to all who gave help and also to the person who created this Comprehensive Flashing guide.
Glad you got your device back to working state but... it could be useful if you can share what was the problem with your initial unsuccessful attempts to reflash.

[adnankamal9]

You got good point minimos.
Well, almost all the links and procedure is correct as given in First post but I did some mistakes as I am new to this thing. I was unaware of the command inputs. Anyways, I made few changes to the commands mentioned in the first post.

I only gave the command for Restore Operating System like
instead of "flasher -f -F main.bin" I gave
"flasher -f main.bin -F -R".

Also, this was not mentioned in the first post. After downloading the main and emmc files, we have to copy these files in the "C:\Program Files\Nokia\Flasher". I didnt knew this and that's why the flasher was not opening.

Hope this will help others to get their devices back alive. :)

[bananas]

My N9 died without any warning, first time i tried to reboot, get stuck in the logo, then, the image was corrupted, reboot it again, but this time no image, so long for 3 or 4 times, then i tought was an flat battery problem, tried the malf state fix, i could never mount the device, then flash it, but never get image back, now im just trying recover my data, my phone has a code, i tried this:


There is a quick way to boot the device to maintanance mode and telnet into it. This would make sure if the problem is indeed the screen or if the device does not boot at all.

Get my MOSLO based maintanance boot from svn repository;
"svn co https://toosa.swagman.org/svn/sillykbd/TRUNK/moslo", and have a look at the README file for details.

If you can telnet to the device you can be sure it's just the screen that is broken.
Also, you can manually export your mmcblk partition via the USB connection to take backup on external PC, if you for example need to send the device for repair.

but, never boots, after i flash the moslo img

this appears in dmesg

[38569.715228] usb 3-1: new high-speed USB device number 20 using xhci_hcd
[38569.738659] usb 3-1: New USB device found, idVendor=0421, idProduct=0105
[38569.738664] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[38569.738667] usb 3-1: Product: N9 (Update mode)
[38569.738669] usb 3-1: Manufacturer: Nokia
[38569.738672] usb 3-1: SerialNumber: 357923049514963
[38570.162778] usb 3-1: USB disconnect, device number 20


what can i do?

sorry for my english

im love this phone, never felt this way before about a phone, i dont need android, i want this phone for ever, i bought another and im planning get a third one (used) for parts.

[maxdroid]

I got the alternative os Android at startup aswell as maego (I can choose either one at startup using the volume key to fit the android picture above or maego below).

I'm gonna send back phone for repairs on warranty so I wonder if I only need to reflash to my country version and the phone will be in it's original state even though I got dual boot, or if I need to do something else.

I presume all information will be deleted in this process aswell?
/maxxy

[Pratyush]

Hi Guys, Got my N9 from ebay - worked very well on day 1. Now its dead. When I charge the Nokia logo shows up and then the battery sign with the exclamation mark. Thats it.

I thought it was a battery problem - so I downloaded the latest firmware and tried to charge the battery through flasher.

The Battery says - its a 100%.And the flasher gave me a message saying "Downgrade Not Allowed"

Checked the firmware through flasher -i and I get DFL61_HARMATTAN_40.2012.21-3.335.1_PR_335

I have tried the Chinese Firmware and the 001 firmware so far - Both gave me the same errors.

I have tried these 2 firmwares:
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_003-OEM1-958_ARM

Any help trying to revive my N9?

P.S. : I was trying to get my contacts through Bluetooth to N9 when the phone went kaput

[Newby]

Hi there,

I thought I did a "successful" firmware flash on my phone but the screen STAYS BLANK when I start it up.. any ideas?

Current status:

1. I made sure to re-imaged with the correct bin corresponding to my phone model (059K114)

2. Power = 70% (according to what flasher says when I re-image)

3. I have tried enabling rd mode - no change - the LED light blinks like mad initially then changes rates over time so "something" is happening.. :rolleyes:

4. it doesn't do that quick vibration like it used too when i turn it on..

I've tried my best to search for another option BEFORE posting but I've run out of options.. THANKS in advance!

[Pratyush]

Hi Guys,

I am now at a total loss how to resolve this.

I received the phone a couple days back. I was using it normally when it suddenly stopped.

I found out the Firmware in my phone to be:
DFL61_HARMATTAN_40.2012.21-3.335.1_PR_335

I downloaded the firmware from the links and started the flashing - nothing works. I get interrupted between 37-44% . I have tried the cold flash as well - does the same thing.

The error I am getting is this:
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 19975 ms
ERROR: WriteFile(0 of 14) timeout (5000 ms); tried 14

Fetching error list:
ERROR: WriteFile(0 of 28) timeout (5000 ms); tried 28
ERROR: WriteFile(0 of 10) timeout (5000 ms); tried 10



Here is the complete log:


f:\Program Files\Nokia\Flasher>flasher -f -F main_335.bin -c
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
Suitable USB interface (bootrom) not found, waiting...
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 45
96 2a 39 6d 33 aa 70 ed 58 07 b3 a7 79 0c a1 bb
90 4d 66 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
ERROR: ReadFile error 31
usb_bulk_read: No error
Got HWID: RM-696:1603
Suitable USB interface (bootrom) not found, waiting...
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 45
96 2a 39 6d 33 aa 70 ed 58 07 b3 a7 79 0c a1 bb
90 4d 66 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 (7273728 bytes)... done.
Suitable USB interface (bootloader/phonet) not found, waiting...
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_40.2012.21-3.335.1_PR_335
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 100 %, 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 ]
[_] cmt-mcusw [finishing 0 % 6050 / 6050 kB 2866 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 2209 kB/s]
[_] rootfs [writing 41 % 409600 / 979170 kB 8997 kB/s]
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 19975 ms
ERROR: WriteFile(0 of 14) timeout (5000 ms); tried 14

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 2866 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 2209 kB/s]
[f] rootfs [writing 0 % 409600 / 979170 kB 8997 kB/s]
Fetching error list:
ERROR: WriteFile(0 of 28) timeout (5000 ms); tried 28
ERROR: WriteFile(0 of 10) timeout (5000 ms); tried 10

ERROR: Failed to flash images
------------------------------------------------------------------------------------
I
Please can anyone help. If it helps I got the phone off ebay and it has 059M7K1 in the Sim tray.

[joerg_rw]

DO NOT COLDFLASH when your device does not need it!
Coldflashing is solely to restore a broken bootloader, and obviously your bootloader isn't broken since it boot up to display stuff on screen and even starts flashing procedure. If it was broken then your device would act _really_ bricked and not show any sign of life (except BOOTROM "hello" via USB, that gets detected by flasher). ONLY THEN you should consider coldflashing - after you made sure it's not your battery that's defect.

It's not like coldflashing could do massive harm to your device since you can repeat it under nearly all circumstances (unlike flashing BIOS of your PC, which might render your motherboard bricked when you abort it), but definitely it won't usually fix anything for you, and just may introduce another level of failure cause that complicates things even further.

on the errors you encounter: try a better USB cable and a different port on your PC, those errors *might* be simple data corruption on USB protocol.

/j

[Pratyush]

DO NOT COLDFLASH when your device does not need it!
Coldflashing is solely to restore a broken bootloader, and obviously your bootloader isn't broken since it boot up to display stuff on screen and even starts flashing procedure. If it was broken then your device would act _really_ bricked and not show any sign of life (except BOOTROM "hello" via USB, that gets detected by flasher). ONLY THEN you should consider coldflashing - after you made sure it's not your battery that's defect.

It's not like coldflashing could do massive harm to your device since you can repeat it under nearly all circumstances (unlike flashing BIOS of your PC, which might render your motherboard bricked when you abort it), but definitely it won't usually fix anything for you, and just may introduce another level of failure cause that complicates things even further.

on the errors you encounter: try a better USB cable and a different port on your PC, those errors *might* be simple data corruption on USB protocol.

/j

ok I have changed the USB Cable - I have tried 2 different computers. But I have the same problem. Any other ideas?

[Pratyush]

ok I have changed the USB Cable - I have tried 2 different computers. But I have the same problem. Any other ideas?

Do I have any choice guys? Please respond.

Should I take this to Nokia Care? I would be charged for this but I am ok with it, as long as they fix it.

[suyog]

Do I have any choice guys? Please respond.

Should I take this to Nokia Care? I would be charged for this but I am ok with it, as long as they fix it.

Are you from India?
DO NOT take N9 to Nokia care, many nokia care guys hardly have any idea about N9. They will tell very high service charge and will not be confident of fixing it.

[Williz]

Could someone possibly help me?

I'm unable to flash to UK or Aus or Denmark FW 001, 299 or 340 variants.

Here is my log attached:

C:\Program Files\Nokia\Flasher>flasher -f -F14991FD9_DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_LEGACY_340_ARM_RM-696_PRD_signed.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 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.299.1_PR_299
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 19354 kB/s)
Suitable USB interface (phonet) not found, waiting...
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_40.2012.21-3.340.04.1_PR_340
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 21 %, 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:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1342067459)
[Pipe 0] Finishing in error state with status 10
========================================

Phone is just bootlooping now... Any assistance is greatly welcomed!

[Williz]

Nevermind! Was being stupid / dyslexic and had downloaded 249 variant. Managed to flash fine with 299

[unoace]

Whenever I plus in my n9 it always comes on, how can I reflash like this? It comes on and stays at the Nokia screen.

[mcbook]

This is weird!

I did a secure erase on my second N9 just now and during tbe first setup process (where you set time, date, language....) the device remembered my nokia account user name!!!!

whats secure about that??

[thedead1440]

press the power button for 8-10seconds before plugging into usb port for the n9 to be powered off...

[unoace]

Yes I got it, I'm trying to see if its the death by batter drain issue before flashing, I hope it is lol

edit: nevermind **** is bricked.

[Pratyush]

Are you from India?
DO NOT take N9 to Nokia care, many nokia care guys hardly have any idea about N9. They will tell very high service charge and will not be confident of fixing it.

With no help arriving here I had no option but to give it to Nokia Care. And as you said, they have no clue how to fix it. In fact so much so that they entered the model as N900 in the system as N9 does not even reflect in their system.

Its been a week and they have told me if to wait till Monday. I guess my only option now is to return the item to Hong Kong and 'hope' the seller sends me a new one.

[suyog]

This is weird!

I did a secure erase on my second N9 just now and during tbe first setup process (where you set time, date, language....) the device remembered my nokia account user name!!!!

whats secure about that??

This is not issue of secure erase but the way nokia account works.
It is same with other nokia phones, symbian and even some Ashas.

Nokia account is tied to your number. So if you put SIM while flashing and it switches on, it connects to nokia servers and knows which account that number is associated. Hence it asks you to enter password of that account.
So it is not that some data was left after secure flashing.

[suyog]

With no help arriving here I had no option but to give it to Nokia Care. And as you said, they have no clue how to fix it. In fact so much so that they entered the model as N900 in the system as N9 does not even reflect in their system.

Its been a week and they have told me if to wait till Monday. I guess my only option now is to return the item to Hong Kong and 'hope' the seller sends me a new one.

Yes, and please get your phone back from nokia care as soon as possible before they break(physically)
I had very bad experience and just wanted to warn you.

[STRANG3R]

i have a NOKIA N9 White 64gb CHINA PR 1.3.

i live in INDIA Can I INSTALL Firmware Of PR 1.3 INDIA ??

OR ANY OTHER BATTER VERSION WITHOUT BRICKING IT ?

THERE IS INFO ABOUT ONLY PR 1.1 ON 1ST PAGE.

:)

[suyog]

If your chinese fw version number < indian fw then you can do it.
1st page guide is generic , not only specific to PR1.1

From back of your N9 SIM tray you should be able to find product code.
Then go to this link http://mrcrab.net/NokiaProductCode/Nokia_N9.html?productType=RM-696

and find which fw your phone has.

[Pratyush]

Yes, and please get your phone back from nokia care as soon as possible before they break(physically)
I had very bad experience and just wanted to warn you.

Hey Suyog, git this back and as expected these guys imparted a couple of scratches on it.

Here is the interesting part now:

Was almost ready to ship it back to the seller when I decided to give this another go. COnnected to a pc and started flasher. The battery was down to 5% so it kept charging. It reached 10% and it started the flash.

Viola - In about 2 minutes the flashing competed. However the CMT is still not flahsed which meant SIM functions wont work.

The took another firmware and only flashed the CMT. Here is my Nokia N9 now - working !!!

This is the config:
1, Hardware: China
2. CMT: China
3. OS: PR 1.3 But has a region code of 335 (checked it belongs to Middle East)

Is there a way to flash it to global or Indian version? Or should I play very safe and dont try to kill it.

[suyog]

Hey Suyog, git this back and as expected these guys imparted a couple of scratches on it.

Here is the interesting part now:

Was almost ready to ship it back to the seller when I decided to give this another go. COnnected to a pc and started flasher. The battery was down to 5% so it kept charging. It reached 10% and it started the flash.

Viola - In about 2 minutes the flashing competed. However the CMT is still not flahsed which meant SIM functions wont work.

The took another firmware and only flashed the CMT. Here is my Nokia N9 now - working !!!

This is the config:
1, Hardware: China
2. CMT: China
3. OS: PR 1.3 But has a region code of 335 (checked it belongs to Middle East)

Is there a way to flash it to global or Indian version? Or should I play very safe and dont try to kill it.

Pratyush, Great news. As I expected Nokia care guys in india are clueless about N9. They think it is Lumia 800 :)
What they told you? How much they charged for putting scratches?
Let me know which is product code on sim tray?
And which one you flashed now?

if everything is working fine, DO NOT bother to flash again as you wont get anything different by flashing Indian fw.
Is seller ready to refund you if you send back device?
If yes then do it quickly as many N9s seems to having this issue.
else try to sell it locally via olx or quickr. Try to get good money.

I will always suggest to buy from middle east and I feel these hong kong based sellers are selling chinese operator based N9 somehow. Hence you cant be sure if SIM related issues come again.

[mofazar]

Hi guys! I try to flash my N9 death but nothing works.
I put the control (flash-i ") it says that the current version (DFL61_HARMATTAN_40.2012.21-3.339.2_PR_339) and when I try to flash with (FB2CF12A_DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_009-OEM1-958_ARM.bin) it says (downgrade disallowed) at the end. I start to panic because I do not know what to do. Help me please.

[LinuxCub]

[mofazar] What kind of weird thinking (or not) lead you to try flashing with DFL61_HARMATTAN_30.2012.07-1_PR_LEGACY_009-OEM1-958 ?

(trying to teach fishing here, instead of giving fish ...)

[mofazar]

I'm sorry, in fact I try to flash with (DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin) and this is where he says (downgrade disallowed)

[mofazar]

what must i do, please (Linux Cub)

[mofazar]

I'm stuck squarely guys :(

[mofazar]

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_40.2012.21-3.339.2_PR_339
Success

C:\Program Files\Nokia\Flasher>flasher -f -F main.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 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.339.2_PR_339
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 20275 kB/s)
Suitable USB interface (phonet) not found, waiting...
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_40.2012.21-3_PR_005
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 81 %, 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:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1341314349)
[Pipe 0] Finishing in error state with status 10
========================================

ERROR: Failed to flash images

Trying to flash with (DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_003-OEM1-958_ARM.bin)
Help me please! :(

[minimos]

what must i do, please (Linux Cub)
You should read carefully the first post of this thread, and possibly the following discussion, because your exact issue is expained there.
At very least do a search for "downgrade disallowed". The results should explain you the causes.

[mofazar]

thanks guys. problem fixed

[Pratyush]

Pratyush, Great news. As I expected Nokia care guys in india are clueless about N9. They think it is Lumia 800 :)
What they told you? How much they charged for putting scratches?
Let me know which is product code on sim tray?
And which one you flashed now?

if everything is working fine, DO NOT bother to flash again as you wont get anything different by flashing Indian fw.
Is seller ready to refund you if you send back device?
If yes then do it quickly as many N9s seems to having this issue.
else try to sell it locally via olx or quickr. Try to get good money.

I will always suggest to buy from middle east and I feel these hong kong based sellers are selling chinese operator based N9 somehow. Hence you cant be sure if SIM related issues come again.


Hey Sorry for getting back late on this.

Nokia Care (and I believe it was a pretty bad one to choose) charged me 100 bucks to 'inspect' nothing else. I have told this to the seller that it works and they say there is no point of shipping it back. I kind of agree. There is absolutely no surety that the money would be refunded or they will send another phone (they gave me this option before) as the payment was processed outside of Paypal and does not come under Ebay guarantee.

So here is my take on this- would keep using it, hope it lasts about a year. Its a fabulous phone and it's rather sad to see Nokia not manufacturing Meego/Meemo based phones.


There is a trip scheduled to US later this year, hope to pick another phone from Amazon (should be better).

[nokiabot]

in phones with embeded battries you need to disconect battery and try again it works 99% time and also uninstall device via device manager in windows (left click on my computer then select properties ) and connect again:)

[suyog]

in phones with embeded battries you need to disconect battery and try again it works 99% time and also uninstall device via device manager in windows (left click on my computer then select properties ) and connect again:)

For which issues , this solution works? SIM Error also?

[suyog]

@Pratyush , That is fair enough I guess, N9 is brilliant phone and most people think same as you except may be 2 Steves :) ( Ballmer and Elop)
Let me know if you are planning any trip to Poland :)

[subhash.yadav]

The dreaded SIM card error has caught my N9 too. I have read many posts on this forum and other Meego forums to no avail.

The latest on the saga is that I keep getting PIN code requests (SIM card PIN) every now and then. When that is provided, the carrier network is detected for a brief period before the SIM card error is displayed again. I must add that the last --flash-only=cmt worked and showed success!

I've tried flashing numerous times and I am not sure what could be going wrong here. Its a unlocked N9 64 GB, product code 059J228 (Middle East version, I believe!).

Any help much appreciated.

[suyog]

The dreaded SIM card error has caught my N9 too. I have read many posts on this forum and other Meego forums to no avail.

The latest on the saga is that I keep getting PIN code requests (SIM card PIN) every now and then. When that is provided, the carrier network is detected for a brief period before the SIM card error is displayed again. I must add that the last --flash-only=cmt worked and showed success!

I've tried flashing numerous times and I am not sure what could be going wrong here. Its a unlocked N9 64 GB, product code 059J228 (Middle East version, I believe!).

Any help much appreciated.

Did you try zerorize and flash again?
Sometimes I feel Nokia might have pulled some type of kill switch :) to kill N9s.
So many people faced this issue and we still don't know reason. Why and how it happens suddenly?
I tried checking SIM tray mechanism by opening N9 but that also didnt help. I have given up :(

[subhash.yadav]

Did you try zerorize and flash again?
Sometimes I feel Nokia might have pulled some type of kill switch :) to kill N9s.
So many people faced this issue and we still don't know reason. Why and how it happens suddenly?
I tried checking SIM tray mechanism by opening N9 but that also didnt help. I have given up :(

Hi Suyog,

here is the log for the last flash attempt. Everything seems to be alright. The cmt module flashed correctly too. As far as I've gathered, it isn't a hardware problem.

C:\Program Files\Nokia\Flasher>flasher.exe -f -F main.bin -F emmc.bin --erase-us
er-data=secure -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.

Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 23734 kB/s)
Suitable USB interface (phonet) not found, waiting...
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 82 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_006
Image moslo not present
Image tar skipped
Image config skipped

Battery level 82 %, 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 2906 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 1811 kB/s]
[x] rootfs [finished 100 % 978983 / 978983 kB 10479 kB/s]
[x] mmc [finished 100 % 1829147 / 1829147 kB 13691 kB/s]
Updating SW release
Success

[suyog]

Did you try different SIM?
Also try to put thin paper below SIM in SIM tray and check.

[subhash.yadav]

Did you try different SIM?
Also try to put thin paper below SIM in SIM tray and check.

At first when the phone went kaput I thought the SIM card tray went bust! I ordered for a new one but that ofcourse wasn;t the problem. I also tried the thin paper method. I've tried other SIMs too, no luck. Only that the SIMs that I've tried were cut to Micro-SIM size and not the ones that came from the carrier.
I'm trying wifey's SIM card now, her's is a carrier provided one. Lets see.

[subhash.yadav]

Did you try different SIM?
Also try to put thin paper below SIM in SIM tray and check.

I'll try the thin paper method once again. Wifey's SIM behaves exactly the same as mine. The network appears for a brief period and then vanishes into thin air making me miserable as hell!

[suyog]

I'll try the thin paper method once again. Wifey's SIM behaves exactly the same as mine. The network appears for a brief period and then vanishes into thin air making me miserable as hell!

Ohh, hard luck then ! Exactly same thing I have here.
Network appears for few seconds and then goes off.
Can you see IMEI number after networks goes away?

[subhash.yadav]

Ohh, hard luck then ! Exactly same thing I have here.
Network appears for few seconds and then goes off.
Can you see IMEI number after networks goes away?

That's the funny bit in my case. I can see the IMEI number when the network goes away but again only for a brief period. After that it goes off again! On and off. I think I may have mixed up flashing different versions (most likely India version). Today I will try flashing the cmt only for the India version and then do a full flash with the German version or any version higher than the India one. Fingers crossed!

[ydereky]

After trying every tutorial and forum thread I can find, I will admit that I now need to ask for help.

N9: Singapore Black 16 GB (059J246)

I received it new when the phone was first released. We used it for a day loaded up some software, then tried to wipe it to bring it back to factory clean after we ran into a problem. It never came back up. That was a while ago and I don't remember the details. I had other new phones at the time and was traveling, so we didn't get the phone fixed. The phone now gets caught in a loop of Nokia screen / reboot.

Since then I've tried various things from this discussion board and elsewhere. Here's where we are now:

When I try to flash the device using the Navifirm downloaded images for the variant on Flasher 3.12.1 on both Mac, PC and Linux, here's the output:

flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 253, device address 4.
Device serial number is N/A
Found device RM-696, hardware revision 1507
NOLO version 2.1.5
Version of 'sw-release': DFL61_HARMATTAN_20.2011.40-4_PR_005
Sending ape-algo image (7032 kB)...
100% (7032 of 7032 kB, avg. 27906 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 253, device address 4.
Device serial number is
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.6.3
Found product RM-696 rev. 1507
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_20.2011.40-4_PR_005
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped
Charging battery, 10 % battery level (11 % required). Ctrl-c to exit
Battery level 11 %, 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 ]
[_] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3005 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 93 / 93 kB NA ]
[x] kernel [finished 100 % 2712 / 2712 kB 1967 kB/s]
[_] rootfs [finishing 100 % 32768 / 1102546 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 ]
[_] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3005 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 93 / 93 kB NA ]
[x] kernel [finished 100 % 2712 / 2712 kB 1967 kB/s]
[f] rootfs [finishing 0 % 32768 / 1102546 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 ]
[f] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3005 kB/s]
[x] xloader [finished 100 % 23 / 23 kB NA ]
[x] secondary [finished 100 % 93 / 93 kB NA ]
[x] kernel [finished 100 % 2712 / 2712 kB 1967 kB/s]
[f] rootfs [finishing 0 % 32768 / 1102546 kB NA ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: sfdisk returned status 1
mmc: Could not exec 'tune2fs -L rootfs /tmp/sudmmcSPkpss/internal0p2'
mmc: Could not remove mount directory /tmp/sudmmcSPkpss/mnt: No such file or directory
[Pipe 4] Finishing in error state with status 1
MTC_NOS_READY not received
MTC_NOS_READY not received
MTC_NOS_READY not received
CMT RFS failed
[Pipe 7] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

Where should I go from here? What answers can I provide to hopefully find a fix?

[suyog]

@Subhash

I will suggest following.
1) Flash original fw. (of product code below SIM tray)
2) Then try mix and match of main and cmt. Try not to use higher versions. North Europe seems good.
3) DO NOT try chinese or operator locked fw unless you have exhausted all other options.
4) Try to send it to country of origin and get it fixed if it is still in warranty.

Keep us posted about your progress :)

[subhash.yadav]

@Subhash

I will suggest following.
1) Flash original fw. (of product code below SIM tray)
2) Then try mix and match of main and cmt. Try not to use higher versions. North Europe seems good.
3) DO NOT try chinese or operator locked fw unless you have exhausted all other options.
4) Try to send it to country of origin and get it fixed if it is still in warranty.

Keep us posted about your progress :)

@Suyog, I think I've given up now! I do not know the consequences of flashing a Chinese FW (guess they are disastrous!). I think I'm just going to keep this as a navigation device.
Look at the bright side, its time for a new phone ;)

[suyog]

Ok, which one you are going to buy next? I bought 808 and then now Xperia ZR.
Also check your N9 after few days by putting SIM in, in my case it works sometimes :) for 1-2 days before starting same issue again.

[subhash.yadav]

Ok, which one you are going to buy next? I bought 808 and then now Xperia ZR.
Also check your N9 after few days by putting SIM in, in my case it works sometimes :) for 1-2 days before starting same issue again.

Yeah, will try the N9 is a few days again. Until such time a basic handset will do duty. I'm not certain what to get next. The N9 has spoiled me :-P! I am thinking the Nexus 4 should be a nice option, there are some sweet deals on ebay.
Any particular reason why you bought the 808? Let me guess, photography!

Sorry about the OT, folks!

[metRo_]

Will it work with n950?

[Mikkosssss]

Will it work with n950?

How you have N950 if you dont know this?

But yes you can flash it, but you need other firmware for N950 not N9 one.

[sandy_locke]

Hi, I have an issue flashing, and I didn't find the right answer anywhere on the web.

First I have a product code 059L8L7 nowhere to be found. Anyway, I tried with several firmware 40.2012.21-3.313 which are the latest: france, germany, row and Mobitel telekomunikacijske (the nearest to my product code).

Everytime I get "Downgrade not allowed", but the variants used with those firmwares are 001, 005 and 009.

I don't know what to do next. I'm downloading the Australian firmware and one that I found on thread which worked for the OP who had the same issue. I will see if it work. But in the meantime, I'm asking here for help as I truely don't believe it will work !

The issue here is that my phone is in a reboot loop. The solution to mount the N9 on desktop with flasher doesn't work. It would have allowed me to put back the original system files. Now every boot present itself with the Nokia warranty warning, but it's normal as I understood.

So my only option is to flash the device, and it still doesn't work. I struggle finding the good firmware, so I ask you for advices.

In the hope there is a happy solution to all this ^^

BTW: I was attempting a zeroize of the device, so all data are already erased. Now my only possibility is a flash.

[lorenzo]

--flash-only=ARG
what are the possible ARGs? eg i edied wrong a file in /usr/share/themes/base/meegotouch so i just need to reinstall base theme, is this possible? how? thanks

[juiceme]

Hi, I have an issue flashing, and I didn't find the right answer anywhere on the web.

First I have a product code 059L8L7 nowhere to be found.

According to NaviFirm 059L8L7 is the "Swisscom CH Cyan 10G" variant. For some reason the latest firmware for it is 20.2011.40.4 which is fairly odd. Maybe Nokia thinks that Swiss do not deserve newer than PR1.1 releases?

What is the original Swisscom variant firmware you have on the device, is it later than the PR1.1?

Anyway, I tried with several firmware 40.2012.21-3.313 which are the latest: france, germany, row and Mobitel telekomunikacijske (the nearest to my product code).

Everytime I get "Downgrade not allowed", but the variants used with those firmwares are 001, 005 and 009.

I don't know what to do next. I'm downloading the Australian firmware and one that I found on thread which worked for the OP who had the same issue. I will see if it work. But in the meantime, I'm asking here for help as I truely don't believe it will work !

The issue here is that my phone is in a reboot loop. The solution to mount the N9 on desktop with flasher doesn't work. It would have allowed me to put back the original system files. Now every boot present itself with the Nokia warranty warning, but it's normal as I understood.

So my only option is to flash the device, and it still doesn't work. I struggle finding the good firmware, so I ask you for advices.

In the hope there is a happy solution to all this ^^

BTW: I was attempting a zeroize of the device, so all data are already erased. Now my only possibility is a flash.

[sandy_locke]

According to NaviFirm 059L8L7 is the "Swisscom CH Cyan 10G" variant. For some reason the latest firmware for it is 20.2011.40.4 which is fairly odd. Maybe Nokia thinks that Swiss do not deserve newer than PR1.1 releases?

What is the original Swisscom variant firmware you have on the device, is it later than the PR1.1?

Yes, the firmware I have on the device is PR1.3, updated OTA. You know, that was exactly what I was afraid of: the firmware deployed onto my firmware variant has not been released by Nokia through Navifirm and I wont be able to flash the device... Still hope I'm wrong, though!

You think there's a solution for that ?

EDIT: I read that a flasher program called Phœnix could have a better chance to flash without this kind of issue. What about it ?

[suyog]

Yeah, will try the N9 is a few days again. Until such time a basic handset will do duty. I'm not certain what to get next. The N9 has spoiled me :-P! I am thinking the Nexus 4 should be a nice option, there are some sweet deals on ebay.
Any particular reason why you bought the 808? Let me guess, photography!

Sorry about the OT, folks!

Nexus or such so called pure google phones are overhyped and crippled hardwares compared to other flagship phones by same manufacturers. Better to buy Samsung, Sony or HTC flagship phone.
I always feel customizations which these manufacturers add over stock android are useful and hardware is always better.
I got Sony Xperia ZR and happy with it, sold 808 after 8 months.

[minimos]

--flash-only=ARG
what are the possible ARGs? eg i edied wrong a file in /usr/share/themes/base/meegotouch so i just need to reinstall base theme, is this possible? how? thanks
Nope, you cannot flash only one file.
Here are the options you can pass to the flash-only parameter:
$ ./flasher --flash-only=help
flasher 3.12.1 (Oct 5 2011) Harmattan
ERROR: Valid --flash-only options: nolo,kernel,moslo,initfs,rootfs,cmt,mmc,tar
ERROR: Error processing option

[juiceme]

EDIT: I read that a flasher program called Phœnix could have a better chance to flash without this kind of issue. What about it ?

I am rather unfamiliar with Phoenix since it's only running under Windows, but I am fairly sure it will not help you any further than the command line flasher.

Flashing on N9 depends on the counterpart running on the device itself, the method to feed data to it from outside source does not affect the process.

[Bernard]

Excellent guide!!

I recently got a second N9 from eBay and used these instructions to change the Chinese firmware to the Australian one with Benelux map-data.
Works perfectly, thank you all very much!

[sandy_locke]

I am rather unfamiliar with Phoenix since it's only running under Windows, but I am fairly sure it will not help you any further than the command line flasher.

Flashing on N9 depends on the counterpart running on the device itself, the method to feed data to it from outside source does not affect the process.

Ok, thx juiceme.

Should I have any hope of finding a solution, then ??

[Bernard]

Hi, I have an issue flashing, and I didn't find the right answer anywhere on the web.

First I have a product code 059L8L7 nowhere to be found. Anyway, I tried with several firmware 40.2012.21-3.313 which are the latest: france, germany, row and Mobitel telekomunikacijske (the nearest to my product code).


http://www.mrcrab.net/Nokia-Product-Code.html?ProductCode=059L8L7
Does show a 40.2012.21.3 version for that product code.

[sandy_locke]

http://www.mrcrab.net/Nokia-Product-Code.html?ProductCode=059L8L7
Does show a 40.2012.21.3 version for that product code.

You know that you saved my day(s) ? Thank you so much for finding me the right firmware, I'm now ready for a good OpenMode and the ensuing pleasures :D

[STRANG3R]

i have nokia n9 64gb SW VER PR1.3 40.2012.21-3_PR_003
ProductCode=059K164 China
http://www.mrcrab.net/Nokia-Product-Code.html?ProductCode=059K164

CAN I INSTALL SAME VERSION WITH INDIA COUNTRY ???
THIS http://www.mrcrab.net/nokia/Nokia_N9.html?productType=RM-696&releaseID=7048842309&variantID=7076921652&productCode=059M5Q5&version=40.2012.21.3

can i use phoenix as i have used that on my N8 many times ?

[Bernard]

Yes, you can most likely install the Indian firmware on your Chinese N9.
Just read the first post completely before proceeding.

Don't know anything about phoenix, I would advise you to use the flasher and instructions form the first post.

[MarcAnton]

@STRANG3R
"can i use phoenix as i have used that on my N8 many times ? "

I used Phoenix to flash my N9 two times (knew it also from flashing the N8 before) and it worked fine. If you did it with your N8, you know how it works, so there should be no problem.

[STRANG3R]

@STRANG3R
"can i use phoenix as i have used that on my N8 many times ? "

I used Phoenix to flash my N9 two times (knew it also from flashing the N8 before) and it worked fine. If you did it with your N8, you know how it works, so there should be no problem.

thanx mate will try & reply

[raider-R150]

hello guys i just want to ask, I have nokia n9 64GB black and I successfully reflashed it. Now , I have nokia n9 64GB white, can I use the same image for both device? Can I use the one I'm using on black to my white n9? I need help thanks in advance

[juiceme]

hello guys i just want to ask, I have nokia n9 64GB black and I successfully reflashed it. Now , I have nokia n9 64GB white, can I use the same image for both device? Can I use the one I'm using on black to my white n9? I need help thanks in advance

Yes, the images for all colours are the same even as they are in different menus on NaviFirmEx. (as long as the country variant is same, of course...)
Even the images for 16G and 64G devices are the same.

disclaimer: I know this for a fact on the North European images and I strongly belive that same holds for other country variants too but of course I cannot guarantee it...

[raider-R150]

Yes, the images for all colours are the same even as they are in different menus on NaviFirmEx. (as long as the country variant is same, of course...)
Even the images for 16G and 64G devices are the same.

disclaimer: I know this for a fact on the North European images and I strongly belive that same holds for other country variants too but of course I cannot guarantee it...

Thanks. Well I think I need more survey because you said that you cannot guarantee. I am from philippines , the product code for my black 64GB is 059J232, and for my white is 059N1D5. They are both from Philippines. Do you think I would not have a problem with that? Does anyone here tried already this? Thanks

[raider-R150]

Yes, the images for all colours are the same even as they are in different menus on NaviFirmEx. (as long as the country variant is same, of course...)
Even the images for 16G and 64G devices are the same.

disclaimer: I know this for a fact on the North European images and I strongly belive that same holds for other country variants too but of course I cannot guarantee it...

I had the image of my black 64GB. I saved it and I used it everytime I need to reflash my phone. I wanted to get the image of the white one on the navifirm+ but I think nokia locked it coz I always got this error "service specific exception:com.nokia.caresuit.webservice.Unauthoriz edFault"

[raider-R150]

hello guys check this out

http://www.mrcrab.net/Nokia-Product-Code.html?ProductCode=059J232
this is for the black

http://www.mrcrab.net/Nokia-Product-Code.html?ProductCode=059N1D5
this is for the white.

Do you think this site is ok? and by the way , how may I know the variant ID? where can I find it? I only now the product code

[juiceme]

Both of your devices point to the same set of files on NaviFirm:

http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0312/7076665785/A6D5F456_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_005-OEM1-958_ARM.bin

http://nds2.fds-fire.nokia.com/p/d/fds_fire/1207/0312/7076666921/59BEC3BC_DFL61_HARMATTAN_40.2012.13-7.SEAP_EMMC_SEAP.bin

[STRANG3R]

@ALL
Successfully Flashed Hongkong N9 64gb.
To INDIA version FW.
then i have downloaded original Files also to flash cmt of Hongkong because it cant detect sim if you have INDIAN FW :)
INSTALLED NITDROID 5 Also.

[unfuccwittable]

Flashed my phone to get out of a frakking reboot loop, only for the phone to no longer open the messaging app. Brand new phone, too. So sick of this phone.

[STRANG3R]

Flashed my phone to get out of a frakking reboot loop, only for the phone to no longer open the messaging app. Brand new phone, too. So sick of this phone.

Try Reset Phone.
BackUp ur data 1st.

[unfuccwittable]

Thanks, but I tried that twice already. I got a white Lumia 1020 today that I'm gonna play with until the first Jolla phone arrives. I may sell my two white N9s though.

[rahulvala]

while flashing my dead N9 , I got this error, can anyone help me

[minimos]

Your screenshot is pretty much unreadable, and you haven't even cared to explained how you got to that situation (which original firmware, what image you flashed and all that jazz).
Anyhow, the solution is probably in included in the thread http://talk.maemo.org/showthread.php?t=82693 so start reading from there.

[Suresh kumar]

I Have Serious Prblm Wit My N9
Wen i Use net If I attend Any Call After Tht Phone stops Wrkng doesn't open Any App It Takes To Long Time N I should Reboot Every Time
Plz Give Me Any Solution fr ths

[Mikkosssss]

If you cant give any info you should just reflash.

http://talk.maemo.org/showthread.php?t=82693

[Suresh kumar]

Wat Info i Should Say

[TonyUkuk]

Hi guys.

At last, after 5 or 6 ( no sleep no eat :D ) hardly days workings, testings and lookings for, i just found the way to solve the problem with Nokia N9 cmt problem during flashing.

Yea,till it i red many post from many forums from nice guys :) Thank you at all!!!

So lets begin. I'll tell you just the way with which one i solved it - in most situations this problem with cmt happening with chines versions of Nokia N9 (ofcourse brand:)), that why. If any questions feel free to ask.

(I do all these in Ubuntu 12.04) Steps:
1) Go here (http://smartdevays.ru/official_nokia/4234-originalnaya-proshivka-dlya-nokia-n9-rm-696.html) (prefer with Chrome browser to translate to english,cause site in russian)

2) Go to the section For any "gray" smartphones and download one firmware file and one content(emmc) file (i prefer to download just firmware file,no need to flash emmc,but if you want and have a time and patienсе download and flash also emmc). Save this (them if u decide to flash firmware and emmc) somewhere in the folders of /home/user/. In my option this folder was Downloads (I prefer to clean the folder before putting there the flashing files.

3) I prefer...no, I INSISTENLY prefer to have flash operations on computers with LINUX OS. If You cant, so just find someone who using Linux distributins :) Maann))
You must install flasher.3.12....deb.
here (http://tablets-dev.nokia.com/maemo-dev-env-downloads.php) you can download it. But something get wrong during downloads, i think tablets-dev site went down,never mind - if problems, then click to the file at the end of this post, download and install it.


4) So, after steps 1 and 2, do these:
a)make sure that phone is FULLY charged
b)make sure that you did step a) and detach your Nokia N9 from all connections - charging, usb.. just put your phone back.
c)open terminal, type
sudo su
If live-cd no need, if installed OS then type your superuser password and then type this
flasher -F TheFirmwareWhichYouDownloadedByStepTwo.bin --flash-only=cmt -f -R

5) If success Your log must be like that
root@aceraspire4935g:/home/penryn/Загрузки# flasher -F D2C89BF2_DFL61_HARMATTAN_40.2012.21-3.418.2_PR_LEGACY_418_ARM_RM-696_PRD_signed.bin --flash-only=cmt -f
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 002, device address 033.
Device identifier IMEIIMEIIMEIIME (SN: N/A)
Raw data transfer EP found at EP2.
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_40.2012.21-3.418.2_PR_418
Image cert-sw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 95 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[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 3087 kB/s]
Success
root@aceraspire4935g:/home/penryn/Загрузки# flasher -R
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 002, device address 033.
Device identifier: IMEIIMEIIMEIIME (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Success

If no success, just put here output, let us to see. In 99% if no success, then we will try download another firmware - if need, we will download one by one firmwares (in this time here (http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696) and try it again))) funny, but it will work 100% at last!

6) So after succes, just type
flasher -R
and wait - device will reboot and boots to OS. Yo will see that your network come back, you will be able type *#06# and get output. Your about product section will work fine and will shows IMEI and at last, you'll see that OS working fine, no have frozens, no have hitting, so no need to flash firmware!!! - by the way, I see that, after error cmt, the device top (wher the processor with flash) hitting very vell :) after this success,all getting fine.

This was guide for beginners with easy tongue:) I'm sorry from advanced users if in some places and sorry for not good english :) Although this guide is to NOT DEAD device. If you have a dead device, then its another story. I'll try to find easist way to alive dead devices and share here - to beginners ofcourse :)

Join! :)

[suyog]

@TonyUkuk Many Thanks for details steps written here and time take by you to post. Though it is mostly similar , I am going to try again.
I am using Linux Mint and I feel that should be ok.

[suyog]

@TonyUkuk I tried and got exactly same result as I get on Windows. :(
I guess it is some hardware issue.

[Ta76eem]

Flashed My n9 and brought main.bin from here :
http://www.mrcrab.net/Nokia-Product-Code.html...

Downloaded this :
Dfl61 Harmattan 40.2012.21-3 Pr Legacy 006-oem1-958 Arm.bin

but when it finished this apeared on my N9 :
Device not working properly [in BLUE]
Try updating the device software with Nokia Software Updater. If the problem persists, contact the nearest Nokia Care point. [in WHITE]

Help Please...

[TonyUkuk]

@suyog, what is your problem? same cmt-mcsuw? say please,
1)did you successfully flashed your device with last firmware version?
2)put log here please or attach a screen phoyo of log of your actions on flashing it
3)i dont think so that is hardware issue..hope that not.
3)which version is your device? is this 003 (brand but factory shipping China)

a little tip : go to the settings>about product, take a snapshoot the place where shows barcode. send this picture to your computer,scan this picture via any barcode scanner - you will get the wright product code which with you find the wright firmware to flash cmt - i did like that. (ofcourse if your device booting in OS)

[TonyUkuk]

@Ta76eem, seems it's partition issue. chechk this thread (http://talk.maemo.org/showthread.php?t=82655&page=2) for knowledge. but lets fitst chechk whether your partitions are wright - from here (http://wiki.meego.com/N950/Fixing_MALF_state) do like the instructions describing and fllow the steps till step 7 - from the beginning step 7 begins solving another issue, we need 1,2,3,4,5,6 steps. so after fdisk -l (step 6) there will be partition table - take snapshoot and attach here.

PS: it will be open three window as mass storage where you will see your folders - its good if you snapshoot them too and show. Although the instructions are able on linux, not on windows.

[Ta76eem]

Although the instructions are able on linux, not on windows.

I am using Windows :|

[nieldk]

I am using Windows :|
Download and boot from a Ubuntu live-cd distro ;)

[Bega]

Hi guys,

Lately I have been getting errors when flashing my phone. Normally flashing goes right right away but now I think I have repartition problems. Don't know if Nemo install has anything to do with this. The error I get when flashing is the same as in this post: http://talk.maemo.org/showthread.php?t=82655

I have used the same firmware images for over a year now with no problems so I'm not sure what's wrong.

Anyways, here are the partitions on my N9 attached to this post.

PS. Tried reflashing after cleanin device from N9 settings with no help. Not even "updating" fw through Nokia suite helped

[thedead1440]

Bega,

You should simply insert the following command to flash:

flasher -f -F rootfs.bin -F emmc.bin --no-preserve

The above would fix the partitioning of the device and flash both the rootfs+emmc...

[Bega]

@thedead1440,

The command you gave me works and the device began to flash normally like it always has. Thanks for the quick reply ;)

[TonyUkuk]

I am using Windows :|

You are using Nokia N9, so you must know how to use linux :) Ok, if dont know, I'm sure that there are friends of yours who can use linux. Maan, just fix this little problem ;)

[Garp]

HELP! My USB connection dont work besides charging after flashing openmode.:confused:

My N9 chrashed and needed to flash. After flash to standard mode the USB worked OK.

Then i used zImage from here to flash openmode
http://wiki.maemo.org/Ubiboot#Moving_files_using_Filebox_Root

C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage --flash-only=kernel --suppres
s-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan

Picked ape-algo from a FIASCO file
Device is in Sync and connect mode, sending ADL reboot.
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 4975 ms
Unable to detect flashing interface: standing by for device reboot.
Suitable USB interface (bootloader) not found, waiting...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_340
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 14798 kB/s)
Suitable USB interface (phonet) not found, waiting...
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 <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 92 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2834 / 2834 kB 1971 kB/s]
Updating SW release
Success

C:\Programmer\nokia\Flasher>

Then installing Backupmenu_1.1.9_tar and restored from backup as before but USB only charging
Edit: Also BEFORE installing Backupmenu!

In terminal:
accli -I
Current mode: open
uname -r
2.6.32.54-dfl61-20121301

[MONVMENTVM]

Yesterday suddenly my browser crashed and several apps wouldn't start, so I rebooted the phone and got the "Device not working properly" message.

Trying to flash the phone I receive a "Downgrade disallowed" message although the version/variant number is higher or am I blind and/or stupid?

sudo flasher -f -F 34417842_DFL61_HARMATTAN_40.2012.21-3.430.01.1_PR_LEGACY_430_ARM_RM-696_PRD_signed.bin
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 008, device address 014.
Device identifier: 357923041477417 (SN: N/A)
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.350.3_PR_350
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 33664 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 008, device address 015.
Device identifier: 357923041477417 (SN: N/A)
Raw data transfer EP found at EP2.
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_40.2012.21-3.430.01.1_PR_430
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 43 %, 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:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1354010096)
[Pipe 0] Finishing in error state with status 10
========================================

ERROR: Failed to flash images



Why is that and what can I do now?

[thedead1440]

MONVMENTVM,

Get the same image; it could be because you are on a telco-variant you can't upgrade...


Garp,

Maybe your backupmenu restore screwed up? First thing I would do is reflash and see if your N9 works without backupmenu...

[Garp]

Garp,

Maybe your backupmenu restore screwed up? First thing I would do is reflash and see if your N9 works without backupmenu...

Thanks but dont think thats problem because I couldn't get backupmenu_1.1.9_tar because it was only on PC. Have to flash again to standard mode to get it to N9!

[MONVMENTVM]

MONVMENTVM,

Get the same image; it could be because you are on a telco-variant you can't upgrade...


Garp,

Maybe your backupmenu restore screwed up? First thing I would do is reflash and see if your N9 works without backupmenu...

Thanks, yes it's a t-mobile austria variant. The one I was trying to install apparently was v2 of the firmware while the one installed is the v1 (which probably is why the original variant number is 350 and now 430 despite having the same product code 059L6C3).

http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696&releaseID=6978621696&variantID=7005660274&productCode=059L6C3&version=30.2012.7.1

I can't find the T-Mobile Austria v1 firmwares with the 350 variant other than in older PRs. For PR1.3 I can only find the v2 (430) :(

[thedead1440]

Thanks, yes it's a t-mobile austria variant. The one I was trying to install apparently was v2 of the firmware while the one installed is the v1 (which probably is why the original variant number is 350 and now 430 despite having the same product code 059L6C3).

http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696&releaseID=6978621696&variantID=7005660274&productCode=059L6C3&version=30.2012.7.1

I can't find the T-Mobile Austria v1 firmwares with the 350 variant other than in older PRs. For PR1.3 I can only find the v2 (430) :(

The PR1.2 link you posted is also a v2 variant (430)... Can you try finding in other countries but T-Mobile variants too and try one of those images?

[MONVMENTVM]

Oh yes posted the wrong link when I was checking older PRs.

I already tried T-Mobile Hungary variant which is 40.2012.21-3.373.1_PR_LEGACY_373 (which is relatively low but still higher than the installed 350) but still no luck. Could it be that OTA updates messed up the timestamps on the system or something?

[thedead1440]

You did an OTA to PR1.3? It's possible that screwed the timestamp then... I would advice trying to use Nokia Software Updater for Windows as it seems to restore factory firmware from what others have mentioned although I haven't personally ever tried it...

[Garp]

Using another kernel than zImage, the zImage_2.6.32.54-openmode_l2fix solved USB problem even using backupmenu.

But then even if as user:
disclaimer-cal remove View-openmode
AND the --suppress-warranty-warnings
Every time reboot this irritating warning appears:confused:
and tried flash twice.

Does I really need to use old zImage.PR13 to get it to work or...?

C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage_2.6.32.54-openmode_l2fix --fl
ash-only=kernel --suppress-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan

Picked ape-algo from a FIASCO file
Device is in Sync and connect mode, sending ADL reboot.
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 4975 ms
Unable to detect flashing interface: standing by for device reboot.
Suitable USB interface (bootloader) not found, waiting...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_340
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 13427 kB/s)
Suitable USB interface (phonet) not found, waiting...
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 <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 55 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2712 / 2712 kB 2032 kB/s]
Updating SW release
Success

C:\Programmer\nokia\Flasher>

[nieldk]

HELP! My USB connection dont work besides charging after flashing openmode.:confused:

My N9 chrashed and needed to flash. After flash to standard mode the USB worked OK.

Then i used zImage from here to flash openmode
http://wiki.maemo.org/Ubiboot#Moving_files_using_Filebox_Root

C:\Programmer\nokia\Flasher>flasher.exe -a DFL61_HARMATTAN_40.2012.21-3.340.04.1
_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin -k zImage --flash-only=kernel --suppres
s-warranty-warning -f -R
flasher 3.12.1 (Oct 6 2011) Harmattan

Picked ape-algo from a FIASCO file
Device is in Sync and connect mode, sending ADL reboot.
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 4975 ms
Unable to detect flashing interface: standing by for device reboot.
Suitable USB interface (bootloader) not found, waiting...
Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_340
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 14798 kB/s)
Suitable USB interface (phonet) not found, waiting...
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 <none>
Image cert-sw not present
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped

Battery level 92 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] kernel [finished 100 % 2834 / 2834 kB 1971 kB/s]
Updating SW release
Success

C:\Programmer\nokia\Flasher>

Then installing Backupmenu_1.1.9_tar and restored from backup as before but USB only charging

In terminal:
accli -I
Current mode: open
uname -r
2.6.32.54-dfl61-20121301

not sure, but might be wrong zImage.
Suggest you try this one
http://maemo.cloud-7.de/HARM/N9/1.3/openmode-kernel/

[MONVMENTVM]

You did an OTA to PR1.3? It's possible that screwed the timestamp then... I would advice trying to use Nokia Software Updater for Windows as it seems to restore factory firmware from what others have mentioned although I haven't personally ever tried it...

Doesn't work because apparently NSU needs the phone to be able to boot, while the flasher does not. As I've booted into Windows anyway now I've downloaded NaviFirm+ and downloading the firmware again (maybe it's timestamped differently). I really hope this works... while googling for solutions I've found this btw.:

http://my-symbian.com/forum/viewtopic.php?t=43973

Exactly what happened to me. Can't believe I have this N9 for a couple of weeks (after my N900 died of hardware failure) and this thing is already bricked after surfing the web. :mad:

EDIT: Nope does not work either. What could I try next? :confused:

[Garp]

not sure, but might be wrong zImage.
Suggest you try this one
http://maemo.cloud-7.de/HARM/N9/1.3/openmode-kernel/

Thanks you were right this one function without USB or Warnings trouble, even if I dont know why:)

[MONVMENTVM]

Doesn't work because apparently NSU needs the phone to be able to boot, while the flasher does not. As I've booted into Windows anyway now I've downloaded NaviFirm+ and downloading the firmware again (maybe it's timestamped differently). I really hope this works... while googling for solutions I've found this btw.:

http://my-symbian.com/forum/viewtopic.php?t=43973

Exactly what happened to me. Can't believe I have this N9 for a couple of weeks (after my N900 died of hardware failure) and this thing is already bricked after surfing the web. :mad:

EDIT: Nope does not work either. What could I try next? :confused:

Nobody else did the mistake to upgrade to PR1.3 via OTA and then had to reflash? I really don't know how to unbrick my device now. :(

[MONVMENTVM]

Ok finally fixed it and for people having similar issues flashing their n9 this might come in handy.

It appears that not only does the variant number have to be higher or equal, also the following numbers have to be higher. For example I had

DFL61_HARMATTAN_40.2012.21-3.350.3

installed. It appears that this actual firmware does not really exist for my product code. It did for a previous PR but got changed to variant 430, but as I updated via OTA the firmware variant never got changed to the correct 430. It kept the 350.3 part and replaced the 40.2012.21-3 to resemble the PR1.3.

Having to flash my phone now there is only this 430 variant available for my product code which is precisely:

DFL61_HARMATTAN_40.2012.21-3.430.01.1

One would think coming from a 350, flashing to 430 wouldn't be a problem because the variant number is higher. But no, it doesn't work because of big a** version numbering inconsistency fail. As you can see it's actually variant 350.3 vs 430.01(.1) and apparently the numbers following the 350 and 430 variant codes ALSO WILL BE COMPARED.

So I was looking around for a firmware that has both the variant number and what follows after it at equal or higher numbers and I found this N9 Rm-696 Optimus Pt V1-black - 16g firmware named:

DFL61_HARMATTAN_40.2012.21-3.398.3

And voilá that damned thing works again.

[Timpaxi]

Hi. Maybe someone knows what my friend should do. His phone product code is 059L4M9 but firmware on that phone is DFL61 HARMATTAN 40.2012.21-3.335.1 PR LEGACY 335 ARM RM-696 PRD signed.bin and that is arab emirates variant, product code 059L6B8. So i told him to use that arab emirates file to flash and it flashed but not that cmt-mcusw.. So then try only cmt flash but same result. Is that somekind mix in that phone, so he needs to flash that cmt with some other variant?

And now it might have RPL problem. Is there any way to fix it or just take it to nokia carepoint?

[suyog]

@suyog, what is your problem? same cmt-mcsuw? say please,
1)did you successfully flashed your device with last firmware version?
2)put log here please or attach a screen phoyo of log of your actions on flashing it
3)i dont think so that is hardware issue..hope that not.
3)which version is your device? is this 003 (brand but factory shipping China)

a little tip : go to the settings>about product, take a snapshoot the place where shows barcode. send this picture to your computer,scan this picture via any barcode scanner - you will get the wright product code which with you find the wright firmware to flash cmt - i did like that. (ofcourse if your device booting in OS)

@TonyUkuk Thanks for reply but I guess I have already tried most of things. if you can read my posts earlier you will come to know.
Anyways I will try to answer again.
1) My Phone was from poland , central europe 64GB variant(059J1V8). Now due flashing many times , I am on highest number fw available for N9 which is swiss variant, (480)You can check my posts from this onwards http://talk.maemo.org/showpost.php?p=1305428&postcount=378
And bit updated here http://talk.maemo.org/showpost.php?p=1338615&postcount=636
2) please refer links posted in 1st.
3) 3) I feel it is hardware issue now(???) , my current version is 480 swiss variant with china cmt.

And I have made sure that by even scanning QR code product code is 059J1V8.

[suyog]

Ok finally fixed it and for people having similar issues flashing their n9 this might come in handy.

It appears that not only does the variant number have to be higher or equal, also the following numbers have to be higher. For example I had

DFL61_HARMATTAN_40.2012.21-3.350.3

installed. It appears that this actual firmware does not really exist for my product code. It did for a previous PR but got changed to variant 430, but as I updated via OTA the firmware variant never got changed to the correct 430. It kept the 350.3 part and replaced the 40.2012.21-3 to resemble the PR1.3.

Having to flash my phone now there is only this 430 variant available for my product code which is precisely:

DFL61_HARMATTAN_40.2012.21-3.430.01.1

One would think coming from a 350, flashing to 430 wouldn't be a problem because the variant number is higher. But no, it doesn't work because of big a** version numbering inconsistency fail. As you can see it's actually variant 350.3 vs 430.01(.1) and apparently the numbers following the 350 and 430 variant codes ALSO WILL BE COMPARED.

So I was looking around for a firmware that has both the variant number and what follows after it at equal or higher numbers and I found this N9 Rm-696 Optimus Pt V1-black - 16g firmware named:

DFL61_HARMATTAN_40.2012.21-3.398.3

And voilá that damned thing works again.

So that means
if 1st number of new fw > 1st number of old fw then
If 2nd number of new fw > 2nd number of old fw then
allow flash
endif
endif

?

[Garp]

Thanks you were right this one function without USB or Warnings trouble, even if I dont know why:)

http://wiki.maemo.org/Ubiboot#Moving_files_using_Filebox_Root

And I still would like if anyone could give an answer to why the kernel:
zImage (new from e-yes) made USB not working?
http://talk.maemo.org/showpost.php?p=1374779&postcount=950

zImage_2.6.32.54-openmode_l2fix (solving this point 4) http://www.swagman.org/juice/ubiboot/README ) made warranty warnings appears at reboot?
http://talk.maemo.org/showpost.php?p=1374817&postcount=958

At least I got an answer from juiceme to the backupmeny problem with my installed kernel, thanks:
http://talk.maemo.org/showpost.php?p=1376623&postcount=196

Edit: And problem now solved thanks to nieldk
http://talk.maemo.org/showpost.php?p=1376738&postcount=173

[MONVMENTVM]

So that means
if 1st number of new fw > 1st number of old fw then
If 2nd number of new fw > 2nd number of old fw then
allow flash
endif
endif

?

Looks like it, yes.

[Callum.Brierly]

Do I have to 'zeroize device' to remove open mode? Or will a comprehensive reset do the trick? How long does zeroizing take?

Sorry if this has already been answered in this thread.

[botski]

Hi guys! i got my n9 today. i want to flash my n9. i will try to finish my download. :D

[botski]

can anyone help me? when i extract this file 059N1D5_RM-696 NDT PHILIPPINES WHITE 64GB.tar always corrupt. ive download this file for 2 times to verify. but is corrupt. :( i cant continue my flashing.

[minimos]

Well, what did you use to download the file, from where did you download it, what's the file length of the tar you download, does that length match with the original file... ?

[Soban]

Hi guys.
Bought a N9 two days back.
It was dead by battery drain charged it using a method on another side.
Booted and after nokia logo it give an error screen.
tried flashing good an error
here is the log

Sobans-MacBook-Air:~ Soban$ flasher -F /Users/Soban/Desktop/059J228_RM-696\ NDT\ MEA1\ MEA2\ BLACK\ 64GB/DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_006-OEM1-958_ARM.bin -f
flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

Suitable USB interface (bootloader/phonet) not found, waiting...
USB device found at bus 250, device address 6.
Device serial number is N/A
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. 19990 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 250, device address 6.
Device serial number is
Raw data transfer EP found at EP2.
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_40.2012.21-3_PR_006
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 36 %, 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 3957 kB/s]
[_] rootfs [writing 0 % 2048 / 978983 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 3455 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 3615 kB/s]
[f] rootfs [writing 0 % 3072 / 978983 kB NA ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
mmc: handle_buffer failed in lzo decompress (-1)
[Pipe 5] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

N9 Code: 059J228
operating system: Mac OSx
Thank you
waiting for help.

[Timpaxi]

can anyone help me? when i extract this file 059N1D5_RM-696 NDT PHILIPPINES WHITE 64GB.tar always corrupt. ive download this file for 2 times to verify. but is corrupt. :( i cant continue my flashing.

Download from here: http://www.mrcrab.net/nokia/Nokia_N9.html?productID=4823499691&productType=RM-696&releaseID=7048842309&variantID=7076927120&productCode=059N1D5&version=40.2012.21.3

[Timpaxi]

Hi guys.
Bought a N9 two days back.
It was dead by battery drain charged it using a method on another side.
Booted and after nokia logo it give an error screen.
tried flashing good an error
here is the log



N9 Code: 059J228
operating system: Mac OSx
Thank you
waiting for help.

Are you sure of that product code? Read that QR-code from settings-> info

[thedead1440]

Soban,

I may be mistaken but iirc, that error usually indicates borked flash memory :(

[Soban]

Are you sure of that product code? Read that QR-code from settings-> info

I've rechecked. It's the product code.

[Soban]

Soban,

I may be mistaken but iirc, that error usually indicates borked flash memory :(

Thanks buddy.
Any possible way to unblock it. When connected to mac, it do work as a storage device.

[andy_con]

can someone help, am following the guide on page one and get here

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

but it does not do anything, what am I doing wrong?

[Soban]

Hi guys.
Bought a N9 two days back.
It was dead by battery drain charged it using a method on another side.
Booted and after nokia logo it give an error screen.
tried flashing good an error
here is the log



N9 Code: 059J228
operating system: Mac OSx
Thank you
waiting for help.

on an other note using Diskutil list i got these readings

sh-3.2# diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 120.5 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *64.1 GB disk1
1: Windows_FAT_32 Nokia N9 57.7 GB disk1s1
2: Linux 2.1 GB disk1s3

[andy_con]

can someone help, am following the guide on page one and get here

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

but it does not do anything, what am I doing wrong?

can someone please offer some advice?

[Eztran]

If it ran, it's probably worked, and you can move on.

That step's not actually necessary, it just helps with running the commands (i.e. you don't have to be working from the flasher directory or use the whole path every time).

[roman2205]

I was browsing web with my white Nokia N9 64GB.......suddenly my n9 switched off completely......No sign of life......tried to restart....no luck....plug it in with a wall charger.....no luck.....its not charging and the LED is not flashing....when I connect it with my laptop using Win Flasher.......the charging Led flashed consistently for 10-15 min thn gone again.....can anyone help.....Thnks in advance


De-assembled my beloved N9........left it for 24 hour.....assembled it again....connect with laptop....problem solved.....apparently....lets see....what happens......

[k4rl]

Hey, guys. Just created an account.

Im in a pickle and Im forced to ask you guys for help. I recently bought used n9 (My first pay check and bought myself a new toy:)). I just thought I will put the 'ol n900 on shelf.

As I found some stuff from the previous user I decided to flash the device with the help of Nokia Suite. The device did some things and after a reboot SIM card wouldnt work, Meego system is freezing. I have stumbled upon this forum post - read all pages and tried to reset N9 to working condition - without success. Im fighting with this issue for 3 days.

Nokia product code: 059M7K1

which points to China White 64GB image according to navifirm - and thats odd I have a black 16GB:/

HARMATTAN installed on device: DFL61_HARMATTAN_40.2012.21-3_PR_005

so sais the Flasher


As I understand there is no way I can load 001 variant on my device? Can Someone please help me? If You need any further information let me know. Ill post it ASAP.

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

[matbernard]

Hi all,

just get a nokia N9 from one of my friend that couldn't use it anymore because don't remember the security code.

Look on google and find you post try it but get the following error message. Did someone get any clue on it.

Thanks

sudo flasher -f -F A6D5F456_DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_005-OEM1-958_ARM.bin -F 59BEC3BC_DFL61_HARMATTAN_40.2012.13-7.SEAP_EMMC_SEAP.bin --erase-user-data=secure


flasher 3.12.1 (Oct 5 2011) Harmattan
WARNING: This tool is intended for professional use only. Using it may result
in permanently damaging your device or losing the warranty.

USB device found at bus 001, device address 006.
Device identifier: 357923040588388 (SN: N/A)
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1603
Server implements softupd protocol version 1.8

Battery level 100 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_005
Image moslo not present
Image tar skipped
Image config skipped

Battery level 97 %, 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 ]
[ ] mmc [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 ]
[ ] mmc [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1342067459)
[Pipe 0] Finishing in error state with status 10
========================================

ERROR: Failed to flash images

[juiceme]

Downgrade disallowed (1342067459)
ERROR: Failed to flash images

That's your problem.
You need to get later versions for emmc and firmware.

[zaidk9]

how to open flasher through cmd.exe???

[Eztran]

If you added the Flasher directory to the system path, just use the commands normally.

If not: cd to the folder flasher's in (C:\Program Files\Nokia\Flasher\) first, then run the commands. If the rootfs/emmc files aren't in that directory, you'll have to specify the full path to them.

Alternatively, give full paths to everything, but that's a bit of a hassle.

[zaidk9]

Hope this works on windows 8

[d3monico]

because I can flash my n9 only with the original firmware DFL61_HARMATTAN_40.2012.21-3.232.05.2_PR_LEGACY_232_ARM_RM-696_PRD_signed.bin and not with the DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin?
thanks

[d3monico]

hi,
because I can flash my n9 only with the original firmware DFL61_HARMATTAN_40.2012.21-3.232.05.2_PR_LEGACY_232_ARM_RM-696_PRD_signed.bin and not with the DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin?
thanks

[minimos]

hi,
because I can flash my n9 only with the original firmware DFL61_HARMATTAN_40.2012.21-3.232.05.2_PR_LEGACY_232_ARM_RM-696_PRD_signed.bin and not with the DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin?
thanks

The general reason is that the device has an internal rule to block the possibility to downgrade the software, i.e. to flash a firmware with a 'lower' number (within the same release).
The side effect of that is: if you want to flash a firmware for a different release (i.e. different geographic region or operator) depending on how the numbers match up, in some cases it is possible (e.g. 001->232), in some other is not (e.g. 232 ->001).
It's a case that in the commercial life of the device is not considered (e.g. a phone shipped with settings for Italian operators should be used in Italy), so it is what it is.
And as repeated several times in this thread, no, there is no way to avoid this block.

[mdoube]

Just went through several reflashing attempts using the correct images for my N9 downloaded with NaviFirm+, and every time had the scary boot warning and also an inability to set the device lock password (Wrong password). Turns out it was a broken download with wrong CRC. I should have guessed sooner...

To save others the inconvenience, would it be worth updating the main instructions / wiki with a CRC-checking step (I used crc32 in the libarchive-zip-perl Ubuntu package)? It's a little time spent which maybe saves a lot of confusion. The CRCs are contained in the small .vpl files listed alongside the image files in NaviFirm+, in the <Crc> field (here it's 8c9ea3a3).

RM696_[your product code]_firmware_version.vpl

<File><Name>DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin</Name><FileType>Binary</FileType><FileSubType>Mcu</FileSubType><Signed>false</Signed><Optional>false</Optional><Crc>8c9ea3a3</Crc></File>

[dak_sriv]

Followed it step by step. works perfectly. Thanks!

[unfuccwittable]

Hey guys, I'm not able to find the correct firmware image for my Nokia N9. Does anyone know where I can find the image for a White 64GB N9 059N151. I flashed with the 'Rest of World' image and after a few hours, the phone shuts off and throws the following error when I boot it back up:

security problem (xorg): /usr/lib/xorg/modules/input/evdev_drv.so

This is quite frustrating as I just got this phone and when I updated to pr 1.3 it failed and all attempts to update it since have resulted in the error above. Any help is appreciated. At this point I'm ready to just sell the phone and get something else. But I figured I'd give it one last go here.

[juiceme]

Hey guys, I'm not able to find the correct firmware image for my Nokia N9. Does anyone know where I can find the image for a White 64GB N9 059N151. I flashed with the 'Rest of World' image and after a few hours, the phone shuts off and throws the following error when I boot it back up:

security problem (xorg): /usr/lib/xorg/modules/input/evdev_drv.so

This is quite frustrating as I just got this phone and when I updated to pr 1.3 it failed and all attempts to update it since have resulted in the error above. Any help is appreciated. At this point I'm ready to just sell the phone and get something else. But I figured I'd give it one last go here.

059N151, that'd be Vietnam variant, right?

Download these:
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1212/2717/7140840508/33EAD321_DFL61_HARMATTAN_40.2012.21-3.454.5_EMMC_454.bin
http://nds2.fds-fire.nokia.com/p/d/fds_fire/1212/2717/7140840368/43AD05DD_DFL61_HARMATTAN_40.2012.21-3.454.6_PR_LEGACY_454_ARM_RM-696_PRD_signed.bin

[BaronKatz]

After flashing the phone it worked for about a week or two and then I started to get the message "Phone not allowed MM #6" I never had this before and I've had the phone for a year now. I have not idea what is going on... It's so strange! How can I fix this and why did it happen after I installed the firmware update?

[StygiAn TrepidAtioN]

Hi!

I bought a new N9 couple of days ago and am trying to come up to speed with all the develpoment that has happened.

I've downloaded the 2 bin files from NaviFirm+ for product code 059J228. But before proceeding with flashing, I want to ensure the files are accurately downloaded.

Can someone tell me where me where I may find checksum for these 2 files so I could cross verify?

Warm regards,
JoEy

[peterleinchen]

Can someone tell me where me where I may find checksum for these 2 files so I could cross verify?

Just look above (http://talk.maemo.org/showpost.php?p=1392281&postcount=993).


To save others the inconvenience, would it be worth updating the main instructions / wiki with a CRC-checking step (I used crc32 in the libarchive-zip-perl Ubuntu package)? It's a little time spent which maybe saves a lot of confusion. The CRCs are contained in the small .vpl files listed alongside the image files in NaviFirm+, in the <Crc> field (here it's 8c9ea3a3).

RM696_[your product code]_firmware_version.vpl

<File><Name>DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM.bin</Name><FileType>Binary</FileType><FileSubType>Mcu</FileSubType><Signed>false</Signed><Optional>false</Optional><Crc>8c9ea3a3</Crc></File>

[kikujiro0208]

I have possibly good news for us chinese N9 owners. I am still very guarded with my comment, but it looks promising.
In answer to your question, yes I used the main.bin from the sim tray. in my case was a 003 aka chinese version. I would recommend you try what i did. I also tried nemesis, but had no luck. yes i was able to change product code, but thats it. afterwards i still was unable to flash(using phoenix, i never tried winflasher w/new product code).
my code looked something like this flasher>flasher -F nameofyourold.bin --flash-only=cmt -f
note that i did this after doing a full reflash with in my case a 009 main and emmc.bin files. I recvd the sim card error and after doing the cmt flash, it was gone. on my first flash, i also had a "unable to use camera while connected to pc msg" that is gone now!! fixed?
I am also downloading new maps, also a previous problem. I would give it a try, though you may need to change your product code back in nemesis to prevent other errors???
stay tuned I will report back on how my N9 is fairing!

Sadly it seems that I have the same problem...
I have a 003 Chinese N9 that I tried to flash into a 005 AsiaPacific version...
So I flashed both the 005 FW and EMMC bin files and now got stuck with "sim card error", "cannot open applications", "EMEI info not visible"...
Since there is no way to go back to the previous 003 version, what can be done to have all the above issues fixed?
Thanks,

[kikujiro0208]

Sadly it seems that I have the same problem...
I have a 003 Chinese N9 that I tried to flash into a 005 AsiaPacific version...
So I flashed both the 005 FW and EMMC bin files and now got stuck with "sim card error", "cannot open applications", "EMEI info not visible"...
Since there is no way to go back to the previous 003 version, what can be done to have all the above issues fixed?
Thanks,

Problem solved...
flasher -F 003version.bin --flash-only=cmt -f -R
This did the trick... N9 reborn now...

[smit]

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.

Suitable USB interface (bootloader/phonet) not found, waiting...
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)
Suitable USB interface (phonet) not found, waiting...
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:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1329851503)
[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.

I had installed PR1.3 on my N950 from here (http://thepiratebay.ac/torrent/7530337/Nokia_N950_PR1.3_firmware_%28leaked%29). I am facing same problem.

As suggested in quoted post, it can be solved by trying different images (probably with higher variant version). For N950 PR1.3, there is only one image available here (http://thepiratebay.ac/torrent/7530337/Nokia_N950_PR1.3_firmware_%28leaked%29). Is there any other place where I can download images for N950?

[kFORDMATT]

Good day to everyone, i hope someone can help please.

i've just taken ownership of a N9 which originated in China. I've never done this kind of thing before but want to and am keen to learn.

I'd like to flash it to remove the 003 china firmware to a european ?? one if possible.

I've used the product code in Navifirm + but it only gave me a single variant. this being a chinese variant. 40.2012.21.3 = PR1.3

what i'd like to know is am i stuck with the chinese firmware. After reading the comprehensive flashing guide i thought i would be able to choose an option to move away from it.

Looking forward to some help else there 's a very nice N9 for sale soon.

many Thanks :confused: