SSD Controller Technical Reference
Samsung Phoenix Controller Reference
Samsung's in-house NVMe controller in the 970 EVO and 970 PRO. ACELab's PC-3000 SSD supported-controller list does not currently cover this controller, so we take these drives case by case rather than as a published service. For the rest of the workflow at our Austin, TX lab, see our SSD data recovery page.
We take Samsung Phoenix drives case by case
The Samsung Phoenix is not on ACELab's PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.9.8), so no firmware utility we operate rebuilds its translator. We still look at these drives one at a time. A drive that still enumerates often needs nothing more than a logical recovery. On the 970, 980 and 990 families a drive a normal computer will not see can sometimes still be read through PC-3000, with no firmware utility for the controller involved. Contact us with the model & the symptom before you ship anything, & we will tell you in writing what we think is possible.
Source of truth: ACELab PC-3000 SSD supported-drives list. Internal evidence file: src/lib/ssd-support-matrix.ts.
Samsung Phoenix Specifications
| Manufacturer | Samsung |
| Interface | NVMe Gen3 |
| NAND Types | MLC, 3D TLC |
| DRAM Cache | Yes |
| Channels | 8 |
| PC-3000 Support | Not supported (absent from the ACELab list) |
| Chip-Off Viability | Not viable (controller-bound data path) |
Hardware encryption makes chip-off not viable.
Affected SSD Models
Samsung's in-house controller is the part inside the following consumer drives. A failure in this controller impacts access to the NAND flash on these specific models.
| # | Drive Model | Interface |
|---|---|---|
| 1 | Samsung 970 EVO | NVMe Gen3 |
| 2 | Samsung 970 PRO | NVMe Gen3 |
Common Failure Modes and Symptoms
Each failure mode below describes a specific way the Samsung Phoenix fails and the symptoms you will observe. If your SSD matches any of these patterns, do not run recovery software; it cannot communicate with a dead controller. See the zero-byte SSD diagnostic reference for a deeper technical explanation of controller and FTL failures.
- Firmware corruption from power loss
Sudden power loss during writes frequently corrupts the FTL or Service Area.
- NVMe SSD not detected after power loss
- Drive not seen in BIOS
How Is Data Recovered from a Failed Samsung Phoenix SSD?
Controller-class recovery starts by keeping the original board alive, reading controller state, and rebuilding the Flash Translation Layer from surviving NAND metadata. No PC-3000 SSD utility rebuilds the translator on the Samsung Phoenix, so the firmware-level half of that workflow is closed to us. On the 970, 980 and 990 families a drive a normal computer will not see can sometimes still be read through PC-3000, with no firmware utility for the controller involved. What is left is triage, logical recovery on a drive that still enumerates, and board-level repair of the original silicon.
Firmware access that needs Safe Mode or a volatile loader happens before any imaging. File-copy software never reaches this stage, since it needs a controller that already enumerates to the host. When the Samsung Phoenix also handles decryption, chip-off returns unreadable data, so the original silicon has to stay in the loop.
Holding a controller stable long enough to expose ROM state, firmware behavior, and NAND metadata without letting the drive write over itself is the core of controller-class recovery. Our SSD data recovery overview covers intake & triage, why SSDs report 0 bytes explains capacity failures, & how SSD controller encryption works explains why the original silicon matters.
- Samsung Phoenix failures usually break the Flash Translation Layer, firmware boot path, or local power rail before macOS or Windows sees a mountable volume. Symptoms such as NVMe SSD not detected after power loss, Drive not seen in BIOS tell us which bench the drive belongs on.
- Samsung Phoenix is not on ACELab's PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.9.8), so no firmware utility we operate rebuilds its translator. On the 970, 980 and 990 families a drive a normal computer will not see can sometimes still be read through PC-3000, with no firmware utility for the controller involved. We look at these drives one at a time instead of publishing a blanket refusal.
- If the controller is electrically dead, the work is board-level repair of the original silicon. The media key is generated on and wrapped by that controller, so a donor chip reads its NAND as ciphertext.
Watch a Samsung Phoenix Recovery
Samsung 970 EVO recovery: Samsung Magician reported healthy status while the drive's in-house controller masked degraded NAND sectors. PC-3000 multi-pass reading extracted data that consumer diagnostics missed.
Frequently Asked Questions
Can software recover data from a dead Samsung Phoenix?
Why not use chip-off recovery on Samsung SSDs?
Does Rossmann recover data from Samsung Phoenix drives?
Can you recover deleted files from a Samsung Phoenix SSD?
Since 2008
Established
As Featured In
Have a Samsung Phoenix drive?
The Samsung Phoenix is not on ACELab's PC-3000 SSD supported-controller list, so no firmware utility we operate rebuilds its translator. We take these drives case by case anyway. Contact us before shipping anything; we will tell you in writing what we think is possible for your specific drive.