Create a Portable ADB Backup and Restore It on Any Android Phone (No Root)

13 min read Learn a step‑by‑step method to back up apps and data with ADB, make the backup portable, and restore it on a different Android device without rooting. October 09, 2026 16:00 How to Create a Portable ADB Backup and Restore It on Any Android Device (No Root)

Backing up an Android phone is easy when you stay with the same device, but moving that backup to a completely different phone often feels risky. This tutorial shows you how to use the official adb tool to create a portable backup that can be restored on any Android device that supports the same Android version, without ever rooting the phone.

Why a portable ADB backup matters

Most built‑in backup solutions (Google Backup, OEM cloud services) tie the data to a specific Google account or device. If you change phones, you may lose app settings, game progress, or even SMS history unless the app itself offers its own cloud sync. A portable adb backup gives you a single .ab file that contains the selected apps and their private data. Because the file is generated on the device itself, it respects the app’s encryption and permission model, yet you can move it to any computer, USB stick, or cloud storage and later restore it on another phone.

Before you start

  • Computer with ADB installed – Windows, macOS, or Linux. If you haven’t installed ADB yet, download the Platform‑Tools package and extract it.
  • USB cable – Use the cable that came with the phone for reliable data transfer.
  • Charging level – Keep the phone above 50 % to avoid interruptions.
  • Backup destination – Ensure you have enough free space on your computer. A full backup can be several gigabytes for media‑heavy devices.
  • Enable Developer Options & USB debugging on both source and target phones (Settings > About phone > Tap Build number seven times, then Settings > System > Developer options > USB debugging).
  • Optional: encryption password – If you want the backup file to be unreadable without a password, decide on a strong passphrase now.

Step‑by‑step: Creating the backup

1. Connect the source phone

Plug the phone into your computer via USB. On the phone, you’ll see a prompt asking to allow USB debugging. Tap Allow and optionally check “Always allow from this computer”.

Verify the connection by opening a terminal (or Command Prompt) and running:

adb devices

You should see a device ID followed by device. If you see unauthorized, re‑check the prompt on the phone.

2. Decide what to back up

The adb backup command can target:

  • All user apps and data (-apk -shared -all)
  • Specific packages (comma‑separated list after -apk)
  • Only the shared storage (photos, downloads) with -shared

For a portable backup, it’s safest to exclude large media files that you can copy separately. The example below backs up all installed apps and their private data, but skips the shared storage:

adb backup -apk -all -nosystem -f backup_all.ab

Explanation:

  • -apk – Include the APK files so you can reinstall them without pulling from the Play Store.
  • -all – Back up every user‑installed app.
  • -nosystem – Skip system apps (they’re already present on the target device).
  • -f backup_all.ab – Write the output to backup_all.ab in the current folder.

3. Set an encryption password (optional but recommended)

When you run the command, the device will display a dialog asking for a backup password. This password protects the .ab file. Choose a password you can remember, or store it in a password manager.

If you prefer an unencrypted backup (e.g., for quick testing), simply leave the password field blank and confirm.

4. Wait for the backup to finish

The progress bar on the phone shows the backup status. Large apps (games, navigation) can take several minutes. Do not disconnect the USB cable until the terminal returns to the prompt.

When the command finishes, you’ll see something like:

Backup transport: 0.0.0.0:0

The backup_all.ab file is now ready for transport.

Step‑by‑step: Making the backup portable

1. Verify the file integrity

Run a quick checksum on the backup file. On Windows, you can use certutil -hashfile backup_all.ab SHA256. On macOS/Linux, use shasum -a 256 backup_all.ab. Store the hash value in a note – it will help you confirm the file wasn’t corrupted during transfer.

2. Transfer the file to a safe location

Copy the .ab file to a USB flash drive, external SSD, or a cloud folder you trust. Because the file may contain personal data, treat it like any other sensitive backup.

3. (Optional) Convert to a tar archive for inspection

If you ever need to peek inside the backup, you can convert it with the Android SDK’s adb utility:

adb backup -noapk -noobb -nosystem -f dummy.ab
# (create a dummy file to get the conversion tool)

# Convert the real backup to tar
openssl pkcs12 -in backup_all.ab -nodes -passin pass:yourPassword | tar -xvf - -C ./backup_extracted

Only do this on a trusted computer, as the extracted files contain private app data.

Step‑by‑step: Restoring the backup on a different Android device

1. Prepare the target phone

Enable Developer Options and USB debugging on the new device (same steps as in the “Before you start” section). Also, make sure the target phone is running an Android version equal to or newer than the source. Restoring a backup from a newer OS onto an older OS is not supported.

2. Connect the target phone

Plug the phone into the same computer (or a different one with ADB installed). Verify the connection with adb devices. The device should appear as device.

3. Initiate the restore

Run the following command, pointing to the backup file you transferred:

adb restore backup_all.ab

The phone will display a prompt asking to confirm the restore and to enter the backup password (if you set one). Confirm and type the password.

4. Wait for the restore to complete

The device will show a progress bar similar to the backup step. Do not disconnect the USB cable. When the terminal returns to the prompt, the restore is finished.

5. Verify the apps and data

Open a few of the restored apps to confirm that settings, login states, or game progress are present. Some apps encrypt their data with a device‑specific key; in rare cases you may need to log in again.

Troubleshooting common issues

  • Backup/restore fails with “Transport error”: Ensure the phone is not in “Charge only” USB mode. Switch to “File transfer (MTP)” or “USB tethering”.
  • “Backup failed: No space left on device”: The temporary backup buffer on the phone can be limited. Free up internal storage or use the -shared flag to exclude large media.
  • Restored apps won’t launch (crash on start): The target device may have a different CPU architecture (e.g., ARM64 vs. ARM32). ADB backup includes the APK, but native libraries compiled for the source architecture won’t run on the target. In that case, reinstall the app from the Play Store on the target device.
  • “Password incorrect” after restore: Double‑check that you typed the exact password. Remember that the password is case‑sensitive.
  • Backup file is corrupted (checksum mismatch): Re‑transfer the file using a reliable method (e.g., copy directly over USB rather than through a flaky Wi‑Fi share).

Safety warnings and best practices

  • Never share the .ab file without encryption – it contains private data like login tokens and personal messages.
  • Keep a copy of the backup password – If you lose it, the file cannot be restored.
  • Avoid restoring over a system update – If the target phone has just received a major OS update, restore after the first reboot to let the system settle.
  • Test on a non‑critical device first – If you have an older phone, try the restore there before applying it to a primary device.

When to choose a different method

If you need to move large media collections (photos, videos) alongside app data, consider using a dedicated media backup (Google Photos, a manual file copy) in addition to the ADB backup. For apps that store data in the cloud (e.g., WhatsApp, Telegram), use the app’s own export feature to avoid missing messages.

Wrapping up

With the steps above you can create a portable ADB backup, move it safely, and restore it on any compatible Android phone without rooting. This workflow gives you full control over what gets saved, protects the data with encryption, and avoids reliance on cloud services that may disappear or change policies. Keep the backup file in a secure location, remember the password, and you’ll have a reliable safety net for future device migrations.

User Comments (0)

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