[Barnes & Noble Nook Tablet] meghd00t:
YES, all the re-partition tools are there sgdisk, genptable etc.

this is an example of how I recovered my new nook with my OLD serial no.

I zapped all info, created a new DEFAULT partition, then resized data and media installed factory recovery and image restored my old serial number and reset.

/tmp/busybox dd if=/dev/zero of=/dev/block/platform/mmci-omap-hs.1/mmcblk0 bs=4096 count=256 conv=notrunc,fsync
sgdisk -Z /dev/block/platform/mmci-omap-hs.1/mmcblk0

/tmp/busybox blockdev --rereadpt /dev/block/mmcblk0

cd /tmp
genptable ptable
dd if=ptable of=/dev/block/platform/mmci-omap-hs.1/mmcblk0 conv=notrunc,fsync

sgdisk -e /dev/block/platform/mmci-omap-hs.1/mmcblk0

sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -d 11 -d 10
sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -n 0:0:+12G -n 0:0:0
sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -c 10:media -c 11:userdata

/tmp/busybox dd if=/dev/zero of=/dev/block/mmcblk0p1
/tmp/busybox dd if=/dev/zero of=/dev/block/mmcblk0p2
/tmp/busybox dd if=/dev/zero of=/dev/block/mmcblk0p3
/tmp/busybox dd if=/dev/zero of=/dev/block/mmcblk0p4

mkdosfs -F32 -n rom /dev/block/mmcblk0p5
mkdosfs -F32 -n bootdata /dev/block/mmcblk0p6
mkdosfs -F32 -n MyNook /dev/block/mmcblk0p10

make_ext4fs -L factory /dev/block/mmcblk0p7
make_ext4fs -L system /dev/block/mmcblk0p8
make_ext4fs -L cache /dev/block/mmcblk0p9
make_ext4fs -L userdata /dev/block/mmcblk0p11

# On the Linux host
# dd if=nooktablet_1_4_2_update.zip of=factory.zip bs=423 skip=1
# adb push busybox /tmp
# adb push factory.zip /tmp
# adb push rombackup.zip /tmp

/tmp/busybox unzip -o factory.zip MLO_es2.3_BN u-boot.bin boot.img recovery.img romrestore.zip

mkdir -p /mnt/factory
mkdir -p /mnt/rom
mkdir -p /mnt/bootdata

mount -t ext4 /dev/block/mmcblk0p7 /mnt/factory
mount -t vfat /dev/block/mmcblk0p5 /mnt/rom
mount -t vfat /dev/block/mmcblk0p6 /mnt/bootdata

cp factory.zip /mnt/factory/
cp rombackup.zip /mnt/factory/
cp romrestore.zip /mnt/factory/

cd /mnt/
/tmp/busybox unzip /tmp/rombackup.zip
umount /mnt/rom/

/tmp/busybox dd if=/dev/zero of=/mnt/bootdata/BCB bs=1088 count=1
/tmp/busybox dd if=/dev/zero of=/mnt/bootdata/BootCnt bs=4 count=1
echo -n .a:B > /mnt/bootdata/BootCnt
umount /mnt/bootdata/

cd /tmp
/tmp/busybox dd if=MLO_es2.3_BN of=/dev/block/mmcblk0p1 conv=notrunc,fsync
/tmp/busybox dd if=u-boot.bin of=/dev/block/mmcblk0p2 conv=notrunc,fsync
/tmp/busybox dd if=recovery.img of=/dev/block/mmcblk0p3 conv=notrunc,fsync
/tmp/busybox dd if=boot.img of=/dev/block/mmcblk0p4 conv=notrunc,fsync

---------- Post added at 07:44 AM ---------- Previous post was at 07:37 AM ----------

[/QUOTE]

cwm_6012_sdcard.img is just that - it is a recovery image to be placed on a sdcard and booted with cyanoboot it is NOT a sd image, you cannot dd it onto a sdcard and expect it to work.

if you are using cyanoboot on the sd then place MLO, uboot & flashing_boot.img plus cwm and or twrp img on a sdcard. rename the cwm as recovery and twrp as altboot and you have the best of both worlds.

right now I mostly use only twrp

also you can place cwm_emmc on internal emmc and twrp_sdcard in /bootdata/altboot.img and cyanoboot can start anyting you want!

You have all the raw tools it is up to you how you want to use it!