Notices


Reply
Thread Tools
tomislav's Avatar
Posts: 298 | Thanked: 355 times | Joined on Sep 2010
#11
Originally Posted by filip.pz View Post
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
it is because is broken security part in rpl on n9 and since there is no backup of the original one you cant fix it unless there is new rpl file specific for that phone, which Nokia used to sell them to small cellphone repair shops

Last edited by tomislav; 2015-09-29 at 16:06.
 
Posts: 992 | Thanked: 3,225 times | Joined on Oct 2014
#12
Originally Posted by tomislav View Post
atf and best
Hmm OK later i will see what can be done with ATF (Nitro)
__________________
You can still support my work by donation - click here

ETH: 0xf7544913017653719259c92d38d50d9d55f7c6cd
 
tomislav's Avatar
Posts: 298 | Thanked: 355 times | Joined on Sep 2010
#13
Originally Posted by lokai View Post
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)?
tried that, getting this error

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
 
nokiabot's Avatar
Posts: 1,973 | Thanked: 1,819 times | Joined on Mar 2013 @ india
#14
Originally Posted by tomislav View Post
atf and best
aha i dont have acces to them
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
i am just curious why the technician didnt check whats wrong yet
thanks
 
nokiabot's Avatar
Posts: 1,973 | Thanked: 1,819 times | Joined on Mar 2013 @ india
#15
Originally Posted by tomislav View Post
it is because is broken security part in rpl on n9 and since there is no backup of the original one you cant fix it unless there is new rpl file specific for that phone, which Nokia used to sell them to small cellphone repair shops
rpls are unique to each devices unlike pm actualy pm feild 308 and 128 which cannot be reconstructed so its advisable to backup
or it finally ends up in generating ask files and associated troubles there in
also i dont think nokia sold em ?
source ?
 
Posts: 79 | Thanked: 130 times | Joined on Feb 2015 @ Poland
#16
So can I make a backup of RPL file from working device? (before its dead?)
 

The Following User Says Thank You to badpixel For This Useful Post:
tomislav's Avatar
Posts: 298 | Thanked: 355 times | Joined on Sep 2010
#17
Originally Posted by badpixel View Post
So can I make a backup of RPL file from working device? (before its dead?)
Yes, highly advisable
 
OVK's Avatar
Posts: 534 | Thanked: 879 times | Joined on May 2008 @ Finland
#18
Originally Posted by tomislav View Post
Yes, highly advisable
How can this backup be made? And how can it be used to recover N9 if the cmt issue arises?
__________________
Hattivattein lauma sankka suur!
 
Community Council | Posts: 3,984 | Thanked: 9,416 times | Joined on May 2012 @ Southerrn Finland
#19
no way if it is a HW issue...
 
tomislav's Avatar
Posts: 298 | Thanked: 355 times | Joined on Sep 2010
#20
Originally Posted by juiceme View Post
no way if it is a HW issue...
yeah but there is no way finding if is hardware at all at least without rpl file

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
 
Reply

Tags
nokia n9

Thread Tools

 
Forum Jump


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