How to Recover Data From an SSD: Complete Technical Guide
A comprehensive guide to SSD data recovery covering assessment, available methods, success factors, and when professional intervention is necessary.
SSD Recovery: Bottom Line
SSD data recovery has three possible paths: (1) Software tools work for deleted files or formatted partitions only if the drive is detected with correct capacity and TRIM has not run. (2) Professional firmware recovery via PC-3000 works for controller lockups, SATAFIRM S11 errors, and 0-byte capacity issues by rebuilding the Flash Translation Layer. (3) Board-level microsoldering works for dead controllers and shorted power circuits by repairing the original hardware. Hardware-encrypted drives require the original controller to function for decryption; chip-off without the controller yields only ciphertext.
Cost: $200–$1,500 (SATA) or $200-$2,500 (NVMe).Timeline: 3-8 weeks.Success factors: NAND health, encryption status, and whether TRIM has executed on deleted data.
How to Assess an SSD for Recovery
Before choosing a recovery method, determine the failure type through systematic assessment. This determines whether software tools have any chance or if professional equipment is required.
- Check BIOS/UEFI Detection
Power on the computer and enter BIOS setup. Look in storage devices. If the SSD appears with correct model name and capacity, the controller is functional and software tools may work. If it shows "0 bytes," wrong capacity, or does not appear at all, the controller or firmware has failed; professional recovery is required.
- Check SMART Status
If detected in BIOS, boot to an OS or use a live USB. Run CrystalDiskInfo (Windows) or smartctl (Linux). Look for reallocated sectors, pending sectors, or wear-leveling errors. High numbers indicate NAND degradation. This affects recovery difficulty but does not prevent it if the controller is functional.
- Check Physical State
With the drive disconnected, visually inspect for burn marks, bulging capacitors, or physical damage. Connect power only (no data) and feel for heat within 10 seconds. If it gets hot to touch or emits a burning smell, a component is shorted. Power off immediately; this requires microsoldering repair.
- Determine TRIM Status (for deleted files)
If recovering deleted files, check if TRIM has run. On Windows:
fsutil behavior query DisableDeleteNotify. If TRIM is enabled and files were deleted hours or days ago, recovery is likely impossible. If disabled, or deletion was immediate, software tools may recover data. - Identify Controller Model
If possible, identify the SSD controller (Phison, Silicon Motion, Samsung, Marvell). This affects recovery approach but not pricing tier. Common failures: Phison PS3111-S11 shows SATAFIRM S11; Silicon Motion SM2258XT shows 0 bytes or wrong capacity; Samsung Elpis has 0E health bug.
Do not continue if: The drive is not detected, shows wrong capacity, gets hot, has burning smell, or disconnects during access. Every additional power-on reduces recovery odds. Contact a lab with PC-3000 equipment immediately.
SSD Recovery Methods Explained
Method 1: Software Recovery (Logical Only)
Uses standard data recovery software (PhotoRec, Disk Drill, R-Studio) to scan the file system or raw NAND through the controller. Only works when the SSD is detected with correct capacity and the controller is fully functional. Addresses deleted files (if TRIM has not run), formatted partitions, and corrupted file systems.
Requirements: Drive detected in BIOS/OS with correct model and capacity. No physical symptoms.Success rate: High for logical failures where data still exists in NAND mapping.Cost: Free (PhotoRec/TestDisk) to ~$90 (Disk Drill, R-Studio).
Method 2: Firmware Recovery via PC-3000
Uses PC-3000 Portable III with SSD/NVMe modules to force the controller into diagnostic mode (Techno Mode, Safe Mode, Factory Mode). Allows direct access to NAND without going through the corrupted firmware. Rebuilds the Flash Translation Layer by scanning spare area metadata on every NAND page.
Addresses SATAFIRM S11, 0 bytes capacity, wrong model name, firmware panic states (Phison E12 MN-5236), and controller lockups where the silicon is intact but firmware is corrupt.
Requirements: PC-3000 Portable III with controller-specific utility. Controller silicon must be functional.Success rate: High when NAND is intact. Cost: $600–$900 (SATA) or $900-$1,200 (NVMe) at professional labs.
Method 3: Board-Level Component Repair
Uses microsoldering equipment (Hakko FM-2032, FLIR thermal cameras) to repair the SSD's circuit board. Replaces shorted PMICs, blown capacitors, and damaged voltage regulators. Reflows or reballs controller BGA packages with connection issues. Required when the controller has no power or physical damage prevents operation.
Essential for hardware-encrypted drives (virtually all modern NVMe). Since AES-256 keys are bound to the controller silicon, the original controller must be revived for decryption. Chip-off to donor board does not work (keys do not transfer).
Requirements: Microsoldering station, thermal imaging, schematic knowledge.Success rate: Moderate to high depending on damage extent.Cost: $450–$600 (SATA) or $600-$900 (NVMe).
Method 4: NAND Transplant (Last Resort)
Physically desolders NAND chips from the failed PCB and solders them to a matching donor PCB. Only viable for unencrypted drives where the donor controller can read the raw NAND. Modern encrypted drives require Method 3 (board repair) instead.
Requirements: BGA rework station, matching donor PCB with same controller/firmware, XOR scrambling knowledge.Success rate: Moderate; depends on NAND health after removal.Cost: $1,200–$1,500 (SATA) or $1,200-$2,500 (NVMe) with 50% deposit.
| Method | Failure Type | Equipment | Cost |
|---|---|---|---|
| Software | Deleted files, formatted partition (if TRIM not run) | Standard computer | Free - $90 |
| Firmware (PC-3000) | SATAFIRM S11, 0 bytes, wrong capacity, controller lockup | PC-3000 Portable III with SSD/NVMe modules | $600–$900 |
| Board Repair | Dead controller, shorted PMIC, power circuit failure | Hakko microsoldering station, FLIR thermal camera | $450–$600 |
| NAND Transplant | Severe PCB damage (unencrypted drives only) | BGA rework station, donor PCB | $1,200–$1,500 |
TRIM and Deleted File Recovery
TRIM is the most significant factor affecting SSD recovery feasibility for deleted files. Understanding how TRIM works determines whether recovery is worth attempting.
- What is TRIM?
- TRIM is an ATA command that tells the SSD controller which logical blocks are no longer in use. When you delete a file, the OS sends TRIM. The controller marks those pages as invalid in the Flash Translation Layer and returns zeroes on subsequent read requests. The actual NAND cells are not immediately erased, but the controller refuses to serve the data.
- Can TRIMmed data be recovered?
- Generally no. Once TRIM executes and the controller acknowledges it, the logical addresses are permanently unmapped. Even though charge may remain on the floating gates temporarily, the controller will not provide access. Professional labs cannot bypass this; it is a fundamental SSD protocol feature.
- When might recovery work?
- If the SSD failed hardware-wise (dead controller, power loss) before the OS sent TRIM commands, the data remains mapped in the FTL. Recovery via PC-3000 can access this data by bypassing the failed controller and reading raw NAND through diagnostic mode.
TRIM timing by OS: Windows runs TRIM continuously on idle SSDs with native drivers. macOS enables TRIM automatically on Apple SSDs; third-party SSDs require manual activation with sudo trimforce enable. Linux varies by distribution: some batch TRIM weekly via fstrim.timer, others use real-time discard.
Hardware Encryption and Recovery Challenges
Modern SSDs (virtually all NVMe and many SATA) use hardware AES-256 encryption that is always active. This fundamentally changes the recovery approach compared to unencrypted drives.
Self-Encrypting Drives (SED)
The SSD controller generates an AES-256 key on first use and stores it in hardware fuses or a Physically Unclonable Function (PUF) unique to that specific chip. All data written to NAND is encrypted. There is no "disable encryption" option on modern drives. The key never leaves the controller.
Why Chip-Off Fails on Encrypted SSDs
Desoldering NAND chips and reading them with a flash programmer produces only ciphertext. Without the original controller's unique hardware-bound key, decryption is mathematically impossible. The only path to data is repairing the original controller so it can decrypt in place.
Apple T2 and M-Series
Apple Silicon Macs (M1/M2/M3/M4) and T2 Macs (2017-2020) solder NAND to the logic board and bind encryption to the Secure Enclave. The NAND cannot be read separately. Recovery requires logic board microsolderingto restore power to the Secure Enclave so it can decrypt data in place.
Bottom line: For encrypted SSDs with dead controllers, recovery depends entirely on reviving the original hardware through board-level repair. Labs without microsoldering capability cannot handle these cases. Be wary of any lab promising encrypted SSD recovery without naming their soldering equipment.
What Happens at a Professional SSD Recovery Lab
When you ship an SSD to a professional lab, here is the process from arrival to data return. Understanding this helps set realistic expectations and identify legitimate operations.
- Receipt and Initial Inspection
Drive is logged, photographed, and physically inspected for damage. PCB condition, connector integrity, and visible component damage are documented.
- Power Analysis
Drive is connected to a current-limited bench power supply. Current draw at 5V (SATA) or 3.3V (M.2) is measured. Abnormal draw indicates shorted components. FLIR thermal imaging locates hot spots.
- Controller Communication Test
PC-3000 attempts vendor-specific commands to enter diagnostic mode. If the controller responds, firmware version and health are queried. If not detected, board repair is prioritized.
- Board Repair (if needed)
Shorted PMICs or capacitors are replaced. Damaged traces are jumpered. Controller BGAs are reflowed if connection issues are suspected. Goal: restore power and communication to the controller.
- Firmware Reconstruction
PC-3000 enters diagnostic mode (Techno Mode, Safe Mode). Service area modules are read. Corrupted Flash Translation Layer is rebuilt from NAND spare area metadata. This can take hours depending on NAND size and corruption extent.
- Multi-Pass Imaging
Drive is imaged sector by sector to a target drive. Sectors failing on first read are queued for retry with adjusted voltage/timing parameters. For degraded NAND, thermal stabilization may be applied.
- Verification and Return
Recovered files are verified. Customer receives file list for approval. Data is transferred to customer-provided media or new drive. Original drive is returned or securely disposed of per customer instruction.
Timeline: Evaluation takes 1-3 business days. Actual recovery takes 3-8 weeks depending on failure complexity. NAND degradation cases with multi-pass imaging take longest. Rush service (+$100) moves cases to front of queue.
SSD Recovery FAQs
Common questions about how SSD data recovery works.
Can data be recovered from a dead SSD?
How much does SSD data recovery cost?
Can you recover data after TRIM?
How long does SSD recovery take?
Can I recover SSD data myself?
What are the chances of SSD recovery success?
Get Expert SSD Recovery Help
Rossmann Repair Group provides professional SSD recovery from $200-$2,500. Free evaluation. No data, no charge. Austin lab, nationwide mail-in.