![]() |
Fix Nokia n9 deadly cmt issue
Now, Confirmed by technician (not Nokia) of course, thanks god those still exist, deadly cmt issue in Nokia n9 that is causing to loose all gsm and telephony functions as well as imei can be fix only by new
RPL File RPL - RPL is a structured programming language. it used to be provided and sold to technicians by Nokia care and now that support is gone we are left alone if anyone know more info and how or where to get rpl file for nokia N9 can contribute to this topic it would save a lot of n9s there |
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
looked into local disc but n9 isint there let me dive more as i never tested a n9
|
Re: Fix Nokia n9 deadly cmt issue
after a quick check on the boards looks like its doable with cyclone or mxkey but its not as simple as writing a rpl file though
you need to ask your technician what tools he got and activations/credits i maybe able to help more then |
Re: Fix Nokia n9 deadly cmt issue
I know those RPLs used for Symbian devices.
But are they really used for N900/N9? What about flashing matching firmware on device completely (with errors) and then flashing CMT only with chinese firmware (003)? |
Re: Fix Nokia n9 deadly cmt issue
err i know how to work with those boxes but not much about the code aspects of the phones ;
|
Re: Fix Nokia n9 deadly cmt issue
op pls respond quick
|
Re: Fix Nokia n9 deadly cmt issue
will ask technician today
|
Re: Fix Nokia n9 deadly cmt issue
I have two N9 with faulty CMT (one resets after entering PIN, and one can't communicate with CMT at all - ie flasher can't flash CMT), so I've done my "homework", and found this a while back:
http://talk.maemo.org/showpost.php?p...3&postcount=87 In other words: If you can't flash CMT that phone will be brick for ever |
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\windows\system32>cd.. C:\Windows>cd.. C:\>cd n9 C:\N9>Flasher -f -F china.bin --flash-only=cmt -f -R flasher 3.12.1 (Oct 6 2011) Harmattan ERROR: Only single flash option is allowed ERROR: Error processing option -f C:\N9>Flasher -f -F china.bin --flash-only=cmt 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 1501 NOLO version 2.3.6 Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.480.04.1_PR_480 Sending ape-algo image (7096 kB)... 100% (7096 of 7096 kB, avg. 14542 kB/s) Suitable USB interface (phonet) not found, waiting... 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_003 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 27 %, 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:\N9>Flasher -f -F china.bin --flash-only=cmt 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. 1501 Server implements softupd protocol version 1.8 Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_003 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 27 %, 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 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 |
Re: Fix Nokia n9 deadly cmt issue
Quote:
ill check their interfaces later also i am out should be back in two days most probably it should start with backup rpl pm then wipe phone and reflash then check for simlocks to proceed ok so to make the process a little more faster get your n9 to them ask why they coudnt repair it lisen to it then ask them to flash your phone then do a check info , simlock check , sx4 authorization i dont know their interface so you may need to use a little common sence basically i want the logs or rather better click photos easiest or if this is too much wait for me to explore or rather remote me to the machine :D i am just curious why the technician didnt check whats wrong yet thanks |
Re: Fix Nokia n9 deadly cmt issue
Quote:
or it finally ends up in generating ask files and associated troubles there in also i dont think nokia sold em ? source ? |
Re: Fix Nokia n9 deadly cmt issue
So can I make a backup of RPL file from working device? (before its dead?)
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
no way if it is a HW issue...
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
two technicians told me that they could fix it with new rpl file or they were shooting blanks who knows, but according to them is fixable with rpl |
Re: Fix Nokia n9 deadly cmt issue
Hi.
Does anyone know if this can help at least to make a backup? http://manpages.ubuntu.com/manpages/.../0xFFFF.1.html There's a "dump" option.... Regards. |
Re: Fix Nokia n9 deadly cmt issue
The "Supported devices" section should be a giveaway.
|
Re: Fix Nokia n9 deadly cmt issue
How to make a RPL backup? USB cable and pirated soft is enoufg, or some special hardware is needed?
Could you give me examples of such soft and hw. (I'm scared I will break mine phone soon) |
Re: Fix Nokia n9 deadly cmt issue
https://github.com/filippz/kernel-ad...1c54b344ffc9fd
Quote:
|
Re: Fix Nokia n9 deadly cmt issue
Quote:
For conspiracy theory supporters: last official update for our N9 was "3G network compatibility fix" For HW enthusiast: google for N9 Schematics and check how's CMT connected. According to schematics CMT is connected to OMAP3630 only, so there is no other way to access it if OMAP3630 is not able to communicate with it. Since I've destroyed my N9 that had this issue (I have another with different CMT problem), can someone paste dmesg output? I guess there should be something that will tell us if OMAP can communicate with CMT and (in case it does) what's wrong. I still have my money on HW issue. |
Re: Fix Nokia n9 deadly cmt issue
please continue here: http://talk.maemo.org/showthread.php?t=98857
i have a similar problem but i can boot into my n9 can you tell me what to do |
Re: Fix Nokia n9 deadly cmt issue
Found this and don't know if it helps
They talk about Factory BB5 RPL Writing Fixed http://www.clangsm.com.br/topic/3828...nctions-added/ |
Re: Fix Nokia n9 deadly cmt issue
Hello Friends,
I got a nokia N9 from an online store last week. it came with Chinese Firmware. so i wasn't comfortable with it so i decided to flash it to another variant (Eurasia to be specific) using phoenix flasher. During the flashing it got to 80% then stopped with an error. Since then i couldn't connect to the PC anymore. Now, it starts up with a warning turned on that my phone is no more supported by nokia ....etc that i should reinstall the software that came with the phone. booting to desktop, my imei,network are all gone, showing SIM error. Now,the phone freezes with screen washing out until i restart it. it show "Phone connected in non-compatible mode"making it difficult to re-flash. Please help me guys. i just used the phone for just a week. thanks. |
Re: Fix Nokia n9 deadly cmt issue
Have a look in this thread and see if it appertains to your situation:https://talk.maemo.org/showpost.php?...83&postcount=6
|
Re: Fix Nokia n9 deadly cmt issue
I have the exact same issue.
The phone battery was drain (due to old phone, nothing unexpected.) I start the flasher and having a hard time relocating the .bin image to a specific folder to get access to it from the flasher. My intention was as u can understand to charge the drain battery with the flasher. What I did not know was that the phone had charged during the time of relocating that .bin file. I start the flash sequence, and HOLY **** the battery is at 17%, the process keep going. Try to stop it as fast as i can. But no. Now it seems it wont flash any firmware I try. |
Re: Fix Nokia n9 deadly cmt issue
I am sorry but I do not understand.
If this assumption that you started flashing to charge battery and only after a few minutes you started again and this time the flashing process started. And then you stopped it (how?) then you might have produced a problem. Try the cold flashing switch '-c'. |
Re: Fix Nokia n9 deadly cmt issue
Quote:
then I had trouble locating the .bin file in CMD, so I messed with that trouble some time before I could do the "-f -F *image* Then it already had charged a bit. Stopped the process with Ctrl + C |
Re: Fix Nokia n9 deadly cmt issue
Right now I am trying to flash my phone, and I am following this line
that I found in another thread: flasher -F main.bin -F emmc.bin --erase-user-data=secure --erase-mmc=secure --no-preserve -f -R But what should I write as emmc.bin when there is nothing on the phone? |
Re: Fix Nokia n9 deadly cmt issue
This is the errors I get
Image mmc not present Image tar skipped Image config skipped Battery level 54 %, 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 ] 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 3381 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 1953 kB/s] [f] rootfs [pending 0 % 1024 / 1170282 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 3381 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 1953 kB/s] [f] rootfs [pending 0 % 1024 / 1170282 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 bb5_rdc_cert_read failed bb5_rdc_cert_read failed mmc: sfdisk returned status 1 mmc: Could not remove mount directory /tmp/sudmmccYoyLH/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
I know very well how to flash but I am not a Nokia engineer knowing all those error messages.
Please follow also all sub links in https://talk.maemo.org/showpost.php?...01&postcount=9 for a possible answer :( But I have no idea what you wanted to achieve? Simply charging by flasher: 'flasher -i' is enough. Now you started flashing firmware and interrupted. Definitely not a good idea, a NoGo. Is this a chinese phone? Why did you not try my advice with parameter '-c'? And flasher throws a big warning when started, did you read that? I propose you read a bit more about flashing process in wiki and/or itsnotabigtruck flashing thread. And give more info what device, aims, actions, output. btw: emmc.bin is a synonym for a file containing the contents of the 'hard disk'. You do not really need it but it can be fetched from the net as well as the firmware files. |
Re: Fix Nokia n9 deadly cmt issue
Slightly off topic:
I am not using my N9 anymore, but it has installed Ubiboot with NitDroid as seconday rom. However it has the problem that it doesn't charge if its off. How to remove completely NitDroid and Ubiboot without loosing the data on MeeGo and restoring the battery charge when powered off? |
Re: Fix Nokia n9 deadly cmt issue
Quote:
All you need to do is flash a regular kernel to the device to replace the ubiboot kernel and you are done :D If you have just Nitdroid and no Nemo on your device it is easy to reclaim the space used by Nitdroid after you boot to normal Harmattan; just remove the directory containing the Android subsytem and that's it. If you hsve also Nemo/Sailfish/Ubunti/Firefox/whatever it is a bit more difficult since that means your device has been repartitioned accordingly. That's doable too, but requires a bit more expertise. |
Re: Fix Nokia n9 deadly cmt issue
@Gamerouge Best guess is the flash memory of device have gone bad, Not much to do about it.
|
Re: Fix Nokia n9 deadly cmt issue
@claustn
You could try flasher -i trick. Or just connect/disconnect a few times to give battery a bit of charge to load at least the second kernel and start (with charging). That is how I revivdd my N9s when emptied via Nitdroid. |
Re: Fix Nokia n9 deadly cmt issue
Quote:
Thanks for your answer. I simply followed the thread about the dead battery, and assumed I would see the battery precente rising if I used the -f -F command as well. This is an european device, 16gb cyan. Would you mind writing out the whole line for a cold flashing? I know I made some mistakes. Best regards |
All times are GMT. The time now is 02:14. |
vBulletin® Version 3.8.8