MobileRead Forums - View Single Post - K5 Backporting a newer version of the Kindle firmware/GUI from Paperwhite to Touch

WaseemAlkurdi · 07-23-2019, 03:45 PM

P.S.
1. If not for @geekmaster's U-Boot profiles (under the Select Boot thread) and imx_usb, then both my Kindle and I would have become toast by now.

2. /var/local/logs/* on the third eMMC partition did not change at all between boots.

3. (

) While I was getting my feet deep in the cesspool of "why the hell USB Downloader Mode doesn't blank the e-Ink display and how you should check your host's dmesg instead", a rather amazing thought (is it?) struck my head:
Why not use KVM and qemu to boot Android on the Kindle?
Note that we have U-Boot access, so we can modify ARM ELs however we please. This isn't possible on more "mainstream" consumer devices (like phones and ARM tablets) because U-Boot isn't there.
I know, it would be slow as molasses, but who cares? Isn't that a good first step?

07-23-2019, 03:45 PM	#31
WaseemAlkurdi Zealot Posts: 147 Karma: 20 Join Date: Jul 2019 Device: Kindle Touch (K5) Wi-Fi x 2, Kindle (7th Gen, KT2), Paperwhite 3rd Gen	P.S. 1. If not for @geekmaster's U-Boot profiles (under the Select Boot thread) and imx_usb, then both my Kindle and I would have become toast by now. 2. /var/local/logs/* on the third eMMC partition did not change at all between boots. 3. () While I was getting my feet deep in the cesspool of "why the hell USB Downloader Mode doesn't blank the e-Ink display and how you should check your host's dmesg instead", a rather amazing thought (is it?) struck my head: Why not use KVM and qemu to boot Android on the Kindle? Note that we have U-Boot access, so we can modify ARM ELs however we please. This isn't possible on more "mainstream" consumer devices (like phones and ARM tablets) because U-Boot isn't there. I know, it would be slow as molasses, but who cares? Isn't that a good first step?