[Nook Color General] samuelhalff:
Well, in theory it's quite easy to do. Read the entire post before attempting the trick.

As usual, I'm not responsible if your NC starts speaking Flemish. Be careful with your Internal partitions!

Requirements: stock on internal, gparted, maybe my UMS utility (DEV), an SDCard (8GB at least, to be safe), a few minutes.

Partition an SDcard following stock layout.

You can partition the SD by using gparted. Create a new partition table, then create the partitions. Then apply. Don't forget to use "round to cylinder" and always leave a 1mb space at the beginning of each partition (except boot). Or else, you'll end up with corrupt partitions, writing over one another. Partition size can be changed, just make sure they're big enough..

Make sure the first partition has the bootable/boot flag.

To print the layout, use ADB command "fdisk /dev/block/mmcblk0 -l".

Or search for the layout in dev forum.

Layout looks like this (by heart, so check):

(Primary: )

p1: boot = FAT32 ~70 MB

p2: rom = FAT32 ~70 MB

p3: factory = ext2 ~??MB (this can left at 1mb, its a recovery partition, no use here)

p4: extended (not a partition strictly speaking, it's an extension)

(Logical: )

p5: system = ext2 ~470MB

p6: data = ext3 ~900MB (this can be bigger, app data storage)

p7: cache = ext3 ~350MB

p8: media = media FAT32 ~5GB (this can use all the remaining space, as big as you can/wish: media storage, books, films)

Then, you'll need to copy partition contents onto the SDCard's newly created partitions.

The easyiest way of doing it is by making .tar files of internal partition contents and extracting the files onto the SD partitions.

To create the tar files:

- either use <tar XXX.tar *> adb command on each partition, make sure you compress the actual content, not the container folder (i.e tar system content and not system, the * in the command stands for all content). Then pull the tar file. Delete it afterwards from internal!

- OR, probably more user friendly, use my USB mass storage utility found in DEV, mount each partition and create tar files with your usual UI (Ubuntu, Windows, OSX).

Copy every tar file onto your PC.

Tar files of internal partitions aren't all mandatory, all depends on if you want to make a complete backup of running stock rom, or if you just want the general stock rom on an SD. For instance, cache and media can be ignored, if you just want a general version. If you want to backup your media, tar media as well.

Then, extract each file onto the corresponding partition of you partitioned SD. Delete .tars afterwards from SD partitions.

THEN: download attached file, erase uRamdisk from you SD's boot partition and replace it with the one in the attached zip file (rename SD-STOCK-uRamdisk to uRamdisk). Without this step, your SD will boot from system and data internal partitions.

This uRamdisk has adb activated, so you should be able to push files to the SD once booted. Some internal commands won't work though (i.e, mount). You'll have to install busybox and root (su) the system, well if that's your goal that is.

Then insert the SD and boot.

In theory, this should boot up to stock from SD.

I could be missing something, it's late here, and I haven't tried any of this.

Beware: recovery, even from SD, will affect the internal partitions! Maybe it's best you delete uRecRam and uRecImg from your SD's boot (NOT INTERNAL!).

NB: you need to edit vold.conf. See second page of this thread.

Note: you could also use 'dd' command instead of making tars, but you'd end up with huge .img files.

PS: If you have no way of accessing your SD partitions once they're created, use the following command from ADB while booted from working internal system, with SD inserted in NC:

This last command should open every SD partition in you PC's explorer.

Sam