Data Recovery Case File · Cameras, Drones & Cards · Entries, Not Files
What the Gallery Was Actually Doing
Her enquiry describes something genuinely alarming to watch. A memory card in a phone: "a few days ago I got a message as if the card wasn't placed in the correct place anymore. I wasn't even using my phone in that moment. After a while a countdown from the gallery started removing all my photos, videos, documents. It's like the card has been damaged and cannot read it anymore." Sitting there while a progress bar deletes your photographs one by one is a horrible experience. But that countdown was almost certainly not deleting anything — it was the phone tidying up references to files it could no longer see, and the distinction is the whole case.
| Media | microSD card from a mobile handset — card ceasing to respond during idle operation; gallery index subsequently purging entries; card not readable in other devices |
| Reported situation | Card in a phone, not in active use at the time · host reporting the card as no longer correctly seated · gallery removing photographs, videos and documents progressively · card not readable in other devices · content required |
| Fault class | Card ceasing to enumerate with the host media index purging orphaned entries — content unaltered on the card |
| Equipment used | No further insertion attempts · enumeration attempted write-blocked under strict timeouts (DeepSpar USB Stabilizer 10Gb) · chip-level read past the controller where required · media validated by rendering and playback |
The decode: what a media index is, and why it emptied
How a phone gallery actually works: it does not read the card every time you open it. That would be far too slow. Instead the phone maintains a media index — a database on its own internal storage listing every photograph and video it knows about, with thumbnails, dates and locations. The gallery displays that database. When you scroll through your photographs, you are looking at the index, and the actual files are only fetched when you open one.
What happens when a card stops responding: the phone notices that a large number of indexed files are no longer reachable and runs a cleanup, removing the entries for everything it cannot find. That process has a progress indicator, because it may be removing thousands of entries. What she watched was that cleanup — the phone deleting its own records of her photographs, not the photographs. The files never moved; the card simply stopped answering, and the phone tidied up after what it assumed was a removed card.
Why this is such a distressing thing to see: it looks exactly like deletion. The thumbnails vanish one by one, in order, with a count. Nothing about the interface distinguishes "removing entries for files I cannot reach" from "deleting your photographs", and there is no way to stop it.
What that means for her position: the card was not wiped by the phone. Whatever is on it is still on it, and the actual fault is that the card stopped responding — which the phone's message about incorrect seating was the first sign of, and which is confirmed by the card not reading in other devices either.
Why it failed while she was not using it: worth saying, because it feels like it should need a cause. Cards are read and written continuously in the background — indexing, thumbnail generation, application databases, logging — regardless of whether the screen is on. So a card can fail during what feels like idle time, and the controller failing to respond is the commonest way it happens.
The one caveat, stated honestly: a countdown removing files is also, occasionally, what malicious software looks like. If anything unusual had been installed shortly before, that is worth mentioning — but a card that has simultaneously stopped reading in every other device points firmly at hardware, because malware on a phone does not make a card unreadable elsewhere.
What to stop: reinserting it. The elimination is complete across devices, and each attempt powers a controller that is failing.
On the bench
No further insertion was attempted, since the card had already failed to read in several devices and each attempt powers a failing controller. Enumeration was attempted write-blocked behind the DeepSpar USB Stabilizer 10Gb under strict timeouts, establishing where the introduction stopped — since a card that ceases to respond during idle operation has usually failed at controller level rather than lost its contents. Where the controller could not be brought up, the memory was read at chip level past it and reconstructed in software. Media was validated by rendering and playback.
The outcome
The failure point established under timeout control, the memory read past the controller and the media validated and delivered. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode, for anyone who has watched a gallery empty itself: that was almost certainly the phone removing its own records rather than your files. Galleries display a database of known media held on internal storage, and when a card stops responding the phone cleans up entries for everything it can no longer reach — with a progress bar, because there may be thousands. Your photographs did not move. The card stopped answering, which is the actual fault.
Gallery that emptied itself while you watched
What you saw was almost certainly the phone deleting its own records, not your photographs. A gallery doesn't read the card each time you open it — it keeps a database on the phone's internal storage listing everything it knows about, with thumbnails and dates, and that's what you scroll through. When a card stops responding, the phone notices that thousands of indexed files are unreachable and removes those entries, with a progress indicator because there are so many. It looks identical to deletion and there's no way to stop it, but the files never moved. The real fault is that the card stopped answering, which is why it won't read in other devices either. Stop reinserting it — each attempt powers a controller that's already failing.
They're probably still on the card — call Newcastle Data Recovery on 0191 406 1051; enumeration read under strict timeouts, memory read at chip level past the controller, media validated by rendering.
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.