Back up an Android phone in three separate passes: verify Google Photos says “Backup complete,” review the device-backup details for the data and messages you need, and sync or transfer authenticator access before erasing the original phone.

Android does not provide one universal backup. Photos and videos, supported device data and messages, and authenticator access use separate systems. Backup completion, restoration and account recovery are different claims; one does not prove another.

Before you start

Keep the old phone charged, unlocked, on reliable Wi-Fi and available. Confirm its screen lock and the password for the intended backup account. Check cloud storage, then list the information you cannot replace: important media, downloads, documents, messages, app records and accounts protected by two-step verification.

More storage is not another copy. Our 128GB vs 256GB Android guide explains capacity, but every phone needs a backup plan. For an Apple source device, use the guide to transfer data from iPhone to Android because its migration routes and limits differ.

This framework mainly applies to phones using a Google Account and Google Play services. Work-managed phones may restrict backup or transfer, and no menu path is universal. [1] [2]

The three separate backup systems

Use this graphic to decide which system protects each category and what evidence to check.

Diagram showing separate Android backup systems for photos and videos, device data and messages, and authenticator access
Android safety depends on verifying three systems separately, not trusting one backup toggle.
Data to protect Main system Evidence to check
Photos and videos Google Photos Correct account, required folders, finished status and item details
Device data and messages Android backup Correct account, current details and restored examples where possible
Authenticator access Authenticator-specific sync or transfer Codes available elsewhere and critical sign-ins tested

1. Verify photos and videos

Enabling Google Photos does not prove every local image or video is included. Confirm the selected Google Account and the device folders that matter. Screenshots, downloads, edits and app-created folders may not be covered simply because the camera folder is uploading.

Wait for “Backup complete,” then inspect a recent photo, an older photo, a video and an item from every important non-camera folder. Paused, queued, failed or local-only items have not passed verification. [3]

Choose quality deliberately. Original quality preserves captured resolution; Storage saver can compress or resize eligible media, while Express uses stronger reductions and is unavailable in some regions. [4] These checks verify selected Photos media—not documents, hidden locations, device data or authenticator access.

2. Verify device data and messages

Android backup can include apps and some app data, call history, contacts, settings, SMS and MMS. RCS can be included when you use Google Messages, and Google says received end-to-end encrypted Google Messages conversations are included under its documented conditions. This does not cover every messaging app, chat history or app database. [1] [6]

Check the backup account, listed categories and latest finished status. Google notes that backup can take up to 24 hours and restored data may take time to appear. [1] App developers determine whether their apps support Android backup and how much data restores. Some apps need separate sign-in, export, sync or transfer; downloads, hidden files and non-Google account data may remain outside Android backup or direct copy. [7]

On an available destination phone, inspect older and newer messages, contacts, important settings and critical apps. One restored category does not prove the others.

3. Protect authenticator and recovery access

Google Authenticator uses its own protection methods. Codes can sync when you are signed into a Google Account inside Authenticator. Without an account, complete the documented manual transfer while the old phone remains available. [5]

This graphic separates Authenticator sync, manual transfer and provider recovery.

Flow diagram showing Google Authenticator account sync, manual transfer and provider recovery routes
Authenticator access needs its own verified path; normal Android backup is not proof that codes can be recovered.

Confirm every expected entry on another usable device, then test critical codes while the original phone and an approved recovery method remain available. Do not delete a synced entry as a test; deletion can remove it from other connected devices. [5] Third-party authenticators may use different systems, so follow that app’s current documentation and retain recovery codes, security keys or alternate verification where supported.

The shortest safe workflow

  1. Inventory irreplaceable data. Identify folders, messages, files, app records and protected accounts.
  2. Confirm the accounts. Check the accounts used by Android backup, Google Photos and Google Authenticator.
  3. Run Android backup. Select the required categories and allow a fresh backup to finish.
  4. Finish Photos separately. Confirm folders and quality, wait for “Backup complete” and inspect representative items.
  5. Protect sign-in access. Confirm Authenticator sync or transfer, then test critical codes and recovery methods.
  6. Copy when useful. Cable or Wi-Fi transfer can migrate supported data during setup, but it is not proof of an independent backup. [2] [7]
  7. Verify before erasing. Open restored information on the destination or confirm it through the relevant cloud service.

When replacing a device, follow its prompts and then set up your new Android phone. Reaching the home screen proves setup completed, not that every required item arrived.

Do not erase until this checklist passes

Use this graphic to make the final go/no-go decision.

Checklist for verifying Android photos, device data, messages and authenticator access before erasing a phone
The erase decision comes after separate evidence checks, not one successful backup message.
  • Photos shows the intended account, required folders, acceptable quality and a completed status.
  • Representative old, new, video and folder-specific media opens from the verified destination.
  • Android backup shows the correct account, a recent finished status and the expected categories.
  • Important messages, documents and app records have been opened or checked elsewhere.
  • Expected authenticator entries work away from the old phone, with an alternate recovery route available.
  • The old phone remains unchanged until every required check passes.

For a sale or trade-in, continue with the before-selling Android phone checklist. Transfer and verify first; account removal and reset come later.

When backup or transfer fails

If the old phone is available, stop the reset or handover. Recheck accounts, Wi-Fi, power, cloud storage, Photos folders and status. Let pending work finish, export local-only app records through documented methods and transfer offline Authenticator codes before erasing the phone.

If the destination is missing data, identify whether Photos, Android backup, a manufacturer tool or the app owns that category. A manufacturer transfer tool can help migration, but it does not prove an independent cloud copy or guarantee unsupported app data. Restoring from a newer Android version to an older one can also be incomplete. [1]

If the old phone is lost, damaged or erased, recovery depends on what reached another location beforehand. Local-only files, unsupported app data, unsynced authenticator secrets and app histories without another copy may be unrecoverable. Use provider recovery codes, a security key, alternate verification or account recovery when codes are missing.

Frequently asked questions

Does Android backup save everything on my phone?

No. Android backup can include supported apps and some app data, call history, contacts, settings, SMS and MMS, but coverage depends on the app and device. Photos use Google Photos separately, and authenticator access needs its own sync, transfer or recovery method. Check local files and app-specific exports before erasing anything. [1]

Does Android backup include SMS, MMS and RCS messages?

SMS and MMS can be included. RCS can be backed up when you use Google Messages, including received end-to-end encrypted conversations under Google’s documented conditions. This does not prove chats from other messaging apps are covered, so check each app’s own backup or transfer instructions. [1] [6]

Does Google Photos back up screenshots and app folders?

Google Photos can back up selected device folders, but camera backup does not prove that screenshots, downloads, edits or app-created folders are included. Review folder settings, wait for “Backup complete” and inspect representative items from each important folder before deleting local originals. [3]

Are Google Authenticator codes included in normal Android backup?

Do not rely on normal device backup for them. Google documents separate account-based sync and manual transfer methods for Authenticator. Confirm the entries on another usable device and test critical sign-ins before erasing the old phone. Third-party authenticators require their own current instructions. [5]

Can I restore an Android backup to a phone running an older Android version?

You may restore some data, but do not expect a complete result. Google warns that moving data from a newer Android version to an older one can be incomplete. Keep the original phone and independent copies until you have checked the messages, settings, apps and files you actually need. [1]

The go/no-go rule

If any important photo, message, file, app record or sign-in method exists only on the original phone, do not erase, sell, trade in or hand over that phone.

Sources

The official references used in this guide are listed in the source panel below and were checked on August 5, 2026. Recheck app-specific and manufacturer instructions for the exact phone and software version.