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
Related
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Do a factory reset, install the update, then use the new autonooter.
how to do a factory reset? thanks, I am a newbie to this area!
Not sure how much I can help-
Just how "bricked" is it?
A truly bricked device will do nothing. It will not start or do anything whatsoever.
A machine that is thoroughly HOSED may get stuck in a boot loop, or try to start and fail every time you press the power button.
When I forced the update manually it took a few minutes to take and reboot; how long ago did it do the update?
Have you tried connecting with adb yet?
Have you tried booting it with a nooter or auto-nooter sd card yet?
http://nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC
Instructions for manually updating.
Here is my situation:
Around 9:30, my NC started updated itself, it reboot in about 15 minutes, and takes a very long time get to the "nook color" screen, then took another 10 minutes letting me select "home or zeam", after that, it has no response.
I tried to reboot, it got up to the "Nook Color" welcome screen, no further response!
I tried to factory reset, not working through adb, it did appear on the adb devices command!
Do a factory reset and start over.
I ran into a similar problem, but here is what happened to me:
1. I reset the device to factory settings.
2. I rebooted the nook 8 times, stopping the boot process. This took my NC back to factory version and no rooting at all.
3. Installed NC update 1.01 per B&N instructions.
4. Used AutoNooter (latest version for 1.01). AutoNooter rebooted the device as it is supposed to.
5. After AutoNooter reboot, I installed Astro File Manager and then after that the NC stopped responding to screen touch.
6. I held the power button to shut the device down. Strangely, the screen shut off and it appeared to be shut down, but I think it did not truly shut down.
7. I could not turn the NC back on. I tried to reset to factory settings 2-3 times and no response.
8. I plugged in my NC as if to charge, and it went through the boot process.
and it has worked just fine since then. To be honest it kind of scared me, because I love this thing to death, but I remained calm and kept at it and it was not bricked. I guess what I'm trying to say is that before you post here that the new update bricks the NC, you should be absolutely sure it is bricked and not just frozen like mine was.
gtechnical said:
Just mandatorily installed the update over the air, and after that my rooted NC becomes brick, can not get to the home screen anymore, any solution? what did BN do on this update?
Click to expand...
Click to collapse
Brick, like you can't do anything at all anymore, might as well lay it on papers, use it as a door stop and pour cement to build a house?
That's what bricked means... If you still can access it via ADB, run recovery, etc.. it is far from "BRICKED"...
-CC
I did a manual shutdown because I couldn't kill some goofy NES rom app. Now it won't reboot. Do I have to replace the SD card with the imaged one every time I want to restart this thing?
No... Sounds like you medded something up when you manually rebooted, though. Oh well, just restore to factory and reroot and you should be fine Id bet...
Sent from my NookColor using XDA app
Crapcrapcrap. I think I broke it.
I tried to do the factory reset as you suggested but it wouldn't do ANYTHING. I did some more searching and finally got it to work by holding power button plus volume up plus home button and then holding power button. But it went to the future of reading screen and then the Nook screen and wouldn't do anything. More searching told me to reset it 8 times and on the 9th it would completely restore factory, so I tried that.
It seemed to have worked but then went into ANDROID boot/initialize sequence and was repeating that over and over and over. Seems weird that it would boot Android after a complete reset, but I digress....
I thought maybe it was because the imaged card was not in, so I inserted that into the slot. Same thing....repeat over and over Android boot up sequence.
I powered it down manually and it seemed dead again - not booting back up by traditional means. I tried holding different buttons, whatever...FINALLY got it to the future of reading screen again. Proceeded to boot up - Android sequence....you guessed it, on repeat. No card in now. Crap!
Please help! Newbie here not sure what to do!
your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.
jerry_smith_80 said:
your case is similar to what I experienced yesterday. I took out my memory card, and did factory reset and 8-time reset trick. On the 9th it installed a fresh rom (1.0.0), and booted successfully afterwards.
Click to expand...
Click to collapse
Thanks for the response jerry. Something is definitely jacked here.
I did the 8-time reset again....Got the message it was installing a software update, the future of reading screen, etc.....and then it went into the freaking Android boot sequence on repeat again. Why is it booting up Android instead of 1.0.0?
No memory card here, either. I am totally flustered.
I would really appreciate any help that anyone out there can provide. Did I brick this thing?
Update. I powered it down from the Android reboot cycle and then followed the instructions here to perform another factor reset. Somehow this time it worked. It rebooted with 1.0.0 and made me go through the setup steps again.
I think I'm going to upgrade to 1.0.1 this time before rooting....I was having some bugs and somehow it culminated in the above debacle. Hopefully it is smooth sailing from here.
Something is still messed up here and I'm not sure what's going on.
As mentioned above, I finally got the thing to reset, clear, and boot back up with 1.0.0....or at least so I thought.
I had only ordered one book and it was present on the reboot - not sure if that is significant or not. At any rate, my initial plan was to update to 1.0.1 like I mentioned since I seemed to have issues/bugginess before w/ 1.0.0. I downloaded the .zip file to my desktop, copied it over exactly as instructed and the thing never rebooted with the update. I waited and waited. I put it to sleep and waited. I woke it up. I tried to navigate to it. Nothing.
Ok, perhaps another fluke. From what I've read the update is unimportant anyway. So I tried to root again with auto-nooter on 1.0.0. Followed steps again to a T. Even re-downloaded all of the files to my computer just to eliminate issues. Put my card in, plugged it into my laptop....never found any drivers. CN stayed off. Tried to boot it up manually - nothing. Tried to reset it manually w/ Power + home + volume up. Nothing.
Finally I removed the SD card and booted it up and it worked. During initialization I quickly put my card into the slot and it booted Android successfully....much like the first time I rooted it.
It is working...but not like it is supposed to. I'm wary to go down this path again considering the trouble I eventually encountered last time. Should I start over? What the hell did I do wrong?
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.
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.
I purchased a nook color the other day and successfully rooted and used it for a few days. My youtube would not open so I reinstalled, it ran once and then failed to open again so I gave up on that issue. In reading about youtube app I found that you could get the new market app. I could not get it to install...and in trying multiple things I accidentally deleted my original market app.
I could not get it back so I whiped my nook color and reflashed autonooter. I got all my apps back but I get a connection error when trying to access the market now. I added my account via youtube which again opened once to allow me to sign in and now fails to open.
So I decided to try to reset it back to the way it was out of the box and start from scratch.
I tried the adb 8x reboot method.....it just reboots the nook as it normally would. No bootloader or install screen.
I tried the button method. It works once or twice then it goes through the entire boot. I did it for a half hour and used counts to verify I was doing the process correctly and no matter what I did I could get it to fail boot once and one the second or third it would always bypass and go through with boot even with my finger on the button.
I also am running windows 7 64bit and I cannot get my computer to see "nook" in the device manager for more than a second and it auto installs as a storage device. I've tried to "uninstall" the different devices and last night I was able to catch the "nook" in time to install usb drivers manually but when I reset the nook today my PC no longer see's it again. I was wondering if there is an easier way to install the adb device.
Thanks
UPDATE: Somehow the ADB way to reflash worked the second time I tried it. I also changed some settings in the development menu to fix the device manager issue. I'll update again if I can use youtube and the market.
I don't know what to tell you about everything else but for ADB I would highly recommend adbWireless... it works great on my NC and I never had to install any drivers.
To reset I used the button and counted slow to 15 after the screen gose off each time it worked for me. Good luck