Originally Posted by hawhill
The "dumping" process is to make dumps, probably useful as backups of original data. Thinking of it, dumping the first ~32MB is probably a good idea in any case. It also serves as a quick test of the connection to the Kindle.
Currently, it's mainly partition images for the root partition and kernels what's floating around. We probably need partition table, eink data, uboot and some other stuff, too. However, in the first few sectors there's also a device identifier, I think. This should probably remain untouched for general-purpose recovery.
A quick and simple view:
core2quad embed $ fdisk -l kindle-hawhill-0x00000000-0x02000000.img
Disk kindle-hawhill-0x00000000-0x02000000.img: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders, total 65536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x489339d6
Device Boot Start End Blocks Id System
kindle-hawhill-0x00000000-0x02000000.img1 * 7688 1338943 665628 83 Linux
kindle-hawhill-0x00000000-0x02000000.img2 1338944 1388095 24576 83 Linux
kindle-hawhill-0x00000000-0x02000000.img3 1388096 1404479 8192 83 Linux
kindle-hawhill-0x00000000-0x02000000.img4 1404480 7815167 3205344 b W95 FAT32
It is a "standard" x86 style, ms-dos disk label at the default location.
What is not "standard" is the storage area between the end of the partition table and the start of the first partition.
Mapping the contents of that area will take a bit more work by someone.
we are not (yet) diddling the eMMC control registers to get copies of the one or two reserved areas.
Details in the eMMC data sheet, plus there is a mmc-util program, that with only a little bit of work to include this eMMC device, will give us that information. (one of the driving reasons for DIY-KeK - I want to use it myself)