Data Recovery Case File · Solid State & Flash · The Upgrade Is the Full Read
People Upgrade Old Storage, and Old Storage Fails When Read Completely
His enquiry describes a favour that went wrong. A small card holding around six gigabytes that came out of somebody's phone, which he was "asked to copy the contents across to a larger card" — and which is now not recognised at all. The two facts in that sentence are connected. Cards get upgraded because they are old and full, and old cards fail when something finally reads all of them.
| Media | 8GB microSD card from a mobile phone holding approximately 6GB — not enumerating; failure occurring in the context of a capacity migration undertaken on the owner's behalf |
| Reported situation | Card removed from a phone by a third party at the owner's request · migration to a larger card intended · card not recognised by the computer at all · approximately 6GB of content held · content required on the owner's behalf |
| Fault class | Controller failure on aged media surfaced by migration read load — content unaffected by controller state; custodial notification indicated |
| Equipment used | Owner notified before any commitment · device addressed through hardware with imposed timeouts rather than the host stack · chip-level read past the controller with translation layer reconstructed in software · output delivered to the owner directly |
The decode: why upgrades and failures arrive together
Why somebody asks for a card to be upgraded: it is full, and it is full because it has been in use for years. The decision to move to a larger card is itself evidence of a long service life, which is the condition under which flash controllers run out of the spare blocks they use to replace worn ones.
What a migration asks of a card: a complete read. Every file, every region, in sequence — which for most cards is the first time in their lives that everything has been asked for at once. Ordinary phone use reads a small fraction repeatedly.
So the two are not coincidental: the card was old enough to be worth upgrading, and the upgrade was the first full read it had faced. The failure was arrived at rather than caused, and it would have surfaced eventually whether or not anybody had tried to copy it.
Why that matters to him particularly: he did somebody a favour and their card failed in his hands. The natural reading is that he broke it, and the natural response is to try to fix it quietly before saying anything. Neither is right.
What to do first, and it is not technical: tell the owner. They may have the photographs elsewhere — synchronised to an account, copied to a computer, or shared — and only they can answer that. The question takes a minute and may end the situation.
Why the decisions belong to them: whether to commission a recovery and what to spend are theirs, not his. Making those choices on somebody's behalf, however well meant, takes a decision that is not his to take.
Now the technical position, which is more hopeful than total non-recognition sounds: a card that will not enumerate has a controller that cannot complete its start-up. The memory holding the photographs is a separate component and is unaffected by that — the failure is in the part that speaks for the storage, not the storage.
What the route is: the memory read directly at chip level, past the controller entirely, with the pattern by which it distributed data reconstructed in software.
What must not happen: no formatting, no repair tools, and no further insertion attempts.
On the bench
The owner was notified before any commitment — content potentially existing elsewhere in accounts or copies that only the owner can confirm, and decisions regarding expenditure belonging to them. The device was addressed through hardware with imposed timeouts rather than the host stack, a controller unable to complete initialisation leaving the memory itself unaffected, with chip-level reading past the controller and the translation layer reconstructed in software.
The outcome
The owner notified before any commitment, the device addressed through hardware, and the memory read past the controller. 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 upgrade and the failure are connected. A card gets replaced because it is old and full, and a migration is the first complete read of its life — so the fault was arrived at rather than caused.
Somebody else's storage that failed while you were helping
Tell them today rather than trying to fix it first — they may have the photographs in an account or on a computer, which only they can confirm, and the decisions about what to spend are theirs. You almost certainly didn't break it either. People upgrade a card because it's old and full, and a migration is the first time in that card's life that everything on it gets read at once, where ordinary use reads a small fraction repeatedly. So the failure was arrived at rather than caused, and it would have surfaced eventually. A card that won't enumerate has a controller problem, not a memory problem.
Tell them first — then call Easy Data Recovery on 028 9002 0144; addressed through hardware with imposed timeouts, memory read past the controller, output delivered to the owner directly.
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.