View Single Post
Old 02-06-2016, 03:38 AM   #34
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by RoBoKoP View Post
I must compile a version of uboot that sets S/N and board id for me. So binary is no go.
EDIT: hint here https://www.mobileread.com/forums/sho...&postcount=679
I'm not sure I have to do this though.
Can I connect to the uboot command line to have access to the `idme` command with the device in this state?
The u-boot is talking over the serial port, same as the SoC before it and the kernel after it.
So yes, but it my only be available in the full u-boot build.
What you see at first is a mini-uboot, you have to load the full one manually (called: bist).

The 'idme' command is also available over a fastboot connection, but you have to use the kindle's serial port to start fastboot.

Both ways of accessing the idme command require only u-boot to be working, the rest of the eMMC can even be erased.

Read the thread about recovering a Kindle with fastboot, that one was an 'erase all' victim.
knc1 is offline   Reply With Quote