Reply
Thread Tools
Posts: 13 | Thanked: 3 times | Joined on Jul 2013
#861
Hi Guys, Got my N9 from ebay - worked very well on day 1. Now its dead. When I charge the Nokia logo shows up and then the battery sign with the exclamation mark. Thats it.

I thought it was a battery problem - so I downloaded the latest firmware and tried to charge the battery through flasher.

The Battery says - its a 100%.And the flasher gave me a message saying "Downgrade Not Allowed"

Checked the firmware through flasher -i and I get DFL61_HARMATTAN_40.2012.21-3.335.1_PR_335

I have tried the Chinese Firmware and the 001 firmware so far - Both gave me the same errors.

I have tried these 2 firmwares:
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_001-OEM1-958_ARM
DFL61_HARMATTAN_40.2012.21-3_PR_LEGACY_003-OEM1-958_ARM

Any help trying to revive my N9?

P.S. : I was trying to get my contacts through Bluetooth to N9 when the phone went kaput

Last edited by Pratyush; 2013-07-06 at 03:23. Reason: Add details
 
Posts: 1 | Thanked: 0 times | Joined on Jul 2013
#862
Hi there,

I thought I did a "successful" firmware flash on my phone but the screen STAYS BLANK when I start it up.. any ideas?

Current status:

1. I made sure to re-imaged with the correct bin corresponding to my phone model (059K114)

2. Power = 70% (according to what flasher says when I re-image)

3. I have tried enabling rd mode - no change - the LED light blinks like mad initially then changes rates over time so "something" is happening..

4. it doesn't do that quick vibration like it used too when i turn it on..

I've tried my best to search for another option BEFORE posting but I've run out of options.. THANKS in advance!

Last edited by Newby; 2013-07-06 at 03:47.
 
Posts: 13 | Thanked: 3 times | Joined on Jul 2013
#863
Hi Guys,

I am now at a total loss how to resolve this.

I received the phone a couple days back. I was using it normally when it suddenly stopped.

I found out the Firmware in my phone to be:
DFL61_HARMATTAN_40.2012.21-3.335.1_PR_335

I downloaded the firmware from the links and started the flashing - nothing works. I get interrupted between 37-44% . I have tried the cold flash as well - does the same thing.

The error I am getting is this:
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 19975 ms
ERROR: WriteFile(0 of 14) timeout (5000 ms); tried 14

Fetching error list:
ERROR: WriteFile(0 of 28) timeout (5000 ms); tried 28
ERROR: WriteFile(0 of 10) timeout (5000 ms); tried 10



Here is the complete log:


f:\Program Files\Nokia\Flasher>flasher -f -F main_335.bin -c
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 45
96 2a 39 6d 33 aa 70 ed 58 07 b3 a7 79 0c a1 bb
90 4d 66 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 45
96 2a 39 6d 33 aa 70 ed 58 07 b3 a7 79 0c a1 bb
90 4d 66 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 (7273728 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_40.2012.21-3.335.1_PR_335
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 100 %, 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 0 % 6050 / 6050 kB 2866 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 2209 kB/s]
[_] rootfs [writing 41 % 409600 / 979170 kB 8997 kB/s]
ERROR: ReadFile(65540) GetOverlappedResult() error 2 timeout 19975 ms
ERROR: WriteFile(0 of 14) timeout (5000 ms); tried 14

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 2866 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 2209 kB/s]
[f] rootfs [writing 0 % 409600 / 979170 kB 8997 kB/s]
Fetching error list:
ERROR: WriteFile(0 of 28) timeout (5000 ms); tried 28
ERROR: WriteFile(0 of 10) timeout (5000 ms); tried 10

ERROR: Failed to flash images
------------------------------------------------------------------------------------
I
Please can anyone help. If it helps I got the phone off ebay and it has 059M7K1 in the Sim tray.
 
joerg_rw's Avatar
Posts: 2,215 | Thanked: 12,631 times | Joined on Mar 2010 @ SOL 3
#864
DO NOT COLDFLASH when your device does not need it!
Coldflashing is solely to restore a broken bootloader, and obviously your bootloader isn't broken since it boot up to display stuff on screen and even starts flashing procedure. If it was broken then your device would act _really_ bricked and not show any sign of life (except BOOTROM "hello" via USB, that gets detected by flasher). ONLY THEN you should consider coldflashing - after you made sure it's not your battery that's defect.

It's not like coldflashing could do massive harm to your device since you can repeat it under nearly all circumstances (unlike flashing BIOS of your PC, which might render your motherboard bricked when you abort it), but definitely it won't usually fix anything for you, and just may introduce another level of failure cause that complicates things even further.

on the errors you encounter: try a better USB cable and a different port on your PC, those errors *might* be simple data corruption on USB protocol.

/j
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member

EX Hildon Foundation approved
Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/

IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N

Last edited by joerg_rw; 2013-07-06 at 14:47.
 
Posts: 13 | Thanked: 3 times | Joined on Jul 2013
#865
Originally Posted by joerg_rw View Post
DO NOT COLDFLASH when your device does not need it!
Coldflashing is solely to restore a broken bootloader, and obviously your bootloader isn't broken since it boot up to display stuff on screen and even starts flashing procedure. If it was broken then your device would act _really_ bricked and not show any sign of life (except BOOTROM "hello" via USB, that gets detected by flasher). ONLY THEN you should consider coldflashing - after you made sure it's not your battery that's defect.

It's not like coldflashing could do massive harm to your device since you can repeat it under nearly all circumstances (unlike flashing BIOS of your PC, which might render your motherboard bricked when you abort it), but definitely it won't usually fix anything for you, and just may introduce another level of failure cause that complicates things even further.

on the errors you encounter: try a better USB cable and a different port on your PC, those errors *might* be simple data corruption on USB protocol.

/j
ok I have changed the USB Cable - I have tried 2 different computers. But I have the same problem. Any other ideas?
 
Posts: 13 | Thanked: 3 times | Joined on Jul 2013
#866
Originally Posted by Pratyush View Post
ok I have changed the USB Cable - I have tried 2 different computers. But I have the same problem. Any other ideas?
Do I have any choice guys? Please respond.

Should I take this to Nokia Care? I would be charged for this but I am ok with it, as long as they fix it.
 
Posts: 131 | Thanked: 22 times | Joined on Sep 2012 @ India
#867
Originally Posted by Pratyush View Post
Do I have any choice guys? Please respond.

Should I take this to Nokia Care? I would be charged for this but I am ok with it, as long as they fix it.
Are you from India?
DO NOT take N9 to Nokia care, many nokia care guys hardly have any idea about N9. They will tell very high service charge and will not be confident of fixing it.
 
Posts: 6 | Thanked: 3 times | Joined on Feb 2013
#868
Could someone possibly help me?

I'm unable to flash to UK or Aus or Denmark FW 001, 299 or 340 variants.

Here is my log attached:

C:\Program Files\Nokia\Flasher>flasher -f -F14991FD9_DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_LEGACY_340_ARM_RM-696_PRD_signed.bin

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.

Found device RM-696, hardware revision 1603
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3.299.1_PR_299
Sending ape-algo image (7103 kB)...
100% (7103 of 7103 kB, avg. 19354 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
Image SW version DFL61_HARMATTAN_40.2012.21-3.340.04.1_PR_340
Image moslo not present
Image mmc not present
Image tar skipped
Image config skipped

Battery level 21 %, 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
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
bb5_rdc_cert_read failed
Downgrade disallowed (1342067459)
[Pipe 0] Finishing in error state with status 10
========================================

Phone is just bootlooping now... Any assistance is greatly welcomed!
 
Posts: 6 | Thanked: 3 times | Joined on Feb 2013
#869
Nevermind! Was being stupid / dyslexic and had downloaded 249 variant. Managed to flash fine with 299
 
Posts: 128 | Thanked: 53 times | Joined on Nov 2012
#870
Whenever I plus in my n9 it always comes on, how can I reflash like this? It comes on and stays at the Nokia screen.
 
Reply

Tags
flashing, nokia n9

Thread Tools

 
Forum Jump


All times are GMT. The time now is 23:07.