Nook wont boot normally after being off all night.. - Nook Color General

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.

Related

Random Kinda/Sorta Brick?? Ideas??

Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
since you have tried a lot of things already, you may need to flash the rc29 image in bootloader and re-root your phone, if it still will not work after the rc29 flash, then it is hardware related altogether.
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
themoebius said:
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
Click to expand...
Click to collapse
to unroot you flash the DREAIMG.nbh file because it will overwrite everything.
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
Try adb, USB debugging is usually on with these modded ROMs. See if you can get a logcat to someone who is much more knowledgeable.
Hold on...not to call you out, but im pretty sure cm 4.1.999 HAS NOT been out for 2 weeks...please clarify...did you flash the newest update THEN had problems?
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
I am having the EXACT same problem with CM4.2.4. I certainly hope its not hardware, but it sure "feels" like it. Especially when my G1 is even shutting down from the Recovery Menu. I'll try to unroot and see if that resuscitates it.
Another one....
Have a look at my current issue on this thread: http://forum.xda-developers.com/showthread.php?t=582576. Check to see in bootloader mode what your board type is (it states it at the top for those who don't know).
Mine is currently showing an EVT board, which doesn't exist. I've pulled the battery out and am leaving it for a while. It could be a hardware issue, but I'm not sure. I was having the "fading screen" issue and eventually got back to RC7 (when I could get into recovery).
Which recovery are you using?

HELP! Constant Re-Boot!

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.

Nook color won't turn on, won't boot sd card

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.

[Q] Battery drain causes Nook to hang on boot

Hi, I rooted my nook some time ago, and ever since then I noticed that when my battery goes completely dead, and I recharge it, my Nook will hang up on boot. It doesn't matter how long I leave it on the charger, but when I boot up, it just hangs on "Touch the future of reading." My solution so far is restore a nandroid with clockwork recovery, and that always works, but of course, it's not ideal. Does anyone have any suggestions?
Also #2 question: Will updating to 1.1.0 software on the B&N site mess up my nook if it's already rooted? I was hoping to update it without having to reinstall everything.
Thx.
issue solved...
The problem with my nook booting after power discharge is solved by booting into clockwork recovery, going to "advanced" and selecting the first option... I think it's called "fix boot" or something.
So the system restore was unnecessary, being as that solves the issue.
Just had this happen to me this morning, the option is "Reboot Recovery". Thanks!
Had to remove SD card
I was having the same problem, but I couldn't even boot into recovery. Once I tried this a couple times, I removed the SD card and tried again, and it booted normally.

Really confusing boot loop (Rooted stock)

Edit: Aaand somehow this ended up in the accessories forum. Can I get this moved to general? I don't even browse accessories. Sigh.
I recently returned to stock 1.2 with the default recovery flashed (CWM SD card), and then I upgraded to 1.3, and then rooted with the ManualNooter 4.5.18 and 4.6.16 (or whatever their numbers are, I followed the instructions to the T).
It worked fine and I installed everything i needed from the market/titanium backup/etc but the second time I reboot the device it is stuck in a boot loop. The splash screen slowly writes out the word "Nook Color" and it will complete this once, but the second time it does this, it reaches the L in Color it stops and starts over. It will do this for hours.
I wiped it and started fresh over, reinstalling 1.2, re-updating to 1.3, re-nootering (sounds dirty...) all over again, re-installing all my apps all over again (took forever) and yet it still does this. As soon as I rebooted it, this began again
I'm a longtime lurker with a rooted and much-abused DInc, I've had PhireMod, CM7 (without the sleep of death) and Honeycomb on my Nook all without issues (that I couldn't fix). But this has me completely flummox'd. What makes this harder to deal with is that my Nook will not recognize my home Wi-Fi so I have to do all my work on it during my lunchbreak (another issue entirely; unrelated, home wifi is a software solution)
Any Ideas? I haven't yet had the chance to flash the better kernel, because when I reboot it's stuck in this loop. I tried re-nootering and that did not help.

Categories

Resources