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.
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.
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.
The adb backup command can target:
-apk -shared -all)-apk)-sharedFor 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.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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
-shared flag to exclude large media..ab file without encryption – it contains private data like login tokens and personal messages.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.
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.









