PW Bootlooping Kindle Paperwhite possible repair?

FruitPolo · 10-27-2019, 06:56 AM

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

When attempting to access the kindle's fat32 partition on the computer through recovery or diag it appears to have no filesystem as the computer asks to format the drive before using. When in recovery however, Export FAT Partition causes an immediate YKNR screen.

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

knc1 · 10-27-2019, 07:45 AM

Quote:

Originally Posted by FruitPolo

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

When attempting to access the kindle's fat32 partition on the computer through recovery or diag it appears to have no filesystem as the computer asks to format the drive before using. When in recovery however, Export FAT Partition causes an immediate YKNR screen.

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

KindleTool.
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.)

NiLuJe · 10-27-2019, 01:00 PM

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.

FruitPolo · 10-27-2019, 01:36 PM

Quote:

Originally Posted by NiLuJe

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.

Sorry, might have been a misunderstanding. In the recovery menu when you press enter during booting, when export FAT is selected it shows the YKNR screen. When in diags you select USB Mode it just keeps refreshing the display and not doing anything. Serial doesn't even say any issue with the partition like I expected. Here is the serial output when the kindle is crashed using recovery:

Spoiler:

Code:

U-Boot 2009.08-lab126 (Jan 08 2013 - 21:47:48)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 66666666Hz
ipg per clock : 66666666Hz
uart clock    : 24000000Hz
ahb clock     : 133333333Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Celeste (256 MB)
Boot Reason: [POR]
Boot Device: MMC
Board Id: 0151XXXXXXXXX
S/N: B01D1603XXXXXXXX
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffc000
POST done in 17 ms
Hit any key to stop autoboot:  0
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4608640 Bytes =  4.4 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
MX50 LPDDR2 MfgID: 0x3 [Elpida]
2.6.31-rt11-lab126 #1 Tue Jun 11 15:56:48 PDT 2013 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (39836 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (51424 bytes)
INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu...       0 /
INFO:Loaded module /lib/modules/arcotg_udc_yoshime.ko  (22912 bytes)
INFO:Loaded module /lib/modules/g_file_storage.ko recovery_mode=1 (36308 bytes)

=== BATTERY IS CRITICALLY LOW - DEFERRING BOOT ===
Charge: 7% [#####:::::::::::::::::::::::::::::::::::::::::::::::::::::]

[Critical Battery Lock-out Menu]
1. Skip
R. reboot
Choose: /-
*** Skipping critical battery lock-out.
INFO:!!! Checking MBR /dev/mmcblk0 !!!!
INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 4, start sector is 1044480
INFO:maximizing partition 2863104 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
Charge: 7% [#####:::::::::::::::::::::::::::::::::::::::::::::::::::::]


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
Choose:    4 \


INFO:storage_export(/dev/mmcblk0p4): exporting
Charge: 7% [#####:::::::::::::::::::::::::::::::::::::::::::::::::::::]

[FAT32]
1. done
R. reboot
Choose: /


USB CONNECTED!!
Charge: 7% [#####:::::::::::::::::::::::::::::::::::::::::::::::::::::]

[FAT32]
1. done
R. reboot
Choose: /boot: C def:bcut:batterycut=1,version=196798:
kernel: E savemsg:Abnormal reset detected but saved buffer invalid:            -still alive...
Charge: 7% [#####:::::::::::::::::::::::::::::::::::::::::::::::::::::]

[FAT32]
1. done
R. reboot
Choose: /

Here is the code when attempting to run USB Device Mode from diags:

Spoiler:

Code:

POST done in 17 ms
Hit any key to stop autoboot:  0
uboot > bootm 0xE41000
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4608576 Bytes =  4.4 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
2.6.31-rt11-lab126 #1 Tue Sep 25 22:13:12 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (36956 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (51152 bytes)
INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu...       0 /INFO:!!! Checking MBR /dev/mmcblk0 !!!!
INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 4, start sector is 1044480
INFO:maximizing partition 2863104 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
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.
  argc == 11
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p2"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
  argv[9]: "mem=256M"
  argv[10]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p2) = dev(179,2)
kinit: root_dev = dev(179,2)
kinit: /dev/root appears to be a ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.
init started: BusyBox v1.17.1 (2012-09-25 22:07:53 PDT)
starting pid 424, tty '': '/etc/init.d/rcS'
/etc/init.d/rcS: line 85: boot_milestone: not found
system: I rcS:def:starting /etc/rcS.d/S50diags
USER=root
prevlevel=N
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/
VERBOSE=no
READ_AHEAD=4
USER=root
prevlevel=N
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/
VERBOSE=no
IO_SCHED=anticipatory
USER=root
prevlevel=N
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/
VERBOSE=no
TMP_SIZE=32M
info firsttime:mount_rw:time=5280:Mounting root RW for first boot
info firsttime:cursor:Linking Xorg cursor:
ln: /usr/share/fonts/X11/misc/cursor.pcf: No such file or directory
info firsttime:mount_ro:time=5310:Mounting root RO
elevator: type  not found
info system:start:time=5380:
/etc/rcS.d/S50diags: line 466: f_proto: not found
info system:config:platform=yoshime3,board=celeste,rev=22,proto=N,wifi=Y,wan=Y:
info system:done:time=5730:
info cyttsp:update:vendor=CANDO:
/etc/rcS.d/S50diags: line 466: iptables-restore: not found
/opt/ar6k/include/dbglog.h.save: No such file or directory
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
mkdir: can't create directory '/var/local/system': Input/output error
info userstore:run:time=7010,action=start:
info userstore:mntus.param_not_found::mntus.param not found, initializing volume
info userstore:check_us::checking userstore filesystem

sfdisk: ERROR: sector 0 does not have an msdos signature
 /dev/mmcblk0p4: unrecognized partition table type
No partitions found
1+0 records in
1+0 records out
64 bytes (64B) copied, 0.042463 seconds, 1.5KB/s
BLKRRPART: Invalid argument

Disk /dev/mmcblk0p4: 44736 cylinders, 4 heads, 16 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature
 /dev/mmcblk0p4: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/mmcblk0p4p1            16   2863103    2863088   b  W95 FAT32
/dev/mmcblk0p4p2             0         -          0   0  Empty
/dev/mmcblk0p4p3             0         -          0   0  Empty
/dev/mmcblk0p4p4             0         -          0   0  Empty
Successfully wrote the new partition table

Re-reading the partition table ...
BLKRRPART: Invalid argument


sfdisk: ERROR: sector 0 does not have an msdos signature
 /dev/mmcblk0p4: unrecognized partition table type
No partitions found
crit userstore:create_failed::could not create the userstore partition
/etc/upstart/userstore: line 244: can't create /var/local/system/mntus.params: nonexistent directory
/etc/upstart/userstore: .: line 244: can't open '/var/local/system/mntus.params'
/etc/rcS.d/S50diags: line 13: /usr/local/sbin/dropbear: not found
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
mkdir: can't create directory '/var/local/eink': Input/output erEXT3-fs error (device mmcblk0p3): ext3_add_entry: ror
bad entry in directory #2: rec_len % 4 != 0 - offset=0, inode=3735924190, rec_len=21025, name_len=82
mkdir: can't create directory '/var/local/eink/': Input/output error
/etc/upstart/display: line 273: can't create /var/local/eink/waveforms/md5: nonexistent directory
info display:update:Creating panel directory:
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
mkdir: can't create directory '/var/local/eink/': Input/output error
failed to write out waveform file to /var/local/eink/panel/06_05_00ae_3c_2b4b02_07_dc_00000df5_85_12.wbf
WBF file of [/var/local/eink/panel/*.wbf] is invalid
/etc/upstart/display: line 285: can't create /var/local/eink/panel/panel_id: nonexistent directory
/etc/upstart/display: line 285: can't create /var/local/eink/panel/version: nonexistent directory
mounting waveform filesystem
rm: /mnt/wfm/images: is a directory
cp: can't stat '': No such file or directory
gzip: /mnt/wfm/waveform_to_use: No such file or directory
info display:update:Creating waveform proxy from  at /mnt/wfm/waveform_to_use:
Using 25C-only waveform!
info display:update:Displaying splash screen:
umounting waveform filesystem
info display:started:time=16690:
/etc/upstart/battery-diags: line 91: f_proto: not found
info battery:charged:cap=11,mV=3766,mAH=133:
USER=root
prevlevel=N
OLDPWD=/
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/dev
VERBOSE=no
LD_LIBRARY_PATH=/usr/lib/tts/speech/components/common/:/usr/lib/tts
/etc/rcS.d/S50diags: line 13: alsactl: not found
/etc/rcS.d/S50diags: line 13: audioServer: not found
FATAL: Module mxc_keyb not found.
/etc/rcS.d/S50diags: line 13: kb: not found
diags : /opt/factory/rootfs_md5_list not found.
Change list is: [174700]
Sending: mkdir -p /mnt/base-us/diagnostic_logs/
mkdir: can't create directory '/mnt/base-us/diagnostic_logs/': Read-only file system
PostMode len = 6 of 16
Ignoring PostMode
GlobalHalImpl: found DeviceType: 25
found: cyttsp
HalWifi: name: /mnt/us/tools/atheros/art_rel/art/bin, artRootPath: /mnt/us/tools/atheros/art_rel/art/bin
system: I mntroot:def:Making root filesystem writeable
EXT3 FS on mmcblk0p2, internal journal
Will output 1024 bit rsa secret key to '/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgwClKVrvQypg8EghwOrRkErSp0xKLhvR0fMaacMRRPWDc5okz33+DCP9bHD+vFTJueECFZEdWjOxjKC9HntvmWTw+CSr0NhTKv7xweDVKyG6I7TJkPGnUJMAP8eqjjDmiHNHeSorz//8eq97UjCRNDDVD26cwTihdcNwStlSofdBL6oP root@kindle
Fingerprint: md5 79:78:f4:9d:76:ba:83:57:bb:68:5f:55:5d:a8:02:8f
system: I mntroot:def:Making root filesystem read-only
DeviceSettingObjectImpl: setUserVersion (NULL)
        PCBID: 0151607XXXXXXXXX
        MainTest:exe
        MainTest:exeTest Set CPU to faster speed
system_diags[MainTest] 1 INFO : Start test
   CELESTE - System Diags
   ~~~~  1.9.389.174700  ~~~~
     pcbId:01516XXXXXXX
~ S ~ Device Setting
P) Touch Sensor Plate Test
O) Operator test suite
E) 511
N) Misc individual diagnostics
Y) nART factory test
U) USB device mode
D) Exit, Reboot or Disable Diags
L) Lock diags screen
X) Exit


EInkPanel:clear_display m_eink.size: [786432]
        MainTest:is_chargerConnected: charger is: connected
mxc_rtc: saved=0x0 boot=0x51
boot: I def:rbt:reset=user_reboot,version=174700:
U
[Found] name: KEY_U, symbol: U, value: 22
Cmd: U
        USB_DeviceModeTest:exe
system_diags[USB_DeviceModeTest] 1 INFO : Start test
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
        testName = USBexport
        export USB
        Check USB_cable
        Exporting USB user store
found: g_file_storage
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
   CELESTE - USB device mode -  11
   ~~~~  1.9.389.174700  ~~~~
     pcbId:015160XXXXXXX
   USB device exported

   Once you are done
   Eject the USB device from the PC then


   Battery capacity  11

~ Q ~ to continue

X) Exit


EInkPanel:clear_display m_eink.size: [786432]
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
   CELESTE - USB device mode -  11
   ~~~~  1.9.389.174700  ~~~~
     pcbId:0151607XXXXXXXX
   USB device exported

   Once you are done
   Eject the USB device from the PC then


   Battery capacity  11

~ Q ~ to continue

X) Exit


EInkPanel:clear_display m_eink.size: [786432]
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
   CELESTE - USB device mode -  11
   ~~~~  1.9.389.174700  ~~~~
     pcbId:01516071XXXXXXX
   USB device exported

   Once you are done
   Eject the USB device from the PC then


   Battery capacity  11

~ Q ~ to continue

X) Exit


EInkPanel:clear_display m_eink.size: [786432]
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
   CELESTE - USB device mode -  11
   ~~~~  1.9.389.174700  ~~~~
     pcbId:0151607XXXXXXX
   USB device exported

   Once you are done
   Eject the USB device from the PC then


   Battery capacity  11

~ Q ~ to continue

X) Exit


EInkPanel:clear_display m_eink.size: [786432]
        USB_DeviceModeTest:is_chargerConnected: charger is: connected
x
[Found] name: KEY_X, symbol: X, value: 45
Cmd: X
run: Status: WAIT_FOR_STATUS_EXIT
Un export the user store
Diff time =  0.00
bio too big device loop0 (1 > 0)
FAT: unable to read boot sector
mount: /dev/loop/0: can't read superblock
        Cannot open /mnt/base-us/diagnostic_logs\!
system_diags[USB_DeviceModeTest] 1 FAIL : 126
system_diags[USB_DeviceModeTest] 1 INFO : End test
exe: Status: WAIT_FOR_STATUS_EXECUTED
   CELESTE - System Diags
   ~~~~  1.9.389.174700  ~~~~
     pcbId:0151607XXXXXXX
S) Device Setting
P) Touch Sensor Plate Test
O) Operator test suite
E) 511
N) Misc individual diagnostics
Y) nART factory test
~ U ~ USB device mode
D) Exit, Reboot or Disable Diags
L) Lock diags screen
X) Exit


EInkPanel:clear_display m_eink.size: [786432]
        MainTest:is_chargerConnected: charger is: connected

Any idea where I can start with this if it's possible at all?

knc1 · 10-27-2019, 03:37 PM

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.

That seems to indicate you have been trying to mess with the USER VISIBLE usb accessible storage.

Quote:

When in diags you select USB Mode it just keeps refreshing the display and not doing anything

That is correct.
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.

FruitPolo · 10-27-2019, 03:42 PM

Quote:

Originally Posted by knc1

That seems to indicate you have been trying to mess with the USER VISIBLE usb accessible storage.

I got this kindle for free in this condition. If I knew what had gone on, maybe i'd have a bit better idea how to sort this but I have no idea.

Quote:

Originally Posted by knc1

That is correct.
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.

Oh, I didn't understand that was for the fastboot connection. Sorry. I thought it was usb accessible storage.

knc1 · 10-28-2019, 11:10 AM

Quote:

Originally Posted by FruitPolo

- - - - -
Oh, I didn't understand that was for the fastboot connection. Sorry. I thought it was usb accessible storage.

On the menu you posted:

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

If you mean using entry "E", then it does mean for you to insert the USB cable so that you can access user storage from your PC.

But...
You should also read:

Code:

=== BATTERY IS CRITICALLY LOW - DEFERRING BOOT ===
Charge: 7% [#####:::::::::::::::::::::::::::::::::::::::::::::::::::::]

Which means exactly what it says.
But instead:

Code:

[Critical Battery Lock-out Menu]
1. Skip
R. reboot
Choose: /-

If appears that you ignored the low battery condition (or you allowed the system to ignore the low battery condition).

Code:

*** Skipping critical battery lock-out.
INFO:!!! Checking MBR /dev/mmcblk0 !!!!

And now guess what ...
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.

FruitPolo · 10-28-2019, 03:18 PM

Quote:

Originally Posted by knc1

On the menu you posted:
If you mean using entry "E", then it does mean for you to insert the USB cable so that you can access user storage from your PC.

Yes, Entry E when selected on both linux and windows when connected to them shows no filesystem.

Quote:

Originally Posted by knc1

And now guess what ...
The system tried to fscheck the system, the eMMC lost power during the process, and you have now fried the eMMC.

That would be something I could believe if it wasn't the exact same serial output I have been getting with the battery fully charged since the very first time I accessed serial. It was only low battery during that time of reading the serial because it had bootlooped itself so much and I didn't disconnect the battery. I always have it connected to power when using serial.

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.

knc1 · 10-28-2019, 04:01 PM

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.

10-27-2019, 01:00 PM	#3
NiLuJe 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.

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

10-27-2019, 06:56 AM	#1
FruitPolo 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 When attempting to access the kindle's fat32 partition on the computer through recovery or diag it appears to have no filesystem as the computer asks to format the drive before using. When in recovery however, Export FAT Partition causes an immediate YKNR screen. 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-28-2019, 04:01 PM	#9
knc1 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.