I rooted my 1.0.1, then followed it with a pre-rooted "update" image for 1.1.0 from this thread http://forum.xda-developers.com/showthread.php?t=932145
It worked perfectly initially, but on my second boot up it was stuck at the black screen with "touch the future of reading". I kept rebooting but I couldnt get past the initial screen. Even after 8 fail boots, it didnt go into reflashing/system partition. The only way to boot as of now is to use the usb cable and plugging it to a comp a ac adapter. Everything works fine when Im able to boot it, but once I try to reboot without the cable, it gets stuck again .
I scanned through the thread I linked above but couldnt find a similar situation.
Anyone know any solutions?
I could be wrong, but if you had 1.0.1 and installed the 1.1.0 root it may be why this is happening. Have you tried resetting to nook default, update to 1.1.0 and then install the rom you mentioned?
migrax
Related
My NC wont boot no matter what I do. When I connect it to my pc (windows xp) I get an RNDIS ethernet gadget in the new hardware notifications. The nook was rooted but I did a hard reboot before finishing the setup because it wouldn't connect to my google account. The NC wont even show the "touch the future of reading screen" and I cant get adb to find the device. I rooted when I had freshly wiped everything and downgraded to 1.0.0 then I upgraded to 1.0.1 then I rooted. It worked fine until after the hard reset.
HELP!!!!
FIX!
I'm sorry for the double post, but I want to make this clearly visible when someone else has this problem.
So, all you have to do to get it to boot is try to put the device into recovery mode. It won't actually go into recovery mode though, it will just boot into the regular os.
Clockwork Mod Recovery
I can't go into recovery. I have Clockworkmod installed.
bumpity bump,
Im back to this issue seems my fix up there wasn't right. I did a FULL wipe on the nook (/system, /data) and then proceeded to update and root. after rooting I rebooted the nook with the autonooter sd card still inserted and then the device wouldnt boot. I tried removing the sd card and still no luck. adb doesn't find it but it is detected as a "RNDIS/Ethernet Gadget" under windows. Is there a way for me to boot the nook?\
EDIT:
got it to boot by mashing the power button and putting nookie froyo inside :/ im not sure why but thats probably how I got it last time too.
Clockwork...did the same thing
pndo1 said:
I can't go into recovery. I have Clockworkmod installed.
Click to expand...
Click to collapse
Folks,
I've done the same thing. I backed up with Clockwork to the SD. The Nook would only boot into Clockwork. So, I recovered and now the device will not power up at all. I fear that I have bricked a wonderful device that I spent alot of time on. It will not boot at all, will not respond to the power button at all and I don't know what to do. Does anyone have any suggestions or am I screwed?
FG.
I have the same problem with Motitas and it was updated to 1.1 recently. Please help.
the screen stops to nook icon only. does it mean i have a brick now ? PLEASE Help.
Please read my threa a few threads down from this one, titled "dummies guide to my nook wont boot." it explains everything.
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.
Sorry if this is available here, but I am not having much luck with the instructions that I tried.
I have an auto-nootered 3.0 NC & want to return to stock in order to apply the 1.2.0 update. ( I run CM7 from SD when I want to really have fun) I tried the 8 fail boots & ended up in a boot loop to CWM recovery. What is my easiest (non-ADB) method to get this thing back to 1.1 stock? Again, I apologize if this is right in front of me, but most of the relative threads that I found are very old.
Thanks,
kev
I followed this thread to first remove CWR
http://forum.xda-developers.com/showthread.php?t=914690
followed by instructions here to restore to stock
http://nookdevs.com/Flash_back_to_clean_stock_ROM
and lastly to side load the 1.2 update.
Cheers
I had to restore to 1.1.0 after autonooter 3.0 by erase and dereg., then 8 starts; 1.2.0 then installed fine.
Jim
For those of us that do NOT have CWM (ClockWorkMod) recovery installed on eMMC, but do have CM7 installed to eMMC, can we use the 8 boot trick to reset our nooks to stock?
I'm running CM7 on my eMMC that I installed using the "CWM on SD" technique. My Nook stopped booting last night after midnight. Since I did not change anything with the OS and had rebooted a couple times earlier in the day, I'm ASSUMING that the 1.2 update came down automagically via wifi late last night, and was unable to complete install when rebooting. I did not see any prompts or input from the Nook during use or on reboot that would have indicated that and update had been received and/or applied.
Also, I was under the impression that the 8 boot reset pulls the software off a chip that has the OS "cooked" into. Is that correct? If not, wouldn't an eMMC install of CM7 remove any chance of the 8 boot reset being successful?
EDIT: just read the linked instructions above. I'll give that a shot tonight.
Anyone have any ideas here - I successfully removed CWM from my NC, then did the eight boot interrupts, and the stock software reload thing seemed to go okay. When I try to reset data by holding down power+n, nothing happens. It turns on, but then right back off. If I try to boot without holding n, it stalls on the "n" screen.
Any thoughts?
Flashed again with cwm up to 1.0.1 and I can't update to 1.2 or 1.1 via internal memory or sd. I changed file names and verified checksums and they are accurate and still no dice. WTF
edit:-----------
Weird. After an erase and deregister 1.1 and 1.2 finally went through. Something must have not been in the right state without that.
So if you're getting stuck do both methods in Part 2 of http://nookdevs.com/Flash_back_to_clean_stock_ROM
Same issue as others
Yeah... same issue here. Was running 1.0.1 rooted (no SD method). I did not have CWM Recovery installed in eMMC but did make an 8GB SD CWM Recovery.
So after the failed push update from B&N ... I now have the boot loop issue. My guess is their update failed because of some root thing I had in place. Not installing CWM Recovery to eMMC was my biggest issue because at least that would have blocked the automatic update from B&N.
At any rate... I've tried multiple time to recover and now find myself going back to unrooted stock just so I can get the B&N working again.
My wife is gonna kill me if I can't get this thing working again soon. The new magazine issue of "US" is about to come out. =)
Everybody calm down and just follow the Instructions here:
http://forum.xda-developers.com/showthread.php?t=931720
[HOW-TO] : Restore Nook Color back to stock EASILY!
That should fix your Nook no matter what you did to it.
____________________________________________________
Sent from NookColor CM7 using Tapatalk
=japzone;That should fix your Nook no matter what you did to it.
Click to expand...
Click to collapse
Yes, that works, but that restores the Nook back to 1.0.1. How does one then get it back to 1.1.0?
I followed the same procedure using the 1.1.0 firmware, but it refuses to work.
Anybody know how I can get back to 1.1.0?
Thanks.
assuming you have cwr, have you tried this?
http://forum.xda-developers.com/showthread.php?t=1050520
I'm about to try it now since I fail at ADB and rebooting apparently...
cameraz said:
Yes, that works, but that restores the Nook back to 1.0.1. How does one then get it back to 1.1.0?
I followed the same procedure using the 1.1.0 firmware, but it refuses to work.
Anybody know how I can get back to 1.1.0?
Thanks.
Click to expand...
Click to collapse
I tried this method and it worked perfectly!
http://forum.xda-developers.com/showthread.php?t=945838
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.
Ok guys heres the deal, i have been trying to reflash NC stock and to no avail i get the same issue everytime no matter what version i use, i have even tried ADB, and that does not work.
Ok my problem is this everytime i try to boot it it just loops at the barnes and noble nook color screen forever. When i tried ADB my computer would not even find the device but it found 2 which when i tried to uninstall them they install right after so i cannot use ADB(and yes i turned off automatic driver install). So here is where i land and my question. Do i have a 300 dollar paper weight or is their hope, and if so please explain what i am doing wrong. Thank you for your time
First off...
are you trying to flash the stock B&N?
how are you trying to flash it?
do you have CWM or TWRP on eMMC or stock recovery?
if you're trying to use cwm or twrp to flash stock rom... see the customizing rom thread in my signature for modifications required.
ok i am trying to flash to the stock bn, i am using cwm, but when i do that it just loops through, and adb now does not even recognize the device so i can tie them together so to speak.
Ok, i did everything that forum on your sig told me to do got it installed but it still loops at the "barnes and noble Nook Color" flash screen. Any Ideas?
Now that you have stock on the nook color... do the 8 failed boots to cause it to erase data and deregister the device... it should bring it back to factory and resolve the boot loop issue
Finally! thank you so much for your help been working on this issue for 3 or 4 months now, it works just need to get it charged and hopefully it will take a charge.