Data recovery for NVMe SSD
Advanced intervention on SSDs with electronic failure, firmware corruption or no access. Recovery via direct NAND read and data reconstruction.
Request diagnostic →SSD architecture: beyond storage
An NVMe SSD is not just memory. It depends on a controller, internal firmware and a complex logical structure that manages the data translation (FTL).
When these elements fail, data access is lost even if the NAND memory remains intact.
Critical issues
- • SSD not detected
- • Corrupt firmware
- • Controller failure
- • FTL table corruption
- • Inaccessible sectors
Cases where software no longer reaches
Standard tools (Recuva, R-Studio, PhotoRec) work when the SSD is alive and only software is missing. When it isn't detected, reports zero capacity or shows electrical faults, you need a lab.
SSD not detected by BIOS
You connect the SSD and it doesn't appear in BIOS, doesn't appear in Disk Management, or shows 0 GB capacity. The usual cause is a burned controller or corrupt firmware. The NAND remains intact. We work board-level to restore communication or, if not viable, do chip-off to read the NAND directly.
Electrical damage (surge, water)
Voltage spikes from a storm, faulty PSU or spills. The usual damage is to voltage regulators on the SSD's PCB. Microsoldering on affected components, line reconstruction and controlled boot.
Safe mode / "0 GB" / firmware bug
The SSD enters the manufacturer's protection mode: the system sees it but with 8 MB or 0 GB capacity and it can't be read. Typical cases in some Crucial, Samsung and SanDisk series with buggy firmware. Resuscitation via PC-3000 or equivalent with controller-specific profile.
Extremely slow reads
The SSD works but reads take minutes per file. Usually indicates NAND blocks degraded to the limit and a controller working overtime. Sector-by-sector imaging with aggressive timeouts before the SSD dies entirely.
Common cases
Recovery process
Controller diagnostic
NAND memory access
Chip read
FTL reconstruction
Data extraction
Related services
Controller, FTL, NAND and the tyranny of TRIM
An SSD is nothing like a hard drive. No platters, no heads: there is a board with NAND memory chips where data is stored, a controller that decides which physical cell each bit goes into, and a table called the FTL (Flash Translation Layer) that maps the logical addresses Windows or macOS sees to actual physical cells. Without that table, the data is there but unreadable, like a book with the index and bookmarks ripped out.
When an SSD fails, it's usually not the NAND that's damaged (memory chips are surprisingly robust), but the controller that has suffered electrical failure or a firmware bug. With no working controller, BIOS detects nothing and the FTL is inaccessible. Recovery requires either restoring controller communication with tools like PC-3000, or desoldering the NAND chips, reading them directly with a hardware programmer (chip-off) and rebuilding the FTL manually using knowledge of the manufacturer's algorithm.
On top of this is the complication of TRIM: when you delete a file on a working SSD, the OS tells the controller "this cell is no longer in use". The controller, during idle moments, physically wipes those cells so it doesn't lose write speed later. Result: on a powered SSD, deleted data physically disappears within hours. The golden rule for SSD data loss: power off the device and disconnect the disk. Every minute powered reduces the chances.
Mistakes that reduce recovery probability
On SSDs the clock starts from the moment you notice the loss. These are the moves that destroy recoverable information.
Leaving the SSD powered after the incident
TRIM and garbage collection keep running. Every minute powered, the controller can wipe blocks that contained your data. The rule: power off the device and physically disconnect the SSD as soon as possible.
Clicking 'Initialise disk' in Windows
When Windows sees an SSD with a broken partition table it asks to initialise. If you say YES, it writes a new table and recovering the data becomes much more complex. Always say NO and send it in.
Running 'repair' tools or chkdsk
chkdsk, sfc, Recuva-style tools or marketplace software can write sectors on the SSD. On an SSD with problems, every write can destroy entire blocks that were going to be recovered.
Reformatting or reinstalling the OS
A clean Windows or macOS install writes gigabytes onto the SSD and triggers TRIM massively. Previous data becomes unrecoverable. It's neither 'fast' nor 'cheap' as an option.
Connecting the SSD via cheap adapters
Low-quality SATA-USB or NVMe-USB adapters provide unstable voltages. On an already-damaged SSD they can finish off the controller. If you must test the SSD in another machine, use brand-name adapters and a stable connection.
Insisting if BIOS doesn't detect it
Restarting twenty times, trying different SATA ports, or warming the device doesn't bring a burned controller back. The more you try, the more you stress the remaining electronics. After 2-3 attempts, send it in.
Brands and formats we recover
We work with SSDs of any brand and format, from consumer NVMe to enterprise U.2. Every controller has its own algorithm and we keep specific profiles for the most common models.
NVMe M.2 (PCIe)
- ·Samsung 980 / 990 Pro / Evo Plus
- ·WD Black SN850 / SN770
- ·Crucial T700 / P5 Plus / P3
- ·Kingston KC3000 / NV2
- ·Seagate FireCuda 530
SATA M.2
- ·Samsung 860 / 870 EVO M.2
- ·WD Blue SA510 M.2
- ·Crucial MX500 M.2
- ·Kingston A2000 / A400 M.2
2.5" SATA SSD
- ·Samsung 860 / 870 EVO / QVO
- ·WD Blue / Green SATA
- ·Crucial MX500 / BX500
- ·Kingston A400 / KC600
- ·SanDisk Ultra / Plus
Enterprise / U.2
- ·Samsung PM9A3 / PM1733
- ·Intel D7-P5520 / SSD DC
- ·Micron 7400 / 7450
- ·Kioxia CD6 / CM7
Apple soldered SSD
- ·MacBook Air / Pro 2016-2017
- ·MacBook with T2 (2018-2020)
- ·MacBook Apple Silicon M1/M2/M3
- ·iMac and Mac mini with soldered SSD
Legacy and special formats
- ·mSATA
- ·SATA Express
- ·Apple PCIe Blade SSD (Mac 2013-2015)
- ·M.2 2230 / 2242 / 22110
- ·PCIe accelerator cards
SSD and NVMe data recovery
01Can data be recovered from an SSD that isn't detected?+
02What is the FTL and why does it make SSD recovery so complex?+
03Does TRIM destroy deleted data? Can it still be recovered?+
04What about encrypted SSDs (BitLocker, OPAL, hardware encryption)?+
05How much does SSD data recovery cost?+
06Can I connect the SSD to another computer to try to read it?+
07How long does SSD recovery take?+
08Do you recover enterprise SSDs (U.2, datacenter)?+
Recover your data from a damaged SSD
Free evaluation. You only pay if we recover the information.
Request diagnostic