Encrypted SSD Data Recovery | Hardware Encryption & SED Recovery

No Data, No Fee

Guarantee

2.49M+

Subscribers

4.9

1,837+ Google Reviews

Since 2008

Established

Repairs on Video

Full Transparency

As Featured In

BBC News CBC News ABC Australia Wall Street Journal Business Insider Vice Fast Company 404 Media

Why Most SSDs Are Already Encrypted

Since approximately 2015, the majority of SSD controllers implement always-on AES-256 hardware encryption. Samsung, Phison, Silicon Motion, Marvell, and Intel/Solidigm controllers all encrypt data before writing it to NAND. This encryption is active by default with no user configuration required.

The controller generates a Media Encryption Key (MEK) during manufacturing or first initialization. Every write to NAND passes through the AES engine, and every read is decrypted before being sent to the host. Under normal operation, this is invisible. The OS reads and writes plaintext; the controller handles encryption transparently. Performance impact is negligible because the AES engine is implemented in dedicated hardware on the controller die.

Always-on encryption exists for two reasons. First, it enables instant Secure Erase: instead of erasing every NAND cell, the controller destroys the MEK and generates a new one, making all existing data permanently unreadable in milliseconds. Second, it provides a foundation for user-set passwords. When a user enables ATA Security, TCG OPAL, or BitLocker hardware mode, the MEK is itself encrypted with the user's authentication key. The NAND data was already encrypted; the user password simply locks access to the MEK.

How SSD Encryption Keys Work

The encryption key hierarchy has multiple layers. Understanding where each key lives determines whether recovery is possible after a hardware failure.

Media Encryption Key (MEK): The AES-256 key used to encrypt and decrypt all data on the NAND. Stored in a secure region of the controller chip or in a protected area of the NAND that only the original controller can access. Unique per drive; no two SSDs share the same MEK.
Key Encryption Key (KEK): When a user password is set (via ATA Security, OPAL, or OS-level encryption in hardware mode), the MEK is wrapped with the KEK derived from the password. The wrapped MEK is stored on the drive. Without the correct password, the MEK cannot be unwrapped and data remains encrypted.
Self-Encrypting Drive (SED): An SSD that complies with the TCG OPAL specification for hardware encryption management. OPAL provides a standardized interface for setting user authentication, defining encryption ranges, and managing the key hierarchy. Samsung, Micron/Crucial, and Intel enterprise SSDs commonly support OPAL 2.0.
Class 0 Encryption (Always-On): Drives that encrypt all data by default without user authentication. The MEK is accessible to the controller without a password. Data is protected from raw NAND reads (chip-off) but not from normal host access through the controller.

Encrypted vs. Unencrypted SSD Recovery

The presence of hardware encryption changes the viable recovery methods. On an unencrypted drive, multiple paths exist. On an encrypted drive, the original controller is the only key holder.

Recovery Method	Unencrypted SSD	Encrypted SSD (Class 0)	Encrypted SSD + User Password
PC-3000 firmware repair	Works; data reads directly	Works; controller decrypts transparently	Works if password is known; controller decrypts after authentication
Board-level controller repair	Works; original controller not required	Required; only the original controller holds the MEK	Required; original controller + user password both needed
Chip-off NAND recovery	Viable; raw NAND is plaintext	Yields ciphertext; data unrecoverable	Yields ciphertext; data unrecoverable
Controller swap to donor	May work for some older controllers	Fails; new controller has different MEK	Fails; new controller has different MEK

Why Board-Level Repair Is the Only Recovery Path

When a hardware-encrypted SSD fails, the MEK is trapped inside the dead or malfunctioning controller. Replacing the controller destroys the key association. The only option is to repair the original controller circuit so it can boot, access the MEK, and decrypt NAND reads.

01
Diagnose the failure point
Using FLIR thermal imaging and multimeter probing, we identify whether the failure is in the controller itself, the PMIC (Power Management IC), voltage regulators, decoupling capacitors, or the NAND interface. Many "dead controller" symptoms are actually failed passives on the power delivery circuit that prevent the controller from booting.
02
Component-level repair
Using Hakko FM-2032 microsoldering irons and Atten 862 hot air rework, we replace failed voltage regulators, capacitors, resistors, or rework BGA connections on the controller. The goal is to restore power delivery and signal integrity so the controller boots its firmware and initializes the AES engine with the original MEK.
03
Firmware stabilization and imaging
Once the controller boots, PC-3000 communicates with it via vendor-specific commands to stabilize the firmware and image the drive. Because the original controller is running, all reads pass through the AES decryption engine. The imaged data is plaintext, ready for file system analysis.

This is where Rossmann's background in board-level repair directly applies to data recovery. Most data recovery labs are equipped for firmware-level work but not for component-level soldering. When the failure is electrical rather than logical, those labs cannot proceed. We can, because board-level repair is the foundation of this shop.

Apple T2 and M-Series: A Special Case

Apple T2 and M-series chips implement hardware encryption through a Secure Enclave coprocessor. The AES keys are fused into the Secure Enclave silicon, and the NAND storage is soldered directly to the logic board. There are no removable drives to send to another lab.

On a MacBook with a T2 or M-series chip, the SSD controller is integrated into the Apple silicon. The NAND chips are soldered to the logic board and communicate with the SoC through a proprietary bus. The Secure Enclave generates and stores the volume encryption keys. If the logic board fails, the keys are inaccessible. Desoldering the NAND yields AES-256 ciphertext with no path to decryption.

Recovery requires repairing the logic board so the T2 or M-series chip boots and the Secure Enclave can serve the decryption keys. This is T2/M-series data recovery at the board level: identifying which power rail, capacitor, or IC failure prevents the SoC from initializing, repairing it, and imaging the drive through the running system.

How Much Does Encrypted SSD Recovery Cost?

Encrypted SSD recovery typically falls into the circuit board repair or firmware recovery tier. SATA SSD board repair: $450–$600. NVMe board repair: $600–$900. Firmware recovery (if controller boots but firmware is corrupted): SATA $600–$900, NVMe $900–$1,200. Free evaluation, firm quote before work begins, no data = no charge.

If board repair requires a donor drive for component harvesting, the donor cost is additional. A donor drive is a matching SSD used for its circuit board. Typical donor cost: $40–$100 for common models, $150–$300 for discontinued or rare controllers.

Rush service: +$100 rush fee to move to the front of the queue. Call (512) 212-9111 for a free evaluation.

Frequently Asked Questions

Can you recover data from a hardware-encrypted SSD?

Yes, if the original controller can be revived through board-level repair. The AES-256 key is stored on the controller silicon. By repairing or reworking the controller, the decryption chain remains intact and the drive decrypts data transparently during imaging. SATA SSD board repair: $450–$600. NVMe: $600–$900. Free evaluation, no data = no charge.

Does chip-off recovery work on encrypted SSDs?

Not for drives with hardware encryption. Chip-off reads raw NAND data by desoldering the flash chips. On an encrypted drive, the raw NAND contains AES-256 ciphertext. Without the key stored in the original controller, the data cannot be decrypted. Chip-off is only viable for older drives without always-on encryption or for unencrypted controllers.

Is my SSD encrypted even if I never turned on encryption?

Most SSDs manufactured after 2015 implement always-on hardware encryption (also called Class 0 encryption). The controller encrypts every write and decrypts every read using a key burned into the controller during manufacturing. This happens transparently; the OS never sees it. The data on the NAND is always ciphertext. If you also set a user password (ATA Security, OPAL, or BitLocker hardware mode), the media encryption key itself is encrypted with your password.

What is the difference between hardware encryption and BitLocker?

Hardware encryption (SED) is performed by the SSD controller using a key stored in the controller silicon. BitLocker is software encryption performed by Windows using a key stored in the TPM or entered by the user. They can operate independently or together. When BitLocker uses 'hardware encryption mode,' it delegates encryption to the SSD controller. Recovery from a dead hardware-encrypted drive requires reviving the controller first, then applying the BitLocker key to the imaged data.

What happens to the encryption key if the controller is replaced?

The AES-256 media encryption key is unique to the specific controller chip. Replacing the controller with an identical model does not transfer the key. The new controller generates its own key during initialization, making the existing NAND data permanently unreadable. This is why controller replacement is not a recovery option for encrypted drives; the original controller silicon must be repaired.