Home Page » News » How To » How to Backup and Restore Individual Android Apps Using ADB (No Root)

Backup and Restore Individual Android Apps Using ADB (No Root)

12 min read Learn step‑by‑step how to back up a single Android app and its data with ADB, then restore it without rooting your device. September 26, 2026 16:41

Before you start

These steps assume you have a Windows, macOS, or Linux computer nearby and a USB cable that can transfer data (not just charge).

Charge your phone to at least 50 % – a failed backup during a power drop can corrupt the file.
Enable USB debugging on the device (Settings > About phone > Tap Build number seven times, then Settings > System > Developer options > USB debugging).
Install the Android SDK Platform‑Tools (contains adb) on your computer.
Have a folder ready to store the .ab backup file; you’ll need enough free space for the app’s data.

Step 1 – Install ADB (Android Debug Bridge)

Windows:
1. Download the latest Platform‑Tools zip from the official Android developers site.
2. Extract the zip to a permanent location, e.g., C:\adb.
3. Add that folder to your PATH (Control Panel > System > Advanced > Environment Variables).
macOS:
1. Open Terminal and run brew install --cask android-platform-tools if you have Homebrew.
2. Alternatively, download the zip as for Windows, extract, and add the folder to your PATH (edit .zshrc or .bash_profile).
Linux:
1. On Debian/Ubuntu, run sudo apt-get install android-tools-adb.
2. On Fedora, run sudo dnf install android-tools.

Verify the installation by opening a command prompt (or terminal) and typing adb version. You should see a version number like Android Debug Bridge version 1.0.41.

Step 2 – Connect the device and verify communication

Connect your phone to the computer with a USB cable.
On the phone, you’ll be prompted to allow USB debugging from this computer. Tap Allow and optionally tick “Always allow”.
In the command window, run adb devices. You should see a line with a device serial number and the word device.
```
List of devices attached
1234567890ABCDEF    device
```

If the device shows as unauthorized or does not appear, try reconnecting the cable, changing the USB mode to “File Transfer”, or restarting the ADB server with adb kill-server && adb start-server.

Step 3 – Find the exact package name of the app you want to back up

Open the app’s Google Play Store page on your phone.
The URL contains the package name after id=, e.g., com.whatsapp.
Alternatively, run adb shell pm list packages | grep -i "keyword" to search for a partial name.

Write down the full package name; you will need it for both backup and restore commands.

Step 4 – Back up the app and its private data

Choose a folder on your computer, for example C:\adb\backups (Windows) or ~/adb/backups (macOS/Linux).
Run the backup command, replacing com.example.app with your app’s package name:
```
adb backup -apk -shared -all -f "C:\adb\backups\myapp.ab" com.example.app
```
- -apk includes the APK file itself (useful if you later reinstall on a device that does not have the app in the Play Store).
- -shared backs up files stored on the shared storage (photos, downloads) that belong to the app.
- -all ensures all data categories (including Wi‑Fi credentials, if the app stores them) are captured.
- -f specifies the output file.
After issuing the command, the phone will display a backup dialog. Do not set a password unless you need encryption. Leaving it blank makes restoration easier, but the file will be stored in plain text on your computer.
Tap Back up my data. The process may take from a few seconds to several minutes depending on the app’s data size.

On Android 12 and later, some apps opt‑out of the ADB backup mechanism. If you see a message like “Backup failed for com.example.app”, the app does not support ADB backup.

Step 5 – Verify that the backup file was created

Navigate to the folder you chose in Step 4.
You should see a file with the .ab extension. Its size gives a quick indication of success – a few kilobytes usually means only the APK was saved, while megabytes indicate data was included.
Optionally, you can inspect the archive (it’s a custom Android format). A quick sanity check: adb restore "C:\adb\backups\myapp.ab" will prompt for restoration – you can cancel at the dialog if you only wanted to verify.

Step 6 – Restore the app on the same or a different Android device

Make sure the target device has USB debugging enabled (repeat Step 2 if necessary).
If the app is not already installed, you can let the restore process reinstall the APK (requires the -apk flag used during backup). Otherwise, install the app from the Play Store first to satisfy package‑name matching.
Run the restore command, pointing to the backup file:
```
adb restore "C:\adb\backups\myapp.ab"
```
The phone will show a restore dialog. Confirm by tapping Restore my data. The device will reboot the app’s data and may take a few minutes.

Restoring to a device with a newer Android version may trigger a data‑migration step inside the app. Open the app after restoration to verify that settings, logins, and saved files appear as expected.

What to expect after restoration

The app should launch exactly where you left it – same account logged in, same preferences, and any locally stored files (e.g., notes, offline maps).
If the app uses cloud sync, it may re‑download data after you open it; this is normal and does not indicate a failed local backup.
Some apps encrypt their private data with a key tied to the original device. In those cases, the restored data will be unreadable and the app will behave as if it were a fresh install.

Limitations and important caveats

Backup opt‑out: Developers can set android:allowBackup="false" in the manifest, which disables ADB backup for that app.
Encrypted app data: Apps that encrypt their own databases with a device‑specific key cannot be restored to a different device.
Large games: Games often store data on external storage (> 1 GB). The -shared flag captures those files, but the transfer can be slow and may exceed your computer’s free space.
Android 12+ restrictions: The system prompts you to confirm each backup; you cannot silently back up multiple apps in a batch without user interaction.

Troubleshooting common issues

Backup command returns “Error: device not found”

Ensure the USB cable is data‑capable (some charging‑only cables lack the required wires).
Check that the phone is set to “File Transfer (MTP)” mode, not just “Charging”.
Restart the ADB server: adb kill-server && adb start-server.

Backup fails with “Backup failed for package …”

Confirm the app does not have allowBackup="false". You can inspect the manifest via adb shell pm dump com.example.app | grep allowBackup.
If the app is a system app, you may need root privileges – which defeats the “no‑root” premise.

Restore shows “Restore failed” or the app crashes on launch

Make sure the exact same package name is present on the target device (same app version helps).
If the app uses device‑specific encryption, you’ll need to log in again and let it sync from the cloud.
Delete the partially restored app (adb uninstall com.example.app) and try the restore again.

Safety warnings

Never share your .ab backup file with anyone unless you have removed sensitive data. The file can contain login tokens, messages, and personal files.
If you set a password on the backup, remember it – ADB cannot recover a lost password.
Restoring a backup over an existing app will overwrite its current data. If you are unsure, make a fresh backup of the target device first.

Wrapping up

Using ADB to back up and restore a single Android app gives you granular control over your data without needing root access. The workflow described here works across Windows, macOS, and Linux, and it respects the device’s security model. Keep your backup files in a safe location, and remember the limitations imposed by developers who disable the backup feature. With these steps you can confidently move an app’s data between phones, safeguard a favorite game before a factory reset, or simply keep a local copy of a productivity app’s configuration.

User Comments (0)

Add Comment

No comments added yet.

Add Comment

Your Name: *

Comment Title: *

Your E-mail: * We'll never share your email with anyone else.

Your Comment: *

Comments will not be approved to be posted if they are SPAM, abusive, off-topic, use profanity, contain a personal attack, or promote hate of any kind.