SSD Controller Recovery
Innogrit IG5236 (Rainier) Data Recovery
The Innogrit IG5236 (codenamed Rainier) is a premium 8-channel Gen4 NVMe controller with onboard DRAM. When the controller suffers a firmware exception, it drops its OEM identity and reverts to its factory silicon descriptor MN-5236 with capacity shrinking to 2.1GB or 2MB. A deeply ingrained firmware instability under sustained mixed I/O causes buffer overflows that crash the controller into this permanent ROM state. PC-3000 SSD provides dedicated Active Utility support for this controller. Controller-level work for the Innogrit IG5236 (Rainier) sits inside our broader SSD data recovery workflow at the Austin, TX lab.
Innogrit IG5236 (Rainier) Specifications
| Manufacturer | Innogrit |
| 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) |
AES-256 hardware encryption makes chip-off not viable. PC-3000 SSD Extended supports Innogrit controllers. 8-channel architecture with onboard DRAM.
Affected SSD Models
The Innogrit IG5236 (Rainier) 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 | ADATA XPG Gammix S70 Blade | NVMe Gen4 |
| 2 | HP FX900 Pro | NVMe Gen4 |
| 3 | Acer Predator GM7000 | NVMe Gen4 |
| 4 | Mushkin Redline Vortex | NVMe Gen4 |
Common Failure Modes and Symptoms
Each failure mode below describes a specific way the Innogrit IG5236 (Rainier) 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 exception / BSoD trigger
Early firmware revisions on drives using this controller caused Windows BSoD (KERNEL_DATA_INPAGE_ERROR) under sustained mixed workloads. The drive may enter read-only mode or become unresponsive after the crash.
- Windows BSoD during file operations
- Drive enters read-only mode
- SMART reports pending sector count increase
- Power loss recovery loop
After an unclean shutdown, the controller enters a recovery cycle that can take 30+ seconds. If interrupted by the user power cycling again, FTL corruption results. Repeated power cycling during this window makes the drive permanently undetectable.
- Drive takes 30+ seconds to enumerate after power loss
- Repeated power cycling makes drive undetectable
- Drive not seen in BIOS after multiple reboots
- MN-5236 firmware panic
When the controller suffers a firmware exception under heavy workloads, it drops its OEM identity (ADATA, HP, Mushkin) and reverts to its factory silicon descriptor MN-5236. The reported capacity shrinks to 2.1GB or 2MB. The drive causes severe BIOS hang-ups and Windows BSODs before entering this permanent ROM state.
- Drive shows as MN-5236 in BIOS
- Capacity dropped to 2.1GB or 2MB
- System hangs in BIOS with drive connected
- BSODs preceded by drive instability under load
How Is Data Recovered from a Failed Innogrit IG5236 (Rainier) 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.
- Innogrit IG5236 (Rainier) 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 Windows BSoD during file operations, Drive enters read-only mode, SMART reports pending sector count increase point to controller-level work, not file-copy software.
- PC-3000 SSD gives us a controller-aware path into Innogrit IG5236 (Rainier) so we can inspect ROM behavior, load working code into SRAM, and rebuild translator metadata from NAND page headers before imaging starts.
- If encryption is bound to the original controller, board-level repair comes before any NAND removal because the controller still holds the path needed to turn ciphertext back into files.
Innogrit IG5236 (Rainier) Recovery Process
The IG5236 has a deeply ingrained firmware instability under sustained mixed workloads. When the controller encounters a defective NAND page under heavy I/O, a buffer overflow crashes it into the MN-5236 state. Running OEM diagnostic tools (e.g., ADATA SSD Toolbox) on a destabilizing drive can trigger the total failure.
- Connect drive to PC-3000 Portable III via M.2 NVMe adapter
- PC-3000 recognizes the MN-5236 panic state from the diagnostic name reported by the controller
- Force controller into Techno Mode using PC-3000 SSD Extended InnoGrit Utility
- Read raw physical NAND data, bypassing the completely corrupted firmware
- Reconstruct Flash Translation Layer metadata from scratch using PC-3000
- Image data sector-by-sector using the original controller's descrambling algorithms
Equipment Used
- PC-3000 Portable III
- PC-3000 SSD Extended InnoGrit Utility
Typical timeline: 4-8 hours
Learn more: controller encryption affects recovery, and how wear leveling works
Transparent Pricing for NVMe Gen4 SSD Recovery
Flat-rate pricing with no diagnostic fees. The cost to recover data from a Innogrit IG5236 (Rainier)-based SSD depends on the severity of the failure. For the full diagnostic path across controller, firmware, and NAND-level failures, see our SSD recovery flagship; deleted-file cases are governed by DZAT and NAND physics. No data, no recovery fee. Full SSD recovery cost breakdown.
| Tier | What It Covers | Price |
|---|---|---|
| Simple Copy | Your NVMe drive works, you just need the data moved off it | $200 |
| File System Recovery | Your NVMe drive isn't showing up, but it's not physically damaged | From $250 |
| Circuit Board Repair | Your NVMe drive won't power on or has shorted components | $600–$900 |
| Firmware Recovery | Your NVMe drive is detected but shows the wrong name, wrong size, or no data | $900–$1,200 |
| PCB / NAND Swap | Your NVMe drive's circuit board is severely damaged and requires NAND chip transplant to a donor PCB | $1,200–$2,500 |
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. +$100 rush fee to move to the front of the queue.
Frequently Asked Questions
Can software recover data from a dead Innogrit IG5236 (Rainier)?
Why not use chip-off recovery on Innogrit SSDs?
How much does Innogrit IG5236 (Rainier) data recovery cost?
Can you recover deleted files from a Innogrit IG5236 (Rainier) SSD?
Need Innogrit IG5236 (Rainier) Recovery?
Ship your NVMe Gen4 SSD to our Austin, TX lab. Free evaluation, no diagnostic fee. If we recover your data, you pay the quoted tier. If not, you pay nothing.