Home / Case Studies / Solid State & Flash
Solid State & Flash · case file

A RAW Card in One Phone, a Bricked Phone Beside It

She has two problems and hopes for one answer. The photos on the microSD card in her Samsung Galaxy "have disappeared", her laptop "showing it as a RAW SD card" — it "was working yesterday" before the gallery emptied. And separately, an older Samsung "which appears to be completely bricked", from which she also wants photos. These are two distinct recoveries needing two different methods — a logical fault on a memory card, and a dead phone with its photos on sealed internal storage — and separating them is the first step, because what works for one does not apply to the other.

Memory CardPhone / TabletCorruption / FilesystemDead / No Power
// case at a glance
MediaA microSD card from a Samsung Galaxy showing as RAW after its photos vanished · a separate older Samsung phone, bricked and unresponsive, with photos on internal storage — two independent devices
Reported situationCard working the previous day, gallery photos then disappeared · laptop now reporting the card as RAW · a second, older Samsung phone completely bricked · photographs wanted from both · the two faults unrelated beyond both being Samsung devices
Fault classTwo separate faults — filesystem corruption on the microSD card, recoverable behind a lost structure, and a non-functioning phone whose internal storage location and encryption govern what is possible
Equipment usedmicroSD imaged under a hardware write-blocker, structures parsed in R-Studio and carved in PhotoRec, card health checked · bricked phone assessed on a current-monitored bench supply for power and life, board inspected under stereo microscope · boot or storage access re-established where the fault allows, or chip-level examination on the phone's generation subject to internal encryption · all recovered photographs validated by rendering, both results delivered together
// the decode

The decode

The card and the phone are unrelated faults, and treating them separately is essential. They share only the Samsung name. The card is a memory card with a logical problem; the bricked phone is a dead device with its data on internal storage. Each needs its own diagnosis and its own method, and the prognosis for one says nothing about the other — so they are assessed as two cases delivered in one report.

The card showing as RAW, one day after working, is classic recoverable corruption. RAW means the laptop can no longer read the card's filesystem, so it reports no format — but the photos sit intact behind the damaged structures. That the gallery emptied and the card went RAW between one day and the next describes structural corruption, not vanished data. Recovery rebuilds the structures from their backup copies where possible and carves the images from the data area otherwise, and the outlook for the card's photos is good.

The one card risk to flag is the laptop's likely format prompt. A RAW card prompts a format offer, and accepting would write empty structures over the recoverable photos. As with any RAW media, that prompt is declined, and all work is done on a write-blocked image so nothing writes to a card whose structures are already damaged.

The bricked phone is the harder and more variable case, and honesty about it comes first. "Completely bricked" covers a range — a software failure that stops it booting, a power fault, or deeper board damage. The photos are on internal storage, which is sealed inside the device, so reaching them is not as simple as removing a card. The realistic outcome depends on why the phone is dead and on the phone's generation.

Two things decide the phone's prognosis, and both are established by assessment. First, the nature of the fault — a phone that can be revived, or whose storage access can be restored, offers a direct route; deeper board damage is harder. Second, encryption: modern phones encrypt internal storage against the passcode, so even chip-level access can yield sealed data without the code. An older Samsung may fall on the more accessible side of that line, which is checked rather than assumed. Where encryption applies, her knowing the passcode matters.

The honest split is stated per device before any work. The card's photos are likely recoverable; the bricked phone's depend on its specific fault and generation, and that is assessed and reported plainly — two verdicts, delivered together, neither promised on the strength of the other.

// on the bench

On the bench

The microSD was imaged under a hardware write-blocker, its structures parsed in R-Studio and carved in PhotoRec, and the card's health checked. The bricked phone was assessed on a current-monitored bench supply for power and life, its board inspected under stereo microscope, and boot or storage access re-established where the fault allowed, or chip-level examination attempted on the phone's generation subject to internal encryption. All recovered photographs were validated by rendering, both results delivered together.

// the outcome

The outcome

Two separate recoveries — the RAW card rebuilt and carved, the bricked phone assessed and accessed as its fault allowed. The assessment is free and the quote is a single fixed figure inclusive of VAT; if the data cannot be recovered, there is nothing to pay. The decode: the card and the phone are different problems with different answers. The RAW card's photos sit intact behind a lost structure and recover well; the bricked phone depends on why it died and whether its storage is encrypted — assessed honestly, not assumed from the card's good news.

A RAW memory card and a separately dead phone

For the card, don't accept the format prompt and stop reinserting it — RAW means a lost filesystem with the photos intact behind it, recoverable from an image. For the bricked phone, don't keep force-restarting it or let anyone factory reset it, and note your passcode, because modern phones encrypt internal storage and reaching those photos may depend on it. Treat the two as separate recoveries with separate outlooks — the card's good prognosis says nothing about the phone's.

Sending this in from Staines? Every case starts with a free diagnostic and one fixed written quote before any work — no fix, no fee. If the data is inside a laptop, PC, Mac or server, remove the hard drive or SSD and send us just the drive; we don’t provide an internal drive-removal service, and we don’t recover storage soldered to a motherboard (e.g. Apple Silicon Macs) — only drives that can be removed and sent to us. Post or courier tracked and insured to our Guildford Data Recovery lab — full sending instructions and the shipping form are here.
Start a free diagnostic

Our case files are written up from genuine enquiries our lab has handled for customers across Staines, Surrey and the surrounding area, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.

// related case files

More cases like this one

Browse all case studies →

Got a device with a story like this?

Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.