Database Develop

Captivate (not Galaxy S) won't boot.

I was doing an Odin One Click restore to return to stock
Odin got stuck for some reason. I waited nearly 45 minutes before pulling the battery and attempting to start over.
Upon pulling the battery, the phone went off, as expected. removed Sim, SD card, replaced battery, replaced battery cover, etc etc.
The phone is 100% unresponsive.
1: Removing and replacing battery - no effect
2: VolUp + VolDn + Power - no effect
3: Plugging into any one of the 5 USB ports on the computer - no effect
4: Plugging directly into the wall - no effect
Nothing I've tried or read has given any solution to even get the phone to come on.
Last ditch effort, going to leave the battery out for an hour or so, and failing that, going to leave everything plugged in for an hour or so.
The battery on the phone had nearly 95% when I started this endeavor.
Does anyone have any hints or suggestions as to other things to try?
Thanks.

I had that happen last night. Got stuck sending "factory.rfs" or something like that.
Anyway, plug your phone to the wall for a few minutes. Maybe an hour. Then open Odin, hold Vol-UP and Vol-DOWN (dont push power), and plug the device to the computer. It should boot to Download mode.
Now, I used the version of Odin that allows you to select the firmware -- there's another that comes with JF6 preloaded. I installed JH3. Also, when I selected the firmware with the "Phone" section and flashed, it did not work (FAIL). Later I tried the "PDA" section and it did.
Let me know how that goes.
EDIT: Plugging to the wall, the screen will not turn on. But the back will get warmer. Trust me, it is charging. My battery was full after the flash.
del

Thanks for the quick response.
I figured at this point, I couldn't do anymore harm that good. Worst case, I buy a new one.
So, I started tinkering with various key combination... Lo and behold, one particular set gave me the infamous "orange dump".
From there, and a bit of searching (i had remembered seeing the bit about the orange hex dump somewhere), I found the same solution you just provided.
Worked, phone is stock and functional.
Kudos.
Dave

i too was trying to install vodoo and after installing it my phone wont turn on it just keep on flashing atnt screen and next screen i see is samsung and thts keep on repeating no luck my phone wont turn on please help me am badly stuck.
thaank you.

IF you are able to get your phone to the point of seeing the att screen then you should be able to hold down the vol up+down buttons while also holding the power button...Just to be safe, hold it till the att screen flashes twice. Then release and you should be taken to the recovery mode. If not, Try the same steps again plugging in the usb while the att screen is present. Repeat as necessary. Good luck.

How to unbrick a "dead" Milestone.

After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.

I tried following this guide, though without success. The phone still has that white LED lit when it's connected to the PC.

After a reply on this thread I also made, it might be possible that the battery is charged, but the phone refuses to boot at all. Is there any way to unbrick the phone in this state?

Do you think your device is really BRICKED?
If so, you can try to flash your original sbf file into your phone. Guide here: http://forum.xda-developers.com/showthread.php?t=696845
If you are using a Linux, google for "sbf_flash".

I agree with my front floor..ermm, u dont need to worry about its 'dead'. just flash original sbf can rescure your phone.

I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck

algopem said:
I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck
Click to expand...
Click to collapse
"My phone is in limbo state... "
That's a pretty cool statement.
From technical view, it might have happened that something caused a kind of deadloop when reading scratchpad SRAM inside OMAP processor.
This SRAM, as well as the internal RTC is powered by a small battery soldered on the mainboard, while the phone is shut down and the battery is taken out.
What you did was, to wait untill this battery became uncharged.
All SRAM and RTC setting as well then gets erased.
Afterwards the CPU will start up with empty scratch SRAM, might be called a "real" cold boot
Normally the phone should not behave like this. Even if SRAM is not valid the phone should boot up...
...but anyway as you observed it like this, it might happen.
@andoruB:
Apart from that, the Milestone is hard to brick in general.
Might happen though, if you do evil things while flashing new firmware.
Especially while flashing bootloaders...
If you got some more information about the things you did, would be helpful!
Good luck anyway!
scholbert

andoruB said:
After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.
Click to expand...
Click to collapse
how did u root it? can u give a more detailed description? and hows ur phone? sometimes, the milestone would just shut off and wont come up if the battery is gone. Try charging it for maybe 2-3 hours, untouched, and see what happens.

Have this exact problem. Was doing a nandroid recover when the phone got stuck. Pulled the battery out. Placed it back in, pressed the power button. Nothing.
Led lights up only when connected to the computer's USB. Battery was charged before Nandroid recover. Used nandroid a lot of times but for some reason, my stone stopped playing nice.
I just removed the battery. Hoping this works. Can someone please post if you got this same issue resolved? I like this phone no matter how slow it goes sometimes. Thanks!

I completely forgot about this thread, sorry guys!
I don't remember exactly what happened, it's been so long... but I do remember I left the phone "inactive" (it's not like i had much of a choice! XD ) for 1 or 2 months, with the battery out. After I got hold of a wall charger, I plugged in the battery, after I plugged in the charger, and what do you know? It worked! It started charging (was 60% charged, fully charged, I unplugged it, but after putting it to charge again just to make sure it was fully loaded before I would flash a new ROM, it was charged up to about 80%, weirdly, so I guess it was a weird battery problem)
I do remember I didn't do anything to it, so I'm not sure what to tell you guys to do, except leave out the battery for a month or so ^^;

Bricked Touchpad need help

NOTE - I added this post here thinking the CM9 experts could help. I then realized it should be in the Q&A section. If this does not belong here, I ask a moderator to please delete it.
I have been running CM9 nighties for some time now with no issues on my 16GB US WiFi only Touchpad. I installed TWRP and after some time decided to remove it and just use CWM. After trying several things from the posts (which would not work) I decided to remove CM9 completely then reinstall. This is where I got into trouble...
I loaded all necessary CM9 files in the cminstall folder on the Touchpad. I successfully ran ACMEUninstaller and got back to the WebOS language selection (i.e. the initial WebOS screen from factory). Instead of logging into WebOs (felt there was no-need since I never use it), I put the unit in Download mode (vol down + power). I then ran ACMEInstaller2. I received an error (text on the black touchpad screen which I assume is the bootloader) saying the needed files were not installed and something like "remove the wall". I thought I would reboot the unit and now log into WebOS and reinstall the CM9 files (thinking I made a typo when loading them). Now I cannot get the Touchpad to reboot - totally black and even when connected to the PC I dont get the USB connection sound.
Does anyone know if there is a hardware method to bring the unit back (maybe a different sequence of button presses or shorting a pin on the USB connector)? I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port.
Any thoughts would be greatly appreciated.
Resolution: In a post I saw dated May of 2012, the user indicated HP was still honoring their warranty. I contacted HP via their Chat service, after giving them my model and serial number, I was told I had three weeks remaining on my warranty. HP sent me the return box with authorization and in a week I received (what seems to be) my exact Touchpad... only now it booted just fine. I have since reinstalled ICS and am running fine. Thanks to all who responded. I wanted to share this as I am extremely impressed with HP's warranty service (no questions were asked if I had rooted the device, where I bought the device, etc).

I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....

chozyn said:
I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....
Click to expand...
Click to collapse
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?

enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
It's a good idea to use only stock cable and charger.
Sent from my ClassicJewel

enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
Are you able to get into download mode at all?

A$$h4t said:
Are you able to get into download mode at all?
Click to expand...
Click to collapse
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.

enmriley said:
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.
Click to expand...
Click to collapse
This happened once to my TP when I first put CM7 on the device a while back. I woke up one morning, forgot to plug it in overnight and it had died. No response to any charger, I was getting worried but then I found a solution. With it plugged in, hold the power button and home button down together for 15 to 30 seconds. It was that or hold the power button down and keep pressing the home key over and over. Not 100% sure, but it came back to life and I remember it took me a couple tries. Try holding both down simultaneously for 30 seconds or a minute, if that doesn't work, push and hold power first then home right after and hold both for 30 seconds.

Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true

-SGA- said:
Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true
Click to expand...
Click to collapse
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:

rhidalgo1973 said:
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:
Click to expand...
Click to collapse
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.

enmriley said:
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.
Click to expand...
Click to collapse
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.

bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks

sstar said:
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks
Click to expand...
Click to collapse
In Tasker add a New profile and give it a name like Battery_Low
Choose State and then Power for the profile.
In Power choose Battery level and set From to 0 and To to say 8%
Set New Task and do Add give it a name like Shutdown and then pick the Misc category
Choose Reboot and set Reboot type to Shutdown
All done. When battery level drops to 8% or below then Tasker will shut the tablet down. Note it will do this without warning. I think one could probably arrange a pop up warning first but I preferred to keep it simple.

bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.

enmriley said:
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.
Click to expand...
Click to collapse
The only way I know is to put it on a Touchstone and after an hour or so it Will come back to life. All thanks to Reverand KYLE. His site is well worth checking out.

[Q] [Help Thread] Nook HD not booting at all

I recently went on a 3 month trip. Before I left, my nook was working perfectly fine, when i got back, it didn't work at all. It's not dead because i left it plugged in overnight but it still didn't turn on. when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all. I can't get to recovery either.
This is a Nook HD, I believe it had CM11.
:crying:
Can this be fixed
or should i plan it's funeral

Same here
The same has happened to me. Screen doesn't turn on, but there is power, I can play it into my laptop and something is there, just not enough.
Good excuse for a new tablet!

It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).

tambourineman86 said:
It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).
Click to expand...
Click to collapse
If would be fab if you could fix. Seems to be a common issue

I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.

tambourineman86 said:
I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.
Click to expand...
Click to collapse
Not sure we have the same problem. My screen doesn't come on at all, I don't get a battery depleted icon, no matter how long I hold in the power button. The only sign of life I get is when it's plugged in, when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.

YMMV. But mine was the same issue. You should be able to get the icon by holding the power button down for 5 or 6 seconds. I'd say just eff with it until that icon appears. Try different button combinations. I used power and home trying to get the icon to show.

developerbuzz said:
when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.
Click to expand...
Click to collapse
Anyway... since people are continually running into this kind of issue...
Give or take 21 seconds after turning orange it turns green during actual boot cycle into rom
Give or take 10 seconds after turning orange is cwm internal recovery.
After about 10 seconds the charging screen image disappears.
The charging screen image once finally no longer may not show up again until full power off/on (holding power button > 10 seconds or full battery discharge). Unplugging and plugging back in does nothing except making the device look bricked if there's too much light shining on it.
Device may not automatically leave the above state under a specific situation(s). May still need manual full power off/on.
Guessing 10 seconds could also be something else during the early/late boot process or other. The light changing color though should indicate that something is indeed happening.
Light should stay green during the boot process if its completely and fully no questions asked 100%. If you go based on that than yours doesn't appear to be completely fully charged which should either mean its turning on and using battery or not charging correctly.
The light turning off is curious. The device could be shutting off. If light comes back on a moment later then the device has rebooted. if the light stays off = n/a.
If its booting into recovery then the device would be available via adb. At that point it could be further evaluated.
On the off chance the screen was damaged it should boot and usb should be available via computer as well as adb.
If not then its probably toast unless its simply not getting a good enough current causing mislead battery stats and/or not enough energy to get to charging screen (bad wall power adapter in use, damaged power cable - though could be bad battery, defect, damage or whatever). OR there's some major error on behalf of the user happening (think should have tried that in the morning not while 1/2 asleep or came home from long trip and forget how that works).
Maybe the only other things are the emmc brick bug, was left sitting in the sun or heat or ocean air or other physical damage/defect even to the power port as well.
Or maybe it was mad that you left it. Shouldn't have hurt its feelings you know. At least its not crying battery acid on you.
That should just about cover everything except for the things not mentioned. Since its your device, you decide what happened.
Its complicated so anyone see any improvements, clarifications, or mistakes? Please put it in a post.

Jsorren said:
when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all.
Click to expand...
Click to collapse
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.

sandsofmyst said:
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.
Click to expand...
Click to collapse
I actually ended up fixing it yesterday!! I haven't touched it in about 3 months, and I was planning on just throwing it out getting rid of it some how. For the heck of it, I decided to plug it in, assuming that it was gonna go through the same process. But this time it went from green to amber, but it never went off. So I pressed the power button and the battery icon appeared. This was a really good sign. So I left plugged in for about 5 to 10 minutes then tried to power on.:fingers-crossed: As soon as I saw that '' Nook" boot up screen, my heart stopped. It booted up perfectly and I almost blew up from excitement :victory:. So I then flashed the stock firmware back onto it, so this would never happen again.
I guess the battery had to be completely depleted or just had to cool down. Idk but either way this was one heck of a miracle
So I recommend for anyone having this problem to just leave it off and don't mess with it. I wouldn't say for 3 months like I did but maybe test it each week or wait a month if you have good patience

Wow. Man, that's awesome! Glad you posted that update on it. Thought if you had posted an update it would be the opposite as in trashed it
Actually, I guess only you could answer if you had also moved/unplugged the power cable from the wall adapter or put it into a different wall adapter, etc. Thinking there could have been a difference there.
These modern day devices are so finicky, guess anything is possible. Like you say, maybe sitting without power is another answer.

From some experimentation I have etermined that your power adapter (that plugs into the outlet) is the issue. It does not like to be leaft plugged in indefinately. It will continually use power even when the nook is not plugged in.
Also, if you use a differnt adapter you will have the same problem unless it is also of the exact same voltage and amps.

Phone Display shows empty battery and wont boot

Hi Guys - after some help if you please! My Z3 C has decided to refuse to power up. Without the charger plugged in nothing happens, even when I use all the usual vol up and power etc.
When I plug the phone into the charger the screen just shows the empty battery screen and turns off/on/off/on etc cycling like that.
Just cant get it to start.
I can manage to get it to reload the software through pc companion and it gives the successful message. But after trying a reboot, nothing happens.
Now because it does the software rebuild, I assume the phones not bricked. So could it just be a goosed battery?
Cheers
Terry

Hello,
I have similar priblem few years ago.
I figured out in this "overdischarged" state when i try to charge, and appear the battery screen, if the battery reach a critical charge level, the phone will try to boot. But its fail, because te voltage still too low, so thats why its reboot. I did this: (i dont take any responsibility)
Put the phone in a plastic bag, hermeticaly close it to minimize the vapor, then put it in the freezer.
Wait.
When its cold, connect to charger, now you able to charge more, before phone is start to boot. Charge it till start to boot, and Turn it off immidiatelly with the little button next to the sim card.
Now, you haveto warm it up, i do it with a hairdryer, use it at least 10 mins, not jost the cover, but the battery must have warm too. 50 celsius is fine.
Now connect the charger, and try to boot. Hopefuly, you can able to boot, and the phone will start charge.