04-26-2016, 01:32 PM | #1 |
Member
Posts: 10
Karma: 10
Join Date: Apr 2016
Device: none
|
Help recovering kindle paperwhite after 'eraseall'
Hi all,
It is my first post in this forum. I can't find any good information on kindle paperwhite anywhere else. I was trying to debrick the device and some image flashing went wrong, so after reboot for some very not wise reason I entered 'eraseall' command which without any confirmation wiped out everything from the device. All partitions. Now if I connect device to USB port on my linux I can see only: Code:
[ 2559.969903] usb 1-2: new low-speed USB device number 2 using xhci_hcd [ 2560.100814] usb 1-2: New USB device found, idVendor=1949, idProduct=dead [ 2560.100821] usb 1-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 2560.100824] usb 1-2: Product: USB Charger [ 2560.126950] input: USB Charger as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:1949:DEAD.0005/input/input20 [ 2560.127232] hid-generic 0003:1949:DEAD.0005: input,hidraw2: USB HID v1.11 Device [USB Charger ] on usb-0000:00:14.0-2/input0 [ 2561.539633] usb 1-2: USB disconnect, device number 2 Also, I have (had) access to serial port and it was ok. The bad thing is that I haven't made any backups of serial numbers or whatsoever. Is there any chance to restore fastboot on this device? The rest I can handle as there is plenty of information. Br |
04-26-2016, 01:40 PM | #2 |
Ex-Helpdesk Junkie
Posts: 19,422
Karma: 85397180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
|
MadMAXXX's experiences might help you: https://www.mobileread.com/forums/showthread.php?t=269099
He eventually got his PW3 fully recovered from an unwise eraseall. Last edited by eschwartz; 04-26-2016 at 01:42 PM. |
Advert | |
|
04-26-2016, 02:51 PM | #3 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
I can't say anything about "Device: None" that is in the O.P.'s info box, but.....
Yup, those are the directions for any kind of touch screen device, only the name of the firmware image to work with changes with the model in question. Note: Amazon firmware images rarely (never?) include the diags kernel or system image. You will have to get that from another working Kindle of the same model number (the first 4 or 6 characters of your serial number). Just be sure you get the correct update_*.bin from Amazon for your same model also. |
04-27-2016, 03:24 AM | #4 |
Member
Posts: 10
Karma: 10
Join Date: Apr 2016
Device: none
|
Hi,
Images of paperwhite is not a problem I suppose as they are available here: http://ixtab.tk/kindle-touch-images/PaperWhite/ Main thing is to restore U-boot somehow and after that device will be at least somehow alive and accessible. eschwartz. Thanks for the link. I will try to read everything and see if I will manage to restore. Will get back here with the results. |
04-27-2016, 06:43 AM | #5 |
Connoisseur
Posts: 51
Karma: 10
Join Date: Nov 2015
Device: PW2
|
Similar disconnecting issue: https://www.mobileread.com/forums/sho...d.php?t=267946
|
Advert | |
|
04-27-2016, 08:58 AM | #6 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
ixtab.tk is down for maintenance, it will return RSN according to ixtab.
|
04-27-2016, 09:03 AM | #7 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
"Erase All" re-loads u-boot from the copy running in memory at the time. There is another "don't use it" command to zap contents + u-boot. |
|
04-27-2016, 09:49 AM | #8 | |
Member
Posts: 10
Karma: 10
Join Date: Apr 2016
Device: none
|
Quote:
Reg. ixtab.tk there is no problem for me as I have all images downloaded before all that. I'm most concerned about serial number which I didn't save as well as other information. Br, |
|
04-27-2016, 10:08 AM | #9 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
That sounds like a Kindle Touch, not a Paperwhite. OR What you are calling 'Erase All' is not the same as what we are calling 'Erase All'. It isn't 'dead' - Unless you somehow managed to damage the SoC bootcode that is burned into it at the factory. There is a thread here explaining how to recover a Kindle that has a truely blank eMMC. Check out the one on upgrading the size of the eMMC (which comes from the factory as blank as it can be). |
|
04-28-2016, 03:12 AM | #10 |
Member
Posts: 10
Karma: 10
Join Date: Apr 2016
Device: none
|
Hi,
It is in fact Kindle Paperwhite (Motherboard PCB:30-000539). What I did was that I executed U-boot command "eraseall". I hope I haven't damaged SoC bootcode with this command. Why I call it dead it's because even USB id code says so when I connect it to computer. Kindle now is only recognized as USB charger and I can't even reboot it. It look pretty dead for now, but I hope it can still be restored. |
04-28-2016, 03:16 AM | #11 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Do a '30 second press' of the power button to re-boot - Save the entire capture log, compress it, attach to your next post. Just saying "its dead" is not much more informative than saying "its broke". |
|
04-29-2016, 03:51 AM | #12 | |
Member
Posts: 10
Karma: 10
Join Date: Apr 2016
Device: none
|
Quote:
|
|
04-29-2016, 07:00 AM | #13 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Something changed or broke. Unless you actually managed to alter the code burned into the SoC's internal ROM. Which is hardly possible unless you have tried to chemically peel the case off the chip. |
|
04-29-2016, 09:00 AM | #14 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
U-boot runs on the kindle flash chip (or uploaded to RAM). The SoC should go into Downloader (serial or USB) mode and allow reflashing over serial, at least, though of course without the interactive textual assistance of u-boot running . It may be worth reading the manual for the SoC in your device...
One concern is that only a smaller u-boot (without BIST and fastboot) can fit in the SoC RAM, and it is u-boot itself that initializes SDRAM where it can bootstrap a larger more-capable u-boot version (with fastboot support). [Beware that I have not read the manual for your specific device, going by prior knowledge from earlier kindle versions, but it should be basically the same.] |
04-29-2016, 09:06 AM | #15 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
I see that ixtab.tk is up now. I like how he has firmware images from my PW1, which disappeared from my hotel room in California quite some time ago...
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle Touch - Fastboot eraseall | Deivid3g | Kindle Developer's Corner | 21 | 10-16-2013 08:46 AM |
Free (Kindle/Nook) Change the World: Recovering the Message and Mission of Jesus | arcadata | Deals and Resources (No Self-Promotion or Affiliate Links) | 2 | 05-11-2011 07:17 AM |
Troubleshooting Recovering Wet Kindle | dvhh | Amazon Kindle | 21 | 12-26-2010 08:27 PM |
help recovering my library | babyz | Calibre | 12 | 06-03-2010 01:26 PM |
help recovering my library | babyz | Calibre | 1 | 06-01-2010 12:42 PM |