Back Up & Restore Android Using ADB (No Root)

17 min read A step‑by‑step guide to create a complete backup of apps, data, and settings on any Android phone using ADB, and restore it safely without rooting. October 12, 2026 17:00 How to Back Up and Restore Your Android Phone Using ADB (No Root)

When a phone gets damaged, you change devices, or you simply want a safety net, a full backup is the most reliable way to keep your apps, settings, and personal data intact. While cloud services cover photos and contacts, they rarely capture every app’s private files or the exact system configuration. Using the Android Debug Bridge (ADB) you can create a local, device‑wide backup without ever rooting the phone.

Before You Start

  • PC or Mac with a recent version of the adb platform‑tools installed.
  • A USB cable (or a reliable Wi‑Fi ADB connection) to connect the phone.
  • At least as much free storage on the PC as the total size of the data you intend to back up.
  • Battery level above 50 % (or keep the device plugged in) to avoid interruptions.
  • Patience – the first full backup can take 10–30 minutes depending on the amount of data.
Note: ADB backup works on Android 4.4 – 11 out of the box. Starting with Android 12 Google restricted the adb backup command, but many manufacturers still honour it, and a fallback method using adb shell tar works on all versions.

Step 1 – Enable Developer Options and USB Debugging

  1. Open Settings on your phone.
  2. Scroll to About phone → Software information (or directly About phone on some devices).
  3. Tap Build number seven times. You’ll see a toast confirming “You are now a developer!”.
  4. Return to the main Settings screen; a new entry Developer options appears.
  5. Enter Developer options and toggle USB debugging on. Confirm any security prompt.
If your device runs Android 12+, you may also need to enable “USB debugging (Security settings)” for a full backup.

Step 2 – Install ADB on Your Computer

Download the official Android SDK Platform‑Tools package for your OS:

  • Windows: platform-tools_windows.zip
  • macOS: platform-tools_mac.zip
  • Linux: platform-tools_linux.zip

Extract the archive to a convenient location (e.g., C:\adb or ~/adb). Add the folder to your system PATH or use the full path when invoking commands.

Step 3 – Verify the Connection

  1. Connect the phone to the PC with a USB cable. Choose the File Transfer (or Transfer files) USB mode.
  2. Open a terminal (Command Prompt, PowerShell, or macOS/Linux shell) and run:
    adb devices
  3. You should see a line like xxxxxxxxxxxx device. If it says unauthorized, a dialog appears on the phone – tap Allow and optionally check “Always allow from this computer”.
  4. If no device appears, try a different cable, enable “USB debugging (Security settings)”, or reinstall the USB drivers (Windows).

Step 4 – Choose the Backup Method

There are two reliable ways to back up a device without root:

  1. Standard ADB backup command – creates a single .ab file that can be restored with adb restore. Works on most Android 4.4‑11 devices.
  2. Shell‑tar method – uses adb shell tar to archive the /data and /sdcard partitions into a .tar file. Works on any Android version, but requires a bit more post‑processing.

We’ll cover the standard method first because it’s the simplest for most users.

Step 5 – Create a Full Backup with adb backup

  1. Open a terminal in the folder where you want the backup file to reside.
  2. Run the following command:
    adb backup -apk -shared -all -f full-backup.ab
    • -apk – includes the APK files of installed apps.
    • -shared – backs up the shared storage (photos, downloads, etc.).
    • -all – backs up all user apps and their data.
    • -f – specifies the output file name.
  3. On the phone, a system dialog appears asking for a backup password (optional). Leave it blank for an unencrypted backup, or set a password if you need encryption.
  4. Tap Back up my data. The device will start compressing data; you’ll see a progress bar.
    • Typical time: 5 – 20 minutes depending on data size.
    • Do not disconnect the phone until the terminal returns to the prompt.
  5. When finished, the terminal shows Backup finished: xxxx bytes. Verify that full-backup.ab exists and its size matches expectations (usually a few hundred MB to several GB).

Why the Options Matter

The -apk flag ensures you can reinstall apps without needing the Play Store, which is handy for devices without Google services. -shared captures the user’s media files, while -all tells ADB to include every user‑installed app. If you only need app data, you can drop -apk and -shared to shrink the backup.

Step 6 – Verify the Backup

A backup file can be corrupted without obvious signs. Quick checks:

  1. Check the file size: ls -lh full-backup.ab (Linux/macOS) or dir full-backup.ab (Windows).
  2. Run a test restore on a spare device or an emulator (see Step 9) to ensure the file is readable.
  3. If you used a password, try decrypting the file with android-backup-extractor (see the optional section below).

Step 7 – Optional: Extract the .ab File for Inspection

Sometimes you may want to inspect the contents without a full restore. The open‑source tool android-backup-extractor (abe) converts .ab to a .tar archive.

  1. Download the abe.jar file.
  2. Run:
    java -jar abe.jar unpack full-backup.ab backup.tar
  3. Extract the resulting backup.tar with any archive tool to view individual app data folders.
Warning: Extracted app data may contain sensitive information (tokens, passwords). Handle the files securely and delete them after use.

Step 8 – Restore the Backup on the Same or a New Device

  1. Make sure the target device has Developer options → USB debugging enabled (see Step 1).
  2. Connect the device and verify it appears with adb devices.
  3. Run the restore command:
    adb restore full-backup.ab
  4. If the backup was password‑protected, you’ll be prompted on the phone to enter the same password.
  5. Tap Restore my data. The device will unpack the archive; you’ll see a progress bar similar to the backup process.
  6. When the terminal returns to the prompt, the restore is complete. Reboot the phone to let the system re‑index restored apps and media.

After reboot, you should see all your apps, contacts, messages, and media exactly as they were at the time of the backup.

Common Restore Issues

  • “Restore failed” error – Usually caused by an incorrect password or a corrupted .ab file. Verify the password and re‑run the command.
  • Missing apps after restore – If you omitted -apk during backup, only app data is restored. Re‑install the missing apps from the Play Store, then launch them once to allow data restoration.
  • Permission denied on restored files – Some apps store data in protected directories that ADB cannot write to on Android 10+. In that case, consider using the adb shell tar method (next section) or reinstall the app and use its own import feature.

Step 9 – Alternative Method: Full Backup with adb shell tar

If your device runs Android 12+ where adb backup is disabled, you can still archive the data partitions directly.

  1. Open a terminal and start a shell on the device:
    adb shell
  2. Gain temporary root‑like access (no actual root needed) using the run-as trick for each app, or simply back up the public partitions:
    cd /sdcard && tar -cvf /sdcard/userdata.tar .
  3. Exit the shell (exit) and pull the archive to the PC:
    adb pull /sdcard/userdata.tar ./userdata.tar
  4. Optionally, back up the /data partition (requires the device to be in adb root mode, which most production devices do not allow). For a non‑root device you can only capture what is readable from /sdcard and the app‑specific data you can access via run-as.
  5. To restore, push the archive back and extract:
    adb push userdata.tar /sdcard/
          adb shell "cd /sdcard && tar -xvf userdata.tar"
  6. Reboot the device. Media and files will appear as before; app data that was not captured will need to be re‑installed.

This method is more manual but works on any Android version, and you can combine it with run-as per‑app backups for critical apps.

Step 10 – Automate Regular Backups (Optional)

If you want a scheduled backup without manual intervention, you can create a simple script on your PC. Below is a Bash example for Linux/macOS; Windows users can adapt it to a batch file or PowerShell.

# backup.sh – creates a dated ADB backup
#!/bin/bash
DATE=$(date +%Y-%m-%d_%H-%M)
FILE="android-backup-$DATE.ab"
adb backup -apk -shared -all -f "$FILE"
if [ $? -eq 0 ]; then
  echo "Backup saved as $FILE"
else
  echo "Backup failed"
fi

Make the script executable (chmod +x backup.sh) and schedule it with cron (e.g., 0 2 * * * for a daily 2 AM backup).

Store the backup files on an external hard drive or encrypted cloud storage for extra safety.

Troubleshooting Common Problems

SymptomPossible CauseFix
ADB reports "device unauthorized"USB debugging not confirmed on phoneCheck the prompt on the device, tap Allow, and enable "Always allow".
Backup file is 0 KBPhone denied the backup requestMake sure you tapped Back up my data on the dialog. If the dialog never appears, toggle USB debugging off/on and reconnect.
Restore fails with "Failed to read backup"Corrupted .ab file or wrong passwordVerify file integrity (compare checksum), re‑enter the correct password, or create a fresh backup.
Missing media after restoreUsed -shared flag omittedRe‑run backup with -shared or manually copy media from the old device.
App data not restored for certain appsApp opted out of ADB backup (e.g., WhatsApp, Signal)Use the app’s own export feature (e.g., WhatsApp chat export) or backup its private folder via run-as if you have the package’s debug flag.

Safety and Privacy Considerations

  • Encryption: If the backup contains sensitive credentials, set a password during the backup step. Remember the password – it cannot be recovered.
  • Storage: Treat the backup file like the original device. Store it on an encrypted drive or a password‑protected cloud folder.
  • Legal: Do not use ADB backup to extract data from devices you do not own or have explicit permission to copy.

When to Use ADB Backup vs. Cloud Services

ADB backup shines when you need a complete snapshot, including app APKs and private data that cloud syncs skip. It is also useful for devices without Google Play Services, for custom ROMs, or when you want a quick offline copy before flashing a new firmware.

For everyday photo or contact sync, Google Drive, OneDrive, or native device backups are more convenient. Use ADB backup as a supplemental safety net before major changes (OS upgrade, custom ROM flashing, factory reset).

With the steps above you now have a reliable, repeatable workflow to back up your Android phone locally and restore it whenever needed – all without rooting or paying for third‑party software.

User Comments (0)

Add Comment
We'll never share your email with anyone else.