Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 9 hrs, 59 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 14 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 2 days, 2 hrs ago -
n770 youtube video (0)
to General by nmdv - 6 days, 1 hr ago - more...
Artisn |
2012-03-27
, 23:18
|
|
Posts: 5 |
Thanked: 2 times |
Joined on Mar 2012
|
#131
|
Originally Posted by dumpystig
Sorry. Although it carries some hints about keeping files at one place, i don't think meego's .bin file is that much all over the place
 |
|
2012-03-27
, 23:23
|
|
Posts: 464 |
Thanked: 338 times |
Joined on Feb 2011
@ UK, Northwest
|
#132
|
No prob.
Let us know if/how you sort your N9.
Let us know if/how you sort your N9.
|
|
2012-03-27
, 23:50
|
|
Posts: 5 |
Thanked: 2 times |
Joined on Mar 2012
|
#133
|
whenever i get to table of progress, cmt-mcusw line never completes and rootfs line never gets over 4 or 5% before the whole process stalls.
Might it be that i partially damaged my devices memory?
~2 weeks ago using the same flasher/image/flasher i got it going after bricking due to use of "nokia software updater".
Might it be that i partially damaged my devices memory?
~2 weeks ago using the same flasher/image/flasher i got it going after bricking due to use of "nokia software updater".
|
|
2012-03-27
, 23:55
|
|
Posts: 464 |
Thanked: 338 times |
Joined on Feb 2011
@ UK, Northwest
|
#134
|
Not sure what/if anything may be damaged but something is definitely corrupted. If you have tried several times and are still unsuccessful then I reckon you've nothing to lose by trying the method in the vid I linked to.
|
|
2012-03-28
, 00:17
|
|
Posts: 5 |
Thanked: 2 times |
Joined on Mar 2012
|
#135
|
Sorry to still emphasize - Phoenix is symbian targetted s/w. although it's for nokia devices, N9 cannot really be considered such. Elop clearly stated so.
| The Following User Says Thank You to Artisn For This Useful Post: | ||
|
|
2012-03-28
, 06:45
|
|
Posts: 464 |
Thanked: 338 times |
Joined on Feb 2011
@ UK, Northwest
|
#136
|
No disrespect, but F uck Elop.
I have used this method successfully on my N8, E7 and N9 with no problems whatsoever. And it's easier than the method at page 1 in this thread.
If you presently have a N9-brick then you have nothing to lose by trying this...
I have used this method successfully on my N8, E7 and N9 with no problems whatsoever. And it's easier than the method at page 1 in this thread.
If you presently have a N9-brick then you have nothing to lose by trying this...
| The Following User Says Thank You to dumpystig For This Useful Post: | ||
|
|
2012-03-28
, 07:13
|
|
Posts: 10 |
Thanked: 4 times |
Joined on Mar 2012
|
#137
|
Firstly I want to say a massive thanks to itsnotabigtruck for the great howto.
Before i update my phone I am hoping that my few questions can be answered by someone who knows a little more than me.
I have an Australian carrier branded phone so I know i want to use a 005 firmware
I have a question about which files to download
I know the guide says "Click Unmark All, then scroll to the bottom of the Files section. Tick the boxes for the two files starting with DFL61_HARMATTAN."
I am wondering what the other files are for and do i actually need them?
There are some BIN files
xxx.......keyidentifiers32
ape_hwc_xxxx
ape_cc_xxx
cmt_hwc_xxxx
cmt_cc_xxx
simlock_maemo_xxxx (2 of these files)
RM696_xxxxxxx_signature
And a few other files ending in pcx, vpl, xml and dcp
I have seen some quides/videos where people use all of the files and some (Like this guide) which says they are not needed.
If I want to keep my carrier customisation should i ignore the EMMC file or is it best to use the newer non carrier branded PR1.2 EMMC file when updating from an old PR1.x?
When my carrier releases PR1.2 i am guessing that it will be possible to replace the generic 005 firmware with PR1.2 firmware from my carrier as it will not be a downgrade?
Thanks!
Before i update my phone I am hoping that my few questions can be answered by someone who knows a little more than me.
I have an Australian carrier branded phone so I know i want to use a 005 firmware
I have a question about which files to download
I know the guide says "Click Unmark All, then scroll to the bottom of the Files section. Tick the boxes for the two files starting with DFL61_HARMATTAN."
I am wondering what the other files are for and do i actually need them?
There are some BIN files
xxx.......keyidentifiers32
ape_hwc_xxxx
ape_cc_xxx
cmt_hwc_xxxx
cmt_cc_xxx
simlock_maemo_xxxx (2 of these files)
RM696_xxxxxxx_signature
And a few other files ending in pcx, vpl, xml and dcp
I have seen some quides/videos where people use all of the files and some (Like this guide) which says they are not needed.
If I want to keep my carrier customisation should i ignore the EMMC file or is it best to use the newer non carrier branded PR1.2 EMMC file when updating from an old PR1.x?
When my carrier releases PR1.2 i am guessing that it will be possible to replace the generic 005 firmware with PR1.2 firmware from my carrier as it will not be a downgrade?
Thanks!
|
|
2012-03-28
, 10:33
|
|
Posts: 5 |
Thanked: 2 times |
Joined on Mar 2012
|
#138
|
Phew! 
The Phoenix raised my brick from ashes.
Thanks dumpystig!
The Phoenix raised my brick from ashes.
Thanks dumpystig!
|
|
2012-03-28
, 14:05
|
|
Posts: 20 |
Thanked: 0 times |
Joined on Mar 2012
|
#139
|
Why I Can Not Flash My Device With Orginal Product Code ?
C:\Program Files\Nokia\Flasher>flasher.exe -c -F DFL61_HARMATTAN_30.2012.07-1.33
3.2_PR_LEGACY_333_ARM_RM-696_PRD_signed.bin -f -R
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.
Using 1st image to detect HW
Suitable USB interface (bootrom) not found, waiting...
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 63
e7 d5 29 d1 d7 5e 26 bc 94 04 a5 46 ea 8f 7e 68
64 30 3e 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
HW variant: HS
Found matching 1st (916)
Sending 1st image (26496 bytes)... done.
Sending HWID query... Received 11 bytes from 1st
ERROR: ReadFile error 31
usb_bulk_read: No error
Got HWID: RM-696:1603
Suitable USB interface (bootrom) not found, waiting...
Waiting for ASIC id...
Got 69 bytes.
ASIC ID:
05 01 05 01 36 30 07 07 13 02 01 00 12 15 01 63
e7 d5 29 d1 d7 5e 26 bc 94 04 a5 46 ea 8f 7e 68
64 30 3e 14 15 01 12 dd 2f 66 d4 55 fe 19 2c 62
b9 b8 e2 65 0a fc 1d 9f 3f 90 15 09 01 13 bf 3e
ef 15 52 e7 03
Sending 2nd image (26112 bytes)... done.
Sending ping... pong.
Sending ape-algo (7273344 bytes)... done.
Suitable USB interface (bootloader/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
Image SW version DFL61_HARMATTAN_30.2012.07-1.333.2_PR_333
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped
Battery level 100 %, continuing.
image [state progress transfer flash speed]
---------------------------------------------------------------------
[_] cert-sw [init 0 % 0 / 0 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 ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 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 10: Security failure
image [state progress transfer flash speed]
---------------------------------------------------------------------
[f] cert-sw [init 0 % 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 ]
[ ] xloader [pending 0 % 0 / 0 kB NA ]
[ ] secondary [pending 0 % 0 / 0 kB NA ]
[ ] kernel [pending 0 % 0 / 0 kB NA ]
[ ] rootfs [pending 0 % 0 / 0 kB NA ]
Fetching error list:
========================================
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Progress bar initialization failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1331081272)
[Pipe 0] Finishing in error state with status 10
========================================
ERROR: Failed to flash images
C:\Program Files\Nokia\Flasher>
|
|
2012-03-28
, 16:54
|
|
Posts: 464 |
Thanked: 338 times |
Joined on Feb 2011
@ UK, Northwest
|
#140
|
Originally Posted by Artisn
No prob, glad it worked for you. Maybe others will give it a try if in the same boat.
Phew!
The Phoenix raised my brick from ashes.
Thanks dumpystig!
Now enjoy your resurected N9 again
And it is a Nokia
