MobileRead Forums - View Single Post - need help: I select Erase MMC0 in my kindle gen 8 recovery menu..

knc1 · 06-26-2017, 06:42 PM

On your device (why would I give you directions for his device?) . . .
loady is in the bist command set (at least it was last time I looked).
enter:
bist
then enter:
help

- - - -

But due to the fact that is was broken (ymodem protocol) for so long, you may be looking at u-boot build with it remove.
When you updated to 5.8.9.2, one of the things the update did was install a u-boot built for the firmware version.

- - - -

The bootloader (u-boot) lives in a hardware, write protected, area of the eMMC, which you normally can not even see (its mapped out by the eMMC hardware).

The way to install a new (or at least a different) u-boot is to load it to memory, execute it, perform an 'erase all' function.
Part of that function is (after erasing the entire eMMC device) to copy the currently executing u-boot into its protected storage.

(I don't recall anyone verifying that things still work that way now, that was how 5.3.x (or something like that) once worked.)

06-26-2017, 06:42 PM	#29
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	On your device (why would I give you directions for his device?) . . . loady is in the bist command set (at least it was last time I looked). enter: bist then enter: help - - - - But due to the fact that is was broken (ymodem protocol) for so long, you may be looking at u-boot build with it remove. When you updated to 5.8.9.2, one of the things the update did was install a u-boot built for the firmware version. - - - - The bootloader (u-boot) lives in a hardware, write protected, area of the eMMC, which you normally can not even see (its mapped out by the eMMC hardware). The way to install a new (or at least a different) u-boot is to load it to memory, execute it, perform an 'erase all' function. Part of that function is (after erasing the entire eMMC device) to copy the currently executing u-boot into its protected storage. (I don't recall anyone verifying that things still work that way now, that was how 5.3.x (or something like that) once worked.) Last edited by knc1; 06-26-2017 at 07:08 PM.