View Single Post
Posts: 470 | Thanked: 173 times | Joined on Oct 2009 @ Melb
#1
Symptoms:

Plug in USB, semi-dimmed LED comes on solid, and stays on.

Sometimes LED just turns off, sometimes LED flashes, hard on, hard off (pretty sure it's the recharging indicator).

Sometimes pressing the power button works, the LED illuminates as expected, but when it vibrates, it isn't the standard vibration.

No matter what, it doesn't start.

Dualbooting,
No OC.
Flasher can connect to it, (flasher -i), but after a couple of seconds it too will disconnect.

If you have these symptoms, you probably have a completely flat battery.


Running:
flasher -i
Code:
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 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Success
After this the phone will have a fully illuminated LED, which remains for a few seconds before it powers off, disconnecting from everything completely.


Running this:
flasher -F <firmware-image> --flash-only=kernel -f -R
If you're dualbooting run this command instead:
flasher -a <firmware-image> -k zImage.pr13 --flash-only=kernel -f -R
Code:
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.

Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-696, hardware revision 1601
NOLO version 2.3.6
Version of 'sw-release': DFL61_HARMATTAN_40.2012.21-3_PR_005
Sending ape-algo image (7096 kB)...
100% (7096 of 7096 kB, avg. 12649 kB/s)
Suitable USB interface (phonet) not found, waiting...
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_005
Image cmt-2nd skipped
Image cmt-algo skipped
Image cmt-mcusw skipped
Image xloader skipped
Image secondary skipped
Image moslo skipped
Image rootfs skipped
Image mmc skipped
Image tar skipped
Image config skipped
Charging battery,  0 % battery level (11 % required). Ctrl-c to exit
Flasher will connect to the phone like before, but now it will maintain it's connection. This will allow your N9 to recharge.

Code:
Charging battery,  1 % battery level (11 % required). Ctrl-c to exit
Charging battery,  2 % battery level (11 % required). Ctrl-c to exit
Charging battery,  3 % battery level (11 % required). Ctrl-c to exit
Charging battery,  4 % battery level (11 % required). Ctrl-c to exit
This is what it will look like whilst it's charging, I successfully disconnected mine at 7%, then plugged into the stock N9 wall-adapter to finish charging.

You must disconnect your N9 before it completes charging, or the program will proceed to wipe your phone. When you're ready to disconnect your N9, press ctrl and c simultaneously, which should show:

Code:
Cancelling flashing
       ...
This should fully resolve your N9's 0% battery troubles, if none of this works for you then this probably isn't your problem.

A few questions for the pros out there:
Wil running flasher -F <firmware-image> --flash-only=kernel -f -R leave everything but the kernel untouched if somebody forgets to cancel it?
Is there a command that would allow the phone to charge, but wouldn't actually flash anything to the N9 in case it executed?

Last edited by optimaxxx; 2012-11-05 at 08:52.
 

The Following 6 Users Say Thank You to optimaxxx For This Useful Post: