Please also visit the About and Issues & Limitations pages.
You can choose to create a flashable undo file that can be used later to revert the theme changes. The creation of the undo file is relatively quick and does not add significant time to the build process. Using an undo file is generally faster and easier than Nand backups. However, in order for the undo file to work it must be created at the time the theme update is created. It can't be created after the theme has been applied in recovery. Also, undo files must be applied in exact reverse order of creation in order to reliably back out changes from several independently flashed theming operations.
The choice to make an undo file is controlled by a preference setting with a default value of "Ask". In this mode, a dialog is displayed asking for your decision to create the undo file at the beginning of each build. You may also choose to "Always" or "Never" create undo files.
Undo files are written to the same directory as the update zip file. They will have a similar name except with a "-undo.zip" suffix.
There are two formats for the script file inside an Android update.zip file. The old format is called "Amend", and the new format is called "Edify". As of this writing most recovery programs support both formats, but Amend has been deprecated in favor of Edify. ClockworkMod 3.0 no longer supports the Amend format and users with this recovery must configure ZipThemer to use Edify scripting.
Begin by selecting the Menu -> Update Edify option. Pick one of the two options. Option 1 is likely to work for most users and simply requires that you have a flashable ROM or update on your sdcard that contains an Edify script. The device type name field on this screen is used for display purposes only. Enter whatever you want for this value. Browse and select the ROM or update file. Click "Configure..." and you're done. This is normally a one-time operation that you don't have to repeat, assuming it succeeds without errors (see the FAQ for exceptions).
You can control which format ZipThemer generates by changing the "Update Script Format" setting. Amend is the default and should work for many users . If you require Edify (ClockworkMod 3.0 users) or just want to try it, first check to see if your phone is listed in the Update Script Format setting list. If its not listed, update the database via the app's "Update Edify" menu item. If your phone still doesn't appear, try one of the "Generic" phone options or generate a configuration using "Option 1" on the Update Edify screen. Finally, if you still can't get themes to install then ask for support by visiting the support forum or sending me (the dev) an email.
Edify Phone Database
File-system partitions must be explicitly mounted when using Edify and the mount commands can vary from phone to phone. ZipThemer can extract the required information from a flashable ROM or update file, and there is a database of mount commands provided by nubecoder as an artifact of his amend2edify tool project. ZipThemer can use this database when generating Edify scripts and ships with a built-in version, but if you use Option 2 in the "Update Edify" menu screen the latest version of the file will be downloaded to /sdcard/ZipThemer/edify/phoneDatabase.xml. This file takes precedence over the built-in one.
ZipThemer also contains a built-in version of the update-binary file which is used when running edify scripts after configuring with Option 2. The file gets copied into the update.zip automatically during generation when Edify scripting is enabled. The default version was also obtained from the amend2edify project. At the time of this writing the built-in update-binary file is known to work on most phones, but you can provide your own version by copying one into the /sdcard/ZipThemer/edify directory (it must be named "update-binary"). However, not all update-binaries are created equal so you're on your own when doing this.
Changing the output file via the "+Output" button implicitly changes the default output directory to the containing folder of the selected file. The default output directory value is persisted across application restarts and can be changed again by selecting a file in another directory via "+Output". If the directory is ever found to not exist, then the default directory will revert back to /sdcard.
This feature of persisting and re-using the default output directory is meant to aid users whose method of installing updates requires the output zip files to be located somewhere other than in /sdcard.