Hi all,
I bought a Nook HD+ around a year ago, and installed CM11 and CWM recovery on it. Everything worked fine until coming back from a trip in June, when I noticed that the power button required several tries to power on the device. I thought nothing of it until I came home and found that it wouldn't turn on at all, having tried all the button combinations and power cycles suggested in these forums. Now here's the strange part: I believe the internal eMMC may be corrupted because a) there's no battery icon when plugging it in. and b) when trying to turn it on, the screen is clearly on for a couple of seconds. It turns grayish and I can see the edges of backlighting, but there's nothing on it. Also, it won't boot from microSD or show anything on the screen at all. So, I have two questions: 1) What is the cause of this problem, e.g. broken screen or bad memory, and 2) What can I do to fix this? The tablet is just out of warranty, but I do live relatively close to a B&N store.
Thanks in advance,
sgamer395
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
Hello all...I get a black screen, and nothing more. (Tried for 5-6 hours of different combination of holding the power and n button etc.) Still nothing
This happenes with, and without an SD card in there.
Tried all combinations of different recoveries with CWM and other SD boot suggestions.
All I did was root it, and then used CM7 off an SD card. Working fine for a day...then today it all stopped completely.
The only way I'm getting activity is when I plug it into the computer. I makes the chime of that it recognizes new hardware, and immediately makes the chime of that it was unplugged (which its not) Still nothing on the screen though.
Right before I could no longer boot...my screen was turning yellow...yellow lines, and odd pixles. Luckily I took a picture (see attachament) so everyone can get what I'm saying
Would this be a symptom of a hardware faulty Nook? Its only 3 days old...safe to bring it back to B&N for a exchange...even though its rooted?
I understand rooting will void the warranty, but does it void getting an exchange from B&N?
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.
Hello guys, I am in need of some serious help, but please excuse me if I ask too many newbie questions.
I was running SlimROM on my Nook HD+ (I came back from running CM10.1>CarbonROM>SlimROM>CM10.1>SlimROM) and browsing the web late a couple of nights ago when the nook turned itself off. It rebooted itself and got stuck in the CM spinning logo for about 5 minutes. Since this had never happened to me before, i hard reset(held on the power button for long to force a restart) and now it is stuck on the Nook logo until the battery is fully drained. I tried rebooting it many times, while trying to force it into CWM recovery by pressing the vol down/vol down+home while turning it on. No effect, it just keeps showing the Nook logo.
So I brought out my SD card using which I had first installed CWM and CM upon receiving my new Nook HD+ and tried to boot from it. It starts up, shows the Nook logo, then goes on to Cynoboot Universal Bootloader logo for a few seconds, dims, then lights up again and gets stuck there. It then shuts down the Nook itself after a couple of minutes or so.
I brought this tablet with myself to Afghanistan, where I am currently stationed, so I cannot even go into a B&N store until my next R&R (not that I want to take an EMMC flashed Nook to B&N anyway). Please advise.
Am I going to have to buy a new tablet?
Thankyou very much in advance.
chr0 said:
Hello guys, I am in need of some serious help, but please excuse me if I ask too many newbie questions.
I was running SlimROM on my Nook HD+ (I came back from running CM10.1>CarbonROM>SlimROM>CM10.1>SlimROM) and browsing the web late a couple of nights ago when the nook turned itself off. It rebooted itself and got stuck in the CM spinning logo for about 5 minutes. Since this had never happened to me before, i hard reset(held on the power button for long to force a restart) and now it is stuck on the Nook logo until the battery is fully drained. I tried rebooting it many times, while trying to force it into CWM recovery by pressing the vol down/vol down+home while turning it on. No effect, it just keeps showing the Nook logo.
So I brought out my SD card using which I had first installed CWM and CM upon receiving my new Nook HD+ and tried to boot from it. It starts up, shows the Nook logo, then goes on to Cynoboot Universal Bootloader logo for a few seconds, dims, then lights up again and gets stuck there. It then shuts down the Nook itself after a couple of minutes or so.
I brought this tablet with myself to Afghanistan, where I am currently stationed, so I cannot even go into a B&N store until my next R&R (not that I want to take an EMMC flashed Nook to B&N anyway). Please advise.
Am I going to have to buy a new tablet?
Thankyou very much in advance.
Click to expand...
Click to collapse
I thought the normal way to get to recovery is to power up with the nook button held down? - have you tried that?
jazzy2fives said:
I thought the normal way to get to recovery is to power up with the nook button held down? - have you tried that?
Click to expand...
Click to collapse
Yes, i tried that first, then the vol down+power and then vol down+nook+power. I guess I was desperate, and searched everything remotely similar to the issue.
jazzy2fives said:
I thought the normal way to get to recovery is to power up with the nook button held down? - have you tried that?
Click to expand...
Click to collapse
That is not the way to boot to recovery. You boot to recovery from power off by holding BOTH power and n for like 5-8 seconds, releasing power first followed a few seconds later by releasing n. But be careful how long you hold power, if you hold it too long it will power back off.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
That is not the way to boot to recovery. You boot to recovery from power off by holding BOTH power and n for like 5-8 seconds, releasing power first followed a few seconds later by releasing n. But be careful how long you hold power, if you hold it too long it will power back off.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yes sir, that's what I meant I tried. I have (successfully) force booted my way into recovery a couple of times before, but this time it is just stuck on the Nook logo (or cyanoboot logo if I power up with the CWM/CM SD inserted)
Wow. So many views on the post.
Guess the tablet is done for then.
Anyway, thankyou devs of CWM, CM and other ROMs who made my short journey with my first Android so very informative.
Would love to come back here when I buy my new tablet. I think it will be the new Galaxy note 10.1. Or the Nexus 10.
'Till then.
-
Chr0
I'm a real newbie to this stuff, so I may be talking rubbish and I'm not familiar with the ROM you were using, but is it possible you're emmc is damaged, for instance by trim. I know there are some people on the board running of special SDCard only roms, and some talk of possible ways to recover damaged emmc.
The reason I say this is it seems stuff is working up to a point, I think even the normal bootable SDCards and recovery partition probably try to mount some things from the emmc, and I wonder if this is where it's freezing up.
Until recently, my HD+ has continued to labor on almost flawlessly since converting over to full Android quite some time ago. It is currently running v5.1.1/CM 12.1-20151018 Ovation.
In the last two months it has started to simply not boot up (even while fully charged) unless I plug it in. Even then, it takes several minutes before it boots. I can get it to reboot while unplugged, but if I fully shut it off by holding down the power button, it will not restart unless I plug it in again.
Have had to go to holding the power button down for full shutoff as it also will spontaneously reboot if you select power off from the menu.
As it has not exhibited any issues until now, I am clueless as to what is going on.
I am using it only for viewing photos taken with my digital camera via its sd card, using it for graphic novels, and using the Prestigio ereader for for ebooks with photographs and color plates.
Other than the apps for the graphic novels and Prestigio, I have it totally stripped down and don't even use the wifi connection.
Will be very greatful for any assist with fixing this.
Could it be as simple as refreshing 12.1 or should I go back to 11.1?
PS: Appears to be related to having the sd card inserted or not. Will start with card out when it won't with it in. Cannot reboot into TWRP.
PPS: It was definitely the sd card used to configure the Nook. Replaced it with a clean one and (almost) all of the problems disappeared.
Still does a spontaneous reboot if I use the software "Power Off" from the menu once the power button is pushed.
If I hold the power button it will fully turn off and not reboot. and then starts normally.
For the limited use I have configured it for, I should leave "well enough" alone at this point.
Any ideas as to the spontaneous restarts???
It still has one of the best screens around!!!
Thanks in advance.