PW3 Need help for debricking

[algenist]

Hello,
After reading a lot of instructions and thread and dealing with some technical problems I stuck at some point and I really need a pro advice.

I bought this kindle from ebay as bricked thinking it would be an easy fix. Apparently I was wrong. The seller claimed it is not used for a long time and it didn't work after 4 hours charging. When I get it realized factory refurbished.

So, When I get it,
- I tried, 2 days charging with a wall charger and resetting by holding 20 and 40 seconds
- Opened it, it was very clean there isn't any sign of amateur work.
- tested battery, it is ok.
- made a serial connection, here is my first screen,

U-Boot 2009.08-lab126 (Jun 29 2019 - 10:27:24)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   36 C, calibration data 0x59a5205f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 24000000Hz
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: Muscat WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 067070918133198Y
S/N: G090KBxxxxxxxxxxx
I2C:   ready
DRAM:  512 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0x1fff0000
POST done in 111 ms
Battery voltage: 4154 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:    2952672 Bytes =  2.8 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.096583] boot: C def:bcut:batterycut=1
[    0.263949] pmic_soda_connects_notify_otg_out:423
[    0.280222] LPDDR2 MfgId: 0x5 [Nanya]
[    0.284076]
[    0.284079] just text: vaddr c0131fdc, va 0xc0131200 pa 0x801000c3 attr 0x6
[    0.292358]
[    0.292361] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
[    0.305407]
[    0.305410] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
[    0.313728]
[    0.313731] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.322453]
[    0.322456] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.330842]
[    0.330844] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.340917]
[    0.340919] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.354354]
[    0.354357] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.363294]
[    0.363296] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
DEBUG:recovery-util.c:1680:setup_die_signals():Installed signal handlers.
3.0.35-lab126 #2 PREEMPT Tue Jul 24 06:43:56 PDT 2018 armv7l
Press [ENTER] for recovery menu...       0 /BOOTING DEFAULT.
IP-Config: no devices to configure
kinit: Mounted root (ext3 filesystem) readonly.

I couldn't see any error and reboot in to diags menu. There were some errors but it I could see the menu on the touch screen.

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

Starting kernel ...

[    0.098553] boot: C def:bcut:batterycut=1
[    0.285357] LPDDR2 MfgId: 0x5 [Nanya]
[    0.289259]
[    0.289263] just text: vaddr c0150d44, va 0xc0150200 pa 0x801000c3 attr 0x6
[    0.301812]
[    0.301816] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
[    0.310661]
[    0.310664] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
[    0.318991]
[    0.318994] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.329831]
[    0.329834] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.344184]
[    0.344187] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.356327]
[    0.356331] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.366732]
[    0.366735] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.376635]
[    0.376637] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
3.0.35-lab126 #1 PREEMPT Thu Jul 27 04:48:26 PDT 2017 armv7l
Press [ENTER] for recovery menu...       0 //dev/mmcblk0p4:
CHS=4/16/99776 size=3269459968 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6385648
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
BOOTING DEFAULT.
IP-Config: no devices to configure
kinit: Mounted root (ext3 filesystem) readonly.
init started: BusyBox v1.17.1 (2017-07-27 04:40:39 PDT)
starting pid 625, 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
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
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
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/
VERBOSE=no
TMP_SIZE=32M
info firsttime:mount_rw:time=6350: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=6380:Mounting root RO
[    6.446829] elevator: type
[    6.446834]  not found
[    6.451987] elevator: switch to
[    6.451991]  failed
[    6.465873] elevator: type
[    6.465878]  not found
[    6.471031] elevator: switch to
[    6.471034]  failed
[    6.484767] elevator: type
[    6.484772]  not found
[    6.489988] elevator: switch to
[    6.489992]  failed
info system:start:time=6490:
/etc/rcS.d/S50diags: line 500: f_proto: not found
info hardware:no_wan::WiFi only device. No WAN found
info system:config:platform=wario,board=muscat,rev=7,proto=N,wifi=Y,wan=N:
info system:done:time=6900:
ls: /lib/firmware/cyttsp4/muscat*.bin: No such file or directory
info cyttsp4:update:cyttsp4 fw ver=0097 file version=.bin:
/etc/upstart/cyttsp: line 49: syntax error:  0x.bin
crit modules:modprobe_failed:failed to load touch module:
/etc/rcS.d/S50diags: line 500: iptables-restore: not found
/opt/ar6k/include/dbglog.h.save: No such file or directory
info userstore:run:time=8200,action=start:
info userstore:start:found_bootup_flag:Found BOOTUP flag file
dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
      8192 bytes per cluster
      2134 reserved sectors
First FAT starts at byte 1092608 (sector 2134)
         2 FATs, 32 bit entries
   1594880 bytes per FAT (= 3115 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4282368 (sector 8364)
    398580 data clusters (3265167360 bytes)
32 sectors/track, 64 heads
         0 hidden sectors
   6385648 sectors total
Checking for unused clusters.
Checking free cluster summary.
/dev/loop/0: 864 files, 32135/398580 clusters
Wifi cal bin symbolic link AR6003_calfile.bin is already created
system: I mntroot:def:Making root filesystem writeable
/etc/rcS.d/S50diags: line 13: /usr/local/sbin/dropbearkey: not found
system: I mntroot:def:Making root filesystem read-only
/etc/rcS.d/S50diags: line 13: /usr/local/sbin/dropbear: not found
mounting waveform filesystem
waveform filesystem already mounted
info display:update:Checking '/opt/eink/images/R206_ED060KD1C4' for overrides:
umounting waveform filesystem
drawing default
cannot find image: /opt/amazon/low_level_screens/splash.png
info display:started:time=9890:
/etc/upstart/battery-diags: line 91: f_proto: not found
info battery:charged:cap=100,mV=4158,mAH=1420:
USER=root
prevlevel=N
OLDPWD=/
HOME=/
runlevel=S
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: kb: not found
diags : /opt/factory/rootfs_md5_list not found.
Change list is: [321316]
Sending: mkdir -p /mnt/base-us/diagnostic_logs/
PostMode len = 6 of 16
Ignoring PostMode
DiscoveryObjectImpl:getDeviceDiagsInfo FOUND: MUSCAT_WFO: [067] [103] with 067070918133198Y
Device found: MUSCAT_WFO [067] [103]
GlobalHalImpl: found DeviceType: 0x67
found: cyttsp4_i2c
found: cyttsp4_core
found: cyttsp4_mt_b
[   10.098446] cyttsp4_device_access_init: Registering device access device for core_id: main_ttsp_core
[   10.108575] cyttsp4_device_access cyttsp4_device_access.main_ttsp_core: cyttsp4_device_access_probe
[   10.118541] cyttsp4_device_access_init: Cypress TTSP Device Access (Built 20121109) rc=0
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "max77696-onkey"
Supported events:
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "cyttsp4_mt"
Supported events:
 failed to open /dev/input/event2
 failed to open /dev/input/event3
 failed to open /dev/input/event4
 failed to open /dev/input/event5
 failed to open /dev/input/event6
 failed to open /dev/input/event7
Ignoring PostMode
diag>open_device m_vsInfo.xres: 1072
get_m_test_xmlFile wfo.xml
        device type = 0x67
        PCBID: 067070918133198Y
        TCP_IP_Server_Handler:start_USBnet Enabling USB net
Cannot open xmlFile /mnt/base-us/USBnet.xml
NOT Found NFS path
[   10.315982] unregistered gadget driver 'g_file_storage'
ERROR: Module g_serial does not exist in /proc/modules
[   10.375718] usb0: MAC ee:59:00:00:00:15
[   10.379562] usb0: HOST MAC ee:29:00:00:00:15
[   10.383838] g_ether gadget: controller 'fsl-usb2-udc' not recognized; trying CDC Ethernet (ECM)
[   10.415611] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
[   10.422247] g_ether gadget: g_ether ready
[   10.431342] fsl-usb2-udc: bind to driver g_ether
system: I mntroot:def:Making root filesystem writeable
[   10.485896] EXT3-fs (mmcblk0p2): using internal journal
sock_init 1888

I have navigated to usb export and kindle window popup my screen.
- I downloaded latest firmware from amazon and copied to kindle. After reboot it is installed successfully but the nothing was changed except that I have screen lights now.
- I tried factory firmware with some way but it refuses to install.

Now my only option is fastboot I think. But I cannot connect fastboot to device in windows10 due to the lack of a proper driver. USB linux is pain in the ass because of the UEFI and my computer's recovery which interferes many distros I have tried.

I need some good advice to go on...

[knc1]

That looks like a partial update (kernel and /lib/modules/* do not match).

[algenist]

Originally Posted by knc1

That looks like a partial update (kernel and /lib/modules/* do not match).

Thank you for your quick response. What do you suggest at this point? Factory firmware gives an error when I try to install it by the way of copying and rebooting. I think it is some kind of downgrade protection.

[algenist]

Solved Thanks.
I used my wife's mac for fastboot. Flashed uImage and rootfs.img. My kindle is alive again.

[knc1]

Originally Posted by algenist

Solved Thanks.
I used my wife's mac for fastboot. Flashed uImage and rootfs.img. My kindle is alive again.

And there is the cause of your incomplete file system image ...
Kindles are not able to completely read rootfs.img (file to large, but no error given) with fastboot.


What you have now is a mixed set of system files, when you hit the wrong one, then the Kindle will fail.

[algenist]

Originally Posted by knc1

And there is the cause of your incomplete file system image ...
Kindles are not able to completely read rootfs.img (file to large, but no error given) with fastboot.


What you have now is a mixed set of system files, when you hit the wrong one, then the Kindle will fail.

I don't have any experience on kindles. I thought fastboot program can handle it. Somehow, it survived after first update. I spent a lot of time trying to run necessary tools. So I hope it won't fail for a while...