![]() |
Re: Fix Nokia n9 deadly cmt issue
Update! Tried this (thank you aspergerguy.)
Any suggestions ? >flasher -f -F c:\main.bin --erase-user-data=secure -F c:\emmc.bin --erase-mmc=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. Ping attempt 1 (250 ms) Server application: 1.7.2 Found product RM-696 rev. 1603 Server implements softupd protocol version 1.8 Warning: user data may reside on MMC. In that case the MMC is unnecessarily erased twice. Battery level 77 %, continuing. Erasing, this may take a while. Erase done. Battery level 77 %, continuing. Erasing, this may take a while. Erase done. Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_001 Image moslo not present 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 ] [ ] 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 ] [x] cmt-algo [finished 100 % 789 / 789 kB NA ] [_] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3377 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 2028 kB/s] [f] rootfs [pending 0 % 2048 / 1170282 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 ] [f] cmt-mcusw [finishing 0 % 6050 / 6050 kB 3377 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 2028 kB/s] [f] rootfs [pending 0 % 2048 / 1170282 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/sudmmcFq5tFf/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 |
Re: Fix Nokia n9 deadly cmt issue
You found thd right command
https://talk.maemo.org/search.php?searchid=21402586 https://talk.maemo.org/showpost.php?...postcount=1512 But :( Quote:
As nieldk already is the guy with the bad info: I am afraid to second that. @niel: even I do not recognize the MTC_NOS_READY error |
Re: Fix Nokia n9 deadly cmt issue
Unfortunately you will find exactly the same scenario in this thread with no resolution:
https://talk.maemo.org/showthread.php?t=91333 |
Re: Fix Nokia n9 deadly cmt issue
There is also a slight possibility that the download is broken.
So if you know the checksum of the specific firmware revision file (there were/are lists in the web) then check or download it once more and compare. I would also try once more: Code:
flasher -f -F c:\main.bin --erase-user-data=secure -F c:\emmc.bin --erase-mmc=secure --no-preserve -c |
Re: Fix Nokia n9 deadly cmt issue
Unfortunately Ancelad one of the Russian authorities upon the subject, concurs stating causes of flashing failure here quite succinctly:
1) Wrong firmware 2) Corrupt firmware image - compare checksums 3) Broken NAND http://4pda.ru/forum/index.php?s=&sh...ost&p=26036061 Use of "zeroize device" unnecessarily also seems to be implicated as here: http://nokiasymbianplus.blogspot.com...-comandos.html |
Re: Fix Nokia n9 deadly cmt issue
Quote:
Will try this when I get home :) |
Re: Fix Nokia n9 deadly cmt issue
Quote:
Thanks again guys, for helping out. |
Re: Fix Nokia n9 deadly cmt issue
Bad idea to flash 003 variant, that is for sure to give you troubles (you cant revert that CMT)
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
It does not start due to: "Looking for bootable USB device, waiting" And nothing else happens, wa waiting about 40 minutes before I gave up. I am currently looking for a new motherboard I guess. Thanks anyhow |
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
Also got my hands on a new, never used battery as well. Will surely be asking some questions, the ultimate goal is to use the N9 as a daily driver ! |
Re: Fix Nokia n9 deadly cmt issue
Quote:
did you fix it? |
Re: Fix Nokia n9 deadly cmt issue
Quote:
Could you confirm that, to restore Meego only and the original kernel the command is Code:
flasher -F <firmware-image> --flash-only=kernel -f -R |
Re: Fix Nokia n9 deadly cmt issue
This command will let the battery charge and flash the kernel only when reached 11%.
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
I see HW failure instead of RPL file damage setting in /dev/mtd1.. :hopeless
|
All times are GMT. The time now is 05:00. |
vBulletin® Version 3.8.8