11-27-2014, 08:15 AM | #1 |
Junior Member
Posts: 3
Karma: 10
Join Date: Oct 2014
Device: Kindle Paperwhite
|
Debricking Kindle PW
Hi, my Kindle PW is frozen and does not boot after hard reset and is not seen as a device when connected to a PC or MfgTool. I connect to it via the console - it cyclically restarts. It tries to boot a diags mode was unsuccessful because both partitions - main and diags were damaged. After that I switch to fastboot mode and flash the image and the kernel for diags partition, boot into diags mode, connect the drive via USB Device mode and began to copy the image to main partition, but received an error writing to mmc (after 70% writing of image). I tried using fastbot erase main and diags partition, but unsuccessfully – I again received an error writing to mmc. Then I typed:
fastboot eraseall fastboot flash diags fastboot flash diags_kernel fastboot reboot It was a big mistake - eraseall, now uboot is not available, log: Spoiler:
Any ideas? P.S. Now i can see Kindle in MfgTool, but it cyclically trying to connect to the device |
11-27-2014, 09:50 AM | #2 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Abandon all hope until you replace the bad eMMC chip (the original cause of the file corruptions).
|
11-27-2014, 10:22 AM | #3 |
Junior Member
Posts: 3
Karma: 10
Join Date: Oct 2014
Device: Kindle Paperwhite
|
It may be that after eraseall, bad blocks are marked as unused, and possibly now somehow copy the image to the mmc? Moreover, that smaller files are copied to the flash was successful.
|
11-27-2014, 06:15 PM | #4 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
That can't be the only damage - 'bad blocks' that is.
The reason I write that is because you say that u-boot was erased by the 'erase all' command. It **SHOULD** have just been replaced. U-Boot is in a protected area of the eMMC device, and the 'erase all' command replaces the contents of that protected area by the program resident in memory that runs the 'erase all' command (I.E: u-boot). |
11-27-2014, 11:45 PM | #5 | |
Junior Member
Posts: 3
Karma: 10
Join Date: Oct 2014
Device: Kindle Paperwhite
|
Quote:
|
|
01-02-2015, 11:40 AM | #6 |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
One user restored his Kindle after eraseall (story starts here) with this U-Boot and previously made data backup.
Though, I think, it wouldn't help you in solving original problem. |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Please Help with Debricking Kindle Paperwhite | 8a8e8ei2i20 | Kindle Developer's Corner | 5 | 10-25-2014 05:57 PM |
Kindle Touch. Desenladrillado(debricking) | cristbo | Amazon Kindle | 6 | 01-23-2013 09:48 AM |
Any help with debricking kindle 3? | andy2082 | Kindle Developer's Corner | 13 | 11-25-2012 07:58 AM |
kindle touch simple debricking for help | non_fox | Amazon Kindle | 4 | 04-18-2012 08:32 PM |
Troubleshooting simple kindle touch (and k4nt) debricking method | geekmaster | Amazon Kindle | 0 | 03-02-2012 10:31 PM |