I'm in a similar situation with my Paperwhite 2. All of a sudden (since a lot of months, tbh, but it makes no difference) the device is being recognized as "SE Blank MEGREZ" and I've been trying to reflash the bootloader and all the stuff.
I managed to compile u-boot but now when I try to load it with MfgTool I am missing some of the expected serial output, such as the board name and the ram size:
Code:
U-Boot 2009.08-lab126 (Aug 03 2022 - 12:50:24)
CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature: 45 C, calibration data 0x5734fe5f
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
This is what I did:
I downloaded the Kindle_src_5.6.2.1_2634390002 source package (more recent ones are missing the boardinfo.h, and I found this to be complete, maybe there are more recent ones that are also complete).
I compiled the bundled linaro toolchain.
I patched include/configs/imx60_wario.h as explained
here, then I did the following:
Code:
make CROSS_COMPILE=arm-linux-gnueabi- imx60_wario_config
TYPE=prod make CROSS_COMPILE=arm-linux-gnueabi- -j4
cp u-boot.in ../u-boot-prod.bin
make clean
make CROSS_COMPILE=arm-linux-gnueabi- imx60_wario_bist_config
TYPE=bist make CROSS_COMPILE=arm-linux-gnueabi- -j4
cp u-boot.in ../u-boot-bist.bin
I copied the .bin files one level higher because I noticed that they would get erased by the clean command. Then I followed the other modifications for MfgTool that are listed in the same tried, and tried to flash the u-boot-prod.bin file.
The MfgTool itself reports a failure and here's the log, but still I get the (partial) information on the serial port.
Code:
DLL version: 2.2.3
Wednesday, August 03, 2022 14:28:39 Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[03AED888]
ModuleID[2] LevelID[10]: Device Manager thread is running
ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is C:\<hidden for privacy>\Mfgtools-Rel-4.1.0_130816_MX6SL_UPDATER\Profiles\MX6SL Linux Update\OS Firmware\u-boot.bin
ModuleID[2] LevelID[10]: *********MxHidDevice[03AED888] Jump to Ramkernel successfully!**********
ModuleID[2] LevelID[1]: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed
ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)
I have also tried unpacking with kindletool the update provided by Amazon and flashing the contained u-boot.bin, but that does not seem to work at all, and I get the following log from MfgTool (and no output on the serial port):
Code:
DLL version: 2.2.3
Wednesday, August 03, 2022 14:33:26 Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[0413D888]
ModuleID[2] LevelID[10]: Device Manager thread is running
ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is C:\<hidden for privacy>\Mfgtools-Rel-4.1.0_130816_MX6SL_UPDATER\Profiles\MX6SL Linux Update\OS Firmware\u-boot.bin
ModuleID[2] LevelID[1]: MxHidDevice::Write() Error writing to device 0x3e3.
ModuleID[2] LevelID[1]: RunPlugIn(): TransData(0x9804A0, 0x1A1DC,0x4147FC0) failed.
ModuleID[2] LevelID[1]: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed
ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)
Do you have any suggestion?