Originally Posted by eureka
Data from Kindle Touch:
[root@kindle root]# fdisk -l -u /dev/mmcblk0
Disk /dev/mmcblk0: 3959 MB, 3959422976 bytes
4 heads, 16 sectors/track, 120832 cylinders, total 7733248 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 65536 782335 358400 83 Linux
/dev/mmcblk0p2 782336 913407 65536 83 Linux
/dev/mmcblk0p3 913408 978943 32768 83 Linux
/dev/mmcblk0p4 978944 7733247 3377152 b Win95 FAT32
Still, I can't find any traces of u-boot code in dump of /dev/mmcblk0. (Though, kernel is definitely there, Kernel Id is somewhere near address given by you). I've searched for 'u-boot' and didn't found any Boot Loader Id.
This is just my prediction, but it may be that in Linux, there is no read (and maybe no write) access to some parts of the mmc. For example, I took the Uboot offset for the kernel and dumped that part of /dev/mmcblk0 and got the kernel. System too. But when attempting to dump the serial & boardid information as defined by the offsets in Uboot source, I get all zeros. Maybe it's to protect the device from a virus or something?
I also do know that by dumping the mmc from Uboot on my kindle 2, I get the serial number information, Uboot, and other stuff (eink calibration data). That's where my information came from. I have yet confirmed if it is the same on k4/kt.