An Asus laptop stopped booting when its M.2 SSD suddenly shrank to a tiny capacity and refused to give up its data — a firmware protective state, not a dead drive. The flash was intact underneath. We reached it at a lower level and rebuilt the mapping to recover the files.
The laptop failed to boot, and when the SSD was checked it appeared with a tiny capacity — a few megabytes instead of its real size — and would not present its contents. On it were work files and personal photos with no backup. This is a recognised SSD failure mode rather than physical destruction, so the drive was set aside rather than being repeatedly reformatted or power-cycled, either of which can make recovery harder.
SSDs run their own firmware, and when a controller detects a problem — too many failing flash blocks, a corrupted internal structure — it can drop into a protective or safe state to prevent further damage. In that state the drive stops presenting normally: it may report a fraction of its capacity, appear read-only, or refuse access entirely. It looks dead, but the flash and the data it holds are usually fine; the controller has simply stopped serving them through the normal interface. That's a good sign, because it means the drive is trying to protect the data rather than losing it.
The drive was brought up in the controller's manufacturer technical mode — a diagnostic state that bypasses the protective lock and allows the flash to be reached. Where a controller is too far gone even for that, the NAND is read directly instead. In both cases what comes back first is raw flash: scrambled, error-coded and physically out of order, not yet usable as files.
Turning that raw flash into data meant reconstructing the translator — the map from logical blocks to physical flash pages — removing the controller's scrambling, and applying the correct error-correction to repair read-time bit errors. With the mapping rebuilt, the logical drive returned to order, the file system reappeared, and the work files and photos were extracted with their names and folders intact.
Files were opened across the recovered set to confirm they were whole, then returned on fresh media. About 97% came back, the small remainder tied to the failing flash blocks that had triggered the protective state in the first place. As with any SSD, the lesson is that failure comes without warning, so a second copy of anything important is the cheapest insurance there is.
Controller technical-mode access and direct NAND reading · de-scrambling, ECC correction and translator (FTL) reconstruction · file-system rebuild. All work carried out in-house in Belfast.
Send it to us for a free, no-obligation diagnostic. We’ll tell you what can be recovered and put a fixed price in writing before any work starts — and on most jobs, if we can’t get your data back, there’s nothing to pay. Post your device in, or drop it to us by appointment.
Usually, yes. That's typically a firmware protective state, not a dead drive — the flash and data are intact behind a locked controller. We reach the flash at a lower level and rebuild the mapping to recover the files.
Yes — SATA, M.2 and NVMe alike. We remove the drive and recover from it directly, so it doesn't matter whether the laptop still boots.
No — reformatting or resetting a drive in a protective state can overwrite recoverable data or worsen the fault. Stop and have it assessed; a free diagnostic will show what's recoverable.