Alcor Micro Unknown Fa00 F W Fa04 Work Hot! -

The identifier Unknown FA00 f/w FA04 typically appears in AlcorMP mass production tools when a USB flash drive's controller is corrupted or incorrectly identified. This specific error often maps to the Alcor AU6989SN-TA or AU6989SNCS-TA controller series. Core Technical Profile

Controller Identity: The "FA00" code is not a standard model name but an internal designation often associated with the AU6989SN-TA .

Common Symptoms: The drive may show as "No Media," display 0 bytes of capacity, or fail to show a Flash ID (FID).

Flash ID Error: A common red flag is a fake or missing FID (e.g., 898989898989), which suggests a communication failure between the controller and the NAND memory chip. Recovery and Repair Procedures

To resolve the "Unknown FA00" status, you must force the controller into a state where it can be reflashed using a compatible Alcor Micro Mass Production Tool (AlcorMP).

Identify Exact Hardware: Use tools like ChipGenius or Flash Drive Information Extractor to confirm the VID (Vendor ID) and PID (Product ID). Standard Alcor values are often VID: 058F and PID: 1234. Enter Test Mode (Hardware Reset):

If the software does not detect the drive, you may need to manually short the pins on the NAND flash chip (typically pins 29-30 or 30-31) while plugging it into the USB port to force "Test Mode". Software Configuration: Run AlcorMP.exe as an administrator.

Navigate to the Setup or Driver button and enter your specific VID/PID.

Select High Level Format for a quick fix, or Low Level Format if the NAND has bad blocks. Flashing the Firmware: Ensure the tool version supports the series.

Press Start to begin the mass production process, which will rewrite the controller's firmware (FA04) and re-partition the drive. Technical Challenges

BGA vs. TSOP48: Many modern Alcor-based drives use BGA memory chips, which makes manual pin-shorting difficult compared to older TSOP48 chips.

Firmware Mismatch: Using the wrong version of AlcorMP can result in "Load Firmware Error" or permanent bricking of the controller. AI responses may include mistakes. Learn more Alcor [Fa00] Aka Au6989sn-Ta - Usb Flash Drive - Scribd

Description: [D:]USB Mass Storage Device(Generic USB F. Device Type: Mass Storage Device. Protocal Version: USB 2.00. [Link] 1/13. Alcor [Fa00] Aka Au6989sn-Ta - Usb Flash Drive - Scribd

Alcor Micro USB drive showing as an device or reporting firmware (often equivalent to the AU6989SN-TA controller), you must Mass Production Tool (MPTool) to reflash the firmware 1. Identify the Controller with ChipGenius

Before downloading software, you must confirm the hardware details. ChipGenius alcor micro unknown fa00 f w fa04 work

: This tool identifies the specific controller vendor and part number. Locate the "Flash ID" and "Controller"

: For your specific issue, it should identify as an Alcor Micro chip (e.g., Note the VID and PID : Typically, Alcor devices use Linux Mint 2. Download the Correct AlcorMP Tool

"AlcorMP" is the factory-level software used to format and repair these controllers. Find the specific version : Since your device reports firmware , you need an AlcorMP version that supports the AU6989SN-TA Sourcing the tool

: Common repositories for these tools include specialized sites like FlashDrive-Repair 3. Repair Procedure (Mass Production) : This process will permanently erase all data on the flash drive. Launch AlcorMP : Run the application as an administrator. Configure the Driver button in the tool. Enter your ) and click "Add VID/PID" Connect the Drive : Plug in your USB stick. If it isn't detected, click "Refresh (R)" Settings Adjustment (leave the password blank if prompted). "Auto Disc Size" is selected and "Lead Normal On" is ticked. "Factory Mode" for a full reset. Start Flashing

to begin the low-level format. The process is complete when the status bar turns green.

The identifier Unknown [FA00] with firmware typically refers to an Alcor Micro controller (often identified as AU6989SN-TA AU6989SNCS-TA

) that is not being correctly recognized by standard flash drive repair tools

. This status often indicates a corrupted firmware or a drive that has entered a "no media" state. Recommended Recovery Procedure

To resolve this, you generally need to use a specific version of (Mass Production Tool) or Identify the Correct Tool Version

For controllers marked as [FA00], users often recommend modified editions like AlcorMP by Nat27 which include expanded identifier databases.

is a modern firmware revision, you should look for the latest versions of ALCOR U2 MP (e.g., v23.08 or later). Manual Driver Configuration Open AlcorMP and click the

Manually enter the Vendor ID (VID) and Product ID (PID). For Alcor devices, these are frequently Add VID/PID Save InstallDrive

. This forces the utility to recognize the connected stick even if the Windows default driver is failing. Optimization Settings

If the tool detects the drive but fails with "Too many bad blocks," go to Flash Type to "Capacity optimize" and Scan Level to "Full Scan4" for the most thorough analysis. The identifier Unknown FA00 f/w FA04 typically appears

If the drive is dual-channel but the tool fails, try changing the setting to Single Channel

in the configuration, though this will halve the reported capacity. Hardware Test Mode (Last Resort)

If the software still cannot see the drive ("Unknown [FA00]"), you may need to physically short specific pins on the controller chip (Test Mode) to force it into a state where it can accept new firmware. Common Error Codes

: No Support Dual Channel (Try switching to Single Channel). : Too many bad block error (Try a deeper scan level).

For detailed tool downloads and specific firmware files, the USBDev.ru Alcor Micro Section is the primary resource for these utilities.

AlcorMP – инструкция по восстановлению флешек

AlcorMP – инструкция по восстановлению флешек – [USBDev.ru] AlcorMP – инструкция по восстановлению флешек Home. Articles on Alcor. Alcor [Fa00] Aka Au6989sn-Ta - Usb Flash Drive - Scribd

When your USB flash drive identifies as Alcor Micro Unknown FA00 F/W FA04

it typically indicates a firmware corruption or a communication error between the controller and the NAND flash memory chip

. This specific "FA00" code often appears when the system cannot retrieve the correct Flash ID (FID), resulting in a "No Media" or "0 Byte" status. Troubleshooting and Repair Guide

If your device is showing this error, you can attempt to restore it using software tools or low-level formatting. 1. Identification via ChipGenius

Before attempting a repair, confirm the exact controller model. Since "FA00" is a generic error code, use a tool like ChipGenius to find the actual Controller Part-Number AU6989SN-TA

. This will allow you to find the specific mass production (MP) tool needed for your chip. 2. Use Alcor Micro Recovery Tools

Standard Windows formatting often fails for this error. You must use specialized recovery software: AlcorMP (Mass Production Tool) How to test this feature On Linux: #

: This is the official factory software used to re-flash the controller. Look for versions that support your specific controller part number. Alcor Recovery Tool

: Some simplified versions of these tools are available on third-party repositories like the Alcor Micro USB Repair Tool on Google Drive or specialized forums like 3. Command Line Reset (Diskpart)

If the device is still recognized by Windows but shows 0 bytes, try a hard reset of the partition table: Command Prompt as an administrator. and press Enter. to find your USB's disk number. select disk X (replace X with your drive number). to wipe the partition data. create partition primary followed by format fs=fat32 quick 4. Hardware "Test Mode" (Advanced)

If software cannot detect the drive at all, the controller might be stuck. Advanced users sometimes "short" specific pins on the NAND chip (typically pins 29 and 30) while plugging it in to force the controller into , allowing recovery software to recognize it. Warning: This carries a risk of permanent hardware damage. Common Causes for FA00 Errors

The device ID USB\VID_058F&PID_0039 (often labeled as "Alcor Micro USB 2.0 Card Reader" or appearing as "Unknown Device" with hardware IDs ending in FA00, FA04, etc.) is a very common issue in laptop repair and IT maintenance.

Below is a professional blog post tailored for a tech support or IT repair blog that addresses this specific driver issue.

How to test this feature

On Linux:

# Find your device (look for Alcor Micro)
lsusb

Part 5: Common Scenarios Where "FA00 F W FA04" Appears


| Hardware Product | Typical Use Case | Working Driver Source |
|----------------|------------------|----------------------|
| Alcor AU94XX | SD/MMC card reader | Alcor Micro Generic Card Reader Driver v1.0.3.4 |
| HP Smart Card KB | Secure login (CAC/PIV) | HP SoftPaq – USB CCID (uses pid_FA04) |
| Lenovo Fingerprint Reader | Windows Hello (T440p era) | Lenovo Alcor Micro Fingerprint Driver |
| Cherry ST-1044U | e-ID authentication | Cherry USB CCID Driver (Alcor variant) |


If your device is a multi-card reader (SD/MMC/MS/xD), the working driver is usually AlcorMP.exe (for firmware updates) plus a standard USB mass storage driver. In that case, the "Unknown" appears because the device is in firmware mode – you need to flash the proper firmware using AlcorMP under Windows XP/7 compatibility mode.


D. Microsoft Update Catalog (Last Resort Search)


    

  1. Visit catalog.update.microsoft.com
    2. 

  2. Search FA04, VID_058F, or Alcor Micro
    3. 

  3. Download the CAB, extract, and manually point Windows to the INF.
    4. 



Phase 3: The "Burn" Process


The critical step is clicking the "Burn" or "Start" button in the MPTool.


    

  • The tool injects the "Burner Code" into the controller's RAM.
    • 

  • It initializes the NAND flash.
    • 

  • It rewrites the firmware configuration to the first block of the NAND.
    • 

  • Crucial Note: This process creates a new file system. It destroys all existing data. If the goal is data recovery, this is the wrong approach; professional firmware repair is needed instead of a factory reset.
    • 



Step 1: Verify the Hardware ID (Do Not Trust Labels)


Do not rely on "Alcor Micro" as a name. In Device Manager:


    

  • Right-click the unknown device → Properties → Details → Hardware Ids property.
    • 

  • You will see strings like:

      

    • USB\VID_058F&PID_FA00&REV_0100
      • 

    • USB\VID_058F&PID_FA04&REV_0001
      • 

    

    • 



Write these down. The PID_FA04 is critical. The VID_058F confirms Alcor Micro.


Step 2: Check for Microsoft Native Drivers (Windows 10/11)


If you are on Windows 10 or 11, try forcing Microsoft’s generic driver.


    

  • Right-click the unknown device → Update driver → Browse my computer → Let me pick from a list.
    • 

  • Select Smart card readers or Universal Serial Bus devices.
    • 

  • Choose Microsoft Usbccid Smartcard Reader (WUDF).
    • 

  • Click Next. If it works, your device follows CCID standards. Many FA04 devices do not.
    • 



Verifying the Fix


Once you have installed the correct driver:


    

  1. The "Unknown Device" in Device Manager should disappear.
    2. 

  2. It should be replaced by a new category usually named "Memory technology devices" or "Alcor Micro USB 2.0 Card Reader."
    3. 

  3. Insert an SD card. It should now pop up in File Explorer immediately.
    4.