At http://wiki.mobileread.com/wiki/Kind...ing#Partitions it says this about partition 4:
Couple questions about this.
My goal is to make a good attempt at secure-erasing this partition before passing on my stock (i.e. not jailbroken) Kindle Touch to someone else. If I'm understanding everything I've read correctly, this partition is actually an entire disk image containing a MBR, partition table, and then the FAT32 partition exposed to over USB Drive Mode.
Is it safe to zero out the entire exposed disk (since it should just be the contents of partition 4)? Or at least the FAT32 partition-within-a-partition? i.e. will the Touch recreate the partition if it detects it has been zeroed?
Quote:
|
Partition 4 (FAT32, 3.3 GB (KT) / 1.4 GB(PW)): This is where your documents go. In normal operations, it is mounted as /mnt/us, and this is the partition you get to modify when you mount the Kindle via USB. You can delete the contents if you can afford to lose your documents; the device will still work. [Do not delete /diagnostic_logs/device_info.xml from a USB Drive exported from the diagnostic recovery menu screen, or it will be difficult to reboot to the main partition.] |
My goal is to make a good attempt at secure-erasing this partition before passing on my stock (i.e. not jailbroken) Kindle Touch to someone else. If I'm understanding everything I've read correctly, this partition is actually an entire disk image containing a MBR, partition table, and then the FAT32 partition exposed to over USB Drive Mode.
Is it safe to zero out the entire exposed disk (since it should just be the contents of partition 4)? Or at least the FAT32 partition-within-a-partition? i.e. will the Touch recreate the partition if it detects it has been zeroed?
