MobileRead Forums - View Single Post

TBennettcc · 04-13-2014, 10:17 PM

If that's the case, is the device really, truly, completely bricked, or is there still a way to restore it?

Other than running the standard unbricking procedures (flashing diags partition and kernel and main kernel, etc.), I have not tried to run any updates. The device is still acting the same as when I received it. I have never seen a screen on the device besides the diags partition, the "update failed" screen, the "boy under the tree" when booting (and the loading bar), and the "Your Kindle needs repair" screen (which, ironically enough, didn't need the boot count file reset to get rid of...). I have never seen any kind of main "desktop" menu or interface.

So far as I understand, my friend tried to turn on the device, and it showed the "empty battery-plug me in-recharge me" screen. Someone told him this meant he needed a new battery, so he bought one and put the new battery in.

As far as how it got to that point, I'm not sure. I don't know which screens, if any, he saw before the "plug-in-to-charge" screen. I don't know if it tried to do an update first, and failed, and showed the "failed update" screen before it showed the "plug-in-to-charge" screen.

Is it possible it was trying to do an update, and the battery died in the middle of the update? I don't have a Kindle of my own yet (I was planning on buying a PW2 in short order), so I don't have any experience with updates or the updating process. I don't know if the device needs to be plugged in to power before starting an update, etc. (If something like this can happen because of that, IMHO, they should make that a *requirement*!)

I can boot to fastboot (1949:d0d0). I can boot to diags. I can enter USB Recovery mode (15a2:0052). I can talk to the device through the serial console. I can flash the diags partition, diags kernel, and main kernel. All of which tells me *something* has to be working, right?

Is there *any* way to completely nuke everything and start over? Maybe erase MMC0? I've seen various threads on this site claim to be able to repair a Kindle that has had its MMC0 nuked, but they all seem to be predicated on getting the main partition image successfully copied over to the USB user partition, which seems to be a problem for me.

Thank you for your time.

04-13-2014, 10:17 PM	#23
TBennettcc Member Posts: 15 Karma: 10 Join Date: Mar 2014 Device: Kindle Touch	If that's the case, is the device really, truly, completely bricked, or is there still a way to restore it? Other than running the standard unbricking procedures (flashing diags partition and kernel and main kernel, etc.), I have not tried to run any updates. The device is still acting the same as when I received it. I have never seen a screen on the device besides the diags partition, the "update failed" screen, the "boy under the tree" when booting (and the loading bar), and the "Your Kindle needs repair" screen (which, ironically enough, didn't need the boot count file reset to get rid of...). I have never seen any kind of main "desktop" menu or interface. So far as I understand, my friend tried to turn on the device, and it showed the "empty battery-plug me in-recharge me" screen. Someone told him this meant he needed a new battery, so he bought one and put the new battery in. As far as how it got to that point, I'm not sure. I don't know which screens, if any, he saw before the "plug-in-to-charge" screen. I don't know if it tried to do an update first, and failed, and showed the "failed update" screen before it showed the "plug-in-to-charge" screen. Is it possible it was trying to do an update, and the battery died in the middle of the update? I don't have a Kindle of my own yet (I was planning on buying a PW2 in short order), so I don't have any experience with updates or the updating process. I don't know if the device needs to be plugged in to power before starting an update, etc. (If something like this can happen because of that, IMHO, they should make that a requirement!) I can boot to fastboot (1949:d0d0). I can boot to diags. I can enter USB Recovery mode (15a2:0052). I can talk to the device through the serial console. I can flash the diags partition, diags kernel, and main kernel. All of which tells me something has to be working, right? Is there *any* way to completely nuke everything and start over? Maybe erase MMC0? I've seen various threads on this site claim to be able to repair a Kindle that has had its MMC0 nuked, but they all seem to be predicated on getting the main partition image successfully copied over to the USB user partition, which seems to be a problem for me. Thank you for your time.