Alcor Micro USB Flash Controller FA00 F/W 87B9 Repair and Firmware Details

Detailed problem analysis

• Why you see this string
  • Alcor controllers (AU698x family and derivatives) often enumerate with generic strings. Community tools parse their descriptors and print an “Unknown [FA00]” tag when the exact sub‑model cannot be resolved. The same output line—with varying firmware codes—appears across multiple cases. (usbdev.ru)
• What it means technically
  • FA00 is not a consumer part number; it’s an internal/placeholder identifier observed in dumps and MP tool INI files for the AU698x family. The four‑hex firmware tag (here 87B9) identifies the controller’s firmware branch/build that governs NAND timings, ECC, and the FTL (flash‑translation layer). (usbdev.ru)
• Symptoms that go with this
  • “No media,” wrong capacity, intermittent detection, or write‑protect—classic signs of FTL/firmware corruption on Alcor sticks. These reports accompany FA00 devices and are typically resolved only via the Alcor MP process. (elektroda.com)
• Why OS formatters fail
  • The defect is below the file system: the controller’s FTL map and parameters live inside the MCU and are rebuilt only by the vendor MP tool. OS‑level formats don’t touch those structures. Community guides and case write‑ups stress the need for AlcorMP for FA00. (elektroda.com)

Current information and trends

• Proven FA00 support exists in AlcorMP v16.09.30.00 (and other builds that list FA00 in Setting/Parameter INI). Community mirrors continue to host these versions. (flashboot.ru)
• Forums show ongoing FA00 cases through 2024–2025 with the same output pattern and successful re‑initialization using recent Alcor MP builds; newer U2 MP builds target USB 3.x parts but legacy FA00 still appears in tool INIs. (usbdev.ru)

Supporting explanations and details

• How to confirm you’re in the Alcor FA00 case
  • Plug the drive and run ChipGenius/FDIE; look for:
  • Controller Vendor: Alcor Micro; Controller Part‑Number: Unknown [FA00] – F/W 87B9
  • VID/PID commonly 058F:6387 or 058F:1234
  • If you open the stick, the controller package often reads AU6989SN/variants. (usbdev.ru)
• Why some posts say “FA00 doesn’t exist”
  • That statement means “FA00 isn’t a public model name,” not that your device is fake. It’s a placeholder group identifier that Alcor tools and community databases use. (usbdev.ru)
• Distinguishing from other interpretations
  • Not an inverter/emergency‑stop code: those systems don’t present bracketed “Controller Part‑Number” lines with “F/W xxxx.”
  • Not a vintage ROM address/checksum: the bracketed FA00 + “F/W xxxx” string aligns with USB flash diagnostics, not ROM listings. Multiple independent examples document the exact wording for Alcor sticks. (usbdev.ru)

Ethical and legal aspects

• MP tools are factory utilities; public builds are often leaked and may be subject to licensing restrictions and malware‑risk. Download only from reputable archives and scan before use. Data will be erased; obtain owner consent. (flashboot.ru)

Practical guidelines

• If data recovery is required
  • Stop. MP tools rebuild the translator and typically zero your chances of later NAND‑level recovery. Engage a data‑recovery lab first. Community experts repeatedly warn about this for FirstChip/Alcor alike. (reddit.com)
• If you just want a working USB stick
  1. Identify: Confirm “Unknown [FA00] – F/W 87B9” and record VID/PID and Flash ID.
  2. Tool: Obtain an AlcorMP build that lists FA00 support (example: v16.09.30.00). (flashboot.ru)
  3. Setup: Use a rear‑panel USB 2.0 port on a Windows PC, run as Administrator.
  4. Configure: In AlcorMP Setup, keep original VID/PID, select Full Scan/Capacity‑Optimize; leave NAND/ECC to Auto unless instructed otherwise by a known recipe. (elektroda.com)
  5. Run: Start a full scan. Success shows green; failure/red typically indicates worn NAND or a bad controller—replace the device. (elektroda.com)
  6. Verify: After re‑init, validate capacity with H2testw/F3 and discard if bad‑block count is high.
• Expected outcomes
  • The device may return with its true physical capacity, which can be lower than the label if the stick was mis‑programmed or counterfeit—this is commonly reported. (reddit.com)

Possible disclaimers or additional notes

• We did not find a public case that shows the exact firmware tag “87B9,” but the FA00 format with other firmware codes (F103, FA04, C2DE, 3623, etc.) is well‑documented; 87B9 fits the same pattern. (usbdev.ru)
• If your device is not a USB flash drive, please provide context (equipment type, screen/log excerpt). The interpretation would change.

Suggestions for further research

• If you need a specific, known‑good AlcorMP INI for your NAND Flash ID, share your tool readout (VID/PID, Flash ID). Community recipes are organized by Flash ID tables on usbdev/flashboot threads. (usbdev.ru)

Brief summary

• “[FA00] – F/W 87B9” almost certainly comes from an Alcor Micro USB flash controller status line: FA00 = placeholder controller family; F/W 87B9 = firmware build. To repair a failing stick, use an AlcorMP build that supports FA00 and run a full capacity‑optimize re‑init (all data lost). If you need data, do not run MP tools—seek recovery first. (usbdev.ru)

If you can paste the full diagnostic output (VID/PID, Flash ID, model strings) or a photo of the controller package, I can pick the exact AlcorMP build and settings for your case.