SSD Controller Technical Reference
KIOXIA TC58NC1202GST (Phison E12C rebrand) Controller Reference
The KIOXIA TC58NC1202GST is a rebranded Phison PS5012-E12C controller used in the KIOXIA Exceria and Exceria Plus Gen3 NVMe SSDs. Despite the KIOXIA part number, it shares the same firmware family as other Phison E12 drives. KIOXIA applies heavy proprietary firmware tweaks to optimize for their BiCS flash memory, and a generic PS5012 loader may struggle with KIOXIA's specific block allocation and dynamic SLC caching algorithms. 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.
KIOXIA TC58NC1202GST (Phison E12C rebrand) is not on the current PC-3000 SSD supported-controller list
KIOXIA TC58NC1202GST (Phison E12C rebrand) 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.

KIOXIA TC58NC1202GST (Phison E12C rebrand) Specifications
| Manufacturer | KIOXIA |
| Interface | NVMe Gen3 |
| NAND Types | 3D TLC |
| DRAM Cache | Yes |
| Channels | 4 |
| PC-3000 Support | Supported (Active Utility) |
| Chip-Off Viability | Not viable (AES-256 hardware encryption) |
AES-256 hardware encryption makes chip-off not viable. This is a rebranded Phison PS5012-E12C; the Phison NVMe module in PC-3000 SSD Extended handles recovery. Same firmware family as other E12-based drives.
Affected SSD Models
The KIOXIA TC58NC1202GST (Phison E12C rebrand) 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 | KIOXIA Exceria (Gen3) | NVMe Gen3 |
| 2 | KIOXIA Exceria Plus (Gen3) | NVMe Gen3 |
| 3 | Toshiba RC500 (predecessor branding) | NVMe Gen3 |
Common Failure Modes and Symptoms
Each failure mode below describes a specific way the KIOXIA TC58NC1202GST (Phison E12C rebrand) 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 recovery mode
The controller enters a diagnostic mode after firmware table corruption. The drive enumerates with a vendor-specific device string and reports 0MB capacity. SMART data becomes inaccessible in this state, and the drive is not bootable.
- Drive shows as 0MB KIOXIA device
- Not bootable
- SMART data inaccessible
- Power loss FTL corruption
Unclean shutdown corrupts the flash translation layer. The drive fails to enumerate or shows wrong capacity after a power loss event. Recovery requires Phison E12 firmware repair via PC-3000.
- Drive not detected after power loss
- Shows wrong capacity or 0MB
- Drive fails to initialize after outage
- BiCS NAND wear with KIOXIA-specific caching
KIOXIA's custom firmware optimizes a 19GB SLC cache for their 96-layer BiCS flash memory. As the BiCS TLC NAND degrades, the controller encounters increasing uncorrectable errors that the KIOXIA firmware handles differently than standard Phison E12 implementations, requiring adjusted read-retry parameters.
- Slow performance degradation over time
- Increasing correctable errors in SMART data
- Drive intermittently fails read operations
- KIOXIA SSD Utility shows health warnings
How Is Data Recovered from a Failed KIOXIA TC58NC1202GST (Phison E12C rebrand) 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.
- KIOXIA TC58NC1202GST (Phison E12C rebrand) 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 shows as 0MB KIOXIA device, Not bootable, SMART data inaccessible are useful to recognize, but on this controller they do not unlock a tooling path we can offer in-lab.
- KIOXIA TC58NC1202GST (Phison E12C rebrand) 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.
- KIOXIA TC58NC1202GST (Phison E12C rebrand) 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 KIOXIA TC58NC1202GST (Phison E12C rebrand)?
Why not use chip-off recovery on KIOXIA SSDs?
Does Rossmann recover data from KIOXIA TC58NC1202GST (Phison E12C rebrand) drives?
Can you recover deleted files from a KIOXIA TC58NC1202GST (Phison E12C rebrand) SSD?
Have a KIOXIA TC58NC1202GST (Phison E12C rebrand) drive?
We do not currently offer in-lab recovery for KIOXIA TC58NC1202GST (Phison E12C rebrand) 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.