yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] ganovim:
update-softkey-240dpi-5-06-Rev16.zip

My copy is good , since it worked when I used the old sd setup.

I will give it another shot. And in the meantime, thanks again for all your

contributions and followups.
[Nook Color Android Development] sdho:
leapinlar,

I'm not sure verygreen is still active but you know of a way to repartition /data to 1.5GB or 2GB? My kids' books are filling up 1GB very quickly.

Thanks in advance.
[Nook Color Android Development] leapinlar:
Backup your SD media to your PC. Then put your SD card in the PC and use a partitioning program like Mini-Tool Partition Manager (free on web) to shrink partition 4 by a GB or so. Take it off the front of the partition so there is free space between partition 3 and 4. Then expand partition 3 to fill the empty space. Hopefully all your data will remain intact and you don't have to use your backup. Put it back in the Nook and reboot and your sdcard should be smaller and your internal storage larger.

Edit: Why are kids books filling /data? I thought books either went to emmc or sdcard.

Sent from my NookColor running ICS and Tapatalk
[Nook Color Android Development] bobtidey:
I thought for the Nook reader application it does use /data to hold the content. This was one of the reasons that on later stock Nooks they changed from a 1G data 5G emmc to a 5G data 1G emmc.

Edit: I just double checked on my Nook running from internal memory and the content seemed to go into a Nook folder on the sdcard. So either my understanding was wrong or it depends on whether an sdcard partion is present or not.

Edit2: I think the difference may be between ordinary books (ePubs) and childrens' books which are effectively apps to give the interactivity and therefore get stored on /data.
[Nook Color Android Development] sdho:
yeah, bobtidey is correct. These are interactive books (apks) that are stored on /data partition. I can move them to SDCARD using the applications menu but it gets really slow on boot. Let me try Mini-Tool Partition Manager. Thanks
[Nook Color Android Development] leapinlar:
That makes sense. I wondered why they made it bigger.
[Nook Color Android Development] therkr:
Sorry if this has been asked before, but I think I've seen an improved version of this SD script (for CM9) in the early days of cm9 development.

I tried to search but it returned nothing.

So my question is, will this be sufficient to run CM9 builds by samiam/eyeballer on the sdcard, or do I need something else?

Thanks.
[Nook Color Android Development] leapinlar:
Look at my tips thread in my signature. There is a link there for the updated version. And it works fine with those cm9 builds.
[Nook Color Android Development] bachikho:
why i can only use eyeballer's cm9 builds with this sdcard img but not with samiam303's ones?
[Nook Color Android Development] leapinlar:
Have you tried Sam's? They should work. If they are not installing, the only thing I can think of is how he is naming his. They should be named with update- at the beginning. It can be named other things, but update- is the best.

Edit: I just checked his, they are named update-. Why do you say they don't work?
[Nook Color Android Development] bachikho:
everything is ok with eyeballer's builds but with samiam303's ones, they cant boot, what's wrong?
[Nook Color Android Development] leapinlar:
You mean they install ok, but just don't boot? Do you watch for error messages during installation? They should work. Maybe they are not downloading right on your system. Or could be a problem with the latest build. Look on his thread and see if anyone is complaining. Try an older one. There should be nothing in the SD script causing his to not work and eyeballers to work.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] fastoy:
I used this thread successfully to build an SD card for my NOOK Color that ran CM7 and have used it ever since. Thanks so much for the help.

Now I'm ready to move to CM9. Is there a similar thread for building an SD card for my NOOK Color that will run CM9?

There seem to be lots of discussion around CM9 but it's always a side topic. It seems you have to pull a download from here and an image from here.

Did I miss the CM9 for NOOK Color thread?
[Nook Color Android Development] leapinlar:
There is not a separate thread for putting CM9 on the verygreen SD setup. Verygreen has not been active on the nook color scene since mid-last year. So he has not updated his original post. However, with minor modifications his script works on CM9. I have modified his image so it works great with CM9. Just follow his directions in the first post of this thread, substituting CM9 when it says CM7. Only don't use the image file posted there. Use my modified image file linked in my tips thread in my signature.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] bachikho:
i've updated the image to rev2 and everything's fine, many thanks!
[Nook Color Android Development] fastoy:
Thanks for keeping the Nook Color alive using uSD.

Is this the SD image file you recommend? generic-sdcard-v1.3-ICS-large-Rev2.zip from http://xdaforums.com/attachment.php?attachmentid=1051784&d=1336620009

Where do I get the CM9 nightly build? The OP points to http://download.cyanogenmod.com/?device=encore but that's all CM7.

I found this http://android.sphsolutions.net/Encore/Nightlies/CM9/. Is this the CM9 nightlies I should use?

Should I get the Google apps from here http://goo.im/gapps/latest?
[Nook Color Android Development] leapinlar:
Those look all correct. But I recommend using the CM9 from here:

http://techerrata.com/browse/nightly_kangs/encore

Pick the newest that does not say opengl.

And for gapps here:

http://goo.im/gapps

Pick latest ics version.
[Nook Color Android Development] HTC-187:
I'm not able to create the bootable SD card. What am I supposed to do. I have downloaded installer (generic..v1.3.img.gz). I have downloaded one of the images, and I have installed WinImage. I'm using win7 64-bit. and I can't do anything with WinImage. How am I supposed to use the img.gz, the instructions aren't helpful and I didn't see anything in the first few pages to help with this.

Thanks for any help.
[Nook Color Android Development] leapinlar:
You have to unzip the file with an archive program like winzip. And don't use winimage to burn, use win32diskimager (free). There is a simplified guide that Taosaur prepared to help newbies. He has links to my updated image file there, use that.

http://taosaur.blogspot.com/2011/09/running-cyanogenmod-7-from-sd-nook.html?m=1
[Nook Color Android Development] Homer_S_xda:
Hey Leapinlar,

I noticed the date on the two files gets updated after flashing a nightly. Do your files get replaced after every flash? I have to add "update-" to the start of the filename for it to flash after the first time.

Homer
[Nook Color Android Development] leapinlar:
The date on the original files? During the flash of the first ROM, the original uImage and uRamdisk files get renamed to uRecImg and uRecRam and become your recovery files. The flash puts new uImage and uRamdisk files from the installation zip there and they become your kernel and ramdisk. They get updated with every ROM flash, so those dates will always change. But your original files stay there as uRecImg and uRecRam and the dates on those do not change.

You need to update the uRecImg and uRecRam files to my latest version. I have modified them to recognize the new CM naming standard of cm- instead of update-. But the new script continues to recognize the old naming scheme too. Go to my tips thread linked in my signature and there are links there that tell you how to upgrade.
[Nook Color Android Development] Homer_S_xda:
Ah... that explains it.

I must have gotten a bad download. The files are named uRamdisk and uImage in mine. I just downloaded a fresh copy, same name BTW, and the files are named as you state.

D'oh! and Thanks!

Homer
[Nook Color Android Development] Homer_S_xda:
Is it possible to do this somewhere besides under /data? I played around with trying to get both your file and Goomanager to point to the same directory with no luck. Any suggestions?

Homer
[Nook Color Android Development] leapinlar:
Yeah I tried the same thing with no luck. The problem is Goo Manager has to point to your SD card and the SD card is not mounted yet when my script runs so sdboot cannot be created there. I have not tried emmc, but I suspect the same problem exists.
[Nook Color Android Development] patgnds:
Have you used NookColorUMS_1.0 You can mount boot. tested this with Joy sd card, worked great.
[Nook Color Android Development] leapinlar:
Yes, but it mounts it to the PC, not to the nook. I used it all the time until I developed my script. In fact, I modified that program to also work on CM9. See my tips thread in my signature.
[Nook Color Android Development] DizzyDen:
Not sure I follow what's the last couple of questions... but... why can you not create /sdcard/boot and mount /dev/block/mmcblk1p1 to it? This is how I update using adb wireless... then the boot partition is available as /sdcard/boot
[Nook Color Android Development] leapinlar:
You can do that. But that requires that you are already booted. What we were talking about was doing it during boot as an init.d script so that it is there waiting for the user to have available to copy a new nightly whenever they want to. I have a script that does that, but it mounts it to /data. And Homer was asking if I could change it to mount to sdcard. He wanted it there so Goo Manager could download there directly and not have to copy later to the boot partition mounted in /data. I told him I did not think it was possible.

Maybe symlinking so that Goo Manager could see it? Any ideas would be welcome.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] leapinlar:
Homer, I've played around a lot and the best I've been able to come up with is the sdboot directory can be symlinked to the root directory so that you don't have to migrate through the /data directory to get to it. Goo Manager still will not download to it. It tries, but crashes. But you can access it without a root file manager now.

If people are interested in this version I could post a revised version to my original post.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Homer_S_xda:
Thanks for trying! I was hitting similar issues. The script can only access /data as I assume that is what the system has mounted when the script is running and GooManager won't accept a path in /data.

Oh well, thanks again for the script and for trying. I have to continue with the step of moving the file manually but at least I can do it all on the Nook and no longer have to rename.

Would say Root Manager follow the symlink? If so, linking to the ../GooManager directory would at least make the move one step. If that works, you could add the couple of lines to the script and leave them commented out. That way, people can use it as is and those with GooManager are *probably* savvy enough to uncomment them. Just a thought.

Homer
[Nook Color Android Development] leapinlar:
Hooray! Big time edit! I got it to work. It was just a matter of getting the permissions right.

I went ahead and posted the new version to my original post here.

This version adds the symlink so that it shows up in the root directory as 'sdboot' as well as under /data/sdboot. Just change Goo Manager to download directly to 'sdboot' and it will download to your boot partition. I would suggest that you check in sdboot to be sure it downloaded correctly before you reboot.
[Nook Color Android Development] garretwilson:
can't upgrade to CM7 7.2.0 on Nook Color

I'm trying to upgrade to CM7 7.2.0 using the bootable SD card. Months ago I successfully updated to 7.1.0.

I downloaded the cm-7.2.0-encore.zip file, placed it in the root of the first partition, and rebooted into recovery mode. It looks for things and then shuts down. I even renamed it to "update-cm-7.2.0-encore.zip" and then "update-cm-7.2.0-encore-signed.zip" to no avail.

The recovery mode script says "let's see if you have gapps, too" or something to that effect, but nothing seems to be installed---it says something like "1+0 records in, 1+0 records out" or something and then shuts down.

How do I upgrade to CM7 7.2.0 on my Nook Color using the bootable SD card?
[Nook Color Android Development] leapinlar:
You were doing it right. Renaming the file to begin with update- should have worked. But if the file is still there after trying, it did not work. I suggest you update your script files to my latest version (rev 3). Look in my tips thread linked in my signature to see how to do that.
[Nook Color Android Development] garretwilson:
Actually, I had forgotten that the first drive that appears on Windows 7 via a USB connection is not actually the first partition on the SD card. After removing the SD card, inserting it into a reader, renaming the file to "update-*", and putting the file on the real first partition, it picked it up just fine.
[Nook Color Android Development] stolenmoment:
How about the following? Put this at the beginning of a script in /data/local/userinit.d:

if [ ! -d /sdcard/whatever ]
then
(sleep 60; $0) > /dev/null 2>&1 < /dev/null &
exit 0
fi

Replace whatever with your mount point.

And after this just put the mount command.

The redirecting of all I/O to /dev/null and the last & lets the script lurk in the background until /sdcard is mounted.

Sometimes being an old command-line hacker comes in handy...
[Nook Color Android Development] leapinlar:
Good idea. Thanks. But I just figured out how to make the original work so Goo Manager can download directly. See my earlier edit.

I'll tuck that one away for use in the future if I need it.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Android Development] Homer_S_xda:
I can confirm that this works perfectly. Now, we have one step for SDcard users.

Be sure and "Thank" Leapinlar!

Homer
[Nook Color Android Development] atr73:
Small boot partition. SOLVED

I have a 8GB microSD and my boot partition seems very small. Is this ok and normal? I know the update will be deleted but CM nightlies are increasing in size in the next updates I might run of space in my boot partition.

Issue solved by extending/resizing one of the partitions. I have four total.
[Nook Color Android Development] atr73:
I am stump. I am stuck with updating to the latest build. I did in fact put my microSD into a reader and drag/drop the file into the boot partition. The recovery reads the file and shutdowns after completing. (the file is deleted from the microSD) but once I boot back into android is not updated to the latest. I tried without renaming and renaming 'update-' with no go. Any suggestions, this did work fine before. Rev 3 updated fine.
[Nook Color Android Development] leapinlar:
If you adjusted any partition other than partition 4 after installing the SD the first time, you probably messed them up. Windows does not do well with Linux partitions, which p2 and p3 are. I recommend getting my whole rev 3 image file which is 203MB after burning it. Then start over. You will be ready to move on to higher versions of CM later if you want to.
[Nook Color Android Development] atr73:
I think you are correct. Lucky I made a backup. But my now I still unable to give boot partition more space. I can start over, waiting for jellybean. Any ideas? I used easeus and minitools with no go. My next idea is boot into linux and re-partition using microSD over USB at work monday.

My only problem now is the /boot partition is not allowing me to update cyanogen latest build. I loaded a stable and nightly separately and changing them with 'update-' prefix. It finishes and shutdown but doesnt update to latest.
[Nook Color Android Development] leapinlar:
It is installing correctly since it deletes the file. But if you messed up p2 or p3, the files may not have copied properly. Remember, the SD rom installer does not format p2 (/system) like happens with an emmc install. So if messed up, it stays messed up. I recommend you start fresh so that p2 and p3 are created new and are clean. By starting fresh I mean burn the newer image in my thread, letting it create new partitions and install the roms fresh.
[Nook Color Android Development] atr73:
I backup my install before messing around with the partitions. The reason I mess with the partitions was because I cant install the updates. I suspect my boot partition is too small. When the files extract during the nix screen it ran out of space or something.

Do you know any programs that will backup my apps including location? (which screen the apps belong)
[Nook Color Android Development] leapinlar:
How did you back up? What did you use?

If you are using the old image file the boot partition IS too small. That's why I keep suggesting you start over.

If you want to do a complete back up of your SD install, I can tell you how to do that so after a fresh image install and new partitions created, you can restore everything.
[Nook Color Android Development] atr73:
Alright, going to start from scratch. I backing up using MybackupPro and Titanium Backup. (Mybackupro can remember home screens)

I created an backup using win32 imager.

If I start from scratch using the generic image will I get something like this: 460M system, 975M data, rest is FAT for sdcard. (I have 8gb card)

Steps:

download: generic-sdcard-v1.3.img.gz

write: to SD card using win32 disk imager

download: CM7 (drag and drop into the boot partition)

Setup: Wifi and then install gapps using recovery procedure.

thank a handful for your help.
[Nook Color Android Development] leapinlar:
No, that is the wrong image file! That is the old one.

Use the one from here (Rev 3):

http://xdaforums.com/showthread.php?p=23153010

It is attached to that post.
[Nook Color Android Development] atr73:
thank you very much. totally missed that.
[Nook Color Android Development] atr73:
I successfully running the latest build. Most of my apps are installed. The only thing is the settings, none saved :(.

thank you
[Nook Color Android Development] rockyddroid:
I had a 8GB san disk card. After writing the image to it, I had just 115MB free.

Is that normal?
[Nook Color Android Development] leapinlar:
Yes that is normal. All the PC can see is the boot partition which on the original verygreen image is that size. If you have any thoughts of moving up to CM9 or higher in the future, you should upgrade to my newer image which has a slightly larger boot partition to accommodate the larger CM9 zips. You can get the new image by going to my tips thread linked in my signature (item B2).
[Nook Color Android Development] rockyddroid:
I did all that was asked except for the gapps part. But the touch screen is not responding! Please help. However when I popped the sd card out, it worked on the original B&N OS.
[Nook Color Android Development] leapinlar:
Since it works with stock, it's got to be your software you just installed. I would start over clean and see if you can get it to work. By clean I mean reburn the image and install the rom again. You did not say which rom you were using. That can be the problem too.
[Nook Color Android Development] rockyddroid:
I installed this one:

http://mirror.teamdouche.net/get/update-cm-7.0.0-encore-signed.zip

Can you please give me the link of the rom that works?
[Nook Color Android Development] leapinlar:
That is really old. Pick the one here that says 7.2.0.

http://download.cyanogenmod.com/?device=encore&type=stable
[Nook Color Android Development] rockyddroid:
How to write the image again?

If I format the disk, there's still 115 MB left.

---------- Post added at 02:14 PM ---------- Previous post was at 01:54 PM ----------

I think I gotta rename it starting it with 'update'
[Nook Color Android Development] DizzyDen:
Use win32diskimager and write the original card image back to the card... leapinlar has an updated SASD in his tips thread that allows the newer filename convention as well as avoiding having to resize partition 1 to allow for the size of newer ROMs... it is VERY NORMAL to have a small partition visible in windows.. it only shows the boot partition... that's where you drop updates and is used to boot the nook off sd... that is why it is small.
[Nook Color Android Development] rockyddroid:
How to get original sd card

I am done with burning this sd card. I want to get the original sd card as it was. How to do it?
[Nook Color Android Development] dcharleyultra:
Format it.
[Nook Color Android Development] pasdabeer:
I used this a while back, for some reason I can NOT get this SD card set up. Has anyone else been having an issue with win32 imager lately? Is there any other program that will work?

I've even tried the linux method, still cant get it to load correctly.
[Nook Color Android Development] leapinlar:
Yes, WinImage also works. But there can be many things that can cause the SD not to boot. Look at my item A9 in my tips thread linked in my signature.
[Nook Color Android Development] pasdabeer:
Thanks, ended up doing it on my netbook running kbuntu and made it work. For some reason my desktop with fedora wasn't doing the job.
[Nook Color Android Development] DizzyDen:
If you were using an internal SD reader/writer that could likely be the problem... cheap usb reader/writers seem to work without issue.
[Nook Color Android Development] tablo:
thank you quinxy.

One more question please, in the first post it reads:

However, I have unpacked the "update-CM7-dalingrin-OC-sd-033111.zip" and found the following:

system (folder)

META-INF (folder)

uImage

So does this mean I can just use the contained uImage file and without renaming the file per the first post instructions?
[Nook Color Android Development] quinxy:
All you care about is the uImage. In the first post he says the file is named "kernel", but I believe that's the way dalingrin used to distribute it (because I believe that's the way the build leaves things). So, yes, just rename your existing uImage (since you might find you don't like the new one, and may wish to go back to it), and then copy the new one over.

Q
[Nook Color Android Development] tablo:
Thanks for the info, quinxy. Just installed and here are my quadrant scores, if anyone is interested:

STOCK CPU

nightly 32 - 1548, 1689

dalingrin-OC-sd-033111 - 1317, 1572, 1584, 1650

OC'ed CPU @ 1.1

dalingrin-OC-sd-033111 - 1775, 1981, 2012, 2112, 2134
[Nook Color Android Development] verygreen:
Actually it does not matter, the kernel is the same.

The only difference is in scripts, but since the scripts are not used and we move the kernel in place by hand, it does not matter which one you pick.
[Nook Color Android Development] DizzyDen:
Since there are additional fixes in modules and this method does not quite function as an update, you will also want to use ADB to copy over contents of system to the NC if you want to use the added fixes included (tunnel, etc.).

Maybe Green can make the update process work with Dal's kernel update layout.
[Nook Color Android Development] bladerunner0427:
Bought a NC and installed CM7 on SD card. It's my understanding that nothing is changed internally in the NC and CM7 runs on the SD card. When you install an app from the Market, is that installed on the SD card automatically? When I check Storage in Settings, I see 2 headings titled "internal storage." I'm guessing that the one called "internal storage/mnt/emmc" is the NC internal storage. Is the other "internal storage" actually on the SD card set aside for applications?

Thanks.
[Nook Color Android Development] khaytsus:
It's ALL on the SD card. The first post explains the partition structure for different sized cards. There is a /data partition created (internal) and an /sdcard partition created (external).

From what I can tell, when booted up it uses /cache from eMMC and it makes the eMMC 5G /media partition available as /emmc.
[Nook Color Android Development] bladerunner0427:
That's what I thought. Thanks for confirming.