Reply
Thread Tools
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#861
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
#862
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
#863
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
#864
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
#865
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
#866
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
#867
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.
 
Posts: 446 | Thanked: 207 times | Joined on Sep 2012 @ Austria/Germany
#868
This is weird!

I did a secure erase on my second N9 just now and during tbe first setup process (where you set time, date, language....) the device remembered my nokia account user name!!!!

whats secure about that??
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#869
press the power button for 8-10seconds before plugging into usb port for the n9 to be powered off...
 
Posts: 128 | Thanked: 53 times | Joined on Nov 2012
#870
Yes I got it, I'm trying to see if its the death by batter drain issue before flashing, I hope it is lol

edit: nevermind **** is bricked.

Last edited by unoace; 2013-07-13 at 22:05.
 
Reply

Tags
flashing, nokia n9


 
Forum Jump


All times are GMT. The time now is 03:36.