Phone won't stay on or power on - G1 Q&A, Help & Troubleshooting

I'm 99% sure this isn't a failed rooting attempt.
My phone works fine *IF* I can get it to power on with the power cord. As soon as it comes unplugged it's anybody's guess as to how long it will stay on for.
After it powers off it won't turn on at all. I have to plug a power cord into it and wait for the green light to show up. (Sometimes takes minutes, sometimes takes days.)
Sometimes when it's plugged in and won't turn on if I hit the power button all the button lights come on for just as long as I press the button, I can push the power button over and over and all the buttons light up. But if I unplug it that too stops working.
When it started I had moved back from CM6 to 5.0.8.
I am on the 2.22.23.02 radio and have Rom manager with the clockwork mod recovery that it wants you to use.
I have tried multiple batteries this is not a battery issue
I'm hoping it's not a hardware problem.
Could it be the recovery or radio causing these issues? I'm afraid that if I try to reflash the radio it will power off in the middle of the flash process and really brick my phone.
Anyone have any other ideas or maybe has anyone seen this before?

xelaboy said:
I'm 99% sure this isn't a failed rooting attempt.
Click to expand...
Click to collapse
I'll bump that certainty up to 100% for you. Your battery has failed. Time to buy a new one.
I realize you say it isnt, but it is.

I have 2 batteries of my own.
I took it to batteries plus to have them test it there. They had a perfectly good battery and it wouldn't power the phone on. Believe me I desperately wanted to believe that it was just a battery issue. I actually still do. But having 2 batteries myself and seeing a third not work just seems like overwhelming evidence against the battery being the problem.

You can try to wipe battery statistics, it might help you.
In AmonRA there is an option to do so, if such an option exists in Clockwork, too, I I don't know.

AndDiSa said:
You can try to wipe battery statistics, it might help you.
Click to expand...
Click to collapse
That's a good idea. I hadn't thought of doing that. I'll give it a shot next time my phone allows me to turn it on.

Related

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] HTC One frozen - black screen & not responding

Hi guys,
So as the title states, I have an issue with my HTC One having frozen - before anything else, I understand that this is a developers forum, and although I have am still using the stock software and have not rooted my device, I'm hoping that some of you will be able to help me with this!
Yesterday at about 7pm, I opened the Gmail app, which froze, and tried to resolve this by opening the task manager to close the app, which subsequently froze, and then I tried pressing the power button twice to refresh the display - and this is how I am stuck on the black screen. In addition to this, no lights flash when holding the power button, and the device won't take a charge (the LED doesn't light up)
I quickly searched the net to find methods of trying to unfreeze the device - namely doing a soft reset for 30 seconds, a soft reset under a bright light (to overwhelm the sensor) for 30 seconds, holding the power button for 20 seconds, unplugged and plugged into the mains. It was also recommended to me to leave the phone on mains for 10 minutes, and then press the power, volume up and volume down buttons for 2 minutes - but this had no effect.
I have had the device for about 6 months, and this is the first time I've had any problem at all with it.
My options are to send it in for repair, or to leave it for a few days to drain any remaining charge, and then attempt to turn it back on.
I was hoping that some of you might be able to recommend any methods that I have not yet tried, or might be able to estimate roughly how long it will take for the device to drain?
I'm sorry if this post is mainly a repeat of what has been posted before, but in all of the cases that I found, people were still able to access the soft reset menus (of which I am unable)
Thank you for any help you can offer!
I have the same problem, but I was on a custo ROM (CM11).
Nothing that I have tried works, and I also hope the someone can tell us how to solve this...
blackhawk_LA said:
I have the same problem, but I was on a custo ROM (CM11).
Nothing that I have tried works, and I also hope the someone can tell us how to solve this...
Click to expand...
Click to collapse
Oh no, that's not good! How long has your device been affected?
I suppose that the main problem is that the warranty is now void on yours? I can't imagine it being a cheap repair :/
i have same problem but im running 4.4.2 and until now i can't fix it :crying:
MattHead93 said:
Oh no, that's not good! How long has your device been affected?
I suppose that the main problem is that the warranty is now void on yours? I can't imagine it being a cheap repair :/
Click to expand...
Click to collapse
Since 3 days, so I'm still hoping that when the battery drains completely, it will turn off and then boot normally.
If it is a hardware problem, I hope that it will be hard enough to repair for the technical service to give me a new unit
blackhawk_LA said:
I have the same problem, but I was on a custo ROM (CM11).
Nothing that I have tried works, and I also hope the someone can tell us how to solve this...
Click to expand...
Click to collapse
MattHead93 said:
Oh no, that's not good! How long has your device been affected?
I suppose that the main problem is that the warranty is now void on yours? I can't imagine it being a cheap repair :/
Click to expand...
Click to collapse
Ehfida said:
i have same problem but im running 4.4.2 and until now i can't fix it :crying:
Click to expand...
Click to collapse
Have you done a Hard Reboot of the phone by holding the power button + vol up/down for about 15 seconds ?
clsA said:
Have you done a Hard Reboot of the phone by holding the power button + vol up/down for about 15 seconds ?
Click to expand...
Click to collapse
Yeah, I tried doing that for 2 minutes (as advised by HTC Support) yesterday and Thursday - although I've not done anything with the phone today, as I'm hoping leaving it to discharge will have an effect!
Same here. 15seconds, 2 minutes, one hour... there's no hard reboot.
Also plugging ad unplugging, taking out the SIM card... anything happens.
My battery was nerly full so maybe it will take one week to discharge
clsA said:
Have you done a Hard Reboot of the phone by holding the power button + vol up/down for about 15 seconds ?
Click to expand...
Click to collapse
yes i tried about 3 minutes and 2days in wall chargeing and nothing now im leave it to discharge hope to get led flash:good:
Ehfida said:
yes i tried about 3 minutes and 2days in wall chargeing and nothing now im leave it to discharge hope to get led flash:good:
Click to expand...
Click to collapse
Whilst I'm unsure as the whether the device will have actually charged while frozen, if it has charged, it will probably take a long time to discharge.
Thankfully, mine was only on about 25% when it froze - so here's hoping I'll have a result by Monday...
MattHead93 said:
Yeah, I tried doing that for 2 minutes (as advised by HTC Support) yesterday and Thursday - although I've not done anything with the phone today, as I'm hoping leaving it to discharge will have an effect!
Click to expand...
Click to collapse
blackhawk_LA said:
Same here. 15seconds, 2 minutes, one hour... there's no hard reboot.
Also plugging ad unplugging, taking out the SIM card... anything happens.
My battery was nerly full so maybe it will take one week to discharge
Click to expand...
Click to collapse
Ehfida said:
yes i tried about 3 minutes and 2days in wall chargeing and nothing now im leave it to discharge hope to get led flash:good:
Click to expand...
Click to collapse
does the computer even recognize the phone when you plug it in ?
are you able to do a fastboot command ?
No, it doesn't. I have also tried installing a RUU but it's not possible. The phone seems to be completely dead. I hope it is just a deep coma from which it can be recovered.
clsA said:
does the computer even recognize the phone when you plug it in ?
are you able to do a fastboot command ?
Click to expand...
Click to collapse
no it dosn't yes i tried fastboot it say waiting for device
blackhawk_LA said:
No, it doesn't. I have also tried installing a RUU but it's not possible. The phone seems to be completely dead. I hope it is just a deep coma from which it can be recovered.
Click to expand...
Click to collapse
Sorry to here that ..are you going to try and get a warranted replacement ?
clsA said:
Sorry to here that ..are you going to try and get a warranted replacement ?
Click to expand...
Click to collapse
I will wait a few days to see if the battery drains and it can boot again. I don't even know if the phone is still on or off..
blackhawk_LA said:
I will wait a few days to see if the battery drains and it can boot again. I don't even know if the phone is still on or off..
Click to expand...
Click to collapse
That's the problem I'm having - I don't actually know if the device is on or off! It makes sense that if it's not responding in anyway, then the device is still on and frozen, or it could be the implication of a hardware fault, maybe blown motherboard or something.
Yes, and for me that would be an absolut mess, cause I had very important data stored on the phone...
And if you send the phone to repair they always make a factory reset and delete everything in your phone.
I had this issue on my One X and my fix was leaving it on the charger for about 6 hours and unplugging it and holding the power button for a full two minutes.
Sent from my One X using xda app-developers app
Thanks, but first I will try to leave the battery fully discharge. If I charge the phone and it doesn't work, then I will have to wait one week for it to drain completely again.
Hold it under a very bright light or point a flas hled to the sensor and hold power and volume down for a couple seconds

Stuck in eternal boot loop with stock settings

I have encountered a strange phenomenon on my HTC One. I woke up and forgot to charge my phone the previous night, so I went to charge it and after about ten minutes it kept turning on and off with the HTC "quietly brilliant" screen over and over again. There is no LED light to signify a charge, and I am able to get to the bootloader screen (I hope that is what it is called) by pressing the volume down but the phone restarts and won't let me click anything. It will only let me scroll down or up once so I can't get to the factory reset. I've tried many battery tricks such as holding both volume buttons and the power button for two minutes and nothing happened. I plugged it into my computer and the same thing happened.
I tried posting a video but the forum won't let me since I'm a new user!
Hoping someone can help me out! I just want to get my photos back more than anything.
Thanks!
esdlax said:
I have encountered a strange phenomenon on my HTC One. I woke up and forgot to charge my phone the previous night, so I went to charge it and after about ten minutes it kept turning on and off with the HTC "quietly brilliant" screen over and over again. There is no LED light to signify a charge, and I am able to get to the bootloader screen (I hope that is what it is called) by pressing the volume down but the phone restarts and won't let me click anything. It will only let me scroll down or up once so I can't get to the factory reset. I've tried many battery tricks such as holding both volume buttons and the power button for two minutes and nothing happened. I plugged it into my computer and the same thing happened.
I tried posting a video but the forum won't let me since I'm a new user!
Hoping someone can help me out! I just want to get my photos back more than anything.
Thanks!
Click to expand...
Click to collapse
Also, I have never rooted the phone or flashed a rom! Everything is stock.
Thanks!
esdlax said:
Also, I have never rooted the phone or flashed a rom! Everything is stock.
Thanks!
Click to expand...
Click to collapse
looks like the phone doesnt have enough battery to boot, shut it down and let it charge for 1-2 hours at least. If there is no led when charging, its probably because of a bad cable or charger. You can shut the phone down from bootloader: fastboot ---> power down.
alray said:
looks like the phone doesnt have enough battery to boot, shut it down and let it charge for 1-2 hours at least. If there is no led when charging, its probably because of a bad cable or charger. You can shut the phone down from bootloader: fastboot ---> power down.
Click to expand...
Click to collapse
Thanks for the quick response! I've switched out the charger to the original stock charger and I'm still having the same problem. The phone will automatically turn itself on after 10-20 mins and go into the boot loop. The other issue is I can't select anything from bootloader because it reboots again. I think the video would be helpful so I might go post on random parts of the forum to get 10 posts.
esdlax said:
Thanks for the quick response! I've switched out the charger to the original stock charger and I'm still having the same problem. The phone will automatically turn itself on after 10-20 mins and go into the boot loop. The other issue is I can't select anything from bootloader because it reboots again. I think the video would be helpful so I might go post on random parts of the forum to get 10 posts.
Click to expand...
Click to collapse
is the video on youtube?
alray said:
is the video on youtube?
Click to expand...
Click to collapse
Yes, I just sent it to you in a private message. And if anyone else wants it, I can send it to them.
Thanks
esdlax said:
Yes, I just sent it to you in a private message. And if anyone else wants it, I can send it to them.
Thanks
Click to expand...
Click to collapse
doesnt looks good mate. Maybe an hardware defect.
Just to be sure, you can power off the phone, if you do it reboots?
Maybe a problem with the power button or the battery...
Sounds to me like a knackered battery, unfortunately, that's one of the down sides of LiPo batteries, when they die they actually still contain 5% charge, if it drops below that, they are pretty much dead and cant really be charged properly again, ive learned this experience from flying radio controlled aircraft, basically, once the power starts dying, land it and charge it, if you push it right to the end, not only do you risk the chance of an expensive crash, but you have also just killed a £70 battery.
http://i817.photobucket.com/albums/zz96/seanie280672/DSC00170.jpg
Seanie280672 said:
Sounds to me like a knackered battery, unfortunately, that's one of the down sides of LiPo batteries, when they die they actually still contain 5% charge, if it drops below that, they are pretty much dead and cant really be charged properly again, ive learned this experience from flying radio controlled aircraft, basically, once the power starts dying, land it and charge it, if you push it right to the end, not only do you risk the chance of an expensive crash, but you have also just killed a £70 battery.
Click to expand...
Click to collapse
Oh man, that means I killed two batteries that day. I was flying my friend's quadcopter and the screen uses a lipo battery, which randomly died and now won't charge Yikes! You live and you learn. Is there anything I can do to "spark" the battery? Or more importantly any way to save my pictures? Thanks for all the replies!
esdlax said:
Oh man, that means I killed two batteries that day. I was flying my friend's quadcopter and the screen uses a lipo battery, which randomly died and now won't charge Yikes! You live and you learn. Is there anything I can do to "spark" the battery? Or more importantly any way to save my pictures? Thanks for all the replies!
Click to expand...
Click to collapse
I dont think you'll be able to backup anything with the phone stuck in this bootloop. Probably the battery can be replaced wihout loosing data on the phone.
alray said:
doesnt looks good mate. Maybe an hardware defect.
Just to be sure, you can power off the phone, if you do it reboots?
Maybe a problem with the power button or the battery...
Click to expand...
Click to collapse
I don't have a choice when the phone powers off, it randomly does it on its own when I'm in bootloader or if its just sitting there. I don't think its the power buttom because I can still press it, so its not jammed or anything. We have insurance on our phones so I can get a new one. I'm just looking to save the data at this point! Thanks for all your help so far!

[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.

[Q] phone cuts off when battery still has like 30%

A few weeks ago my battery was doing crazy stuff. It would go from 80% to 30% in 10 minutes and then back up to 70%, then down to 20%, back up to 60%, etc.
I drained the battery all the way down and then charged the phone while off to full. I thought this fixed the issue, but now when the phone gets around 30% it will just cut off and won't turn back on because it says the battery is completely dead.
All this happened out of nowhere... I had GREAT battery life before this.
Any ideas?
Didn't some early devices have battery reporting issues? I wonder if this is what you are experiencing.
Do you have any idea if there is anything that fixed it? And/or if moto is replacing phones with this issue?
I've read that they were being replaced, I don't recall if the service provider was doing it, or Motorola. I'll see if I can find more.
Thanks - FYI I called Motorola support. They had me reboot into recovery mode. Then wipe cache. They said this would not cause a factory reset. All my apps and settings would persist.
Instructions they gave...
Power off
Hold vol down for 3 second and then press and hold power without releasing vol down until you get bootloader
Use vol down to scroll to recovery mode and then press power to select.
Once in recovery mode (Andy on back with red exclamation mark)...
Hold vol up for 15 seconds then keep pressing vol up and press power as well and hold until you get blue text.
Use vol down to scroll to the "wipe cache" option and press power to select.
It says "erasing..." for a while.... like about 5 minutes so far and still going
Will post again to say what happens
phone rebooted after about 10 minutes of "erasing..." and all my apps and settings do seem to be in tact. I will see how my battery issues go now.
Please let us know if it does it again. I have been having the same issue.
I will post back... Might take a while... it only died at 30% on occasion because I often don't get it down that far.
The fluctuating issue (going down and up like crazy) hasn't happened in a while. That actually stopped after I drained it fully then charged while off... Then I thought it was fixed until the die-suddenly-at-30% thing started happening.
In any case - I actually have some screenshots of the battery fluctuating problem so I will post those just so people can see how crazy it was. (notice there is no charging when battery goes back up)
Check out my post here, sounds like a calibration issue, good luck!
http://forum.xda-developers.com/showpost.php?p=61179657&postcount=10
Thanks rhcreed - I will try your suggestion as well if I continue to have problems.
Speaking of which - I have not had any problems yet after I did what motorola walked me through. I don't consider myself completely out of the woods yet though because I don't generally get my battery very low, and so the problem was only occasional for me... so might just not have hit it yet. But so far, so good.
Glyphix said:
Thanks rhcreed - I will try your suggestion as well if I continue to have problems.
Speaking of which - I have not had any problems yet after I did what motorola walked me through. I don't consider myself completely out of the woods yet though because I don't generally get my battery very low, and so the problem was only occasional for me... so might just not have hit it yet. But so far, so good.
Click to expand...
Click to collapse
Had a similar problem... Turned out to be a faulty SIM card... Replaced the SIM card and it worked fine....
This may not be the case here... But what's worth a try is using the phone without a SIM for a couple of days if possible so that you can tell if it is a faulty SIM issue [emoji4]
Sent from my LG-D802 using Tapatalk

Categories

Resources