yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] bonzer2u:
try this Windows util attached here:

set options to:

Full overwrite format

Format size adjust = ON
[Nook Color Android Development] eyecrispy:
Thank you for continuing to try to help me. I so appreciate it. I just tried this and Windows 7 still can't see my SD card. I've got to find a Mac version of this.
[Nook Color Android Development] grandmasterlarry:
Alright now im having the same problem. im trying to restore back to stock and i get the. cant install (bad) error...

I sware i hate CWM... i have formated the disk several time several different ways. i copy the file on the SD card fine but when i take it out and stick it back in windows asks for the rest of the volume for the disk? WTF? why cant **** just work...

Ok its not CWM i think the file is bad some how other .zips work. ill keep you all filled in.
[Nook Color Android Development] eyecrispy:
What version stock? 1.0.1?
[Nook Color Android Development] bonzer2u:
what hardware are you using for your sd reader? I use the micro to mini sd adapter on my laptop's internal reader..

always assume shizz wont work that way you wont be so disappointed:eek:
[Nook Color Android Development] grandmasterlarry:
yeah the stock 1.0.1 and 1.0.0.

same internal read in my laptop...
[Nook Color Android Development] bonzer2u:
did you try formatting with the sdformatterv3 i posted at #315? if not give it a go...
[Nook Color Android Development] eyecrispy:
Ok, I just tried with a different SD card and got the same result. Of course, I didn't get to use those Windows utilities you suggested since I'm running on Mac.

Here is something that someone suggested on a different thread. Do you know if if I should flash the boot partition fix before or after reflashing stock? Or do I need to reflash stock at all?

Update: Tried this and no go. I went all the way back to stock 1.0.1 and absolutely cannot get CWM to flash. I can't flash through ROM Manager correctly and if I boot to CWM from SD, I can't flash the version that will let me do nandroid. The version in IOMonster's root pack will flash but that one doesn't let me do a nandroid. HELP!
[Nook Color Android Development] Kerflop:
I have been through all pages of this thread and I didn't see this question asked so here goes... (if i am mistaken please direct me to correct post and I will go away in shame :) )

I have installed Rom Manager and from in that app installed the latest CWM. I can get to CWM from either booting into recovery from within Rom Manager or by the 2 finger salute (since you don't have to use the V-up button anymore)... CWM comes up just fine but when I select ANY of the options all text disappears and all I see in the Rom Manager icon in the center of the screen. I have let it sit there for more than 20 mins and nothing happens. I have to hold the power button down for like 20 seconds or more just to reboot the Nook. Any suggestions on what I have done wrong? I am have no experince or knowledge with ABP... I have been using CWM with my EVO and so I was pretty excited to see it come to the Nook, till I found it doesn't want to work for me...

Any help would be greatly appreciated... :)
[Nook Color Android Development] Geezer Squid:
Hope this answer isn't too simplistic but have you tried to reflash CWM? You perhaps did not get a good flash the first time?
[Nook Color Android Development] Kerflop:
If by reflash you mean go back into Rom Manager and reinstalling CWM, I tried that but to no avail. Still the same behavior.
[Nook Color Android Development] spyz88:
Does anyone have any ideas on how to fix this issue? I tried to ping @koush but he never answers tweets :/

EDIT: I found a fix. Here's the link to the post.

http://xdaforums.com/showpost.php?p=10265722&postcount=11
[Nook Color Android Development] htowngator:
So I went into Rom Manager and it installed CWM successfully then I did a backup successfully. Am I to assume it can do a restore or is that still not ready?
[Nook Color Android Development] sapienta:
Dude thank you so much. Finally able to boot into CWR. Gonna try honeycomb next :) After I have a good backup of course.
[Nook Color Android Development] james robinson:
Me too!!! That's why I joined XDA!!!
[Nook Color Android Development] Tuanies:
I installed it on a rooted 1.1, says Clockwork install was successful, so I started a backup from Rom Manager. It boots into Clockwork, runs the backup and everything, but now I can't get out of Clockwork.

Can anyone help please?
[Nook Color Android Development] Hextall:
I'm having this same problem. Rooted with the new autonooter 3.0 today from stock 1.1, working fine today. installed ROM manager, flashed CMR, and now when I reboot system now... it shows the Touch the Future of Reading, a quick flash of the n, then back into CWR.

I've never abd'd before.

Any help?

Edit: removed cwr with the zip in this thread via cwr: http://xdaforums.com/showthread.php?t=943956
[Nook Color Android Development] Big-A-Rob:
Same problem here. Had to remove CWR.
[Nook Color Android Development] simon.ponder:
CWR will not install

At least I think not. Rom Manager states that it is installed, but after trying to boot into recovery, or start a backup from Rom Manager, all the nook does, is reboot. I have tried Power-n-VolUp as well, no dice.

Any ideas, I have nookieFroyo v0.5.9, and wanted to ensure that I was wiping things completely before flashing a newer version of NF on it.
[Nook Color Android Development] MadMikeSS:
I have the same problem with CWR in NF 0.6.7. I have NF flashed to uSD, you?
[Nook Color Android Development] adma84:
don't use the power button to select, use the nook button... Tap the power button again, and all your text will come back
[Nook Color Android Development] smalltownbird:
I get the same thing with the latest nookie. It's frustrating. I want to overclock but can't get into recovery unless I make a bootable SD with clockwork on it, but then it won't mount the sd card.

Preston
[Nook Color Android Development] rawfish:
EDIT: My apologies, I realized I posted in the regular CWR thread and not CWR-SD one. I understand that as of late, my posts are all over this side of XDA now, but am just curious to know what I can do to really fix this, or at least understand why this happens.

If I am unable to boot CWR-SD (and even Froyo/HC-SD), does this mean my device is permanently bricked? So far, most (if not all) unbricking methods involve the successful loading of CWR/Android OS/Nooter into the SD for further tinkering.

Issue: I could never go past the loading screen, at that stage the device will just display a black screen until I reset it.

Tried:

1) without uSD in: resetting via holding power x8 and power+n

2) with uSD in: many power + n + up/down variations and for long periods up to 60secs+++

3) 5 different uSDs across different capacities, speed and and brands

4) clean-formated uSD via another Android device, Ubuntu Disk Utility, parted, Windows 7 OS and EASEUS Partition Manager

5) burned the images tonnes of times to ensure no bad burns, with Win32DiskImage and WinImage

Is/was anyone else in the same boat as me, and how did you manage to fix it? Do remember, I can't get in even via CWR-SD and do not think it's a bad uSD burn.
[Nook Color Android Development] bartimeus:
Same problem here, although this is the second time I have had NF on my device and the first time I kept CWR. The first time I flashed NF using Rom Mangaer on th e1.1 custom rom. Not sure what difference that would make though.

Anytime I try to boot int CWR It says loading, then flashes to a different loading, then starts the android boot animation.

I am on NF 0.6.7 with it installed on emmc
[Nook Color Android Development] AntsInMyPants:
I am able to backup and restore a ROM fine using CWR. The problem I have is that there must be some sort of Token file that B&N uses for authorization. If I restore the default 1.10 ROM (rooted) that I created a few days ago, I get an authorization error message and that the system will reset. No way to decline the factory reset.
[Nook Color Android Development] gitanojr:
how do i manually reboot into recovery??

meaning within the clockworkmod: meaning the phone being turn off and then by turning it on go into recovery :p
[Nook Color Android Development] Hextall:
I read a tutorial in the following link that after flashing CWR via rom manager, you need to reboot your nook prior to booting into CWR. Apparently this solves the issue with the CWR boot loop.

My nook is at home (I'm at work), can anyone confirm?

http://www.androidtablets.net/forum...m-manager-nandroid-backup-custom-kernels.html
[Nook Color Android Development] Hextall:
Isn't it hold down power+n for 5 seconds?
[Nook Color Android Development] eyecrispy:
Hold power and n until you see the "touch the future of reading" screen. Then count to 5 and let go of the buttons. If CWR is installed properly, it will go into recovery.
[Nook Color Android Development] willverduzco:
Weird. Despite it identifying that I have CWR 3.0.0.5 installed, I can't boot into it using this method or using the reboot into recovery in Rom Manager. Luckily I can use an SDCard image of CWR thanks to Brian's Customized Nookie Froyo, so this isn't the end of the world for me.
[Nook Color Android Development] Hextall:
Did you have to zip the CWR remove zip file to get out of CWR bootloop the first time you booted to recovery after rooting?

I flashed the CWR removal zip when stuck in the loop, and rom manager still says it's installed. I haven't tried to reboot into recovery though after getting out of the bootloop (i scared).
[Nook Color Android Development] sd2649:
CONFIRMED!!!

Rebooted after installing recovery and then it went straight in, flashed kernel and booted right past the "n"

Awesome find!!!!
[Nook Color Android Development] Hextall:
I did this last night... installed Rom Manager, flashed CWR, then rebooted the nook. Then I was able to get in and out of CWR.

I flashed the 1.1 ghz kernal in CWR, and the only hiccup was that after clearing Dalvik cache, the nook locked up. I did it several times, waiting a while after flashing, and the nook wouldn't respond. It said the dalvik cache was clear, so I just power+n'd it back into recovery and flashed the kernal. It worked.

Some other people here also had it freeze after clearing dalvik cache.
[Nook Color Android Development] DomSim:
i have an auto nootered nc with froyo on emmc and HC on sd card set to boot froyo standard or hc by holding the n button as outlined in this thread, http://xdaforums.com/showthread.php?t=947698

i have edited the volb.fstab file so both roms share the same sdcard partition, which is partition 4 btw. the version of clockwork i previously had loaded the correct partition (4), i just updated to 3.0.0.5 and it loads the first partition on the sdcard which is actually the boot partition for hc on the sdcard. i have tried to downgrade but flashing 3.0.0.2 cause boot loops and i cannot even get it to boot into recovery. any ideas?
[Nook Color Android Development] Oskiee:
Hey guys... im hoping i can get help for this... yesterday i installed autonooter 3.0. everything was fine, no problem there. Today i installed CMR from the market, flashed it and then rebooted in. Now i cant get past recovery, it keeps booting into it. Ive tried the power+n For 5 secs, nothing. its version 3.0.0.5

thanks for any help
[Nook Color Android Development] Hextall:
You need to uninstall CWR. There's a zip file called something like CWR-removal.zip. flash that in CWR. It reinstalls the stock recovery. Reboot and you can start using your nook again.

If you want to install a working CWR (and get back out of it), download rom manager, flash CWR, then reboot (not boot into recovery, do a full reboot back into the nook's os). Then you can start using CWR.
[Nook Color Android Development] Oskiee:
Where do i find it? cant seem to find it.
[Nook Color Android Development] siraltus:
I know this might have been beaten to death and apologize in advance, but:

If you have Nookie Froyo in eMMC, can you have CWR in eMMC as well and boot into it with Power+N?

I flashed CWR in from ROM Manager but no matter whether I try to boot into CWR from ROM Manager or by holding Power+N, the nook just boots into Nookie Froyo. The only way I can boot into CWR is from an SD card holding a CWR image.

Am I doing it wrong or is this just how it is?
[Nook Color Android Development] Hextall:
I found it in a thread called something like "return to stock."
[Nook Color Android Development] chemical1der:
http://xdaforums.com/showthread.php?t=914690
[Nook Color Android Development] Philstadt:
install problem

Hey there,

I have a problem with installing the new recovery version.

I put the zip file onto my sd card.

I used 2 methods, but nothing works.

1: I flashed the zip file via recovery aus normal zip file

2: I renamed the recovery3.0.0.5 file into update.zip and installes it as : apply sd card update

After installing(both methods) the recovery is orange, also I can see the new version number.

But, after restarting the device and going back into recovery, its the old recovery.

I flashed my Desire in August with Unrevoked.

What can I do?

Please help me
[Nook Color Android Development] davidukfl:
installed from rom manager it defaults to version 3.0.0.6 and downloads that, not the one i place on the SD card.

it installs fine, however it says it can't mount the system and will not complete a full backup
[Nook Color Android Development] stevedawg85:
I'm running stock root and dloaded the latest rom manager from marketplace. Will this work if I choose the "install CWM" I'm sorta hesitant and hate to break the wife's nook :P
[Nook Color Android Development] Robertjm:
Nook Color or Nook Color (old)???

Hi all,

I just went to flash Clockworkmod Recovery, but it asks me to "Confirm Phone Model" and offers me:

Nook Color (old)

Nook Color

Which one should I select? I've got a rooted Nook Color, running stock kernel 1.0.1 version. ROM Manager installed via Market is 3.0.1.7. Do I still need to copy anything to my microSD card?

Thanks!!

Robert
[Nook Color Android Development] jtbnet:
Not the (old)/3.0.0.5=Ext3 FS one... as that is obsolete for a while... the other should give you 3.0.1.0=Ext3 and Ext4 which supports all including CM7 which is Ext4...
[Nook Color Android Development] Robertjm:
Thanks! Actually, as it turned out it was Nook Color (old). I tried the non-old version, but it wouldn't back up the sysem folder.

After Googling the error I was getting, which I don't remember, I found another XDA posting that said to switch to the old version when getting the error.

Robert
[Nook Color Android Development] arodey:
No it won't install properly through ROM Manager alone. The uRecRam is still needed.
[Nook Color Android Development] Analias:
I have successfully run the procedure above and the reboot worked. I also did a backup from the recovery and it appeared to work. I haven't tried restoring yet.

There was a bit of quirk under linux when it wouldn't allow the /media partition to mount while plugged into the usb. I had to push the file directly to the /system/boot directory.

-Freeman
[Nook Color Android Development] arodey:
I believe that that is why this instruction was included:
[Nook Color Android Development] Analias:
I saw that and that wasn't problem in my case. I do all my Android development under Linux. My system is configured not to automount file systems when they are seen, but that hasn't kept the Nook from unmounting /media and /sdcard. I don't see a way to force the Book to drop out if this mode without disconnecting the usb.

-Freeman
[Nook Color Android Development] arodey:
I used ADB Wireless.
[Nook Color Android Development] deitiphobia:
I was able to install via Rom Manager succesfully. I then performed the following from a batch file:

adb push clockwork-b3-nook-uRecRam /media/

adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system

adb shell mkdir /system/boot/

adb shell mount -t vfat /dev/block/mmcblk0p1 /system/boot

adb shell "cat /system/boot/uRecRam > /system/boot/uRecRam.bak"

adb shell "cat /media/clockwork-b3-nook-uRecRam > /system/boot/uRecRam"

adb shell umount /system/boot

adb shell rmdir /system/boot

I'm in the process of a backup now. Selection works with vol up / down and nook button to select.

Edit: Backup took quite a long time but it completed successfully. Backup took about 25-30 minutes to complete.

Now I'm off to brave a restore!

My nook is very new within the 30 days, so I will brave this and attempt a restore once it's done backing up. :)

Edit: Backup worked. My Nook Color still works normally. But looks like backups aren't complete yet and are missing a few things.
[Nook Color Android Development] sp1kez:
Need froyo internal memory rom now
[Nook Color Android Development] deitiphobia:
Not sure how current the info on that page is. It says that one of the bugs is not being able to control the selections, but that's working now. Looks like they have progressed beyond what that page says.
[Nook Color Android Development] :
Installing from ROM Manager did not work for me. Not gonna bother with the manual install until it's bug free.
[Nook Color Android Development] madfatter:
let us know how it goes.
[Nook Color Android Development] beerock:
Thanks to all involved !! took the plunge and followed directions here. Worked perfectly, also successfully did a backup and restore....... I was a little nervous on restore :p
[Nook Color Android Development] deitiphobia:
I was also nervous when it came to performing a restore, but thankfully it worked! Restore took about 20 minutes. Backup took about 25-30 minutes.

These times seem quite slow in comparison to backing up and restoring my Motorola Droid. Maybe I just never payed attention before at how long this takes?

Thank you to the person/persons involved in getting this going!
[Nook Color Android Development] duloz:
To confirm for everyone... Currently, backup is NOT complete...

Performed a backup on my nook in tandem with my incredible, results on the nook are:

Included:

cache.img

Data.img

Nandroid.md5

System.img

Missing:

Boot.img

Datadata.img

Recovery.img
[Nook Color Android Development] oc3rulz:
It works great, got a backup, now for some Froyo nookie
[Nook Color Android Development] beerock:
deitiphobia, do you have quick backup and restore enabled under setting in rom manager? this may help shave some time.
[Nook Color Android Development] beerock:
duloz, I too noticed some things missing, but I also noticed that when doing a restore it did not erase anything first.
[Nook Color Android Development] duloz:
Fair, I was just getting at the fact that it is probably a little early to start begging for roms at this point.
[Nook Color Android Development] deitiphobia:
Thanks...sure enough I had not turned that on.
[Nook Color Android Development] GMPOWER:
I installed using the xboxexpert method, and it all went well. For my first backup on a fresh restore with only auto-nooter took 10 min. to complete.
[Nook Color Android Development] oc3rulz:
Has anyone figured out a button Combo to start Recovery from boot?
[Nook Color Android Development] BertoJG:
To address some of the concerns I have seen listed:

This is not taking a complete backup. It is not backing up data critical to restoring the state of the device to the stock form in the event something goes wrong, it is missing three partitions, two of which are critical.

To boot into recovery, you use the stock method, hold down Vol+, N, and Power, then let go of power shortly after you see the screen come on, then let off the other two buttons a few seconds later.

Until all of the partitions are backed up properly or some other method is established, I would not get to crazy with your device.
[Nook Color Android Development] suzook:
Totaly agree. Its stil in the dev stage...people should wait till its complete. Its really not useful yet.
[Nook Color Android Development] likearaptor:
So when we flash this recovery option to our Nook Color, are we loosing the Barnes and Noble recovery? This I assume means we would loose the ability to apply future update.zips from B&N? And are we able to reflash the B&N recovery through the 8 failed boot method? I would like to help out as well but I also need to know what we loose by using this tool
[Nook Color Android Development] yerand:
is there gonna be a more streamlined way of installing cwr? or is this going to be the only way?
[Nook Color Android Development] arodey:
Eventually you should be able to flash from ROM Manager like on other devices.
[Nook Color Android Development] Geezer Squid:
It will be streamlined shortly (is my guess??). :D
[Nook Color Android Development] gedster314:
What great day. I just read that BT is powered on the NC and now CW is almost ready. Things are about ready to explode for the NC!
[Nook Color Android Development] AintSkerd:
Looking at twitter time lines it appears koush is knee deep in evo recoveries and drooling over sports cars. :o

It will come together soon enough. Its not like there are an abundance of ROMs to flash too.

It is exciting to see his support. I am just as eager as most to see what more intelligent people than myself have up their sleeves in the coming months.
[Nook Color Android Development] tnpapadakos:
awesome, i managed to get this thing to boot loop after updating to nook color clockwork recovery using rom manager...

not even the 8 button press is resetting it back to stock
[Nook Color Android Development] gottria:
So once CWM is stable and there are custom ROMS out there we can completly wipe the NC color out and have none of the BN stuff on there. I don't use it as a reader I bought it for rooting.
[Nook Color Android Development] cabbieBot:
the reading app needs to get ported IMHO
[Nook Color Android Development] likearaptor:
I agree, I would love to run stock Android 2.2 or 2.3 but only if I could keep the Library/Reading apps so I can read the kids books with my kids and read my magazine subscriptions. Both which don't work on the Nook app for Android.
[Nook Color Android Development] Geezer Squid:
That certainly is my plan.

There are good ebook apps already available if that is needed.
[Nook Color Android Development] tnpapadakos:
yeah so i definitely borked this NC trying to update to the nook color recovery in rom manager

so i took it in and got a new one at B&N...watching the clerk trying to boot it up for ten minutes was priceless:D

and this post will go unanswered and unnoticed just like my last one:mad:
[Nook Color Android Development] suzook:
As it should. You are one of the reasons for crappy return policies.
[Nook Color Android Development] tnpapadakos:
thank you...(but i thought it was a pretty good return policy)

just curious, what are some of the other reasons for crappy return policies?
[Nook Color Android Development] madfatter:
edited for content...sorry
[Nook Color Android Development] the_scotsman:
Please keep the discussion on topic, and no more flaming.
[Nook Color Android Development] tnpapadakos:
yes i am clueless:confused:

thanks for your kind words
[Nook Color Android Development] gedster314:
Don't take it personal about your first post. No one had answer on how to fix it because no one had NC backup image. When it comes to imaging the firmware its best wait till there is a proven undo.

Im glad it worked out for you. I kind of frown on those type of returns too but when I first started hacking phones and I made a claim on my sprint insurance.
[Nook Color Android Development] tnpapadakos:
no problem, if my skin wasnt thick enough to take someone's opinion, i would be hiding in a basement somewhere, just amazed at the backlash

i actually thought it was kinda funny i did that having successfully rooted/modded ten or so different devices over the last year without any problems before...i wasnt blaming anyone or complaining, but i was sorta surprised i got no response till i said that

anyway, its over now...moving on
[Nook Color Android Development] Geezer Squid:
I think your post went unanswered because none of us had an answer. All this is too new for most of us. Good luck. :)