Database Develop

Nook Color Only boots into clockwork recovery

Is there a way to get rid of the clockwork mod boot on the nook color
As per onstuctions on this site, I got a 1.1 pre roote version and installed it
from the sd card with the clockwork menu which informed me that the
"NookColor" install complete.
when I reboot, it starts with the welcome message,but then only reboots into the same recovery menu.
At this point I would just like to go back to a stock rom, but cannot boot anything but the recovery.
By the way, I can boot froyo from the sd card
Please help me

I've moved your thread to the correct forum.

So you dont have the CWR sdcard in? Because if you did, you would need to remove that first. Sorry if this dumb, but thats all I can think of right now. Maybe reflash the 1.1 pre rooted rom? Or follow the instructions in Samuelhalff's "Easily restore to stock" thread located here in the Nook forums.

The "Easily restore to stock" saved the day. I am now up and running.
Thanks

How did you do that? I have CWR on mine and I went to buy a book from the shop on the Nook and it downloaded and installed 1.1... Now when I try to go back and restore from backup CWR doesn't respond... All it does is sit there and if I select something from the menu it goes to the background image (the circle with the top hat) and sits there. I would like to remove this so I can reroot my Nook...
Thanks for any help.
Bob

See the other thread or sticky that's labeled "How to Restore to Stock easiliy." I believe you can also use the power down and on 8 times trick to restore to stock as well.

Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.

porear said:
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
Click to expand...
Click to collapse
Ditto that. I reinstalled CW and everything seems to be working fine. Has anyone else had issues with using Rom Manager on the NC? I've had to go back to stock twice whenever I've used it.

I had a problem when trying to roll my 1.1 rooted NC back to stock because I futzed it up that I ended up in a CWR loop. 8 resets didn't get me a reflash, it got a recovery. Took me finally getting the NC flashed and rerooted at 1.1 a second time when I reinstalled ROM Manager and ended up with the problem again. Took me this wasted effort to realize that CWR runs in lieu of the reflash if CWR is installed and that's an obvious problem when I wanted a reflash and not restore a different backup.
There is a thread with a zip that CWR can run that blasts CWR off and reflashs stock and getting that done put me back both times I messed up above.
Seems to me that perhaps the whole "can never brick" response when people ask for help needs to have an addendum about how CWR gets in the way of an 8 reboot reflash and provide guidance on how to get that update file and use it instead to get back to square one. (Plus some advice on when to clear caches and data partitions to avoid weirdness later).
Now rerooted on 1.1 with no ROM Manager running but I'm missing the nandroid bacjup capability, so maybe I reinstall but stay away from the recovery option until I need it?

I reinstalled CW after I rerooted 1.1 and have had no problems with it so far, but I also haven't tried to backup or anything since the first time (which initially got me into this mess).
I do think you're right about having some sort of addendum thrown in. I was running circles around the XDA forums for a few hours trying to find some sort of fix the first time my Nook started acting weird. The 8-reboot trick just wouldn't work, and my battery was more or less drained because CW was interfering. Maybe this is just understood by most, but it certainly would have saved me some time (and some gray hairs) if someone had mentioned it earlier.

So what is the conclusion of this thread? I have a new NC, updated to 1.1 and installed AutoNooker 3.0, immediately installed Clockwork and did a NAND backup... bad thing is that it won't boot off the eMMC anymore, only CW.
I can boot roms off of the SD card (ie Honeycomb) but this isn't want I want. I've downloaded and flashed several roms but its looped at CW. So the rom isn't the problem.
If we can't install Clockwork Recovery, then how can we flash new roms to the eMMC?
[UPDATE]
Found a flashable file which removes Clockwork Recovery.
http://www.etoile-laconnex.com/CWR-removal-rootsafe.zip
After I flashed that I am now booting off the eMMC froyo rom. Nice! Saved me from Restoring it, updating it, and reRooting it.
[UPDATE 2]
Well while it worked initially, it loaded the homescreen and reset. Now it is stuck at the "Touch the Future of Reading" screen with no Recovery... which worse off. Now I have to make a CWM bootable SD, flash the restore, and start over. Nice.
[UPDATE 3]
Finally got it back to stock after hours. I found a "MonsterPack" here:
http://forum.xda-developers.com/showthread.php?t=922870
Even this was more complicated then it needed. I had to download the 128mb RootPack image, and get it going so I can grab the needed root files. Then download the right size Clockwork image for my memory card and get it going. The end result ended in a Clockwork SD card. Then I made a "sdcard" folder from where I added the rootpack files and the stock image 1.0.1 flashable zip file.
Format the system and boot partitions, then flash the stock zip.
I just upgraded stock to 1.1, then will proceed to boot off the microsd and root, install GAPPS, etc.
I wish I knew of a great custom rom to flash. I flashed Nookie Froyo 0.6.8 and it powers down immediately (several complaints about this). Maybe CM7?

Ditto
I'm having this problem as well, but I can't seem to do anything to fix it. I was running 1.1, and auto-nootered using v3.0. Everything was hunky dory until I installed CWR. I flashed, shutdown, restarted, then chose to perform a backup which brought me down into CWR and I was never able to get out. I used the Monster pack zip to remove CWR, and now I boot to the "n" screen and sit forever. I tried the 8 hard resets and it said it installed on two different occasions, but still I sit on the "n" screen during boot. I tried the 1.0.1 restore zip as well, but to no avail. What do I need to do to get back up and running?

CW Recovery only
So I flashed my NC with both the pre-dualboot and the dual-honeycomb rom, but every time I reboot with the SD card inserted, it only boots to CW recovery. When I take it out..it boots to NC stock OS.
Am I suppose to remove clockwork recovery with the CW-removal zip? I tried that.. once it rebooted it went right back to CW. Should I be using two different SD cards? One for CW recovery and one to load the eMMc?
So confused...
What I need to know is what should be on the SD card after everything is flashed.

Mw : you could use a bootable cwr sdcard and flash 'emmc recovery repair', then format data and restore your backup.
Ehamonn: you have to remove cwr from the sdcard. Format should do the trick. But you'll loose the data on it..
Sent from my Desire HD using XDA App

Do I need to keep a boot image on the card after I format?

Well, if you only want to boot from internal memory, no.

[Q] Nook stuck at Nook Color boot-up screen. I think I screwed up.

Hello, I guess I went in blind and screwed it up. Here's exactly what I did.
1. Created a bootable CWR SD card and used ManualRooter on my stock 1.2. Everything went perfectly. Checked Market and full app list etc.
2. Copied phiremod 6.2 to CWR card. Booted into Recovery. Wiped data/factory reset. Installed phiremod. No error so far. Wiped dalvik cache (not sure if I ran wipe cache partition). Then I turned it off, rebooted and the Nook is now stuck at the loading screen.
Of course, only then did I realize I got a nook with the new partitions (blue sticker). What should I do now? I was planning to try repartitioning but not sure if that would do more damage.
Any input? Thanks.

Fixed it Went ahead and installed the 2 repartition/reformat zips and installed phiremod on top. Everything is just peachy

hey itaintrite, i'm have a similar issue.
burned my working rom to sd so i could flash emmc to 1.2 manual nooter. prob now is when i boot from my sd it hangs at 'touch the future of reading.'
what's this 'repartition/reformat' zip you speak of?
raze

Similar problem....could use some help please!!
OK. Noob who is eternally grateful to all the awesome folks here. With your help I successfully rooted my EVO last summer. Now I have a problem with my new Nook Color. I successfully rooted (NC 1.2) it with ManualNooter, but now it won't accept any other ROMS. Runs MN fine, but I used ROM Manager to download and flash CM7.0.3, but it hangs at the "n COLOR" boot screen. Same exact result with Phirerom. I was able to restore to MN by somehow achieving the CM Recovery and restoring the Nand backup. Meanwhile, while I am unable to flash CM7, I AM able to boot into it from an SD card. Help, please.

razorgaze said:
hey itaintrite, i'm have a similar issue.
burned my working rom to sd so i could flash emmc to 1.2 manual nooter. prob now is when i boot from my sd it hangs at 'touch the future of reading.'
what's this 'repartition/reformat' zip you speak of?
raze
Click to expand...
Click to collapse
The repartition/reformat are in the thread that helps you repartition your 1.2 refurb nook to the older partition format. You can't install any custom roms otherwise.

I am having a similar issue. I rooted my new Blue Dot NC, I made my microSD card image with CW 3.2.0.1-eyeballer and ManualRooter 4.6.16 followed all instructions, and everything came out fine. installed apps, copied over books etc. all running fine. The problem is when I reboot the NC it will start rebooting and then get stuck cycling in the NOOK COLOR animation. I have to reset it, and re-register it with B&N and install ManualRooter again.
Any ideas why this happens? Could it be an app causing this??
I am rooting again and testing the reset before I add any apps, then app by app and see if something comes up.
Any help would be appreciated.

Recent Trouble with ROM Manager

I recently decided that I wanted to do a fresh install of CM7 using the latest nightly. I wiped everything, including boot (which I think is the problem). I made a bootable CWR SD card and installed the latest nightly and gapps. Everything booted up fine and ran great, until I tried to use ROM Manager. Every time I try to boot into recovery, the Nook hangs at the "ReadForever" screen. It was hanging at the new Cyanogen boot logo, but in an attempt to correct the issue, I flashed the stock 1.2 uboot. I have also noticed that several apps are now showing up at phone size when they were fine before running the same setup. I am running n87, 5/23/11 OC, and the stock 1.2 uboot. Does anyone have any idea what the problem might be?

You can try to disable the "compatibility mode" in order to try and get the apps to use the full screen. Regarding the Clockwork recovery issue, I have no idea - sorry!

Stumped....Maybe you guys can help. Or maybe not

I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue

oman0123 said:
I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue
Click to expand...
Click to collapse
You probably have the wrong bootloader and kernel...the newest cm7s are based on the 2.6.32, not the older 2.6.29 (or something), and the newest 1.2 bootloader..which you probably don't have if it's "been awhile"..lol...You have to upgrade your Cwm first, from 3.0.1.0 to 3.0.2.8, I think, then flash your Cwm to a nightly after 86??(Google to check), and it will change your boot partition to the correct one...If your nook still says "touch the future", you're on the wrong bootloader.....Also, quit using Phiremod.....it's a copy of Cm7 first of all, but by the time it's released, it's already outdated, it's not updated like it should be, and it's Douchey. Google the basics of what I described above if it sounds like that might be your problem and lmk how it works out for you....Btw....I used nightly 106 for this exact thing on another of my Nooks a few days ago and it worked flawlessly...There are newer nightlies out, but that one for sure worked.....
Sent from my NookColor using Tapatalk

I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?

Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above

DiDGR8 said:
I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?
Click to expand...
Click to collapse
Ive tried all of that. hopefull mazooks way works. Otherwise im out of ideas

oman0123 said:
Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above
Click to expand...
Click to collapse
If I remember correctly, you can't just jump from 3.0.0.6 or 3.0.1.0 to newest...there's one in between that transitions the upgrade in bootloaders...I'm pretty sure I went 3.0.1.0 to 3.0.2.8 to flashing Cm7 nightly 106...then to upgrade to Cwm 3.2.0.1 while in Rom manager, while using Cm7....leSigh....Clockworkmod is the only thing I can't stand about using my Nook....(though I rarely need it any more) AmonRa is such a better (and fully functional) recovery build...One thing I wish we had gotten.....
Sent from my NookColor using Tapatalk

What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?

oman0123 said:
What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?
Click to expand...
Click to collapse
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk

mazook98 said:
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Well Id love to try that but.....My nook wont turn on. It was fully charged today. Im either gonna make a bootable cwm or go back to stock and root again. I dont know if that will work though because its not even powering up.

Ok....i think im making progess....The newest nightly just goes into a bootloop. better than a clockwork bootloop i guess..... any advice on how to get it to install properly? i feel like im making progress. normal bootloops are better than what i was getting

Bueller............Bueller lmao.
Seriously though.....if anybody can figure this out it would make my year

Try this, install stock 1.2....
boot it up, go through the annoying setup, log into google apps, then power down.
Boot into CWR SD, this should have the os that you want already on it, and the google apps file.
THen click install from zip, choose zip, install the OS, after complete install google apps, then restart without sd
Do not format anything, it should do the trick.

Cant mount ECCM and lost internal recovery?

The other day i took my HD+. I havent used it for two years, and had been running the hybrid boot from the sd card, which was awesome! Well, I wiped the SD card and wiped the tablet. So essentially it was stock.
I formatted a new microSD card with verygreens recovery, booted it, flashed the rom and google apps, and thought everything was fine. Well, I kept getting a google services stopped working error so I decided to just experiment with Marshmallow. I went into the recovery, wiped everything, and flashed amaces ASOP rom. Then tried flashing gapps, and got an error that said that I didnt have android 6.0.x
Must have failed. And when I booted from the SD, sure enough it booted to KitKat, the one I had flashed previously. Well, eventually I took out the SD and to my surprise, cyanoboot was installed to the tablet and not booting from the SD card. And the marshmallow rom launched (without gapps). I tried booting into the internal cyanoboot, but it was the old one. I held the power button and the home button, but to no avail.
This is probably where I messed stuff up. It started booting and started booting stock, which I didnt want. Where it has the little white loading bar. I force shut it down. Well then it started acting weird and not even booting with the internal cyanoboot. It now just flashes the nook logo.
Luckily, I can boot to the external cyanoboot, but it has an error mounting the emmc. Should I reflash the stock rom and recovery?
Thanks!

SouthernGeorge said:
The other day i took my HD+. I havent used it for two years, and had been running the hybrid boot from the sd card, which was awesome! Well, I wiped the SD card and wiped the tablet. So essentially it was stock.
I formatted a new microSD card with verygreens recovery, booted it, flashed the rom and google apps, and thought everything was fine. Well, I kept getting a google services stopped working error so I decided to just experiment with Marshmallow. I went into the recovery, wiped everything, and flashed amaces ASOP rom. Then tried flashing gapps, and got an error that said that I didnt have android 6.0.x
Must have failed. And when I booted from the SD, sure enough it booted to KitKat, the one I had flashed previously. Well, eventually I took out the SD and to my surprise, cyanoboot was installed to the tablet and not booting from the SD card. And the marshmallow rom launched (without gapps). I tried booting into the internal cyanoboot, but it was the old one. I held the power button and the home button, but to no avail.
Click to expand...
Click to collapse
Running CM internally on EMMC and on SDcard use different CM ROM image versions that are not interchangeable. Currently there is no SDcard build for CM12.x or CM13, so your only choice is to flash and run them on EMMC.
This is probably where I messed stuff up. It started booting and started booting stock, which I didnt want. Where it has the little white loading bar. I force shut it down. Well then it started acting weird and not even booting with the internal cyanoboot. It now just flashes the nook logo.
Luckily, I can boot to the external cyanoboot, but it has an error mounting the emmc. Should I reflash the stock rom and recovery?
Click to expand...
Click to collapse
If you plan to go back to stock ROM and recovery, see item #6 of http://forum.xda-developers.com/showthread.php?t=2062613.

I don't really care about going back to stock, but I can't mount the emmc, will flashing the original recovery fix that do you think?

SouthernGeorge said:
I don't really care about going back to stock, but I can't mount the emmc, will flashing the original recovery fix that do you think?
Click to expand...
Click to collapse
I don't think the cause of your "can't mount emmc" problem is due to not having the original recovery. And there is no point in restoring stock recovery unless you want to re-install stock ROM.

So what do you suggest? Try to flash to CWM recovery and hope it fixes the mounting emmc problem?

Great news! Luckily the rom was still intact. I was able to run a "factory reset" and that fixed the emmc mount problem. The CWM recovery was still installed too and it booted into Marshmallow like I had before!
At this point, can I install a different resident recovery utility? I dont see why not.
Thanks for your help