Partition table layout and how to dump partition images sucessfully.Please help

[johnpence]

Hi , can someone help me with the partition layout for Polaroid tablets with 10 partitions. I did some research and saw that Shawn had them posted on his Google docs account. but the links are dead. i know that recovery is nandg. and i believe nandc is boot. Also when i "dd if= /dev/block/nandg of=/sdcard/recovery.img " the output is 32mb and same with nandc. am i doing something wrong? seems these files should be smaller.
UPDATE

nanda
nandb
nandc boot?
nandd /system
nande /data
nandf
nandg recovery
nandh cache
nandi
nandj


One last thing , does anyone know how to modify a compatability.zip so that i can include the "gt811_ts.so" touchscreen driver as the 702c one made by william kleinman seems to be a close match as it is a13 based and the only difference i noticed so far is the touchscreen driver.

Please anyone with info thanks.

[dolorespark]

Hi , can someone help me with the partition layout for Polaroid tablets with 10 partitions.

nanda bootloader
nandb environment for bootloader
nandc boot (kernel & rootfs contents)
nandd /system
nande /data
nandf misc (seemingly used only to pass an argument to the bootloader to enter recovery)
nandg recovery (identical in layout to the boot partition)
nandh /cache
nandi "data image backup"
nandj "internal SD card"

Also when i "dd if= /dev/block/nandg of=/sdcard/recovery.img " the output is 32mb and same with nandc. am i doing something wrong? seems these files should be smaller.

You're getting a raw dump of the entire partition; each of these two are 32mb. The actual contents are smaller (9-10mb).

does anyone know how to modify a compatability.zip so that i can include the "gt811_ts.so" touchscreen driver as the 702c one made by william kleinman seems to be a close match as it is a13 based and the only difference i noticed so far is the touchscreen driver.

Is the driver not included in the package or is it there but not working? This could be as simple as unzipping the thing, adding the driver, then rezipping (you can use Windows to do this, and if you use CWM to install it, you shouldn't need to sign it either).

Sadly, few things are ever that simple. At the least, you'll have to verify that the "vermagic" string in the driver matches the kernel - and change it with a hex editor if it doesn't. Then too, the package's "init.sun5i.rc" may not load that driver, meaning you have to get it to do so. Let's save that can of worms for later...