Specialist · Samsung SSD recovery
No clatter, no beep — an SSD fails in silence. An 870 EVO in an Exeter office drops out of the BIOS mid-afternoon, a T7 stops mounting, a drive that ran for years suddenly reports 0MB. Nearly always the controller or its firmware has hung while the NAND chips still hold everything; reaching them is bench work with programmer hardware, not something an app on the same machine can manage.
Talk it over with an engineer
0800 6890668
| What's wrong | What it usually means | Step one |
|---|---|---|
| The drive vanished mid-use and won't come back | Controller lockup or worn NAND — the classic 860 and 870 EVO ending | Power off; this is bench work |
| Detected, but as 0MB capacity | The firmware has dropped into a safe state with your data intact behind it | Needs firmware-level access |
| T7 dropped, USB-C port snapped off | Damage to the connector, not the flash — the memory is usually untouched | Strong odds of recovery |
| Getting slower, files hanging, random freezes | Worn cells forcing retries — the slow-then-gone decline in its opening act | Image it before it stops reading |
| Deleted files from an SSD — recoverable? | TRIM wipes freed blocks within minutes; honest answer, often no | Stop using it, then talk to us |
| Samsung Magician says the drive is failing | Magician diagnoses — it cannot fetch data back once access has gone | Copy off now, skip the re-tests |
Your device is logged under its own case number the day it arrives. An engineer finds the fault, tells you plainly what stands a real chance of coming back, and writes you one fixed quote. Nothing is charged for that look, nothing obliges you, and paid work starts only when you say so.
The drive comes off USB and onto native SATA or NVMe rigs where the controller can be questioned directly — telling locked firmware from worn NAND from a broken connector, distinctions an ordinary PC cannot make.
Firmware faults are worked around in the controller's service mode; where that fails, the NAND is read chip by chip and reassembled. A hardware-encrypted T-series needs its password — without it, no lab reads anything.
Once access exists it may not last, so imaging runs gently: cool, short sessions, weak cells revisited with patience, and the freshest copy banked at every stage before the drive is asked for more.
Before any fee falls due you see a full listing of everything recovered and approve it. Your files travel back on brand-new media, return postage on us, and the case stays open until you've confirmed everything opens on your own machine.
Why Samsung failures run to a pattern: these are good drives, which is why so many arrive holding the only copy — owners trusted them and skipped the backup. The endings we see are two: NAND worn until the firmware can no longer juggle it, and controllers that lock up without notice. Both leave chips full of data the computer cannot see, so nothing you install will help — there is no visible drive to point it at. Access comes from beneath: service-mode commands, controller work, or the NAND read raw.
It had run faultlessly for years, then one morning the laptop booted to a missing drive. On the bench rig the controller answered service-mode commands, the firmware lockup was stepped around, and the flash was imaged in short, cool sessions — slower where cells were weak. The bookkeeping came back complete, folders and filenames intact.
Almost always the controller or its firmware has hung — the classic ending for an 860 or 870 EVO. The drive stops answering, so the BIOS lists nothing, yet the NAND chips behind the controller still hold your files. No app can scan a drive the machine cannot see; access is reopened at the bench through service-mode commands or, failing that, by reading the chips directly. Power it off and leave it off.
Usually everything. A Samsung showing 0MB has dropped into a safe state: the firmware hit a fault mid-housekeeping and now boots just far enough to give its name, with no capacity behind it. Your data sits intact beyond that barrier. Formatting, initialising or re-flashing at this point only stacks new damage on old — what the drive needs is firmware-level access on a bench rig, and as failures go the odds here are usually good.
With the password, yes. The encryption is done in the drive's own hardware, and once the fault — typically a snapped USB-C port or a locked controller — has been dealt with, your password opens the data exactly as before. Without it, no, and that is true of every lab in the country: there is no back door in these portables. Dig the password out before you post the drive, and tell us if one was never set.
No — and it doesn't claim to. Magician reads drive health, runs benchmarks and applies firmware updates; it has no recovery function at all. Worse, the two things it can do to a struggling drive — stress it with tests and re-flash its firmware — are exactly what a struggling drive should be spared. If Magician is showing warnings, copy off whatever still opens, then power down and let a bench take over.
Each power-up of a failing device takes more data with it. Open a case first — the look-over is free whichever way it goes.