yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] openallnight:
sorry if I mention the obvious. Did you try booting from SD (with clockwork) and then manually installing a backup if you have one? it may just fix your boot partition if its out of whack. Once you are up and running you can go ahead and install clockwork manually as mentioned in the OP. I have never relied on ROM manager to install the right version of CWR but always installed it manually after booting from SD and it has always worked w/o any issues.

As for booting into CWR i press the Power button immediately followed by N for a 2-3 seconds into seing the "Touch the..." screen but you don't even see that message.
[Nook Color Android Development] anurbanlegend:
Sounds like you have the wrong u-boot.bin too... Search back a few pages for steps to get you back onto the stock u-boot.bin that will show you the "the future of reading" screen and will let you boot into recovery...
[Nook Color Android Development] jayhammy:
Ok, I want to thank everybody who helped me with the CWMR on my emmr partition. I was unable to get it to boot. Apparently, since I was never getting "Touch the Future of Reading" (I was getting "Loading" instead), I had the wrong boot partition. I simply uninstalled CWM and then reinstalled it. This link was where I went for help: http://xdaforums.com/showthread.php?t=914690

THANKS, AGAIN!
[Nook Color Android Development] cmstlist:
I've noticed that any time I wipe the dalvik cache, recovery freezes immediately after. No big deal as I can always force power off and start again, but it happens pretty consistently.
[Nook Color Android Development] eyecrispy:
Not new to this version. But would be nice if we didnt have to power off every time we clear dalvic.
[Nook Color Android Development] *damo*:
My Rom manager says that 2.5.0.7 is latest, how do I update it?
[Nook Color Android Development] doncaruana:
I beg to differ. Maybe if you are using emmc this is the case. But in some cases (a stock 1.1.0 rooted, in my case), the "Nook Color" option DOES NOT WORK. It causes the "can't mount system" issue. Once I reflashed with "Nook Color (old)", it worked perfectly.

Multiple people have reported the same issue, so it's not just me. Maybe it all worked keen with previous versions of Rom Manager, but as of 3.0.1.2, this is an issue.
[Nook Color Android Development] cmstlist:
The current version of ROM Manager flashes 3.0.1.0 which works on both ext3 and ext4. If you are not successful in flashing it via ROM Manager, then flash any version you can (or boot from a CWM SD card), and then use the cwmr_3.0.1.0.zip file to get internal 3.0.1.0. Or alternately use the info in this thread:

http://xdaforums.com/showthread.php?t=987735

to make a bootable 3.0.1.0 SD card.
[Nook Color Android Development] doncaruana:
I guess this is the part that confuses me - "successful". Rom Manager said it flashed it to 3.0.1.0 when I selected "Nook Color", but I, like so many others, ran into the "can't mount system" issue. The original post mentioned it had problems, but led me to believe that the issue is only with ext4 roms (which this isn't). Even the part about not being able to backup refers to ext4.

If we are saying that we just flat out shouldn't even try to use the one that rom manager flashes, then what's the point of selecting nook color vs nook color old? I mean I can accept that we have to go flash using this image, etc, but is that what is being said?
[Nook Color Android Development] KDOG2020:
Running into similar problem....new CWR installed fine (and also had to select Nook Color) but won't get past the "Touch the Future of Reading" screen at boot up. But will startup fine WITHOUT card installed, and runs fine when I install card after its started. I'm considering going to CM7 and want to know if this will be a serious problem.
[Nook Color Android Development] atomclock:
Does this version have adds?

I am using 3.0.0.5 and there aren't any adds. I was wondering if the 3.0.1.0 version has adds?

I'm asking because I tried the nookie-froyo 6.8.3 and CW had adds. I would rather stay with 3.0.0.5 than have adds flashing at the bottom of the screen.

Thanks
[Nook Color Android Development] faceman66:
That was the issue that I was trying to point out before, but was vehemently told I was wrong (as your quote above shows). Despite many people posting the 'can't mount /system' issue there has been no official answer. However it seems that everyone that has had the issue that has gone back and flashed CWR again from ROM Manager and selected the 'Nook Color (old)' device has been able to successfully back up their devices. So, for now, it's apparently just dozens of "anomalies" and should be ignored by the op.
[Nook Color Android Development] cmstlist:
Perhaps the issue you are having is the related to the fact that ROM Manager can't successfully flash the right kernel for ext4 from within a booted-up OS?

If you are having the /system problem - have you tried flashing cwmr_3.0.1.0.zip from Clockwork as an alternate way to install 3.0.1.0? Do you still have the problem then?
[Nook Color Android Development] doncaruana:
I guess this is what I was driving at. I haven't tried this (at this point, "if it ain't broke, don't fix it") yet, but, if indeed that's the answer, it shouldn't be.

Maybe it's just my ignorance, but it doesn't seem to me that if I am running rooted stock that I should need to worry about ext4, hence this shouldn't be the necessary solution for the issue. If, however, this *is* the case, then the original post is certainly far from clear in this point and might even be called misleading.

My point here is trying to bring a little clarity to a clearly confusing issue. The empirical data (ie the number of people who have the issue I had) says that there is something fundamentally missing from the instructions in the original post and I'm trying to get that sorted out for the benefit of everyone.
[Nook Color Android Development] junkrobot:
What's interesting is that after flashing the "Nook Color" over "Nook Color (Old)," my boot issues have seemingly stopped, which is great, but I still can't mount /system, which is not so great. I don't need to back anything up since no major changes have happened, but in the event that I do want to try something else, being able to mount is obviously essential. I'm not sure I've seen a solution to the mounting issue in here, but I also have been on vacation.
[Nook Color Android Development] doncaruana:
My suspicion is that the right approach is as follows:

1) Don't bother flashing from Rom Manager and don't worry if you already have. Perhaps flashing nook color (old) is best here to have a visual acknowledgement later, but, if you do, reboot immediately.

2) Create a bootable sc card with cmr on it and load cwmr_3.0.1.0.zip from the original post. I suppose you could boot into recovery from rom manager, but this seems risky to me.

3) Reboot and see if you can do a backup, also note that Rom Manager should now show 3.0.1.0

There are "known problems" with 3.0.0.5, but I don't know if any of them have anything to do with using a stock rom anyway, but we are told that "Nook Color (old)" is going away, so all this is important. But no one has confirmed any of this yet.

My experience and observation thus far is as follows:

a) Nook Color(old) is the only one that works OOTB if you want to do backups.

b) If you flash the recovery and IMMEDIATELY boot into recovery, you end up with boot loops

c) The way to get rid of the boot loops is to remove cwr by installing CWR-removal.zip from recovery mode once you are in it.

My guess is that somewhere you're recovery kernel is whacked out and you need to do a removal (per c above) and start over on the cmr stuff, per 1-3 above. But I'm just an observant noob, so I might be completely offbase. That's why I'm hoping someone can provide some more definitive feedback.
[Nook Color Android Development] comdei:
How do you get the new version to work on emmc froyo?

I hold down n and it still boots up.
[Nook Color Android Development] DeadStiff:
I figured out a way to wipe dalvik without CWM locking up.

Go into wipe dalvik like normal but don't press yes, back out of the menu using the power button.

After that you can now wipe dalvik without it locking up.
[Nook Color Android Development] DizzyDen:
You should also be able to just go into mounts and storage and unmount dalvik before wiping it.
[Nook Color Android Development] woot1524:
I just want to post this as an FYI.

I was one of the people who didn't have the "Touch the future of reading" boot splash, along with not being able to boot into recovery from the off state.. I found a simular post a few pages back and he removed CWM then reinstalled it.

Now here comes the fun part.

Now I'm stuck at the "n" screen after removing cwm via this thread: http://xdaforums.com/showthread.php?t=914690

I'm not asking for help, I can solve this on my own.

I'll just recover my backup with a bootable SD-card

What I want to know is this, Why did this happen, and how can I update my recovered /boot partition to the proper CWM version without repeating this little mishap?

Thanks to anyone that can help.

EDIT:

I fixed the issue and got the latest, and working, version of CWM installed.

I re-tried the remove CWM tool, again it messed up my boot partition hanging at 'n' screen. I then tried the CWM 3.0.1.0 flashable .zip from the front page, which didn't fix my boot problem, but it did fix my no CWM from off-state problem. I then re flashed the CM7 OC kernel, and BOOM, boots like a champ.
[Nook Color Android Development] will2live:
I'd be interested in knowing why this happens also as I've had it happen a couple of times myself. Since then I've made life easy tho. I no longer flash CWR to eMMC as it seems to cause nothing but issues like this when trying to change things around. Plus IMO at least it makes more sense for me to have CWR on a bootable sdcard with all my backups. This way no matter what happens to the Nook I still have all my stuff to be able to flash back to in a heartbeat if needed.
[Nook Color Android Development] faceman66:
I think that the "remove CWR" zips might need to be updated since the advent of the newer CWR's that incorporate ext4, this only seemed to crop up after CWRv3.0.0.6
[Nook Color Android Development] cvhovey:
Didn't work for me. And in addition to lock up after Dalvik wipe, I've started to get a lock up after doing a backup or restore. Re-installing didn't help.
[Nook Color Android Development] DizzyDen:
If you're seeing issues about error mounting system.... update the kernal manuall per OP.

I've found unmounting dalvik before wiping prevents lock up.... works to unmount any partition you are going to wipe prior to wiping it.
[Nook Color Android Development] jtbnet:
CWR to install zip on SDcard

Maybe I'm the only one who cares here, as I haven't gotten replies in a couple sdcard install related threads, but it would seem to me that a cwr that could actually install packages to the bootable SDcard could be useful for many.... especially as there are a good number of 'Roms' ;

brianf's Froyo sd install,

deeper-blue's HoneyComb Preview,

Divine_Madcat's CM7

that folks are running from SDcard for testing and everytime I see folks confused about how to manually extract and install things like Gapps that normally you would install via CWR on a EMMC install...

With this in mind I took one of the 3.0.1.0 uRecRam images and extracted the files from the Ramdisk to poke around and see if it might not be fairly easy to repackage CWR for local use on the SDcard installs... I noticed it seems the important file is /etc/recovery.fstab...

# mount point fstype device [device2] [fstype2]

/boot vfat /dev/block/mmcblk0p1

/system ext4 /dev/block/mmcblk0p5 NULL ext3

/data ext4 /dev/block/mmcblk0p6 NULL ext3

/cache ext4 /dev/block/mmcblk0p7 NULL ext3

/emmc vfat /dev/block/mmcblk0p8

/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3

That would seem to control what FS devices/partitions CWR would use to install things to...

Am I correct? Is this really only a case of needing to edit this file and change the appropriate mmcblk0p? devices to point to mmcblk1p? and repackage the uRecRam, or am I missing something that might be obvious to someone actually understanding the full working of CWR?

I'm just thinking it could be useful to have 2 uRecRams (.emmc and .sdcard) to choose from when manually installing CWR on an SDcard and this might be something I could pull off... as lack of real time and stable build environments has kept me from things that might be more interesting and useful but maybe something like this could help some folks...
[Nook Color Android Development] fwdixon:
EXT4 support?

Ok I'm a bit confuddles. Supposedly this CWR has support for both ext2/3 and ext4. Does that mean it can only backup/restore both FS or that it can format to either FS. The reason I ask this is that I tried to use this CWR to format my eMMC for CM7 and could not get it to boot, however, installing the ext3 HC preview, Froyo, and Stock all worked fine.

I tried with both kernels as well. Suggestions?

EDIt: Seems to be a Kernel-related (the regular one, not the uRecImage) issue. Reverted back to CWR 3.0.0.6 just in case and flashed an updated CM7 Kernel and once the battery charged back up it booted fine. Will play around with 3.0.1.0 again later.
[Nook Color Android Development] evilmerlin:
I'm still quite confuse about the implementation of CWM and Rom Manager in the various roms.

I've updated CWM in Rom Manager to the 3.0.1.0 and it says that's the latest version. However, when I try to reboot into Recovery via the reboot menu, it simply reboots into Android instead of the recovery menu.

So can I still use the "Install Rom from SD Card" function to flash a new rom? Specially, I'm trying to update Phiremod without having to use a bootable SD card.
[Nook Color Android Development] kronium:
Did you try "Reboot into Recovery" from Rom Manager?
[Nook Color Android Development] sd_matto:
I get the same issue as you do with respect to power/home ('n') button combo, as well as power button and "reboot/recovery" not rebooting me into recovery. But, when I go into ROM Manager, and click reboot into recovery, my system reboots into recovery.

Is this failure to enter recovery other than through ROM Manager a glitch that can/will be fixed? Or, did I bork my nook with all of the flash iterations I have done (in which case, is there a method to unbork it)?
[Nook Color Android Development] evilmerlin:
Yup, tried that and it still boots into Android rather than recovery.
[Nook Color Android Development] vlucchetti:
I can boot into recovery from ROM mgr with the latest build, but I can't backup my custom nookie froyo .68. Starts fine, then tells me it cannot find /system
[Nook Color Android Development] faceman66:
Just for giggles, try going into ROM Manager and re-Flashing Recovery, except this time select device 'Nook Color (old)' and see if you can perform a backup. If you can, awesome. If you can't just go and reflash again and reselect the regular 'Nook Color' device.
[Nook Color Android Development] fwdixon:
Having the same issue
[Nook Color Android Development] vlucchetti:
reflashed, after upgrade to 3014, did nook color, hit backup, and voila! Many thanks!
[Nook Color Android Development] faceman66:
Just to be clear, you upgraded ROM Manager to 3014, 'Flashed CWR Recovery' using the device 'Nook Color' and backup worked fine.

Also, what rom are you using?
[Nook Color Android Development] ADude:
Is there any way to see your installed-version-number of CWR without booting into Recovery ?
[Nook Color Android Development] em2drvr03:
hey my nook is stuck in clockwork and its like froze....how do i fix this!!!???

Edit: Nvm i got it out
[Nook Color Android Development] vlucchetti:
last one I loaded was the framework for nookie froyo 3-24-11
[Nook Color Android Development] GrillMouster:
Noob here. This thread has me confused. I'd appreciate a little help.

I've been running Nookie Froyo for a while. I had CWM 3.0.0.5 and everything worked fine. I was able to flash OC ROM kernels, patches, etc., and create backups and restore backups using CWM on the device.

I just flashed CM7 to internal memory using the SD in the CM7 instructions. I believe that the version of CWM on that card was 3.0.0.6. I guess that was an unofficial build, because CM7 needs ext4 support. My NC still had CWM 3.0.0.5 on internal after installing CM7. I flashed 3.0.1.0 through ROMManager, but according to this thread, that's not enough if I ever want to restore my old ext3 ROMs from internal recovery.

Do I have to continue using CWM on SD to work with my CM7, or can I use the internal 3.0.1.0? The OP and other posts keep saying that it needs to be installed manually because ROMManager (I have the premium version) won't install the necessary recovery kernel. However, also in the OP is a zip file. I want to make sure: Does that zip file flash the updated CWM 3.0.1.0 and the updated recovery kernel? It seems like the answer is yes, but "manual install" is mentioned so frequently throughout the thread, and I've come across several threads where the OP still has old, incorrect info, so I just want to be safe.

Thanks!
[Nook Color Android Development] millbean:
cant boot past clockwork .when i do it gets hung on the n logo
[Nook Color Android Development] jasoncarothers:
I am new to XDA and I am so grateful that you guys are doing this kind of stuff. I am learning so much. however because I am a noob, I have some questions that I am wondering if you would help me with.

I have adb setup so that when I issue " adb devices" it shows my device serial number. so as far as I know I have ADB setup correctly. I also have gone to the adb setup link and made sure I have the .android/adb_usb.ini installed into the correct location.

What I have done

installed rom manager 3.0.1.4

it updated and installed CWM3.0.0.5

I tried to install CWM3.0.1 via zip but nothing seems to change. when I boot into recovery it still says 3.0.0.5

so now I am trying to install using the manual way.

1. I have a mytouch4g, should I be trying to put CWM3.0.1 on it? I have searched all over the mytough4g forums and everyone directs us to here.

2. When I issue the "adb shell busybox mount / -o rw,remount" command I get the msg "mount: mounting /o on rw,remount failed: No such file or directory"

and from there I cant create the /boot directory to push the update into the right directory. so I am having a problem mounting and changing the drive to read/write. has anyone else had this problem?

I apologize for the noob question. and thanks in advance
[Nook Color Android Development] quinxy:
I'm running CM7 on SD and have the latest CWM installed, but I have yet to see CWM work properly. It crashes the device if I attempt to backup current ROM, and only very very very rarely goes into CWM recovery on boot. is this because I'm booting on SD card?
[Nook Color Android Development] ADude:
CWM 3.0.1.0 works fine for me, both from SD card or from eMMC.

I do not use "ROM Manager" for anything (other than "fix permissions" when seemed needed).
[Nook Color Android Development] quinxy:
I'm confused, when you talk of ROM Manager you mean the app running inside the OS rather than the console portion running pre-OS. I've tried about everything to enter CWM Recovery, how do you do it? Most of the Nook instructions seem to say hold power and N to boot from off for 6 seconds. Others I read said power + N + volume up for 6 seconds. I've tried those and others and maybe 1 in 20 times I seem to end up there... or it seems to go there on its own for no reason. What works for you?

Quinxy
[Nook Color Android Development] newellj79:
Hold down the n and power buttons. Keep pressed untill device powers off after "touch the..." screen. Release buttons. Press and hold power button untilled screen flashes signaling it has been turned on. Release button immediately and it should boot into recovery. Atleast this is how I get there aside from simply selecting boot into recovery from rom manager.
[Nook Color Android Development] quinxy:
Great, thanks! That would explain why I rarely got there, I didn't realize you had to hold it down long enough to power off, that's where I was going wrong! (Getting there from the app never worked for me.)
[Nook Color Android Development] bradputt:
wow, this is confusing.

how do you get into CWM in the powered off state?

press and hold the N + power button until the "touch the...." screen?

do we release both the buttons or hold the N button but release the power button?
[Nook Color Android Development] newellj79:
Typo... release buttons. This really isn't that complicated. Hold down power and n until it turns on and shuts off, let go. Press power to turn on.
[Nook Color Android Development] arcmanov:
Exactly how do I create a bootable SD-card with this latest version?

I have 3.0.0.5 on my NC at present, and I would like to upgrade it.

For some reason, I'm getting a 'couldn't mount SD-card' message when trying to use the zip file provided in the 1st post.
[Nook Color Android Development] bradputt:
ok i get it, i hold both the buttons untill "touch the future of reading" then let go everything.... and it boots to CWM....

thanks...
[Nook Color Android Development] ADude:
Because that is an important thing, it is buried in the fourth post of another thread:

http://xdaforums.com/showpost.php?p=11999569&postcount=4

Be sure to check this download (and all others) using the MD5 files. (if you don't have a checker, go to getmd5checker.com )

In case you don't know what to do with them, put your uSD card in a USB reader in your PC, and burn the image of correct size for your card, using Win32DiskImager (which you can get from softpedia.org).
[Nook Color Android Development] kc_hubbard:
Want to make sure I get this right

OK, let me start by saying I have read the root, recovery/cwm threads here pretty extensively and I think I understand. Let me also say that I'm NOT new to flashing android ROMs, I'm virtually a flash-a-holic on my EVO.

So, I want to get my wife's NC rooted w/ CWM recovery so that I can flash a new ROM to it. In a nutshell, here's what I think I have to do...anyone, please, let me know what I have wrong or have missed.

1) Root the NC using Auto-Nooter 3.0.0 (NC is on 1.1)

2) Install CWM Recovery (likely the manual method mentioned in this thread)

3) Install RomManager, as from what I can tell this is the only method to boot into CWM Recovery

4) Use CWM Recovery to flash new ROM (w/ the required wipes etc)

I know I've left some detail out, but do I have the right general idea here? Any help I can get is appreciated.
[Nook Color Android Development] quinxy:
Hmm, this definitely does NOT work on my Nook Color with verygreen's SD install of CM7. :(

The Rom Manager shows CWM installed, the latest version (even tried re-installing it), but it won't go into it following these instructions. (And as I mentioned before choosing the reboot to recovery does nothing, it just reboots.)

Anyone have any other ideas? Not sure how my setup could be magically different from everyone else's.

^ Quinxy
[Nook Color Android Development] ADude:
Post instead to verygreen's SD install of CM7 thread.
[Nook Color Android Development] GrillMouster:
In the first post of the official CWM 3.0.1.0 thread there's a zip file just below the manual install instructions. Flash that zip using whatever ext4-compatible version of CWM on sd that you used to flash CM7. Now you'll have CWM 3.0.1.0 and the recovery kernel internally (updating to CWM 3.0.1.0 from ROM Manager does not update the recovery kernel).

To boot to internal CWM from a powered-down Nook Color, hold down the power + n button. When the "touch the future of reading" screen appears, continue to hold down the n button for an additional two or three seconds. Wait, and it should boot into CWM 3.0.1.0.
[Nook Color Android Development] newellj79:
Sorry. Works fine on my emmc cm7.