Database Develop

Nook Color won't boot

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.

Nook bricked, please help

Ok so here's what happened.
I rooted my nook with autonooter 3.0.0, then I installed rom manager to install cwm. I installed the latest version of cwm and I tried to make a backup, it ended up in my nook only booting in cwm. So I found a cwm removal script and removed cwm. I booted my nook and opened rom manager and I decided to try an older version of cwm. I pressed make a backup in rom manager and it just went into a boot loop. I can't really turn off my nook, and I can't really turn it on. It just keeps going to "touch the future of reading", then turns off, then a couple of minutes later, goes back to "touch the future of reading". To make it clear, I do not have a backup.
So can anyone please assist me in fixing my nook? I'm in a dead end here.

Sounds like a boot loop try
Method one: Eight interrupted Boots
1. Power off the nook.
2. Tap the power button.
3. As soon as Welcome to the future of reading appears, hold the power button down to interrupt the boot process.
* If the boot animation does not appear, add 1 to your interrupted boot count.
* If the boot animation DOES appear, your interrupted boot count is reset to zero. Start over.
4. Repeat from step 2 until your failed boot count reaches 8. At this point, the nook will re-flash its /system partition. You will see the process on the right.
From Nook Devs

i went through this yesterday... i was told you can't brick a nook color so I restored it back to the original firmware...go to this website www.theunlockr.com then click the how to's then go to Android and look for Nook Color then look for how to restore to stock firmware and follow the instructions. they worked for me and I'm sure they will work for you also...Good Luck

Stupner said:
Method one: Eight interrupted Boots
1. Power off the nook.
2. Tap the power button.
3. As soon as Welcome to the future of reading appears, hold the power button down to interrupt the boot process.
* If the boot animation does not appear, add 1 to your interrupted boot count.
* If the boot animation DOES appear, your interrupted boot count is reset to zero. Start over.
4. Repeat from step 2 until your failed boot count reaches 8. At this point, the nook will re-flash its /system partition. You will see the process on the right.
From Nook Devs
Click to expand...
Click to collapse
Thing is, I can't power off or power on the nook.
I'm going to try and restore it to stock.

bennook said:
Ok so here's what happened.
I rooted my nook with autonooter 3.0.0, then I installed rom manager to install cwm. I installed the latest version of cwm and I tried to make a backup, it ended up in my nook only booting in cwm. So I found a cwm removal script and removed cwm. I booted my nook and opened rom manager and I decided to try an older version of cwm. I pressed make a backup in rom manager and it just went into a boot loop. I can't really turn off my nook, and I can't really turn it on. It just keeps going to "touch the future of reading", then turns off, then a couple of minutes later, goes back to "touch the future of reading". To make it clear, I do not have a backup.
So can anyone please assist me in fixing my nook? I'm in a dead end here.
Click to expand...
Click to collapse
You need to boot a stock image. Try this link http://www.androidtablets.net/forum...ll-clockwork-recovery-revert-stock-image.html

I'm So hoping someone will help me, I tried to root my device but it didn't work I couldnt get off the software so I installed 2gb clockwork 0.7 and nook complete restore 1.0.1 I followed all tutorials carefully, but when it comes to restore data it says no files found. Lost, I went ahead with the restore. It appeared to work except now I get a message flashing up that I cant read the screen just flashes and I think the partitions are lost too. I'm on the verge of tears. (im a girl dont judge) lol. And I'm lost with my expensive doorstop. PLEASE can anyone help me fix this as i'm at a loss (

No need to worry. The nice thing about the NC is that it will always boot from the SD card first. Sounds like you tried this...I suggest deleting everything you have (clockwork mod files, stock restore files etc) re-download everything and start fresh.
on your computer, format your uSD card, use Win32DiskImager to flash the clockwork mod boot image onto the uSD card and copy over the stock restore files. Place the uSD card into the NC and reboot. you should boot into clockwork mod and from there you can install the stock zip file from the uSD card.
GL!

Thanks,
I managed to get it working by resetting 8 times and booting a factory reset, but now it wont install any updayes and i'm stuck on the poo 1.01 software. I tried putting the official update on clockwork and booting from there but it says file bad with any version I use (screams in frustration)

This will fix your partitions
It was awhile ago, so I don't remember the exact steps, but the following file will fix everything...
nookie-froyo-0.6.8.custom.3.zip
When you unzip it you will get the following:
nookie-froyo-0.6.8.custom.3.img
You will need a program like 'WinImage' to write this image file to your SD Chip. Once done, boot your Nook with this chip and install Froyo. You probably don't want Froyo, but thats OK. This is just the first step... but it is key.... This install will 100% recreate and fix all your partitions.
Now you have two choices,
1. Find a stock nook image, and install it to your nook. I think it is 1.01
or
2. Find 'boot.img' and 'system.img' for the nook color. Write those to a bootable SD chip and install.
I am not sure if it was #1 or #2 that worked for me. Try #1 first. If it works, you will be able to start up your nook and register it with B and N. Then you can download their 1.2 update and install it as they instruct.
Good luck.

Follow this thread and you can get it back to original stock 1.0 or 1.01 and then do the updates as normal by waiting for OTA or sideloading them.
http://forum.xda-developers.com/showthread.php?t=931720

Thank you guys I've followed your steps and also looked around this site and im back on the latest stock software. I appreciate your help

Restore to stock before 1.2.0 update

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

Bricked Nook HD+

Hi guys, I have bricked my nook hd+ and I hope to get some advice, thank you.
I had the problem where i was only able to boot to cwm recovery, I managed to solve it by using a stock backup, combined with flashing a 2.1 stock rooted rom as i had problems recovering the data partition.
After I did all that(I should have really stopped when I got it working) I tried to install cwm recovery by using the bootable sd card as i lost my custom recovery for some reason. However, I was not able to after rebooting 20+ times. I previously bought two nooks, my other nook had no problems but this particular device had to be rebooted 20-30 times before it worked the other time. Being the genius I am, I then tried to flash recovery using various apps since I still had root..one of the programs flashed and restarted my nook hd+ and I can only boot to the "nook" screen now. Holding power and the n button only restarts the tablet.
I guess my only way out is if i could somehow get adb to work? I know its a long shot but I have been trying for the past 1 hour and have not been able to do anything. My computer manages to recognize the tablet as "Blaze_Tablet" and i am unable to change the drivers. Anyway i was hoping if someone could give me an idea of what i could do or if i should give up on the device as it is unrecoverable. I would appreciate any response at all, thank you good people of xda!

I somehow managed to get fastboot working and flashed custom recovery and managed to restore from backup of stock :victory:

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.

*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.

Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app

Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX

http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app

SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.

Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.

When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.

SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.