As attached, for the touch screen Kindles only.
It is a script, with a pair of tables to control what gets backed up.
The tables could be changed for the earlier than KT devices if somebody was interested in doing it.
You will need command line access to the Kindle to run this script.
Translation: one of kTerm, telnet, ssh, serial port
Installation?
Un-compress it and put it wherever you want it on the Kindle (it will run from the user storage partition).
Running it:
It writes to user storage (/mnt/us/backups) so it will not work if you have user storage exported over the USB cable.
Just call it by name, it will create the (Kindle:)/backups directory if required.
In the couple of cases where the exact size to copy is not known in advance, it copies an over-sized chunk.
That only happens when copying the two kernels and those can be trimmed down to size after they are copied.
(The 'file' command or the 'mkimage -l' command will tell you how long the actual contents is.)
For the curious, the script:
An example execution:
It is a script, with a pair of tables to control what gets backed up.
The tables could be changed for the earlier than KT devices if somebody was interested in doing it.
You will need command line access to the Kindle to run this script.
Translation: one of kTerm, telnet, ssh, serial port
Installation?
Un-compress it and put it wherever you want it on the Kindle (it will run from the user storage partition).
Running it:
It writes to user storage (/mnt/us/backups) so it will not work if you have user storage exported over the USB cable.
Just call it by name, it will create the (Kindle:)/backups directory if required.
In the couple of cases where the exact size to copy is not known in advance, it copies an over-sized chunk.
That only happens when copying the two kernels and those can be trimmed down to size after they are copied.
(The 'file' command or the 'mkimage -l' command will tell you how long the actual contents is.)
For the curious, the script:
Spoiler:
An example execution:
Spoiler: