|
You've already tried a lot of things, much respect for that. I'd probably done the same things and I can't think of much other possibilities than hardware failure. Well, I would have probably tried out k3flasher on Linux, too, and I would in fact be interested in how it behaves. I don't expect a success report with it, though.
You could also hook up a serial connection (though this is cumbersome due to the low-voltage requirement), out of interest whether uboot and early kernel init run well.
About the blank screen: I think it is only initialized when the kernel's eink drivers get loaded.
Between the lines of what you wrote, I was thinking a lot about the Tight-Restart-Loop that keeps so many people from using the ATK/k3flasher method. I'm still puzzled over that distinct, clear repeating picture of this specific error you are facing. After figuring out USB Downloader mode for backup/recovery, this seems to be the next hurdle for K3 recovery.
|