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

WaseemAlkurdi · 07-21-2019, 07:12 PM

So I have downloaded the Paperwhite 1 5.6.1.1 firmware package and extracted it, then mounted the resultant rootfs.img.
However, I'd like to ask a few things first:

- Can I get to monitor the boot process, possibly using dmesg, over USB alone? (I can't do serial)

- Can I 'netboot' the Kindle without serial too?

- I've seen that the Kindle retrieves each and every splash screen from /opt/amazon/low_level_screens/600x800/* on the Touch, while the Paperwhite uses /opt/amazon/low_level_screens/* (no resolution). In theory, that would mean that the Touch would fail to even start booting because the boot pictures are mislocated. I'm copying those over from the Touch to the Touch path in the Paperwhite image.
The question is: are there more resolution- or device-specific files in the rootfs image that I should pay attention to?

- I've found and flashed (using dd on the Kindle's main system) a modified diags (mmcblk0p2) partition for SSH access (first thought of modifying it by hand, but then got too lazy). However, mount -o rw,remount /dev/mmcblk0p4 / && touch /ENABLE_DIAGS && reboot doesn't seem to work. I don't have a Windows machine (Linux only), so I can't use MfgTool to "select boot". What do I do?

07-21-2019, 07:12 PM	#22
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	So I have downloaded the Paperwhite 1 5.6.1.1 firmware package and extracted it, then mounted the resultant rootfs.img. However, I'd like to ask a few things first: - Can I get to monitor the boot process, possibly using dmesg, over USB alone? (I can't do serial) - Can I 'netboot' the Kindle without serial too? - I've seen that the Kindle retrieves each and every splash screen from /opt/amazon/low_level_screens/600x800/* on the Touch, while the Paperwhite uses /opt/amazon/low_level_screens/* (no resolution). In theory, that would mean that the Touch would fail to even start booting because the boot pictures are mislocated. I'm copying those over from the Touch to the Touch path in the Paperwhite image. The question is: are there more resolution- or device-specific files in the rootfs image that I should pay attention to? - I've found and flashed (using dd on the Kindle's main system) a modified diags (mmcblk0p2) partition for SSH access (first thought of modifying it by hand, but then got too lazy). However, mount -o rw,remount /dev/mmcblk0p4 / && touch /ENABLE_DIAGS && reboot doesn't seem to work. I don't have a Windows machine (Linux only), so I can't use MfgTool to "select boot". What do I do? Last edited by WaseemAlkurdi; 07-21-2019 at 07:14 PM.