Originally Posted by geekmaster
I have a modified a copy of the u-boot boot loader, and I have it loaded and running (in RAM) on my bricked k4nt, thanks to yinfalu
. So far, I patched only the boot message identifying the u-boot version (replacing "Yifan Lu patch" with "geekmaster mod") and the boot message from the serial port changed accordingly, proving that we are running "custom" boot loader code.
It even gets farther into the boot process, saying that it tested RAM successfully (which does not happen "normally" on this bricked kindle).
Now I have to modify the boot loader to force the board ID so it can initialize it and continue booting.
Once I get farther along in the boot process, I should be able to use idme to rewrite the board ID and serial number (I hope).
Anyway, do not discard your "hopelessly" bricked devices. This recover method is making rapid progress (thanks to the hard work of Yifan Lu). This is a k4nt, but it should work on the Touch as well. Thanks!
Here is the output captured from the serial port when I upload the patched u-boot using the Freescale MfgTool:
Normal (ROM) boot:
Umm, that "patch" is literally hex editing the version string. I never announce something until I am certain of the project. If someone are into the development process, they can join the IRC. It's never good to give false hope if this doesn't go anywhere. I mean I want to help you unbrick your Kindle because I'm interested in seeing how it would work, but it's not a certainty. If this process works out, I'll write a very in-depth post detailing everything from the commands to the data structures to the memory layout of the device, but now we have people expecting something which puts pressure on me.