Solid state drives fail without any warning noise, and that is the part people find hardest to take. Working on Thursday, invisible on Friday, with nothing in between to give notice. SSD hard drive recovery is a separate trade from disk work altogether — no platters, no heads, no clean bench — and it goes on daily for households, the labs at Norwich Research Park and the offices along the A11 corridor.
Every ssd job is diagnosed free. The quote follows in writing, fixed, before a screwdriver is picked up.
No fix, no fee all jobs except electronic and mechanical failures, chip level work, DVR and Forensic jobs. Full pricing is on the data recovery cost page.
The first job on any ssd is matching the symptom to the fault — and after twenty-odd years, these thirty account for very nearly everything that comes through the door.
The management chip resigns and the drive vanishes from the bus, every file still sitting in the NAND behind it. What is missing is something to speak on the memory's behalf, and that is precisely what a firmware bench provides.
That name is a Phison controller stuck in its own boot loader rather than a drive called anything of the sort. The files are untouched behind the wrong label, and service-mode work walks them out.
Translator failure. The drive stays polite and reports a size that belongs to nobody. Rebuilt in service mode, then imaged in full before it is asked to do another thing.
Boot code, power rail or controller, and all three look identical from the outside: nothing on the screen. Separating them takes a bench, and it is the first thing the free diagnostic settles.
End-of-life protection has frozen writes to preserve what is there. Inconvenient at a desk; on an imaging rig it is close to a gift, because the drive cannot make matters worse while we copy it.
Flash does not usually send notice. It is fine on Friday and absent on Monday, which is why so many calls to this workshop begin with somebody saying it was working perfectly the last time they used it.
An interruption mid-write scrambles the translation tables that turn logical addresses into physical ones. A genuine surge takes the power stages with it. Both arrive here regularly and both are bench work.
Tired NAND reads back differently from one pass to the next while SMART mutters about it quietly. The first complete image is the only account worth trusting, so it is taken carefully and taken once.
Deleted blocks get erased in the background whenever the drive has power. Unplug it and the countdown stops. Leave it connected while you think about it and the thinking costs you files.
Thin boards lose arguments with screwdrivers, upgrade attempts and stiff envelopes. Track repair covers a clean break near the edge; anything worse goes to chip-off, which is slower and works just as well.
Samsung's MZ-76E500 and its siblings are among the commonest SSDs in British desktops and laptops, so we see the full range of how they end. The signature version is abrupt: the drive drops off the SATA bus mid-session, comes back as a tiny capacity or not at all, and no amount of re-cabling changes it. The MJX controller has lost its translator, the V-NAND behind it is intact, and service-mode work followed by a full image is the route back. Owners who keep the power off it from the moment it first stumbles get the best outcome, every time.
First-run examples of the MZ-77E1T0 were documented reallocating sectors at a rate that had Samsung issuing a firmware update. Unpatched drives still arrive. The memory reads; the map is what needs rebuilding.
Crucial's MX500 has a well-known habit of reporting a rising pending-sector figure that alarms owners more than it should — until the day it is genuinely accompanied by read failures. Telling the harmless version from the real one is a bench job, not a guessing game.
WD's SATA Blue has a documented tendency to disappear until firmware attention is applied. Familiar patient, familiar route, and the NAND is rarely the problem.
The A400 SA400S37 and its relatives shrink to a few megabytes or vanish outright when the translator corrupts. Service-mode territory, and the flash underneath is usually blameless.
These lock up partway through a write and then decline all further conversation. Some wake in service mode; the ones that will not are read at chip level instead.
SSUBX and SSPOLARIS blades from 2013 to 2017 machines fail like any other SSD and image here on native adapters. No donor Mac is involved at any point, which surprises people.
No DRAM cache means clumsy wear-levelling, and a BX500 given a heavy workload gets old before its time. The chips come off and the data comes out.
Marketplace fakes loop their writes over a sliver of genuine flash. Everything that landed inside the real capacity is recoverable; everything written after the wrap-around was never stored anywhere at all.
The plastic tongue shears during a routine swap and takes a few pads with it. Board-level repair, and afterwards it behaves as though the accident had never happened.
Years of heavy writing exhaust the rated life and the drive locks up or reads unpredictably. There is budget for one imaging attempt, so it gets planned like one rather than started hopefully.
The manufacturer's utility stopped halfway and left a drive that cannot say its own name. It is either reflashed on the bench or bypassed entirely, depending on what the controller still has to say for itself.
QLC flash runs quickly until the fast cache is used up, then slows to a fraction of the speed. Owners assume a hang and pull the lead, and it is the pulling that does the damage rather than the slowdown.
Reading a block repeatedly nudges the charge in its neighbours. On a drive holding archives that are read often and rewritten never, the errors quietly accumulate until ECC can no longer cover them. Slow, patient re-reads recover far more than one confident pass.
Cells leak while unpowered. A drive last used in 2019 can read back as noise. Repeated-read imaging with ECC patience returns a great deal of what a single quick pass would have written off.
Seasons of warming and cooling fatigue the BGA joints under the controller and the memory packages. Rework restores contact for long enough to take a clean image, which is all it needs to do.
Enterprise and datacentre SATA units carry capacitors that hold the drive up long enough to flush its buffers when the power goes. Those capacitors age. When they have quietly failed, the next power cut takes the mapping tables with it, and nobody knew the safety net had gone.
Nearly every modern SSD encrypts as it writes, whether or not the owner asked for it, with the key held in the controller. Corrupt that key store and the memory is perfectly readable and completely meaningless. We say so plainly rather than selling hope.
More than one maker has shipped code that stops the drive dead at a set number of power-on hours. The hour arrives, the drive does not. Repaired in service mode and imaged straight afterwards.
A glitched security state locks a self-encrypting drive shut. The PSID printed on its label reverts it by wiping everything, which is the opposite of what anybody wants. So we do not use it, and neither should anyone else.
An SSD does not keep your files where the computer believes they are. Wear levelling scatters them across the NAND packages as the controller sees fit, and the only description of that arrangement lives inside the controller's own firmware. Lose the controller, or corrupt the table, and the drive stops answering the bus entirely while the data sits behind it in perfect health, waiting for somebody to ask. Two honest ways in exist. One is to reach the controller through the manufacturer's service mode and coax it into rebuilding what it mislaid. The other is to take the NAND off the board, read the packages themselves and reconstruct the translation in software — slower, and completely indifferent to whether the drive answers at all. Neither is anything a consumer utility can attempt, because every one of those programs needs a drive the computer can already see.
Samsung, Crucial, Kingston, SanDisk, WD, Intel, SK hynix, Kioxia and Apple's removable blades all pass through, as 2.5-inch SATA units, mSATA cards and M.2 sticks. The regulars are whatever every builder in the county was fitting that year: the Samsung 860 EVO and the 870 EVO that followed it, the Crucial MX500 and BX500, the Kingston A400 and KC600, the WD Blue SA510 and the SanDisk Ultra 3D. The Samsung 860 EVO earns a paragraph of its own, because its signature failure brings more people to this page than any other single model. A healthy-looking MZ-76E500 leaves the SATA bus mid-session and comes back reporting a lost or corrupt signature, a small fraction of its real capacity, or nothing whatever. That is the MJX controller having mislaid its translator rather than V-NAND that has worn out — with no mapping to work from, the drive has nothing coherent to present, while every file sits untouched in the memory behind it. Samsung issued firmware revisions across that generation aimed squarely at the behaviour, and for a drive already past the point of accepting one, service-mode work rebuilds the translator and a full image is taken before the drive is asked to do another thing. Two jobs are declined here, and it is fairer to say so before the postage than after it: storage soldered permanently to a mainboard, and phones or tablets, which are not part of this service in any form. Aggressive TRIM and hardware encryption both make a job harder than it first looks, and you will hear about that at the assessment rather than read it on an invoice.
A spinning disk gives notice. It ticks, it slows, it asks for the same sector twice, and an owner paying any attention gets a few days out of it. A solid state hard drive gives none of that, because there is nothing mechanical inside to make a sound: the controller either answers or it does not, and the change from one state to the other happens between two ordinary Tuesdays. That is why so much solid state hard drive data recovery arrives here with the owner insisting the drive was perfectly healthy on the day before, and why they are generally right. Wear is real, but it is rarely the culprit. A consumer SSD is far likelier to lose its translator to a power cut, a firmware bug or a controller that has simply stopped answering than it is to run out of write cycles, which is the failure most people expect and the one we see least. Whichever of them it turns out to be, the diagnostic is free and takes two working days from arrival, and any one SSD is £300 + VAT, with M.2 and NVMe modules included at the same figure.
Solid-state work is firmware and chip surgery from the very first minute, and this bench is specified for it:
Brings a silent drive up in its own manufacturer's service mode, corrects the firmware, rebuilds the translator, and takes a full image before that drive is asked to do another single thing.
Drives that stall get hardware-enforced timeouts and a retry pattern chosen for the unit on the bench rather than lifted out of a manual.
A proper connector for every removable solid-state format, including 2230 stubs and Apple blades, with active cooling for modules that misbehave when warm. No hopeful USB caddies anywhere in the chain.
Where service mode cannot rouse the controller, the packages are lifted off the board and read individually. A longer road to the same address.
Interleave, XOR and ECC worked out from bare dumps until the mapping exists once more in software, with the volume standing on it.
Burnt power stages and cracked boards are repaired first. Imaging a drive that browns out halfway through achieves nothing except a second attempt.
If one drive defines this page it is the Samsung 860 EVO. The MZ-76E500 went into an enormous number of machines when people were replacing hard drives, and a decade on those upgrades are reaching the end of their working lives together. Its signature failure — a drive that leaves the SATA bus abruptly and returns as a fraction of its size, or not at all — is a translator problem sitting on top of perfectly good V-NAND, and it recovers. The 870 EVO generation behaves much the same way. Around them: the A400 SA400S37 losing its map, the MX500 fretting about pending sectors, the SA510 exiting without comment, the BX500 worn out early, and the NV2 which ships with whichever controller and flash were available that quarter. Anything that unplugs is workable — 2.5-inch, mSATA, M.2 — including drives that have locked themselves read-only. Two things are not: flash soldered onto a motherboard, and phones or tablets, without exception.
Most of what reaches this bench arrived by tracked, insured post. It is the steadiest way to move a poorly drive, and a parcel posted in Norfolk is usually on the bench the next working day.
Is the drive still bolted inside a laptop, desktop, MacBook, iMac, server or CCTV / DVR recorder? The hard drive or SSD needs to come out first, and only the bare drive travels — taking drives out of machines is not something we do here. Storage soldered to a motherboard (Apple Silicon Macs, one or two very thin laptops) is the single thing beyond us: if it will not come out, it cannot come in.
↓ Print the shipping & booking-in form (PDF)
Mark the parcel for the attention of Cambridge Data Recovery. From Norwich it is about an hour and twenty down the A11, then two minutes off the A14 at Junction 32 — or next working day by tracked post. You hear from us as soon as it is booked onto the bench.
Unsure what to put in the box? Ring 0800 689 0668 before you seal it, or run the free online diagnostic.
Diagnosis free, one figure written down, most work under no fix no fee. Start online, or ring us.