Data Recovery Case File · Cameras, Drones & Cards · It Is Preserving What Is There
A Protective State, Not a Fault
This enquiry describes a card doing something deliberate. A phone giving "notification to say that the card is read only, all photos and videos no longer showing and the card not recognised. Tried it in a different phone — the card was recognised but said it needed to be formatted to work. Did not complete the action as it also said it would erase the data. Nothing backed up." Declining that format was exactly right. And read-only is not the card breaking — it is the card deciding to stop writing before it damages anything, which is the most useful thing it could have done.
| Media | SD card reported as read-only by its host handset — contents not listing; recognised by a second device with a format prompted and declined; no backup held |
| Reported situation | Host phone notifying that the card had become read-only · photographs and video no longer showing · card not recognised by the original phone thereafter · card recognised by a second phone · format prompted and correctly declined · no backup held |
| Fault class | Controller-initiated read-only mode following write-reliability threshold — content preserved and protected from overwrite; media at end of service life |
| Equipment used | Format declined and card removed from use · read-only state confirmed as controller-initiated rather than a physical lock · imaged write-blocked with per-block timeouts (DeepSpar USB Stabilizer 10Gb) · structures reconstructed on the image · media validated by rendering |
The decode: what read-only means, and why it is good news
What a flash controller does when it can no longer write safely: it stops. Every card manages a pool of spare blocks used to replace ones that wear out, and it tracks error rates as it goes. When the spares are exhausted, or the error rate crosses an internal threshold, many controllers switch the whole device permanently to read-only. That is a designed response, not a malfunction — the controller has concluded that any further writing risks corrupting what is already there, and has chosen preservation over continued use.
Why that is the best possible position to be in: the contents are intact and, from this moment, cannot be overwritten by anything. Every other case in this archive turns on the race between recovery and something writing to the media. Here the card itself has taken that risk off the table. Nothing you do can now damage the data by accident, which is a genuinely unusual protection.
Why the photographs stopped showing: the transition to read-only frequently happens partway through normal operation, when the device was updating its filing structures. Those updates cannot complete on a read-only device, so the structures are left inconsistent and the host cannot list the contents — while the image data sits untouched underneath.
Why the second phone offered a format: it found a volume it could not interpret and proposed the only remedy it has. It would very likely have failed anyway, since the card will not accept writes — but the offer should be declined regardless, and it was.
What must not be attempted: the various suggestions found online for "removing" read-only status. Some address a physical lock switch on full-size cards, which is a different thing entirely. Others involve low-level commands intended to force a controller out of the state — and where the controller entered it because it can no longer write reliably, forcing writes is precisely what it was protecting against.
Why this is nevertheless urgent: read-only is the state before unreadable. The condition that triggered it is degradation, and degradation continues. The card should be imaged now rather than left in a drawer on the basis that it is safe — it is safe from overwriting, not from further decline.
What happens to the card afterwards: nothing. It has reached the end of its service life and should not be reused even if a format later appears to succeed.
On the bench
The format was declined and the card removed from use. The read-only state was confirmed as controller-initiated rather than a physical lock, the two being unrelated and only one indicating end of service life. The card was imaged write-blocked with per-block timeouts behind the DeepSpar USB Stabilizer 10Gb — the same degradation that triggered read-only mode producing marginal blocks that frequently succeed on a later pass. Structures were reconstructed on the image and media validated by rendering.
The outcome
The read-only state confirmed as protective, the card imaged with marginal blocks re-read and the structures rebuilt. 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: read-only is a decision, not a fault. When a card exhausts its spare blocks or crosses an internal error threshold, the controller switches the whole device to read-only rather than risk corrupting what is there. Your photographs are intact and now cannot be overwritten by anything — but the underlying degradation continues, so act now.
Card that has become read-only
Refuse the format and don't try any of the methods you'll find online for removing read-only status — some address a physical lock switch, which is a different thing, and others force a controller out of a state it entered deliberately. Your card made a decision. Every card keeps spare blocks to replace worn ones and tracks its own error rate, and when the spares run out or errors cross a threshold, the controller switches to read-only permanently rather than risk corrupting what's already stored. So your photographs are intact and, unusually, can no longer be overwritten by anything — that risk is off the table. But the degradation that triggered it continues, and read-only is the state before unreadable, so don't leave it in a drawer.
Don't force it — call Guildford Data Recovery on 01483 901310; read-only confirmed as controller-initiated, imaged write-blocked with marginal blocks re-read, structures rebuilt on the copy.
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.