Reply
Thread Tools
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:
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#2
your battery is dead...

press the power button for around 8seconds to let it turn OFF completely then plug it into flasher with commands flasher -i and let it charge for an hour... Then plug into wall charger for another hour or two...
 

The Following 2 Users Say Thank You to thedead1440 For This Useful Post:
Posts: 470 | Thanked: 173 times | Joined on Oct 2009 @ Melb
#3
Done, turned off completely, plugged in with flasher -i

returns:
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
The device then has a fully illuminated LED, which remains for a few seconds before it powers off, disconnecting from everything completely.
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#4
then do flasher -f -F rootfs.bin

it'll tell you that not enough power to flash as battery is less than 11%... Let it charge to 10% and then plug it out and connect to wall plug...
 

The Following 2 Users Say Thank You to thedead1440 For This Useful Post:
Dousan's Avatar
Posts: 1,161 | Thanked: 1,707 times | Joined on Jan 2010 @ Denmark
#5
Plug it into a wallcharger and every time the led dies turn the phone of by holding the power button for 8 secs as thedead1440 said and repeat this untill you see the multiboot screen. Then boot into Nitdroid and let it charge there till it has about 10% then boot into MeeGo and charge it.
Meego somehow needs more juice to boot than Nitdroid?
It happend a few times for me that I ran out of juice in Nitdroid and it seems to fully drain it in Nitdroid to the point of no boot. Anyway this was the way I got it back to life. It takes some effort and time to make it charge to booting state

Dousan...
__________________
My Procreate art:
https://folio.procreate.art/dousan

My Søciety6:
http://society6.com/Dousan
 
JonWW's Avatar
Posts: 623 | Thanked: 289 times | Joined on Jan 2010 @ UK
#6
Originally Posted by optimaxxx View Post
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.
This sounds like how mine behaved after I changed the screen when it got cracked. I only switched it off with a short key press so I think it detected what it would assume was a hardware failure when I disconnected then damaged screen, and prevented itself from being switched on, it also behaved like yours. Solution was to open it up and disconect the battery then reconnect it, after that it booted fine.
 

The Following User Says Thank You to JonWW For This Useful Post:
Posts: 22 | Thanked: 0 times | Joined on Dec 2012
#7
please help me , my n9 is deth. I tray to install android and something in nat good.

when the command Prompt write flasher -i, I have a message

Suitable USB interface (bootloader/phonet) not found, waiting...
Found device RM-969, haedware revision 1603
NOLO version 2.3.6
Version of `sw-release` : DFL61_HARMATTAN_40,2012,21-3_PR_001
Success

I miss the field
device indentifier: (number) SNN/A)

how to get back the field in phone?
 
Moderator | Posts: 6,215 | Thanked: 6,400 times | Joined on Nov 2011
#8
floyd03,

Firstly, stop posting in random threads!

Secondly, describe exactly what you did and what is the problem now? By dead N9 do you mean that trying to power it on does nothing? No blinking white LED too?
 

The Following User Says Thank You to thedead1440 For This Useful Post:
Posts: 22 | Thanked: 0 times | Joined on Dec 2012
#9
I tray to install nitdroid_n9_jellybean_alpha5.tar

everything was ok until I installed apps2sd_fix_alpha5.tar, because I wrote the wrong command it should be entered like "tar xjvf / home/user/MyDocs/apps2sd_fix_alpha5.tar.bz2-C / home / nitdroid /", and I was entered tar xjvf / home/user/MyDocs/apps2sd_fix_alpha5.tar.bz2-C.

and since then I can not run MeeGo system.
white LED is working, I have comunication with phone.
 
Posts: 22 | Thanked: 0 times | Joined on Dec 2012
#10
When I enter through the command prompt flasher -i get this
Attached Images
 
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 20:33.