How ADATA SSDs Fail
ADATA sources controllers from Silicon Motion, InnoGrit, & Realtek. This means ADATA SSDs share failure modes with every other brand using the same controller silicon: Crucial, Kingston, WD, Sabrent, Corsair. Our SSD data recovery lab works from the controller down, not from the brand label up.
The recovery advantage: PC-3000 SSD's Silicon Motion utility covers the SM2258XT, SM2259XT, SM2262EN, & SM2263XT. The same loader injection & FTL reconstruction procedures that recover a Crucial MX500 apply to an ADATA SU800. Controller-level expertise transfers across all Silicon Motion brands.
Two failure categories dominate. Firmware failures cause the controller to lock out, report wrong capacity, or drop the drive's identity string. Hardware failures include shorted voltage regulators, dead PMICs, & NAND cell degradation from write exhaustion. Both require lab-level intervention with firmware repair or board-level microsoldering.
What Are the Known ADATA SSD Failure Patterns?
Each ADATA product line uses a different controller generation with different firmware architecture & different failure modes. The most common failures we see map to the controller, not the ADATA branding.
SU800 & SU650: Silicon Motion FTL Corruption
The ADATA SU800 uses a Silicon Motion SM2258 controller with DRAM cache. The SU650 is a DRAM-less budget drive that shipped with SM2258XT controllers in early production, then switched to Realtek RTS5735DLQ or Maxio MAS0902 / MAS1102 controllers in later batches without changing the model name. Both controllers store critical Flash Translation Layer data in TLC NAND. When those NAND pages degrade past the controller's LDPC error correction capacity, the FTL mapping corrupts. The drive enters ROM mode: it reports 0GB, 1GB, or 1023MB capacity in BIOS & may display a raw controller string like "SM2258XT" instead of "ADATA SU650." This is the same failure mechanism that produces the SATAFIRM S11 lockout on Phison-based SSDs. PC-3000 SSD's Silicon Motion utility loads a safe mode module to bypass the corrupted boot sequence & reconstruct the FTL from NAND residuals.
XPG SX8200 Pro: Controller Swap & Firmware Instability
The XPG SX8200 Pro was one of ADATA's most popular NVMe SSDs, originally shipping with a Silicon Motion SM2262EN controller. ADATA later substituted the SM2262G (a cost-reduced variant) in some production runs without changing the product name. Both controllers share the same core architecture, but different firmware branches handle wear leveling & garbage collection differently. Failures on the SX8200 Pro include sudden BIOS disappearance after heavy write loads, read-only lockout from depleted spare blocks, & firmware panics during power loss events. Recovery requires identifying which controller variant is actually on the PCB, then using the correct PC-3000 SSD Silicon Motion NVMe utility module.
XPG GAMMIX S70 Blade: InnoGrit IG5236 Firmware Panic
The GAMMIX S70 Blade uses the InnoGrit IG5236 (Rainier), a high-performance Gen4 NVMe controller with AES-256 hardware encryption. When the IG5236 firmware panics, all cores stall & the drive drops off the PCIe bus completely. The Media Encryption Key is dynamically generated inside the controller and wrapped by a hardware-unique root key fused into the IG5236 silicon, so desoldering the NAND yields only ciphertext that no donor controller can unwrap. Board-level repair to revive the original InnoGrit controller is the only recovery path. Once the controller is operational, it handles AES decryption natively and we image the drive via standard NVMe read commands.
ADATA LEGEND Series: Mixed Controller Failures
ADATA's LEGEND line spans budget to high-end NVMe drives, each using a different controller. The LEGEND 700 & 710 use Realtek NVMe controllers. The LEGEND 850 uses the Silicon Motion SM2269XT. The LEGEND 840 uses the InnoGrit IG5220 Gen4 NVMe controller. The LEGEND 960 uses the Silicon Motion SM2264, a flagship Gen4 controller that currently lacks a dedicated PC-3000 SSD utility module; recovery on the 960 relies on board-level hardware repair to keep the original controller alive. When a LEGEND drive fails, the first step is identifying the actual controller on the PCB, because the recovery procedure & encryption status depend on which silicon is inside.
How Much Does ADATA SSD Data Recovery Cost?
ADATA SATA SSD recovery (SU800, SU650, SU760) ranges from $200 for a simple data copy to $1,200–$1,500 for NAND swap with microsoldering. ADATA NVMe recovery (XPG SX8200 Pro, GAMMIX S70 Blade, LEGEND series) ranges from $200 to $1,200–$2,500. Free evaluation, firm quote before paid work, and no data means no charge.
ADATA SATA SSD Pricing (SU800, SU650, SU760)
Simple Copy
Low complexityYour drive works, you just need the data moved off it
$200
3-5 business days
Functional drive; data transfer to new media
Rush available: +$100
File System Recovery
Low complexityYour drive isn't showing up, but it's not physically damaged
From $250
2-4 weeks
File system corruption. Visible to recovery software but not to OS
Starting price; final depends on complexity
Circuit Board Repair
Medium complexityYour drive won't power on or has shorted components
$450–$600
3-6 weeks
PCB issues: failed voltage regulators, dead PMICs, shorted capacitors
May require a donor drive (additional cost)
Firmware Recovery
Medium complexityMost CommonYour drive is detected but shows the wrong name, wrong size, or no data
$600–$900
3-6 weeks
Firmware corruption: ROM, modules, or system files corrupted
Price depends on extent of bad areas in NAND
PCB / NAND Swap
High complexityYour drive's circuit board is severely damaged and requires NAND chip transplant to a donor PCB
$1,200–$1,500
4-8 weeks
NAND swap onto donor PCB. Precision microsoldering and BGA rework required
50% deposit required; donor drive cost additional
50% deposit required
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. NAND swap requires a 50% deposit because donor parts are consumed in the attempt.
Rush fee: +$100 rush fee to move to the front of the queue.
Donor drives: 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.
Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost plus a small markup. All prices are plus applicable tax.
+$100 rush fee to move to the front of the queue. 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.
ADATA NVMe SSD Pricing (XPG, GAMMIX, LEGEND)
Simple Copy
Low complexityYour NVMe drive works, you just need the data moved off it
$200
3-5 business days
Functional drive; data transfer to new media
Rush available: +$100
File System Recovery
Low complexityYour NVMe drive isn't showing up, but it's not physically damaged
From $250
2-4 weeks
File system corruption. Visible to recovery software but not to OS
Starting price; final depends on complexity
Circuit Board Repair
Medium complexityYour NVMe drive won't power on or has shorted components
$600–$900
3-6 weeks
PCB issues: failed voltage regulators, dead PMICs, shorted capacitors
May require a donor drive (additional cost)
Firmware Recovery
Medium complexityMost CommonYour NVMe drive is detected but shows the wrong name, wrong size, or no data
$900–$1,200
3-6 weeks
Firmware corruption: ROM, modules, or system files corrupted
Price depends on extent of bad areas in NAND
PCB / NAND Swap
High complexityYour NVMe drive's circuit board is severely damaged and requires NAND chip transplant to a donor PCB
$1,200–$2,500
4-8 weeks
NAND swap onto donor PCB. Precision microsoldering and BGA rework required
50% deposit required; donor drive cost additional
50% deposit required
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. NAND swap requires a 50% deposit because donor parts are consumed in the attempt.
Rush fee: +$100 rush fee to move to the front of the queue.
Donor drives: 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.
Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost plus a small markup. All prices are plus applicable tax.
+$100 rush fee to move to the front of the queue. 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.
How Do We Recover Data from ADATA SSDs?
ADATA SSD recovery follows a four-step process: identify the controller vendor & model, diagnose the failure type, stabilize the controller through firmware intervention or board repair, & image the data. The controller determines which PC-3000 SSD utility module we use.
- 01
Identify the controller
We open PC-3000 SSD & identify the specific controller: Silicon Motion SM2258/SM2259XT (SATA), SM2262EN/SM2262G (NVMe Gen3), InnoGrit IG5236 (NVMe Gen4), or Realtek RTS5762/5763 (NVMe Gen3). ADATA uses different controllers across product lines & sometimes within the same model name, so visual PCB inspection confirms the silicon.
- 02
Diagnose the failure category
If the controller responds to PC-3000 SSD, we check firmware status, FTL integrity, & NAND health. If the controller is dead (no response at all), we use FLIR thermal imaging to locate shorted voltage regulators or failed PMICs on the PCB. An SU800 reporting 0 bytes is a firmware failure. An XPG drive that dropped off NVMe entirely is either firmware or hardware.
- 03
Repair or reconstruct firmware
For firmware failures on Silicon Motion SATA controllers, PC-3000 SSD loads a safe mode firmware module into the controller's SRAM, bypassing the corrupted boot sequence. The utility then accesses the raw NAND pages & rebuilds the FTL mapping from residual metadata. For NVMe controllers, ROM pin shorting or vendor-specific commands halt the NAND boot & force controller initialization. For hardware failures on any model, we replace shorted components using a Hakko FM-2032 on an FM-203 base station.
- 04
Image & verify
With the controller stabilized, we image the drive sector-by-sector. On Silicon Motion SATA drives, data is scrambled (XOR randomization) but not encrypted; PC-3000 SSD reverses the scrambling automatically. On InnoGrit NVMe drives, the repaired controller handles AES-256 decryption natively during the imaging pass. File system analysis verifies directory structure & individual file integrity. Data ships via nationwide mail-in service. All work is in-house at our Austin, TX lab.
Can Recovery Software Fix an ADATA SSD?
Recovery software works on ADATA SSDs with logical failures only: accidental deletion (with TRIM disabled), partition table corruption, or a formatted volume. The drive must be physically healthy, detected in BIOS with its correct model name & capacity, and responding to read commands.
Software can't fix an SU800 showing 0 bytes in BIOS, an XPG drive that dropped off the NVMe bus, or any ADATA SSD with a dead controller. These failures mean the controller isn't serving data to the operating system. No software running on the OS can talk to hardware the OS can't see.
TRIM is the other boundary. On ADATA SSDs with TRIM enabled (the default on Windows 7+ & macOS 10.6.8+), deleted files are unmapped from NAND within seconds to minutes. The controller unmaps those logical addresses and schedules garbage collection. Once garbage collection completes, no software & no lab can recover that data. If your ADATA SSD has failed (not detected, wrong capacity, or sudden death), power it down & send it for evaluation.
What Should I Do if My ADATA SSD Is Not Detected?
An ADATA SSD that doesn't appear in BIOS has a dead controller, a shorted power management component, or corrupted firmware that prevents initialization. A drive showing 0 bytes or wrong capacity is detected but locked; a drive that's completely invisible is a different failure class.
Before sending the drive, rule out the obvious. These checks take two minutes & cost nothing.
- Check the BIOS/UEFI device list. Reboot, enter BIOS (F2 or Del on most boards), and look under Storage or NVMe Configuration. If the ADATA SSD shows any model string (even with 0MB capacity), the controller is partially alive. If nothing appears at all, the controller or PMIC is dead.
- Try a different SATA port or M.2 slot. Some motherboards disable M.2 slots when specific SATA ports are populated. For SU800/SU650 SATA SSDs, try a different SATA cable & port. For XPG/LEGEND NVMe drives, try the primary M.2 slot closest to the CPU.
- Test in a USB enclosure. A USB-to-SATA or USB-to-NVMe enclosure on another computer isolates whether the issue is the drive or the motherboard.
- Stop here if the drive isn't detected anywhere. Do not run ADATA SSD Toolbox, do not attempt firmware updates, do not run secure erase. A drive with a dead controller needs board-level repair, not software troubleshooting. Power it down & send it for evaluation. Free diagnosis, no obligation.
SATA ADATA SSD board repair: $450–$600. NVMe ADATA SSD board repair: $600–$900. +$100 rush fee to move to the front of the queue.
Controllers Used in ADATA SSDs
ADATA sources controllers from five vendors: Silicon Motion (SATA & NVMe), InnoGrit (NVMe Gen4), Realtek (NVMe Gen3), Maxio Technology (late-production SATA & NVMe), & Phison (PCIe 4.0 first-generation only). Unlike Samsung, which designs its own controllers, ADATA customizes the vendor's reference firmware for branding & warranty telemetry. The underlying silicon, FTL architecture, & diagnostic mode entry points match the vendor's reference design.
Silicon Motion SATA (SM2258, SM2259XT)
The Silicon Motion SM2258 powers the ADATA SU800, ADATA's long-running mainstream SATA SSD. The SM2258 includes a DRAM buffer for FTL caching, which gives it better endurance than DRAM-less alternatives. The SU650 originally shipped with the SM2258XT (a DRAM-less variant) but later production batches switched to Realtek or Maxio controllers without changing the model name. When SM2258 or SM2258XT FTL pages degrade, the controller enters ROM mode & the drive reports 0GB, 1GB, or 1023MB capacity. PC-3000 SSD's Silicon Motion utility loads a safe mode firmware module for both controllers, bypassing the corrupted boot sequence & rebuilding the translation table from NAND residuals.
Silicon Motion NVMe (SM2262EN, SM2267XT, SM2269XT)
The SM2262EN in the XPG SX8200 Pro is a dual-core ARM NVMe Gen3 controller with DRAM. It's the same silicon behind the HP EX950 & ADATA SX8100. The SM2262G variant that appeared in later SX8200 Pro production runs is architecturally identical but uses a different firmware branch. Both are well supported by PC-3000 SSD. The LEGEND 850 uses the SM2269XT (Gen4), which is supported by PC-3000 SSD's Silicon Motion utility for safe mode entry & FTL reconstruction. The LEGEND 960 uses the SM2264, Silicon Motion's highest-end Gen4 controller with dedicated DRAM cache; the SM2264 currently lacks a PC-3000 SSD utility module, so recovery on the 960 relies on board-level hardware repair rather than firmware reconstruction.
InnoGrit NVMe (IG5236 Rainier)
The InnoGrit IG5236 (Rainier) powers the XPG GAMMIX S70 Blade, ADATA's flagship Gen4 NVMe SSD. The IG5236 uses AES-256 hardware encryption with the Media Encryption Key dynamically generated inside the controller and wrapped by a hardware-unique root key fused into the silicon during manufacture. When the IG5236 firmware panics, all cores stall & the drive disappears from the PCIe bus. The encryption makes chip-off recovery impossible; the original controller must be revived through board-level repair. Once the controller boots, it handles AES decryption natively and we image the drive via standard NVMe read commands.
Phison NVMe (PS5016-E16 in XPG GAMMIX S50)
ADATA skipped Phison's mainstream PCIe Gen3 turnkey controllers (PS5012-E12, PS5013-E13T) entirely & partnered with Phison only on the PS5016-E16 for the original XPG GAMMIX S50 (the non-Lite variant), one of the first PCIe 4.0 consumer SSDs. The SX8200 Pro, GAMMIX S11 Pro, S40G, Falcon, & Swordfish all use Silicon Motion or Realtek silicon. The S50 Lite uses the Silicon Motion SM2267, not Phison. If a customer ships an SX8200 Pro thinking it's a Phison drive based on community guesses, we identify the actual Silicon Motion SM2262EN/G on the PCB before quoting.
Realtek NVMe (RTS5762, RTS5763)
ADATA's budget NVMe drives, including the SE770G and some LEGEND 700/710 models, use Realtek NVMe controllers. Realtek is a newer entrant in the SSD controller market, and PC-3000 SSD does not currently support Realtek NVMe controllers. Recovery from Realtek-based ADATA drives focuses on board-level hardware repair to keep the original controller alive & serving data. Chip-off is not a viable fallback because Realtek controllers also implement data scrambling that requires the original silicon to reverse.
How Does Encryption Affect ADATA SSD Recovery?
ADATA SSDs have different encryption implementations depending on the controller. Understanding which model uses what encryption determines whether chip-off recovery is viable or whether the original controller must be repaired.
- SU800 & SU650 (Silicon Motion SM2258, SM2259XT)
- No always-on AES-256 hardware encryption. Data is scrambled using Silicon Motion's XOR data randomization (required for NAND cell wear leveling) but not encrypted with a controller-bound key. PC-3000 SSD reverses the scrambling automatically during imaging. Chip-off is theoretically possible but impractical because the FTL page mapping must still be reconstructed.
- XPG SX8200 Pro (Silicon Motion SM2262EN/SM2262G)
- The SM2262EN supports AES-256 hardware encryption, but implementation depends on the firmware version & whether ADATA enabled the encryption engine on that production run. Even without encryption, the Silicon Motion NVMe controller uses XOR data scrambling. The original controller is required for FTL access & descrambling in all cases.
- GAMMIX S70 Blade (InnoGrit IG5236)
- AES-256 hardware encryption with the Media Encryption Key wrapped by a hardware-unique root key fused into the controller die during manufacture. Every byte on the NAND is encrypted, even without a user-set password, and the wrapped key blob cannot be unwrapped by a different die. Chip-off yields ciphertext only. Board-level repair of the original InnoGrit controller is the only recovery path.
- LEGEND Series (Mixed Controllers)
- Encryption status depends on which controller is inside the specific LEGEND model. Silicon Motion-based LEGEND drives use XOR scrambling without always-on AES. Realtek controllers implement data scrambling. In all cases, the original controller is the safest recovery path. We identify the specific controller on the PCB before determining the recovery procedure.
ADATA SSD Product Line Reference
ADATA's SSD lineup spans budget SATA, mainstream NVMe, & high-performance Gen4 drives under both the ADATA & XPG brands. Each model uses a different third-party controller with different failure patterns, encryption implementations, & PC-3000 recovery procedures.
| Model | Interface | Controller | Encryption | Common Failure |
|---|---|---|---|---|
| SU800 | SATA | SM2258 | Scrambled (no AES) | FTL corruption, 0 bytes |
| SU650 (early) | SATA | SM2258XT / SM2259XT | Scrambled (no AES) | DRAM-less FTL failure |
| SU650 (late) / SU630 / SU635 | SATA | Maxio MAS0902 / MAS1102 | Dynamic XOR scrambling | 0.12MB capacity, BSY state |
| SU760 | SATA | Silicon Motion SATA | Scrambled (no AES) | FTL corruption |
| XPG SX8200 Pro | NVMe Gen3 | SM2262EN / SM2262G | Varies by firmware | Firmware panic, BIOS disappearance |
| XPG GAMMIX S70 Blade | NVMe Gen4 | InnoGrit IG5236 | AES-256 | Firmware panic, PCIe dropout |
| XPG GAMMIX S50 Lite | NVMe Gen4 | Silicon Motion NVMe | Scrambled | Firmware corruption |
| SE770G | NVMe Gen3 | Realtek RTS5762 | Scrambled | Controller death |
| LEGEND 700 | NVMe Gen3 | Realtek NVMe | Scrambled | Sudden death, firmware lockout |
| LEGEND 710 / LEGEND 750 | NVMe Gen3 | Maxio MAP1202 | Dynamic XOR scrambling | PCIe dropout, FTL panic |
| LEGEND 900 | NVMe Gen4 | Maxio MAP1602 | Dynamic XOR scrambling | Firmware panic |
| XPG GAMMIX S50 (original) | NVMe Gen4 | Phison PS5016-E16 | AES-256 (varies by firmware) | Firmware lockout, controller death |
| LEGEND 840 | NVMe Gen4 | InnoGrit IG5220 | Scrambled | Firmware panic |
| LEGEND 850 | NVMe Gen4 | SM2269XT | Varies | FTL corruption, firmware panic |
| LEGEND 960 | NVMe Gen4 | SM2264 | Varies | Firmware panic |
Why DRAM-less ADATA SSDs Fail Differently
The ADATA SU650, SU630, & SU635 are DRAM-less SATA SSDs. The LEGEND 850 (SM2269XT) is a DRAM-less NVMe SSD. DRAM-less means there is no dedicated DRAM cache chip on the PCB. The absence of that chip changes how the Flash Translation Layer (FTL) is managed, & it changes what happens when the drive loses power mid-write.
How DRAM-less SATA Controllers Handle the FTL
On an SU800 (SM2258 with DRAM), the entire FTL lives in the onboard DRAM cache & the controller performs address lookups at DRAM speed. On an SU650 (SM2258XT, DRAM-less), the FTL lives in a reserved metadata region of the TLC NAND. The controller uses a small internal SRAM to cache the hottest mapping entries. On a cache miss, the controller stalls the pending I/O, reads the mapping page from NAND, loads it into SRAM, & only then completes the operation. This dual-access penalty hurts 4K random I/O & means the controller is constantly paging FTL fragments back & forth between SRAM & NAND.
How HMB Differs on DRAM-less NVMe
NVMe 1.2 introduced Host Memory Buffer (HMB), which lets a DRAM-less NVMe SSD reach across the PCIe bus via DMA & borrow 16 MB to 64 MB of the host computer's system RAM. The SM2269XT in the LEGEND 850 & several other ADATA NVMe controllers use HMB to hold active FTL entries in host RAM instead of NAND. Random I/O recovers most of the speed lost to the DRAM-less design. Two caveats matter for recovery. HMB only holds metadata, not user data. HMB is also unavailable over USB bridges, so a DRAM-less ADATA NVMe drive in a USB enclosure reverts to SATA-DRAM-less-class latency. The persistent FTL still lives on the NAND; HMB is a working cache, not a store of truth.
Power Loss & Retroactive FTL Corruption
DRAM-less SATA drives are unusually fragile in the face of unexpected power loss because the controller is continuously updating FTL pages in NAND during normal operation. If a power cut interrupts an in-flight TLC or QLC program operation, neighboring pages in the same physical cell can lose their voltage margins. The next boot triggers uncorrectable LDPC errors, & the firmware enters ROM mode to protect the NAND from further damage. The drive reports 0 GB, 1 GB, 2 MB, or 1023 MB in BIOS & exposes the raw controller string ("SM2258XT", "SM2259XT") instead of the ADATA model name. On the SM2258XT, the drive may instead hang the host bus with an ATA "Keep BSY" loop. At that point, the logical path between the OS & the NAND is severed. Consumer software cannot reach the data; board-level intervention is the only path forward. SSD firmware corruption recovery starts here.
How Do Maxio Controllers in Late-Production ADATA SSDs Fail?
Between 2020 and 2023, ADATA quietly migrated several SU-series and LEGEND-series SSDs from Silicon Motion and Realtek silicon to Maxio Technology controllers. The packaging, model number, & firmware updater names did not change. A customer who buys an SU650 today & an SU650 from 2019 may receive completely different silicon with different recovery procedures. We confirm the controller by visual PCB inspection before quoting.
Maxio MAS0902 in SU630, SU635, & SU650
The MAS0902 is a 4-channel DRAM-less SATA controller. It commonly pairs with Micron B27A or B0KB 3D TLC NAND in the SU630 & SU635 alongside other TLC NAND variants used in different MAS0902 SU650 production runs. PC-3000 SSD has full Active Utility support for the MAS0902, including vendor-specific commands to enter Safe Mode & volatile loader injection into controller SRAM. The same loader family covers the MAS0902's rebrand variants (including the Lexar DM918) using Maxio reference designs.
Maxio MAS1102 in Late SU650 Production
The MAS1102 is a cost-reduced SATA controller that appears in late-production SU650 drives. ACELab lists the MAS1102 as under active development. PC-3000 SSD support is validated for specific drive variants (the ADATA SU650 240GB with MAS1102 is supported through the existing Maxio Active Utility); other MAS1102 variants are awaiting validated loaders. We confirm controller revision and validated loader availability before quoting an MAS1102 recovery, and we verify capacity by reading NAND configuration directly before launching translator reconstruction.
Maxio MAP1202 in LEGEND 710 & LEGEND 750
The MAP1202 is a DRAM-less Gen3 NVMe controller with 4 NAND channels and Host Memory Buffer support. It powers the ADATA LEGEND 710 & LEGEND 750, typically paired with 3D TLC NAND. Maxio NVMe controllers (MAP1202, MAP1602, MAP1602A) are not currently supported by PC-3000 SSD firmware utilities; recovery for these controllers requires board-level repair to bring the original silicon back to a responsive state, after which data is read out over the standard NVMe interface. The LEGEND 900 moves to the Maxio MAP1602 (PCIe 4.0).
The 0.12MB Capacity Anomaly & BSY State
Maxio FTL firmware panic produces a distinct symptom set that differs from Silicon Motion ROM-mode failures. When the MAS0902 or MAS1102 cannot validate its FTL on boot, the controller halts NAND access & reports a tiny diagnostic capacity to the host BIOS: 0.12MB, 2MB, or 0 bytes. The drive may also lose its Vendor & Product ID strings, appearing in Windows Disk Management as a generic SCSI entry with empty ATA registers. Some MAS0902 drives instead enter a continuous BSY state, holding the SATA bus busy as the controller cycles through failed NAND initialization attempts. None of these states are recoverable through software running on the host OS. Power the drive down & ship it to the lab.
Why Chip-Off Recovery Fails on Maxio
Maxio SATA controllers use a dynamic XOR scrambling algorithm where the scrambling key changes per-page, influenced by both block address & page offset within the block. PC-3000 Flash does not have a Maxio raw-reconstruction module. Desoldering the NAND from a Maxio drive yields scrambled data that cannot be reassembled without the original silicon to reverse the XOR sequence. Recovery requires the original controller to be alive & responding; if the MAS0902 die is physically destroyed by a power surge or a previous DIY repair attempt, the data is gone.
PC-3000 SSD Safe Mode Workflow for ADATA SMI Controllers
When an ADATA SU650 or SU635 enters ROM mode, the PC-3000 SSD Silicon Motion utility follows a four-step Safe Mode workflow. The procedure bypasses the corrupted on-NAND firmware & rebuilds a read-only translator in the host workstation's memory. Nothing gets written back to the degraded SSD.
- 01
Permanent technology-pin shorting
The SM2258XT & SM2259XT require a dedicated pair of test points on the PCB to remain shorted for the entire Safe Mode session, not just during power-on. The short disconnects the controller CPU from the NAND boot path, which breaks the ATA "Keep BSY" loop & blocks background garbage collection or TRIM from running while we work. Phison controllers only need a momentary short; SMI SATA drives must be kept in Safe Mode until recovery is complete.
- 02
SRAM loader injection
With the controller stuck in CPU-only mode, PC-3000 SSD reads the raw Flash ID from the NAND dies & matches the controller revision & NAND lithography to a specific ACE Lab loader image. The loader is pushed into the controller's SRAM via Vendor Specific Commands. Once loaded, the controller runs in Technology Mode: channel-level access to NAND, all writes & TRIMs blocked, ECC & scrambling logic available for the utility to drive.
- 03
Configuration-page extraction
From the NAND service area, PC-3000 SSD pulls the Configuration Page modules: bad-block tables, reallocated-sector lists, scrambling seeds, channel geometry, & wear-leveling counters. These modules define the geometry the virtual translator needs. If the CP modules themselves are corrupted, we fall back to heuristic parsing of page headers & block sequence numbers.
- 04
Virtual translator reconstruction
Every physical NAND block gets scanned. The utility reads page headers, sequence numbers, & metadata appended to each data frame, then assembles a fresh LBA-to-PBA map in the PC-3000 workstation's RAM. That virtual FTL is never written back to the ADATA drive. Once the map compiles, we open the drive in the Data Extractor module, verify the file system, & image sector-by-sector to a known-good destination. This is the standard Silicon Motion recovery path for every SMI SATA brand.
XPG SX8200 Pro Controller Swap: What It Means for Recovery
ADATA shipped early XPG SX8200 Pro units with the Silicon Motion SM2262EN, then switched some production runs to the SM2262G without updating the model name. Reviewers flagged the swap when benchmark results on new SX8200 Pro purchases didn't match the original reviews.
The SM2262EN & SM2262G share the same core dual-core ARM architecture & interface to NAND. The difference is in firmware revision branches, DRAM caching behavior, & the controller's silicon stepping. From a data recovery perspective, both controllers are supported by PC-3000 SSD's Silicon Motion NVMe utility. The recovery procedure is the same; the utility module selection differs.
When an SX8200 Pro arrives for recovery, we inspect the PCB to confirm the actual controller IC. The chip markings identify SM2262EN vs. SM2262G. This takes 30 seconds & prevents loading the wrong firmware module, which could corrupt the controller's existing state. Both variants recover at the same rate. The swap was a consumer trust issue, not a recovery obstacle.
ADATA SSD Recovery FAQ
How much does ADATA SSD data recovery cost?
ADATA SATA SSD recovery (SU800, SU650, SU760) starts at $200 for a simple copy and ranges up to $1,200–$1,500 for NAND swap. ADATA NVMe recovery (XPG SX8200 Pro, GAMMIX S70 Blade, LEGEND series) starts at $200 and ranges up to $1,200–$2,500. Free evaluation, firm quote before paid work, no data means no charge. +$100 rush fee to move to the front of the queue.
Can data recovery software fix a failed ADATA SSD?
Recovery software works on ADATA SSDs with logical failures only: accidental deletion (with TRIM disabled), partition corruption, or a formatted volume. The SSD must be physically healthy, detected in BIOS with correct model name & capacity, and responding to read commands. Software cannot communicate with a dead controller, a drive showing wrong capacity, or one that dropped off the SATA/NVMe bus. Running software scans on a failing ADATA SSD stresses degrading NAND cells and can trigger garbage collection that permanently erases data.
Why did my ADATA SSD suddenly show 0 bytes or wrong capacity?
ADATA SATA SSDs using Silicon Motion SM2258XT or SM2259XT controllers store their Flash Translation Layer in TLC NAND rather than in dedicated DRAM cache. When those NAND pages degrade beyond the controller's LDPC correction capacity, the FTL mapping corrupts and the controller enters ROM mode. The drive reports 0GB, 1GB, or 1023MB capacity in BIOS and may display a raw controller string like 'SM2258XT' instead of the ADATA model name. This is the same failure mechanism behind the SATAFIRM S11 bug on Phison controllers. PC-3000 SSD's Silicon Motion utility loads a safe mode firmware module to bypass the corrupted FTL and reconstruct the translation table from NAND residuals.
Does ADATA SSD encryption prevent data recovery?
It depends on the model and controller. ADATA SATA SSDs using Silicon Motion SM2258XT or SM2259XT use XOR data scrambling for NAND cell health but do not implement always-on AES-256 hardware encryption. PC-3000 SSD reverses the scrambling automatically. ADATA NVMe SSDs using InnoGrit IG5236 (GAMMIX S70 Blade) implement AES-256 with the Media Encryption Key wrapped by a hardware-unique root key fused into the controller silicon; chip-off recovery yields ciphertext only. NVMe drives using Silicon Motion SM2262EN (XPG SX8200 Pro) support hardware encryption but implementation varies by firmware version. In all cases, board-level repair of the original controller is the safest recovery path.
What ADATA SSD models do you recover?
We recover all ADATA consumer and XPG gaming SSDs: SATA models (SU800, SU650, SU635, SU760, SU630), NVMe models (XPG SX8200 Pro, XPG SX8100, XPG GAMMIX S70 Blade, XPG GAMMIX S50 Lite, SE770G), LEGEND series (LEGEND 700, 710, 800, 840, 850, 960), and ADATA portable SSDs (SE800, SC685). Each product line uses a different third-party controller with different failure patterns and different recovery procedures.
What should I do if my ADATA SSD is not detected?
An ADATA SSD invisible to BIOS has a dead controller, a shorted power management component, or firmware that failed to initialize. Try a different SATA port or M.2 slot first, then test in a USB enclosure on another computer. If the drive isn't detected anywhere, the failure is internal. Do not run ADATA SSD Toolbox or attempt firmware updates on an undetected drive. Power it down and send it for evaluation. SATA board repair: $450–$600. NVMe board repair: $600–$900. Free diagnosis, no obligation.
How long does ADATA SSD data recovery take?
ADATA SSD recovery timelines depend on the failure type. Simple data copies take 3-5 business days. File system recovery and firmware repairs take 2-4 weeks. Board-level circuit repair (shorted voltage regulators, dead PMICs) takes 3-6 weeks. NAND swap cases requiring microsoldering take 4-8 weeks. +$100 rush fee to move to the front of the queue to move to the front of the queue.
Did ADATA switch controllers in the XPG SX8200 Pro?
ADATA shipped early XPG SX8200 Pro units with the Silicon Motion SM2262EN controller, then silently switched some production runs to the SM2262G (a cost-reduced variant). The SM2262G has the same core architecture but uses different firmware revision branches, which affects PC-3000 SSD recovery procedures. When we receive an SX8200 Pro, we identify the actual controller on the PCB before selecting the correct Silicon Motion utility module. The controller swap doesn't affect recoverability; both variants are well supported by PC-3000 SSD.
What is HMB and why does it complicate DRAM-less ADATA SSD recovery?
Host Memory Buffer (HMB) is an NVMe 1.2 feature that lets a DRAM-less SSD borrow a small slice of the host computer's system RAM (typically 16-64 MB) over PCIe DMA to cache hot Flash Translation Layer entries. It's used in ADATA NVMe drives built around DRAM-less Silicon Motion controllers like the SM2269XT in the LEGEND 850. SATA DRAM-less ADATA drives (SU650/SU630/SU635 on SM2258XT or SM2259XT) do not have HMB; the SATA protocol doesn't allow the controller to touch host RAM, so those drives page FTL fragments between a tiny internal SRAM and reserved NAND metadata pages. Either way, the persistent FTL lives on the NAND, so unexpected power loss during a background FTL page update can corrupt metadata that was written days or weeks earlier. Recovery still requires PC-3000 SSD to enter Safe Mode on the original controller and rebuild the translator from surviving NAND residuals; HMB state is volatile and cannot be reconstructed from the drive after power loss.
Why does my ADATA SU650 show 0.12MB or 100KB capacity?
A 0.12MB or near-zero capacity reading is a known Maxio FTL firmware panic symptom on late-production SU650, SU630, or SU635 drives. ADATA shipped these models with Silicon Motion controllers in early production, then switched to Maxio MAS0902 or MAS1102 controllers in later batches without changing the model name. When the Maxio FTL fails its on-boot integrity check, the controller halts NAND access and reports a tiny diagnostic capacity (0.12MB, 2MB, or 0 bytes) to the host BIOS. The drive may also lose its Vendor and Product ID strings, appearing in Disk Management as a generic SCSI entry. Recovery on supported MAS0902 SATA variants uses PC-3000 SSD ROM pin shorting plus volatile loader injection into controller SRAM. Do not run secure erase, firmware update, or recovery software on a drive in this state; chip-off is not viable because Maxio SATA controllers use dynamic XOR scrambling that requires the original silicon to reverse.
Does ADATA's warranty cover data recovery?
No. ADATA's SSD warranty covers hardware replacement only. ADATA will send a replacement drive but does not recover data from the failed unit. If you file a warranty claim, ADATA may require the failed drive to be returned, and any data on it is gone once they receive it. Complete data recovery before pursuing a warranty claim for the hardware cost.
ADATA SSD not detected, showing 0 bytes, or dead after firmware update?
Free evaluation. SATA recovery from From $200. NVMe recovery from From $200. No data, no fee.