Transfer Android Apps and Their Data Between Phones Using ADB (No Root)

Before you start – What you need

Transferring an app together with its private data from one Android phone to another is a common request when you upgrade devices or switch to a fresh install. The Android platform isolates each app’s data for security, which also means the data isn’t automatically copied when you install the same APK on a new phone. Using adb (Android Debug Bridge) you can create a backup that contains both the APK file and the app’s private data, move it to the target device, and restore it – all without rooting either phone.

• Two Android phones running Android 5.0 (Lollipop) or newer. The method works on most OEM skins, but menu wording may differ slightly.
• A computer (Windows, macOS, or Linux) with the Android SDK Platform‑Tools installed.
• USB cables for each phone (or a single cable if you use a USB hub).
• Enough free storage on the destination phone for the app and its data.

Important: The backup created by adb backup is not encrypted by default. If the data is sensitive, you should encrypt the backup file yourself (e.g., with OpenSSL) before transferring it.

Step 1 – Install the Android SDK Platform‑Tools

Step 2 – Enable Developer Options and USB Debugging on both phones

Step 3 – Verify ADB connection for each device

Step 4 – Create a backup of the app on the source phone

Step 5 – Transfer the backup file to the destination computer (optional)

If you are using the same computer for both devices, you can skip this step. Otherwise, copy myapp.ab to a location accessible by the destination phone (e.g., a USB flash drive, cloud storage, or via the same computer).

Step 6 – Restore the app and data on the target phone

Step 7 – Verify the transfer

Open the restored app on the destination phone. Check that your settings, login state, and any locally stored content (e.g., notes, game progress) appear as expected. If the app asks you to log in again, it may be because the developer has disabled data migration for security reasons – in that case, the APK transfer succeeded but the data could not be restored.

Alternative approaches

• Using Android’s built‑in “Share app” feature (Android 12+) – Some OEM skins allow you to share an app’s APK via the Share menu, but this never includes private data.
• Third‑party backup apps (e.g., Helium, Super Backup) – These often require a desktop companion or root to access data, making ADB the most universal method for non‑root devices.
• Full device backup with adb backup -all – This captures every app and system data, but restoring to a different device can cause conflicts and is not recommended for selective transfers.

Troubleshooting

1. “Backup failed: No space left on device”

Both the source phone and the computer need enough free storage for the temporary .ab file. Check the size of the app’s data (Settings → Apps → App → Storage). Free up space or use a larger external drive.

2. “Restore failed: Permission denied”

This usually happens when the backup was encrypted with a password but the wrong password is entered, or when the backup file is corrupted. Verify the password or recreate the backup without encryption (or encrypt it manually with a known method).

3. “Package not installed” after restore

Some apps refuse to install if the signature on the APK does not match the one expected for the device (e.g., carrier‑specific builds). In such cases, download the official APK from a trusted source and install it first, then restore data only (omit -apk flag in the backup command).

4. “Device unauthorized”

Re‑plug the USB cable, revoke USB debugging authorizations in Developer options, and accept the RSA prompt again. On some devices, you may need to enable “Install via USB” under Developer options.

Safety warnings and best practices

• Data privacy: The .ab file contains everything the app stores internally, which can include passwords, messages, or location history. Treat it like a private key – keep it in a secure folder and delete it after the transfer.
• Compatibility: Not all apps allow their data to be restored on a different device. Apps that use device‑specific identifiers (IMEI, hardware IDs) may reset themselves.
• Battery: Ensure both phones are charged above 50 % or keep them plugged in during the backup/restore to avoid interruption.
• System updates: If the source device runs an older Android version, some newer system libraries may be missing on the target, causing crashes after restore. In such cases, consider updating the target phone first.

Step‑by‑step recap

1. Install Platform‑Tools on your computer.
2. Enable USB debugging on both phones.
3. Connect each phone and verify with adb devices.
4. Identify the app’s package name.
5. Run adb backup -apk -obb -f myapp.ab <package> on the source phone.
6. Transfer the .ab file if needed.
7. Run adb restore myapp.ab on the destination phone.
8. Open the app and confirm that data migrated correctly.

With these steps you can move any installable app and its private data between Android devices without rooting, without relying on cloud backups, and without losing the context that makes the app useful.

When to consider a full device backup instead

If you are migrating everything – contacts, messages, settings, and multiple apps – a full device backup (e.g., using adb backup -all or a custom recovery) may be more efficient. However, full backups are harder to restore selectively and can run into version‑specific issues. Use the app‑by‑app method described here when you only need a handful of apps or when you want fine‑grained control over what data moves.