Data Recovery Case File · Cameras, Drones & Cards · Do Not Accept the Prompt
The Card Dropped Out Mid-Read, and the Phone Will Offer to Fix It
Her enquiry describes a card that worked for years and then behaved oddly on one particular route. Photographs taken normally on a trip, then "when I took the card out of the camera and put it in a phone adapter, the photos appeared at first and then suddenly disappeared. I retried this process but the phone" would not. Appearing and then vanishing is the card dropping out during a read — and the greater risk now is what the phone suggests next.
| Media | SD card in long-term camera service — enumerating briefly through a phone adapter and disconnecting during read; subsequently not recognised on retry |
| Reported situation | Card used in a camera over a long period without difficulty · photographs taken normally during a trip · card inserted into a phone via an adapter · photographs listed briefly and then disappearing · process retried · phone no longer recognising the card · photographs required |
| Fault class | Intermittent enumeration under read load — marginal supply through adapter or controller degradation; formatting prompt the principal ongoing risk |
| Equipment used | No further insertion into the phone permitted · read attempted on a powered reader rather than through an adapter · imaged write-blocked under strict timeouts during available windows · chip-level read past the controller where enumeration failed |
The decode: what dropping out means, and the offer to avoid
What the brief appearance establishes: the card powered up, its controller initialised, and it presented a readable list of photographs. Everything up to and including reading the directory worked — which is a considerable amount, and it means the content is very likely intact.
What the disappearance means: the card stopped responding partway through. Either it lost power, or its controller failed to complete an operation and the host dropped it. Both produce exactly what she saw.
Why an adapter on a phone is the likeliest setting for it: phones manage power to accessories tightly, and an adapter adds a connection and a small voltage drop. A card near the edge of its tolerance works in a camera and fails through an adapter, because the camera supplies it directly and generously.
Why the card's age is the other candidate: long service means the controller has been managing an ageing memory for years. A controller running short of spare blocks becomes unreliable at completing operations, which presents as exactly this intermittency.
Now the urgent part, which is not technical: a phone that cannot read a card frequently offers to format it. That offer appears at the worst possible moment — after several failed attempts, when the person holding it wants any button that might help — and it is worded as repairing the card rather than erasing it.
So the instruction is simple: stop putting it in the phone. Every attempt is another mount cycle and another opportunity for that prompt, and the card is not going to behave differently on the fourth try.
What to do instead, if anything is attempted at all: a powered reader on a computer, which supplies the card properly, and one attempt at copying everything rather than browsing. The camera itself is also a better reader than a phone adapter, since it was designed for that card.
Why browsing is the wrong use of a window: if it mounts, that is an opportunity to copy, not to look. Select everything and copy it before opening anything.
On the bench
No further insertion into the phone was permitted — a host unable to read a card commonly offering to format it, worded as a repair and presented after repeated failures. Reading was attempted on a powered reader rather than through an adapter, phones managing accessory power tightly while an adapter adds a connection and a voltage drop, so a card near its tolerance fails there while working in a camera. Imaging ran write-blocked under strict timeouts during available windows.
The outcome
No further phone insertion permitted, reading attempted on a properly powered reader, and capture performed during available windows. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: the brief appearance means the card powered up, initialised and read its directory — so the content is very likely fine. It dropped out under load, which an adapter on a phone makes likely.
Card that shows briefly and then disappears
Stop putting it in the phone — a host that can't read a card will offer to format it, worded as repairing it, and that offer arrives exactly when you've tried several times and want any button that might help. The brief appearance is good news: the card powered up, its controller initialised, and it produced a readable list, so the photographs are very likely intact. It dropped out under read load, which an adapter on a phone makes likely, since phones manage accessory power tightly and an adapter adds a voltage drop where a camera supplies the card directly. If it mounts again, copy everything rather than browsing.
Keep it out of the phone — call Oxford Data Recovery on 01865 593000; read attempted on a properly powered reader, imaged under strict timeouts during available windows, read past the controller where needed.
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.