Hi all,
We got our Nook HD+ on Wednesday. I was intending to root it and install CM 10.1 but haven't even got that far before problems have started. I thought I'd post this just in case anyone else had the same problem. When the problem first started, it still should have had plenty of charge left. I had been using it to read a book and play a game earlier in the day. I turned it off after use; now it won't boot back up again. The backlight seems to come on for a few seconds but then goes off. Holding Power and 'n' does nothing except turn the backlight on as previously mentioned.
We have not modded this device in anyway, neither is there a micro-SD card in the device. It is now fully charged but still presenting the same issue.
If anyone has come across this before, or knows another way to do a hard reset, please let me know.
Thanks, Peter
Let it charging for a while then try what you did again.
extrem0 said:
Let it charging for a while then try what you did again.
Click to expand...
Click to collapse
That's what I did this morning. No difference.
iamthefish said:
Hi all,
We got our Nook HD+ on Wednesday. I was intending to root it and install CM 10.1 but haven't even got that far before problems have started. I thought I'd post this just in case anyone else had the same problem. When the problem first started, it still should have had plenty of charge left. I had been using it to read a book and play a game earlier in the day. I turned it off after use; now it won't boot back up again. The backlight seems to come on for a few seconds but then goes off. Holding Power and 'n' does nothing except turn the backlight on as previously mentioned.
We have not modded this device in anyway, neither is there a micro-SD card in the device. It is now fully charged but still presenting the same issue.
If anyone has come across this before, or knows another way to do a hard reset, please let me know.
Thanks, Peter
Click to expand...
Click to collapse
Did you try holding the power button for like 15 seconds, releasing and then briefly hold the power button? If you hold it too long, it turns itself back off.
If you tried that and are sure it is charged and it does not turn on, it is a hardware issue and it is time for a warranty exchange at the B&N store.
Sent from my BN NookHD+ using XDA Premium HD app
Had a similar issue the first time... Power it on... Plug the charger, leave it with the screen looking like this and wait 20 minutes. Reboot and check if it boots properly. If not, try rebooting by holding the power button and the volume buttons simultaneously...
KostasR said:
Had a similar issue the first time... Power it on... Plug the charger, leave it with the screen looking like this and wait 20 minutes. Reboot and check if it boots properly. If not, try rebooting by holding the power button and the volume buttons simultaneously...
Click to expand...
Click to collapse
Thanks. I went on the Nook UK support chat and they couldn't instruct me to get it started again. It's been returned and hopefully our replacement will be on the way soon. Possible hardware fault was the suggestion.
Related
okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
I have a similar issue.
Sometimes just the capacitive buttons light up and not the screen. I have to make 2 or 3 tries to get it to turn on. Its rare, but its there. It only happened on 2.2.
ok good, me too!
was just looking for this topic.
mine doesnt always turn anything on at all. sometimes the light go on, others nothing. Also trying to turn off the phone is hard as it sleeps straight away with out opening up the power menu.
I have a stock N1, which recently updated to Froyo, with the same problem.
any ideas would be great!
cheers,
lorin.bute said:
I have a similar issue.
Sometimes just the capacitive buttons light up and not the screen. I have to make 2 or 3 tries to get it to turn on. Its rare, but its there. It only happened on 2.2.
Click to expand...
Click to collapse
Also happens on CM 5.0.7.1.
i think it may be a hardware button issue.
I have tried turning mine off (had to pull the battery out) and then to turn it on.
It should turn on readily as it has nothing to do with the OS at that point.
any ideas?
No HW button issue described. HW button works - if it didn't, lights wouldn't go on. It's a wrong reaction on the button, at least that's what OP describes (and me too).
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
I've read more than one or two threads on power button issues, and I know what I'm talking about. My power button DOES power up the phone when the battery is taken off the first shot, it DOES wake the phone from standby, it DOES register long presses - there was even one time when a second press was long, and suddenly the screen woke up with power menu, while the first press left it dark with touch button light going on.
Doesn't look even a bit like HW to me. HW would leave the phone dead, non-responsive to touches, or create a loose touch which would translate into several touches - none of those would EVER turn into a phone being on with screen off, and suddenly snapping back to screen on when the SCREEN is touched several times.
Could be your cpu was too busy to accept any inputs.
I have a thread about it here:
http://forum.xda-developers.com/showthread.php?t=692874
Take your time! As for me, I'm using my N1 for 3 months now for the power button to completely dead with everyday use (I didn't use any app to trackball-wake).
As I said, all the things you are yelling I have been through. And I, too, thought it was software problem.
I tried both MCR and Cya with no hope.
Good luck!
ps: One of my friend just told me about his N1's power button issue right after hearing me telling about mine.
This sucks
anyone know where i can buy a new button??
Corrupt SD Card
I had the same issue. I'd press the power button, the bottom four buttons would light up but no screen wake. Only way to get out of it was to pull the battery. It would happen maybe 30-40% of the time. (Nexus One Froyo FRF72)
I think it was due to a corrupt MicroSD card. I recently installed a 32gb card and put some music on it using songbird and possibly didn't safely remove. That's when I started getting issues. Removed the SD card completely and it worked fine. Changed back to the old card and no issues. Then formatted the 32gb and tried again, worked fine. Then I tried to transfer more music, there was an error and I got the same problem. (Cheap ebay card from Hong Kong, that'll teach me).
Anyway, I'd be interested to know if that solved anyone else's problem, because all I see on forums are that it's a faulty power button, but that didn't seem to be the case in my situation.
Cheers,
Dylan
-Witty esoteric statement about science/technology.
Mine is doing kinda the same weird thing but a little different.
When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.
It usually does this after being inactive for a period of time, like after sitting overnight.
FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
jimbobalu said:
Mine is doing kinda the same weird thing but a little different.
When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.
It usually does this after being inactive for a period of time, like after sitting overnight.
FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
Click to expand...
Click to collapse
i have almost the same issue, although mine happened twice when i was on EPE54B but it's been far more common on FRF91
the only difference is my power will continue to turn the back light on and off no matter if the screen has already timed out or not
kobecamp2009 said:
okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
Click to expand...
Click to collapse
I have exactly the same issue. Over in the general forum, there's another thread on this issue. Many, myself included, are reporting that this problem started after the FRF91 update. Can you confirm?
rtx101 said:
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
Click to expand...
Click to collapse
Read again carefully. Are you sure your hardware problem was identical to what the OP described? I've noticed a lot of people with obvious hardware problems (i.e., the power button is completely unresponsive) posting on threads like this when they actually have a different problem. It's very confusing.
britoso said:
Could be your cpu was too busy to accept any inputs.
I have a thread about it here:
http://forum.xda-developers.com/showthread.php?t=692874
Click to expand...
Click to collapse
This sounds VERY promising -- thank you britoso!
PS: Are you guys getting the unresponsive unlock slider like britoso describes?
I had this problem when I first flashed CM6 yesterday. Even after wiping and reflashing it was the same. Only way to get out of the black screen was to do a soft reset, power + vol down + trackball. I finally found out that my SD card malfunctioned and was corrupt. I tried reformatting the sd card in an microsd card reader but windows said it could not be reformatted. I finally switched back to another microsd card that was working, wipe and reflashed cm6 and the problem went away. Try backing up all the data on your microsd onto your computer then reformat it and wipe then reflash to see if it works
Edit: ughhhh it just happened again, but not as bad as before, turns back on after second try... maybe i didnt press the trackball hard enough
Hey all. So up until about a week ago I was running CM7 nightly build 150 something on internal memory and all was fine on my nook, with just the occasional issues with the facebook app, but SoD seemed to be gone, and so on. Recently I updated to CM7 build 253 which fixed my Facebook problem, seemed to run better blah blah blah. I made some changes, added some new widgets (HD widgets was only 10c on the market!), and SoD had seemed to come back. I was literally checking my email, I put it down, checked it again 1/2 hour later and it was dead.
I wasn't too concerned because in the past all I would do is plug in my charger and it would pop up. Well not this time. It wouldn't come back on, the power switch wouldn't work either. So I decided to let it charge up fully. This morning, power button still didn't work, unplugged it and tried again. It just straight out won't even try to turn on.
I'm considering trying to format my SD card as bootable and see if something maybe just got cooked internally.... But I have doubts that it would even boot from that. Unfortunately didn't have time to test it much, but has this happened to anyone else? Do I now own an expensive doorstop?
I don't know that it'd work very well as a doorstop :/
Hold the power and n button down for a lonnng time.
Sent from my HERO200 using XDA App
From what I understand it's not possible to brick it. I assume you read the thread of how to unbrick pinned to the top of this forum? That is where I would ask the question if it is still open.
Also try just holding the power button alone for a long time. Wait a few seconds. Then try to boot again.
Hold down the n + power button for 10 seconds. Release. Hold down the power button for 10 seconds. Repeat this process 2 or 3 times, if necessary. Has never failed me.
Try making a bootable SD card and see if it will boot that way.
---------------------------------
Sent from my LG Optimus V using Tapatalk
k8108 said:
Hold down the n + power button for 10 seconds. Release. Hold down the power button for 10 seconds. Repeat this process 2 or 3 times, if necessary. Has never failed me.
Click to expand...
Click to collapse
I had to do this about 7 Times, then it finally booted.
What was stranger, the battery level was the same as when it died, even though I had plugged it in and "charged" it till the n light went green. According to the battery history it basically seems as if I had simply shut it off and never plugged it in.
Normally I wouldn't be so concerned about a SoD moment, but in almost a year of having the nook color it has never locked up like this (running CM7 anyway).
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
IIRC the Xperia Z1 has a hard reset button under the sim flap, it's a small red button, give it a shot.
remove sim card and sd card and try again, if it's still not responding do an update repair using SUS or PCC
BTW there is a known fault with the XZU and it could also be on the Z1 as they use similar Firmware, what people have found is that the phone will start up eventually and then they go into the display setting and untick the auto backlight option and that fixes it
I also reboot my Z1in this way when it blackout.
Sent from my C6902 using xda app-developers app
Had the same issue called Sony, push hard reset button all is fine in the world. Known issue Sony is working on it
Sent from my C6903 using Tapatalk 4
Managed to hard reset using power and up volume .
Put it on charge overnight but it doesn't see,m to have taken any charge at all....just trying again using diff PSU and cables but it doesn't want to charge. It recognises that I've out a cable in as I played with the smart connect setting. When it is off completely I get a red light (presumably meaning its charging ) but not in android
Any ideas?
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Sometimes phones have issues. I got one once that had no speakers or Mic inside... it happens lol
Try to go exchange it, and see if the next device gives you issues.. if not then you're good, if it does pick a different phone..
Do it soon though, most carriers only have a 14 day exchange period, and then after that will charge you all sorts of fees and try to fix your phone rather than just giving you a new one....
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
thefunkygibbon said:
Got it charging again by pushing the red button near sim slot for a couple seconds.
Just had another issue with SD card not being recognised after I removed another (/safely) had to reboot again using power plus vol up as it stuck on the shutdown logo when I tried to power down'...
Wow I can't believe the amount of issues I've ran into within 24hours of having this thing. I really don't know what to do...return it because it sounds like a faulty device (but all the issues are seemingly unrelated) or return and get another phone (is anyone else getting problems like I am?)
Click to expand...
Click to collapse
sounds like a similar problem I had with my 64gb SD card - as I mentioned above remove all cards then start from there - a reflash of the firmware might help also
thefunkygibbon said:
ok so i've been using it a bit but my battery was 70% last i checked. was playing around with throw and just opened youtube and the screen flickered a bit (black lines) then decided to go black completely.
nothing i do will make the screen do anything.
holding the power button for ages (usually the way to turn off/reboot a phone) doesnt do anything. the backlight is on as i can see that. but nothing is on the screen.
anyone got any ideas on how to force a shutdown/reboot on these?
Click to expand...
Click to collapse
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
LadFromWales85 said:
Something happened to mine with Youtube too. I'd started a video and paused it on a frame for comparison with another screen. While I was setting the other phone up, the screen on Z1 timed out. I pressed power, the screen come on and flickered, then went black!
Power and both volume keys function the same as the red button under the flap. I wasn't able to reproduce the bug.
Click to expand...
Click to collapse
yeah i've been trying to reproduce it and failing to. very odd. maybe its something to do with the first time you use youtube and do something specific?
gunna phone o2 up tomorrow and see what they say about all my issues. seems to have been fine this last 24 hours though and in their eyes that is prob reason enough not to issue a replacement.
I've had mine since Monday and this happened to me yesterday. I was troubleshooting sending MMS with T-Mobile tech support (not a phone issue as it was happening on previous phones too) and had to restart the phone several times. I noticed upon restarting that the backlight seemed to be on but the phone was not booting up. Had to perform several hard resets (both with the red reset button as well as the power/volume up buttons) before it FINALLY rebooted and stayed on. While trying to figure this out I ran a Google search to see if others were having this problem. One solution was to make sure the backlight option is checked. I had been messing with settings the night before and must have unchecked it. Since I rechecked it I haven't had the same issue.
Hey guys,
I left my HTC One to charge and when I tried to unlock it, it wouldn't respond. Right now it's a blank screen, the red LED is on even when I unplug the phone, and the hardware buttons are lit. I've tried to restart the phone by holding the power, holding power + volume down, but nothing is working. Device isn't showing up under adb or fastboot devices. What is going on? How can I fix this?
Help me out. Thanks!
-Coby
Edit: Recently this has been happening to my phone frequently, but I am usually able to get it to restart doing the methods said above. This is the first time I can't get it to do anything.
Put it under a stronger light and longpress power + vol-
Try this
I was actually searching through old threads and found that same answer and tried it. I can't believe it worked! Thanks! Why does this happen though? And will this hopefully prevent it from happening later on?
Are you rooted with a custom rom?
However, idk why it happened
Guich said:
Are you rooted with a custom rom?
However, idk why it happened
Click to expand...
Click to collapse
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
COBYATCH said:
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
Click to expand...
Click to collapse
:good:
Strange that you had this issue, but :good:
Guich said:
Put it under a stronger light and longpress power + vol-
Try this
Click to expand...
Click to collapse
Why the stronger light? Im confused! :cyclops:
This has worked for me a ton of times too, I guess it must just trigger something with the light sensor the phone has and wakes it up.
TwinAdk said:
Why the stronger light? Im confused! :cyclops:
Click to expand...
Click to collapse
It's a tips
Maybe the light sensor is always on...
Sent from One with Tapa4
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
kungfudavie said:
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
Click to expand...
Click to collapse
Can you please give me a little bit more details?
I have exact the same issue: The battery ran out completely, then I can't charge it or turn it on.
I have tried
1. with charger connect to outlet, power + vol-
2. with charger connect to PC, power + vol-
3. under desk light, without charger connected, power + vol-
Nothing worked for me.
Some questions:
- Should I connect the cable when I attempt to turn on the phone?
- Is normal desk fluorescent light "bright enough"?
- Should I move the phone under the light first then press the button, or the other way around?
Thank you for your help!
i have the same problem in my htc eye. i tried your solution. but it won't worked for me. phone still on blank screen and red light is on. how can i fix it?????
I have been using my nook HD+ on CM10.1, 10.2 and 11 for a few months with no problems. Then recently I got a weird problem. After some investigating and testing I can consistently replicate it as follows:
Leave it idle at 12:00pm.
Screen goes off at 12:01pm. (normal, because set to 1 min)
Now if I touch the screen or press the 'n' button or press the power button at 12:02 or 12:03, the screen comes back on, which is normal behavior.
However if I touch the screen or press the 'n' button or press the power button at 12:11 or about 10 mins after screen off, nothing happens, the screen does not turn on. It feels like it has turned off, but I don't think so because I have to hold the power button for 5-10secs to "forced turn off" (no visual indication), let go then hold the power button again and it will boot up the nook like it was turned off.
I have assumed software error at first so I completely wiped the entire nook, including /system, /data, /0, reinstalled a fresh M6 or M8 along with pagapps, but get the same problem behavior on the fresh install.
I'm out of ideas and suspect a hardware fault of some kind that may not be fixable by me. Anyone has the same problem and found a fix?
Edit: additionally, the 10mins is not fixed. It could be 10 mins this time, 20mins at another time. Also if I plug in the charger at this point of time, the led is a steady green.
Edit: more googling yielded the term 'sleep of death' that have somewhat similar symptoms. Still no solution yet.
Do you have a case with a magnetic cover? If so the solution is to open the cover twice.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Do you have a case with a magnetic cover? If so the solution is to open the cover twice.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Nope it's not that.
Googleplex84 said:
Nope it's not that.
Click to expand...
Click to collapse
I don't know how to fix your problem, but it is caused by your device going into deep sleep. The device is designed to enter a very deep sleep mode after 10 to 15 minutes of inactivity. This is to save battery. For some reason your device is hard to wake up. You might try playing with some of your settings, like whether wifi stays on in sleep mode, etc to see if that helps. The HD+ does not suffer from SOD (Sleep of Death) like the Nook Color used to.
Sent from my BN NookHD+ using XDA Premium HD app
Wifi may not stay on in sleep mode anyway even when set to always on - though I've not noticed this problem since M8 on the nook hd+, my phone does still have it. Perhaps enabling it will help due to wakelock on the cpu (keeps the cpu in use during sleep).
Noticed at rare times in the past that the screen could take much longer time than normal to come back on. It could just be hard to wait long enough. Don't know how long you were waiting but I've done the same thing as well as waiting for it to finally turn on.
If your using a lockscreen, you could try disabling that completely. Sometimes, there are bugs there.
In case anyone else has my problem, my workaround is to install wake my android pro so that it remains in sleep and never goes into deep sleep.