4 Installation
Izzy edited this page 2 years ago


  • ADB installed (and configured for your device) on your computer. This can either be the complete Android SDK, or a minimal installation of ADB.
  • Bash (version 4 or higher). As this is a very common shell environment, it's available by default on most Linux distributions.
    • on Linux, this should ship per default
    • on Windows, you can use Cygwin (confirmed); MobaXterm should do as well (no reports yet; includes Cygwin and is easier to install, even offers a portable version)
    • MacOS ships with an ancient version of Bash (3.5). You can use Macports to install a newer version. This doesn't overwrite the current version, just installs the newer version in a different location. Once it's installed, Adebar will use it by default, thanks to d5ve's contribution.
  • Android 4.0+: As the adb backup and adb restore commands have not been present before Android 4.0, Adebar will not be of much use with devices running older versions – except for creating a „device documentation“, which turned out to work even with Android 2.1.

Adebar will work with Android versions before 4.0 – for device documentation and list of installed apps, and maybe even some more. Though it creates the backup and restore scripts as well, those will be of no use – as adb backup and adb restore have only be added with Android 4.0.

Obtaining Adebar

There are multiple ways to get hold of a copy of the code:

  • you can clone the Git repository (see the main page)
  • you can download the repository code as .zip file (from the same place)
  • you can download the latest release from the IzzyOnDroid Download Area

The master branch here at Codeberg should always reflect the latest „stable“ code. The devel branch might hold newer stuff which was not yet much tested. The choice is entirely yours :)


Just unpack the contents of the downloaded .zip/.tar.gz file into an empty directory of your chosing, no special installation required. If you cloned the repo, you can run adebar-cli directly from within your clone, and also create your config/ and cache/ directories there (these are contained in the .gitignore file, and thus should cause no conflicts).

Note: when cloning the repo on Windows (native) for use in Cygwin, take care to set autocrlf = false before cloning, or the resulting files are unusable (see here for details).