yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] nemith:
Make sure RomManager is up to date and make sure you are selecting "NookColor"
[Nook Color Android Development] fuzzynco:
ROM Manager / CWR for SD card bootable OSes?

Is there a ROM Manager / CWR 3.0.2.8 modded for Nookie Froyo SD card OS,

/boot (p1, Fat32), /system (p2, ext2), /data (p3, ext3) and

/sdcard (p4, Fat32)?

Market ROM Manager puts the uRecImg / uRecRam on emmc :(.

Thanks
[Nook Color Android Development] malisha1:
I tried to write an 1gb CWM image to my 1gb sd card and diskimager is giving me an error not enough memory. Can i read the 128mb CWM image instead onto my 1gb sd card?
[Nook Color Android Development] stricknook:
i would find it helpful if the actual rom was actuly on this page. thanks for the info but not the program i keep getting routed to. how the heck do i word the reqjuest any clearer to avoid talking about and finding the rom?
[Nook Color Android Development] cmstlist:
I haven't a clue what you're talking about. This thread is not about a ROM.
[Nook Color Android Development] Lynehammike:
Hey, if you are after a bootable SD card image, then you should be able to follow the links on this page:

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

Hope that helps.
[Nook Color Android Development] matrix2004:
Ok when i go into CWR, i can't access the SDcard. I try install zip or mounts and it gets stuck on the Hat with the arrow. Any ideas? I'm running the latest Autunooter.
[Nook Color Android Development] whgarner:
cwm stuck on 3.0.1.0

when using rom manager v4.3.0.1, the "flash clockworkmod recovery" shows the current recovery as 3.0.1.0 and tapping this has no effect except to blue the "rom manager premium v4.3.0.1" for 1/2 second but no upgrade to 3.0.2.8. any help would be appreciated. thank you

bill g.

'
[Nook Color Android Development] stricknook:
please in the future include the file that the title states is here
[Nook Color Android Development] DreamingWolf:
The newest version 3.2.0.0 is out and flashes perfectly from ROM Manager. Scoop it up while it's fresh and avoid avoidable headaches :rolleyes:
[Nook Color Android Development] Paul22000:
What is new/fixed in this new version?
[Nook Color Android Development] eyeballer:
Check the OP of this thread........
[Nook Color Android Development] BitingChaos:
Well, I like clean interfaces, so the best part of the .32 kernel is the cleaner boot. It just flashes the screen and loads CWM.

Older kernels flashes some Loading text and had "Android" with a blinking cursor for some reason.

Also, in 3.2.0.0, /boot is *still* an option on the format menu. It may not work (I won't try it), but it is still there, and not removed like it said in the changelog.
[Nook Color Android Development] newellj79:
Nevermind....
[Nook Color Android Development] oldman_58:
Won't format /data

The OP says is is a highly recommended upgrade..... NOT

If you do not want to restore for ever format data jump on this upgrade.. Then use use your boot SDCard to restore or format /data...

Hope there is a fix soon!!!!!!!!!
[Nook Color Android Development] Chahk:
Problem with advanced restore of /data with 3.2.0.0 when formatted with the "new" partition layout (4 GB data and 1 GB media). Getting a "cannot format /data" error.
[Nook Color Android Development] long2know:
Does this latest verison allow me to format my old new so that it has the same partition sizes ("Support for newer nooks with the 5G /data parition!") like the newer Nooks? That would be sweet to have a bigger /data partition. I hate having to move stuff to SD card constantly..
[Nook Color Android Development] eyeballer:
There's scripts here to change partitions: http://xdaforums.com/showthread.php?t=1094371
[Nook Color Android Development] nemith:
Grab a /tmp/recovery.log for me. Details on the OP. Make sure it says 3.2.0.0 when you start CWM.
[Nook Color Android Development] nemith:
What? This is not very helpful. Can you please explain what the F!@k you are talking a about. I can't fix what I don't know is broken.

Please explain what you mean or refrain from these FUD type posts.
[Nook Color Android Development] will2live:
anyone have a link to the 3.2.0.0 files (uImage & uRamDisk ) so we can update our bootable sdcards so we are not stuck using 3.0.2.8 still and possibly causing issues. Thanks in advance
[Nook Color Android Development] 12paq:
Fyi: Upgraded CWM internal eMMC to 3.2.0.0, then upgrading from 91 to nightly 93, cleared cache and delvik, solid and no problems to report. Cleared delvik with no lockup, looks like that minor bug is squashed.

CWM 3.2.0.0 worked perfect.
[Nook Color Android Development] nemith:
Thanks for the report. I have the same outcome on my NookColor as well. I do see /boot is not being excluded from the format menu so there is one confirmed issue :)

Everyone else:

Please if you have any issues let me know either through this post, PM or #nookcolor on freenode
[Nook Color Android Development] eyeballer:
Here is a 1gb 3.2.0.1 sdcard I made: http://xdaforums.com/showthread.php?p=14462733#post14462733
[Nook Color Android Development] sisterchick:
Problems with 3.2.0

Running CM7 stable on Nook purchased May 2011 - v1.2 with green sticker (5MB partition). Updated to 3.2.0 CWM and initiated a backup through ROM Manager. Ended up in an unrecoverable boot loop. (Read Forever over and over. Could not restart into recovery with Nook and power button and tried interrupting startup 8+ times. End up using an SD image to fix recovery and reflash boot.

Several others reported similar experience in CM7 ROM thread.
[Nook Color Android Development] junkrobot:
I had a sudden instance of aggressive boot looping with 3.2.0.0, but I'm on 3.2.0.1 now and it seems to be okay. I've restarted a number of times and powered it down completely. Hopefully that won't happen again! I knew nothing was broken, but it was frustrating not even being able to get to the recovery menu in order to restore.
[Nook Color Android Development] BitingChaos:
I see 3.2.0.1 still formats /boot, and that the removal of that is no longer listed in the changelog.

Is this still planned?
[Nook Color Android Development] nemith:
Please describe this bootloop (bootloop by itself is not very informative). Did it continually boot into recovery?

Please describe as I am prety sure CWM is not the problem.
[Nook Color Android Development] nemith:
3.2.0.1 doesn't format /boot. Users select an option that formats /boot. Users are the issue not CWM.

That being said it will be in the next release cause apparently there are some really retarded users out there who love selecting that option.
[Nook Color Android Development] nemith:
I don't think this caused by CWM.

If you are reporting trouble please be detailed on what you did and what the problem is. (i.e WHAT is bootlooping. WHAT is shown on the screen)

If you really want to help provide an 'adb logcat' of the deice booting up.
[Nook Color Android Development] nemith:
Sounds like you flashed a bad kernel or ramdisk for CM7. This probably has NOTHING to do with CWM.
[Nook Color Android Development] Jimbo67:
Sorry in Advance for this stupid question-

Should I just use Rom Mgr. to update CWM, or should I download-unzip-hashcheck-and burn an sd to do the upgrade?;)

Thanks guys!
[Nook Color Android Development] Cotys:
Cannot flash or wipe data

I originally posted this on the CM7 thread. It doesn't seem to be anything common in CM7.

I've been running 7.1.0 RCO for a while and it has been working great. I let my Nook go completely battery dead over the weekend. After charging it again I had all type of problems with widgets not loading and getting a lot of FCs and occasional reboot loops.

I decided to restore from backup in CWM, it failed. I thought I might just go back to the last CM stable. I did the flash and it booted right back into 7.1.0. I did a wipe data / factory reset, wipe cache, wide davlik. After rebooting it loaded right back into 7.1.0 with all data intact. I'm running CWM 3.0.2.8. I loaded my recovery image CWM (3.0.1.0) and did the same drill. It booted right back into 7.1.0 with all data still in place.

I stepped through each of the mounts and storage options formatting everything. All completed except for System, it would run and hang. After a restart, everything is still there.

Also tried to flash the latest CWM in Rom Manager, it appeared to work. When booting into recovery the old 3.0.2.8 is there. I just downloaded an image with 3.2.0.1 and tried it also, still no go.

Not sure what to do here. It acts like it is working, but I come right back into CM 7.1.0.
[Nook Color Android Development] creepdogg:
I hope my problem is an easy fix so hear it goes,

Currently I am running one of the first builds of Honeycomb v04 from EMMC on my nook, I want to install the latest CWM, I downloaded rom manager but every time I go to flash it i receive the error "An error occurred while attempting to run privileged commands" ??? Any thoughts?

Also I can not boot into my existing install of CWM

UPDATE !!!

I was able to burn a bootable CWM , wiped / flashed phiremod , downloaded ROM manager, flashed newest CWM, but still cant boot to CWM by rom manager, reboot options, or holding down power and N ??????????????? Any ideas?
[Nook Color Android Development] Divine_Madcat:
Since 3.0.1.0, i have just updated through rom manager, with no issues at all.
[Nook Color Android Development] long2know:
Awesome! Thanks for the links! Maybe now I won't ever have to move an app to SD again.
[Nook Color Android Development] TJNooker:
I don't know who is responsible, nemith from CWM or someone from the CM7 team, but I just wanted to say thanks to whoever resolved the freeze issue with clearing dalvik cache. Since I started using CWM on Eclair, about 95% of the time I cleared dalvik cache in CWM it would freeze immediately afterward. While it only took a hard reset to get things back to normal, it was really annoying.

Somewhere between CM7 nightly 86 and nightly 91, clearing dalvik cache started working perfectly and it has continued to do so. I know CWM has gone through a few versions since nightly 86, so it could have been nemith's doing. Either way, thank you!
[Nook Color Android Development] nemith:
Believe it or not, the problem magically gone away when we went with a .32 kernel for recovery.
[Nook Color Android Development] Divine_Madcat:
Magically eh? Sounds Applish. ;)
[Nook Color Android Development] fuzzynco:
Can 3.2.0.1 Save Nand's to booted SD card?

Can 3.2.0.1 booted from SD, but effecting eMMC,

store / restore its nandroid backups to/from

the booted SD card?

I'm wondering if I could use a single large

(16gb) sd as both a boot and storage

media for recovery? Would I need

a second fat32 partition for '/sdcard'

or can I use mount once the recovery

system is booted to mount '/boot'

(single fat32) as '/sdcard' for recovery

media disk?

I wondered if I had the 'new' 5gb / 1gb

partitioning, would /data still get imaged?

could the new 1gb /media be imaged

for backup?

Would doing a

(1) nandroid backup of old stock 1.2

(2) repartition to 'new' 1.2 (5gb/1gb) w/ zip

(3) reformat /cache /data /media w/ zip

(4) restore backups of /data /media

work to preserve stock 1.2 existing

B&N apps and books? Or can they

be archived during the repartitioning

process? :confused:

Thanks
[Nook Color Android Development] muness:
Yes. http://xdaforums.com/showpost.php?p=14462733&postcount=120

No. One partition is all you need. You do have to pop the microSD out for a second on reboots so that it boots from eMMC, not the microSD card.

Burn the image, linked above and then expand it to fill the microSD (burns to 1GB)
[Nook Color Android Development] TJNooker:
Oh, ok. Well, you're getting a thanks anyway. :)
[Nook Color Android Development] nemith:
Thanks. I did spent a lot of time in GDB trying to figure this one out. It would deadlock when trying to get input from one of the keys. Apparently it was a Kernel bug.
[Nook Color Android Development] fuzzynco:
ok -- clearification on bootable 3.2.0.1 from sd effecting emmc

I create the uSD card from the 1gb image, then use a partition editor to

expand the imaged disk to fill the remaining space on the uSD card.

I boot to the 'normal' OS on the uSD card (should be CWR 3.2.0.1)

and have it NANDroid backup (it should be reading emmc and writing

to the booted uSD card, right?).

Which emmc partitions should be backed up,

does it do /rom, /factory and /media ?
[Nook Color Android Development] nemith:
Yes the CWM is setup to backup/restore/install to EMMC only.

It doesn't do /rom /factory or /media. It will backup /boot (bootloaders, kernels, and ramdisks for rom and recovery) /system, /data, and /cache.

/rom. /factory and /media shouldn't ever really be touched and are not backed up. It seems it would me more risky to backup and restore these partitions and there is little real gain.
[Nook Color Android Development] fuzzynco:
I was able to install it to a large card, but neither gparted (unix) or

easyus (win32) is able to resize a non-partitioned disk (super floppy)

which is how the 1gb is formated.

How can I make a partitioned (MBR style) uSD?

What makes it a bootable?

The created img files from emmc did fit in the 1gb space though.

I've copied the 2 device specific file systems manually. I thought

books and such went in /media, do they go in /data? Is that why

the newest NCs come with a big /data and small /media?
[Nook Color Android Development] nemith:
Yes. SD's without MBRs actually drive me crazy (not sure why they are so popular).

There is a caveat that you must match some very specific drive geometry settings when using a MBR style uSD if you want to boot from it.

Apps. Books are small 1G of books is a lot of books. Apps on the other hand are larger. They came out with the new partitioning after 1.2.
[Nook Color Android Development] fuzzynco:
How to fdisk for uSD bootablitity

OK -- can you tell me what to tell fdisk for partitioning the uSD ?

I figure if I layout the disk as 1 large fat32 partition that's supposed

to be bootable, format it as vfat and cp -a whats on the super

floppy to it, I should have a uSD that's a real hard drive to unix

and windows? And still bootable on NC

Otherwise I can use an existing 2gb CWR img, restore that,

expand it to fill the uSD size, then replace it's contents

with the content of the super floppy? That should also work

as the 2gb img's from 3.0.2.8 were MBR style uSDs.

Thanks again :)

PS:

What would I have to change in 3.2.0.1's ram disk

to make it use the booted uSD

(p1 = /boot (fat32), p2 = /system (ext2), p3 = /data (ext3),

p4 = /sdcard (fat32)) for Nookie Froyo as its source and

target vs emmc?

I should be able to loop mount the ram disk image

to edit it, yes?

:)
[Nook Color Android Development] madguy2006:
8GB Image for CWM 3.2.0.1?

Hello-

Can somebody tell me where I can download the 8GB Image of CWM 3.2.0.1 for SD card?

Thanks in advance!
[Nook Color Android Development] fuzzynco:
[Solved] Creating a MBR format SD card for 3.2.0.1 SD card

I repartitioned a new uSD card as 1 large FAT32 partition,

set the partition as active, formatted it FAT32, then

copied the all the files from eyeballer's 1gb super-floppy

formatted SD card image.

With a partition table there, both EASEUS (win32) and

gparted (*nix) were able to resize the partition to fill

the card.

I just repackaged eyeballer's SD disk as MBR instead

of super-floppy so it could be extended with partitioning

tools. I didn't have a 1gb so I used a 2gb.
[Nook Color Android Development] Colchiro:
If you mean a bootable CWR disk, or just want to update your existing one to 3.2.0.1 try this: http://androidforums.com/nookcolor-...ke-bootable-cwm-3-0-2-8-recovery-sd-card.html
[Nook Color Android Development] pmilford:
u-boot/ROM manager/CWM 3.2.0.1 issue??

HI,

I was running a reasonably up to date CM7 (94?) with current CWM 3.2.0.1

and a recent ROM Manager (4.3.2.3 Premium).

With upcoming changes to CM7/kernel/SOD, I felt it was time to upgrade

today or tomorrow - so I decided to backup current ROM.

I ran ROM manager and selected backup ROM, chose a filename (I have

done this numerous times before when I am about to update)

Upon reboot, the system hung at green uboot(?) loading screen.

I tried rebooting with the power button and it hung again at the same point.

Next I held the 'N' button during boot and was able to access the u-boot

menu. I tried booting into normal CM7 and it hung. I tried booting to recovery

and it hung. (I have no secondary alt boot installed)

I'm trying to figure out how to recover this now. The recovery images that

I found looked like they were pre kernel 2.6.32 and I recall there were some

issues with uboot etc. that changed.

What I am trying:

Bootable CWM 3.0.2.8 from SD. Use it to flash a current Dal OC kernel (6/13)

Then hopefully I can reboot my emmc CM7 and use ROM Manager to re-install

CWM.

It is a long time since I tried SD booting, so I downloaded a newish (3.0.2.8)

2GB img that I found [I probably should have searched more for a 3.2.0.1., but

I have an older NC]

I burned it with WIN32diskimager, then added the cwm flashable 6/13

OC kernel to the SD card.

*** When I booted CWM from the SD card it immediately started to

backup the ROM *** I didn't expect this, I am guessing some leftover

from an interaction with ROM Manager??

After the backup completed, I installed the OC kernel .zip, wiped cache

and dalvik cache, replaced my normal uSD and rebooted into CM7. ROM

manager reported current version of CWM to be 3.2.0.1, but I decided to

reinstall CWM via ROMmanager anyway.

I rebooted CM7 using power button and it booted!! I'll wait a day to

boot with ROMManager.

I tried to boot into CWM from u-boot menu and it hangs at the:

"Booting. One moment..." message - grrr.

Power cycling, and it hangs at the "Loading..." message.

Using "N" to enter u-boot then normal boot mode also hangs...

Using Power and "N" to boot into recovery also hangs, at

"Booting into recovery..."

--> I repeated the kernel install from SD card and system is booting

ok after power cycle or power button menu boot - I won't try

the u-boot menu.

Attached is a last_log, but it looks to me like from the SD install of OC Kernel.

Note it was in cache/recovery not /tmp.

I see there were some changes in N103 that look related to recovery booting...

I think I can run with this for a day or two. My plan is to d/l new versions

of CM N107(?), OC kernel, GAPPS to my bootable uSD with CWM 3.0.2.8 and flash

from there. Hopefully this will fix whatever problem with versions or bugs I

have!

Hopefully this post will help someone solve any similar problems!

Peter
[Nook Color Android Development] zentsang:
<UPDATE> - Disregard my message below. After going through all 52 pages in this thread I found an answer. Man that took a long time! And the search engine didn't help much.

OK... I must be blind. Assuming you have a device that does not yet have CWM, ROMmanager, etc. A plain Nook Color 1.2 that you are rooting for the first time. And that another site redirects to this post on XDA to "download CWM for SD" ... where is that file exactly? I've rooted several other devices but this it the first Nook Color I'm rooting so I need an actual file to work with rather than directions on running ROMmanager to get an update.

Any help is appreciated.
[Nook Color Android Development] Colchiro:
Can't you install Rom Manager from Market after rooting?
[Nook Color Android Development] DigitalMD:
pmilford Peter:

I had the same thing happen when I tried to update form Nightly 134 to 136. I wound up having to wipe and repartition the Nook and return to stock. I then installed 133 and everything was fine. Tried to update to 136 after a full wipe and blamo, it would not boot again. I see a lot of folks have no problem with 136 so this baffles me. I"ve been updating to almost every nightly version since about 86 and no issues until now.
[Nook Color Android Development] Bimboy:
N136 totally hosed me as well. I update a to the newest nightly a couple times a week minimum too.. never had a problem.
[Nook Color Android Development] NiteShdw:
Any chance you could save the rest of the us the same effort and quote or post a link to the post where you found the useful information? I haven't even been able to find a download link to the new 3.2.0.1 version; it's not in the first post for some reason.
[Nook Color Android Development] Dj-Gutz:
Opened a thread on Q&A but got nowhere ( http://xdaforums.com/showthread.php?t=1172846 )

So I'll try here too , can we enable usb-host mode in cwm menu?

I want to use my usb keyboard to navigate instead of the hardware keys ( It's going to be mounted in a car )
[Nook Color Android Development] breebauer:
Did you try the Nook Tweaks app? It has usb settings, among other things.
[Nook Color Android Development] patruns:
After "rooting", no.... at least if you do it does you no good. After installing CM7, yes, you can and most of us do it that way.
[Nook Color Android Development] DigitalMD:
No, there is no support for USB host in recovery,
[Nook Color Android Development] riceknight:
I'm running Phiremod 6.3 and have tried flashing CWM through Rom Manager numerous times. Rom Manager says it installs fine, but I'm never able to boot into recovery without a dedicated CWM SD card. I've tried hold N and power button as well.

Its very frustrating because I lost one of my microsd cards, leaving me unable to get into CWM and flash anything.
[Nook Color Android Development] Jimbo67:
Here is a link to cwm 3.2.0.1:)

http://www.techerrata.com/dl.php?path=15&file=1gb_clockwork-3.2.0.1-eyeballer.zip
[Nook Color Android Development] dasingleton:
I am having the same issue. No matter what recovery I try...it gets stuck in 3.0.1.0. I think next I will try installing CM7 on eMMc!
[Nook Color Android Development] Dj-Gutz:
I know there isn't ( I tried )

The question is , can I make it work?

I don't have much coding skills but if it's possible I'm ready to learn and re-compile it with the necessary code

I don't know how cwm works ( if it's loaded before the kernel or uses it or whatever )

tried google and xda search and came up with nothing ( cuz its not a normal request of course )

So basically my question is : Is It Possible?
[Nook Color Android Development] DigitalMD:
Having developed software for over 30 years I would never say any thing programming wise is impossible with enough time and determination, but recovery code is very basic and not intended to support anything more than the basic functions. Also it needs to load everything into ram to perform its functions. If I understand your needs correctly you want to be able to invoke flash and recovery functions from a remote position. If ROM manager cannot fill your needs, you might take a look at wireless ADB. Using ADB you can do just about anything from a maintenance standpoint without ever touching the Nook.
[Nook Color Android Development] Dj-Gutz:
Thanks for the help , obviously I couldn't know you are an experienced coder ( low posts meter ) :)

Even if it's possible with wireless ADB it still doesn't help me much ( unless I can use my CM7 on HD2 to control it? )

my NC will be installed in a car

If I can't make it happen I'll have to extend the hardware buttons to flash nightly's ( CM7 ) and backing up the system..

My preference of course it to avoid opening the device and mess with it

I read that it's not very wise to update a nightly with ROM Manager , so I'm using cwm - but since it will be installed in a car in a fixed manner I can't open screws and such every time I want to update my ROM and that's why I thought about using usb host ( which will be used already in the car setup )
[Nook Color Android Development] 12paq:
You can find all the information you need by just Google Clock Work Mod and Koush.

Koush is the (amazing) dev/creater of CWM, AFAIK publicly posts his code on CWM. Others have modified it at times for unique kernels and such or for there own use. He and the devs that help him maintain CWM for many devices, generally like to keep things uniform so to not cause confusion, but last I looked his code was publicly posted, again AFAIK.
[Nook Color Android Development] Dj-Gutz:
thanks 12paq I'll look into it :)