|
I think that's the ATK, yes. I didn't check if it's the i.MX35 version, but you will notice when it's installed. It works using the USB connection, you've got to bring your Kindle into bootloader mode to connect. Nobody had success with any step further, however - hacking adventures before you. Since you are asking proficient questions it might not be fully out of scope for you, though. But you would need a good understanding on how a modern CPU/SoC works, what the exact role of a boot loader is and how to compile (for example) the Linux kernel for different targets.
Indeed, Yifanlu provided a great description on how to load a rescue kernel via serial console. It would work just the same on the K3, I think. Thanks for the link, I didn't stumble over that text yet. It's probably the easiest way out, since you know how to get to Uboot already. Also, this is an approach common to many embedded devices using uboot.
AFAIK, if the exporting would work, it should present you _all_ partitions of the Kindles flash storage. The basic layout (I don't have my K3 here right now) is as follows:
- partition 1: root file system, which is mounted read-only on normal Kindle use. Thus it should only break if you forget to bring it back into read-only mode...
- another partition for the user store, which is mounted to /mnt/base-us in normal use which is again mounted as /mnt/us (using a passthrough filesystem that's able to "cut" the bounds to the underlying file system when it needs to be accessed via USB)
- another partition for the kernel, I think
- another partition for bootloader "environment", i.e. configuration variables.
The latter don't carry filesystems. The root file system is ext2, I think, might also been ext3. The user store is VFAT.
|