DEV Community

Tùng Xuân
Tùng Xuân

Posted on Originally published at tanit365.com

The Android Backup That Fails Quietly: 5 Places Yours Is Probably Broken

Most people test a phone backup on the worst possible day: the morning the old phone will not turn on, the new one is in hand, and there is no time to fix anything.

Android's built-in backup is genuinely capable. The problem is that it is not one system — it is several separate ones wearing a single label, and each of them can stop working without ever telling you. These are the five places a phone backup usually breaks, in the order you tend to discover them while restoring.

1. The quota quietly filled up, so the backup quietly stopped

Android's own backup runs through Google One, and it shares the same free storage as Gmail and Google Photos. Every Google account gets 15 GB free across all three, and backup data generally counts against that same allowance.

That is the trap. A year of email attachments plus a handful of WhatsApp videos can push the account close to the limit, and when the free space runs out the backup does not shout at you — it just stops completing. The setting still reads as enabled, which is why this one is missed so often.

Two things to do. First, check the storage number in your Google account before you trust the backup at all. Second, if you need room, paid Google One plans start at 100 GB and step up through 200 GB and 2 TB. Whichever route you take, the point is that the free tier has to stay genuinely free, or the backup has nowhere to land.

2. Photos are backed up — and that is exactly why they got deleted

This single confusion explains most "I deleted one photo on my phone and it disappeared from my account too" complaints.

Backup is one-way. A photo is copied up to your account so that losing the phone does not lose the picture, and the original stays on the phone until you decide to remove it, either with Free up space in Google Photos or by deleting it yourself.

Sync is two-way. With backup on in Google Photos, deleting an item on the phone removes it from the cloud and from every other device signed in to the same account. For a living photo library that behaviour is correct. For an archive it is dangerous, because an archive on an external drive can never delete your files just because you tidied your phone.

Check it by opening Google Photos, tapping your profile picture, then Backup. The screen tells you whether backup is on, when it last finished, and how many items are still waiting to upload. While you are there, look at two settings: Original quality keeps full-size files, Storage saver compresses photos and caps video resolution; and the folder list, which by default can sweep in WhatsApp images, screenshots and memes and waste quota on pictures you will never look at again.

3. The WhatsApp backup whose key exists nowhere

WhatsApp keeps chats on the phone, not on its servers, so a lost phone means lost history unless a backup exists. The cloud backup lives under Settings, then Chats, then Chat backup, where you choose a frequency and can include videos.

Two details break people here. Turn on End-to-end encrypted backup — and then keep the password or the 64-digit key somewhere other than the phone you are protecting. Without that key the backup cannot be restored at all, which turns a good backup into an unopenable file. Also check whether the backup counts against the same Google storage allowance as everything else; the storage indicator in Google Drive under Backups will tell you.

There is a second, separate copy worth knowing about. WhatsApp writes the chat database into the phone's storage, usually under a folder named WhatsApp/Databases and on newer Android versions under Android/media/com.whatsapp/WhatsApp/Databases. The filenames look like msgstore-2026-09-19.1.db.crypt14, and the current one is msgstore.db.crypt14. That file is what gets restored when no Drive backup exists, so copying the whole WhatsApp folder — Databases and Media — to a computer, a USB-C drive or an SD card gives you a fallback that does not depend on any cloud account.

4. Downloads and Documents were never in the backup

Google One backup covers contacts, calendar events, SMS and MMS, call history, app data for apps that allow it, device settings and Wi-Fi passwords. It does not cover the files sitting in your Downloads, Documents, Recorder or scanner folders.

Those folders are where receipts, contracts, warranty cards, scanned paperwork and exported invoices end up. They are also the first thing people look for after a repair or a factory reset, and by then it is too late.

The fix is boring and takes ten minutes: sync those folders into cloud storage, or copy them to a microSD card or a USB-C flash drive through an OTG adapter. A 64 GB stick is cheap and turns an afternoon of copying into a real second copy. Keep the rule simple — one copy in the cloud, one copy on something physical that stays at home.

5. The two categories that are excluded by design

Banking and e-wallet apps treat a new phone as a new device. They need re-activation, sometimes with a card, an ATM or a branch visit, and no backup tool will carry that activation across. Do it while the old phone and the SIM still work.

Authenticator apps are excluded from cloud backups on purpose, because one-time codes are exactly what an attacker would want. Google Authenticator can move accounts to a new phone by QR code; other apps vary, and many services expect you to enrol again with the recovery codes you were given at setup. Migrate before you wipe the old phone, not after.

Alongside those two sit the smaller device-bound items: eSIM profiles, which the carrier has to re-issue; Bluetooth pairings for a watch, earbuds or a car, which are tied to the device and have to be set up again; and work profiles, which are controlled by your employer's system and cannot be restored on your own.

The check to run while both phones still work

A backup that has never been inspected is only a hope. Four screens settle it. The Google backup screen should show a recent date and a size that makes sense — thousands of photos with a backup of a few megabytes means the photos are not in it. The Google Photos backup screen should show a finished run with nothing waiting. The contact count on the phone should match the count in Google Contacts. And the WhatsApp chat backup screen should show today's or yesterday's date with a size that fits your history.

Then do the real test, which costs one minute: open the cloud copy on a computer and confirm one specific old item is there. A photo from last year, a saved note, an exported contact file. If you cannot find one named thing, you do not have a backup — you have a setting.

Restoring is the mirror image. On the new phone, sign in with the same Google account during setup, choose to restore from the cloud, and keep the phone on Wi-Fi and plugged in. Samsung owners can move everything across with Smart Switch instead, and WhatsApp asks to restore as soon as you verify the same number.

The habit underneath all of it is one sentence: a backup only counts if the copy lives somewhere other than the phone. Cloud backup handles most of the job automatically, and the rest — the authenticator, the banking apps, the recovery codes, any folder outside Google's reach — is precisely what hurts when it goes missing. Work through it once, calmly, while both phones are still in front of you.

Top comments (0)