rainisto, thank you for your reply.

Unless I'm missing something, I believe the 2-step flashing, using that --flash-only=mmc option is shown as the "Comprehensive reset" method in the original post of this thread - which is supposed to be the authoritative guide for flashing. Given the random errors I've been getting while flashing, I think splitting them in 2 gives them a better chance to succeed individually.

I'm pretty sure I tried the usage you suggested above, with the same end result.

Eventually I managed to flash it using Nokia Software Updater, after making sure I closed the Nokia Suite (which I believe was trying to use the same USB port, causing troubles). But although the phone boots I'm getting frequent freezes and spontaneous reboots. You may be right about some hardware failures. Either that or Maemo took a turn for the worse from the days of Nokia 770, which was the last time I've used it.

No wonder Elop jumped off the burning platform. Maybe he had a similar experience. Brand new device. Makes for a nice paperweight with a clock.

Thanks for reply, but as i said since default variants failed to flash to to some reasons I tried various others and ended up with combo of swiss+chinese.
Thing which I am unable to understand is - how these SIM error appear out of nowhere suddenly?

This has been explained in several posts in the forum. Each variant binary has a creation timestamp for the firmware certificate and for cmt certificate. So some variants have been created later than the other so they have never timstamps and allow flashing 'as system think its a upgrade) (cmt firmware is same in european variants, so it always succeeds, untill someone flashes chinense cmt (which was always created later than european/vanilla cmt, so it never can be downgraded because of timestamp certificate check).

Well the 'authorative' guide is somewhat lacking on that part, and it doesn't even tell how to do cold flashing (last time when I read the guide).

PS. if your wondering why to believe me and not the guide, I can say that I've read the source code of the flasher and bootloader, so I have pretty good idea what lower level is doing in Harmattan. And I've flashed hundreds of Harmattan phones back in the days when I was still working for Nokia Meego R&D. (I've even flashed the device over serial cable back in the days before there was USB flasher available for it)

rainisto, so what can I do with my problem?
http://talk.maemo.org/showpost.php?p...postcount=1021


Thanks for reply.

Ok, finally I gave up and sold my N9 for about $160, not bad for device which can't function as phone.
May be in future I will pick another if I can get it cheap.
Thanks to all who tried to help me to understand and resolve issues

I flashed my N9 about 2 months ago. Then last month the phone crashed in Whatsup and cannot be started again. So I want to reflash it again. But it failed. Here is the log from the flasher. Anyone can help? Thx.


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 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_006
Success


C:\Program Files\Nokia\Flasher>flasher -f -F main.bin -F emmc.bin --flash-only=mmc
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 1603
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. 18337 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_006
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image kernel skipped
Image moslo skipped
Image rootfs skipped
Image tar skipped
Image config skipped

Battery level 77 %, continuing.

image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[_] mmc [init 0 % 32768 / 1829147 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 ]
[f] mmc [init 0 % 32768 / 1829147 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 '/sbin/dosfslabel /tmp/sudmmcqlZFyn/internal0p1 "Nokia N9"'
mmc: Unable to remove mount point '/tmp/sudmmcqlZFyn/mnt/home': No such file or
directory
mmc: Could not remove mount directory /tmp/sudmmcqlZFyn/mnt: No such file or dir
ectory
[Pipe 1] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

sasacy,

If you want to reflash it, why are you flashing only the emmc?

Instead issue the following command:

Once successful, either plug out your cable and boot it up or issue "flasher -R" to do so...

Hardware broken, so trashcan or sell device as parts.

Hi thedead1440,

Honestly I don't know what is the correct way. Anyway I tried your suggestion but failed. What should I do?

C:\Program Files\Nokia\Flasher>flasher -f -F main.bin -F emmc.bin --no-preserve
flasher 3.12.1 (Oct 6 2011) Harmattan
Warning: --no-preserve is not recommended, instead use erase commands
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_006
Image moslo not present
Image tar skipped
Image config skipped

Battery level 90 %, 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 [init 84 % 6050 / 6050 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 1194 kB/s]
[_] rootfs [init 0 % 20480 / 978983 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 ]
[x] cmt-algo [finished 100 % 789 / 789 kB NA ]
[x] cmt-mcusw [finished 100 % 6050 / 6050 kB 3087 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 1194 kB/s]
[f] rootfs [init 0 % 21504 / 978983 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 exec 'tune2fs -L rootfs /tmp/sudmmc35Gf4L/internal0p2'
mmc: Could not remove mount directory /tmp/sudmmc35Gf4L/mnt: No such file or dir
ectory
[Pipe 4] Finishing in error state with status 1
========================================

ERROR: Failed to flash images