yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] DizzyDen:
It is CWM 3.0.2.8 not CWR... CWM is android front end... the latest CWR is still 3.0.1.0
[Nook Color Android Development] lazinase:
You kidding me...it's 3.0.2.8
[Nook Color Android Development] ylixir:
wut?

cwm=cwr
[Nook Color Android Development] xblue95:
Please guys, any response would be helpful. I'm I on track with my thinking?
[Nook Color Android Development] lazinase:
To me, a CWR SD card is really helpful. Here was my situation: I used rom manager to download CM7.0.2, installed it, tried to update the kernel immediately after the reboot by using kernel manager. Then the nightmare happened that something went wrong and my Nook wouldn' t boot up after the "ANDROID" screen. Only a "-" on top left corner.

Then i powered down my nook, put the CM7.0.2 and the kernel zip into my cwr SD card and reinstalled the rom followed by kernel. My Nook came alive again! No data loss!

See? Isn't it helpful?
[Nook Color Android Development] xblue95:
Thanks lazinase, I'm glad you got it back up and running! I wasn't disputing it's usefulness, was just wondering if it would be useful for reverting back to 1.1 if my NC got zapper by the 1.2 OTA update? I'd really like to turn WIFI back on, but don't want to risk getting the OTA update until they get a 1.2 AutoNooter. I've backed up my current state with CWM (STOCK ROM using ZEAM LAUNCHER), seems like I could put that back-up on the CWM-SD and then revert back to 1.1 if i got zapped with 1.2 OTA update. Also I'm not sure if this CWM-SD will work with STOCK NC Android???
[Nook Color Android Development] DizzyDen:
I'm sorry if I misspoke regarding 3.0.2.8... I did not see links to download a newer version in the Official thread... Have found it now... so give me some time.... I will GLADLY update the images I graciously provided.
[Nook Color Android Development] RegLinUsr:
The files "uRecImg" and "uRecRam" do not exist in the recovery-clockwork-3.0.2.8-encore.zip file. There seems to be no /boot directory in that file which is where the files are located in the v3.0.1.0 file. I've created the v3.0.1.0 bootable SD but not sure how to bump it to v3.0.2.8 with what is provided.
[Nook Color Android Development] Colchiro:
Same here. I think it downloads the latest recovery image.
[Nook Color Android Development] DizzyDen:
It looks like 3.0.2.8 updates some scripts and tools... if it can be ported to the SD version... I will.... looking into it now.
[Nook Color Android Development] cmstlist:
You're right, it's structured completely differently. Updated the top post. Made a 3.0.2.8 SD that boots. Don't know if it performs all tasks successfully so please let me know if any issues. I will update the top post if anyone creates SD img files accordingly.
[Nook Color Android Development] Colchiro:
Rom Manager stores recovery images in /sdcard/clockworkmod/download/mirrorbrain.cyanogenmod.com/cm/recoveries
[Nook Color Android Development] DizzyDen:
NOTE:

3.0.2.8 uSD images.

All credit goes to OP... all I did is updated the original uSD files with OP's results....

I renamed them to *.3.0.2.8.img to distinguish which version of CWR image and ramdisk files are being utilized. I also compressed to rar to distinguish these are not CWR flashable zip files.

M5 Checksums:

RAR's:

128mb_clockwork-3.0.2.8.rar
2BCDC24318A6FF894092F194D120E42B

1gb_clockwork-3.0.2.8.rar
0154139BF2C89D8795DD9DEE07DE2031

2gb_clockwork-3.0.2.8.rar
A62938F0C6255D212DECC14D6D0F117D

4gb_clockwork-3.0.2.8.rar
8CEF6CA12D0FA55F581E38698B69D501

8gb_clockwork-3.0.2.8.rar
00DB4D2CF035127FC5934B49C6B3A091

IMG's:

128mb_clockwork-3.0.2.8.img
E0FD9FB313A9598FBB747C698F4985EF

1gb_clockwork-3.0.2.8.img
28734B6F051F1A600FA92C689F5BE27F

2gb_clockwork-3.0.2.8.img
07DAEC01FEB7535C6438F563134428CC

4gb_clockwork-3.0.2.8.img
E42A4B696A728E14399015F508E0A849

8gb_clockwork-3.0.2.8.img
5377914A5C474FE8D2B9DD1302EF9DE2

GZ's (only available on RapidShare due to file type):

128mb_clockwork-3.0.1.0.img.gz
7214DF7FD5BAA6F803D499F69D792A75

1gb_clockwork-3.0.1.0.img.gz
26ABB66BFEEA76C8AD0ABBA97EDC964E

2gb_clockwork-3.0.1.0.img.gz
3D8F05F0F6FF39271F5F82DBCC4403A3

4gb_clockwork-3.0.1.0.img.gz
8A13A55E045F23F3D3BE5354EDEC26B5

8gb_clockwork-3.0.1.0.img.gz
48D8CB4B93E57FC121C8082CB23FD98F

RapidShare mirrors (folder includes .gz and .img files)

NOTE: there's also a 16 GB version on RS... just can't upload that large file here.
[Nook Color Android Development] xKLoWNx:
Beautiful Instructions, works perfectly!! Thanks!!!!
[Nook Color Android Development] emtownsend:
Is the 16GB uploaded yet?

Thanks!!
[Nook Color Android Development] fpga_guy:
Just clarify, I can decompress these files to a img file, use win image to image the files to an SD card and voila - I have a bootable 3.0.2.8 CWM sd card. Correct?

If so, many, many thank you!
[Nook Color Android Development] DizzyDen:
Yes, extract the file you downloaded to an img file... use winimage or win32 disk imager to write to uSD... you have a 3.0.2.8 bootable SD.

emtownsend: the 16GB images were uploaded the same day as the others... it may not list them in with the others because of the way rapidshare and rapiduploader sorts them... the 8 and 16 are a little lower on the list... due to other uploads finishing before them while they were all uploading.

As for uploading them here... the file attachment exceeds the maximum attachment for xda... have to get 16GB's from my rapidshare.

The note about uploading hasn't been removed yet because i am also uploading the raw img files to RS... some have expressed difficulty extracting the rar and/or gz files.
[Nook Color Android Development] n8w:
I'm sorry, I'm sure this has been explained somewhere, but do I dl the file size that matches the card I will be using?
[Nook Color Android Development] robot8:
Yes, that would be correct.
[Nook Color Android Development] n8w:
Thanks for the response. Silly me though, I already in fact had a 2gb version on a 4gb card...so I guess that still doesn't totally make sense to me. I figure it's good to have extra room, but why would one want a bigger file then what it has to be?
[Nook Color Android Development] DizzyDen:
Because it leaves room for backups of system... all the ROMs and kernels you want to save on it.... in fact... you can run CWR on as small as 128 KB uSD... but, if you are running the 2GB version on a 4GB card... the other 2GB is being wasted and unusable... by putting the 4GB version on a 4GB card... you can at least use the whole thing.
[Nook Color Android Development] fr0zenblood75:
Can i then re format and use it as a normal sd later on?
[Nook Color Android Development] DizzyDen:
yes you can
[Nook Color Android Development] Colchiro:
This app might help: http://en.kioskea.net/download/download-127-hp-usb-disk-storage-format-tool
[Nook Color Android Development] jdyson209:
When i try to unzip the 8gig file it is 0bits and will not mount to the sd with win32disk
[Nook Color Android Development] DizzyDen:
I'll check into that and see what RS has done.

I just downloaded and extracted... so you apprarantly got a bad download... try again... 70 downloads on the rar... 40 on the gz and only one has said of any problems extracting and writing it... I would think it is on your end.
[Nook Color Android Development] FreeMan2012:
I'm a bit stumped.

I have a 2GB uSD card, so I downloaded 2gb_clockwork-3.0.2.8.rar, the MD5 checked out OK.

I decompressed it with 7-Zip (on WinXP).

I tried writing with win32 Disk Imager, but it refused to write to the uSD on either WimXP or Win7.

I downloaded WinImage, and was able to write the .img file, but it warned that The current image format is not supported by the disk drive M:. It will be resized. I went ahead and had it resize. (I'm not sure how just under 4MB won't fit on a 2GB card, but whatever...)

I copied in the new uImage & uRamdisk from NOOK-CWM3028-imgfiles.zip (only to find they are the same size/date as the ones in the img), popped the SD into my nook & powered on. It booted up into the normal nook software with no indication that anything was different. I've attempted to boot holding down the up volume, down volume & "n" button, with to apparent effect.

I've rooted my phone, and I'm familiar with the CWM recovery screen that comes up, and I'm expecting to see something similar here. Am I totally off base?

FreeMan
[Nook Color Android Development] DizzyDen:
What are you seeing that is just under 4MB ? the image itself should extract out to right at 2GB in size.

Try writing the 128 mb image to your sd then resizing the partition... see if that works.
[Nook Color Android Development] FreeMan2012:
Sorry, for clarification, the .img file is reported by windows at 1.7GB, the files that I can see on the uSD card after it's been written total about 4MB.

What should I expect to see when I boot the NC off the SD card, and do I have to hold down any extra buttons during boot to make it happen?

Thanks.

EDIT: just confirmed MD5 on the .img file, too. Took a while to calc that... :)

EDIT2: Used WinImage 8.1 - read that 8.5 wasn't working as expected.
[Nook Color Android Development] DizzyDen:
Did winimage 8.1 work?

Also I usually use win32diskimager 0.2-r23.

When you boot with SD in you should see skull and cross bones boot screen... and boot right into the CWM menu... no key presses necessary.
[Nook Color Android Development] FreeMan2012:
Thanks Dizzy-

I skipped 8.5 completely based on comments I saw earlier that it wouldn't work.

No, WinImage 8.1 did NOT work, it boots directly into BN1.2 as though there's no SD card in at all. Yes, it does report that the SD card is there, and I can browse the contents of the card and see the 4 files put in by WinImage.

I downloaded win32diskimager-RELEASE-0.3-r27-binary and it won't write to the SD card at all, gives "Error 8", but no details on what that error is. I'll try finding r23 and give that a try. I'll also try a different SD card to see if that makes a difference.

Thanks for your help, and any additional thoughts are appreciated!

FreeMan

EDIT: Win32DiskImager r23 didn't work either. Exact error message:

File Error

An error occurred when attempting to get a handle on the file.

Error 8:

I'm not sure if it thinks something is trying to hold the .img file, or the card open. Either way, it's not happy. Will try WinImage 8.1 on a new SD card...

EDIT2: I assume (yeah, I know) that in WinImage, I open my image file, select the SD card from the list of drive letters available, and select 'Write Disk'. it seems to do a format of the card in the process. I don't need to fiddle with any other settings, do I?
[Nook Color Android Development] FreeMan2012:
I've tried 2 different 2GB cards and a 4GB card - I can't get the NC to boot off any of them.

WinImage 8.1 is the only software that will write to the cards, but I get a warning message:

The current image format is not supported by the disk drive M:.

It will re(sic) resized.

I have triple checked to ensure that I'm writing the correct size image to the card (2GB -> 2GB, 4GB -> 4GB), but I still get that warning. Is this part of the problem?
[Nook Color Android Development] mr_fosi:
Do you have access to a linux box? If so, have you tried DD?

I had a problem writing a particular image with win32diskimager, which generally doesn't give me problems and the only way to get the IMG written was to do it with DD.
[Nook Color Android Development] FreeMan2012:
I do, however, I'm no Linux expert. it looks like my command line would be:

dd if=/home/4gb_clockwork-3.0.2.8.img of=/dev/sdb1 bs=1024

where if is my image file, of is my SD card, but I'm not sure what the bs parameter should be. Any tips?
[Nook Color Android Development] mr_fosi:
You're on the right track there but I would use your command sans the bs. :D

dd if=/home/4gb_clockwork-3.0.2.8.img of=/dev/sdb1

Make double sure you are writing to the proper device. I always triple check it in gparted or another GUI partition tool just to be sure.
[Nook Color Android Development] fpga_guy:
win32diskimager 0.1-r15

To the previous post with problems, I use win32diskimager 0.1-r15 with great success. The one hitch is that when you start the program, it comes up with Error #8.

If you are running with admin privileges, just ignore the error.
[Nook Color Android Development] FreeMan2012:
I pulled that line from the Ubuntu docs. I dropped the bs, and it seemed to work, but the NC still won't boot off the SD card.

Here's what dd said for the 4GB img file:

7372800+0 records in
7372800+0 records out
3774873600 bytes (3.8 GB) copied, 558.638 s, 6.8 MB/s

Thanks, using r23 & r27, the Error #8 comes up when I tell it to write, not when the program launches - it doesn't do anything after that. I'll go get r15 and see if that makes a difference. I am running as admin, so I'd think it'd work...
[Nook Color Android Development] mr_fosi:
Well, if the contents of the 7z file look ok i'm sumped.
[Nook Color Android Development] FreeMan2012:
Well, I've tried Win32 Disk Imager, r15, r23 & r27. All fail before writing to the SD card with an Error 8.

I've tried WinImage 8.1 which warns me that the image file won't fit & needs to be resized (even though I've confirmed multiple times that I'm using the right size image for the card), then sits at 0% for a few seconds before the dialog box goes away. Once it's gone away, the card seems to be formatted and the files written, but the NC won't boot off it. I've tried writing the 1GB img to a 2GB card and I still get the "won't fit" warning. Am I missing a step in here about formatting the SD? I see options to format, but they're all floppy disk options, nothing in the GB range.

I've tried using dd on a Linux machine, and it seemed to have worked successfully, but still no dice in booting the NC into CWM.

The 2GB cards are Kingston, class 2, and the 4GB is a Kingston class 4. Would that have anything to do with it? I'm considering running to Fry's this evening to pick up a new card & reader, just to see if there's a hardware issue of any sort. If I were to do that, any suggestions on what to try out?

Thanks again for all the help and suggestions, I continue to be open to feedback. The NC looks like it'll make for a great general tablet, once I can get past this step.

FreeMan
[Nook Color Android Development] FreeMan2012:
Solved

For future reference, when Win32 Disk Image reports "Error 8", that means, "Hey, n00b, quit trying to pull an image file across your network to burn to an SD card, try again from a local copy."

Once I did that, my NC booted right into Clockwork!

Thanks all for your patience and suggestions! (And now, I don't have an excuse to go buy new toys... :()
[Nook Color Android Development] mr_fosi:
lol

I missed where you said you were pulling it over the network.
[Nook Color Android Development] Obeg:
NC 1.2. 2 gig sd card formatted.

I use Win32diskimager to burn the 3.0.2.8 to the card. No errors. Unmount. Plug into nook. Turn on nook. It does not boot to it. The nook sees the card - and the files - but will not boot to it. What am I doing wrong?

Do I need to format the sd card some special way? Is there some special way to burn from Winimager that makes it bootable? Is burning the card with it mounted in my phone through usb not going to work? IE do I need a laptop that has an onboard sd port necessary?

Thanks for insight.
[Nook Color Android Development] Obeg:
Yes that was it - had to be in a local sd drive on my laptop and not connected through my phone...
[Nook Color Android Development] blackderbyhat:
Is the download link in the OP down for everyone or just me? (The legacyschools one)

http://legacyschool.us.to/nookdev/clockwork/0.7/
[Nook Color Android Development] aleem15:
FreeMan,

I am having the same problem as you. Only I tired putting the img file on the desktop, in the main c:\ drive, in my downloads folder; all are returning that same Error 8. Also I am using the built-in sd card reader on my laptop. I've reformated the card multiple times. I am using a 2gb card and the 2gb img file.

Please someone help me figure out what is going on.
[Nook Color Android Development] emtownsend:
Down here too. Any other mirror links available?
[Nook Color Android Development] emtownsend:
Here is 3.0.2.8

http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/

And the win32 image writer is here:

https://launchpad.net/win32-image-writer
[Nook Color Android Development] cmstlist:
Thanks, top post updated.
[Nook Color Android Development] DizzyDen:
Actually... the 3.0.2.8 files have been

in post 34 of this thread since 28th April 2011, 09:16 AM....

Don't mind other places posting my files... but would be nice if they would give me credit... also found them posted on androidtablets.net before... directly linking to my RS shares.... Gotta love that ;)
[Nook Color Android Development] cmstlist:
Updated again.
[Nook Color Android Development] bmorrissette:
I am having trouble getting this to work with my Mac. I have downloaded the 2gb file from post 34, used diskutility to restore the image to a 2gb sandisk microsd that is mounted in the sdcard slot. Yet i can not get my nook to recognized it to boot off of. It just boots normally. Any help would be appreciated.
[Nook Color Android Development] DizzyDen:
Did you download the img file? If you downloaded the .gz or .rar files you need to make sure you extract them first. I don't have a mac so cannot help very much there.
[Nook Color Android Development] bmorrissette:
I have tried it with both the rar and the img files. cant get either to work.
[Nook Color Android Development] DizzyDen:
Did you verify the MD5? As I said... I don't have a mac so I can't help in that regard... but with 100 downloads of 2 GB versions from rapidshare plus however many in post 34 here... I can't imagine it being the files unless you got bad downloads.
[Nook Color Android Development] bmorrissette:
MD5 verified for the rar file. still cant get it to work correctly. gonna try and find a different program since obviously I cant use the windows app to do it.
[Nook Color Android Development] ylixir:
dd works well enough, instructions are almost the same as linux, since OS X is at heart maybe more unix than linux:

first, open up a terminal (typing terminal into spotlight should get you there if you don't know how).

Then type in "mount" to see what your drives are. A quick explanation on this: Your disks should be listed as /dev/diskXsX where the first X identifies a disk and the second X identifies a partition on that disk. These are your raw block devices and will be associated with a folder--or mounted--so that you can see the files on them. When we flash an image we are just going to overwrite the raw block data, we don't care about the file system on the device.

On my computer /dev/disk0 is my main drive, and when i have a flash drive plugged in it shows up as /dev/disk1. This may be different on your computer. MAKE SURE YOU KNOW WHICH DISK IS WHICH. Following these instructions and using the wrong disk number can and will kill your computer.

You'll have to unmount any partitions on your sdcard, type: "sudo diskutil umount /dev/diskXsX" replacing the Xs with appropriate numbers. Do this for any partitions on your sdcard that "mount" shows mounted.

Now flash the image with the command, replacing the if and of paramaters as necessary: "sudo dd if=/path/to/image.img of=/dev/diskX" Remember, make sure the X number points to your sd card, not your computers hard drive.

When dd is done it will tell you how many bytes it transferred. Sometimes OS X remounts your card after the flash, if you see it on the desktop just pull it to the trash.

Pop your card into your nook and win :-)
[Nook Color Android Development] bmorrissette:
I did indeed have to figure out how to do it with Terminal. dd did indeed work, but you dont have to do sudo before the dd command. I just stole the commands from the nookdevs site on how to do it with an AN sdcard.
[Nook Color Android Development] DizzyDen:
Great... glad to hear you got it. Now I learned something as well.... mac can pretty much use linux (unix) commands.... will be able to help more now too.
[Nook Color Android Development] mr_fosi:
It looks like a lot of the problems people are having can be corrected by using dd instead of a windows-based IMG writer. Perhaps the OP should be updated with the recommendation?
[Nook Color Android Development] Omega Ra:
okay, using win32 disk imager I burned the 4gb img onto my card and I can't access it to add a zip file that i want to load. I go into my computer and double click the sd and it says it isn't formatted, do I want to format now...
[Nook Color Android Development] mr_fosi:
what sort of reader are you using?
[Nook Color Android Development] Omega Ra:
I am putting the SD card into a usb adapter thing. Could the problem be that I am burning it through a USB hub instead of it being plugged directly into the computer?

EDIT: also, when I select the image in the Win32, I click write to burn it correct, not read...
[Nook Color Android Development] mr_fosi:
It's been my experience that the reader can cause a uSD to be reported as unpartitioned (which can give you an unformat error). I had a problem similar to yours with my last uSD/adapter combo but when I changed adapters (from an all-in-1 USB to a uSD-to-SD) the problem went away.

Let windows try to format the card. If it works, I would say that something went wrong with the IMG write and you should try it again.

If windows reports that it cannot format the card, then it is probably an error due to the uSD adapter or your USB hub. Try plugging the uSD reader directly into your PC first and if that doesn't fix it, try another adapter.

As a last attempt, you could also try dd from within linux.

EDIT: Also, yes, you should "write" and not "read" in win32diskimager. Make triple-sure you are writing to the correct device.
[Nook Color Android Development] Omega Ra:
Okay, I formated the card, and plugged it into a from USB port on the computer and now I can look at it and the f: is called boot now. There should be 4 files on there after the burn correct??
[Nook Color Android Development] mr_fosi:
Well, the volume label is correct but I don't recall how many files should be there after the IMG write.

If you see files named like so, you should be good to go with the rest of the instructions in the OP:

- uRecImg

- uImage

- uRecRam

- uRamdisk
[Nook Color Android Development] Omega Ra:
I have

mlo

uImage

uRamdisk

u-boot.bin

sound right??
[Nook Color Android Development] mr_fosi:
Looks right to me. You are just missing the backup ramdisk (uRecRam) and backup kernel (uRecImg) and those might be generated on first boot... I dunno for sure.

Try booting with what you have and report back if it doesn't work.
[Nook Color Android Development] Omega Ra:
going to check now...if I have a couple zips on there as well it doesn't boot to them right? I have to select them to install?
[Nook Color Android Development] mr_fosi:
It sounds as if you've never made a recovery uSD. ;)

No, the card will not automatically install anything but rather give you a menu of options to choose from.
[Nook Color Android Development] Omega Ra:
lol this is true. I have been a WM guy, the nook is my first android device and previously I rooted it with autonooter, so I burned the image and started it and that is all.

edit: oh and it boots up fine thanks for the help.
[Nook Color Android Development] Omega Ra:
okay, one last question. How do I turn it off, I can't do my manual nooter install just yet as I have no access to wifi here at work to complete the process. Can I just take out the card and reboot? or is there a shutdown option somewhere, cause hitting the power button doesn't shut it off..
[Nook Color Android Development] mr_fosi:
If you hold the power button for 10 sec, it should shut off.

If not, you can pop the card out and reboot.

I have also traditionally been an WM guy (still have my Touch Pro II) but I got into android with a G2 bought cheap from a friend. Now I'm loving my NC. :D
[Nook Color Android Development] Omega Ra:
yeah I love my Nook Color, but all I really want is the root ability and to be able to side load, I actually like the stock look and feel, I may overclock it too to make it a bit snappier.