10-27-2019, 06:56 AM | #1 |
Junior Member
Posts: 4
Karma: 10
Join Date: Oct 2019
Device: Kindle PW1 + PW2
|
Bootlooping Kindle Paperwhite possible repair?
Hi,
I've come to inherit a Kindle PW1 which is bootlooping on the tree screen. I tried all the basic ways to get past it with no success so connected it to serial to have a look. It appears to be bootlooping because of this error: Code:
EXT3-fs error (device mmcblk0p3): ext3_add_entry: bad entry in directory #2: rec _len % 4 != 0 - offset=0, inode=3735924190, rec_len=21025, name_len=82 I was going to try flashing everything again via fastboot but am unable to get the factory images from the original website that gets used here and while I can download the update officially from amazon, I am unsure if I can use that to do what I want to do. If anyone has any ideas where I can go from here that would be great! Thanks |
10-27-2019, 07:45 AM | #2 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
It can unpackage any Amazon or Mobileread *.bin package. While doing so, it can also create an archive (*.tar.gz) of that package. KindleTool, in NiLuJe's snapshots thread, keeps the tool current. (I.E: Use only the NiLuJe brand, do not accept substitutes.) |
|
Advert | |
|
10-27-2019, 01:00 PM | #3 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
This is going to be tricky if you don't have your own backups, the export option fails, and you don't have shell access in diags.
You can't flash anything else than kernels & diags over fastboot, but an official update will only ship main & main kernel. Diags appears to be functional(-ish), so the usual approach would be export + drop an official update in there. Since that doesn't work, the second approach would be flashing it manually from diags over shell. Which means that if you don't have shell access, and export is b0rked, you're in a bit of a bind. I'd be curious in the exact chain of events displayed in the logs followed over serial when you attempt an export, because I wasn't even aware diags even *had* a YKNR screen. I knew it could boot you to main *to* a YKNR screen, but that's not the same thing. Last edited by NiLuJe; 10-27-2019 at 01:03 PM. |
10-27-2019, 01:36 PM | #4 | |
Junior Member
Posts: 4
Karma: 10
Join Date: Oct 2019
Device: Kindle PW1 + PW2
|
Quote:
Spoiler:
Here is the code when attempting to run USB Device Mode from diags: Spoiler:
Any idea where I can start with this if it's possible at all? |
|
10-27-2019, 03:37 PM | #5 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Code:
ERROR:Could not find partition 0x0b on /dev/mmcblk0p4 ERROR:Unable to access /dev/mmcblk0p4:Cannot update OS ERROR:No userstore partition, cannot check for updates. BOOTING DEFAULT. Quote:
It indicates it is waiting for a "fastboot" connection over USB. NOTE: You must use the proper fastboot tool, these Kindles do not use the same fastboot as an Android machine. |
|
Advert | |
|
10-27-2019, 03:42 PM | #6 | |
Junior Member
Posts: 4
Karma: 10
Join Date: Oct 2019
Device: Kindle PW1 + PW2
|
Quote:
Oh, I didn't understand that was for the fastboot connection. Sorry. I thought it was usb accessible storage. |
|
10-28-2019, 11:10 AM | #7 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Code:
Menu ==== 3. Load MMC0 over USB storage 4. Erase MMC0 I. Initialize Partition Table (fdisk) and format FAT O. Format and overwrite FAT partition E. Export FAT partition U. Update using update*.bin file on FAT partition M. Update using update*.bin file on FAT partition of second MMC port D. dmesg / kernel printk ring buffer. Q. quit But... You should also read: Code:
=== BATTERY IS CRITICALLY LOW - DEFERRING BOOT === Charge: 7% [#####:::::::::::::::::::::::::::::::::::::::::::::::::::::] But instead: Code:
[Critical Battery Lock-out Menu] 1. Skip R. reboot Choose: /- Code:
*** Skipping critical battery lock-out. INFO:!!! Checking MBR /dev/mmcblk0 !!!! The system tried to fscheck the system, the eMMC lost power during the process, and you have now fried the eMMC. Sell the screen as "used", throw the rest away. |
|
10-28-2019, 03:18 PM | #8 | ||
Junior Member
Posts: 4
Karma: 10
Join Date: Oct 2019
Device: Kindle PW1 + PW2
|
Quote:
Quote:
Also, through experimenting I found this, if usb device mode is selected and formatted on the PC, you can then place files on the usb drive as normal and if you disconnect and reconnect the USB quickly, the files do not disappear and they are fully intact to which I would assume the eMMC is still able to read/write. However, if the USB Device Mode is allowed to exit itself which is of course standard when removing the USB, it loses the filesystem again. |
||
10-28-2019, 04:01 PM | #9 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
IIRC, you posted that you do not know the device's previous history.
- - - - What you are looking at, which goes away, is just a cached image of the file system. The actual file system is dead. Sell the screen, throw the rest of it away. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle Paperwhite 2nd Gen: Repair Needed screen | ruskalaka | Kindle Developer's Corner | 2 | 05-13-2017 10:46 PM |
Kindle Paperwhite 2013 edition needs repair. | SKK | Kindle Developer's Corner | 8 | 06-28-2016 08:27 AM |
Troubleshooting Kindle Paperwhite 5.3.5. Getting "Your Kindle Needs Repair" message :sad2: | obelisk | Amazon Kindle | 6 | 08-20-2013 03:31 PM |
Kindle Paperwhite "Repair Needed" | climbingrose | Amazon Kindle | 9 | 10-12-2012 01:03 PM |