|
2013-09-21
, 10:12
|
Posts: 131 |
Thanked: 22 times |
Joined on Sep 2012
@ India
|
#962
|
@suyog, what is your problem? same cmt-mcsuw? say please,
1)did you successfully flashed your device with last firmware version?
2)put log here please or attach a screen phoyo of log of your actions on flashing it
3)i dont think so that is hardware issue..hope that not.
3)which version is your device? is this 003 (brand but factory shipping China)
a little tip : go to the settings>about product, take a snapshoot the place where shows barcode. send this picture to your computer,scan this picture via any barcode scanner - you will get the wright product code which with you find the wright firmware to flash cmt - i did like that. (ofcourse if your device booting in OS)
|
2013-09-21
, 10:23
|
Posts: 131 |
Thanked: 22 times |
Joined on Sep 2012
@ India
|
#963
|
Ok finally fixed it and for people having similar issues flashing their n9 this might come in handy.
It appears that not only does the variant number have to be higher or equal, also the following numbers have to be higher. For example I had
DFL61_HARMATTAN_40.2012.21-3.350.3
installed. It appears that this actual firmware does not really exist for my product code. It did for a previous PR but got changed to variant 430, but as I updated via OTA the firmware variant never got changed to the correct 430. It kept the 350.3 part and replaced the 40.2012.21-3 to resemble the PR1.3.
Having to flash my phone now there is only this 430 variant available for my product code which is precisely:
DFL61_HARMATTAN_40.2012.21-3.430.01.1
One would think coming from a 350, flashing to 430 wouldn't be a problem because the variant number is higher. But no, it doesn't work because of big a** version numbering inconsistency fail. As you can see it's actually variant 350.3 vs 430.01(.1) and apparently the numbers following the 350 and 430 variant codes ALSO WILL BE COMPARED.
So I was looking around for a firmware that has both the variant number and what follows after it at equal or higher numbers and I found this N9 Rm-696 Optimus Pt V1-black - 16g firmware named:
DFL61_HARMATTAN_40.2012.21-3.398.3
And voilá that damned thing works again.
|
2013-09-25
, 09:40
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerĝd, DK
|
#964
|
Thanks you were right this one function without USB or Warnings trouble, even if I dont know why
|
2013-09-27
, 19:43
|
|
Posts: 60 |
Thanked: 34 times |
Joined on Dec 2012
@ St Helens, England.
|
#966
|
|
2013-10-05
, 14:47
|
Posts: 19 |
Thanked: 1 time |
Joined on Dec 2011
|
#967
|
|
2013-10-06
, 09:58
|
Posts: 19 |
Thanked: 1 time |
Joined on Dec 2011
|
#968
|
|
2013-10-06
, 14:12
|
Posts: 646 |
Thanked: 1,124 times |
Joined on Jul 2010
@ Espoo, Finland
|
#969
|
|
2013-10-13
, 06:53
|
Posts: 4 |
Thanked: 0 times |
Joined on Oct 2013
|
#970
|
Sobans-MacBook-Air:~ Soban$ flasher -F /Users/Soban/Desktop/059J228_RM-696\ NDT\ MEA1\ MEA2\ BLACK\ 64GB/DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_006-OEM1-958_ARM.bin -f
flasher 3.12.1 (Oct 5 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...
USB device found at bus 250, device address 6.
Device serial number is N/A
Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_30.2012.07-1_PR_006
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 19990 kB/s)
Suitable USB interface (phonet) not found, waiting...
USB device found at bus 250, device address 6.
Device serial number is
Raw data transfer EP found at EP2.
Ping attempt 1 (250 ms)
Server application: 1.7.2
Found product RM-696 rev. 1601
Server implements softupd protocol version 1.8
Image SW version DFL61_HARMATTAN_40.2012.21-3_PR_006
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped
Battery level 36 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[x] cert-sw [finished 100 % 1 / 1 kB NA ]
[_] cmt-2nd [finished 100 % 95 / 95 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 [writing 37 % 2048 / 2714 kB 3957 kB/s]
[_] rootfs [writing 0 % 2048 / 978983 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 3455 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 3615 kB/s]
[f] rootfs [writing 0 % 3072 / 978983 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: handle_buffer failed in lzo decompress (-1)
[Pipe 5] Finishing in error state with status 1
========================================
ERROR: Failed to flash images
Tags |
flashing, nokia n9 |
Thread Tools | |
|
And now it might have RPL problem. Is there any way to fix it or just take it to nokia carepoint?
Last edited by Timpaxi; 2013-09-29 at 19:07.