Originally Posted by murz_07
Sorry, I can't understand, can it be any useful for unbricking Kindle Touch?
I flashed diags partition and successfully "dd" mmcblk0p1 using SSH but still can't boot in main mode.
Regarding your question about using a custom linux kernel for debricking... I would say "Not at this time".
Booting a custom linux kernel is useful for kernel mode development, such as creating a new device driver, without a bug in the new device driver causing the kindle to get bricked. One of our members (dasmoover
) had his kindle touch sit on a shelf gathering dust after his "tun.ko" driver bricked his touch in a way that required our debricking methods to progress to a point where he was able to recover it.
Regarding the problem that you described, it sounds like you repaired your kindle. Perhaps you need to change your bootmode idme var. To do that, boot to diags, and from an SSH shell, type these commands:
This thread is about custom linux kernel testing. There are other threads for kindle debricking:
idme -d --bootmode main
rm -f /mnt/us/ENABLE_DIAGS
simple kindle touch (and k4nt) debricking method:
Select Boot for K4 and Touch:
fastboot for win32: