Quote:
Originally Posted by knc1
Ah, not likely.
You where running the wrong (or modified) bootloader when you pressed: "Erase MMC".
That process is the only likely way that you could have used to re-flash the bootloader in its protected storage area ("Erase All/MMC/whatever" does that for you - copies the executing bootloader to flash).
That and the message quoted is what tells us most of the story you are trying to hide.
|
To avoid any confusion. Here are the steps to brick my kindle
1) Jail break it.
2) SSHed my kindle and install some programs (official busybox for arm), change boot logo and try to add custom languages.
3) Restart, then it can't open any books. Usbnet never start again
4) TTL and boot into diag partition, mount root partition and remove the login lock.
5) Restart, then it stucks at bootloader and said cannot access the flash chip
I never do "Erase MMC" or use custom bootloader. Why I have to hide in case I want to revive my kindle? Amazon can't blame me.
