Back Up Individual Android App Data Using ADB (No Root)

3. Verify the ADB connection

4. Identify the package name of the app you want to back up

5. Create the backup file

The basic ADB backup syntax is:

adb backup -f <backup-file.ab> -noapk -nosystem -noshared <package-name>

Explanation of the flags:

• -f – output file path.
• -noapk – do not include the APK itself (saves space; you can reinstall from Play Store).
• -nosystem – ignore system apps.
• -noshared – exclude shared storage (photos, downloads). For most app‑data backups you only need the private data folder.
• Omitting -apk is safe because the app’s binary is public on the Play Store.

6. Understand the backup format and optional conversion

The .ab file is a proprietary Android backup container. It can be restored directly with ADB, but you might want to inspect or extract its contents.

• To restore later, use the same adb restore command (see section 8).
• To extract the data, you need the Android Backup Extractor (abe) tool or the Java‑based android-backup-extractor.jar.

  java -jar abe.jar unpack myapp_backup.ab myapp.tar

  The resulting .tar can be opened with any archive manager to view the raw /data/data/com.example.myapp folder.

Because the backup is optionally password‑protected, you will need to supply the same password to abe when unpacking.

7. Common limitations you need to know

• AllowBackup flag – If the app’s AndroidManifest.xml sets android:allowBackup="false", ADB will refuse to back up its data. In that case you cannot use this method unless you have root access.
• Encrypted app data – Some apps (e.g., banking apps) store data in an encrypted format that is meaningless without the app’s internal key. The backup will still contain the encrypted blobs, but you cannot read them directly.
• Media files – The -noshared flag skips files stored on external storage. If the app keeps images, videos, or PDFs in /sdcard/Android/data/…, add the -shared flag to include them, but be aware the backup size will increase.
• Android 9+ restrictions – Starting with Android 9, the backup dialog shows a warning that “Full backup mode may expose your private data”. The process still works, but some OEMs (e.g., Xiaomi) may hide the button unless you enable “Full backup” in Developer options.

8. Restoring the backup to the same or a new device

9. Backing up multiple apps in one go (optional)

If you need to preserve several apps, you can list them separated by spaces:

adb backup -f multi_backup.ab -noapk -nosystem -noshared com.example.app1 com.example.app2 com.example.app3

Or use -all to back up every user‑installed app (excluding system apps). Be mindful of storage space and the fact that some apps will refuse backup because of allowBackup="false".

10. Troubleshooting

11. Safety tips and best practices

• Test on a non‑critical app first. Use a simple note‑taking app to confirm the workflow before handling banking or messaging apps.
• Store backups in a secure location. If you used a password, keep it in a password manager. An unencrypted .ab file can be opened with abe and may expose personal data.
• Keep a copy of the APK. Although -noapk saves space, some apps may disappear from the Play Store later. Save the APK with adb pull /data/app/<package>-1/base.apk (requires root) or download it from a reputable archive.
• Document the package name and app version. Write down the version number you backed up; restoring to a newer version sometimes leads to incompatibilities.

12. When ADB backup isn’t enough

If the app you need to protect explicitly disables backup, you have two realistic options without rooting:

1. Use the app’s own export feature. Many games, note‑apps, and finance tools provide an “Export data” or “Sync to cloud” option.
2. Leverage the Android “Work profile” trick. Create a separate work profile, install the app there, and use the work‑profile backup (available on Android 11+). This isolates the data and lets you use the standard Google backup for that profile.

Both methods keep you within the OS security model and avoid the need for root.

13. Recap of the workflow

1. Install platform‑tools and add adb to your PATH.
2. Enable Developer options and turn on USB debugging.
3. Connect the phone, verify with adb devices.
4. Find the target app’s package name.
5. Run adb backup -f myapp.ab -noapk -nosystem -noshared <package> and confirm on the phone.
6. Store the .ab file safely (optionally convert to .tar for inspection).
7. When needed, restore with adb restore myapp.ab on a device that has the app installed.

Following these steps gives you a reliable, no‑root method to preserve the exact state of any Android app’s private data.