[ROM][CM7] [v1.3] Size-agnostic SD Card image and CM7 installer for SD Cards.

Search This thread

robot8

Senior Member
Apr 4, 2011
111
20
just got the nook color and wanted to mess around with cm7 on it. I downloaded the installer image provided by verygreen, but after I copy the image to the sd card and put it back in its not mounting the sd card anymore.

I tried to burn the image in windows using win32diskimager but it kept telling me there wasn't enough space on the sd card. So i booted into ubuntu and used
sudo dd if=generic-image.img of=/dev/whatever the sd card was bs=1M

Did i copy the image over incorrectly? or is there another reason why this could be happening?

thanks.


If you had followed the OP instructions you should have been fine. Right now you've "copy the image to the sd card" and then "tried to burn the image in windows" and then "booted into ubuntu and used sudo dd", I'd say your sd card is pretty messed up.

I'd mount your sd card to your computer with a card reader. Reclaim full with a partition manager, format fat32. Then burn verygreen's installer img to the card with win32diskimager. Remove, then reinsert card to card reader. Copy CM7 .zip to "boot" (only partition you'd now see in Win), remove sd card and insert into Nook. Power on and let it install.
 

japzone

Senior Member
Dec 25, 2010
592
265
just got the nook color and wanted to mess around with cm7 on it. I downloaded the installer image provided by verygreen, but after I copy the image to the sd card and put it back in its not mounting the sd card anymore.

I tried to burn the image in windows using win32diskimager but it kept telling me there wasn't enough space on the sd card. So i booted into ubuntu and used
sudo dd if=generic-image.img of=/dev/whatever the sd card was bs=1M

Did i copy the image over incorrectly? or is there another reason why this could be happening?

thanks.

I agree with robot8. I would use Ubuntu because it's alot more cooperative when it comes to this.

If you don't have GParted installed get it with this command in terminal:
Code:
 sudo apt-get install gparted

Use GParted to Reformat your entire SD to FAT, and then use dd to burn the Image to your card.

Now resume the instructions and you should have working CM7.


____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
 

angomy

Senior Member
May 4, 2011
294
102
just got the nook color and wanted to mess around with cm7 on it. I downloaded the installer image provided by verygreen, but after I copy the image to the sd card and put it back in its not mounting the sd card anymore.

I tried to burn the image in windows using win32diskimager but it kept telling me there wasn't enough space on the sd card. So i booted into ubuntu and used
sudo dd if=generic-image.img of=/dev/whatever the sd card was bs=1M

Did i copy the image over incorrectly? or is there another reason why this could be happening?

thanks.


When you copied the image to the SD card, did you mean an actual copy action, or did you burn the image to the SD card using win32diskimager?

If your initial attempt to burn the image via win32diskimager was as follows:
- Inserted uSD into uSD reader
- opened windisk32imager and tried to burn the img file to the uSD and was given an error message of not enough space

The issue might be that your reader might be problematic. Is it built-in? My built-in reader in my laptop gives me the same (false) error message. When I connect the reader to one of my front-panel USB ports, I get the same error message as laptop's. When I use a standalone reader connected to one of the main USB ports on my desktop, it works fine.


If you actually did burn the img to the SD card ("after I copy the image to the sd card"), which device were you "putting it back in its not mounting the sd card anymore. "? The Nook or the reader?
 

jpiermarini

Member
Aug 9, 2010
9
0
If you had followed the OP instructions you should have been fine. Right now you've "copy the image to the sd card" and then "tried to burn the image in windows" and then "booted into ubuntu and used sudo dd", I'd say your sd card is pretty messed up.

I'd mount your sd card to your computer with a card reader. Reclaim full with a partition manager, format fat32. Then burn verygreen's installer img to the card with win32diskimager. Remove, then reinsert card to card reader. Copy CM7 .zip to "boot" (only partition you'd now see in Win), remove sd card and insert into Nook. Power on and let it install.

Let me rephrase what i have said in my original post. i put the sd card into my laptop that has a built in sd card slot. i tried to burn the image with win32diskimager but it gave me an error saying the sd card didn't have enough space. according to angomy's post a couple posts down i'm probably getting that error because i'm using the built in sd reader.

after failing at win32diskimager i then booted into ubuntu and burned the image with the dd command. after burning the image with that command the sd card doesn't come up in ubuntu although i can see it with fdisk -l and when i try it in windows it pops up as needing to be formatted.

i'll go ahead and use gparted to get the sd card back to normal and maybe try to find an sd card reader here at work.
 

japzone

Senior Member
Dec 25, 2010
592
265
Let me rephrase what i have said in my original post. i put the sd card into my laptop that has a built in sd card slot. i tried to burn the image with win32diskimager but it gave me an error saying the sd card didn't have enough space. according to angomy's post a couple posts down i'm probably getting that error because i'm using the built in sd reader.

after failing at win32diskimager i then booted into ubuntu and burned the image with the dd command. after burning the image with that command the sd card doesn't come up in ubuntu although i can see it with fdisk -l and when i try it in windows it pops up as needing to be formatted.

i'll go ahead and use gparted to get the sd card back to normal and maybe try to find an sd card reader here at work.

That's probably best.

____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
 

TabletConnect

Senior Member
Aug 8, 2010
292
26
tabletconnect.blogspot.com
My wife got a Nook Color and I just want to confirm that doing creating this CM7 installer on the SD card will basically allow her to dual boot (stock Nook & CM7). The NC will run CM7 if the SD card is installed. If it is not, regular stock Nook will boot. Am I correct in understanding this?

If not, where can I find information on setting up a bootable SD card with CM7?

thank you all
 

cameraz

Senior Member
Feb 3, 2011
206
9
My wife got a Nook Color and I just want to confirm that doing creating this CM7 installer on the SD card will basically allow her to dual boot (stock Nook & CM7). The NC will run CM7 if the SD card is installed. If it is not, regular stock Nook will boot. Am I correct in understanding this?

If not, where can I find information on setting up a bootable SD card with CM7?

thank you all

You're in the right thread, and your assumptions are correct. Your wife's Nook Color will run CM7 with the SD card installed, and will revert back to stock if she powers off, removes the card and then reboots.

It's the best of both worlds!
 
  • Like
Reactions: TabletConnect

angomy

Senior Member
May 4, 2011
294
102
My wife got a Nook Color and I just want to confirm that doing creating this CM7 installer on the SD card will basically allow her to dual boot (stock Nook & CM7). The NC will run CM7 if the SD card is installed. If it is not, regular stock Nook will boot. Am I correct in understanding this?

If not, where can I find information on setting up a bootable SD card with CM7?

thank you all

This will allow you to create a CM7 install on SD card.

(Oops I misread your post, running on 4 hours of sleep today) -- feel free to ignore below if you don't care about multi booting :)

If you want dual boot functionality you will need to get either of the two multi-boots offered here and install it after finishing the agnostic card setup:

rookie1's multi-boot - no menu, depending on how you write the boot order file it will let you boot normally into SD, into EMMC (regular Nook stock) when you hold down N button, and recovery mode when you hold down both volume keys. You can switch the priority boot order by creating and editing a file.

http://xdaforums.com/showthread.php?t=947698&highlight=multi-boot

j4mm3r's multi-boot has a menu. When you boot up you have 5 seconds to hit a key to manually select what to boot from (sd vs mmc vs recovery). If left alone it will boot to w/e default you have it set (see his instructions in:)

http://xdaforums.com/showthread.php?t=962708&highlight=multi-boot

Alternatively, you can do the 2GB expandable sd install w/ j4mm3r's multi-boot menu already incorporated -- but if you're using a 16GB+ card be forewarned that some have had issues (works fine 8GB under).

http://xdaforums.com/showthread.php?t=1022786


I'm using the size-agnostic image with CM7 and nookie1's multi boot on a 16GB Sandisk, it's working fantastic.
 
Last edited:
  • Like
Reactions: TabletConnect

TabletConnect

Senior Member
Aug 8, 2010
292
26
tabletconnect.blogspot.com
You're in the right thread, and your assumptions are correct. Your wife's Nook Color will run CM7 with the SD card installed, and will revert back to stock if she powers off, removes the card and then reboots.

It's the best of both worlds!

This will allow you to create a CM7 install on SD card.

(Oops I misread your post, running on 4 hours of sleep today) -- feel free to ignore below if you don't care about multi booting :)

If you want dual boot functionality you will need to get either of the two multi-boots offered here and install it after finishing the agnostic card setup:

rookie1's multi-boot - no menu, depending on how you write the boot order file it will let you boot normally into SD, into EMMC (regular Nook stock) when you hold down N button, and recovery mode when you hold down both volume keys. You can switch the priority boot order by creating and editing a file.

http://xdaforums.com/showthread.php?t=947698&highlight=multi-boot

j4mm3r's multi-boot has a menu. When you boot up you have 5 seconds to hit a key to manually select what to boot from (sd vs mmc vs recovery). If left alone it will boot to w/e default you have it set (see his instructions in:)

http://xdaforums.com/showthread.php?t=962708&highlight=multi-boot

Alternatively, you can do the 2GB expandable sd install w/ j4mm3r's multi-boot menu already incorporated -- but if you're using a 16GB+ card be forewarned that some have had issues (works fine 8GB under).

http://xdaforums.com/showthread.php?t=1022786


I'm using the size-agnostic image with CM7 and nookie1's multi boot on a 16GB Sandisk, it's working fantastic.

Do I need to be rooted before doing this? Thanks
 

Taosaur

Senior Member
May 4, 2011
836
190
Ohiopolis
taosaur.blogspot.com
Do I need to be rooted before doing this? Thanks

As angomy said, you should probably ignore the things he posted because they don't apply to your situation. You do not need to root or otherwise disturb the operating system on your NC; if you follow the instructions in the OP of this thread, you will have CM7 running entirely from an SD card. You may want to consult this thread about an appropriate card to use:

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

If you have any trouble, this blog post includes more step-by-step instructions as well as a five-part video of the process:

http://www.anamardoll.com/2011/04/ereader-running-cm7-firmware-on-nook.html

All the paragraphs leading up to "Here is a list of all the things you will need" are a rambling introduction you can probably skip, as is the first video, but from there on it's quite helpful.
 

angomy

Senior Member
May 4, 2011
294
102
Do I need to be rooted before doing this? Thanks

Edit: (If you mean CM7 + Nookie1's multiboot, or the 2GB expandable w/ multiboot install) - No, but it requires that you fiddle with files instead of just running the installers :) My install is entirely on the card, nothing's been done to touch the stock OS on the Nook's native drive.
 
Last edited:

paschott

Senior Member
Mar 12, 2006
83
5
Dallas
Is there an easy way to see the large partition of the SD card when dual-booting into the default Nook OS? It sees the card, but seems to only see the "boot" partition from the Nook OS. I'd love to be able to use the whole card if possible. Any ideas on ways to do that without rooting my Nook? Every suggestion I've seen implies that I need to root first and I really don't have a desire to do that right now.

Thanks.
 

GTT1

Senior Member
Apr 16, 2011
158
14
FROM OP
""How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.
""

I have tried and tried and cannot get this to update my SD. I know the CM7.0.3 file is good because I tested it on another card.

I guess I need to start from scratch unless someone has a thought on what I may be doing wrong.
 

Taosaur

Senior Member
May 4, 2011
836
190
Ohiopolis
taosaur.blogspot.com
Is there an easy way to see the large partition of the SD card when dual-booting into the default Nook OS? It sees the card, but seems to only see the "boot" partition from the Nook OS. I'd love to be able to use the whole card if possible. Any ideas on ways to do that without rooting my Nook? Every suggestion I've seen implies that I need to root first and I really don't have a desire to do that right now.

Thanks.

Based on the thread, I'll assume by "dual-booting" you mean you're running CM7 from SD and the stock OS 1.2 from eMMC. If that's the case, are you aware that CM7 running off the SD does recognize the 5GB storage partition on eMMC? If there are files you want shared between the two OSes, you do have that much space available. If you need more space for magazines or kids books from B&N, you could always get a second card and swap.
 

Techienana

Senior Member
Feb 10, 2011
89
6
FROM OP
""How to update to a new build:
put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.
""

I have tried and tried and cannot get this to update my SD. I know the CM7.0.3 file is good because I tested it on another card.

I guess I need to start from scratch unless someone has a thought on what I may be doing wrong.

I was thinking of something you could try but I don't think I know enough about your problem to put my thought out here. Can you give a little more detail?
 

Taosaur

Senior Member
May 4, 2011
836
190
Ohiopolis
taosaur.blogspot.com
I guess I need to start from scratch unless someone has a thought on what I may be doing wrong.

It took a couple tries, but I just got 7.0.3 installed myself. Like Techienana said, it's hard to know if you're doing anything wrong without knowing what you've actually done. The steps are:

1. Place the update .zip file in the SD card's boot partition. If you are using a Windows machine, the boot partition will be the only one recognized. You cannot place this file in the boot partition from within CM7*

2. Return the SD card to your NC and boot into recovery by holding p+n for 3-4 seconds after the Touch the Future of Reading screen appears and then releasing (if the NC shuts off again, you held them too long).

3. A little penguin should appear in the upper left corner (landscape) followed by some text saying it's looking for update packages. If it finds one, you will see many many lines of text as it installs all the elements of the new ROM.

4. When the penguin says "safe to power off" or when the screen goes blank, power off then power back on. Things won't look any different, but go to Settings>CyanogenMod Settings>System and you should see you're running 7.0.3.

Did you definitely get the .zip into the boot partition? Did you successfully boot to the update/recovery screen with the penguin? If so, what did it say?

If the penguin detects your update package but does not install it successfully (as happened to me on round 1), you have to start at step 1, because it will erase the file.

*Except--and I can't confirm because I screwed up this time around--if you have automatic updates enabled, CM7 will download the update automatically, and offer to "reboot and install" WHICH DOES NOT WORK. However, none of the automatic "boot to recovery" options within CM7 work for me, so I'm guessing if I'd picked up at step 2 with a manual recovery boot, it would have installed.

Instead, I dl'ed the file in Windows, mounted the SD card, and tried to copy it over. The update...zip file wasn't visible on the SD, but Windows prompted me to Copy and Replace, then failed to do so, which I'm guessing corrupted the file. When I tried to boot, the penguin found the file but failed to install it, so I started over at step 1 and succeeded.
 

GTT1

Senior Member
Apr 16, 2011
158
14
Finally got it to work after different times releasing. For others it is just before the words go off the screen.

Might just start over again and reload everything clean including apps.
 

Awats

Senior Member
Apr 24, 2011
160
8
I got it work. Nice Taosaur!

I did notice the first time it didn't update and just went into the old build. I rebooted again and held the buttons down as long as I could stand it while the opening screen was up ("Touch the Future or Reading" .. yeah, touch this.

It's a bit of a game of chicken ... or penguin ... around how long you have to hold the buttons. Who's going to flinch first! I count to 5 after the TtFoR comes up.

Voila!

Edit: I have discovered that the success of this stuff is heavily dependent on the speed/quality of the SD card. I started with some 4GB Class 4 Patriots and had continual problems with things locking up, Forced Close, big delays, etc.

I got a Sandisk Class 4 2GB and things starting working. Especially when overclocked. I then got a Sandisk 16GB and things still worked fine. For fun, I tried the 4 GB Patriots again just to see if my lack of experience was the problem.

Nope, they just don't work right. I would assume it's related to the legendary 4kb block write performance. What works on the Sandisk won't work (or is at least very flaky) on the Patriots.

Maybe things are even better flashing to the internal emmc, but for now SD is how I roll.

I wonder if I can go backwards on builds (in case one doesn't work ...) Hmm....
 
Last edited:

paschott

Senior Member
Mar 12, 2006
83
5
Dallas
Actually, I was hoping to use more of the storage on the SD card for actual books and such. In general, I plan to use the NC as intended, as an e-reader. I don't have major issues with the software and so far performance for my Android on SD card has been pretty bad (haven't had/taken the time to investigate). I'd just like the option to use Android as desired by booting into that, but also have a lot of space for my books. I have a 16GB uSD, but when in the Nook boot, can only see the boot partition. Wondering if there's a way to change that so I can see more partitions or if I just need to find a way to resize that partition to make it more usable when I'm using the stock Nook ROM.

Thanks.
 

Moritzio

Senior Member
Nov 19, 2008
358
53
Great build and wonderful instructions. Worked without a hitch. Thanks very much for making the Nook Color more useful.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 165
    Due to popular demand I have created a size-agnostic SDCard CM7 installer.
    Also allows to install unmodified CM7 builds on SD card.

    Current version: 1.3

    Grab the installer image here:
    http://crimea.edu/~green/nook/generic-sdcard-v1.3.img.gz
    it's a ~9M image that would unpack into ~130M disk image.

    Also note - not all SD cards are created equal. Here is a thread of interest is you have not bought one yet: http://xdaforums.com/showthread.php?p=12964262
    Short version: buy Sandisk-branded class 4 microSD cards.

    Write the image on your SD card. I tested with 2G, 4G and 8G cards and all worked.
    Any uSD card of 1G or bigger in size should work if it is recognized by your nook.
    Write on Windows by using WinImage and on Linux/MacOS X by using dd (to the entire device, not one of the partitions. The device name should not have any numbers at the end. The command is something like dd if=/somewhere/generic-sdcard.img of=/dev/sdX bs=1024k)

    After done with writing, eject and then re-insert the uSD card into your computer.

    Download a CM nightly build from here http://download.cyanogenmod.com/?device=encore (It is recommended to choose -87 nightly or later. If you plan to use prior version for initial install, stick with installer 1.2.1 for a different u-boot version)

    Or just use your own update-cm-*-KANG-signed.zip file that is produced if you do your own builds.
    The image would correctly detect unmodified CM7 builds and would make necessary adjustments to make them work on SD card.

    Put the file to the SD card (there is only one partition). Don't change the name of the file.

    unmount the uSD card and insert it into the nook.
    Boot from this SD card. It'll boot and will update you on progress.
    When it's done, it'll power off.

    That's it, you now have CM7 on your SD card.

    How to install market and gapps:
    After you have booted into the CM7 on SD card for the first time and set up wifi access (important!)
    Go to http://wiki.cyanogenmod.com/index.php?title=Latest_Version and at the end there is a table with various google apps versions. Get the one suitable for your cyanogen version (CM7 is the latest for now). The file is named gapps-....zip
    shutdown your nook and take the SD card out, insert it into your computer.
    Copy the gapps-... file to the SD card on the first partition (titled boot) without changing the file name.
    Insert the uSD card back into the NOOK and boot into "Recovery mode" (hold nook N key and then press and hold power until the "Loading..." message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the bootloader "Loading..." message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long).
    Alternatively if you do not want to fight the timing, boot normally into Android, then from desktop hold power key until a poweroff menu appears, In the poweroff menu choose "reboot", in the next menu choose "recovery" and press "OK". The nook would reboot straight into recovery.

    How to update to a new build:
    put the new build you want to try on the first partition. (the name must be update-cm-*.zip or cm_encore_full*.zip or just update-*.zip)
    Boot from the SDcard in the recovery mode (see above) and the new snapshot would be installed.
    The partition layout would be preserved, filesystems are NOT reformatted, so your data should be safe.

    Installing other stuff:
    Booting in recovery mode would install all files that are named "update-..." and end with .zip The files would then be deleted! Most of the packages should work, but I only tested a subset and not entire syntax of updater script is implemented. Certainly format and delete are not implemented.

    OC Kernel installation instructions:
    Starting with v1.2.1 there are no special instructions, install normally as described above.

    Partition layout for the SD cards depends on size:
    Less than 600M - unsupported.
    up to 1G cards gets: system of ~300M and data of the rest of space. No FAT partition
    2G cards (more than 1G up to 1800M) gets: 300M system, 612M data, rest is FAT sdcard
    more than 2G cards gets: 460M system, 975M data, rest is FAT for sdcard.

    How to update if you already installed using older version of the installer and don't want to reinstall (understandably):
    • Get update zip from http://crimea.edu/~green/nook/update-genimage-1.3.zip
    • Put the zip file as is onto the first partition of your sdcard..
    • reboot into recovery (triggered by the keys, the reboot into recovery does not work yet).
    • The new version would be installed and you are done.
    • You can combine this installation together with updating to .32 kernel in one step. Just put the update-cm file and the update-genimage-1.3.zip to the first partition. Make sure there is still at least 1M of space left!

    Changes in 1.3
    • Install u-boot.bin and MLO loaders if provided.
    • Fixed a problem that led to overwrite of recovery kernel if a nightly was installed more than once)
    • (only in full image) updated u-boot to ignore BCB as that was a common source of problems. (that's why this version is not recommended for initial install with older nightlies, those don't provide a more correct u-boot for later operations. It's fine to do the update from older installer release, though)

    Changes in 1.2.1
    • Really fixed dalingrin kernel packages installation
    • A bit more robust handling of install scripts

    Changes in 1.2
    • Updated to new u-boot from B&N 1.2 update
    • Ability to obey BCB in eMMC (allows reboot into recovery from CM7)
    • Hopefully simplified the timing to trigger recovery boots from keyboard
    • Added support for Dalingrin's kernel update packages

    The v1.1 version that is known good to work with 2.6.29 kernel releases is located at http://crimea.edu/~green/nook/generic-sdcard-v1.1.img.gz
    20
    I thought I would share something that I finally figured out. I have been trying to find a way to mount the sd card boot partition without removing the card or booting to emmc. I wanted to do this so that I could download the nightly on the nook and put it directly in the boot partition. I figured out a way and it works great.

    Use a root file manager to create a new folder in /data. I called mine sdboot. Then create a blank text file. I named mine 19mountsdboot (with no .txt on the end!). Then I put the following text in it and saved it:

    #!/system/bin/sh
    # mount SD boot partition
    busybox mount -t vfat /dev/block/mmcblk1p1 /data/sdboot;

    Copy that new file to the /etc/init.d folder using your root file manager. Change the permissions to match the other files there. Now reboot the nook.

    When finished booting, you should be able to use your root file manager to go to /data/sdboot. And you should see your boot files there. (Don't mess with them.)

    Now you can copy the nightly zip there. Then reboot to the verygreen recovery and your nightly should install.

    All this without taking the card out or booting to emmc or hooking up to your PC. And it should stay that way even after flashing new nightlies to the sd.

    Edit: I attached the file here in case people were having trouble getting it right. Just unrar and put in the /etc/init.d folder and change permissions. You still need to create the folder in /data first.

    EDIT 2: I just modified the file to automatically create the directory and mount it. Just unrar and put the file in /etc/init.d folder and fix permissions. No need to create the new folder. Or better yet, I created a flashable install zip that does everything for you. You only need to flash it once (for SD installs). It will survive flashing of new SD nightlies. It can also be flashed to emmc and will mount the SD boot partition, but only if an SD install SD is in the slot. It will recognize an ordinary SD and not try to mount the SD boot partition. However, if you want to keep this on emmc, reflash after every emmc nightly flash.

    EDIT 3: Just found a problem with the install zip. Needed to have the permissions set properly. Should be all fixed now. Use the rev. 1 zip

    EDIT 4 (6-13-12): Added Rev 2 of the script and install zip. Rev 2 adds a symlink to the root directory so that 'sdboot' shows up in the root directory as well as in /data/sdboot. You can manually install the script to the /system/etc/init.d folder. Just unrar it and put it in that folder and set the permissions to execute. If you do not feel comfortable manually installing the script, put the zip in the boot partition and reboot to recovery and it will install it automatically for you. And you do not have to re-flash again after a new ROM flash. (If you previously had installed a prior version to /data/local/init.d, manually remove it before you flash the new version. If you don't you will have two copies on your system and that sometimes causes Root Explorer to lock up.) This version works great to direct download your new zip to sdboot with the new Goo Manager. Just change Goo Manager's download directory to /sdboot/ and it will put it on your boot partition.
    13
    Updated SD image for CM9/CM10

    [Update 10-17-12] Updated installation instructions for putting CM9/CM10 on SD have been posted here. And updated image to Rev 5 to fix an issue with installing CM10.

    [Update 8-21-12] Rev 4 of image and boot files attached.

    I updated the image and boot files to better accommodate CM10 and JellyBean gapp zips and provide bigger /data partitions for larger sized SD cards. The boot partition is now 300MB so the larger CM10 and JB gapps zips will fit. And now all SD cards 8GB and larger will have a 2GB /data partition to accommodate more installed apps. Thanks DizzyDen for that suggestion.

    [Update 6-13-12] Rev 3 of image and boot files attached.

    When updating Rev 2, somehow the duplication fixes got removed. Rev 3 restores the duplication fix along with the naming fixes.

    [Update 5-09-12] Rev 2 of image and boot files attached (Replaced with newer version).

    A pending change that the CM team is implementing will adversely affect verygreen SD users. They are changing the naming standard for new nightlies. They will no longer be naming the files starting with update-. That means the existing install script will no longer recognize or install a new nightly when it is copied to the boot partition. Users must rename the file to start with update- if they want the existing install script to work.

    In order to assist users I have modified the install script to now also install nightlies if they begin with the new standard (cm-). I also added to the script the ability to recognize the new prefix (diff_) that is used by the new Goo Manager program to make an incremental update to an existing ROM. (Edit: The new script will continue to recognize and install zips beginning with update- to provide backward compatibility.) I have attached new rev2 files (replaced with newer version) that are to be used as described in the original post below.


    --------

    I have made new boot files for SD install users. They have been modified to fix the Google App duplication issue with CM9 and Google Apps. The revised script in these files will look to see if you have installed the Google versions of Calendar, Gallery, and QuickSearchBox. If you have them installed it will remove the versions that come with ICS/CM9 so that two versions of those apps will no longer show in your system.

    I have attached two files.

    The first is a revised generic image file for use if you have never set up your SD. It has the new boot files in it. It also has the larger partition so that the CM9 nightlies will fit. Just follow the instructions in the first post of this thread to learn how to install it.

    The second file is the revised boot files themselves. This is for use if you have already set up your SD and you just want the new scripts to fix the duplication issue. To install these files, just go to your boot partition and rename two files, uRecImg and uRecRam. Just add .bak to each file. The attached file is a rar containing the new files. Just unrar and copy the two files to the boot partition to replace the files you renamed earlier. The next time you install a nightly, the script will do its checking and remove the duplicates if necessary.

    Enjoy
    7
    I uploaded the v1.2 update and updated the first post.
    Check the "recovery boot" instructions, they are changed and I believe together with the updated u-boot binary the triggering of it should be easier (even with older u-boot binary updated sequence of events is probably more robust).

    For those who want to upgrade I provide update zip that would do the updating, no need to replace files by hand anymore.
    I tested the upgrade and it works. Also supported is simultaneous u-boot upgrade + update to .32-kernel based image from dalingrin.

    The new image with 2.6.29 kernels is untested! But it might still work, i guess.

    Enjoy.
    4
    Just to let everyone know, I've uploaded a fixed version of this install image that will work better with Ice Cream Sandwich builds -- it'll no longer require you to flash sneakpeek1 first, and you won't have to rename the gapps. It's available for download in the Ice Cream Sandwich Nightlies thread. Huge thanks to Verygreen for helping me get it fixed.