PW3 Is this Kindle fixable?

[edea]

Hello everyone!

I am trying to fix a PW3 (DP75SDI with S/N starting by G090KB).
It doesn't boot at all and does nothing when connected to a PC by USB.

Silly me, I thought all DP75SDI were the same and I swapped the faulty board with another working DP75SDI board, but it turns out the working board is from a PW2, and now my screen shows as half black half white with black lines. I hope this didn't break the screen

Back to the faulty PW3 board, I am trying to see if it's possible to recover it.

When connected to the serial port, I get this (I am using CuteCom on a Rpi4):

[13:56:51:226] U-Boot 2009.08-lab126 (Feb 04 2020 - 07:55:13)
[13:56:51:226] 
[13:56:51:226] CPU: Freescale i.MX6 family TO0.0 at 996 MHz
[13:56:51:226] Temperature:   37 C, calibration data 0x5d95575f
[13:56:51:226] mx6sl pll1: 996MHz
[13:56:51:226] mx6sl pll2: 528MHz
[13:56:51:226] mx6sl pll3: 480MHz
[13:56:51:226] mx6sl pll8: 50MHz
[13:56:51:226] ipg clock     : 66000000Hz
[13:56:51:226] ipg per clock : 24000000Hz
[13:56:51:226] uart clock    : 80000000Hz
[13:56:51:226] cspi clock    : 60000000Hz
[13:56:51:226] ahb clock     : 132000000Hz
[13:56:51:226] axi clock   : 198000000Hz
[13:56:51:226] emi_slow clock: 22000000Hz
[13:56:51:226] ddr clock     : 396000000Hz
[13:56:51:226] usdhc1 clock  : 198000000Hz
[13:56:51:226] usdhc2 clock  : 198000000Hz
[13:56:51:321] usdhc3 clock  : 198000000Hz
[13:56:51:321] usdhc4 clock  : 198000000Hz
[13:56:51:321] MMC:  FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
[13:56:51:385] Board: Muscat WFO
[13:56:51:385] Boot Reason: [ POR ]
[13:56:51:385] Boot Device: NAND
[13:56:51:385] Board Id: 0670509174530R1M
[13:56:51:385] S/N: G090KB and the rest of the S/N
[13:56:51:385] I2C:   ready
[13:56:51:385] DRAM:  512 MB
[13:56:51:385] Using default environment
[13:56:51:385] 
[13:56:51:385] In:    serial
[13:56:51:385] Out:   serial
[13:56:51:385] Err:   serial
[13:56:51:385] Quick Memory Test 0x80000000, 0x1fff0000
[13:56:51:481] POST done in 111 ms
[13:56:52:457] Battery voltage: 3713 mV
[13:56:52:457] 
[13:56:52:457] Hit any key to stop autoboot:  1 <0x08><0x08><0x08> 0 
[13:56:54:418] ## Booting kernel from Legacy Image at 80800000 ...
[13:56:54:418] Bad Header Checksum
[13:56:54:418] ERROR: can't get kernel image!
[13:56:54:418] uboot >

And that's it, I don't have a clue about how to proceed now. Read about some recovery/forensic images on ixtab .tk but the site seems down.

How do I continue?

[eddie.t.h]

You need to upload the kernel using fastboot. You will find the kernel in each update file, you can unpack it using kindletool. Search the forum it has been described many times.

[edea]

Originally Posted by eddie.t.h

You need to upload the kernel using fastboot. You will find the kernel in each update file, you can unpack it using kindletool. Search the forum it has been described many times.

First thing I tried is this:

 uboot > bist fastboot

I hit enter and absolutely nothing happens

[eddie.t.h]

Try the same "fastboot" without bist.
Have you checked if it can not be run in diagnostic mode (bootm 0xe41000)?

[edea]

Originally Posted by eddie.t.h

Try the same "fastboot" without bist.

Just "fastboot" is not recognised. And just "bist" does nothing.

ERROR: can't get kernel image!
[23:06:23:375] uboot > fastboot
[23:06:27:454] Unknown command 'fastboot' - try 'help'
[23:06:27:510] uboot > help
[23:06:32:969] ?       - alias for 'help'
[23:06:32:969] base    - print or set address offset
[23:06:32:969] bist    - start Built In Self Test
[23:06:32:969] boot    - boot default, i.e., run 'bootcmd'
[23:06:32:969] bootd   - boot default, i.e., run 'bootcmd'
[23:06:32:969] bootm   - boot application image from memory
[23:06:32:969] cmp     - memory compare
[23:06:32:969] coninfo - print console devices and information
[23:06:32:969] cp      - memory copy
[23:06:32:969] Crc32   - checksum calculation
[23:06:32:969] go      - start application at address 'addr'
[23:06:32:969] help    - print online help
[23:06:32:969] idme    - idme    - Set nv ram variables
[23:06:32:969] 
[23:06:32:969] loop    - infinite loop on address range
[23:06:33:113] md      - memory display
[23:06:33:113] mm      - memory modify (auto-incrementing address)
[23:06:33:113] mtest   - simple RAM read/write test
[23:06:33:113] mw      - memory write (fill)
[23:06:33:113] nm      - memory modify (constant address)
[23:06:33:113] printenv- print environment variables
[23:06:33:113] reset   - Perform<break>
[23:06:33:113] RESET of the CPU
[23:06:33:113] run     - run commands in an environment variable
[23:06:33:113] setenv  - set environment variables
[23:06:33:113] version - print monitor version
[23:06:33:113] uboot >

Originally Posted by eddie.t.h

Have you checked if it can not be run in diagnostic mode (bootm 0xe41000)?

How can I check that?

[edea]

Originally Posted by eddie.t.h

Have you checked if it can not be run in diagnostic mode (bootm 0xe41000)?

Seems I can't edit my previous post.

uboot > bootm 0xe41000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot >

[eddie.t.h]

Well, it gets a little complicated. You need to run your kindle in SDP mode (learn how to do it here https://www.mobileread.com/forums/sh...d.php?t=345655) and use uboot, which immediately boots to fastboot from this thread https://www.mobileread.com/forums/sh...d.php?t=342535