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.
Related
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.
My nook was idle for a day or two, as I remember I hv shut it off.
But then yesterday I try to charged it, the light was green then turn to red, n then it went off, usually the nook would turn on right after I plug the charger. So I didn't notice it until today, and I tried to turn it on by pressing the power button, and the N button together as well, both didn't work.
It seems that I can't charge it or turn it on. Everytime I tried to re-plug it to power or press power button while its connected, the light went on in green to red then off again.
Sent from my GT-N7000 using xda app-developers app
Connect your charger. Let it stay on charger 20 min. Then try push n button. If this not bring screen on then try push power button for 5 sec. Again if not then try power and n button combination.
Hope this helps.
Thx! Turns out tht external charger didn't work.
Sent from my BNTV600 using xda app-developers app
I think that last opinion is make CWM sd card (without CM10) and insert it do device, then try to switch the device on (with charger trick or power button). If you then get it live all is ok. If not then last change is wait when battery goes empty and charger wakes it up.
Actually i predict that item is itself faulty and you must return it for change (maybe not faulty at hardware side, only OMAP inside code got corrupt).
I don't know, that might because I rooted my device, and I did sth wrong. Sometimes it would reboot itself, since my cmw card was inserted, it would load tht root page so I found out. But I live in Asia so returning the device might be too costly, probably won't do it.
Sent from my BNTV600 using xda app-developers app
ling_1118 said:
I don't know, that might because I rooted my device, and I did sth wrong. Sometimes it would reboot itself, since my cmw card was inserted, it would load tht root page so I found out. But I live in Asia so returning the device might be too costly, probably won't do it.
Sent from my BNTV600 using xda app-developers app
Click to expand...
Click to collapse
It could be several things. The most likely is it was trying to update itself and could not because the CWM card was there. I don't think your device is defective.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
It could be several things. The most likely is it was trying to update itself and could not because the CWM card was there. I don't think your device is defective.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Now i can say same. With first information things was other.
...It's more or less a known bug to those of us who use CM10 (even to some who use stock), the battery simply often can't tell how much she has left. So she may fluctuate from 1% to 26% to 0% a moment later . In one such moment my Nook HD+ shut down (went from 26% to 0%). So I put it up for charging thinking (naively) that it would boot up ... it didn't, now all I get is a charging icon that never goes away (orange led remains lit). What's more I *know* it has some charge (the "26%" was the right value) and I know the battery works, so what prevents it from starting is the "battery charge sensor".
It's a pretty silly way to lose your (my) tablet over. Even more so given how much I grew attached to it for my workflow. So what's next? Is there a secret way to convince it to boot. As I said both the hardware and its software is in top condition. I guess an alternative would be to ship it back for replacement but I'm afraid that I've lost my receipt and -as I said- it's a silly way to lose your tablet over, there *has* to be a (fast) way out...
BTW when connected to my PC my device manager briefly shows an "Omap 4470" unknown device (with an exlamation mark) which goes away few secs later, so I cannot attain ADB control over my devices either (sadly)....
Stevethegreat said:
...It's more or less a known bug to those of us who use CM10 (even to some who use stock), the battery simply often can't tell how much she has left. So she may fluctuate from 1% to 26% to 0% a moment later . In one such moment my Nook HD+ shut down (went from 26% to 0%). So I put it up for charging thinking (naively) that it would boot up ... it didn't, now all I get is a charging icon that never goes away (orange led remains lit). What's more I *know* it has some charge (the "26%" was the right value) and I know the battery works, so what prevents it from starting is the "battery charge sensor".
It's a pretty silly way to lose your (my) tablet over. Even more so given how much I grew attached to it for my workflow. So what's next? Is there a secret way to convince it to boot. As I said both the hardware and its software is in top condition. I guess an alternative would be to ship it back for replacement but I'm afraid that I've lost my receipt and -as I said- it's a silly way to lose your tablet over, there *has* to be a (fast) way out...
BTW when connected to my PC my device manager briefly shows an "Omap 4470" unknown device (with an exlamation mark) which goes away few secs later, so I cannot attain ADB control over my devices either (sadly)....
Click to expand...
Click to collapse
If you are running CM10 or 10.1, there is an easy way to connect with ADB. Do it wirelesly over wifi. That is built into CM. Just enable it in the developer options. No need to mess with the USB cable and windows drivers. You can do the same thing with rooted stock by installing an app called ADBWireless.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
If you are running CM10 or 10.1, there is an easy way to connect with ADB. Do it wirelesly over wifi. That is built into CM. Just enable it in the developer options. No need to mess with the USB cable and windows drivers. You can do the same thing with rooted stock by installing an app called ADBWireless.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
At the time that could not happen , since (as I had implied) my nook was not booting to begin with...
Anyhow, what I did was to leave it for three solid hours on the charger, and after that period of time it booted on its own wiithout warning. It's the first that such behavior was/is ever present to my nook and it's deeply worrying. A battery fix for the CM kernel couldn't come any sooner; now, if only verygreen was around
There's a few ideas on a couple of other threads including putting it in the fridge, etc. Question, if you plug it in, does the charging light come on? Does it come on after pushing the power button or the N button? If so, take your SD out, leave it charging overnight and try again. It often reboots when in this state and if there's an update problem, that could be the issue. Also, it is sometimes erratic on when and how it charges, be careful with the connections.
dbh369 said:
There's a few ideas on a couple of other threads including putting it in the fridge, etc. Question, if you plug it in, does the charging light come on? Does it come on after pushing the power button or the N button? If so, take your SD out, leave it charging overnight and try again. It often reboots when in this state and if there's an update problem, that could be the issue. Also, it is sometimes erratic on when and how it charges, be careful with the connections.
Click to expand...
Click to collapse
As I said it came up on its own, without warning after leaving it for 3 hours on the charger...
As for your question, the led (charging light) was on all the time but it would only show me that it had no battery (couldn't charge even though it was ... charging?)
Maybe the fridge makes sense in those situations, as it was indeed into a (relatively) hot environment and maybe it couldn't charge as a safety against overheating and since (at the same time) it also thought it had 0 battery. But what I can't understand is why needed 3 hours before starting to charge up, it was already cool enough long before ... strange things are/were happening with my battery all along and I worry...
Stevethegreat said:
As I said it came up on its own, without warning after leaving it for 3 hours on the charger...
As for your question, the led (charging light) was on all the time but it would only show me that it had no battery (couldn't charge even though it was ... charging?)
Maybe the fridge makes sense in those situations, as it was indeed into a (relatively) hot environment and maybe it couldn't charge as a safety against overheating and since (at the same time) it also thought it had 0 battery. But what I can't understand is why needed 3 hours before starting to charge up, it was already cool enough long before ... strange things are/were happening with my battery all along and I worry...
Click to expand...
Click to collapse
Yep, I've noticed the same thing a few times. It no longer panicks me. When it doesn't turn on, I take out the SD, plug it in, wiggle the connector a few times, and let it alone. So far, it has always eventually rebooted, often as you say on its own. Quirky, but not fatal at least. One poor guy on here never did get his to turn on, but the key was the charging light,his didn't come on.
Need help cannot turn on Nook HD+ at all
Hi!
I cannot turn it on at all and it won't reboot.
It went out some point I didn't watch it. When I connected it to the charger the LED next to the connector starts blinking amber and green for a few seconds and then stays blinking red and makes a high pitched noise.
The only reaction I get is when I press power on an volume down after some time - it display turns on an shows a charging sign - but it never really seems to fully charge. I left it on the charger over night - still the same. Once the display blinked and showed “nook” but went out immediately after a few milliseconds.
Might it be some kind of bootloop!?!?
What combination to press to make a reset?
Thanks in advance for any help
Medizinmann
Hey helpful XDA'rs,
After somehow avoiding to have a tablet for this many years, I decided to get a 2ndhand Touchpad after seeing all the reviews, ROM support, price to relative specs, etc... so I bought a second hand 32GB tablet off of ebay. In fact, this one right here... http://www.ebay.com/itm/271192613408?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649
Anyways, I got it earlier today, and plugged it into the wall charger it came with (the circular OEM HP one, with the long cable with a silver circle on each end). When I plugged it in, the little white alternating light under the home button switched on, so I figured it was working. Had it plugged in for about a half hour before I decided I couldn't contain my excitement and wanted to power it up. Of course nothing happened. Just a black screen and that little white alternating light mocking me.
I immediately hit up the google machine and XDA and realized that the screen was supposed to be on with an actual charging icon/animation or something like that. Up to this point, I still have not seen any sort of anything appear on screen. Just that little white light. Now yes, I've read through the posts.
First I checked to see if the HP charger/cable would charge my GS2. It did, and quickly (not some sissy trickle charge) and the circular HP thing felt warm to the touch. I also unscrewed the cylinder HP charger and blew in there with my breath pretty hard to clear out any possible dust, then screwed it back on tightly. I have used different cables with the HP charger, and used the HP cable with my GS2 charger. Same results, just that mocking little light, and the HP cylinder did not feel warm to the touch.
I have done pretty much all the button combinations I could find for at least a minute, with no results. Power + home, power + rapid firing the home button, power + volume up + home, power + both volume + home, etc. This is with the charger plugged into the wall.
I did notice two changes though.
#1 When I hold power + home, after maybe 12 seconds, the light stops alternating and is off - for about 2 seconds. Then the alternating starts back up. When the alternating light stops when I do this, it is always for the same amount of time, about 2 seconds, then it starts up again, regardless of if I continue holding the power + home, or if I immediately let go of the buttons, or immediately let go and then try pushing other buttons; it is always the same, the flashing stops after about 12 seconds, pauses with no lights at all for about 2 seconds, and then starts back up again.
#2 When I hold power + home + volume up, after about 12 seconds, the white alternating stops completely and never comes back if I don't do anything else. There are only 3 ways that I have found so far that will get the alternating white light back. First, just simply unplug and replug in, the light immediately comes back. 2nd and 3rd ways are to do the previous two button combos again, (power/home or power/volup/home for about 12 seconds).
MOVING FORWARD, here's where some interesting things happened, which hopefully is enough to have someone knowledgeable know what might be going on.
I decided to try #1 and #2 again, but this time, instead of the wall charger, I plugged the USB cable into one of my computer USB ports. My computer didn't make a device connect sound, nor show any kind of drive being connected in my computer. Just the same alternating white light.
Trying method #1 above, did the same thing. Power/home, alternating light would turn off for 2 seconds then start back up. Still no sounds from computer.
Trying method #2, finally something! When I held power/home/volup, after about 12 seconds the alternating light would turn off for good as expected, but then my computer made a noise! Not the device connected sound (low note to high note sound), not even the device disconnected sound (high note to low note), but that 3rd "device failed to connect" sound, the (three low tone sound). If you go to your windows sounds you'll know which sound I'm talking about. Anyways, I was glad to hear that the computer realized something was there. Although it was just a sound. Nothing in my computer, but for a second I did see a pop-up bubble in my lower right hand notifications say "device did not install correctly" or something like that. Now, with the touchpad still plugged into USB, and the alternating light off, if I either remove the cable (or hold power/home or power/home/volup for 12 seconds so the alternating light goes back on) then my computer makes that "device disconnected" sound. The hell is going on? I can duplicate those two sounds (the device failed to connect sound, and the device disconnected sound) over and over by holding power/home/volup for 12 seconds, and then unplugging and replugging the USB.
Having said all this, anyone have any ideas? Again, up until this point, I have yet to see anything appear on screen. Just that damn white alternating light.
I also know that this might also be a case of the really dead battery. It may just need to charge for like 48 hours via HP wall charger, or it may need to trickle charge for like 48 hours via USB to computer. If that's what it takes, but jesus I'm impatient and don't want to wait a week or longer, especially if I have a small window of opportunity to return this via ebay. So for tonight, I'm going to trickle charge via USB, but with the alternating light OFF via method #2, because at least with #2 and the light off, my computer makes a sound confirming something is plugged in. My rationale is that if it thinks something is plugged in, it will charge it.
Thoughts guys? A million thanks to anyone who actually read this entire essay and is still willing to help out!
Edit: the USB trickle charge I am attempting overnight tonight is via my GS2 cable, NOT the HP cable, since I've read all over the place that the HP cable is of poor quality.
Sometimes, when the battery has been completely depleted, it takes a real long while (24+ hours).
Your cable and charger seem to be Ok, so just plug it into the wall and check on it it tomorrow.
Post again if you keep having problems and we should be able to help you.
Good luck.
Not sure it will help but but holding power,home and volume down button is reboot ,I've had to hold it for 15 to 17 seconds before....
Check here also : http://forums.webosnation.com/hp-touchpad/292681-help-new-touchpad-wont-turn.html
Sent from my skz_tenderloin using xda premium
When i got my touchpad it was deeply discharged. I had to let it charge for several hours before it did anything at all. However i used the weak Samsung charger, so there was at least that message "please use the original charger" on the screen. So maybe you just need to wait...
Good luck though
Cheers
Chris
To my joy, I woke up today with the screen on displaying a low battery charging icon. It's in the red though, but that's definitely progress. Is there a charging animation, or is it just a still icon? Mine has no animation and wanted to make sure mine didn't freeze.
I wanna say there is no animation just the icon (its been a long time since I've seen it ) but it only needs around 10% to boot... Now that you see the icon try holding the power and home button for 15sec and see if it boots.
Sent from my skz_tenderloin using xda premium
I went and grabbed some food and upon returning I saw that my TP had completely turned itself on and was on some sort of setup screen, asking for me to select a language. I'm running through the setup now - two things. First, is it necessary to create a webOS account? Kinda like creating a google account for android? I intend on installing cyanogen10 on this, but wasn't sure if a weOS account was necessary. Or perhaps it's helpful. Second, the touch response is HORRIBLE right now doing the setup, takes multiple attempts to push an area, and with much more pressure than I would think is necessary. I'm assuming this is to low battery,. and it will improve as the battery returns to normal levels?
Not sure about the touch response issue but the low battery could be a possibility , as for the webos account i believe you only need to do that in order to use webos , i would do it anyways though .
Check here if you don't feel like making a webos acct: http://forums.webosnation.com/android-webos/318426-how-install-android-without-setting-up-webos.html
Sent from my skz_tenderloin using xda premium
Yeah it was low battery. After a little more charging the touch response works fine now. Thanks! I was really stressing that I received a dead TP.
There are several programs available in the play store that will turn your tablet off when the battery % reaches a certain level. I use Automatelt (thanks to sstar for the tip) set at 20 %.
ManImCool said:
Yeah it was low battery. After a little more charging the touch response works fine now. Thanks! I was really stressing that I received a dead TP.
Click to expand...
Click to collapse
Good to hear ! Happy installing /flashing.
Sent from my skz_tenderloin using xda premium
chicle_11 said:
There are several programs available in the play store that will turn your tablet off when the battery % reaches a certain level. I use Automatelt (thanks to sstar for the tip) set at 20 %.
Click to expand...
Click to collapse
Is 20% the general consensus around XDA where it shouldn't go any lower than? Are some people setting it higher? Lower?
I have mine at 9% . some prefer more battery left to feel safer i suppose , basically you don't want to let your tp battery drain completely because it might possibly brick
Sent from my skz_tenderloin using xda premium
Hi
I’m wondering if anybody has any advice regarding my problem. I have looked here and tried what has been suggested.
My stock, never rooted, never flashed, Xperia T (think it was Android 4.3 but can’t now check, the latest Sony rolled out) was working fine until yesterday. I was on a plane and noticed it had 20% battery life left so I plugged it into the onboard USB port. The problem is I think I hay have plugged the cable into the port the work way round – not the connection on the phone, but the actual USB socket. This should be impossible but somebody obviously had broken the port and it turned out the cable could be plugged in both ways! (I don’t know if it was plugged in the wrong way round but is the only thing that could possible explain the sudden death.)
Could this have bricked it? I suddenly couldn’t get a red light to show charging and holding down power on and volume up or down does nothing. I tried charging overnight via a wall socket when I got home but the result is still the same. Just a black screen and no sign of life. I have also tried plugging it into a computer with Sony’s PC Companion but as the phone is not ‘on’, it can’t be found.
Does anybody have any advice where to go from here? I’m more concerned about some recent data from holiday on the phone than the actual handset itself. If the phone is dead, is there any way to read the internal memory?
Thanks
Try this: Unplug the charger, press the power button. The phone won’t power up because there is no charge left in the battery. But press the power button along and while doing so, connect the charger without releasing the button. Now, you will probably see the red light. Please don’t take off your finger from the power button for around 1 to 2 minutes when the red light for charging will glow continuously. If you feel tired holding it, you can try sticking a tape on it in it’s pressed mode. Once you are sure that the phone is now charging the battery again(red light keeps glowing even after the power button is released) kindly wait for 5 to 10 minutes or may be more before you press the power button again to power the phone up. Now the phone will be up and running
If that doesnt work maybe ur battery is dead or usb port broken
Thanks for the advice. I gave that a go after trying a 24h wall charge and not touching it (which did nothing).
So, I held the power down, plugged it in but nothing. I held it down for around 5 minutes both manually and then repeated the process using the rubber band trick to keep the button held down but no red light ever came on. I think I’m going to try a new battery as I genuinely see that I have nothing to lose as I doubt it will be possible for anybody to recovery data given as the phone can’t be switched on so if I break it further I’m in no worse position!
Thanks again for trying to help though!:good:
When I got my xperia t it was in described condition. I also tried everything (rubberband trick and so on) but the only thing working was to open it and pull and put in again the plug of the battery. After that it booted immediately and I got this sleep-of-death-thing nearly every day... Since I soldered the battery as described in this Topic it happens only ~once a week. Good luck!
SOLVED! In preparation for the new battery arriving, I decided to take the back cover off. I unhooked the top battery connector and decided to connect it back up again, just to see if it did anything. Plugged in the charger and a red light came on straight away! I let it charge for a good couple of hours and switched it on – not as easy without the case attached – and it worked. I’m so frustrated with it being such a simple issue as needing to disconnect the battery but even more frustrated with the design that it is meant to be a ‘sealed’ unit with a non-removable battery. I used to often need to disconnect my old Omnia II battery to restart it but that was a simple case of cover off, remove battery, replace battery , put cover back on, not the creaky, back cover fear of cracking exercise of yesterday. Still it’s working now and hopefully life in the old phone yet!
Isodrac said:
SOLVED! In preparation for the new battery arriving, I decided to take the back cover off. I unhooked the top battery connector and decided to connect it back up again, just to see if it did anything. Plugged in the charger and a red light came on straight away! I let it charge for a good couple of hours and switched it on – not as easy without the case attached – and it worked. I’m so frustrated with it being such a simple issue as needing to disconnect the battery but even more frustrated with the design that it is meant to be a ‘sealed’ unit with a non-removable battery. I used to often need to disconnect my old Omnia II battery to restart it but that was a simple case of cover off, remove battery, replace battery , put cover back on, not the creaky, back cover fear of cracking exercise of yesterday. Still it’s working now and hopefully life in the old phone yet!
Click to expand...
Click to collapse
Nice to see that bro!
Stuck on "please lock bootloader" screen when plugging in after depleting the battery
No button inputs work. The only solution seems to be waiting until the battery fully runs out and plugging it in again, after which it sometimes boots up. At least I got it to the first time, it failed just now. Maybe I need to hold some button combination while doing so?
How do I fix this properly? And what's a sure way to get it to boot from this? I'm already wasting half and hour on a minute's charge, God forbid I ever forget about it plugged in for longer. Would have to throw it in the drawer for a couple days and probably end up with some permanent burn-in too.
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
What seems to have done the trick is holding power&volume+ (probably just power is enough), so it loops through the 'empty battery' splash screen at least once. I think that's how I did it the first time too.
drwharris said:
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
Click to expand...
Click to collapse
It never seemed to make any difference whether I pressed the power button or not, in fact it always booted up automatically after some time, this scenario excluded.
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
VonZigmas said:
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
Click to expand...
Click to collapse
i had a similar problem after a failed attempt to boot into recovery.
for me the following did do the trick and booted my phone back into system:
- deplete battery completely
- plug in charger and keep power button pressed until phone is charged enough to attempt boot
- keep the power button pressed until nokia logo appears
THMSP said:
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
Click to expand...
Click to collapse
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
VonZigmas said:
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
Click to expand...
Click to collapse
Well, multiple definitly isn't one I haven't stopped the time yet, but expect waiting and pressing them for around 2 to 3 minutes, maybe even 5. It might sound stupid, but it will work.
About fixing it, I don't know. It might be a bug in the reference bootloader that Qualcomm provides for Snapdragon 835 chipsets, and I doubt that FIH / HMD have the resources to debug and fix that.
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
OneDream said:
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
Click to expand...
Click to collapse
No, I guess it isn't. I've tried to plug it in while it's off and turn off as it's charging and in either case it resulted in the phone hanging up on that screen. I can confirm though that holding all three buttons for a while does turn it off and allow me to boot normally which is cool.
But is that possible with a locked bootloader anyway? Or does it always power on? I can't tell if I ever needed it to charge like that.
I see this "warning" message only on android pie builds, it doesn't seem on oreo builds. I think problem seems that kernel dependent (oreo is on 4.4.78 and pie is on 4.4.153). There is one way to get rid of that message, as @THMSP said, holding all 3 buttons pressed during 2-3 minutes and let it to be shuted down. Then, let the device to boot normally and plug in. Finally you shouldn't connect to charger when it's turned off on any pie build.