View Single Post
Old 04-28-2015, 08:09 AM   #62
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by odamizu View Post
Kindle Voyage Software Update 5.6.2.1 just showed up at:

http://www.amazon.com/gp/help/custom...deId=201630670

I'm guessing, hoping the FONT-RAMP hack still works, but can some kind soul confirm this or teach me how to crack open the update (with a Mac) so I can check for myself?

Merci, danke, thank you.

P.S. I found KindleTool, but I am in way over my head. I used the "extract" command, which gave me a folder containing rootfs.img.gz, rootfs.img.gz.sig, update-payload.dat, update-payload.dat.sig and a folder named imx60_wario containing uImage and uImage.sig. Now I am totally lost
Nope, your totally on the correct path.
un-gzip the rootfs.img.gz giving a rootfs.img
- - - -
The following is how you do it on a Linux install, for a Mac OSx, you may need to run Linux in a VM (or however Apple people do things).
- - - -
The rootfs.img is just that, a binary image of the filesystem backing store. Treat it as such.
Use a 'loop mount' to turn the file into a device and mount it into your directory tree. Just don't write to it.

You will probably find other files in that (just mounted) Amazon part of your directory tree that are also filesystem backing store images that have to be loop mounted.
A file type identification utility (such as: file) will be a big help in finding them.

Then all you need to do (famous understatement, (tm) ) is start searching the contents of the *.jar files with an appropriate reverse engineering tool(s) for 'FONT_RAMP' and the code that uses it.

Last edited by knc1; 04-28-2015 at 08:19 AM.
knc1 is offline   Reply With Quote