SSD Controller Technical Reference
Samsung Elpis Controller Controller Reference
Samsung's Elpis is an 8nm, 8-channel NVMe Gen4 controller powering the 980 PRO and PM9A1 OEM drives. PC-3000 cannot perform full FTL reconstruction for Elpis; it can send vendor-specific commands to clear the forced read-only log and shift NAND read voltage thresholds. If the controller is electrically dead, recovery depends on board-level microsoldering to revive the original silicon, as the AES-256 Media Encryption Key is bound to the Elpis die. ACELab's PC-3000 SSD supported-controller list does not currently cover this controller. For context on the SSDs we do recover, see our SSD data recovery page.
Samsung Elpis Controller is not on the current PC-3000 SSD supported-controller list
Samsung Elpis Controller does not appear on the current ACELab PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.8.10) as of 2026-05-12. Case-by-case feasibility only. Contact us before shipping anything and we will tell you in writing whether we can do anything for your specific drive.
Source of truth: ACELab PC-3000 SSD supported-drives list. Internal evidence file: src/lib/ssd-support-matrix.ts.
Samsung Elpis Controller Specifications
| Manufacturer | Samsung |
| Interface | NVMe Gen4 |
| NAND Types | 3D TLC |
| DRAM Cache | Yes |
| Channels | 8 |
| PC-3000 Support | Supported (Active Utility) |
| Chip-Off Viability | Not viable (AES-256 hardware encryption) |
Portable III supports NVMe Samsung. 8nm custom ARM design. Hardware-bound encryption (SED) and proprietary NAND encoding make chip-off not viable.
Affected SSD Models
The Samsung Elpis Controller is deployed in the following consumer drives. A failure in this controller impacts access to the NAND flash on these specific models.
| # | Drive Model | Interface |
|---|---|---|
| 1 | Samsung 980 PRO | NVMe Gen4 |
| 2 | Samsung PM9A1 (OEM equivalent) | NVMe Gen4 |
| 3 | Late 970 EVO Plus revisions | NVMe Gen4 |
Common Failure Modes and Symptoms
Each failure mode below describes a specific way the Samsung Elpis Controller 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.
- 980 PRO read-only failure
Firmware 3B2QGXA7 causes permanent read-only mode (primarily 2TB models). SMART attribute 0E balloons. Firmware fix 5B2QGXA7 prevents but cannot undo damage.
- Drive becomes read-only
- SMART attribute 0E increasing
- Cannot write any data
- Samsung Magician shows health warnings
- Samsung Magician firmware update failure
Interrupted or failed firmware updates via Samsung Magician can leave the drive in a bricked, uninitialized state.
- Drive not detected after firmware update
- Firmware update stuck or failed
- Drive bricked after Magician update
- Thermal throttle crash during imaging
The Gen4 Elpis controller generates immense heat during sustained operations. Prolonged recovery imaging can push the controller past 85°C, triggering firmware panics during the extraction process. Active cooling with heatsinks and high-CFM airflow is mandatory during PC-3000 imaging sessions.
- Drive drops offline during extended reads
- Drive works for a few minutes then disconnects
- Controller surface temperature above 80°C measured via FLIR
- Intermittent detection during sustained access
How Is Data Recovered from a Failed Samsung Elpis Controller SSD?
Data is recovered from a failed controller SSD by keeping the original board alive, reading controller state with PC-3000 SSD, and rebuilding the Flash Translation Layer from surviving NAND metadata. If firmware access requires Safe Mode or a volatile loader, that work happens before imaging. When the controller also handles decryption, chip-off returns unreadable data.
At our Austin, TX lab, the goal is to keep the original controller stable long enough to expose ROM state, firmware behavior, and NAND metadata without letting the drive keep writing to itself. Our SSD data recovery overview covers lab intake and triage, why SSDs report 0 bytes explains capacity failures, and how SSD controller encryption works explains why the original silicon matters.
- Samsung Elpis Controller 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 Drive becomes read-only, SMART attribute 0E increasing, Cannot write any data are useful to recognize, but on this controller they do not unlock a tooling path we can offer in-lab.
- Samsung Elpis Controller is not on ACELab's PC-3000 SSD supported-controller list (PC-3000 SSD / PC-3000 SSD Extended 3.8.10). Without firmware utility coverage, the controller's mapping tables, internal loader, and any factory diagnostic mode are inaccessible to us, which means no firmware-level recovery is on the table.
- Samsung Elpis Controller fuses AES-256 keys to the controller silicon, so desoldering the NAND chips returns ciphertext that cannot be decrypted without reviving the original controller through tooling we do not currently have for this controller.
Frequently Asked Questions
Can software recover data from a dead Samsung Elpis Controller?
Why not use chip-off recovery on Samsung SSDs?
Does Rossmann recover data from Samsung Elpis Controller drives?
Can you recover deleted files from a Samsung Elpis Controller SSD?
Other Samsung Controllers
Have a Samsung Elpis Controller drive?
We do not currently offer in-lab recovery for Samsung Elpis Controller SSDs because the controller is not on ACELab's PC-3000 SSD supported-controller list. Contact us before shipping anything; we will confirm in writing what we can and cannot do for your specific drive.