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.
OK, I've seen this twice (so it isn't complete death) but wanted to see if anyone else had any ideas. I've done a complete shut down (power button for 8 sec) and then couldn't get it to turn back on. When this is happening, I can plug it in and see the green charging light. Holding the power button then for 8 sec will make the green light go out. Pushing it again, light comes on. So the button is working... If i leave it for awhile, the nook will then reboot and appear to work normally...
Rooted, stock, 2.0.5
dbh369 said:
OK, I've seen this twice (so it isn't complete death) but wanted to see if anyone else had any ideas. I've done a complete shut down (power button for 8 sec) and then couldn't get it to turn back on. When this is happening, I can plug it in and see the green charging light. Holding the power button then for 8 sec will make the green light go out. Pushing it again, light comes on. So the button is working... If i leave it for awhile, the nook will then reboot and appear to work normally...
Rooted, stock, 2.0.5
Click to expand...
Click to collapse
If your device battery level is below 10 percent it will not turn on until it charges up to at leat 15 percent level. Then it will turn on.
hwong96 said:
If your device battery level is below 10 percent it will not turn on until it charges up to at leat 15 percent level. Then it will turn on.
Click to expand...
Click to collapse
I think that is the mechanism stopping it, but it is malfunctioning, I'm at about 90% this last time...
Is there ther equivalent of 'battery stats' somewhere that can be affecting this? or is this hardware? It should be turning on fine at 80-90% but no. However, plug in for 10 mins and it works fine. So that seems to be the problem.
dbh369 said:
I think that is the mechanism stopping it, but it is malfunctioning, I'm at about 90% this last time...
Is there ther equivalent of 'battery stats' somewhere that can be affecting this? or is this hardware? It should be turning on fine at 80-90% but no. However, plug in for 10 mins and it works fine. So that seems to be the problem.
Click to expand...
Click to collapse
OK, this is getting worse, I'm now at 100% charge and it happened. Weirder still, if I leave it plugged in for awhile, it will reboot on its own.
I have not had this happen on my HD but something similar has happened on my HD+. It seems to be related to whether an SD is plugged in. I have to take the SD out, press power off for a while, then release and momentarily press power again.
I know on the Nook Colors, they would not turn on unless it could find the boot files to boot from. So if a user formatted his internal boot partition by mistake, it would not turn on unless a bootable SD with active boot files was in the slot. Something akin to this may be happening, only in reverse.
Sent from my Nook HD+ Running CM10 on SD
Huh- will try removing the sd next time- it is a nd plus. Of course then how sui I boot to sd?
Sent from my BNTV600 using xda app-developers app
dbh369 said:
Huh- will try removing the sd next time- it is a nd plus. Of course then how sui I boot to sd?
Sent from my BNTV600 using xda app-developers app
Click to expand...
Click to collapse
Once I got it booting, then I could put the SD back in and boot to it.
(And your thread title says HD).
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
(And your thread title says HD).
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
Fixed
Sent from my BNTV600 using xda app-developers app
leapinlar said:
Once I got it booting, then I could put the SD back in and boot to it.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
OK, this seems to have worked. I tried to change the partition of my CWM SD card using EaseUS, but that seemed to make it no bootable, and removing it does seem to have worked. Now I can boot a new reimaged CWM card.
Thanks!
Good to hear that your nook is working again.
It seems i am having a similar issue, only a little more severe.
I described it here: http://forum.xda-developers.com/showthread.php?t=2088893
leapinlar said:
It seems to be related to whether an SD is plugged in. I have to take the SD out, press power off for a while, then release and momentarily press power again.
Click to expand...
Click to collapse
Something similar happened to my HD+ running the 12/31 build of verygreen's CM. In my case, I think it was precipitated by the battery draining too far first, though. Very weird and a little spooky, but glad there's a workaround.
Wow, this is dumb. I can't believe a badly-formatted SD would cause it to look like it's broken. Put a message up or something. Thanks for the help, thought something was really wrong!
Nook HD Plus won't charge
I've seen dozens of reports of this. The symptoms are all about the same.
The unit drains the battery, even if you plug it in, it still drains, so although the charger and cable are fine, something inside the Nook doesn't get the memo.
It drains down to the point where it turns off. Then every time you plug it in, the light goes green, then amber, then off. The battery never charges.
I tried taking the unit apart and disconnecting the battery overnight, but that didn't seem to help. I suspect something in the software gets in a "vapor lock" where a dead battery condition is mistaken for a fully-charged battery condition. I only paid $109 for it refurbished, so it isn't worth another $60 for a new battery, and I don't think there is anything wrong with this battery.
If I knew the pinouts of the battery connector, I might try charging it without going through the Nook. Perhaps if it was actually fully charged, the "vapor" would realign.
Does anyone have another idea, apart from the nitwit stuff Barnes & Noble allows on its forums, like "push the cable in harder" or try another adapter. I notice they aren't interested in entertaining any idea that their firmware is at fault.
It will not charge when plugged in if OTG USB is activated (e.g., to connect a USB keyboard). That's happened to me a few times using unofficial VG CM versions where the USB state can be changed inadvertently from a pull down drawer. If the USB isn't toggled back to normal in time to recharge the battery before its completely discharged, it might not be revivable.
Sent from HD+ MAG2GA CM 11 from SD
dbh369 said:
OK, I've seen this twice (so it isn't complete death) but wanted to see if anyone else had any ideas. I've done a complete shut down (power button for 8 sec) and then couldn't get it to turn back on. When this is happening, I can plug it in and see the green charging light. Holding the power button then for 8 sec will make the green light go out. Pushing it again, light comes on. So the button is working... If i leave it for awhile, the nook will then reboot and appear to work normally...
Rooted, stock, 2.0.5
Click to expand...
Click to collapse
I've the same problem, except even if I leave it a while, it doesn't boot or even appear to start. Is there something wrong with the battery or display? It was working perfectly fine until suddenly the screen froze and I had to do a complete shut down.
I cant get my nook to turn on. I try charging it and a little green light comes on at the bottom and stays on for about 3 seconds and then a orange light comes on for about 3 seconds and then it shuts off. I dont know if the light is supposed to stay on while it is charging. Sometimes it comes up with a dead battery sign but it just goes right back off.
TiffanyLandis95 said:
I cant get my nook to turn on. I try charging it and a little green light comes on at the bottom and stays on for about 3 seconds and then a orange light comes on for about 3 seconds and then it shuts off. I dont know if the light is supposed to stay on while it is charging. Sometimes it comes up with a dead battery sign but it just goes right back off.
Click to expand...
Click to collapse
Have you tried charging it with its wall-charger for an extended period (8+ hours)?
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
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.
Hi,
I've owned a B&N Nook HD (7 inch) for just over a year, when I first got it I flashed CWM and CM10 onto it and ever since have had absolutely no issues with it, however a couple of weeks back I was having trouble getting it to charge, it would take a few tries of plugging the cable in before it would finally begin (I'm not sure whether this is related at all to the issue) However a couple of days ago I was happily browsing the internet, then it made a strange "Pop" sound and the screen went completely black. Ever since then it won't boot up, it will briefly display the Nook logo but will then make the same pop sound and go to what looks like a black screen, however under low light you can see that the backlight is still faintly on, and to turn it off you have to hold the power button for 7ish seconds. Also on one attempt to boot it made it past the nook logo, and onto the cm loading screen but then had the same issue. I've also tried booting it to recovery but with no success :crying: .
Any help would be greatly appreciated, even if it's just to say that it's a complete right off.
Thanks
Probably you might have damage battery
bobjohnsonandco said:
Hi,
I've owned a B&N Nook HD (7 inch) for just over a year, when I first got it I flashed CWM and CM10 onto it and ever since have had absolutely no issues with it, however a couple of weeks back I was having trouble getting it to charge, it would take a few tries of plugging the cable in before it would finally begin (I'm not sure whether this is related at all to the issue) However a couple of days ago I was happily browsing the internet, then it made a strange "Pop" sound and the screen went completely black. Ever since then it won't boot up, it will briefly display the Nook logo but will then make the same pop sound and go to what looks like a black screen, however under low light you can see that the backlight is still faintly on, and to turn it off you have to hold the power button for 7ish seconds. Also on one attempt to boot it made it past the nook logo, and onto the cm loading screen but then had the same issue. I've also tried booting it to recovery but with no success :crying: .
Any help would be greatly appreciated, even if it's just to say that it's a complete right off.
Thanks
Click to expand...
Click to collapse
Please watch this tutorial how to remove battery. https://www.youtube.com/watch?v=YfYvhtw30mU.
Then charge your battery via external power source i.e.Master charger. If you still can't turn on your device. Then buy new battery. Link of ebay is http://www.ebay.com/bhp/nook-battery
If it is software issue @leapinlar will surely figure it out.
Thank you very much for your quick response, I'll give the link a try!
Battery Charged
keshabbhattarai126 said:
Please watch this tutorial how to remove battery.
Then charge your battery via external power source i.e.Master charger. If you still can't turn on your device. Then buy new battery. Link of ebay is
If it is software issue @leapinlar will surely figure it out.
Click to expand...
Click to collapse
I had a go at removing the battery, but as I don't have a Master charger or anything like that around, just stuck a multimeter onto the connector, and it read about 3.5v so to me that seems pretty charged.
Does this mean it is a damaged battery, as I'm on a bit of a shoestring budget, so want to make sure I'm getting the right thing
Regards
Bobjohnsonandco
bobjohnsonandco said:
I had a go at removing the battery, but as I don't have a Master charger or anything like that around, just stuck a multimeter onto the connector, and it read about 3.5v so to me that seems pretty charged.
Does this mean it is a damaged battery, as I'm on a bit of a shoestring budget, so want to make sure I'm getting the right thing
Regards
Bobjohnsonandco
Click to expand...
Click to collapse
I've install stable cyanodgen 10.2.1 a year ago and have this issue ever since. Not sure if it's common but whenever the nook is drain completely to dead...when you try charging it..the light would be green..then amber. So I don't know whether its charge or not but I guess it is. I would not be able to power it back on...the normal way. It would seems dead. The way for me to get it to power up is to get into cwm recovery by pressing both the power and home button at the same time, then reboot it. It gets annoying because I would have to do that all the time since my 5 year would drain it out lol