Originally Posted by PoP
Ok I did this:
and now have a update_k3w-restore-rootfs-v3.1.bin
for the future.
But it is the first time that I prepare an update package and I have (too many) questions.
The bin file has the expected FB02 header -- thanks to the fb parameter of the python update tool -- with 00 padding up to hex 20000, so it appears to be using the expected block size of decimal 131072
Does that look correct to you for an manual update? The package only consists of an image with its jailkey signed file. I am afraid to test it and not quite ready to risk bricking my Kindle.
When I go to the Recovery menu pressing ENTER at Boot time (per version 3.1 of my Kindle 3 WiFi) I get the recovery screen:
but even after installing the recovery kernel, pressing E
did not seem to do anything. And when plugging the USB to the computer, Windows did not see a file system (and foolishly asked me if I wanted to format the device) so I am wondering if pressing U
will give me the chance in the future to copy the restore-rootfs.bin file before rebooting by pressing R to exit from recovery.
I also read ALT+E
was rather required, I tried it with the same results. How long should one wait for the export to complete? And where will the file be created if I can't connect the USB to the computer.
Finaly, I am not reassured by the description of option U
which suggests that both the file system *and* the kernel will be updated... since my package only contains the file system.
You are correct in using the --fb option to create a large block size. You may have been using my modified kindle_update_tool.py, but for others, the default kindle_update_tool.py creates a "FB01" package with the --fb option. If so, just change either the header of the bin or the python file source to FB02. But other than that, your image looks fine.
You need an ext2 compatible OS to see the filesystem exported by Alt+E. Pressing "U" will only update the kernel if it finds it in the .bin package.