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 was running Phiremod on an sd card a couple of nights ago and something went terribly wrong with my NC. I tried to get into the program and it would boot all the way to the home screen and then just power off. I couldn't get it to boot into CM7 running on an sd card either. I searched these forums and others and although I returned the device to stock, repartitioned the boot, removed clockworkmod, reflashed the roms, reformatted the sd card (16gb), switched to an 8gb card and I don't know what all else (not necessarily in this order), I cannot run any roms other than Autonooter 3.0. It installs from an 8gb card with no problem and runs fine. But when I try to use my CM& nightly 37 from my other NC, no go; I reflashed Tablet Tweaks, HC V4, Nookie Froyo and tried them all, no go.
I could get Phiremod to load all the way to the home screen and then start powering off. CM7 comes up to a blank screen with the status bar and buttons at the bottom but also a status bar at the top that says Android system and then it powers off. I rooted the NC with Autonooter 3.0 and then tried to install Tablet Tweaks and got the same weird Android System status bar at the top and then it powered off.
Any ideas? I have been working on this for 48 hours and I got nothin'. I can't get ADB to work with just the NC running stock (I am no expert and might be doing something wrong).
First run autonooter and root it, then u can use rom manager to flash clockwork recovery to emmc. After that use either of the two to flash another rom to emmc.
Also were trying everything from sd card or were u flashing to emmc?
And i am not sure but ADB should work with rooted stock.
Thanks for the response. I will try flashing cwm to emmc tomorrow. I was trying everything on SD cards and emmc. I installed Tablet Tweaks to emmc with the weird result mentioned in the op. TT wouldn't run from an sd card or emmc: the NC just kept powering off as soon as it got to the home screen but before it finished loading up. I should be able to use adb now that I'm rooted. Silly me, couldn't get the device to be recognized running stock. I'll update on how things go and probably will still need help.
Ok, I just installed Clockwork and then using it I flashed Nookie Comb. The installation went fine, boot up went all the way through to the home screen and then the same thing as usual happened: the weird notification bar at the top that says Android System, the status bar with softkeys at the bottom, and immediate powering off.
I think I saw this weird notification bar once when I was rebooting the Nook before I used autonooter, so I think that something is wrong on the emmc level. I have returned to stock and looked at the information in Factory and it shows that I have been returned to 1.0.0. But after I go through with the registering process, I find that the device is on stock 1.1.0 without having to sideload the update. I don't see any notification that I have been updated to 1.0.1, which used to be the case before all this happened. I was trying to avoid messing with the stock rom (warranty) but it looks like I won't be able to do that unless I can figure out what happened here. If all else fails, I will just stick with autonooter, which works well for the purposes for which I use this NC. I do have a second NC that works just fine and can run roms off an sd card. Maybe I can take something off of it and put it on the other?
Any assistance is appreciated.
04/10/11 - 6:00 pm****As I said above, I searched high and low and I tried everything!, but still nothing has got me back to being able to run roms off sd cards yet. But I feel that I have made some progress. I was very disturbed about going from 1.0.0 to 1.1.0 without applying the sideload update so I decided to start all over again and restore the NC to stock. I found yet another thread and followed the instructions, except that I unknowingly used CWR 3.0.0.6 instead of CWR 3.0.0.5. So, instead of immediately rebooting into the stock hardware, I had to do a hardware reboot. This brought me back to 1.0.1 and I was able to install the sideload update. So stock rom seems to be back to normal. I took the CM7 rom I am running in my second NC and put the sd card in the trouble NC. It did boot up and completely loaded up the homescreen. This time no top notification bar, no Android System message, but yes, the little sd card icon showed up at the bottom although no message about a damaged card or sd card now removable showed up. But the screen was completely frozen and the device immediately turned off. There was no powering off notice or anything; it just went off and the screen went black. This is a 16 gb card. I am going to try with an 8 gb card now.
04/11/11 12:40 am**** Ok, I give up. I have succeeded in getting nowhere fast. I am thankful that I can run Autonooter 3.0 on it and use sd cards to load my files for using on the NC. I miss the froyo/honeycomb/cm7 experience on this NC but at least I get it on my second one. One good thing that came out of this: i can do the eight boot interrupt thing without a hitch!
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
My girlfriend recently purchased a nook color, and being the techie I am the first thing I wanted to do was put a custom rom on it and get it to be like a tablet. I ended up installing Honeycomb V4. She didn't like it because of the slowness, and It kept force closing her nook app. I tried the second edition of Honeycomb that I could find, still the same force closing issue. I then installed phiremod V4. She loved it, fast, didn't have any issues with force closing until this morning when EVERYTHING started force closing after a blackscreen/reboot randomly happened in GMAIL.
I then just said okay and tried to restore it back to factory. I have done the following to try to restore it to factory;
8-boot interrupts
CWM restore to both 1.0.0 and 1.0.1
Many different versions of CWM
These are the errors I get when I try these.
I can format /system just fine, but when I try to format /data I get an error stating "Error formatting /data!"
I did the option on the home screen in CWM "Format data factory restore" and that seems to wipe the /data just fine, but I'm not sure.
Whenever I then try to flash the 1.0.0 or 1.0.1 it freezes on the white Nook Color screen and does a little loop over and over. I can still flash either phiremod V4 or Honeycomb back, and both of them work just fine. I have tried EVERY single way to restore that I have found. I just want a rom that is clean and doesn't have any issues, she just wants to read her books.
Any help would be greatly appreciated. Thank you!
I've followed the instructions from this thread several times and it worked:
http://forum.xda-developers.com/showthread.php?t=931720
BUT, My Nook is a few months old and has the older partitions. Yours may have the new partitions and I'm not sure if the instructions above work with newer nooks. Why don't you just install CM7? I think your GF would be happier with that. Instructions in this thread for both versions of the NOOK
http://forum.xda-developers.com/showthread.php?t=1030227
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).