Data Recovery Case File · Cameras, Drones & Cards · The Card Was Protecting Itself
Read-Only Is Not a Fault, It Is the Last Warning
His enquiry contains a message that arrived before the failure and was not recognised as one. A 64GB card that was in his phone: "I received a message on my phone saying that it has turned to read only. When I looked it wouldn't recognise my card. I put the card into another phone and it recognised" it. A card that reports itself read-only has made a deliberate decision — it has concluded it can no longer write safely, and it is preserving what it holds.
| Media | 64GB microSD card from a mobile device — controller entering write-protected state before ceasing to enumerate reliably; photographic content held |
| Reported situation | Card in use within a phone · host reporting the card had become read-only · card subsequently not recognised by that phone · card recognised when inserted into a second phone · photographic content required |
| Fault class | Controller write-protection following spare block exhaustion or critical error — intermittent enumeration indicating further deterioration; content preserved at the point of lock |
| Equipment used | Read-only state interpreted as a deliberate protective mode · no write attempts or formatting permitted at any point · imaged write-blocked under strict timeouts during available windows · chip-level read past the controller where enumeration failed |
The decode: what the card decided, and why it told him
What a flash controller does when it runs out of room to work: every card holds spare blocks in reserve, used to replace blocks that wear out. When that reserve is exhausted, the controller can no longer guarantee that a write will land somewhere reliable — and rather than write anyway, it locks the device.
Why locking is the right decision: a write that cannot be placed safely risks corrupting the structures describing everything else. By refusing to write, the controller freezes the card in its last known good state and preserves what is on it. That is protection, not failure.
So what the message actually meant: copy everything off now. It is the clearest warning any storage device is capable of giving, and it is almost universally read as an annoyance or a phone problem rather than a final notice.
Why nobody recognises it: the wording is technical and the phone offers no explanation. Nothing says "this card is at the end of its life" — it says the card is read-only, which sounds like a setting.
Why cards in phones reach this point: continuous small writes. Applications, caches, thumbnails, logs and message attachments write constantly, which is a far heavier workload than a camera card sees, and it consumes the spare block reserve steadily over months.
What his subsequent symptoms mean: the original phone stopped recognising it and a second phone did. That is intermittent enumeration, which suggests the controller has deteriorated further since the lock — so the window in which it responds at all is now limited and unpredictable.
Why every remaining window must be spent on capture: the card is readable sometimes. Those occasions are the resource, and testing it in successive phones to see whether today is better spends them on nothing.
What must not happen under any circumstances: no formatting, and no attempt to remove the write protection. Tools exist claiming to clear a read-only state, and on a card that locked itself for cause, forcing writes onto exhausted memory is the fastest route to losing everything it was protecting.
On the bench
The read-only state was interpreted as a deliberate protective mode — flash controllers holding spare blocks in reserve to replace worn ones and locking the device when that reserve is exhausted, since a write that cannot be placed reliably risks the structures describing everything else. No write attempts or formatting were permitted at any point. Imaging ran write-blocked under strict timeouts during available windows, with chip-level reading past the controller where enumeration failed.
The outcome
The read-only state read as protection, no writes permitted, and capture performed during available windows. 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: your card made a decision and told you about it. When the spare blocks it uses to replace worn ones run out, a controller locks the device rather than writing somewhere unreliable — which preserves what is there. That message meant copy everything now.
Card or drive that reports itself read-only
Copy everything off immediately — that message is the clearest warning storage is capable of giving, and it's almost always read as a setting or a phone problem. Flash devices hold spare blocks in reserve to replace worn ones, and when that reserve runs out the controller can no longer guarantee a write will land safely, so it locks the device rather than risking the structures describing everything else. That's protection, and it freezes the card in its last good state. Never format it or use a tool claiming to clear write protection — forcing writes onto exhausted memory loses exactly what the lock was preserving.
Don't format it — call Oxford Data Recovery on 01865 593000; read-only state read as protection, no writes permitted, capture performed during available windows and past the controller where needed.
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.