SSD Controller Architecture
Maxio SSD Data Recovery
Maxio Technology spun out of JMicron's SSD division in 2016 & now powers a growing share of budget NVMe drives. The MAS0902 handles SATA. The MAP1202 covers Gen3 NVMe. The MAP1602 & MAP1602A dominate the Gen4 NVMe budget market, paired almost exclusively with YMTC 232-layer TLC NAND. Every one of these controllers is DRAM-less. SATA recovery starts at From $200. NVMe starts at From $200. No diagnostic fee.
Which Maxio Controller Is in Your SSD?
Maxio ships controllers across SATA & NVMe Gen3/Gen4. All six are DRAM-less; the NVMe variants cache the Flash Translation Layer in host RAM via Host Memory Buffer (HMB). One complication: the DM918 is a rebranded MAS0902 used by Lexar. Same silicon, same PC-3000 interaction, different product label.
| Controller | Interface | DRAM | Common Drives | Failure Signature | PC-3000 Support |
|---|---|---|---|---|---|
| MAS0902 | SATA 6Gbps | No | ADATA SU650, Lexar (DM918 rebrand) | ROM mode, silicon descriptor, 0GB capacity | Full Active Utility |
| DM918 | SATA 6Gbps | No | Lexar SATA SSDs | Same as MAS0902 (rebranded silicon) | Full Active Utility (as MAS0902) |
| MAS1102 | SATA 6Gbps | No | ADATA SU650 240GB (some batches) | ROM mode, wrong capacity, firmware panic | Under development (some variants supported) |
| MAP1202 | NVMe Gen3 x4 | No (HMB) | Lexar NM620, Teamgroup MP33 (some batches) | FTL corruption, 0 bytes, HMB loss after power cut | Universal Utility + custom loaders |
| MAP1602 | NVMe Gen4 x4 | No (HMB) | Lexar NM790, Teamgroup MP44, Fanxiang S880 | FTL corruption, silicon descriptor, AES-256 encrypted NAND | Techno Mode + emerging Active Utility |
| MAP1602A | NVMe Gen4 x4 | No (HMB) | Acer Predator FA200, Silicon Power US75 | Same as MAP1602 (silicon revision, improved PMIC) | Techno Mode + emerging Active Utility |
BOM roulette warning: manufacturers swap controllers between production runs. A Teamgroup MP33 might ship with a MAP1202, a Silicon Motion SM2263XT, or a Realtek RTS5765DL. An ADATA SU650 might contain a MAS0902, MAS1102, SM2258XT, or RTS5735. The recovery engineer must physically inspect the PCB to identify the controller before selecting a PC-3000 profile.
How Do Maxio SSDs Fail?
Maxio SSD failures split into three categories: firmware corruption from power loss, controller death from electrical damage, & NAND degradation from cell wear. Firmware corruption is the most common. Every Maxio controller is DRAM-less; the NVMe variants cache their address map in your PC's RAM through Host Memory Buffer. A power cut severs that link, and the drive can't find its own data.
Firmware Corruption
The drive shows up in BIOS with its factory silicon name (e.g., "MAP1602" or "MAP1202") instead of the consumer brand. It may report 0 bytes, 2MB, or 1GB capacity. Your data is still in the NAND chips; the controller just can't read its own corrupted firmware to access it. PC-3000 SSD injects a temporary firmware loader that bypasses the corruption & provides direct NAND access. Firmware recovery on SATA Maxio drives: $600–$900. NVMe: $900–$1,200.
Controller Failure
A dead controller means no detection at all: not in BIOS, not in Disk Management, not through a USB enclosure. The MAP1602 generates sustained heat under Gen4 write loads, and budget drives (Lexar NM790, Teamgroup MP44) often ship without heatsinks. In cramped or unventilated enclosures, thermal cycling can cause BGA solder micro-fractures between the controller IC & the PCB, or PMIC burnout on the voltage regulation circuit. Recovery requires board-level repair with a Hakko FM-2032 microsoldering iron on an FM-203 base station, using FLIR thermal imaging to locate the failed component. SATA board repair: $450–$600. NVMe: $600–$900.
NAND Degradation
NAND flash cells wear out. Budget SSDs pair Maxio controllers with lower-cost TLC or QLC NAND that degrades faster. As cells wear, bit-flip rates climb until the controller's error correction can't keep up. The drive slows down, locks into read-only mode, or stops responding entirely. PC-3000 SSD can apply voltage threshold shifts during extraction to pull data from degraded cells that the controller has given up on.
When Recovery Software Works (and When It Doesn't)
Recovery software like Disk Drill, EaseUS, PhotoRec, & R-Studio works when the SSD is physically healthy but has a logical problem: accidental deletion with TRIM disabled, a corrupted partition table, or a formatted volume. These tools talk to a working controller through your operating system.
That changes when the controller is dead or the firmware is corrupted. Software can't communicate with a drive that won't power on or identify in BIOS. At that point, you need a lab with PC-3000 SSD & board-level repair capability. On modern SSDs with TRIM enabled (the default on Windows 7+ & macOS 10.6.8+), deleted files are gone within seconds to minutes. The OS sends a TRIM command telling the controller which logical blocks are free. The controller unmaps those addresses & schedules garbage collection, which erases the underlying NAND pages. No software & no lab can recover data from erased NAND cells.
How Much Does Maxio SSD Recovery Cost?
Maxio SATA SSDs (MAS0902, DM918, MAS1102) & NVMe SSDs (MAP1202, MAP1602, MAP1602A) have different pricing tiers. Cost depends on failure severity, not controller model. No diagnostic fee. No data, no recovery fee. Full SSD recovery cost breakdown. +$100 rush fee to move to the front of the queue.
SATA SSD Recovery (MAS0902, DM918, MAS1102)
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.
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.
NVMe SSD Recovery (MAP1202, MAP1602, MAP1602A)
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.
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.
Maxio Firmware Architecture: JMicron Heritage to Modern DRAM-less Design
Maxio's controller firmware descends from JMicron's SSD division, which spun off in June 2016 as Maxiotek Corporation. JMicron (founded 2001, Hsinchu, Taiwan) produced the infamous JMF602 series; those early controllers stuttered under random writes because they lacked DRAM cache. Maxio's MAS & MAP families are new silicon, but the engineering team traces back to the same lineage.
MAS Series (SATA): FTL Stored in NAND
The MAS0902 & MAS1102 are DRAM-less SATA 6Gbps controllers. Without DRAM or HMB, the Flash Translation Layer lives in dedicated service area blocks within the NAND itself. FTL updates write directly to these reserved blocks. A power cut during a write corrupts the FTL backup in NAND; on the next boot, the controller can't locate its address map & reports its silicon descriptor or 0GB capacity.
The MAS0902 uses XOR data scrambling at the page level during normal operation. This isn't AES-256 encryption; it's a data integrity measure that complicates raw NAND reads but doesn't block PC-3000. The DM918 is identical silicon rebranded for Lexar. PC-3000 SSD handles both through the same Active Utility with the same loader profiles.
MAP Series (NVMe): HMB-Dependent FTL
The MAP1202 (Gen3) & MAP1602/MAP1602A (Gen4) are DRAM-less NVMe controllers that cache the FTL in host RAM through the NVMe HMB specification (NVMe 1.2+ for MAP1202, NVMe 2.0 for MAP1602). The PCIe bus carries every address lookup between the controller & the host. A power cut severs that link; the in-flight FTL update never commits to NAND. On the next boot, the controller finds a corrupted mapping table & enters firmware panic.
The MAP1602 adds hardware AES-256 encryption with keys fused to the controller silicon. This is the critical difference for recovery. If the MAP1602 controller dies, the NAND holds only ciphertext. Chip-off (desoldering NAND chips) yields encrypted, unusable data. Board-level repair of the original controller is the only recovery path. This encryption binding applies to all MAP1602 & MAP1602A drives, including the Lexar NM790, Teamgroup MP44, & every other MAP1602-based SSD.
- Flash Translation Layer (FTL)
- The mapping table that converts logical block addresses (what your operating system requests) to physical NAND page locations (where data is stored on the flash chips). Every SSD maintains an FTL. When it corrupts, the controller can't locate any data even though the NAND still holds it.
- Host Memory Buffer (HMB)
- An NVMe specification feature (NVMe 1.2+) that lets the SSD controller borrow a slice of host system RAM as a temporary cache for FTL operations. Eliminates the cost of onboard DRAM but makes the FTL dependent on an uninterruptible PCIe connection to the host. The MAP1202, MAP1602, & MAP1602A all use HMB.
- AES-256 Hardware Encryption
- The MAP1602 & MAP1602A encrypt all data written to NAND using AES-256. The encryption key is generated during manufacturing & stored in hardware fuses on the controller die. This key never leaves the silicon. If the controller dies, the key dies with it, & the NAND contents are unreadable ciphertext.
ROM-Mode Entry & PC-3000 Workflows for Maxio Controllers
When a Maxio controller enters firmware panic, it won't respond to standard read commands. Two methods force it into a diagnostic state where PC-3000 SSD can inject a recovery loader: pin shorting & VCC undervolting bypass. The second method is the key differentiator for Maxio recovery when PCB layouts obscure the pin shorting points.
Method 1: ROM Pin Shorting
- Locate the ROM-mode shorting points on the PCB. On MAS0902 SATA boards, these are typically two through-hole pads near the controller IC, sometimes labeled in silkscreen.
- Short the designated Vout or clock pins with tweezers before applying power. The controller boots into Safe Mode using only its internal BootROM, ignoring the corrupted firmware stored in NAND.
- PC-3000 SSD recognizes the controller in ROM mode. Remove the short when prompted.
- PC-3000 injects custom microcode into the controller's SRAM. This loader contains the NAND access drivers & descrambling parameters for the specific controller/NAND combination.
- Extract data through the loader, bypassing the corrupted firmware entirely. For MAS0902/DM918, the Active Utility reverses XOR scrambling during extraction.
Method 2: VCC Undervolting Bypass
When pin locations are undocumented or the PCB layout obscures the shorting points, the recovery engineer can force Safe Mode through NAND VCC voltage manipulation. This technique works across Maxio controllers where standard pin shorting isn't practical.
- Regulate the NAND Vcc supply voltage to the 1.85V-2.17V range using external power regulation. This is below normal NAND operating voltage.
- At this voltage, the controller powers up but can't read the NAND chips. The NAND cells require higher voltage to produce valid read signals.
- The controller assumes the NAND is blank (factory state). It defaults to Safe Mode & identifies as "Generi Loader SATA Device" or equivalent generic descriptor.
- PC-3000 connects to the controller in this state. The engineer restores normal NAND voltage & injects the recovery loader into controller SRAM.
- Data extraction proceeds normally once the loader is active & NAND voltage returns to specification.
PC-3000 Utility Support by Controller Family
MAS0902 / DM918: Full Active Utility
PC-3000 SSD includes a complete Maxio Active Utility for the MAS0902 & its DM918 rebrand. The utility can switch the controller to Technological Mode, bypass damaged Service Area blocks in NAND, rebuild the translator/FTL mapping, & extract user data with XOR descrambling applied automatically. This is the same level of support that Silicon Motion SM2258XT recovery receives.
MAS1102: Partial Support (Under Development)
PC-3000 support for the MAS1102 is listed as under development by ACELab, but specific drive variants (such as the ADATA SU650 240GB with MAS1102 controller) are already supported through the existing Maxio utility. Other MAS1102 variants may require the Universal Utility with manual loader configuration.
MAP1602 / MAP1602A: Techno Mode + Emerging Active Utility
The MAP1602 has Techno Mode access in PC-3000 SSD, with an emerging Maxio Active Utility for firmware repair & FTL reconstruction. The Active Utility handles AES-256 decryption transparently when the original controller is alive & functioning in Techno Mode. For drives where the controller is dead, board-level repair must revive it first; without the original silicon, the encryption key is lost & the NAND contents are unreadable. NVMe board repair runs $600–$900.
Unsupported Variants: Universal Utility Fallback
For Maxio controllers not yet covered by a dedicated Active Utility (MAP1202, some MAS1102 variants), PC-3000 offers the Universal Utility. This provides basic diagnostic access, can upload custom loaders into drive RAM, & forces single-channel mode, which freezes garbage collection & TRIM to preserve the current NAND state during extraction.
Equipment Used
- PC-3000 SSD
- PC-3000 Portable III
- Maxio Active Utility (MAS0902/DM918)
- Hakko FM-2032 microsoldering iron
- FLIR thermal camera
- Atten 862 hot air rework station
- Zhuo Mao BGA rework station
Linux APST Bug: False Hardware Failure on Maxio NVMe SSDs
Maxio MAP1002 & MAP1602 NVMe controllers have a firmware bug that incorrectly reports power state transition times to the Linux kernel. The kernel places the controller into a deep power-save state that the controller can't wake from. The SSD disappears from the PCIe bus entirely. This looks like a dead drive, but the data is intact & the hardware is fine.
What APST Does & Why Maxio Gets It Wrong
Autonomous Power State Transition (APST) is an NVMe feature that lets the host OS move the controller into lower power states during idle periods. Each NVMe controller reports its supported power states & the time required to transition between them. The Linux kernel's NVMe driver reads these values & builds a transition table optimized for power savings.
Maxio's firmware reports transition latencies that are shorter than the controller actually needs. The kernel schedules a transition to the deepest power state, the controller enters it, & then can't complete the wake-up sequence within the reported timeframe. The NVMe driver times out waiting for the controller to respond. The kernel logs the error: nvme0: Device not ready; aborting reset, CSTS=0x1
The drive vanishes from lsblk & lspci. A reboot may or may not restore it, depending on whether the kernel re-triggers the same APST transition during the next boot.
Linux Kernel Quirks for Maxio PCI Device IDs
The Linux kernel maintains a quirk database for NVMe controllers with known bugs. Maxio controllers have two registered PCI device IDs with associated quirks:
- 1e4b:1002 (MAP1002):
NVME_QUIRK_BOGUS_NID&NVME_QUIRK_DELAY_BEFORE_CHK_RDY - 1e4b:1602 (MAP1602):
NVME_QUIRK_BOGUS_NID&NVME_QUIRK_DELAY_BEFORE_CHK_RDY
NVME_QUIRK_BOGUS_NID indicates the controller reports incorrect namespace identifiers. NVME_QUIRK_DELAY_BEFORE_CHK_RDY tells the driver to wait longer before checking controller readiness after a reset. These quirks mitigate some issues, but they don't fully address the APST wake failure.
Diagnostic Action: Test Before Shipping
If a Maxio NVMe SSD disappears on Linux, test it in Windows first. Windows handles Maxio power state transitions without the same bug. If the drive works in Windows, the data is intact & no lab recovery is needed.
For Linux-only systems, boot with this kernel parameter to disable APST: nvme_core.default_ps_max_latency_us=0
This forces all NVMe controllers to stay in the highest power state, preventing the problematic sleep transition. If the drive reappears with this parameter, your data is safe & no recovery service is needed. We include this diagnostic step in our evaluation process before billing for recovery work. Free evaluation at our Austin, TX lab or via mail-in shipping.
YMTC 232-Layer NAND: Thermal Stress & BGA Micro-Fractures
The MAP1602 is paired almost exclusively with YMTC (Yangtze Memory Technologies Corp) 232-layer 3D TLC NAND. This pairing defines the thermal profile of the drive & creates a specific failure pattern: sustained Gen4 writes generate enough heat to stress the BGA solder joints between the controller & the PCB, especially in budget drives that ship without heatsinks.
YMTC 232-layer TLC packs more transistor layers into the same die area than earlier 128-layer or 176-layer designs. Higher layer counts mean tighter thermal budgets. When the MAP1602 pushes sustained sequential writes at Gen4 speeds (up to 7,400 MB/s read, 6,500 MB/s write), the combined heat output from the controller die & the NAND packages can exceed the thermal limits of budget drives that ship without heatsinks.
Repeated thermal cycling (hot during writes, cool at idle) causes micro-fractures in the BGA solder balls that connect the controller IC to the PCB. These fractures are invisible to the naked eye. The drive may work intermittently before failing completely. FLIR thermal imaging at our Austin, TX lab reveals the fractured joints as cold spots against the controller's normal heat signature.
Repair requires reflowing the controller BGA with a Zhuo Mao precision BGA rework station or, when reflow doesn't hold, replacing the controller IC entirely if a donor is available with matching firmware revision. When the controller boots again, the encryption keys are intact & the data is accessible. Board repair on encrypted NVMe SSDs isn't a separate service from data recovery; for MAP1602 drives, it IS data recovery. NVMe board repair: $600–$900.
BOM Roulette & Verification
The MAP1602/YMTC pairing dominates the Gen4 budget NVMe market: Lexar NM790, Teamgroup MP44, Acer Predator GM7, Fanxiang S880, Netac NV7000-T, Silicon Power US75. The Acer Predator FA200 uses the MAP1602A silicon revision with improved power management.
Other drives play BOM roulette. The Lexar NM620 ships with either a MAP1202 or an InnoGrit IG5216. The Teamgroup MP33 has been found with a MAP1202, Silicon Motion SM2263XT, or Realtek RTS5765DL. Matching the correct PC-3000 utility to the actual controller on the PCB requires physical inspection under magnification, not trusting the product label. Selecting the wrong loader produces extraction failure or garbled data.
How Does HMB FTL Loss Differ from SATA FTL Corruption?
All Maxio controllers are DRAM-less, but SATA & NVMe models store the FTL differently. That difference changes both the failure pattern & the recovery timeline. SATA controllers lose their FTL backup in NAND. NVMe controllers lose their FTL in host RAM. The NAND data is intact in both cases.
SATA FTL Corruption (MAS0902, DM918, MAS1102)
SATA controllers don't have HMB. The FTL backup lives directly in reserved NAND service area blocks. A power cut during a write operation corrupts those blocks. The gap between the corrupted state & the last committed FTL is typically small (a few seconds of mapping updates). PC-3000 recovery scans the NAND, reads the spare area metadata from each page, sorts by sequence number, & rebuilds the logical map. SATA Maxio FTL reconstruction is comparable in complexity to Silicon Motion SM2258XT recovery.
NVMe HMB FTL Loss (MAP1202, MAP1602, MAP1602A)
NVMe controllers cache the active FTL in host RAM via HMB. The MAP1602 at Gen4 speeds fills its volatile write cache faster than the controller can program NAND, so a larger volume of uncommitted mapping data sits in host RAM at any given moment. A power cut severs the PCIe link. The HMB contents are lost instantly. The NAND backup of the FTL is stale by however many mapping updates were pending in host RAM.
The recovery path is the same: force Safe Mode, inject a PC-3000 loader, scan NAND spare area metadata, & rebuild the logical volume. The difference is scale. Gen4 drives operating under sustained write loads accumulate more uncommitted FTL entries in HMB than Gen3 drives do. More stale entries means more pages where the sequence number in NAND doesn't reflect the last valid write. PC-3000 reconstruction takes longer because it must reconcile a wider gap between the NAND-stored snapshot & the lost HMB state.
MAP1602 Thermal Controller Burnout
Budget MAP1602 drives (Lexar NM790, Teamgroup MP44) often ship without thermal pads or heatsinks. Under sustained sequential writes in unventilated environments, accumulated heat can burn out the PMIC or the controller IC itself. The drive goes from fully functional to completely undetectable in a single session.
This is a controller death, not a firmware failure. The drive won't appear on the PCIe bus. PC-3000 reports "no device detected." Recovery starts with FLIR thermal imaging to locate the failed component (shorted PMIC vs. dead controller), then component-level replacement using a Hakko FM-2032 on an FM-203 base station. Once the controller boots again, the AES-256 encryption keys are intact & the data is accessible. NVMe board repair: $600–$900.
Maxio Drive-to-Controller Reference
This table maps verified US-market drives to their Maxio controllers & NAND suppliers. Due to BOM roulette, some drives ship with non-Maxio controllers depending on the production batch. The controller listed is the verified Maxio variant; other batches may use different silicon.
| Drive | Controller | NAND | Encryption |
|---|---|---|---|
| Lexar NM790 | MAP1602 / MAP1602A | YMTC 232L TLC | AES-256 |
| Teamgroup MP44 | MAP1602 | YMTC 232L TLC | AES-256 |
| Acer Predator GM7 | MAP1602 | YMTC 232L TLC | AES-256 |
| Acer Predator FA200 | MAP1602A | YMTC TLC | AES-256 |
| Fanxiang S880 | MAP1602 | YMTC 232L TLC | AES-256 |
| Netac NV7000-T | MAP1602 | YMTC TLC | AES-256 |
| Silicon Power US75 | MAP1602 | YMTC 232L TLC | AES-256 |
| Lexar NM620 | MAP1202 * | Micron / YMTC TLC | Controller-dependent |
| Teamgroup MP33 | MAP1202 * | Various | Controller-dependent |
| ADATA SU650 | MAS0902 / MAS1102 * | Various | XOR scrambling |
| Lexar (DM918 models) | DM918 (= MAS0902) | Various | XOR scrambling |
* BOM roulette: these drives have been found with non-Maxio controllers (Silicon Motion SM2263XT, Realtek RTS5765DL, InnoGrit IG5216, SM2258XT, RTS5735) in other production batches.
Maxio SSD Recovery FAQ
How much does Maxio SSD data recovery cost?
Can chip-off recovery work on Maxio NVMe SSDs?
Why does my Maxio NVMe SSD disappear on Linux?
What is the difference between MAS0902 and MAP1602 recovery?
Can recovery software fix a dead Maxio SSD?
Are Maxio SSDs encrypted?
Why does my drive have a different controller than reviews show?
Is Maxio the same as JMicron?
Need Recovery for Other Devices?
M.2, U.2, PCIe NVMe drives
Mechanical HDD recovery
Soldered SSD recovery
SSD array recovery
Similar NAND flash
View complete catalog
All SSD controllers we recover: Silicon Motion, Phison, Samsung, Marvell, Realtek, InnoGrit
Maxio SSD not detected, stuck in firmware panic, or showing 0 bytes?
Free evaluation. SATA recovery from From $200. NVMe recovery from From $200. No data, no fee.