maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N9 / N950 (https://talk.maemo.org/forumdisplay.php?f=51)
-   -   probably broke my n9 (https://talk.maemo.org/showthread.php?t=99678)

kick 2017-08-09 14:02

Re: probably broke my n9
 
i was wondering is it possible to write the cmt partition completely as in /dev/cmt with the files in the 003 variant dumped from another n9 by using aegis and inception in conjugation to delete the cmt completely and paste the new files there

EDIT-probably a recipie for brick but still is it possible and if it is can some link the dumped files

mr_pingu 2017-08-09 14:13

Re: probably broke my n9
 
C:\Program Files\Nokia\Flasher>flasher -f -F china.bin --flash-only=cmt --no-preserve

You did only flash CMT, what happens if you flash full 003 with --no-preserve or erase?

Probably you can extract it from the image.

Does the flasher have unpack option?
I know that 0xFFFF has for N900 but not for N9 yet.

kick 2017-08-09 14:44

Re: probably broke my n9
 
trying a zeroise with --no-preserve as you suggested now will report in a little while(as soon as its done)

EDIT- nope no progress on zeroise with --no-preserve(tough i guess that was to be expectedwell heres the log anyways
Code:

C:\Windows\system32>cd C:\Program Files\Nokia\Flasher

C:\Program Files\Nokia\Flasher>flasher -f -F china.bin --no-preserve --erase-user-data=secure
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.

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_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 16427 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

Battery level 85 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_003
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 89 %, 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    [finishing  75 %    6050 /    6050 kB    3304 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    3244 kB/s]
[_] rootfs      [writing    10 %  143360 / 1188233 kB    6400 kB/s]
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    3304 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    3244 kB/s]
[x] rootfs      [finished  100 % 1188233 / 1188233 kB    8822 kB/s]
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
MTC_POWER_OFF not received
CMT RFS failed
[Pipe  7] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>flasher -f -F china.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.

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_003
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 90 %, continuing.

    image        [state    progress        transfer    flash speed]
---------------------------------------------------------------------
[x] cert-sw      [finished  100 %      1 /      1 kB      NA    ]
[x] mmc          [finished  100 %  261587 /  261587 kB  10922 kB/s]
Success

C:\Program Files\Nokia\Flasher>


kick 2017-08-09 14:58

Re: probably broke my n9
 
the only problem im having now is whenever i insert the sim card the imei goes away therefore i am unable to connect to the network i reboot the device and the imei is fine and present

mr_pingu 2017-08-09 15:00

Re: probably broke my n9
 
Quote:

Originally Posted by kick (Post 1532328)
trying a zeroise with --no-preserve as you suggested now will report in a little while(as soon as its done)

EDIT- nope no progress on zeroise with --no-preserve(tough i guess that was to be expectedwell heres the log anyways
Code:

C:\Windows\system32>cd C:\Program Files\Nokia\Flasher

C:\Program Files\Nokia\Flasher>flasher -f -F china.bin --no-preserve --erase-user-data=secure
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.

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_001
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 16427 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

Battery level 85 %, continuing.
Erasing, this may take a while.
Erase done.
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_003
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 89 %, 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    [finishing  75 %    6050 /    6050 kB    3304 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    3244 kB/s]
[_] rootfs      [writing    10 %  143360 / 1188233 kB    6400 kB/s]
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    3304 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    3244 kB/s]
[x] rootfs      [finished  100 % 1188233 / 1188233 kB    8822 kB/s]
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
MTC_POWER_OFF not received
CMT RFS failed
[Pipe  7] Finishing in error state with status 1
========================================

ERROR: Failed to flash images

C:\Program Files\Nokia\Flasher>flasher -f -F china.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.

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_003
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 90 %, continuing.

    image        [state    progress        transfer    flash speed]
---------------------------------------------------------------------
[x] cert-sw      [finished  100 %      1 /      1 kB      NA    ]
[x] mmc          [finished  100 %  261587 /  261587 kB  10922 kB/s]
Success

C:\Program Files\Nokia\Flasher>


I'm giving up. Would gladly upload my CMT but it's no 003 CMT if that matters. But I guess it will change you're N9 into a brick like you said.

You could try to force flash / downgrade using JAF or any of the other Baseband 5 flashing tools I suggested. But again no guarantees.

Edit: Did you try cold-flash. Probably won't work but you can try

kick 2017-08-09 15:06

Re: probably broke my n9
 
i would gladly try anything at this point in time to fix the cmt so if anyone reading the thread has any clear ideas please tell me and please explain the steps required briefly(just dont tell me to do anything that has a brick possibility of 50% or more)

kick 2017-08-09 15:14

Re: probably broke my n9
 
for now ill just start uploading the firmware files to my mega account as its really hard these days finding fixed firmware files

aspergerguy 2017-08-10 14:01

Re: probably broke my n9
 
Quote:

Originally Posted by mr_pingu (Post 1532311)
It seems that you can create RPL from PM backup. Making a PM backup and then make RPL from it and write RPL might fix it too.
Maybe Cyclone Box software can be hacked to work over USB too.Or maybe it works out of the box over USB.

It is Cyclone Box/Cyclone Key Reloaded which achieves the function you mentioned:
http://forum.gsmhosting.com/vbb/f528...added-1483437/

Surprisingly although software has not been updated for years, support server moved to new address in January 2017. consequently was able to update my Cyclone Key Reloaded and Read PM upon N9 via USB connection without any modification.
https://s28.postimg.org/lc48jihz1/Cyclone_Reloaded.jpg

kick 2017-08-14 20:26

Re: probably broke my n9
 
so how does it work gimme some steps and ill do em(as ive never used something like this before so what i need is the link to it and what to do to get a rpl backup ill try and figure the rest out from there)

aspergerguy 2017-08-16 19:06

Re: probably broke my n9
 
Sorry for not getting back sooner, beginning to think that Cyclone can only only backup PM or write factory BB5 RPL but not backup RPL upon N9. Any attempt fails with attempting to put device in RAW mode. There is a backup RPL feature within Flashing function although have never used Cyclone for this feature but always Harmattan flasher, so can't confirm validity of what is saved.


All times are GMT. The time now is 14:55.

vBulletin® Version 3.8.8