The direct answer is to compare the phone with a pre-change record, confirm important files and app data are present, verify backups and synchronization independently, and test one harmless file through restore or export. Do not erase the old device or backup until the new state is proven.
Capture the post-change state
Record the phone model, operating-system version, update time, total storage, free space, account names, work profile, removable media, and any warnings. Compare those values with the pre-update screenshot or checklist. A change in reported free space may reflect temporary update files or rebuilt indexes, but missing folders or unexpectedly signed-out apps need investigation.
Review photos, downloads, documents, messages, contacts, offline media, password-manager access, authenticator entries, and business files. Open a sample from each important category. A thumbnail or filename is not proof that the full file is readable.
Verify backup details instead of assuming sync
Google's Android backup guide says Android can back up apps and app data, call history, contacts, device settings, and messages, but not every app can back up or restore all settings and data. It also lets users review backup details and warns that restoration varies by device and Android version.
Check the selected backup account, included data types, and last successful backup time. Review photo synchronization separately from device backup. If the update involved moving to another phone, inspect downloads, hidden folders, non-store apps, and app-specific data because Google's transfer guidance lists categories that may not copy during setup.
Test apps and permissions
Open the apps that hold important local data and confirm the expected account, recent records, offline files, and export function. Review storage, photos, camera, microphone, location, and notification permissions for unexpected changes. Test a normal action without granting broader access than before.
For work devices, confirm management and work-profile policies are active. NIST SP 800-124 Rev. 2, mobile-device security guidance, covers security across deployment, use, and disposal and recommends protecting stored data. A major change should not silently remove the lock, encryption, management, or remote-wipe posture required by policy.
Check synchronization conflicts
Create a neutral test note or photo, wait for synchronization, and verify it appears in the intended account from another authorized device or web interface. Edit it once on the phone and confirm the correct version wins. Then delete the test item and inspect trash or recently deleted folders. Avoid using irreplaceable data for this test.
If there are duplicate contacts, missing messages, or conflicting photo counts, pause cleanup. Export evidence and determine which account or service is authoritative before merging or deleting. Free-space tools can remove local copies that appear backed up, so verify the remote copy directly first.
Prove a recovery path
Restore or export one harmless record through the supported procedure. Confirm that recovery credentials, PINs, backup passwords, or recovery contacts are available to the owner. Do not store recovery secrets in the same unprotected folder as the backup.
The phone passes verification when required data is readable, backups show the expected account and current time, critical apps and permissions behave correctly, storage protection remains active, synchronization is consistent, and one recovery test succeeds. Keep the old backup until those checks are complete and documented.
Sources
- Back up or restore data on your Android device — Google Android Help
- Copy apps and data from an Android to a new Android device — Google Android Help
- Guidelines for Managing the Security of Mobile Devices in the Enterprise — National Institute of Standards and Technology, May 1, 2023