MobileRead Forums - View Single Post - [K4NT, Help needed] Bricked, but visible as USB HID

geekmaster · 01-21-2012, 01:35 PM

Well... I learned one thing at least:

If you export the USB drive from diagnostics mode, or access it with SSH in diagnostics mode, you should not delete /mnt/us/ENABLE_DIAGS and then select "Disable Diagnostics" from the exit menu.

It appears that this can corrupt your serial number and board ID information so that the generic u-boot logic cannot decide how to initialize the hardware. This is what you might call "bricking your kindle".

EDIT: I am now loading and running custom u-boot boot loader code in my bricked k4nt RAM using USB HID mode, thanks to the efforts of yifanlu. Now I need to patch the boot loader to force a valid board ID, so it can continue the boot process.

01-21-2012, 01:35 PM	#8
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	Well... I learned one thing at least: If you export the USB drive from diagnostics mode, or access it with SSH in diagnostics mode, you should not delete /mnt/us/ENABLE_DIAGS and then select "Disable Diagnostics" from the exit menu. It appears that this can corrupt your serial number and board ID information so that the generic u-boot logic cannot decide how to initialize the hardware. This is what you might call "bricking your kindle". EDIT: I am now loading and running custom u-boot boot loader code in my bricked k4nt RAM using USB HID mode, thanks to the efforts of yifanlu. Now I need to patch the boot loader to force a valid board ID, so it can continue the boot process. Last edited by geekmaster; 01-30-2012 at 09:38 PM.