[Dell Venue] social-design-concepts:
wow i am so so so sorry . . . you are correct it does appear that for the venue 7 & 8 I mistakenly copied and pasted the corrected partition.tbl

the modifications in that partition.tbl are the relabel of spare to misc to match .fstab and the resizing of cache to be equal to the size of the system partition. you can always use the partition table that is stored in the fastboot.img under /system/etc/partition.tbl

as for logo.bin you woulld need to use [MENTION=5941423]pm-cz[/MENTION] dump_image to extract it from the device that has the dell logo splash screen i believe it needs to be one for the v7 and one for the v8 do to the different size screens.

Thank you for posting the instructions my laptop died monday so i had been in between computers and work got super busy after lunch . . .

the instructions are correct but when you flash the system.img.gz the partition will take on the size of the image file so after you do

fastboot oem start_partitioning

fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl

fastboot oem erase system
fastboot oem erase cache
fastboot oem erase data
fastboot oem erase logs
fastboot oem erase factory
fastboot oem erase config

fastboot oem stop_partitioning

fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.gz

you should then either reboot into recovery or reboot into the bootloader the start the tethered recovery and then start an adb shell and

# e2fsck -f /dev/block/mmcblk0p8
e2fsck -f /dev/block/mmcblk0p8
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p8: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p8: 1883/65536 files (4.6% non-contiguous), 251459/262144 blocks
# resize2fs /dev/block/mmcblk0p8
resize2fs /dev/block/mmcblk0p8
resize2fs 1.41.14 (22-Dec-2010)
Resizing the filesystem on /dev/block/mmcblk0p8 to 524288 (4k) blocks.
The filesystem on /dev/block/mmcblk0p8 is now 524288 blocks long.

# e2fsck -f /dev/block/mmcblk0p9
e2fsck -f /dev/block/mmcblk0p9
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p9: 11/686784 files (0.0% non-contiguous), 82593/2744311 blocks
# resize2fs /dev/block/mmcblk0p9
resize2fs /dev/block/mmcblk0p9
resize2fs 1.41.14 (22-Dec-2010)
Resizing the filesystem on /dev/block/mmcblk0p9 to 2744315 (4k) blocks.
The filesystem on /dev/block/mmcblk0p9 is now 2744315 blocks long.

# reboot

you probably should run e2fsck -f on any partition you changed from the original

i've attatched the three partition table configs i've been using you need to resize any partition which you flash a smaller image over. View attachment 3092934

it's worth noting incase any other intel device owners come across this and are wanting to resize there devices to always use thier devices partition table as a base and to always be sure to dd any partition they are not sure of in case the contain any crucial files