|Izzy f42d564092||5 days ago|
|.github/ISSUE_TEMPLATE||1 year ago|
|doc||1 week ago|
|lib||1 week ago|
|tools||3 months ago|
|.gitignore||5 months ago|
|LICENSE||5 years ago|
|README.md||5 days ago|
|adebar-cli||1 week ago|
Note: As this is a collection of Shell scripts, you won’t find any „binaries“ attached to releases – there are none for Adebar and no „compilation“ is required. Please take a look at the wiki for further details and instructions.
There are plenty of backup solutions available for Android, including such intended as front-end for ADB. So what is specific for Adebar that I wrote it, knowing of those other solutions?
The task I wrote Adebar for is to be able to quickly backup a device, and restore the backup again – e.g. when I need to factory-reset a device. That includes the case where I have to send a device to be serviced, and need to use a different device meanwhile: that would rule out a “complete restore” due to the side-effects system-apps might cause, especially when the second device is from a completely different manufacturer, and/or runs a different version of Android or even a completely different ROM. That’s one of the reasons why Adebar creates one backup file per app (instead of one huge
backup.ab holding them all) – while the other is to be able to select what to restore in general.
As a side-effect, Adebar generates a „report“ (or „short documentation“) on the device – including general device information (like model, Android version, device features, device status, configured accounts) as well as some details on installed apps (install source/date, last update, version, etc.).
Adebar itself does not create any backups. But it generates multiple files, including
.apkfiles and their data
wpa_supplicant.conffrom your device, which holds information on all WiFi APs you’ve configured (root required) – and also some more configuration files.
packages.xmlfrom your device, which holds all information about apps installed on your device (with Android 4.1 and above, this again requires root)
userApps.mdin the Wiki).
deviceInfo.mdin the wiki).
Optionally, if you have the PHP CLI available on your computer, you can parse the
packages.xml with provided PHP scripts, located in the
tools/ directory. This directory also includes a shell script to convert ADB backup files into
.tar.gz archives (
openssl) – and another one if you have issues restoring ADB backups on Android 7 or higher (
abrestore; if your device is affected by the ADB restore bug, only restoring backups of apps already installed on the device).
As Adebar is not yet tested on too many devices, there might be some errors/bugs here and there; if you encounter one, please file an issue at the project’s Codeberg presence. General feedback is also more than welcome if you’re successfully using Adebar with your device, see List of tested devices.
Most of them should already be obvious from above description. Nevertheless, all of them here in short:
adb restorecommands have not been present before Android 4.0, Adebar will not be of much use with devices running older versions – except for, maybe, creating a „device documentation“ as outlined above.
A documentation describing steps for installation, configuration, usage, and more can be found in the project wiki.
You like Adebar and want to contribute?