yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fwdixon:
No, you have to upgrade to 1.1.0 to get pinch to zoom in the browser.
[Nook Color Android Development] fwdixon:
Okie doke. Took the gapps zip from this package, stripped out all the files except the market and youtube and contents of the meta-inf folder, left the rest of the folders in place but empty, and reflashed. Market up and running :D

Next question, how can I make my SD card visible to all apps? Tapatalk sees it no problem, but none of my nav apps can find it or think it is mounted r/o and won't d/l the data files.
[Nook Color Android Development] thechaps:
Ok i must be missing something. All the Clockwork bootable files i dl are .tar. Where do you guys keep getting these .img files? win32 doesnt see .tar. Please point me in the right direction
[Nook Color Android Development] fwdixon:
use win32image.exe and make sure you are unzipping the pkg with the .img in it. the img is exactly that, a file that is an image of a disk or drive (just like a photo is an image). win32image.exe takes the img and "prints" it to a disk, making it usable.
[Nook Color Android Development] thecubed:
A .tar.gz file is essentially a .zip file. Download winRAR or 7zip and extract the .tar.gz file. You will then end up with a .img file that you use win32diskimager to write to the SD card.

Good luck!
[Nook Color Android Development] eyecrispy:
Sorry. Wrong forum
[Nook Color Android Development] axe2:
Expand filesystem

Apologies if this is a FAQ, but how can I expand these images? I know how to expand a partition, or add an additional partition, but this image does not appear to contain a partition table. Can I expand it to fill a larger sdcard somehow?
[Nook Color Android Development] fwdixon:
As this merely root the stock OS, I don't see where expanding it gives any benefit. I have it loaded on a 2gb card I use as my restore disk.
[Nook Color Android Development] axe2:
I was hoping that this could be used for a general backup/restore sdcard. This could be useful for the time being, since CWR is currently not compatible with Honeycomb or Froyo.

I assume that it should be possible to backup/restore to/from this, no?
[Nook Color Android Development] thecubed:
You are indeed correct- they have no partition table! Simply put, this makes it VERY easy for me to modify the files in the .img files simply by mounting (no need to worry about partition offsets when mounting, etc)

Shortly (I know I've said that a few times already) I plan on releasing different size SD images: 128mb, 2gb, 4gb, and 8gb.

The 128mb image will contain the rootpack, and the others will be just plain ol bootable CWR sd card images. You can add the .zips to it if you'd like.

The only bump in the road for now is my lack of time. School just started up again for me, and I've been really busy getting classes and other things in line.

Rest assured, however, good things are coming soon!

I am also working on an ext4-compatible version that will work for installing/backing up 2.3 and 3.0 on EMMC.

Along with that will come the proper .zips for installing/removing the ext4-compatible CWR to EMMC.
[Nook Color Android Development] axe2:
Thanks for the info.

I looked through your build script, and it looks like you start from some pre-generated images. Are these images created simply by creating an appropriately sized file (e.g. using dd if=/dev/zero ...), and then formatting it FAT32, or is there more to it than that?
[Nook Color Android Development] axe2:
I answered my own question...

Yes, you can just create a file of all zeros (e.g. using dd if=/dev/zero ...), and then format it FAT32. Add this to the list in the build script, and away it goes.

I successfully created a 16GB CWR sdcard this way. Haven't tested what I can do with it yet...
[Nook Color Android Development] thecubed:
Very close! I make an appropriately sized zero image, then I use fdisk to change the heads, tracks, and cylinders to the proper values (255, 63, and total bytes of image times 255 times 63).

Then I create a FAT32 partition, mark it bootable, then exit fdisk. Once I have that done, I mount the image to a loopback device (losetup /dev/loop0 sdcard_x.img) then I mkfs.vfat -F 32 /dev/loop0 . Once that finishes, I can just destroy the loopback device, and mount the image normally with -o loop.

Once I have all of that done, I just tar it all up and put it in the build directory, add a new size to the build script and go for it!

I wrote the buildscript so that I wouldn't be the only one able to build CWR SD cards. I'm going to release an updated version that makes the blank img files, too.

Another script that will come soon is a ramdisk unpacker/repacker. That way you can modify files in the uRamdisk easily.
[Nook Color Android Development] eyecrispy:
OP, any updates on the CWR fix?
[Nook Color Android Development] thecubed:
All good things come with time :)

Honestly, I have it all done, I just haven't tested it yet. I've learned from my last mistake of releasing the rootpack early and finding that it has a multitude of bugs- so I'm going to test it on my own device (make a backup, restore a backup, etc) before I release it.

The reason for the delay: my NookColor has my textbooks on it... and if it dies, so do I :)

I plan on giving it all a go tonight, since I dont have class tomorrow.
[Nook Color Android Development] axe2:
I either got lucky, or you dont have to do the loopback steps. I didnt, and it works great.

Thanks for the help!
[Nook Color Android Development] Vid.:
Torrent for buildenv.tar.gz

I created a torrent for buildenv.tar.gz to lighten the load a bit on IOMonster's server. The MD5 checksum for the file is

MD5 (buildenv.tar.gz) = 77cfc379ce019089e28544078a779236

If you already have a copy of this file, please seed the torrent
[Nook Color Android Development] thecubed:
Thanks! I've gone through 150GB bandwidth in four days. This combined with the rootpack and ADB driver pack are quite popular items on my server.

My only question is how should I update the torrent when I release a new buildenv?
[Nook Color Android Development] thecubed:
1.1 Compatible Rootpack Just released!

This release brings with it the ability to make backups of your NookColor to SD while booted from CWM on SD, and a fixed version of the installClockwork.zip, so backups will now work!

The biggest announcement being that this rootpack is now 1.1 compatible! Want an easy way to root+install market on your 1.1 device? This is it!

Another biggie is the second most requested feature: more SD sizes!

I've now got 128mb, 1gb, 2gb, 4gb, and 8gb images up for download.

As a side note, the 1.1 rooting+gApps ability of this rootpack are UNTESTED. I have replaced the proper files in the proper places, but there is no guarantee that this'll work. If you want to try the 1.1 rooting + gApps, please be ready to factory restore your NookColor if it doesn't work out.

With that said, i'll be sure to remove this warning once i've seen a few successful installs.

Any testers?

OH and for the love of all that's good and holy, TURN OFF YOUR DOWNLOAD MANAGERS / ACCELERATORS!
[Nook Color Android Development] ajm2387:
download link is down for 0.7 :(

EDIT: nvm found it in the dir
[Nook Color Android Development] jhnstn00:
Nice work, root, CWR, and google apps. Wow.

I have contemplated a NC to use as a tablet for pleasure as I wont use it for reading. Is this a good idea?

Sent from Samsung Captivate Continuum 2.2 w/ Sensation 1.2 (Awesome)
[Nook Color Android Development] fwdixon:
I'll test this today!
[Nook Color Android Development] eyecrispy:
I just tested the new CWM zip and it works great! My nandroid just finished without issue! Thank you for your work!
[Nook Color Android Development] fwdixon:
The full rootpack link doesn't work.
[Nook Color Android Development] Rayven01:
I can confirm that backups, restores, partition formats and zip installs all work fine with the 0.7 SD card image. The 1.1 rootpack and google apps zips also work great to root stock 1.1. Very nice work!
[Nook Color Android Development] thecubed:
Fixed, thanks!
[Nook Color Android Development] fwdixon:
If I download the "install clockwork" zip from your server, is that the latest version?
[Nook Color Android Development] fwdixon:
Did the root procedure and installed CWR, boots into CWR on the eMMC only. Will try the full rootpack later, going to remove CWR for now

Edit: Reboot without CWR and it tries to factory recover with an "install Failed" message.
[Nook Color Android Development] fwdixon:
double 10 char
[Nook Color Android Development] axe2:
Is it required to format any of the partitions prior to restoring, or does the restore handle all of that?
[Nook Color Android Development] fwdixon:
I generally format data and system, but i beleive the restore handles that.
[Nook Color Android Development] Fixter:
Hey OP, I used the version 04 and I'm not getting Paids apps, neither on mine or my fiancée. Do you have any solutions for that. I haven't done anything. Just turned them on with the chip and rooted, installed gapps and blocked the 1.1. That was it. Everything is working perfect except for that.
[Nook Color Android Development] fwdixon:
Finally got a clean, stock, non-rooted 1.1 to install and work :D Rootpack works perfectly, and no issues with gapps or youtube.

GJ

Now, installing CWR on the eMMC causes it to only boot into CWR. So...
[Nook Color Android Development] Fixter:
Yeah its VERY tedious. Did you remove the SD?
[Nook Color Android Development] cray1000:
this doesnt allow for a custom recovery on the device and have it work with 1.1 right? CWM must run off the sd card to work with 1.1 right?

Nice work OP, going to use this on my new nook tongith I think
[Nook Color Android Development] thecubed:
Not quite sure what you mean... If you have CWR installed to EMMC, you can just download my zips and run them from CWR on-device. However, I think you'd need a sdcard to store the .zips since clockwork doesn't know about the EMMC's 5gb media partition.

---

As for those having issues with the installclockwork.zip, I'm going to take a look here soon (in the morning!) why it's causing people to only be able to boot to CWR.

---

Also, one more thing! Within 24 hours of releasing this, I've seen about 20gb of downloads for the rootpacks/CWR sdcard images... WOW.

I plan on having a torrent made available here soon, just as soon as I can figure out what AT&T business' TOS are for p2p for legally sharable files.

Failing that, if anyone is able to mirror the files, PM me, and we'll get everything together.

Thanks!
[Nook Color Android Development] fwdixon:
Thx thecubed.

FWIW, it's something with this build of CWR. I can install the one from rootpack v0.4 and it boots normally unless I hold power+n (which loads CWR perfectly)
[Nook Color Android Development] Thibor69:
I installed the "installclockwork.zip" (from the 0.7 pack) on top of the 0.5 pack CWR. It seems to backup now but I do get 2 error's. See picture.

Any thoughts ?
[Nook Color Android Development] thecubed:
Actually, those aren't errors.

SD-EXT is a partition that is made by some apps2sd migration scripts, which we're not using since we've got a BIG /data partition to store apps.

The /sdcard/.android_secure notice is for 2.2+, that's the official apps2sd way that android puts apps on the SD card. And as far as I know, that's 2.2 and up only.

The backup completed correctly, and it should work just fine.

So, you say you used the installclockwork.zip ? Does your device boot fine to the normal OS? I'm just trying to figure out what some people mean by their device won't boot after using it...
[Nook Color Android Development] eyecrispy:
I used the installclockwork.zip and flashed right over the broken version and my NC booted up just fine to my 1.0.1 rooted OS.
[Nook Color Android Development] Thibor69:
Yes and yes. I booted to CWR and then ran your installclockwork.zip. Everything is working 100% now. And all my apps and data are still there.
[Nook Color Android Development] fwdixon:
are you running 1.1.0 or 1.0.1?
[Nook Color Android Development] Fixter:
OP any idea why the Market isn't showing the paid apps tab? I can see paid apps just fine with Market Enabler.
[Nook Color Android Development] james robinson:
128, 1 , 2, 4, 8, etc..

does it matter which size image you download?
[Nook Color Android Development] thecubed:
Honestly? No idea. I'm not even sure what 'market enabler' is, honestly...

My thought though is that it's an issue with not having a proper AndroidID, or possibly there's a problem with the build.prop's signature. I'll look into it here soon.

Yes. 128mb_rootpack is the ONLY image that will root your device. The other X_clockwork files are for different size SD cards. If your goal is to root your device, download the rootpack. If you goal is to make a backup/restore your device, download the proper size for your SD card.
[Nook Color Android Development] james robinson:
oh, ok!!! so if i have an 8 gb sd, then i should the following:

8gb_clockwork-0.7.tar.gz	11-Feb-2011 01:54	10M

>

P.S. do i need to refomat by sd card with the nook first?
[Nook Color Android Development] lafester:
this really has turned into a great tool for flashing and restoring Nooks.

Just wish the damn sd card slot wasn't such a pain in the ass to use.

thanks cubed!
[Nook Color Android Development] forsakenexile:
Good information, Thannks
[Nook Color Android Development] luigi90210:
can someone upload a mirror?

it has taken me 3 hours to download 30% of it and it is driving me crazy
[Nook Color Android Development] phfaty:
Anyone got a faster link to the monster root pack file? It is taking about over 2 hours to download.

thanks
[Nook Color Android Development] thecubed:
This is a call for mirrors! My connection has been capped by AT&T for the month, since I've gone through over 80gb in the past few days alone. (900gb this month total!) Although this is supposedly an uncapped connection, and it's only on one of my IPs, it looks like I'll need some mirrors to help spread the load out until I can come to terms with AT&T.

If you have space for about 100mb of files, and bandwidth for about 10gb/day, PM me!

To everyone downloading this and waiting patiently-- thank you. That really shows dedication.

(Please, no rapidshare or adware-laced mirrors. I refuse to let anyone but the proper people profit from this software. The proper people being the NookDevs team and the CyanogenMod guys)

Also, one more thing: feature requests. Leave a message here, and I'll see what I can do! I plan on adding the OC kernels to the /extras directory, and even some fixes for the stock os (adhoc fix, keyboards, scripts, etc).
[Nook Color Android Development] faceman66:
Feature Request: include the folder structure for Clockwork Recovery backups. This way once the SD image is burned, I can toss in my latest backups and have a complete recovery from SD.

Also, maybe include the zips that samuellhalff is working with (http://xdaforums.com/showthread.php?t=914690) or at least the repartition-boot-with-stock.zip file since that has been the first step to fix for a few nooks I've dealt with lately.

I think you have a great thing going here and I'm eager to pack as many tools into the awesome toolbox you are giving me.
[Nook Color Android Development] thunderstruck!:
Set up a torrent and I'll seed. (Even though I'm not using the root pack yet., just got Nook yesterday.)
[Nook Color Android Development] Thibor69:
I am running 1.0.1 but with with IOMonsters Block1.1 which fakes a 1.1 update.
[Nook Color Android Development] fwdixon:
Ok. Thecubed, seems the issue with booting into CWR is only affected rooted 1.1
[Nook Color Android Development] tcontento:
Awesome work!! I tried auto-nooter running version 1.1 on the NC and got stuck into the reboot loop..... I was stressing, and seen this lovely piece of work. Took three tries to get it right (my issues) and now it is running great. Thanks and I will be dropping sending my thanks for your efforts.
[Nook Color Android Development] Fishfoot:
Any word on a torrent? I'd gladly seed it.
[Nook Color Android Development] cmfreeman:
Is anyone having trouble unzipping the 8gb SD Card CWR? I have tried winzip and also winrar, they both get errors while trying to unzip.
[Nook Color Android Development] rawfish:
If I am unable to boot all CWR-SD variations (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] rawfish:
The only problem I encountered was not having sufficient space on my HDD during the unzipping process. Aside from that, the file extracted successfully for me.
[Nook Color Android Development] thecubed:
Simple test to see if you made the SD right:

1. What SD reader did you use? Ones built into a laptop have limited success (for me, Lenovo T61p, no bueno)

2. If you used a USB reader, check to see if you have the file called "MLO" and "u-boot.bin" in the root of your sdcard.

If you've tried different SD readers and you've got the proper files on the SD card, there's a possibility that there's some gunk in your Nook's SD reader slot. Give it a shot of compressed air, that should help.

If all else fails, I'm contemplating a USB bootloader-like scenario... although I still have to flesh that idea out in the IRC channel with people much smarter-er than I am.
[Nook Color Android Development] jvrobert:
Just like to say thanks, this worked like a charm. I had some issues with Auto-nooter (for some reason, Market would not actually download anything - it would hang with 0 progress). Following instructions and using this was a little more transparent to me, and it also solved my issue with market.

Maybe I'm just "special", but my only issue was I downloaded the wrong .img file at first because it wasn't clear to me, so might save some headaches to make it clear that the [x]gb_clockwork-0.7 files aren't for rooting ;)
[Nook Color Android Development] thecubed:
Hm. Thought it was clear that the "rootpack" was the whole kit, and clockwork was just that, clockwork.

Oh well. I'll see if I can make that clear-er-er. :)

(121gb of rootpacks served this week! WOW.)
[Nook Color Android Development] jttraverse:
Flashed fine, but now always boots to CWR

My Nook was v1.1 and I'd tried Autonooter and gotten it rooted. Was still having problems with ADB, and then saw the Monster Root Pack. So I thought I'd reroot the thing with the Root Pack to see if a new shot at it might do something

I flashed the Monster Root Pack 0.7, and though it seems to have gone perfectly, now I cannot get it to boot to anything other than back to CWR. It tries to boot, but shows the 'n' for a split second and then some extraneous looking characters or something blinks for an instant on the right side of the screen and with that the thing just drops back to displaying the CWR menu.

Even downloading a flashable Froyo image, burning it to the SD card, and then booting the Nook and letting it install the froyo version from the SD card worked perfectly, I thought. On rebooting the device it simply pops back to CWR. It doesn't even try to boot the Froyo image that was just flashed to it! (and yes, the SD card is removed at these times).

Anyone have any idea what my problem may be. This is gettin' old...ug.

-JTT
[Nook Color Android Development] thecubed:
Use the removeclockwork.zip file. It'll reset your device's recovery to stock.

I'm not sure at all why it's not working on 1.1 stock devices.. I think i need a dump of the 1.1 stock device's /boot partition to take a look at it's u-boot and whatnot.
[Nook Color Android Development] rawfish:
1. I used 2 different external readers, the same ones I used to successfully burn working uSDs, before the 'Big Blackout' issue.

2. Yes, "MLO" and "u-boot.bin" are present. Have also verified the file structure integrity, in Ubuntu - I do not see anything wrong.

3. I'm bringing home a big can o' air duster from work today, it's worth a try :)

Thanks for all your suggestions! And any form of help is definitely welcome. If there's anything you need from me to resolve this type of scenario, let me know too (PM, IRC, etc.) - it'll benefit others too.
[Nook Color Android Development] thecubed:
Hm.

1. Well you say that autonooter worked on it once, and it booted from that SD once upon a time... so we know that your SD reader works..

2. You see the right files, so the SD burn worked.

3. Your device does indeed turn on, and is able to turn off, so the device isn't /completely/ borked...

Which leads me to a potential #4: Do you see "Touch the future of reading..." or "Loading" on the screen?

If you see "Loading", then do you see the skulls? If you do, that means that my SD card is indeed booting. (Skulls are part of the bootloader installed on the SD card- skulls courtesy of fattire!)

If you do see the skulls and it never boots, that could potentially mean that there is something reeeally wrong with your partition table and clockwork is having trouble starting.

If you instead see "Touch the future of reading.." or another "Loading..." screen without skulls it means the device isn't even considering the SD card as a boot device. Which would mean to me something is physically wrong; potentially the SD card socket is broken.

Post back here, and I'll see if we can continue this process of elimination...
[Nook Color Android Development] rawfish:
4. Yes, you are right:

a) With CWR-SD uSD inserted: the 'LOADING' text between 2 skulls (splash page) shows, then device screen blacks out

b) With a Froyo/HC-SD from burned SD: the 'LOADING' splash page loads too, and again the screen blacks out

c) Without any SD inserted, I see the standard 'Touch the Future of Readin' page, then yet again the blackout

*at any time the blackout happens, nothing loads, and I know the device is still in ON mode, because holding the power-button results it to go to a true OFF state. Thereafter holding power (or a USB connection established) will result in the device attempting to power up again.

This conclusion should seem logic: SD slot is still functional - but something reeeally wrong may have happened to my partition table. This is what happened:

Purchased 1 week ago, before stock-out event -> From OOBE (1.0) -> B&N 1.01 -> Root -> gApps > modified build.prop -> installed rom manager from market -> installed CWR-internal from rom mgr -> reboot to CWR -> No issues -> HC v4-SD -> manual su and symlinking via adb -> gApps -> still ok -> dalingren's HC OC 1.1 -> still ok -> reboot -> still ok -> adb shell to check on symlinks -> sudden reboot to B&N 1.01 even with uSD inside -> manual reboot -> goes back to HC -> HC loads after 'LOADING' splash -> *forgots exact events, hang perhaps?* -> blackout problem occurs

I have searched quite a bit since then for an unbricking solution, with no positive results. Thanks for all your help, really appreciate this discussion :)