yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] nemith:
It can be synced to Google though. Like i said instead of guessing go in do a wipe in CWM and then mount it and poke around. I really doubt it's not formatting /data.
[Nook Color Android Development] gazorp:
How to enter recovery after install?

Hello! I used a CWM bootable microSD to install the zip file attached in the op. Now for the life of me i cannot figure out how to enter recovery.

I have tried holding vol+, vol-, home key, nothing is working any advice is appreciated!
[Nook Color Android Development] nemith:
While off press and hold 'n' and then press and hold PWR. After seeing the "Touch the power of..." splash screen count to five and let go of the power button. Don't let go of "n" until you are in CWM.

If you are still having problems find a u-boot.bin from the 1.1.0 update and flash that yo your /boot.
[Nook Color Android Development] liqn7:
Brand new autonooted nook- do I install rom manager from the marketand flash recovery via it?
[Nook Color Android Development] ovar:
I have searched through the 1.1.0 update and I can't find this u-boot.bin file.

Can anyone that has had to do this provide some more precise instructions?
[Nook Color Android Development] anurbanlegend:
I got mine out of the original 1.1.0 Sideload_update.zip file you can download from BN website.
[Nook Color Android Development] ovar:
And where do I push it? I can't find a boot directory when browsing my phone with adb.
[Nook Color Android Development] anurbanlegend:
The first post has the code to mount the boot partition. Then just push the u-boot.bin over.

EDIT: try

adb shell busybox mount / -o rw,remount
adb shell busybox mkdir /boot
adb shell busybox mount /dev/block/mmcblk0p1 /boot
adb pull /boot/u-boot.bin u-boot.bin.bak
adb push u-boot.bin /boot/u-boot.bin
adb shell busybox umount /boot
[Nook Color Android Development] ovar:
Total Booya man. I got it. Thanks for your help.
[Nook Color Android Development] faceman66:
Anyone tried this yet? I am hearing that folks are still getting the "can't mount /system" error after flashing this zip. CWR shows up as v3.0.1.0 in ROM Manager and in recovery, but can't perform a backup.
[Nook Color Android Development] lafester:
worked fine for me. just made a backup and restored from it.

only thing is it takes a loooong time to complete either task.
[Nook Color Android Development] faceman66:
Thanks, I am having them re-double check the MD5 of their download, reflash again, and then try the manual install as a last resort.
[Nook Color Android Development] simon.ponder:
I wasn't complaining, just reporting a possible anomaly. I just assumed that those things would be restored only from the primary google account on the phone.
[Nook Color Android Development] simon.ponder:
Size

For what it is worth, the backup that my nook makes, is about 8 to 10 times as big in size as the backup my phone makes, and they are both running CM7 nightlies, so maybe it just the amount of data it has to deal with.
[Nook Color Android Development] richard20260:
Can't seem to use the Muffin link. Although the device says sucess it still remain at the previous version.

Was going to try the manual method but although got the recovery image downloaded, I cannot get the kernal to download from Mediafire, can this be posted elsewhere or in XDA?

Thanks in advance Richard
[Nook Color Android Development] bdcrim:
Did you try rebooting into recovery after installing the zip? ROM Manager might not show the update. Recovery should show the current version.
[Nook Color Android Development] tacitapproval:
I am unable to boot into recovery with either power+n or the cm7 reboot option. I can though get to cwm by selecting reboot to recovery in rom manager. I have tried both the manual and zip method and they seem to be successful, but the problem remains . I'm not sure what to try next. Anyone have any suggestions?
[Nook Color Android Development] junkrobot:
So, I flashed this new version and it worked fine, but now it won't mount /system after selecting "Nook Color," but it will mount if I flash again and select "Nook Color (old)." Has anyone encountered this?

Also, is CWM the reason why my NC can't boot normally after being off all night? Maybe this is unrelated, but it seems reasonable that it might be.
[Nook Color Android Development] eyecrispy:
Seems tricky for some folks. With NC off, hold power + n till you see the "touch the future of reading" screen. Count to 5 after you see that screen and then let go of both buttons and wait. The NC should boot into CWR.
[Nook Color Android Development] junkrobot:
Quick update:

I stepped away from the thread and noticed that the marketplace was encouraging me to update to 3.0.1.1, so I did. Now things are really weird and it won't even let me manually flash from the program. Did I blow it big time? Now the software itself says 3.0.1.1, but the recovery menu says 3.0.1.0. Sorry for all my newbie woes, everyone.
[Nook Color Android Development] richard20260:
Yes, tried that already boots to recovery but still old release hence resorting to manual and the need for the kernal
[Nook Color Android Development] avi!:
Guys I am on CM7 build and I have Rom Manager 3.0.1.1, I can use Muffin's update.zip ???
[Nook Color Android Development] faceman66:
There are a lot of people with this situation, but there has not been any answer beyond "don't use the (old)" even though it's the only one that works for some people.

Don't confuse a ROM Manager version with a CWR version. They are two separate things.
[Nook Color Android Development] Calla969:
So, I used the automated zip to flash the latest recovery, and now I can't boot at all unless there is an SD card in the Nook. I've tried restoring my backups and everything I can think of. I can't access the Nook through ADB (not real familiar with ADB, so I may be doing something wrong). Basically, all I can do is boot into CWR 3. 0.0.6. If I remove the SD card, nothing happens when I try to boot up. Nothing at all. I haven't been able to find any help yet. Everything seems to require ADB. What can I do?? Thanks in advance.

Edit: I was running CM7 v.11 and dual booting HC. I've tried removing the dual boot with no luck.
[Nook Color Android Development] rexroof:
Can't boot into recovery without SD card

I have a nookcolor with CM7 (cm_encore_full-3.zip).

I've tried using the CM7 boot menu, Rom Manager, and the power-n routine, none of them get me into CWR.

Note: I never see the "Future of Reading" lingo talked about in posts above, I only see some text that says "Loading..." and then the CM7 boot screen.

been looking for /tmp/recovery.log, but I haven't found it yet.

using adb shell I noticed there wasn't a /tmp directory, I created one with the perms 1777.

Anyone have any pointers on getting into CWR without re-imagining my SD card?

Also, I had tried using RomManager to install CWR before I found this post. did i munge something up? perhaps my bios/firmware/booting is jacked?

Lastly, I noticed that even though I made a /boot directory and used it during the manual install, it goes away when I reboot the nook.
[Nook Color Android Development] nemith:
Read the posts on replacing your u-boot.bin a couple of pages ago. I don't know where you guys are getting the u-boot.bin that doesn't allow recovery.

/tmp/recovery.log is only after recovery boots.
[Nook Color Android Development] anurbanlegend:
I think the u-boot.bin that is jacking people up is from the dual boot post. From the dual boot first post

"Just a word on booting into recovery. With the dual boot u-boot.bin, I have changed the button combo to VOL UP + VOL DOWN for recovery. So if you want to go to recovery, remember this is the key combo you need to hit. Not Power + n."

So if you guys don't want to go back a couple pages like nemith suggest to fix your u-boot.bin, try vol up + vol down to boot into recovery. If that doesn't work... replace your u-boot.bin with the one from stock.
[Nook Color Android Development] nemith:
Changing this was a poor idea. It may be easier to hit, but there is a reason why the CM7 team doesn't try to replace anything that doesn't need to be replaced.
[Nook Color Android Development] Calla969:
I can boot into recovery (the old one) without problems. I can falsh wahtever I want, but when I select reboot, it shuts down and Pressing any button combination does nothing at all. Black, dead screen. If I insert my bootable SD card, I can boot into recovery, but nothing else. I used the Zip to install the latest CWR, made a backup, everything was fine. This morning, I formated my old bootable SD card and tried to reboot into recovery from the app just to clear battery stats. Ever since using the app to boot into recovery, I've had a dead screen unless I have an SD card in.
[Nook Color Android Development] faceman66:
Sounds like somewhere along the way you got a corrupted /boot. Use a bootable CWR card to flash Dalingrin's Repartition_boot_with_stock.zip and you should be able to boot again. Might be worth flashing the CWR while there and see if that clears everything back up.
[Nook Color Android Development] faceman66:
OK, I can just about say without doubt (there's always a little doubt) that this works as advertised. A few folks had asked me if this was possible and none wanted to try so I went ahead and experimented.

* I started with CM7 - RM v3.0.1.0 - CWR v3.0.1.0: rebooted into recovery and performed a full backup (this is of my latest and current state)

* I then wiped cache, dalvik (locked up - forced reboot to recovery), formatted /data /system, restored my B&N stock 1.0.1 rooted backup (this was my first backup after re-rooting a few weeks ago)

* Restore completed as normal, CWR was locked up after restore (which happens sometimes) - forced reboot and it booted to CWR v3.0.0.5 (reported)

* Rebooted via CWR and loaded up B&N stock 1.0.1 - rooted just fine. Played around and everything seemed to work except I couldn't get wifi to connect, not sure why.

* Loaded up RM and it showed as RM v3.0.0.7 with a CWR of v3.0.1.0 (which conflicts with what I saw in recovery after restoring)

* Rebooted into recovery via RM, recovery console reports being v3.0.0.5 so I am nervouse, but do a wipe of cache, dalvik (no lock), formatted /data /system, restored my latest CM7 recovery.

o (It's important to note this is the scary point because I am trying to restore an ext4 backup from what looks like a ext3 only compatible CWR)

* Restore completes as hoped for, but locks after completion (same as before, this sometimes happens)

* Forced reboot and CM7 loaded as normal before doing any experimenting. Wow.. it works!

* Played around and all seems to be like it was before I started, nice to know.

* Loaded RM and see RM v3.0.1.0 and CWR v3.0.1.0 again, all is well so far.

* Rebooted to recovery via RM, wiped and formatted again, restored my fully tweaked out B&N stock 1.0.1 backup from just before moving to CM7 and it loaded fine.

* Loaded up RM, and see RM v3.0.0.7 and CWR v3.0.1.0 - but reoobting into recovery shows a CWR of v3.0.0.5 (I think this is just coming from a file within recovery but isn't true because my restoring of CM7 worked, not sure)

* Wiped everything and formatted again, loaded up my latest CM7 again, and all is well.

I can say that with my NC, I was able to flash backups from ext4 to ext3 back to ext4 over and over. This means that I can now create a backup of my CM7, wipe and install something completely different for testing or article purposes, wipe it and restore my CM7 for daily use. Woot! Woot! (Definitely deserves the double woot)
[Nook Color Android Development] tacitapproval:
That did it. I was unaware it is so tempramental about booting into recovery. Thanks.
[Nook Color Android Development] Calla969:
Thanks! That worked, but now I'm scared to try to update CWR again. I'm using 3.0.0.6. I'm not sure what to do.

Edit: Installed CWR manually with ADB and everything seems good. This Nook has got to be the best way to learn about hacking Android. One of my best purchases yet!
[Nook Color Android Development] faceman66:
Awesome, glad it worked for you. You should be able to flash the latest CWR from ROM Manager now and be just fine. Go ahead and do a full nand backup before you do though. Of course you can always do a 'removeCWR' with a bootable SD if things go wonky again.
[Nook Color Android Development] rexroof:
thanks! I downloaded the official nook update zip and installed the u-boot.bin from that.

I had previously installed Honeycomb on this nook, perhaps it overwrote the /boot partition with a bad u-boot.bin?
[Nook Color Android Development] onclebob:
hi,

i'have a noob question, i wan't to flash the recovery (maybe it can help with my NC "bad booting") with the new 3.0.1 version.

i think the not to hard solution for me is using the "cwmr_3.0.1.0.zip" method but i'm not completly "flash fluent". So when you said "flash like you would a rom" you mean burning the zip to sd? renaming "update.zip", put on sd and it works alone or using a recovery option , in that case i must choose "apply update from sd card" or "install zip from sd card"?

If someone can explain me the diff between these two options i apreciate.

thank you,

Bob
[Nook Color Android Development] Mistar Muffin:
Find one of the many bootable sd card images for clockworkmod recovery posted on this forum. The images can be written to a micro SD card using WinImage under Windows or dd under linux. Once the image is written to the sd card, copy the cwmr_3.0.1.0.zip onto the root of the sd card and put it in the NC. Boot the NC and it will start CWMR. Choose install zip from sd card, then choose zip. Select cwmr_3.0.1.0.zip and confirm. It will then copy the necessary files for CWMR to your internal NC storage. You can then power off the NC, remove the SD card, and still access CWMR via the button combo at boot.
[Nook Color Android Development] EliteOfficer:
Looking for a little help here please.

I was using the nookie-froyo-0.6.8.custom.3 rom so I decided to update CW by flashing the .zip that was suggested by MrMuffin. Upon flashing with RM and rebooting everything is different, the custom Froyo was stripped and it's all vanilla Froyo again.. lol I'm dying here.
[Nook Color Android Development] onclebob:
as i have a working 3.0.0.5 CWR from the Custom nookie froyo (this one : http://xdaforums.com/showthread.php?t=938200 ), cannot i update the CWR by booting on it.

I understood that cwr load in ramdisk, so overwriting himself is not a problem.

By reading EliteOfficier i'n not too.. confiant..

Edit: just try to install from existing CWR, works fine.

thank you
[Nook Color Android Development] Wile-E-Coyote:
Running Rom Manager 3.0.1.2 (I know it isn't the same as CWR - I haven't flashed the new CWR). However, if I hit "Flash ClockworkMod Recovery) I am given a list which includes "Nook Color (Old)" and, for the first time, "Nook Color." Will this allow me to flash the new CWR without having to create a bootable card?
[Nook Color Android Development] nemith:
As I stated in the OP don't use the one marked old.
[Nook Color Android Development] Wile-E-Coyote:
Thanks, but my question was a little different. Will flashing the "Nook Color" (as opposed to "Nook Color (Old)") eliminate the need for me to flash via SD card? In other words, will this allow me to load new CM7 nightlyies using ROM Manager?

Sorry if I was unclear before.
[Nook Color Android Development] Chahk:
ROM Manager v3.0.1.2 on my NC running CM7 #13 is only seeing CWR 3.0.0.5 for both available and current, even though I have 3.0.1.0 installed and working perfectly.
[Nook Color Android Development] junkrobot:
I wish I could figure out why it won't mount properly when I select the Nook Color instead of Nook Color (Old).

Also, does anyone know if CWR is the reason NC won't boot properly after being turned off for awhile? I'm just trying to diagnose the problem and get it ironed out. It's really a bummer to have to boot into recovery every time I want to turn the thing off. Being able to make a back-up would be great as well. I know this is all a work in progress, but the boot issue is really wearing me thin with my OCD nonsense.
[Nook Color Android Development] KitF:
You have to tap "Flash Recovery" for it to check for updates.
[Nook Color Android Development] tgeske88:
I already marked it as being the 'old nook color', is there any way that I can go back and change it to the 'new'? I haven't had any problems yet, but i just want to be safe. Thanks in advance

Edit: flashed new ROM and had to do a fresh install. Then prompted me to choose, all is well
[Nook Color Android Development] nemith:
That should work but i haven't tested.
[Nook Color Android Development] Pryach:
I hope the good people at XDA can forgive me, but I've made a huge mistake. I didn't see this thread until it was too late.

I'm stuck in a ClockworkMod Recovery loop. Every time I reboot, it goes back into CWMR, I can't get the Nook OS to come up.

I'm pretty sure every time I installed CWM I got version 3.0.1.0 but every time I got into Recovery it said Clockwork Moder Recovery v.3.0.0.5.

A little background: I did the AutoNooter this weekend. I wanted to play around with some ROMs but first I wanted to make sure I had a backup. I went into CWM and flashed Clockwork Recovery, it asked if I wanted the old or non-old, I chose the non-old.

I rebooted into recovery and tried to perform a backup, but it failed stating "can't mount /system". I decided to mess around with the SD card only ROMs so I wouldn't mess anything up on my internal memory. They weren't bad, but I really wanted to get a ROM onto the internal memory. I remember reading somewhere that I should've picked the "old" version of Recovery. So I uninstalled CWM and reinstalled it. When I flashed CWM Recovery, I picked the old version.

After doing this I rebooted into recovery and performed a backup. This time it worked! But now, every time I reboot, it just goes back to clockwork recovery. I can't get it to boot back into the Nook OS.

So my good people, how screwed am I? Reading the top of this thread I realize I did many things wrong, and I know that, and I'm sorry.

--edit-- Hmm, I guess I was confusing things. I think I was downloading ROM Manager 3.0.1.0 and it was flashing Clockwork Recovery 3.0.0.5.
[Nook Color Android Development] Nanan00:
So how do I boot into recovery with 3.0.1.0? Power on and N doesnt work, either does vol up or down.
[Nook Color Android Development] tomorrowneverdie:
One of possible reason is the TF card not compatible. There is a post about it. Of course there might be other reason, such as 8G card with 4G image etc.

Try more, dude.
[Nook Color Android Development] will2live:
Mine is booting fine into 3.0.1.0 recovery. I did have some issue at first but was giving a suggestion. when powering on ( holding the "n & pwr key) as soon as you see the backlight or the first splash screen come on count to 5 and then let go of both button and it should boot into recovery. I tried the trick and it has worked every single time so far.
[Nook Color Android Development] britoso:
Q1: I'm guessing the linked kernel with support for 3.0.1.0 is for 2.3/2.2 ROMs, is there a specific version for honeycomb?

Can I install ROM Manager and then flash CWR recovery from it ? Will that work as expected?

Q2: is there a way to use 3.0.1.0 without a dedicated sd card for boot purposes? I only have one sd card and backing up/restoring data is a pain.

Q3: will 3.0.1.0 be able to restore the backup it makes ? had a bad experience with it and CM7. (MD5 mismatch)

Update: installed ROM Manager and tried 3.0.0.9 and 3.0.1.0 both dont get applied correctly. (no errors)

Cannot get into recovery via the app or via adb. :(

Update 2:

tried the instructions anyway (except for the kernel), it didnt fix the problem. 'adb reboot recovery' still boots to honeycomb :(

update 3:

Now I'm using my CWR 3.0.0.5 sdcard to get to recovery, Whenever I do a full reboot I eject the sd card. Not a bad workaround :P

3.0.0.5 works with both HC and froyo. Didnt find a 3.0.1.0 image anywhere.
[Nook Color Android Development] cj1896:
Update.zip worked like a charm for me going from 3.0.0.5 running nookie froyo 0.6.8
[Nook Color Android Development] andmer:
followed instructinos all went well, but i can not get into recovery no matter how i try.

I tried reboot into recovery option from power button in cm7, I tried reboot into recovery from rom manager, I tried holding down power+n key for 5seconds then letting go, i even tried power + volup/down, I tried adb reboot recovery, all nothing.

any ideas?
[Nook Color Android Development] anurbanlegend:
Been asked and answered several times. Look back a few pages and fix your u-boot.bin.
[Nook Color Android Development] case-sensitive:
I made a dumb noob mistake :( and I hope the good folks here will help me sort things out.

Starting from an autonooked, stocked 2.1 with no rom manager or CWM, I tried to installed CMW 3.0.1 directly following the manual installation instruction in the OP.

That didn't work. Then I came across

http://www.androidtablets.net/forum...m-manager-nandroid-backup-custom-kernels.html

which does work but (because at the time it's an old post) results in a 3.0.0.5 CWM on my recovery sdcard. And now whenever I run CWM on the sdcard, when I hit "reboot" it would first reboot to 3.0.1 on emmc and then reboot back to the NC.

The NC otherwise runs fine and I don't see this incorrectly flashed CMW 3.0.1 unless I use the CWM sdcard, but just bugs me and I know that someday it's going to cause problems...

Could the good folks here suggests a way for me to remove the incorrectly installed CMW 3.0.1? It is clearly sitting on emmc (probably /boot?), and I don't know adb commands well enough to figure how to get rid of the two files (and if that's a bad idea...)

Many thanks for your help.
[Nook Color Android Development] will2live:
@case-sen easiest way IMO to remove CWR from the internal mem is to make a 3.0.0.5 bootable sdcard. Then follow the info on this link that explain what you need and how to remove it using the *.zip file which is linked in the link I'll post below

http://legacyschool.us.to/nookdev/clockwork/rootpack-instructions.html
[Nook Color Android Development] case-sensitive:
I already have a 3.0.0.5 recovery sdcard, so I downloaded the removeclockwork.zip from the link you provided and removed the incorrectly installed 3.0.1 CWM from my emmc. World peace is restored.

THANKS!
[Nook Color Android Development] will2live:
Sweet glad to hear it worked out for ya. Peace
[Nook Color Android Development] constellanation:
is there anyway to change the u-boot.bin file through root explorer or terminal?

I'm kind of angry with adb on my nook right now :)

and yeah I cannot get this thing to boot into recovery...
[Nook Color Android Development] constellanation:
as for the above question, I was specifically asking about these commands.:)
[Nook Color Android Development] jayhammy:
I, like many others, am not having luck booting into recovery via the emmc partition. I've held the N and power and I've done every combination along with different timings, etc. No luck.

Any help is appreciated! I'd hoped this would be like my Incredible, but, alas, it's not.
[Nook Color Android Development] newellj79:
Hmmm. How it works for me. I hold down power and n, it will get to the "future of reading" screen and then shut off. Then I turn on by just pressing the power button and it boots into recovery.
[Nook Color Android Development] jayhammy:
I just tried it your way by pressing the power button right after it shuts off. Nothing. Just reboots as normal.

I've never gotten "the future of reading" upon booting. Only "loading." My friend's Nook that I rooted always has "the future of reading." Interesting.