Data Recovery Case File · Cameras, Drones & Cards · What Can Be Said in Advance
Some of the Answer Is Available Before the Card Arrives, and Some Is Not
His enquiry asks the reasonable question that precedes every commitment. A memory card used in a phone for photographs which "has stopped reading and will not detect in the phone or my laptop or computer" — followed by: do you think you have a chance, and if so I will send it. Part of that is answerable from the description alone, and being clear about which part is which is more useful than an encouraging guess.
| Media | 128GB memory card used in a phone for photographic storage — not detected in the phone, a laptop or a desktop computer |
| Reported situation | Memory card used in a phone for photographs · card no longer reading · not detected in the phone · not detected in a laptop · not detected in a desktop computer · owner seeking an indication of prospects before sending |
| Fault class | Card not completing enumeration across all hosts — controller failure indicated; memory condition not determinable without assessment |
| Equipment used | Determinable and indeterminable elements separated before any estimate of prospects · card addressed through hardware with imposed timeouts rather than the host stack · controller state assessed in vendor technological modes · memory read past the controller where indicated · translation layer reconstructed in software |
The decode: what the description settles, and what it cannot
What his three tests already establish: the fault is in the card. A phone, a laptop and a desktop are three separate readers with separate hardware and separate software, and identical behaviour across all of them removes every external explanation without anyone needing to see it.
What that narrows the fault to: the controller. A card must announce itself before any host can list it, and one that appears nowhere is not completing that introduction — which is a specific finding rather than a general failure.
Why that is a hopeful class of fault: the controller is the part that manages and presents the storage, and it is separate from the memory holding the photographs. Controller failure with intact memory is the commonest reason cards arrive here and the commonest reason they leave with their contents.
What genuinely cannot be known in advance: the condition of the memory itself. Whether the memory can be read past a failed controller depends on the card's internal construction and on whether the memory was damaged alongside it — and neither is visible from outside.
Why the construction matters so much: some cards keep the memory as a component that can be addressed independently, and others build the controller and memory into a single package. The second is harder and slower and is not predictable from the outside of the card.
So the honest answer in two parts: the fault class is favourable and common, and the outcome within that class varies. An assessment costs nothing and converts the general answer into a specific one, which is the only way the second half of his question gets answered.
Why an encouraging guess would be worse than this: it would be a statement about the category dressed up as a statement about his card. The category is genuinely promising, and that is not the same as a prediction — and someone deciding whether to commit deserves the distinction.
What is worth knowing about the content type: photographs are among the more recoverable material, with recognisable openings that allow them to be found without any directory. A card of that capacity used in a phone will hold them in large, mostly continuous runs.
What must not happen while he decides: no further insertion attempts, no formatting if a device offers, and no recovery software run against it. The card should be set aside as it is.
On the bench
Determinable and indeterminable elements were separated before any estimate of prospects — three independent hosts failing identically establishing that the fault travels with the card and that enumeration is not being completed, which places it at the controller, while the condition of the memory and the card's internal construction are not observable externally and govern whether reading past the controller succeeds. The card was addressed through hardware with imposed timeouts, with memory read past the controller where indicated.
The outcome
The knowable separated from the unknowable before any estimate, the card addressed through hardware, and the memory read past the controller. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: your three tests already proved the fault is in the card and that it is not completing its introduction, which is a common and favourable class. What cannot be said in advance is the state of the memory behind it.
Asking whether it is worth sending
Expect an answer in two parts, and be wary of one that is only encouraging. If a card fails identically in three different readers you have already proved the fault travels with it and that it isn't completing its introduction to any host — that points at the controller, which is separate from the memory holding your photographs and is the commonest recoverable case there is. What genuinely can't be judged from a description is the state of that memory, or whether the card is built with the memory as a separate component or fused with the controller. An assessment costs nothing and is what turns the general answer into yours.
Set the card aside — call Easy Data Recovery on 028 9002 0144; knowable separated from unknowable before any estimate, addressed through hardware with imposed timeouts, memory read past the controller.
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.