yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] DizzyDen:
You would be able to do what you want with ADB Wireless and a laptop... OR in a terminal window on the nook....

My solution would be to create folder named boot at root of your system (either eMMC or sdcard) download the nightly to laptop... take the laptop to the car...

adb remount

if eMMC: adb shell mount /dev/block/mmcblk0p1 /boot

if uSD: adb shell mount /dev/block/mmcblk1p1 /sdcard/boot

adb push update.zip /boot (or /sdcard/boot)

adb reboot recovery
[Nook Color Android Development] Dj-Gutz:
I'm new at this so forgive me if I need a little more explaining :)

doesn't those commands only push ( copy ) the update.zip to the device ( which I can transfer manually with the sd card or even dropbox )

and reboot the device to recovery ( which I can use the power menu or rom manager to do that ) ?

Am I missing something here?

I still don't know how to install the zip without using cwm menu and navigate with the hardware keys

Also is there anyway to connect with ADB using my HD2 ( with android ) ?

And how can I achieve wireless ADB when in recovery? I only know the app ADBWireless

Great help guys :) this and the HD2 community here are absolutely the best :) THANKS!
[Nook Color Android Development] DigitalMD:
I sort of undertand what you are trying to achieve, I think. ROM manager is generally realible for flashing and backup / restore, but with any method you can run into situations (as I did recently with build 136) where something goes wrong and things get totally hosed such as corrupted boot file or bad partitions. When that happens you cannot get into recorvery or ADB and it necessitates access to the SD card for an emergency boot. By the way, ROM manager actually uses CW recovery to perform backup, restore, flash etc. It just invokes scripts for you rather than your manual control.
[Nook Color Android Development] Dj-Gutz:
well I got the impression its not reliable , If it is its a whole different story :)

I don't mind that if its get screwed I'll take it out of the car mount and flash it using recovery or use sd card emergency boot

I just don't want it to happen every time I update , which will only happen on a big update not every nightly :)

Can anyone else confirm using ROM Manager works good for updating cm7 nightlies?
[Nook Color Android Development] newellj79:
You can totally do everything u r looking to do with adb wireless as dizzy suggested. If u need more help with commands Ill check the thread after work.
[Nook Color Android Development] Dj-Gutz:
thanks newellj79

It would be great if you can take a look and answer my questions in your free time :)
[Nook Color Android Development] pmilford:
Hi,

I haven't tried updating again for quite some time (I had a long vacation

that I needed a reliable NC)

When I tried to backup like below, I had the same problems, starting with

CM7 from 6/19 (107?) [See my long post quoted below]

This time after booting into CWM on SD, I let the backup finish, then removed

the uSD and put back normal uSD and rebooted into CM7 fine.

I'll try and install CM7/146 now.

Steps: (With ROMManager)

Download GAPPS 20110613 (by itself) don't install

Download CM7 Nightly 146. (by itself) don't install

Used power button to power off then power+home to boot into

boot menu. Switched to recovery image boot. Then tried to boot

into recovery - system hangs.

Reboot with uSD CWM - system reboots fine into CM7.

Reinstall CWM 3.2.0.1 with ROMManager premium 4.3.2.4

Can't boot into CWM with u-boot still.

Use PC to d/l CM7 146 to spare uSD with CWM.

Boot into uSD CWM 3.0.2.8 and install CM7/146 & GAPPS 0613.

Wipe cache and Dalvik cache.

Remove CWM uSD and put back normal uSD and reboot from power switch.

CM7/146 boots!

Tried a few things, they work.

Use power button to turn off and then power to turn back on, system boots

ok and still works! Don't have time to try CWM/ROMManager again.

--> Hope this helps someone with similar issues!

--> Hope this lets someone solve the problem too!

Peter
[Nook Color Android Development] mysql2779:
Hey bro , my ROM manager shown 3.0.0.5 as the latest CWM Recovery. I saw your reply on 1st page. U said provide link. But I didnt see any link in #1. Please help. Thanks.
[Nook Color Android Development] RegLinUsr:
It is linked in Jimbo67's post: http://xdaforums.com/showpost.php?p=15951628&postcount=522
[Nook Color Android Development] Gtech:
Hi all,

Sorry if I'm being thick, but I cannot find a link for the latest CWM file, I want to put this on my Hannspad, which is currently running version 2.5.1.1

Many thanks

Gtech
[Nook Color Android Development] patruns:
Try here: http://www.multiupload.com/0DLC9QATOW

Note, this is being used for the Nook Color. I do not know if other devices use a different file, but you are in the NC forums so.............
[Nook Color Android Development] toxicstone:
Hi, i gut bad luck and need CWM to save photo game cache etc, but the version i use doesnt support backup to SD Card.

I have gt-i9100_clockworkmod-recovery_4.0.0.2 , dunno if its 4.0.02.

Your page says 3.2.0.1 and iv read about 5.0.2.7 so im little confused?

As of now, i just need the ability to backup to SD Card so i dont lose everything on the damn phone.

My Thread is here (unanswerd) http://xdaforums.com/showthread.php?t=1391040
[Nook Color Android Development] patruns:
This is a Nook Color forum. Is that what you have?
[Nook Color Android Development] toxicstone:
Im really sorry, always look so i dont get to the wrong section, but have been so busy with trying to fix my problem all day.

Will try to find the answer somehow.

Sorry for the OT.
[Nook Color Android Development] Midnitte:
Trying to flash CWM recovery from CWM on my SD and it doesn't seem to be installing it :(, any ideas? :o
[Nook Color Android Development] patruns:
More info please.... no clue what you mean by flash CWM from CWM....
[Nook Color Android Development] Midnitte:
ah oops, trying to flash CWM Recovery (from SD card) from ROM manager, says successful but I still have the default recovery on my SD card (I think perhaps it installed to emmc?)
[Nook Color Android Development] patruns:
ROM manager works for eMMC, not SD........
[Nook Color Android Development] ssconceptz:
Please help me understand the usefulness of a post about CWM that doesn't have any links to the CWM files?

Can someone please link them?
[Nook Color Android Development] patruns:
What exactly are you looking for?
[Nook Color Android Development] ssconceptz:
Sorry I found them already thanks. Just think the link to where to download them in the OP would be awesome. Not everyone has access to Rom Manager.
[Nook Color Android Development] Skorpion56:
Without having already flashed CWM this thread/post doesnt make it very clear. Any pointers as what to do first with a fresh NC1.4 straight outta the box. Thanks..
[Nook Color Android Development] rnclock:
If you are talking about rooting a new NC, then you need to read the other threads based on what type of method/rom you want to use. I personally use CM7 on eMMC (installed to internal system on NC with no SD card required for boot). Here is the start thread on that: http://xdaforums.com/showthread.php?t=1030227

But make sure to look at the different methods to ensure you are getting what you want/expect from rooting the NC.
[Nook Color Android Development] Skorpion56:
Thank a bunch! For someone coming on here with a NC, the steps involved are about the most unorganized ive ever seen on XDA! And yes, I do want to run CM7 (whichever can get me running a basic Android setup w/ Amazon apps and market) that is stable and i can update without doing major surgery... Ive been rooting/flashing phones for years and fairly proficient.
[Nook Color Android Development] IVIatticus:
This guy brought me his Nook Color that he tried to put CM7 on, but it wouldn't work. I spent a couple hours trying to get it to work. Turns out, he didn't have the updated CWM, I couldn't even get the thing back to stock. I finally figured out how to make an updated bootable SD card with 3.2.0.1 by searching all over hell, but it really sucks that the only instructions in here say go to ROM manager and install from there. He claims that his SD card worked fine to install CM7 on another nook, but I have my doubts.

These are the instructions that I followed to make a new SD card.

Once I did that, I had it up and running in about 5 minutes. I wanted to do it from the start, but he insisted. I knew better than to listen to him.
[Nook Color Android Development] s22lane:
Agree completely...info with no link??????
[Nook Color Android Development] nemith:
Short answer, no.

Long answer: Yes, but you have to use adb to manually mount /dev/block/mmcblk0p8 (/media) as /sdcard. You can then use adb push to push the image to the sdcard. It's not for your typical noob though.
[Nook Color Android Development] painter_:
Wow, it was really nice to flash without swapping SD cards!
[Nook Color Android Development] openallnight:
It worked. backing up now. Got stuck on first reboot at Android .. but it auto corrected and then booted up fine.
[Nook Color Android Development] TJNooker:
Market issue...

After updating CWM, my market would no longer download apps, purchased or free. I flashed the old CWM recovery 3.0.0.5 and cleared both caches and everything seems to be working again.
[Nook Color Android Development] Hilbe:
Had a similar issue. Flashed CM7-8 and gapps multiple times using the new recovery and couldn't get my gapps to work. I ended up busting out my MicroSD to flash again and then it worked fine. Not sure what is going on with 3.0.0.6 on eMMC.
[Nook Color Android Development] Homer_S_xda:
FYI, I think the kernel in the first post is for emmc. If you want this on SDcard, you will need a CM7 compatible SDcard kernel.

Homer
[Nook Color Android Development] eNkrypt:
Sorry I don't know if this question/problem has already been posted.

However, I only see RomManager 3.0.0.5 in the Market :\
[Nook Color Android Development] hacku:
Thanks for this!

The new update from ROM Manager wasn't able to mount /system so I couldn't create a backup.

After doing the manual install this works perfect now.

Thanks again!
[Nook Color Android Development] anurbanlegend:
Not sure what i'm doing wrong, I installed using manual method but can't seem to get this thing to boot into recovery... either from adb or rom manager. I'm running CM7. Any tips?
[Nook Color Android Development] nemith:
Do you really think this is related?! :)

The Market issues are separate and I am still looking into it. In the mean time people... just by installing CWM is not going to break anything.....
[Nook Color Android Development] nemith:
Use the power+n approach.
[Nook Color Android Development] nemith:
What?!

There is nothing special about the kernel, the ramdisk or anything.

You guys do have a creative imagination though.
[Nook Color Android Development] nemith:
Meaning you couldn't install gapps? or Market wasn't working.

Please be as descriptive as possible.
[Nook Color Android Development] nemith:
For compatibility we always format as ext3. When you mount it with CM7 it will mount as ext4.

This means there are no extents or large_file support, but right now that is acceptable and is how the G2, MT4G, and Incredible handle it for CM7 as well.
[Nook Color Android Development] anurbanlegend:
I tried the power+n. Screen flashes a couple times then boots right into CM7. Is my recovery messed up?
[Nook Color Android Development] adma84:
same here, I go straight to recovery
[Nook Color Android Development] nemith:
That is possible. Try manually copying the files over again

Make sure your md5 sums are correct

Make sure you copy the names to /boot correctly (uRecRam and uRecImg)

Make sure you umount before reboot. vfat has a tendency to not write anything from the buffer until it needs to. Umounting it will force this.
[Nook Color Android Development] Hilbe:
It installed the gapps in the recovery and said it completed, but when I booted back into CM7 they were all broken/nonfunctional. This was an upgrade from a previous CM7 install where they were all working fine. I did it 3 or 4 times before I gave up and went back to the CWR recovery bootable SD which installed the gapps.
[Nook Color Android Development] nemith:
It's not CWM at all. Either your gapps update is not working or you need to clear cache or even wipe data.

If for some reason you are still convenced it is CWM. Attach a recovery.log to your next reply.
[Nook Color Android Development] openallnight:
This worked fine form me.. and I did create a backup from CM7. I have backups from previous CWR on the same card. In case I want to wipe out my sd card, Do you know if these backups can be copied to my pc and back? I do have a different bootable SD card with the latest CWR.
[Nook Color Android Development] newellj79:
Power+n is supposed to take u to recovery.
[Nook Color Android Development] newellj79:
Yes they can b copied back and forth.
[Nook Color Android Development] nemith:
The backups should be completely compatible and you can move them to your pc and back.
[Nook Color Android Development] adma84:
right, I meant to say that when I start the nook, it just goes straight into CWR
[Nook Color Android Development] Homer_S_xda:
Nevermind.
[Nook Color Android Development] Homer_S_xda:
Glad I could help.

Any tips on how to actually backup/restore the stock OS? Starting with an unregistered NC that boots to the OOB experience. I have this version booting from SDcard, pop it in, do a full backup. Then I've tried restoring it a variety of ways and it always gets stuck at the n screen.

Homer
[Nook Color Android Development] nemith:
Make sure you wipe data and cache when you do this!

I will try flashing one of the stock roms to see if it works.. it should.
[Nook Color Android Development] Hilbe:
Starting to think it is the result of a borked CWM flash from ROM Manager. I can't backup /system as others have mentioned.
[Nook Color Android Development] RileyGrant:
Just so everyone knows, if you are using thecubed's bootable version of 3.0.0.6 the format data does not work. I wiped data and system twice, flashed a new nightly and wala, I boot up and all of my apps and settings are still there.
[Nook Color Android Development] lafester:
For kicks I tried to restore a 2.1 backup and it failed to boot past the 'n' screen as well.

When I booted back into recovery I somehow had 3.0.0.5 loaded.

Went ahead and restored my current 2.3 backup and everything works even though it shouldn't using that recovery.

maybe I still need to read up on how these recoveries are working.
[Nook Color Android Development] nemith:
Recovery lives in /boot so when you do a restore it will restore an old recovery. Not ideal, but thats the way it works today.

What zip are using to try to go back to stock so i can test on my NC.
[Nook Color Android Development] lafester:
Yeah that isn't ideal lol. but it is what it is :)

I was just using a backup I had made before I tried out the first cwr flashable froyo build.

I believe I had the 1.1 update rom loaded at the time.
[Nook Color Android Development] openallnight:
I know I can try this out but can I restore back to Eclaire/Froyo backup using the latest CWR? based on what I understand so far I should be able to after reformatting system/data and cache right?

Or will that at any point wipe out boot so its best to do from a bootable sd? I have an eclaire and Froyo backup created using older CWR and a CM7 backup using the newer one.

thought its safer to ask before i mess things up :)

thanks!
[Nook Color Android Development] faceman66:
FYI - To anyone using the new ROM Manager (v3.0.1.0)

I only bring this up because some folks over at another forum I read had some issues with the app and I haven't seen this written out anywhere so I am throwing it up here:

When you install ROM Manager (v3.0.1.0) and select the "Flash ClockworkMod Recovery" option you will be presented with a list of devices. (For most of us Nook Color users this is new, we used to only have one option) There are two (2) nook color options: 1. "Nook Color (old)" and 2. "Nook Color"; what isn't clear is what the difference is between the two.

1. Nook Color (old) - flashes CWR v3.0.0.5 - which is used for all ext3 based ROMs (including but not limited to all stock B&N, Froyo, HC, etc)

2. Nook Color - flashes CWR v3.0.0.6 - which is used for all ext4 based ROMs (at this point anything CM7 based, including some phiremod builds)

Flashing the wrong recovery for your device will result in all sorts of various issues and problems. However, using a 'Remove CWR' zip off a bootable SD will always fix the issue. :) Also, it seems that most of the problems don't prevent booting so you can always load up ROM Manager and flash a new recovery over the wrong one.

Hope this helps some folks, as doing this resolved my earlier issue of my ROM manager still showing v3.0.0.5 as the latest even though it wasn't.
[Nook Color Android Development] nemith:
WRONG!

The OFFICIAL v3.0.0.6 (found in rom manager) supports both ext3/ext4. That is why we pushed koush to official release it. Please use it for both!

The confusion comes from previous posts of unofficial 3.0.0.6 builds that were ext4 only. That has been fixed officially in-between the builds.

This was also explained in the first post!

This different version of CWM for different uses NEEDS TO STOP now.
[Nook Color Android Development] Syco54645:
Does this fix the freezing when clearing dalvik cache?
[Nook Color Android Development] nemith:
Not yet. I still don't know what is up with that.
[Nook Color Android Development] Casao:
Attempting the manual instructions in the OP are not working for me under the CM7n8, any ideas why? I'm not able to boot into recovery.

I started without a recovery installed, so it is that? Is it possible to install via Rom Manager under CM7? I ask because I've had a lot of issues with my rom getting wiped and having to start from scratch, so I'd like to confirm it should work before I start messing with things.
[Nook Color Android Development] Hilbe:
I flashed CWM 3.0.0.6 from ROM Manager "Nook Color" option. CWM then failed to backup /system, and failed to install gapps. I did the manual install on the first post to correct these issues. So if you're missing market (gapps), do a manual CWM install!
[Nook Color Android Development] adma84:
Didn't work for me either, I could only boot into recovery
[Nook Color Android Development] adma84:
And you have no issues now?

**EDIT**

The manual method worked for me, however, I can't reboot into recovery from the shutdown menu. It's odd, because ROM Manager can reboot into recovery.
[Nook Color Android Development] TJNooker:
I do think this is related. Let me explain.

I have been running Eclair on my Nook v1.1.0 with 1.1GHz OC for a while. I've also been using CWM 3.0.0.5 for a while, too. I've never had any market issues, whatsoever. I've flashed different versions of Dalingrin's eclair kernels using CWM recovery without issue, minus one. Without fail, the recovery console would freeze after clearing Dalvik cache on the first attempt. After rebooting and reclearing both caches, the recovery console would no longer freeze and I could continue with flashing the kernel.

The problems with the market appeared after updating RomManager to 3.0.1.0 and updating CWM to 3.0.0.6. After manually installing the new CWM, I tried to flash Dalingrin's updated OC kernel. As usual, CWM froze after clearing Dalvik cache so I rebooted and started over. It froze again and again and again for a total of 8 times before I quit.

I flashed the OC kernel anyway and everything seemed to be fine, until I tried to download some market apps. I couldn't download paid or free apps at all. The download would start and then quit after a few seconds. I cleared cache and data of every google app and service I could find to resolve the issue, but no luck.

Desperate, I went into RomManager and clicked on "All ClockworkMod Recoveries" and flashed CWM Recovery 3.0.0.5. I rebooted and now the market works just like it used to. I did not restore my ROM, I just flashed 3.0.0.5. That's what makes me think it can't be RomManager or the OC Kernel. What do you think?
[Nook Color Android Development] adma84:
@nemith does flashing recovery from Rom Manager normally replace the kernel? Or, am I just misunderstanding your point? Thanks :)
[Nook Color Android Development] faceman66:
I stand corrected, but not in full understanding yet then. What is the difference between the two devices listed in the options when one tries to flash recovery? If there is just one version for all uses, why the two devices at all?

Edit:

Also, which device SHOULD we be using?

Edit Again:

Just looked back at OP to see if I had missed something and see that there was an error of some sorts, I will wait for the update before speculating or spouting off more. Thanks.
[Nook Color Android Development] lafester:
In case anyone missed it :)

Thanks Nemith!
[Nook Color Android Development] Dbl_Tap:
I'm doing the manual fix using adb and when I get to the line:

adb push kernel /boot/uRecImg

I get "can not stat 'kernel' :no such file or directory"

what did I do wrong? all the previous lines worked in adb once I corrected the typo in busybox a few lines up.

and yes I downloaded the kernel file with no extension and it is in the same folder as the img file that pushed no problem.
[Nook Color Android Development] davidukfl:
i used rom manager to flash the recovery, and then just manually did the kernel.

I'm assuming it worked fine because i was able to do a full backup and also able to flash the overclock kernel from CWR

I haven't tried to restore a backup yet though
[Nook Color Android Development] adma84:
can you reboot into recovery from the shutdown menu in CM7?
[Nook Color Android Development] jayhammy:
I downloaded the latest ROM Manager from the Market and flashed the latest recovery to 3.0.0.6 within the app. I then chose "backup ROM." It rebooted into recovery and immediately began to do a Nandroid (actually, this is the first time that actually worked).

Here's my question: From within CWM, it says I have version 3.0.0.5 yet I updated to 3.0.0.6 from with ROM Manager. What gives? I'm running CWM on the SD card.
[Nook Color Android Development] adma84:
Didn't you just answer yourself? You are running CWM from an SD card and you also flashed CWR into EMMC? That's probably why you show two versions
[Nook Color Android Development] jayhammy:
LOL. Did I actually answer it myself? Wasn't sure. So how do I just use the CWR in EMMC? I can't seem to bypass the SD card version.
[Nook Color Android Development] adma84:
Take your SDCARD out of the NC if it has CWR on it. Then you will stop using the SDCARD CWR version. You can just format it and use it as an sdcard for all of your backup data

Then, if you flashed CWR correctly to EMMC you can go into rom manager and select reboot into recovery. Or do backups from Rom Manager.

note: I currently can not reboot into recovery from the shutdown menu in gingerbread (which is where I normally enter recovery), which is unusual, considering I can do it from RM.
[Nook Color Android Development] jayhammy:
Strange. I took out the sd card, rebooted into recovery via ROM manager, but it never went into recovery. Went straight to the OS. So then I went back into ROM manager and it tells me I need to have an sd card installed to use it.
[Nook Color Android Development] adma84:
you do need an sdcard, but it can not be formatted as a boot image (CWR). My guess is that you didn't really install CWR to EMMC
[Nook Color Android Development] jayhammy:
So would you say removing the CWR boot image on the sd card would be a good try and then flashing CWM in Rom manager again? ANy other ideas?

Thanks so far for the help.
[Nook Color Android Development] adma84:
backup any nandroids you have on the card to your computer HD. Flash the sd card so that you can still write backups to it. Follow the manual method listed in the OP, or wait until Koush fixes the version that is in Rom manager. However I would not flash CWR from ROM Manager yet. Hopefully that version will be fixed soon.
[Nook Color Android Development] davidukfl:
I'm on stock ROM