This is pretty much a one-stop shop for Kindle Touch debricking images.
The best thing about these files is that if they are used properly, they will almost
always allow you to debrick your Kindle WITHOUT having to resort to fastboot mode,
which can be a horrible PITA because of Windows device drivers. Just make sure that
you install the SSH-enabled diags in the beginning (i.e., *before* things went wrong),
and you should be on the safe side 99% of the time.
You'll find the following files here:
- kt_5.0.*diags*.gz : Diags kernel and partition, for flashing with fastboot. (1)
- update_k5_diags+ssh.bin: the same thing, but as an update package. (2)
- kt_5.*main*.gz: Main Kernels and partitions, for version 5.0.0 and 5.1.2. (3)
(1) : You may need these files if your Kindle is completely, utterly, bricked, and
if the only way to get it back to life is via fastboot.
(2) : You can use this file if your *diags* partition is bricked, but your main
partition still works. This update package will restore the diags kernel, and
partition, to a "known working and usable state". Note that this package must
be installed from a working and jailbroken main partition.
(3) : These files can be installed from a working diags partition, or (for kernels
ONLY) via fastboot. The fastboot way is explained in the debricking guide,
the "diags way" is explained below.
THE EASIEST WAY TO USE THESE FILES
1. While your Kindle is *STILL WORKING*, make sure that you install the diags partition
with SSH. This is as simple as installing the jailbreak, then installing the update_*.bin
package mentioned above (using the Settings -> Update your Kindle menu entry).
2. Once you get your Kindle into a bricked state, don't despair. If you have the above diags
image installed, it'll normally be working again within 10 minutes. While your Kindle is
plugged into your computer, it should show up as a USB device. Copy the following three files
to the Kindle:
You can of course use other files as well, just make sure that you choose a kernel and partition
for the same firmware version (and for the main partition, obviously), otherwise you may
experience problems later on. Then restart the Kindle. It will restart in diags mode.
3. Select the following menu entries in this order: N - U - Z - X. Wait about 10 seconds, and
your Kindle will be recognized as a network device. Configure your *computer* to use the
following IP settings for the network: IP address: 192.168.15.201, netmask 255.255.255.0.
4. Connect to your Kindle via SSH. The Kindle's IP address will be 192.168.15.244. Use username
"root", password "mario" (type both without the quotes) to log in. Note: It makes sense to
read the noob's debricking guide (http://www.mobileread.com/forums/sho...d.php?t=180789
at this point, because the following commands require you to understand what you are doing.
5. Overwrite the main partition and/or kernel. In most cases, you will only need to overwrite
the partition. You will normally only need to overwrite the kernel if you want to change to
another firmware revision, or if something is hopelessly screwed up.
* TO OVERWRITE THE MAIN PARTITION:
A) if the partition image is gzipped (ends with .gz):
zcat /mnt/us/kt_5.1.2-mmcblk0p1-main+jb+kjb+ssh.img.gz | dd of=/dev/mmcblk0p1 bs=4096
B) if the partition image is NOT gzipped:
dd if=/mnt/us/kt_5.1.2-mmcblk0p1-main+jb+kjb+ssh.img of=/dev/mmcblk0p1 bs=4096
* TO OVERWRITE THE MAIN KERNEL:
NOTE: MAKE ABSOLUTELY SURE THAT YOU USE THE BELOW "of","bs", and "seek" parameters
FOR dd, and that you use the correct method.
Otherwise, your Kindle *WILL* end up being FUBAR.
A) if the kernel image is gzipped (ends with .gz):
zcat /mnt/us/kt_5.1.2-kernel_main.gz | dd of=/dev/mmcblk0 bs=4096 seek=65
B) if the kernel image is NOT gzipped:
dd if=/mnt/us/kt_5.1.2-kernel_main of=/dev/mmcblk0 bs=4096 seek=65
* IF YOU KEEP GETTING THE "Your Kindle Needs Repair" MESSAGE:
This is only needed if the device still doesn't boot after "normal" debricking.
echo 0 > /var/local/upstart/lab126_gui.restarts
* TO RESET ALL SETTINGS:
This is not normally required, but may be needed for severely bricked devices.
My suggestion is to NOT do it, except if your device still doesn't boot after
re-flashing the partition and kernel, and fixing the "repair" count.
dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1K
6. After the repairs, issue the following to reboot your device in main mode:
idme -d --bootmode main