Data Recovery Case File · Cameras, Drones & Cards · The Accessory Is a Component
It Showed Up for a Second and Then Went
Her enquiry traces the failure to a moment and names the likely culprit without quite realising it. A camera card that will no longer read: "I think this is because I used a reader I got online to transfer everything to my phone. Everything showed up on my phone for a second, it then glitched and went away — when I took the card out to insert into the camera, the camera couldn't access it." Working, then a glitch during transfer, then unreadable everywhere. The reader is not an innocent bystander in that sequence, and what happened during that second is worth understanding.
| Media | SD card from a digital camera — contents briefly presented during a transfer through an inexpensive card reader, then lost; card subsequently unreadable in the camera |
| Reported situation | Card in normal use in a camera · transfer to a phone attempted through a low-cost card reader · contents appearing briefly then disappearing during the transfer · card not readable in the camera afterwards · content required |
| Fault class | Failure during transfer with the reader implicated — structure damage or controller instability following an interrupted operation |
| Equipment used | Reader eliminated and not reused · card imaged write-blocked on qualified equipment (DeepSpar USB Stabilizer 10Gb) · structures reconstructed on the image · format-aware carving alongside · images validated by rendering |
The decode: what a reader can do, and what the glitch was
Why a card reader is a real component: it is not a passive adapter. It contains a controller that negotiates with the card, supplies its power, and translates between the card's protocol and USB. Inexpensive readers vary enormously in quality, and the common failings are specific: insufficient or unstable power delivery, which is hardest on a card during sustained reading; poor contact in cheaply made slots; and protocol handling that works for small transfers and falls over on large ones.
What probably happened in that second: the phone enumerated the card through the reader, read enough to list the contents — which is why everything appeared — and then the connection failed partway. If the card was being written to at that moment, which is likely because import processes and media indexing update structures as they go, the interruption leaves the filing structures inconsistent. That produces a card readable a moment earlier and unreadable afterwards, on every device.
Why the camera then could not access it: the camera reads the same structures and finds them incoherent. It is not a second fault; it is the same one seen from another device, and the consistency across devices is what confirms the card rather than the reader as the current problem.
Why the reader still matters: because it should not be used again — not on this card and not on a replacement. If it delivered unstable power or lost the connection under load once, it will do it again, and the next casualty is usually a fresh card containing something new. A reader that fails mid-transfer has told you what it is.
The practical point about phones and readers generally: transferring a full card to a phone through an adapter is the most demanding thing that combination will ever do — sustained reading, a phone supplying the power, and a large volume of data. A computer with a decent built-in slot is a far more reliable route, and where a transfer matters it is the one to use.
Why the outlook is reasonable: an interrupted write damages structures rather than content. The images sit where they were written, and filesystems keep backup copies of their key structures at known positions, so a rebuild frequently returns everything with original names and shooting sequence.
What not to do: no format, from the camera or a computer, and nothing further written to the card.
On the bench
The reader was eliminated and not reused, since one that lost a connection under sustained load will do so again and the next card is usually the casualty. The card was imaged write-blocked on qualified equipment behind the DeepSpar USB Stabilizer 10Gb, which supplies controlled power rather than whatever an accessory provides. Structures were reconstructed on the image from their surviving backup copies, with format-aware carving alongside, and images validated by rendering.
The outcome
The reader eliminated, the card imaged on controlled equipment and the structures rebuilt and validated. 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, for anyone whose card failed during a transfer: the reader is a component, not a wire. It has its own controller, supplies the card's power, and inexpensive ones commonly deliver unstable power or lose the connection under sustained load — which interrupts writes and leaves filing structures inconsistent. Don't use that reader again, on this card or a replacement.
Card that failed while transferring through a reader
Don't use that reader again — not on this card and not on a new one. A card reader isn't a passive adapter: it has its own controller, it supplies the card's power, and cheap ones commonly deliver unstable power, make poor contact, or handle large transfers badly. If it dropped the connection once under sustained load it will do so again, and the next casualty is usually a fresh card with something new on it. What likely happened is that the connection failed partway while the card was being written to, which leaves the filing structures inconsistent — readable one moment and not the next, on every device. Your images sit where they were written. Don't format it, and for transfers that matter use a computer's built-in slot rather than a phone and an adapter.
Retire that reader — call Newcastle Data Recovery on 0191 406 1051; imaged write-blocked on controlled equipment, structures rebuilt from their backup copies, images 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.