Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 08-24-2019, 04:42 PM   #1
sz.bali
Junior Member
sz.bali began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Jul 2019
Device: Kindle Paperwhite 3 (2015)
Help debricking PW2

Hi,

I have a Paperwhite 2 that shows the kindle logo on the screen and doesn't respond to turning on/off or hard reset.

I opened up the kindle and connected to the serial port and this is the output I get:
Code:
HW


U-Boot 2009.08-lab126 (Mar 22 2019 - 17:58:34)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   27 C, calibration data 0x59250f5f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 22000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
MMC:  FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
Board: Pinot WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 027220C143040BAQ
S/N: 9017220143120BHL
I2C:   ready
DRAM:  256 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0xfff0000
POST done in 57 ms
Battery voltage: 3994 mV

Hit any key to stop autoboot:  0
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   Linux-3.0.35-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2957608 Bytes =  2.8 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.097342] No Legacy reboot reason code to print
[    0.278325] LPDDR2 MfgId: 0x1 [Samsung]
[    0.282188]
[    0.282191] just text: vaddr c0133fdc, va 0xc0133200 pa 0x801000c3 attr 0x6
[    0.294668]
[    0.294671] nmx6sl_wfi_iram: vaddr d084e000, va 0xd084e200 pa 0x904043 attr 0x2
[    0.303563]
[    0.303566] mx6sl_ddr: vaddr d0856000, va 0xd0856200 pa 0x905043 attr 0x2
[    0.311898]
[    0.311900] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.322673]
[    0.322675] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.336078]
[    0.336081] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.345918]
[    0.345920] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.359405]
[    0.359408] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.369294]
[    0.369296] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
DEBUG:recovery-util.c:1703:setup_die_signals():Installed signal handlers.
3.0.35-lab126 #2 PREEMPT Fri Mar 22 18:08:46 UTC 2019 armv7l
Press [ENTER] for recovery menu...       1 \BOOTING DEFAULT.
IP-Config: no devices to configure
kinit: Mounted root (ext3 filesystem) readonly.
info sytem:mounted_proc::
info system:mounted_sys::
info system:sy00::
info system:mounted_dev::
info milestone:9.00:49.1:49.1
info milestone:9.04:49.2:49.2
info milestone:9.07:49.3:49.3
info milestone:9.13:49.4:49.4
info milestone:9.16:49.5:49.5
info sytem:mounted_tmpfs::
info milestone:9.25:sy50:sy50
info system:start:time=9270:time=9270
info hardware:no_wan:: WiFi only device. No WAN found
info system:config:platform=wario,board=pinot,rev=22,proto=Y,wifi=Y,wan=N:platform=wario,board=pinot,rev=22,proto=Y,wifi=Y,wan=N
info milestone:9.43:sy51:sy51
lipc-send-event[848]: W def:lipc:method=LipcOpenEx service=com.lab126.hal:Method has been deprecated.
lipc-send-event[846]: W def:lipc:method=LipcOpenEx service=com.lab126.hal:Method has been deprecated.
lipc-send-event[846]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[846]: C def:dbusi::Failed to init dbus
lipc-send-event[846]: E def:open::Failed to open LIPC
lipc-send-event[846]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
lipc-send-event[848]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[848]: C def:dbusi::Failed to init dbus
lipc-send-event[848]: E def:open::Failed to open LIPC
lipc-send-event[848]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
info milestone:10.30:sy99:sy99
info system:done:time=10330:time=10330
crond[864]: crond (busybox 1.28.3) started, log level 8

init.exe: sshd main process (863) terminated with status 127
init.exe: sshd main process ended, respawning
init.exe: recevent pre-start process (867) terminated with status 1



Welcome to Kindle!

kindle login: info milestone:10.64:sc01:sc01
info system_fs_loopbacks:mountingfs:Mounting compressed directories filesystem images:Mounting compressed directories filesystem images
info milestone:10.67:sc02:sc02
info milestone:10.71:/usr/share/X11/xkb:/usr/share/X11/xkb
info system_fs_loopbacks:mounted:Image /usr/share/X11/xkb.sqsh mounted:Image /usr/share/X11/xkb.sqsh mounted
info milestone:10.76:3:3
info milestone:10.76:sc05:sc05
info milestone:10.78:/usr/java/lib/fonts:/usr/java/lib/fonts
info system_fs_loopbacks:mounted:Image /usr/java/lib/fonts.sqsh mounted:Image /usr/java/lib/fonts.sqsh mounted
info milestone:10.82:4:4
info milestone:10.83:sc05:sc05
info milestone:10.85:/etc/kdb.src:/etc/kdb.src
info system_fs_loopbacks:mounted:Image /etc/kdb.src.sqsh mounted:Image /etc/kdb.src.sqsh mounted
info milestone:10.88:5:5
info milestone:10.89:sc05:sc05
info milestone:10.91:/usr/lib/locale:/usr/lib/locale
info system_fs_loopbacks:mounted:Image /usr/lib/locale.sqsh mounted:Image /usr/lib/locale.sqsh mounted
info milestone:10.94:6:6
info milestone:10.95:sc05:sc05
info milestone:10.97:/usr/share/keyboard:/usr/share/keyboard
info system_fs_loopbacks:mounted:Image /usr/share/keyboard.sqsh mounted:Image /usr/share/keyboard.sqsh mounted
info milestone:11.09:7:7
info milestone:11.10:sc05:sc05
info milestone:11.12:/opt/var/local:/opt/var/local
info system_fs_loopbacks:mounted:Image /opt/var/local.sqsh mounted:Image /opt/var/local.sqsh mounted
info milestone:11.16:8:8
info milestone:11.17:sc05:sc05
info milestone:11.18:sc07:sc07
info system:emiting_event:mounted_fs_loopbacks:mounted_fs_loopbacks
debug sytem:event_emitted:mounted_fs_loopbacks:mounted_fs_loopbacks
info milestone:11.23:fs75:fs75
info system:emiting_event:loaded_modules_dependencies:loaded_modules_dependencies
debug sytem:event_emitted:loaded_modules_dependencies:loaded_modules_dependencies
info modules:modprobe:loading module fsl_otg_arc:loading module fsl_otg_arc
info system:emiting_event:loaded_fsl_otg_arc:loaded_fsl_otg_arc
debug sytem:event_emitted:loaded_fsl_otg_arc:loaded_fsl_otg_arc
info modules:modprobe:loading module ehci_hcd:loading module ehci_hcd
info system:emiting_event:loaded_ehci_hcd:loaded_ehci_hcd
debug sytem:event_emitted:loaded_ehci_hcd:loaded_ehci_hcd
info modules:modprobe:loading module fuse:loading module fuse
info system:emiting_event:loaded_fuse:loaded_fuse
debug sytem:event_emitted:loaded_fuse:loaded_fuse
info hardware:no_wan:: WiFi only device. No WAN found
info system:emiting_event:loaded_ppp_async:loaded_ppp_async
info milestone:11.52:fs00:fs00
debug sytem:event_emitted:loaded_ppp_async:loaded_ppp_async
info system:emiting_event:loaded_fakekey:loaded_fakekey
debug sytem:event_emitted:loaded_fakekey:loaded_fakekey
info filesystems_keys:not applicable for this device type::
info filesystems_var_local:createvarlocal:Creating /var/local filesystem:Creating /var/local filesystem
[   17.147522] mmc0: Timeout, intmask=0x00100000
[   17.154942] mmcblk0: error -110 transferring data, sector 527644, nr 8, cmd response 0x900, card status 0xb00
[   22.588875] mmc0: Timeout, intmask=0x00100000
[   22.594275] mmcblk0: error -110 transferring data, sector 527644, nr 8, cmd response 0x900, card status 0x0
[   22.604626] end_request: I/O error, dev mmcblk0, sector 527644
[   22.610798] mmc0: Timeout, intmask=0x00010000
[   22.615157] mmc0: Trigger MMC Recovery
[   22.618985] mmcreinit_work_func: Resetting MMC, try=1, total_time=0
[   22.694722] mmc_reinit: Reinit card
[   32.714980] mmc_reinit: Error (-110) send op cond
[   32.719716] mmcreinit_work_func: Resetting MMC, try=2, total_time=10100
[   32.964979] mmc_reinit: Reinit card
[   42.974981] mmc_reinit: Error (-110) send op cond
[   42.979718] mmcreinit_work_func: Resetting MMC, try=3, total_time=20360
[   44.684983] sdhci sdhci-esdhc-imx.1: esdhc_send_74_clocks: Out of loop, INTA 0x08, Timeout 0
[   44.693427] mmc_reinit: Reinit card
I've managed to get recovery menu, but I don't know which option to choose, or even if one of the option would fix the kindle (or at least safe to try without destroying the system even more). These are the menu options:
Code:
Menu
====
3. Load MMC over USB storage
4. Erase MMC
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
C. Configure USB networking
N. Boot NFS over USB
Z. Boot NFS over ETH
L. List files in many directories
S. Access the shell
8. Test low level screens
D. dmesg / kernel printk ring buffer.
Q. quit
Can somebody make sense of the output and have an idea what could be the problem and how to fix it?
sz.bali is offline   Reply With Quote
Old 08-24-2019, 09:48 PM   #2
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 831
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
I'm no expert in this, but seeing that I/O error on the MMC device may indicate that the storage chip itself is dead/bad. If this is indeed the case you have a spare screen unless you have a workstation available to replace the MMC itself.

I will defer to others with more experience in this area, as it might be possible to recover from this. Although it might have reduced capacity available even after recovery is complete.

Dave
dhdurgee is offline   Reply With Quote
Old 08-24-2019, 10:08 PM   #3
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Where you captured this:
Code:
[   22.610798] mmc0: Timeout, intmask=0x00010000 
[   22.615157] mmc0: Trigger MMC Recovery 
[   22.618985] mmcreinit_work_func: Resetting MMC, try=1, total_time=0 
[   22.694722] mmc_reinit: Reinit card
Let it run, at least over night, to see if it can do the recovery.
You can't wear it out any worse than it probably already is.
Keep the USB cable plugged while it runs, you don't want it to run on the battery like that, not for over night.

Last edited by knc1; 08-24-2019 at 10:15 PM.
knc1 is offline   Reply With Quote
Old 08-25-2019, 05:29 AM   #4
sz.bali
Junior Member
sz.bali began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Jul 2019
Device: Kindle Paperwhite 3 (2015)
Quote:
Originally Posted by knc1 View Post
Let it run, at least over night, to see if it can do the recovery.
The problem is it stops the recovery after 5 tries:
Code:
.
.
.
[   57.943392] mmc_reinit: Reinit card
[   67.954949] mmc_reinit: Error (-110) send op cond
[   67.959686] mmcreinit_work_func: Resetting MMC, try=5, total_time=45320
[   75.154951] sdhci sdhci-esdhc-imx.1: esdhc_send_74_clocks: Out of loop, INTA 0x08, Timeout 0
[   75.163396] mmc_reinit: Reinit card
[   85.174949] mmc_reinit: Error (-110) send op cond
[   85.179672] mmcreinit_work_func: Resetting MMC: failed. Give up after 5 retries, total_time=62540
And after this there's no other output, so I think it won't change anything if I run it overnight. Or maybe there's a way to let the recovery run past 5 tries? Or anything else to try?
sz.bali is offline   Reply With Quote
Old 08-27-2019, 05:53 AM   #5
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by sz.bali View Post
The problem is it stops the recovery after 5 tries:
Code:
.
.
.
[   57.943392] mmc_reinit: Reinit card
[   67.954949] mmc_reinit: Error (-110) send op cond
[   67.959686] mmcreinit_work_func: Resetting MMC, try=5, total_time=45320
[   75.154951] sdhci sdhci-esdhc-imx.1: esdhc_send_74_clocks: Out of loop, INTA 0x08, Timeout 0
[   75.163396] mmc_reinit: Reinit card
[   85.174949] mmc_reinit: Error (-110) send op cond
[   85.179672] mmcreinit_work_func: Resetting MMC: failed. Give up after 5 retries, total_time=62540
And after this there's no other output, so I think it won't change anything if I run it overnight. Or maybe there's a way to let the recovery run past 5 tries? Or anything else to try?
You are correct.
I somehow missed those lines.

As mentioned above in another post here, you now have a used screen for sale.
knc1 is offline   Reply With Quote
Old 09-04-2019, 05:22 PM   #6
WaseemAlkurdi
Zealot
WaseemAlkurdi began at the beginning.
 
Posts: 147
Karma: 20
Join Date: Jul 2019
Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen
Quote:
Originally Posted by knc1 View Post
You are correct.
I somehow missed those lines.

As mentioned above in another post here, you now have a used screen for sale.
Can't OP replace the eMMC instead? I remember that you once said (https://www.mobileread.com/forums/sh...d.php?t=271750) that it costs under $10.
But one must keep in mind that the eMMC is not trivial to replace (chip rework station, reworking skills, ...)
WaseemAlkurdi is offline   Reply With Quote
Old 09-04-2019, 05:48 PM   #7
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by WaseemAlkurdi View Post
Can't OP replace the eMMC instead? I remember that you once said (https://www.mobileread.com/forums/sh...d.php?t=271750) that it costs under $10.
But one must keep in mind that the eMMC is not trivial to replace (chip rework station, reworking skills, ...)
There is a thread here for the purpose.
Not a trivial fix.


Not for a device that the user has failed to create the required backup files (I have posted a script for that purpose here.)
I.E: Some of the user and device information lives OUTSIDE of the file system. My posted script will backup that information also. And you will be unable to use the new device if you do not have that information available.
knc1 is offline   Reply With Quote
Reply

Tags
kindle paperwhite 2, recovery, unbrick


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
PW2 Replace japanese PW2 screen on a french-bought PW2? Narval Kindle Developer's Corner 6 05-17-2019 06:36 PM
Which one are you ordering: PW2 wifi or PW2 3G jocampo Amazon Kindle 37 08-18-2014 10:48 AM
Help for PW2 debricking. reggie.yang Kindle Developer's Corner 0 04-02-2014 10:40 PM
Help debricking K3 metafisica Kindle Developer's Corner 2 06-06-2013 06:33 AM
Debricking sowtus Kindle Developer's Corner 11 10-05-2012 11:11 AM


All times are GMT -4. The time now is 01:36 PM.


MobileRead.com is a privately owned, operated and funded community.