Data Recovery Case File · Cameras, Drones & Cards · Phones Write Without Being Asked
Pulled the Card Out of the Phone
Her enquiry was candid about a rule she had never been told. "I didn't dismount my SD card from my phone — didn't know I had to! It can't be read now. Is there a solution to this? I think on the card is mainly photos I'm keen to have." Nobody tells people, and phones make it worse than computers do. On a computer you at least know when you are copying something. A phone writes to its card constantly, in the background, without being asked — scanning media, generating thumbnails, updating app caches and databases — so the odds that a card is mid-write at any given moment are far higher than most owners would guess. That is why removing one without unmounting is riskier than the same act on a laptop, and it explains what happened to hers.
| Media | microSD card removed from an Android handset without unmounting — no longer readable; photographic content held |
| Reported situation | Card removed while the phone was running · unmount step not performed and not known to be required · card unreadable since · photographs sought |
| Fault class | Filesystem structures left inconsistent by an interrupted background write — content intact behind unreadable records |
| Equipment used | Card imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · partition and filesystem structures reconstructed on the image · format-aware carving alongside · photographs validated by rendering |
The decode: why phones are the risky case, and what unmounting does
What unmounting actually does: it is not a formality. Operating systems hold recent changes in memory and commit them to storage in batches, because writing in bulk is far faster than writing continuously. Unmounting tells the system to flush everything still held, finish any operation in progress, and close the filing structure cleanly by marking it consistent. Remove the card before that and the structure is left mid-update — entries partly written, allocation records disagreeing with one another, and a journal describing a change that never completed.
Why a phone is worse than a computer: the point worth knowing. On a computer, most writing happens because you asked for it, so you have some sense of when the card is busy. A phone does not work that way. Its media scanner indexes new files; the gallery generates and caches thumbnails; applications write their own databases and caches to the card; system services update metadata. All of that happens continuously and invisibly, whether or not the screen is on. So the moment somebody pulls a card out of a running phone, the chance that something was mid-write is high — and it is high every time, which is why the habit catches people who have got away with it for years.
Why her photographs are almost certainly fine: nothing in that sequence erases anything. Interrupted writes damage the small records describing where files live; the photographs themselves are large, contiguous and untouched. Reconstruction rebuilds those records on an image, and the volume typically returns with its folder tree, filenames and dates intact.
What to refuse: both platforms will offer to help and both offers are harmful. A computer will suggest scanning and repairing, or formatting. The phone, on reinsertion, may report the card as damaged and offer to format it for use — which is the same destruction wearing friendlier wording. And the card should not be put back into the phone at all, because a phone that decides to repair or reindex a card writes to it immediately.
Where the unmount option actually lives, for next time: it is in the phone's storage settings, usually as eject or unmount SD card, and it takes a moment. Powering the phone off completely before removing the card achieves the same thing and is easier to remember.
On the bench
The card was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb in a single pass, so that everything afterwards happened against a copy and no prompt from a phone or computer could reach the original. On the image the interrupted structures were reconstructed — the half-written directory and allocation records resolved and the incomplete transaction unwound — until the volume mounted from the copy with its folder tree, filenames and dates intact. Format-aware carving swept alongside for anything beyond structural repair, and every photograph was validated by rendering before delivery.
The outcome
The volume rebuilt from a write-blocked image and the photographs validated and delivered with names and dates. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone who pulled a card from a phone: unmounting flushes writes still held in memory and closes the filing structure cleanly, so removing without it leaves the records mid-update while your photographs stay physically intact; phones are riskier than computers for this because they write constantly in the background — indexing media, generating thumbnails, updating app databases — so something is very often mid-write; do not put the card back in the phone, which may offer to repair or format it; and next time, use eject in the storage settings, or simply switch the phone off first.
Card pulled out of a phone without ejecting
Keep it out of the phone, and don't let anything format it. Your photographs are almost certainly intact — an interrupted write damages the small records describing where files live, not the files themselves — but both your phone and your computer will offer to fix it, and every one of those offers writes over exactly what a recovery rebuilds from. The phone's version is the sneakiest, because it reports the card as damaged and offers to prepare or format it for use, which sounds helpful and isn't. Don't be hard on yourself for not knowing: phones write to cards constantly in the background, indexing media, building thumbnails and updating app databases, so the chance of catching one mid-write is high every single time. For the future, use the eject or unmount option in your phone's storage settings, or just power the phone off before removing the card.
Don't put it back — call Glasgow Data Recovery on 0141 404 0294; imaged write-blocked, interrupted structures rebuilt on the copy, photographs returned with folders and dates.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.