Data Recovery Case File · Cameras, Drones & Cards · The Host Failed, the Card Paid
Something Else Went Wrong and the Card Was Attached
His enquiry describes a failure that began somewhere other than the card. Transferring photographs from a memory card used as phone expansion: "the machine hung during transfer. After turning the machine off, the photos could not be viewed on phone or machine. When loading the card to the machine, the drive can be see"n but not read. The computer was the thing that failed — and the card was mid-operation when it did, which is how a working card becomes an unreadable one without anything happening to it.
| Media | microSD card used as handset expansion storage — host freezing during a file transfer from the card; card subsequently unreadable on both phone and computer |
| Reported situation | Photographs being transferred from the card to a computer · host machine freezing during the transfer · machine powered off to clear the condition · photographs no longer viewable on the phone or the computer · card visible to the computer but not readable |
| Fault class | Filesystem inconsistency from an interrupted operation and unclean removal — card content unaffected |
| Equipment used | No format or repair permitted on either device · imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · structures reconstructed on the image from surviving copies · signature carving alongside · media validated by rendering |
The decode: why a read left the card damaged
Why a transfer is not purely a read: copying from a card sounds like it should touch nothing. In practice the host updates access times, refreshes cached structures, and on removable media frequently writes small bookkeeping changes as it works. So a transfer involves writes even when nothing is being copied onto the card — which is why an interruption partway can leave structures half-updated.
What the freeze did: stopped everything mid-operation, with whatever the system had outstanding never completing. Then the machine was powered off, which is the only available response to a frozen computer and also the most abrupt possible ending for a mounted volume. The card was never closed cleanly, so it carries structures that were being modified and a flag saying it was not put away properly.
Why the phone cannot read it either: the same structures, read by a different device, reaching the same conclusion. Handsets are stricter than computers about what they will accept, so a card a computer merely fails to open may be rejected outright by a phone. Consistency across both confirms the card rather than either device.
Why the photographs are untouched: the damage is to a small structural region. Images occupy the rest of the card and nothing wrote over them — the transfer was reading them, not replacing them. What failed is the record of where they are.
Why "the drive can be seen" is the encouraging half: the card powers, enumerates and presents itself, so the hardware and controller work. That leaves a structural reconstruction, which is among the more routine outcomes here.
What must not happen: no format and no repair utility, from either device. Both will offer, and the phone in particular is likely to propose formatting the card as the way to make it usable again.
The habit worth taking from it: where a transfer matters, copy from the card and verify before doing anything else with it — and eject properly rather than pulling it out or relying on the machine being finished. A frozen computer is not something anybody can prevent, but a card that has already been copied and verified is not exposed when one happens.
On the bench
No format or repair was permitted on either device, both offering one and the handset likely to propose formatting as the route to usability. The card was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb. Structures were reconstructed on the image from their surviving copies — a transfer updating access times and bookkeeping structures even while only reading, so an interruption leaves those half-written while image content is untouched. Signature carving ran alongside and media was validated by rendering.
The outcome
The card imaged write-blocked and the structures rebuilt from their surviving copies. 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: copying from a card still involves writes — access times, cached structures and bookkeeping changes — so a host freezing mid-transfer leaves those half-updated, and powering the machine off ends it without the volume ever being closed cleanly. Your photographs were being read, not replaced.
Card that stopped working when the computer froze
Don't let either device format or repair it — the phone in particular will offer formatting as the way to make it usable again. Your photographs weren't touched. Copying from a card isn't purely a read: the host updates access times, refreshes cached structures and writes small bookkeeping changes as it works, so an interruption partway leaves those half-written. Then powering off a frozen machine, which is the only thing you can do, ends the operation without the volume ever being closed cleanly. The damage is to a small structural region while your images occupy the rest of the card. Both devices failing identically confirms the card rather than either machine, which is reassuring rather than alarming.
Don't format it — call Guildford Data Recovery on 01483 901310; imaged write-blocked, structures rebuilt from their surviving copies with carving alongside, media validated by rendering.
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.