Data Recovery Case File · Cameras, Drones & Cards · Nothing Is Just Reading
The Card Went Into Another Device
His enquiry recorded a sequence, and the sequence is the diagnosis. A microSD card used in an action camera: "I took it out, put it into an e-reader, and it started to not recognise any of the files. Putting it back into the camera, it was showing an SD card error. I then tried it in my Mac and the card does not even show." Three devices, in order, with the problem appearing after the second. This archive has said several times that a television is not a passive reader; the same is true far more widely. Almost every device you put a card into does something to it — and the ones that surprise people are the ones nobody thinks of as computers.
| Media | microSD card used in an action camera — inserted into a second consumer device, after which file recognition failed; subsequently reported as an error by the camera and not enumerated by a computer |
| Reported situation | Card functioning normally in its original device · inserted into an unrelated consumer device · files no longer recognised · camera reporting a card error · card not appearing on a computer |
| Fault class | Filing structure altered or damaged by a second device, with progression to non-enumeration — content typically intact behind unreadable structures |
| Equipment used | No further insertion attempts · write-blocked imaging (DeepSpar USB Stabilizer 10Gb) · structures reconstructed on the image · chip-level read where enumeration failed · footage validated by playback |
The decode: what other devices do, and what the sequence tells us
Why a second device is a risk: a card inserted anywhere is generally mounted, and mounting is a write-capable operation. Devices routinely write index files, thumbnail caches, system folders and metadata of their own, and many will attempt to make the card usable if they do not recognise its layout — reorganising it, adding directories, or offering to prepare or format it. Some do that with a prompt and some quietly. E-readers, televisions, printers, car head units, games consoles and photo kiosks all fall into this category, and none of them is thought of by owners as something that could damage a card.
What his particular sequence suggests: the card worked, went into an unrelated device, and stopped presenting its files. That points at the filing structure being altered or damaged rather than at the memory failing — the second device either wrote something that broke the layout the camera expects, or began preparing the card and did not finish. That is the recoverable category, and the footage sits behind it.
Why the camera then reported an error: action cameras expect a specific folder structure and a specific filesystem. Presented with something they cannot parse, they report a card error rather than explaining — and the next thing they offer is usually to format, which would replace the damaged structure with an empty one and turn a straightforward reconstruction into a carve.
Why the computer now shows nothing: the progression matters. Moving from "files not recognised" to "does not appear at all" suggests the card has deteriorated further, or that repeated insertions across three devices have taken a toll on a controller that was already struggling. Either way it means the next step is not another device.
What follows practically: stop inserting it anywhere. The elimination is already complete — three devices, three different results, none of them useful — and every further attempt powers a card that may be failing while risking a prompt somebody accepts. Where the card still enumerates it is imaged write-blocked and its structures rebuilt on the copy; where it does not, the memory is read directly at chip level.
The habit worth changing: a card holding footage should go from the camera to a computer and nowhere else. If something needs to read those files, copy them off first and give it the copy.
On the bench
No further insertion was attempted, since three devices had already established the position and each additional one risked both wear and a prompt. Where the card enumerated, it was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb and the structures examined on the copy — establishing what the second device had written or altered, and reconstructing the layout the camera had originally created. Where enumeration failed entirely, the memory was read at chip level and rebuilt in software. Every clip was validated by playing it end to end before delivery.
The outcome
The altered structures rebuilt from a write-blocked image and the footage validated by playback. 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 broke after going into something else: devices are not passive readers — mounting is write-capable, and e-readers, televisions, printers, car systems, consoles and photo kiosks all write index files, caches and folders of their own, or try to make an unfamiliar card usable; a card that worked and stopped after visiting a second device usually has an altered filing structure rather than failed memory; the camera's subsequent offer to format would replace that structure with an empty one; and stop inserting it anywhere, because the elimination is already complete.
Card that stopped working after another device read it
Stop putting it in things. Once two or three devices have failed to make sense of it, you've learned everything they can tell you, and each further insertion powers a card that may be struggling while risking a prompt somebody accepts in frustration. Understand what probably happened: nothing you insert a card into is simply reading it. Mounting is write-capable, and e-readers, televisions, printers, car head units, consoles and photo kiosks all write index files, thumbnail caches or folders of their own — and many will try to make an unfamiliar card usable, sometimes without asking. That's usually damage to the filing structure rather than to your footage. So refuse every offer to format, prepare or repair the card, on every device including the camera. And from now on, copy footage off to a computer first and give other devices the copy.
Stop inserting it — call Glasgow Data Recovery on 0141 404 0294; imaged write-blocked, the altered structure rebuilt on the copy, chip-level read where it no longer enumerates.
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.