KindleTool: Create/Unpack Kindle update files

[NiLuJe]

This has been living in a corner of the Wiki/a couple of posts lost in the middle of a sea of threads for a while, so I thought it was time to finally give it a proper home .

PSA: All downloads have been moved to the Snapshots thread!

For those unfamiliar with it, it's the CLI tool we use to package our hacks in a somewhat user-friendly Kindle update file (.bin), and unpack and poke into official updates .
It's the successor of the trusty kindle_update_tool.py Python packager we used in the K1/2/3 days, and a fork of yifanlu's original KindleTool project (historically forked to fix the Linux support, and ultimately permit a native win32 port). So, as always, thanks to all those people .

It's living right here on GitHub.

I won't be rehashing the readme, but I'm available to answer any queries you might have .

If you don't want to/can't build it yourself, you'll always find a set of binaries here for every system supported:

* Linux x86 (32bit):
-linux-i686: Recommended binary.

* Linux x86_64 (64bit):
-linux-x86_64: Recommended binary.

* Windows:
-mingw: Recommended binary (native Win32, 32bit).
-cygwin: Unavailable since v1.6.5. Should you *really* need to use KindleTool in that environment, build it yourself.

* OS X:
-osx: Built on 10.13, might run on something older (provided it's at least 10.6). Standalone. (Mac Intel only, 64bit).

[NiLuJe]

For 'live' examples of how one might use this to package something, here's the source to a minimal package that won't install anything, just run a script during the install process.
It's *very* Touch specific, don't use it on older devices.

For older devices, take a look at any of my hacks, the simplest being the 'dummy' one again .

On a completely unrelated note:
Please don't feed non-POSIXy paths to the native win32 port, it won't like it . That means no Windows drive letters, no weird // links, no weird extra \. and to be perfectly safe, only use /, not \ (although it *should* handle the backslash => slash conversion correctly).
It will also horribly die if you pass a directory with a trailing path separator to the commandline...

EDIT: MKK is another example of a full package, this one supporting *every* devices... (And it's actually fully functional, it's a revamp of PoP's & ixtab's merged developer keystore & Kindlet Jailbreak files & installers).
I aimed for a cleaner/simpler/shorter buildscript, while still supporting every devices.

[qlob]

Thanks!

[silver18]

Everything works!!
Thanks a lot!!!

[NiLuJe]

Shameless bump for the 1.5.0 release/binaries .

(Yes, I switched to a more common versionning scheme, rather than my SVN-like workaround... It's a bit less abstract this way, now that I tag regular releases).

(As for the ChangeLog, it's bundled as always, but the key points of this release are a bunch of fixed minor memory leaks (in the handling of OpenSSL calls), and a legacy switch to make the archiving of directories similar to Yifan's KindleTool, and not like tar/the python tool like it does by default [cf. the -C switch description in the readme/manpage for more details] . And a smaller mingw binary.).

[twobob]

Shameless bump for tomorrow to check these out.
and say thanks for all your great work and help.

[NiLuJe]

Call for testers:

If you happen to have a 'new' K4, the current git tree *should* support those. I've just repacked my stuff to handle both K4, shout at me if it actually works and/or breaks on 'old' K4.

Depending on if it works, and when new infos about the PaperWhite(s) will drop in my lap, I might do a new release soon.

EDIT: Yup, K4B support's good .

[hippy dave]

i just built this for os x 32bit, because my mac is old and creaky - sharing it just in case it's of any use to anyone else. edit: it's version 1.5.0-GIT

[geekmaster]

Originally Posted by hippy dave

i just built this for os x 32bit, because my mac is old and creaky - sharing it just in case it's of any use to anyone else. edit: it's version 1.5.0-GIT

Your post needs to be added to the Tools index wiki. Thanks.

[hippy dave]

good idea, but maybe i should see if niluje wants to add it to his post, otherwise i should replace the zip attachment with one that has the readme/credits etc, rather than just the binary.

[NiLuJe]

@hippy dave: I'm not that familiar with all the different generations of Macs, but, err, why do you need an i386 binary? I'd understand a ppc32/ppc64 one, but was there ever an intel mac released without x86_64 support?

A bit of poking seems to reveal an i386 binary built against the 10.6 SDK with a freakishly ancient Clang build, so I'm genuinely curious as to why you need such a peculiar combo (well, it seems peculiar to me, but like I said, not really familiar with Apple stuff ).

Regardless, if you want me to add it to the first post (which I'll be glad to do, no questions there ), it'll need to bundle libarchive statically linked, and to be linked against system libs, not stuff from MacPorts/Homebrew/Fink. (I don't have a mac on hand, so no otool, so I can't really say anything about the PMS stuff, but I can tell that libarchive is not statically linked ).

Look at the kindletool-static-build.sh script in tools/ to see how I build the stuff in the first post .

[hippy dave]

the first model of macbook, which was available for 6 months in 2006, is core duo so doesn't support 64bit. very annoying by this point, and i'm too skint to upgrade, oh well

oh good point about the static libraries, hadn't crossed my mind so the binary i posted is actually useless to anyone else.

i followed the build instructions to use macports to get the dependencies, god knows how it decided what versions. macports choked on the actual build so i compiled it using x-code. i also don't know why it came out as i386 rather than i686. maybe i'll quit while i'm behind, at least for tonight

thanks for the tool, anyway!

[NiLuJe]

@hippy dave: Ah, wasn't aware of that one, but that explains it, thanks .

I can't tell you much, besides the fact that it does work on a 10.7/10.8 MBA with Xcode 4+CLI tools with MacPorts . But the static build-script actually doesn't depend on MacPorts, that's the whole point, so it should hopefully only require Xcode & its CLI tools, although I haven't tested this on anything older than 10.7 .

(As for i386 vs i686, that's just how the Mach-O binaries refer to the arch, I have no idea what actual compiler settings it defaults to ).

(That said, if you can run the MacPort build in debug mode [-d] and forward me the build log, I can try to look at it & fix it . I suspect you'll encounter the same failure when building it manually/via the static script anyway, so, let's try to fix it ^^).

[NiLuJe]

Released 1.5.1, with K4B support .

[geekmaster]

Originally Posted by NiLuJe

Released 1.5.1, with K4B support .

What K4B support. Amazon claims that the silver and black models are the same, other than color and price. Did you find a difference?