Related
I've had my NC rooted for 3 weeks. No probs. I decided to update to 1.0.1 to see if wifi was better and so I entered the adb command to force system update and all seemed to be well. After that it went into a boot loop.
I forced another "update" by powering down 8x during bootup. It reinstalled and then same problem. I then tried the directions at nookdevs to fix boot loops. I couldn't ssh into the NC, but to my surprise I could use adb, but I can't do the listed commands because I get "permission denied".
I did an adb logcat and I get nonstop info going by, mostly looking for stuff that shouldn't be there anymore, i.e. apps I loaded when it was rooted. Dalvik cache??
So, long story short, I've tried a system wipe 4x now and I'm stuck in an endless boot loop BUT I do have adb access. What now?
Power, +, N button doesn't work either?
norkoastal said:
Power, +, N button doesn't work either?
Click to expand...
Click to collapse
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
GTOMEX09 said:
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
Click to expand...
Click to collapse
Head over to Nook Devs for the breakdown of the two.. Both methods are requied for using the newest AutoNooter... Glad to hear the device is still in working order.
Stuck in Boot Loop
Noob here with a problem. I’ve had my NC rooted for 5 days and the rooting went well. I had all my favorite android apps up and running. However I was experiencing random reboots (2-3 times per day). So, I decided to unroot and let the 1.0.1 update install and then I was going to use Auto-Nooter 2.12.18 to get everything back.
I did the 8X reboot thing and after reloaded, the NC went into a boot loop. The first thing I tried to do was the n, volume+ and power button. It simply went back to the boot loop.
I immediately put the auto-nooter sdcard in the NC, plugged in the usb to the pc. As opposed to the other times I did this, I got no visual indication that the PC recognized or activated the NC. I waited the full 5 minutes and removed it. The boot animation had changed, but the NC stayed in the boot loop.
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
Before I ejected the NC I opened the command line window and I did adb devices and it came back with nothing. So now my NC is not recognized by the PC (and was before all this).
Can anyone point me in the right direction? Any help with the putty ssh screen issue? Any help will be appreciated.
Geezer Squid said:
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
.
Click to expand...
Click to collapse
Out of desperation I downloaded putty.exe again and it worked this time. Using the script on the nookdev.com website, the NC booted. I then did the data wipe and the 8X reset. I'm now back to stock (mostly) and I'll see if it updates tonight. If not, I'll force it tomorrow and don the new auto-nooter.
I'm learning!!
Glad you fixed yours too. This device is nearly impossible to brick unless you deliberately try to. Definitely easy to undo hard work, but hard to brick.
I have the same problem. Minutes after rooting with autonooter, my Nook restarted and I didn't even set up ADB access. I tried reseting several times with no luck Please help!!
Mine is currently stuck in a boot loop as well. I did not update to the newer firmware it auto-updated and jacked everything up. Pretty upset right now.
I know I can reset the device but I need to get the data from it first. I have the entire storage full of data that I need. It will not boot at all and if this gets erased i'll more than likely end up returning the device and purchasing something that I won't have this problem with every update.
Unfortunately, there aren't many devices that will automatically backup all your important data to external media without you having to take some action on your own to set that up.
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
Well, I'm not an expert, but I have been through this kind of thing. I would think you have two possibilities. One would be to put the nooter sdcard back in and hook it to the computer again. If it isn't very corrupted, it may automatically reload from the nooter sdcard.
If that won't work, then I think it's time to do the 3 finger data wipe and then the 8X reboot thing. You can then redo the nooter sdcard thing.
Good luck.
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
EXACT Same thing happened to me and a friend when using autonooter and 1.0.1. I think there is a problem with autonooter or 1.0.1 messing up the booting process. I wonder whats wrong So I was able to do the 8X reboot thing and get back to stock 1.0.0 and from here I'll try to attempt to use autonooter for 1.0.1. But I'm staying with 1.0.0 until Froyo next month.
thanks! the 8x thing worked good, I did the whole auto noot process again and it works at all except by this market issue
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
jbright44 said:
I'm stuck at the grey N screen and I can't get out. I just got my NC today, updated to 1.0.1, used the latest Autonooter, followed the instructions to a T, everything worked great.
I left the SD Card in (didn't know you were supposed to take it out and reformat it, none of the instructions were specific about that). I was playing with the unit, everything was working great and decided to reboot it because I saw there was a custom animation and I wanted to see it (didn't remember seeing it the first time around). Now the thing won't reboot. It just gets stuck at the grey N screen. I've tried the power + home method and done the factory resets 3 times but when it resets it still hangs on the N-screen and won't boot.
I'm at a loss here. Some one please help.
Click to expand...
Click to collapse
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
wvcachi said:
Did you try taking the SD out and then booting? It'll keep trying to boot from it as long as nooter is on there.
Click to expand...
Click to collapse
Yes I did. It's doing all of this with the SD card out.
jbright44 said:
Yes I did. It's doing all of this with the SD card out.
Click to expand...
Click to collapse
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
wvcachi said:
I'd say interrupt the boot 8x (powering down will do) to initiate system restore, then re-root.
Click to expand...
Click to collapse
Edit. That fixed it. Thanks. Man do I feel stupid. I thought the 8x reset and the 3 button method were the same. Apparently not. I'll try this again a little smarter hopefully this time.
Thank you for this thread. I thought I just bricked my 2 hour old nook. I stupidly restarted it after root with the nooter card still plugged in. Then I couldn't figure out why it was taking so long for the screen to turn on, so I kept pressing the button and then holding it. Then I realized the card was still in. Took the card out and tried to boot it, but it hung at the 'n' screen. The 8 interrupted boot method saved me from my stupidity though. Thanks.
Same here - left the card in...
8x reset and then a home and power reset cleared me up. Then update back to 1.1 and autonooter 3 again.
Loving it ever since.
hey
im having the same problem i did the factory reset to and nothing
wats the 3 count and wat else can i do
So what to do when factory restores and stock installs fail?!
OK... reviving this thread since it's my exact problem but I've been unable to find resolution. I've been searching everywhere for what to do next but nothing seems to be working.
I'm helping my buddy get his nook working. He said he was updating to 1.4 and when he rebooted it, it froze on the n screen. He plugged it back into his Win 7 machine to try the update again and it wouldn't mount as a USB device.
After a bunch of reading and fiddling, he built an SD card with ClockworkMod and installed in on an SD card. Or so he thought... he hadn't made it bootable. Over the phone, I walked him through restoring the image to his card and then it booted.
CWM comes back with a pile of errors. Specifically,
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When trying to format /data and /system, we also get errors.
We've downloaded various factory restore zips and tried installing them but they install (successfully according to CWM) and we reboot only to get stuck at the dreaded n screen again. We've done the 8 boot interrupt restore and get and error to call support (nobody answers this week) and done the regular power/+/n restore and it completes but leaves us again on the n screen.
Can anyone tell me the significance of these errors in CWM? It's the only thing different from all the tutorials and video walkthroughs we've followed and although we've seen these errors in other posts, there's never been a good explanation of them and how to resolve them if necessary.
Also, what is the latest version of CWM for the Nook Color and where do I find it? Is there an official site for CWM? Seems like people are just linking to older versions and sources all over the place with no common "go to the CWM site and get latest build of CWM." The latest I've found is 3.2.0.1 in a post back in August 2011.
Thanks in advance! Hoping this gets us over this hump and helps anyone else in the in the same situation.
moose
Solved it...
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
I'm also getting the E: Can't mount / errors.
Will try this when I get home.
Also i'm just realizing now that i am using an older CWR v3.0.0.5, so that might be my issue also.
links
Mooseroo Could you please post links used to fix this issue
Try using this version of CWR. Just remember you can always choose a recovery image smaller than or the same as your SD card but not larger.
http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
this is not working. same issue with nook 1.4.1 and CM7...hangs at "N" or goes black with CM7
Have you check the MD5 of all your files to make sure you have good downloads? It is frequently a skipped step but one of the easiest and first things you need to check.
Mooseroo - where are you?
mooseroo said:
I've managed to solve the problem I outlined above. I'm not at home right now, so I'll post the specifics once I can get back and post the links and images I used to get this working.
Note that I had no concern for the data/books/apps that were on the device originally. I just wanted it working again with stock 1.4.1.
Basically, I noticed that after restoring to 1.1, the initial screen said "welcome to the future of reading" and then when I updated to 1.2, it said "read forever" so I knew the updates were at least doing something. I now needed to get rid of the errors in CWM 3.2.0.1 so started looking for something to blow away corrupt (?) partitions.
I found a post that had two zip files and it said they repartitioned the nook entirely. I hoped they would blow away my corrupted partitions by rewriting the partition table. I ran one, and it forced me to reboot. Then I ran the second and rebooted. It loaded up, got to the n screen and paused just long enough for me to lose some hope and then flipped over to the nook color boot animation. Yah! Progress!
Tried to register the device using my own bn.com account but wasn't successful. Turns out that you need to either use the original registered account on bn.com or unregistered the nook from his account, but since the error shared the same wording as previous failed factory restores (but this time in the nook registration interface), I assumed it was something locally. I came across a post in the searching that mentioned the need to unregister the nook from the original account to register it on another.
While trying to figure out what to do, I found a 1.4.1 signed stock image that also reconfigured the restore on the device and worked through CWM "install zip from SD" rather than using bn.com update zip via usb (i was still having trouble accessing the nook via usb at this point).
I downloaded the stock cwm 1.4.1 zip and installed it through cwm 3.2.0.1. It booted and then I saw the intro video on the nook registration page had a different woman. I got my buddy to send me the email and password he registered the nook with and the registration process was successful. I now have a working stock 1.4.1 nook color to return to my buddy.
I'll post the actual links to the posts/images that I used once I get home.
Hope this helps others!
Click to expand...
Click to collapse
Just found this thread and I have the same issue - can you post the links you reference? Please?
tmccully said:
Just found this thread and I have the same issue - can you post the links you reference? Please?
Click to expand...
Click to collapse
I think he's talking about my files in this post.
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
Bought a new color nook two days ago and began rooting it after i bought it using the walkthrough here. I made the bootable SD and that went fine. Put the Zip for nooter on there and that went on fine. I got on and created an account with the android marketplace and all. Then I got the Cyanogen mod from their site, the latest stable version and tried to install it. Got stuck at the color splash loading screen. Turned the unit off and have been constantly messing with it and got it to boot to CM7 but i have no google apps and when i press the home button i am still getting 3 options (Zeam, Softkeys, and something else).
I have tried numerous times reloading MN but it will get stuck at the n screen and not do anything. Sadly my idiot self didnt make a backup before i started rooting and the erase to factory in CWM doesnt do much.
Any ideas? It seems like i might be able to just get by with getting the gapps and putting them on but i dont think it will be that easy...
Thanks in advance for the help
UPDATE: Got the gapps to install but everytime i try and go to something in the market it force closes. Sounds like i need a wipe and start over but i am not sure..
make sure you have a class 2/4 sandisk(brand is what counts here).
Otherwise, I'd just reinstall everything over again through your cwm recovery disk.
As easy as it is to flash back to stock I just don't see the merit of running CM7 off a micro SD. Yes, it can be done, but if you're new to rooting your Nook my suggestion is to start over, wipe everything and install to internal memory.
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.
Same with me. Happened 3 times to me last night. I'm still figuring out what i can do to make stock 1.3 + OC + rooted to work.
I'm trying to determine what I did in those 3 times in common. Only thing i can think of i did in all those 3 times was OC +format SD card and installed titanium backup from market.
I'm sure its not a new issue because I remember this happening to me a month ago then I gave up and just went back to miui.
I had the same problem. Look for post about adobe flash causing boot loops. I solved the issue by:
1: after installing 4.6.16, I signed into the marked, downloaded titanium backup
2: used TB to delete the copy of abode flash and adobe air.
3: restarted the nook and had no boot looping.
4: I searched and found a copy of the current adobe flash and sideloaded it using CWM.
It's been 3 day and no boot looping.
Regards
I also had the boot loop issue. It was caused because I updated my flash. Check out this thread....it fixed my issue.
http://forum.xda-developers.com/showthread.php?t=1208896&highlight=boot+loop
Thanks, Johnny. You've saved me a lot of trouble.
No problem! Happy to help! Thankfully GMPOWER threw together that zip file for everyone!!
Be careful when you install any 3rd party keyboards to /system, it also resulted in boot loops for me with a few of them
joej said:
Be careful when you install any 3rd party keyboards to /system, it also resulted in boot loops for me with a few of them
Click to expand...
Click to collapse
Was thumb kb one of them?
dohturdima said:
Was thumb kb one of them?
Click to expand...
Click to collapse
I have had no issues with Thumb keyboard (either after initial install or updates).