Data Recovery Case File · Cameras, Drones & Cards · Alternating Means Intermittent
Two Different Messages From One Card
Her enquiry reported both errors rather than picking one, which turns out to be the useful thing to have done. A card in a phone that "suddenly stopped working, and the phone either says card not inserted or card corrupted. I have removed and re-inserted several times and no change. I tried it in a card reader on my laptop and it shows nothing there." Around three hundred photographs are on it. Those two messages describe different failures, and a device producing both on different attempts is telling you something quite specific about what is going wrong.
| Media | microSD card from a mobile handset — host reporting the card alternately as absent and as unreadable; not presenting in a separate card reader; approximately 300 photographs held |
| Reported situation | Card in normal use in a phone · function lost abruptly · host reporting card not inserted on some attempts and card corrupted on others · repeated removal and reinsertion without change · card not presenting in a laptop card reader · approximately 300 photographs held |
| Fault class | Intermittent enumeration — controller failing to complete initialisation reliably; memory readable independently of the controller |
| 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 · recovered count reconciled against the stated total · photographs validated by rendering |
The decode: what each message means, and what alternating tells us
Card not inserted: the device has not detected a card at all. The introduction never began — no response to power, no identification, nothing on the bus. As far as the phone is concerned the slot is empty.
Card corrupted: a quite different statement. The device has detected a card, it has completed the introduction, and it has read far enough to find filing structures it cannot make sense of. That is a card that announced itself successfully and then failed at a later stage.
Why getting both matters: a card producing one consistently has a stable fault. Hers alternates, which means the introduction sometimes completes and sometimes does not — intermittent enumeration. That points at the controller rather than at the stored data: the chip that conducts the introduction and manages the memory is failing to initialise reliably, succeeding on some attempts and not others. When it succeeds, the phone gets far enough to complain about the contents; when it fails, the phone sees nothing.
Why the reader showing nothing fits: a second host with the same result confirms the card rather than the phone, which is a useful elimination she performed without being asked. It also suggests the intermittency is worsening.
Why the repeated reinsertion is the thing to stop: two reasons, and this is the practical advice. Each insertion is a power cycle applied to a controller that is already failing to start — and each is physical wear on contacts that are thin gold plating over a small area. Cards are rated for a limited number of insertions in normal use, and a card being tried repeatedly in hope is being worn on top of whatever is already wrong. The elimination is complete after two devices; there is nothing further to learn.
Why the photographs are probably fine: the failure is in the controller, not the memory holding the images. The route past it is to read the memory directly through the card's internal test points and reconstruct in software — descrambled, error-corrected and rebuilt through the translation layer until the filing structures stand up.
Why the count helps: knowing roughly three hundred gives a figure to reconcile the result against, which turns a plausible-looking recovery into a verified one.
On the bench
No further insertion was attempted, since two hosts had established the position and each attempt is both a power cycle on a failing controller and physical wear on the contacts. Enumeration was attempted write-blocked behind the DeepSpar USB Stabilizer 10Gb under strict timeouts, establishing which stage of initialisation was failing and how consistently. Where the controller could not be brought up reliably, the memory was read at chip level past it and reconstructed in software. The recovered count was reconciled against the owner's stated total, and photographs validated by rendering.
The outcome
The failure point established under timeout control, the memory read past the controller and the recovered count reconciled against the stated total. 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 getting two different errors from one card: they describe different failures. Not inserted means no card was detected at all; corrupted means one was detected and its contents could not be read. Getting both on different attempts means the introduction sometimes completes and sometimes does not, which points at the controller rather than your photographs. Stop reinserting it — each attempt is a power cycle and physical wear.
Card giving different errors on different attempts
Stop taking it out and putting it back in — that's doing real harm now. Each insertion is a power cycle applied to a controller that's already failing to start, and it's physical wear on contacts that are thin plating over a very small area. Report both messages though, because together they're informative. Card not inserted means the device detected nothing at all, so the introduction never began. Card corrupted means it did detect the card, completed the introduction, and then couldn't make sense of what it read. Getting both on different attempts means the introduction is succeeding sometimes and failing others, which points at the card's controller rather than your photographs. Trying a second device was the right elimination. Say roughly how many photographs there were, too.
Stop reinserting it — call Newcastle Data Recovery on 0191 406 1051; enumeration read under strict timeouts, memory read at chip level past the controller, recovered count reconciled against your total.
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.