Related
Need a little help here...out of the blue today my phone started continuously re-booting itself. Only gets to the HTC screen and then re-boots. I have done multiple battery pulls with no results. I cannot boot into recovery either, tried that many times as well. My only option is a screen that I have not seen before that asks if I want to clear all data and then reset the device. Anyone have an ideas? Running Fresh 2.3.3, had no previous problems.
I had the same thing happen today. I had just flashed Fresh 2.3.3 to try to fix the GPS issue in the CM6 830 nightly, and my phone started rebooting every minute or so. I pulled the battery and immediately booted into recovery by holding down <home> and <end call>. I was able to get to recovery, where I flashed a different ROM I had on my SD card. I hope this helps.
Well I don't know what I did but this morning when my nookie froyo emmc was at 20 percent it decided to turn off and not turn on and won't turn on when charged and will not boot any sd cards. I feel stupid but after my nook working on emmc froyo for a week and now its not even turning on I feel very stupid. All help is appreciated, thanks!
Sent from my ADR6300 using Tapatalk
Have you tried booting to the CWR card yet? And using Samuelhalff's zip that restores the stock partitions? This seems to have worked for many people experiencing the fatal Froyo crash. Take a look at the 'Easily Restore to Stock" thread found here in the Nook forums. And in the end if your device truly won't turn on, then chances are the guys down at B&N won't be able to either. *Warranty*
Well I have tried monster root pack as a card but I haven't tried stock partitioning,i dont know where the thread is. But will this let me even boot an sd card ?
Sent from my ADR6300 using Tapatalk
RileyGrant said:
Were you running froyo off emmc? If so:
http://forum.xda-developers.com/showthread.php?t=931720
I recommend flashing this ROM instead though (pre-rooted 1.1):
http://forum.xda-developers.com/showthread.php?t=932145
And yes if you insert the CWR sdcard into the nook and hold the power button, it will power on. The reason it isnt powering on currently is because your froyo boot partition is corrupted, not because of the nook itself. The CWR sdcard has a different boot partition that your nook will see and boot to when you hold the power button down with the CWR sdcard in.
Click to expand...
Click to collapse
Thats my post from an earlier thread with someone having the same issues. It worked for him, it should work for you. Just make sure you follow the steps right and especially make sure your burning the Clockwork image to your SDcard correctly that way it will boot into Clockwork instead of staying black.
I'm gonna have to give these steps a whirl. The downloads are taking foreeeever.
Also had Froyo installed with CWM and just got finished installing gapps. I went to format an SD card, had no luck, and tried to reboot. Ol' Nookie decided not to come back to life after that.
edit: wait, instead of flashing the stock rom can I flash the pre-rooted 1.1 rom?
Just read this over on android central (in a thread about flashing honeycomb). I believe it is what I did and why my nook won't boot:
****While running Honeycomb from Internal Memory NEVER choose the option to format your SD Card from within Honeycomb. The files that were altered to let HC run internally will lead the OS to actually format your boot partition instead of your SD. If you need to format an SD, do it on your computer or in an Android phone, etc.*****
Click to expand...
Click to collapse
Drat. Just got my CWM image on my sd card. Here goes nothin! Will report back
OK, I have CWM booting off the SD card, i'm formatting system and data under mounts and storage, and then i'm installing the 1.0.1 complete restore. It goes through and then I got to reboot system. Then...nothing. Back to black screen. Help please!
I can pop the SD card back in and boot back to CWM. I've tried several times now with no luck
samuelhalff has a flashable zip that restores the boot partition for situations like this. Go look for it in the development forum. you should be able to flash it using CWR and your NC ought to boot.
eyecrispy, thank you! samuelhalff's boot zip followed by his 1.0.1 complete restore zip did the trick.
RileyGrant, thank you for your post as well. Much obliged!!
Mine just shows a blank screen. All I did was boot into ClockwordMod Recovery, make a backup, then reboot. I was going to flash the Honeycomb Rom, but decided to give it some more thought first. Now All I get is the blank screen, it won't power all the way off, and it won't power on or anything
EDIT: Managed to get it to turn off, but when I turn it back on it boots into recovery. I select Reboot System now, and it reboots back into recovery. Forgive me, I'm so new to this Nook Color thing lol
EDIT AGAIN: Tried using the Monster Pack or whatever, flashed the removeclockwork.zip, followed by the installclockwork.zip, then removed the SD card, rebooted, and went right back into Clockwork Recovery. What gives?
YUP Same thing happened to me. I have read all the posts in this thread and i did try to format the card i had in my nook in the brand new phiremod froyo rom. Now it wont boot at all. I have a CRW card on hand and it wont even boot that. Idk right now, nothing is working.
Try reading through the Dummies Guide to Fixing 'My Nook Won't Boot'.
I did it last night and I'm back up and running again. Here's my post for an abridged version of what I did last night: http://forum.xda-developers.com/showpost.php?p=11374824&postcount=29
I had the same problem until I flashed the repartition fix.
Give that a try
I've got the exact same problem as the OP. Running Froyo on EMMC with no problems for a few days, then I left it for a while and now it wont turn back on or boot from uSD.
I've tried long presses on the power key, usb cable power up, but nothing works. I've tried the v4 HC image and the clockwork recovery image and neither are booting.
I verified the CWR image on my android phone and it does boot on my phone, so the image is definitely okay.
Hate to think it, but could this be a battery management issue in the 0.6.7 image and the battery is now screwed? Doesn't seem like boot partition corruption to me.
Any comments or suggestions are welcomed
ChrisAC84 said:
Mine just shows a blank screen. All I did was boot into ClockwordMod Recovery, make a backup, then reboot. I was going to flash the Honeycomb Rom, but decided to give it some more thought first. Now All I get is the blank screen, it won't power all the way off, and it won't power on or anything
EDIT: Managed to get it to turn off, but when I turn it back on it boots into recovery. I select Reboot System now, and it reboots back into recovery. Forgive me, I'm so new to this Nook Color thing lol
EDIT AGAIN: Tried using the Monster Pack or whatever, flashed the removeclockwork.zip, followed by the installclockwork.zip, then removed the SD card, rebooted, and went right back into Clockwork Recovery. What gives?
Click to expand...
Click to collapse
how did you get yours to turn off, my screen says loading... and is stuck there. any help in getting mine to shut off would be helpful
Does holding power button for a few seconds turn it off?
Same thing happened to me, this fixed my problem: http://forum.xda-developers.com/showthread.php?t=986977
Sorry for asking what's probably a silly question, but I haven't seen an answer. Is this known to the Nookie dev(s) and being addressed? Just had it happen running Nookie 0.6.8 off the SD card. I was really enjoying it and just telling the wife how I think I'll flash it to the eMMC, but I might have to reconsider if this might occur. Battery was ~80%, no goof-ups reformatting anything. Locked the screen around 1:10 this afternoon & hadn't touched it since. Got home about an hour ago to turn it on, nothing. Disappointing, Nookie is pretty good!
nook color wont turn on
so what to do if i dont have a sd card with cwr or honeycomb (what i was trying to run)ive already called for the replacement, but i would still like to know what to do.
I found this thread after suffering the same or similar problem to everyone else. I turned off the screen and set my nc aside for a few minutes, then it would no longer boot. Screen just stayed black and was completely unresponsive to any input. Working my way through some troubleshooting, I plugged the nc into my computer via USB and it booted into CM7 instantly. I have no idea why this happened, but it's working fine now.
ok so weird problem here..
my NC is fine besides this one problem.
ive rooted with autonooter to 1.0.1
if i turn my NC completely off and leave it all night, when i wake up in the morning it gets stuck on the "touch of... " screen. The only way to get past this is to reboot to recovery and select reboot..
any idea why this happens? if i just restart the NC, or just let it go to sleep this doesnt happen, only when its been fully off for a couple hours.
ive tried reverting to stock/rerooted all that to fix it, but nothing seems to work.
i know i can just let it sleep and problem solved, but id like to know why this happens or if anyone experienced anything like this before.. thanks!
Try holding down the "n" button while turning on the unit...
Other wise you might have messed up your boot partition, go to development and search for samelhaff's thread on a flashable zip where you can fix the boot.
it reboots to recovery (power+n) just fine... just doesnt reboot normally (just pressing n) .. gets stuck on touch of.. screen
after getting into CWR and selecting reboot it then boots up correctly..
dont know why it just wont reboot normally to begin with.
Same problem here.
After some testing with HC and CM7 roms i recovered to the 1.0.1 Eclair rooted with autonooter version. I turn it off and on some times and everything worked allright. Left it all night off and when i turn it on in the morning i was stuck at the "Touch the future...".
I flashed the stock boot repartition and it started normaly.
Yesterday i flashed the custom Froyo 0.6.8 and everything was allright untill the morning when i stuck again athe " touch..." screen.
I booted with CW and rebooted normally.
Same thing has happened to me twice. I've only been able to get it to boot by booting from my bootable cwr and selecting restart.
Also been noticing some oddities with it charging fully, sometimes while plugged in the status is simply "not charging", not "charging" or "dischargin" and the N symbol on the end of the cable is yellow, not green.
Now it's even worst. Every time i try to boot i get stuck in the "Touch..." screen and i can only boot through CW recovery.
Any ideas?
Glad I finally found some people with the same problem
So initially I took my stock nook (1.0.1) and ran autonooter. Worked great but I noticed it would randomly reboot. Also , same as the other posters, if I powered it all the way down it liked to automatically power up and get stuck on the boot screen. Only way to reset was boot into CWR and select the reboot option from there. I loaded CM7 and same problems so i thought it may be some kind of hardware issue.
Reverted to stock, no problems.
Back to autonooter and this time ran dual boot from EMMC with stock as main partition and HC v4 on second partition. So i don't have CWR anymore but have my SD card handy in case I need it.
Well after a couple days of normal usage the random reboots are gone. Left the unit on during the whole time. Last night I turned it off to apply my Phamtomskin and this morning woke up to find it stuck on the boot screen. Must have been doing that for a while because when i stuck in the SD card for CWR it gave me the low battery warning. After 15 minutes it rebooted to CWR and i was able to reboot normal from there.
Hopefully since a couple of us got the problem we can find some sort of fix. I would like to know if it is some kind of hardware issue or as poster #2 suggested its a simple matter of flashing the boot file. Would I loose my dual boot partition if I flash this zip? Any help appreciated and thanks what a great XDA community.
I think that it has to do with CW and boot. Can i remove CW recovery without affecting my configuration?
no change.
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
bump this?
pilotbluemike said:
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
Click to expand...
Click to collapse
Just get the bootable cwr, then you'll always have it handy. The stuck at touch of reading screen has happened to me twice, pulled out my bootable cwr, selected restart and all was well.
I've never heard of anyone having this problem with V 1.0.1. I know that a lot of people are having this same problem with V1.1. Apparently CWR and V1.1 don't coexist well. I had this problem after doing Stock Nook 1.0.1 --> Autonooter 2.12.25 --> Sideload to rooted V1.1. Some people also have the problem when going from stock V1.1 and using Autonooter 3.0. The fix in both cases is to uninstall CWR using the CWR removal tool mentioned here:
androidtablets.net/forum/nook-color-technical/6386-how-installing-using-clockworkmod-rom-manager-nandroid-backup-custom-kernels-20.html#post48469
(sorry, I can't post links yet.) It leaves the device rooted. It worked for me.
I asked a question similar to this earlier, but since then my issue has expanded a bit.
Basically, my problem is this: occasionally (I now have no idea what causes it) when I boot my Nook Color it doesn't boot past "Touch the Future of Reading" OR, when running CM7, it won't boot past the CM7 boot animation (no idea if these two issue are related).
On rooted Eclair, booting into CWM and running "fix permissions" and "clear cache" (per sebanoel's advice) fixes the problem, but doesn't help at all when booting CM7. Is there a known cause of this issue and a way to prevent it?
Also, I flashed CWM onto the NC itself using ROM Manager (to avoid having to carry my recovery SD with me everywhere), but I cannot boot into it using power+n. ROM manager's "Boot Into Recovery" command works, but not the buttons. I've read a few places that the button combo has changed, but these posts are ambiguous and don't offer an alternate button combo. Am I pressing the right buttons? Is there a place i can find definitive info on this?
One last question: is the NC supposed to power on whenever it's connected to a charger? Mine always does, and i think it's weird. Is this normal?
I'm having a very similar problem. I don't know what it is.
I switched over to Honeycomb on SD, then CM7 internal. Tried to put HC internal and nothing has worked. If you get an answer to this, I'd greatly appreciate it
I fixed it! I powered up, held the 'n' and it asked if I wanted to clear the device and it worked perfectly!
I would be back in action, but unfortunately, I have a broken/extra sensitive power button that B&N has to replace... Now I play the waiting game...
Hello,
Earlier today i successfully installed CM10.1 on my new Nook HD+ tablet. After setting up CM10.1 and installing some basic apps i restarted the Nook and it is now stuck in a loop at the Cyanogenmod start up screen. Any suggestions on how to fix this?
Thanks guys!
I had this same issue. I made a titanium backup of everything, and then reinstalled cwm, cm 10.1, and emmc ovation. I used titanium to restore and now it resets just fine.
Sent from my BN NookHD+ using Tapatalk 2
Same here...
I had the same issue. I went in and cleared the cache then reboot and it was fine. My issue now is it'll randomly reboot on its own and sit at the Cyanogen circle boot up but won't boot up. Anyone else?
I booted into recovery and wiped dalvik cache and the othe cache and it booted fin out of recovery but when i would attempt to reboot it normally it would still be stuck in a boot loop...I just factory reset it and it seems to be working fine now *fingers crossed*!
still no go...
I tried that too and it still reboot randomly. Thought that was fixed with latest version
I had the same problem. This is what I did. In the recovery menu I did a wipe / factory reset. Then installed CM and Google apps again. After that I did another wipe / factory reset. After that I rebooted. No more random reboots and no more boot loops. I hope this helps.
trouble restart
Just got a Nook HD+ on the 26. installed CM10.1. every time I turn off or restart the Nook, For the first 3 times, it would stuck at the fast spinning CM logo. I would have to long press the Power button to turn it off, then turn it back on. For the 4th time it would boot without any problem. same thing with boot into recovery, the first 3 times it would ignore my N+down press, only on the 4th attempt. Not sure why, but that's what I found out. I dont see any random reboot yet. Have not try to reinstall CM10.1. Will do that when I have more time. Anyone else with a newly bought Nook care to sound in?
Very similar problems for me, though I don't know if it's exactly every fourth time that it boots properly.
I did a factory reset, re-flashed everything, and it worked perfectly for a couple of days. Then yesterday, a random reboot, and it got stuck at the CM boot animation. It rebooted properly on the second or third try. I just rebooted it manually, and it worked fine again.
I really like this tablet, but I'm seriously thinking of returning it because of this problem. It seems like it could become completely unusable if it gets worse.
CM 10.1 Boot Loop CWM non responsive
I have the same issue. I used powered up and used Volume Down>Menu and it rebooted my Nook HD+ to back to the original Nook OS. Weird because when installed I deleted factory defaults like the instructions said before flashing. Anyway, now when I hold volume down>Menu on boot it come up Black screen with warning telling me it will delete all my documents and reset to factory. Will this wipe the CM 10.1 OS totally? Is there a way for me to get my CM 10.1 back without going through and making a boot image again and reinstalling from starch? CWM dose not seem to be working or am I using the wrong method to booth into CWM on my Nook HD+?
selwynbaptiste said:
I have the same issue. I used powered up and used Volume Down>Menu and it rebooted my Nook HD+ to back to the original Nook OS. Weird because when installed I deleted factory defaults like the instructions said before flashing. Anyway, now when I hold volume down>Menu on boot it come up Black screen with warning telling me it will delete all my documents and reset to factory. Will this wipe the CM 10.1 OS totally? Is there a way for me to get my CM 10.1 back without going through and making a boot image again and reinstalling from starch? CWM dose not seem to be working or am I using the wrong method to booth into CWM on my Nook HD+?
Click to expand...
Click to collapse
What you are seeing is stock recovery (I assume you mean you held n and power on boot, there is no menu button). You must not have successfully flashed the CWM or TWRP recovery to internal memory. That reset to factory it will just wipe your data, not remove the ROM. It will cause you to reinstall your apps though.
If you ever intend on updating your CM10.1 to a newer version in the future, you need to have that bootable recovery SD anyway (or successfully put it on internal memory).
Sent from my Nook HD+ running CM10.1 on emmc.
Reinstalled CWM and CM 10.1
leapinlar said:
What you are seeing is stock recovery (I assume you mean you held n and power on boot, there is no menu button). You must not have successfully flashed the CWM or TWRP recovery to internal memory. That reset to factory it will just wipe your data, not remove the ROM. It will cause you to reinstall your apps though.
If you ever intend on updating your CM10.1 to a newer version in the future, you need to have that bootable recovery SD anyway (or successfully put it on internal memory).
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
In did install both the CWM and CM 10.1 the first time. It booted and rebooted for days without a problem. I believe b what happened was error. I had the alarm set to wake me and half asleep tried to turn it off while the groovy cover was shut by holding down the power button. I may have held down more keys then I thought in a sequence that deleted something that caused the Boot to hang. After that there was no way for me to enter the CWM. The command sequence that would normally send me to CWM sent me to nook factory reset. I noticed that there is a small glitch between hibernate and the b alarm. Holding down the power key to get it to shutdown can cause it enter CWM from time to time.
When I reinstalled everything funny thing is my screen lock settings and background selection (I previously downloaded) stayed along with my user profile. That leads me to believe that everything was in tact on the internal storage. Google play backed up and reinstalled all my apps automatically once I signed in:good:. I'm taking your advice and buying a 4G SD to keep the CMW boot image on with the latest CM. Thanks for your help.
Distorted Boot Animation
Is there a way to fix the distorted boot animation on Nook HD+ CM10.1? I have tried installing a different bootanimation.zip but it didn't make a difference.
I found this post on a similar problem with the nook color running CM10.1, and steven676 fixed the boot animation issue with a new kernel. "I was wandering if it could be used to fix the Nook HD+ as well?"
Josmar1993 said:
Is there a way to fix the distorted boot animation on Nook HD+ CM10.1? I have tried installing a different bootanimation.zip but it didn't make a difference.
I found this post on a similar problem with the nook color running CM10.1, and steven676 fixed the boot animation issue with a new kernel. "I was wandering if it could be used to fix the Nook HD+ as well?"
Click to expand...
Click to collapse
Yes that could fix it, but it messes up other things. Best to just live with the distortion.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks for the reply
leapinlar said:
Yes that could fix it, but it messes up other things. Best to just live with the distortion.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
"I guess in order for one to gain, one must lose something." LOL
In meantime I'll just disable the boot animation with Rom Toolbox.
Hopefully it get's fixed in later updates without any lost.
This thread seems to be in the range of what my issues are. The Nook worked fine for about 4 days and then while installing the Retro Arc apk I sideloaded, it picked up on an unprotected Wifi connection in the area. It then locked up as the notifications were flying in, and the screen went black. I powered off then off after that once and the Cyanogen logo just kept looking. Tried again after and it went to Stock Nook.
The last few days have been spent doing clean installs with care taken to follow the exact steps, but now all I get for 2 days is the Cyanogen Logo looping over and over. Help?
nkca6384 said:
This thread seems to be in the range of what my issues are. The Nook worked fine for about 4 days and then while installing the Retro Arc apk I sideloaded, it picked up on an unprotected Wifi connection in the area. It then locked up as the notifications were flying in, and the screen went black. I powered off then off after that once and the Cyanogen logo just kept looking. Tried again after and it went to Stock Nook.
The last few days have been spent doing clean installs with care taken to follow the exact steps, but now all I get for 2 days is the Cyanogen Logo looping over and over. Help?
Click to expand...
Click to collapse
Just found this on a thread here. I can't find it at this time. I would really like to credit and thank the poster. I had to go into CWM and wipe dalvick cache on every boot. I have only booted once but this change seems to have fixed this issue.
Firsts go into CWM and wipe dalvick cache.( Hold down the power and n buttons until you get into CWM. Go to advanced and wipe dalvick cache. Reboot)
When you get it booted, go into setting/launcher/home screen and uncheck Wallpaper quick render.
Good luck!
josim
Edit to say credit goes to Arron Camp for this fix. Thanks Arron!
josim said:
Just found this on a thread here. I can't find it at this time. I would really like to credit and thank the poster. I had to go into CWM and wipe dalvick cache on every boot. I have only booted once but this change seems to have fixed this issue.
Firsts go into CWM and wipe dalvick cache.( Hold down the power and n buttons until you get into CWM. Go to advanced and wipe dalvick cache. Reboot)
When you get it booted, go into setting/launcher/home screen and uncheck Wallpaper quick render.
Good luck!
josim
Edit to say credit goes to Arron Camp for this fix. Thanks Arron!
Click to expand...
Click to collapse
I have had the same problem in this thread as well (reboots stuck at cyanogenmod logo). I have been wiping the dalvik cache every time (figured it out on my own) and can confirm it works but you do have to do it at every boot (or perhaps after you change wallpaper, not sure).
I got tired of it happening so i google'd the issue and found this thread; mine is stuck right now too (and also out of battery, lol), but once I charge it, wipe dalvik and boot into android I will try the "quick render" trick and see if that fixes the boot problem to begin with.
Edit: I can confirm that disabling quick render has fixed the need to do a dalvik wipe every reboot.
Question
I have a nook Tablet Color + I think, well three of them actually one of them acts like the battery is dead, however when I plut it in using the "Nook" cable it goes green tab turns on, at the first splash screen with the big N for the nook symbol, and than it powers off and loops there? Suggesstions
Tinyneustra said:
I have a nook Tablet Color + I think, well three of them actually one of them acts like the battery is dead, however when I plut it in using the "Nook" cable it goes green tab turns on, at the first splash screen with the big N for the nook symbol, and than it powers off and loops there? Suggesstions
Click to expand...
Click to collapse
I don't know if the color+ has sdcard recovery but if it does that would be the way to go except for...
The other thing is that if you had put on a custom recovery then holding what ever buttons to go to it could allow you to fix it. Or waiting until 8 reboots or whatever if its the same as the nook hd+.
I think there may also be additional stuff that can be tried on the nook logo screen via various button presses as well but don't have any knowledge about that especially for the color+