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

When you switch phones, test a new ROM, or simply want a safety net for a specific app, backing up that app + its data can save hours of re‑configuration. Android’s built‑in backup services are limited, but the Android Debug Bridge (ADB) lets you create a full package of a single app without rooting the device.

Before you start

• Computer with ADB installed – Windows, macOS, or Linux. If you don’t have it, download the Platform‑Tools package and extract it.
• USB cable – Use the cable that came with your phone for reliable data transfer.
• Battery level – Keep the phone above 50 % or plug it in; a sudden power loss can corrupt the backup.
• Enough storage – The backup file size roughly equals the app’s data size. Ensure you have at least twice that amount free on your PC.
• Enable Developer Options & USB debugging on the phone:
  Settings > About phone > tap Build number seven times → Settings > System > Advanced > Developer options > toggle USB debugging on.

Step 1 – Verify ADB connectivity

1. Connect the phone to the computer via USB.
2. Open a terminal (Command Prompt, PowerShell, or macOS/Linux shell) and run:

   adb devices

   You should see a line like 0123456789ABCDEF device. If you see unauthorized, check the phone for a prompt asking to allow USB debugging and tap Allow.
3. If no device appears, try a different USB port or cable, and ensure the correct driver is installed (Windows may need the Google USB driver).

Step 2 – Identify the package name of the app you want to back up

The package name is the unique identifier (e.g., com.whatsapp).

1. Run the following command to list all installed packages:

   adb shell pm list packages | grep -i keyword

   Replace keyword with part of the app’s name to filter the list.
2. Alternatively, you can find the package name in the Play Store URL or by looking at the app’s info page in Settings > Apps > App name > Advanced > Package name (some OEM skins expose it).

Step 3 – Create the backup file

ADB’s backup command can capture both the APK and its private data. The syntax is:

adb backup -f <backup-file.ab> -apk -shared -all -nosystem <package-name>

For a single app, you can simplify it to:

adb backup -f myapp.ab -apk -noobb -nosystem com.example.myapp

Explanation of flags:

• -f – Destination file on the computer.
• -apk – Include the app’s APK (useful if you plan to reinstall on a device without Play Store access).
• -noobb – Skip large expansion files (OBBs). Add -obb if you need them.
• -nosystem – Exclude system apps; keeps the backup focused on user‑installed apps.

When you run the command, the phone will display a “Full backup requested” screen. You can set an optional password to encrypt the backup. Leave the password blank if you prefer a plain backup, but be aware that the file will be readable by anyone with access to your computer.

1. Execute the command, e.g.:

   adb backup -f whatsapp.ab -apk -noobb -nosystem com.whatsapp

2. On the phone, tap Back up my data. The process may take a few seconds to several minutes depending on data size.
3. When the backup completes, you’ll see a confirmation toast. Verify the file exists in the folder where you ran the command.

Step 4 – Verify the backup (optional but recommended)

ADB stores the backup in a proprietary format, but you can quickly check its integrity by listing its contents with the adb restore command in “dry‑run” mode:

adb restore -list myapp.ab

If the command prints the package name and size, the file is likely intact.

Step 5 – Transfer the backup to a safe location

• Copy the .ab file to an external drive or cloud storage (Google Drive, Dropbox, etc.).
• If you encrypted the backup with a password, store the password separately (e.g., in a password manager).

Step 6 – Restoring the app on the same or a new device

Restoration works only on devices that support the same Android version and architecture (ARM vs. x86). Most modern phones are compatible.

1. Connect the target phone and ensure adb devices lists it.
2. Run the restore command:

   adb restore myapp.ab

   The phone will prompt you to confirm the restore. If you set a password during backup, you’ll be asked to enter it now.
3. After confirming, the device will unpack the APK and data. When the process finishes, you’ll see a toast saying “Restore complete”.
4. Open the restored app. It should appear exactly as it did on the source device (logged‑in state, settings, local files, etc.).

Step 7 – Verify the restored app works

• Launch the app and confirm that your preferences, accounts, and offline content are present.
• If the app fails to start, check the log with ADB:

  adb logcat -d | grep -i com.example.myapp

  Look for errors such as PackageManager: INSTALL_FAILED_... which indicate compatibility problems.

Alternative method: Using adb pull for data‑only backup

Some users only need the app’s data folder (e.g., game saves). You can pull the data directory directly:

adb shell "run-as com.example.myapp tar -czf /data/local/tmp/myapp_data.tar.gz ."
adb pull /data/local/tmp/myapp_data.tar.gz .
adb shell rm /data/local/tmp/myapp_data.tar.gz

This method requires the app to be debuggable (most release apps are not). If run-as fails, you’ll need root or the full adb backup approach described above.

Troubleshooting

• Backup stalls or shows “0 bytes” – Ensure the phone stays awake. Enable Stay awake while charging in Developer options.
• Restore fails with INSTALL_FAILED_INVALID_APK – The target device may reject the APK because of signature mismatch (e.g., the app was updated on the source device). In that case, download the latest APK from a trusted source and install it before restoring data.
• Backup file is larger than expected – Some apps store cache in the data folder. You can exclude cache by adding -noapk and then manually reinstalling the app from Play Store before restoring data.
• Permission denied when using run-as – The app is not debuggable. Use the full adb backup method instead.
• Device not listed after plugging in – On Windows, reinstall the Google USB driver. On macOS/Linux, try sudo adb kill-server && sudo adb start-server.

Safety warnings

• Never share an unencrypted .ab file publicly; it may contain personal data and authentication tokens.
• If you set a password, remember it. There is no official way to recover a lost backup password.
• Restoring data from a different Android version can cause crashes if the app relies on version‑specific APIs.

When to use this method vs. cloud backup

Cloud services (Google Drive, OneDrive) are convenient but often store only app settings, not full private data. ADB backup is ideal when you need:

• Offline, portable copies of apps you plan to move between devices without internet.
• Complete preservation of game progress, offline maps, or proprietary data that cloud services don’t sync.
• A quick safety net before flashing a custom ROM.

For everyday sync, continue using the app’s built‑in cloud backup. Use the ADB method for edge‑case scenarios where you need full control.

With these steps you can confidently back up any single Android app and its data, move it to a new device, or safeguard it before a risky system change – all without rooting your phone.