View Single Post
Old 02-19-2012, 10:28 PM   #2
geekmaster
bit basher & pixel pusher
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,689
Karma: 7581653
Join Date: Nov 2011
Location: A young man living in an old man's body.
Device: Too many.
Attention developers: please feel free to add to this thread, showing details on how to use the MfgTool and custom boot profiles to boot a bricked kindle to your choice of diags, fastboot, or main mode. You can modifiy ixtab's jailbreak to deposit a script into /var/local/wan/info, then run the ar11g diagnostic to trigger it. When /var/local/wan/info executes, it should check for and run /mnt/us/RUNME.sh.

Be sure to NOT change the diagnostics boot partition. Instead, do "mount /dev/mmcblk0p1 /mnt/mmc" and make repairs inside /mnt/mnc/etc/*.

Okay? Thanks for helping with this.

Inside the custom boot profiles are kindle touch u-boot.bin files that have had an additional line of code added. Where the original code reads the bootmode idme var, then decides which partition to boot, the new code replaces the local memory copy of bootmode with either "diags", "fastboot", or "main". The idme vars are NOT changed. The boot process continues using the modified bootmode in memory.
geekmaster is online now   Reply With Quote