Reply
Thread Tools
Posts: 1 | Thanked: 0 times | Joined on Oct 2013
#981
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:
Code:
flasher -f -F old_main.bin --flash-only=cmt

Last edited by k4rl; 2013-10-30 at 20:28.
 
Posts: 1 | Thanked: 0 times | Joined on Nov 2013
#982
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
 
Community Council | Posts: 4,920 | Thanked: 12,867 times | Joined on May 2012 @ Southerrn Finland
#983
Originally Posted by matbernard View Post
Downgrade disallowed (1342067459)
ERROR: Failed to flash images
That's your problem.
You need to get later versions for emmc and firmware.
 
Posts: 673 | Thanked: 230 times | Joined on Oct 2012 @ Mumbai
#984
how to open flasher through cmd.exe???
 
Posts: 138 | Thanked: 144 times | Joined on Oct 2012 @ Devon, England
#985
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.
 

The Following User Says Thank You to Eztran For This Useful Post:
Posts: 673 | Thanked: 230 times | Joined on Oct 2012 @ Mumbai
#986
Hope this works on windows 8
 
Posts: 6 | Thanked: 0 times | Joined on Oct 2012 @ italy
#987
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
 
Posts: 6 | Thanked: 0 times | Joined on Oct 2012 @ italy
#988
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
 
Posts: 646 | Thanked: 1,124 times | Joined on Jul 2010 @ Espoo, Finland
#989
Originally Posted by d3monico View Post
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.
 

The Following 2 Users Say Thank You to minimos For This Useful Post:
Posts: 1 | Thanked: 2 times | Joined on Nov 2013
#990
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
Code:
<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>
 

The Following 2 Users Say Thank You to mdoube For This Useful Post:
Reply

Tags
flashing, nokia n9


 
Forum Jump


All times are GMT. The time now is 20:47.