Quote:
Originally Posted by WaseemAlkurdi
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?
|
P.S. Never mind the last point (scratched out) in the question I asked above. I've been able to boot to diags using
imx_usb. Do you know what it feels like when something hides in plain sight? Yep, that's the feeling.
Another point I noticed is that "diags" boot has a slightly different splash screen (older "Amazon Kindle" vs. newer "Kindle" logo). And it happens that the "diags" system is based on the Kindle 5.0.1 firmware. That seems to confirm that yep, the splash is loaded from
/opt/ ... and that the loss of the splash screen (or something possibly more important) due to the path change might be problematic.