Transfer SMS Between Android Phones Using ADB (No Root)

Moving your text‑message history to a new Android phone can feel risky, especially if you don’t want to root the device or rely on third‑party cloud services. The Android Debug Bridge (ADB) offers a built‑in, no‑root method to back up and restore the SMS database. This tutorial walks you through the entire workflow – from preparing both phones to verifying that every conversation arrived intact.

Before you start

• Charge both phones to at least 70 %. ADB backup can be interrupted by a low‑battery shutdown, which may corrupt the backup file.
• Use a reliable USB‑C or micro‑USB cable. Faulty cables cause intermittent connections that break the backup.
• Have a computer with ADB installed. Windows, macOS, or Linux will work; the steps are identical.
• Make sure you have enough free storage on the computer (a few megabytes for the SMS backup, plus extra for any media you may decide to include later).
• Back up any important data on the target phone first. Restoring an ADB backup will overwrite existing app data, which includes SMS.

Step 1 – Install ADB on your computer

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

Note: On some OEM skins (e.g., Xiaomi’s MIUI or Huawei’s EMUI) the wording may differ – look for “USB debugging” or “Android debugging”.

Step 3 – Verify the ADB connection

Step 4 – Create an ADB backup that includes SMS

Step 5 – Transfer the backup file to the new phone

Step 6 – Restore the SMS backup on the target phone

After the restore, Android automatically restarts the messaging app so the new SMS database is loaded.

Step 7 – Verify that the messages arrived

• Open your default Messaging app on the target phone.
• Navigate through recent conversations; you should see the same threads that were on the source phone.
• Send a test SMS to a friend and confirm it appears in the conversation history on both devices.

If any thread is missing, it likely means the backup did not capture it (e.g., if the source device’s SMS provider was disabled). In that case, repeat Step 4 and make sure the com.android.providers.telephony package is included.

Alternative method – Using the built‑in “SMS backup & restore” feature (if available)

Some manufacturers (e.g., Samsung, Xiaomi) ship a native “Backup & restore” tool that can include SMS. If the ADB approach fails because the OEM blocks com.android.providers.telephony, you can use the built‑in option as a fallback:

1. Open Settings → Backup & restore (or similar).
2. Choose Local backup and select “SMS” as the data type.
3. Save the backup file to internal storage, then copy it to the new device via USB or Wi‑Fi.
4. On the target phone, repeat the steps and select “Restore from local backup”.

This method does not require a computer, but it is device‑specific and may not be available on all Android versions.

Troubleshooting common issues

1. ADB reports “device unauthorized”

• Disconnect and reconnect the USB cable.
• On the phone, go to Developer options → Revoke USB debugging authorizations, then reconnect and accept the prompt.
• Make sure you are not using a USB hub; a direct connection is more reliable.

2. Backup file is unusually small (a few kilobytes)

• This usually means the -include flag was missed or the SMS provider is disabled.
• Run adb shell pm list packages | grep telephony to confirm that com.android.providers.telephony is present.
• If the package is missing (some custom ROMs rename it), use the generic -all flag without -include to back up everything, then filter the SMS later.

3. Restore fails with “Failed to restore data”

• Check that the target phone is running the same Android version or a newer one. Restoring a backup made on a newer OS to an older OS can cause incompatibility.
• If you set a password during backup, ensure you type it exactly the same during restore.
• Try the restore command with the -no_restore_permission flag (requires Android 9+):

  adb restore -no_restore_permission sms_backup.ab

4. Duplicate or missing threads after restore

• Some messaging apps (e.g., Google Messages) store a copy of the conversation in their own private database. After restore, the app may merge the old and new data, resulting in duplicates.
• Clear the app cache (Settings → Apps → Messages → Storage → Clear cache) and reopen the app. Duplicates often disappear.
• If messages are still missing, repeat the backup ensuring you did not exclude the shared flag – some OEMs store SMS in a secondary file on external storage.

Safety warnings

• Never restore a backup onto a device that already contains important SMS data unless you have a separate backup of that device. The restore overwrites the existing SMS database.
• If you use a password for the backup, store it securely. Forgetting it makes the backup unrecoverable.
• A backup file (.ab) is essentially a zip archive of app data. Treat it like any personal data – keep it on an encrypted drive if the messages contain sensitive information.

What to do next

Now that your messages have moved safely, you might want to:

• Set up Google’s “Messages for Web” on the new phone to keep a cloud‑based copy of future chats.
• Periodically repeat the ADB backup (e.g., monthly) and store the .ab files on an external drive for long‑term archiving.
• Explore ADB’s other backup options – you can include call logs, Wi‑Fi settings, or even app data for games.

With the steps above, you’ve moved your entire SMS history without rooting, without third‑party apps, and with full control over the backup file. If you run into a scenario not covered here, feel free to revisit the troubleshooting section or ask the Appitika community for device‑specific tips.