View Single Post
Old 06-28-2011, 05:13 PM   #5
PoP
Antonín ♯♭♪♮♫ ᵖʸᶠᵍᶜʳˡ
PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.PoP ought to be getting tired of karma fortunes by now.
 
PoP's Avatar
 
Posts: 511
Karma: 6391817
Join Date: Dec 2010
Location: ♁ ᴺ₄₅°₃₀' ᵂ₇₃°₃₇' ±₆₀"
Device: K3.₄, PRS-350, SGS3, Rπ, iPad Air
Quote:
Originally Posted by yifanlu View Post
... (to make a custom recovery package, copy the Kindle rootfs using "dd if=/dev/mmcblk0p1 of=/mnt/us/rootfs.img", then you can mount the image and modify it on your computer (if you want). After your done, gzip rootfs.img, sign it using the jailbreak key and package rootfs.img.gz and rootfs.img.gz.sig into an update. Change the first 4 bytes of the header from "FC02" to "FB02" and you're done...
Ok I did this:
Spoiler:

dd if=/dev/mmcblk0p1 > rootfs.img

gzip -9 rootfs.img

openssl dgst -sha256 -sign sign.key -out rootfs.img.gz.sig rootfs.img.gz

python kindle_update_tool.py m --k3w --fb k3w-restore-rootfs-v3.1 rootfs.img.gz rootfs.img.gz.sig
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:
Click image for larger version

Name:	Kindle 3 Recovery Menu via ENTER key DSC02429.JPG
Views:	808
Size:	196.1 KB
ID:	73505
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.
Click image for larger version

Name:	Kindle 3 Recovery Menu via ENTER key DSC02430.JPG
Views:	672
Size:	177.5 KB
ID:	73506

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.
PoP is offline   Reply With Quote