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)
: 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 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.
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
The identification of an Alcor Micro [FA00] or FA04 controller often indicates that your USB drive is in a "test mode" or has corrupted firmware, frequently seen in AU6989SN-TA chips. This specific "Unknown" status usually means the AlcorMP tool cannot communicate with the flash memory chip to identify its FID.
To resolve this and restore functionality, follow these steps using standard Alcor repair procedures: 1. Identify the Hardware
Before running repair tools, confirm the exact controller and memory chip.
Use a tool like ChipGenius or Flash Drive Information Extractor to find the VID, PID, and Controller model. If the controller is indeed an Alcor variant like , you will need a specific version of AlcorMP or FC MpTool. 2. Configure AlcorMP for "Unknown" Devices alcor micro unknown fa00 f w fa04 work
If the drive shows as "Unknown [FA00]" or "FA04" in the software, you must manually force the tool to recognize the device:
Open AlcorMP (ensure you use the version matching your chip generation). Click on the Driver button.
Enter the VID and PID of your drive (commonly 058F and 1234 for Alcor). Click Add VID/PID, then Save InstallDrive.
Re-plug the USB stick. If it still doesn't appear, press Refresh. 3. Flash the Firmware
Once detected (even as generic), you can attempt a low-level format:
Settings (Setup): You may need a password (often blank or 0000) to access the configuration.
Optimization: Choose "Capacity Optimize" for standard repair or "Speed Optimize" if you want better performance at the cost of some storage.
Start: Press the start button to begin the low-level formatting process. Note: This will erase all data. 4. Advanced Troubleshooting: Test Mode
If the software refuses to see the drive at all (remaining "Unknown"):
Manual Shorting: You may need to open the drive's casing and carefully short two pins on the controller chip while plugging it in to force Test Mode.
Alternative Tools: For stubborn "Unknown" errors on Alcor chips, try FC MpTool (specifically versions like FC_MpTool_FC8308), which is often more effective for generic or fake-capacity drives.
Warning: Using the wrong firmware version can permanently brick the device. Always try to find the Alcor Micro Tool that specifically supports your FID (Flash ID).
Do you have the VID/PID or the Flash ID (FID) from a tool like ChipGenius to narrow down the exact software version you need?
While the information provided is quite specific, the lack of context makes it challenging to offer a precise solution. If you're experiencing issues with a device related to Alcor Micro's FA00 and FA04 identifiers, following the general troubleshooting steps above may help. For a more accurate and detailed resolution, consider reaching out to technical support with the exact model numbers and a detailed description of the issue you're facing.
In the context of Alcor Micro USB controllers Go to product viewer dialog for this item.
, "FA00" and "FA04" generally refer to firmware (F/W) status codes or version signatures rather than physical model numbers. These codes often appear when a USB drive is corrupted, leading tools like AlcorMP to label the controller as "Unknown". Technical Context of FA00 and FA04
FA00 Status: Often indicates a state where the controller is recognized by the mass production tool but cannot communicate with the NAND flash memory. This may be due to a lack of a valid Flash ID (FID) or "No FID" errors, where the software reads a generic or invalid ID such as 898989898989.
Firmware FA04: This signature typically corresponds to specific versions of the Alcor AU6989SN-GT/GTC series firmware used during the recovery or manufacturing process. Recovery and Repair Procedures
If your drive is showing an "Unknown [FA00]" status, you can attempt to revive it using specific software and hardware methods:
Software Identification: Use identification tools like the Alcor UFD Manufacture Program or ChipGenius to find the exact controller model (e.g., Go to product viewer dialog for this item. ) and its VID/PID. AlcorMP Configuration: Open the correct version of AlcorMP for your chipset.
Access the Driver settings and manually enter your device's VID/PID (standard is often 058F/6387).
Select Add VID/PID and Save InstallDrive to ensure the tool can hook into the device.
Hardware Test-Mode: If the software fails to detect the drive, you may need to manually trigger "test-mode" by shorting specific pins on the controller chip while plugging it in. This forces the controller to bypass corrupted firmware and enter a state where it can be reflashed.
Firmware Reflashing: Once detected, use the AlcorMP "Start" button to re-initialize the drive. This process will rebuild the file system and apply a working firmware version. Cautionary Notes
Data Loss: Reflashing firmware using mass production tools like AlcorMP will permanently delete all data on the drive.
Counterfeit Hardware: Alcor Micro controllers are frequently used in fake or low-quality "refurbished" USB drives. These often report incorrect capacities or use non-standard firmware that makes recovery difficult.
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.
If you have recently reinstalled Windows or opened your Device Manager only to find a perplexing "Unknown Device" with the Hardware ID USB\VID_058F&PID_0039 (often referencing FA00 or FA04 in the driver details), you are not alone.
This is one of the most common "mystery devices" found on laptops from manufacturers like Acer, HP, Dell, and Lenovo. Today, we are going to demystify what this component is, why the drivers are missing, and how to get it working in minutes. When your USB flash drive identifies as Alcor
Restart-PnpDevice -InstanceId "USB\VID_058F&PID_FA00..."
After reset, the FA04 interface should reinitialize without a full unplug.
Windows includes generic drivers for mass storage (USBSTOR) and human interface devices (HID). But Alcor’s FA00/FA04 devices often implement proprietary protocols:
Additionally, OEMs like Hewlett Packard (in their USB CCID Smart Card Reader Keyboard) or Cherry (in their smart card terminals) rebadge Alcor chips. Therefore, the driver is not hosted on Alcor's public site, but buried in an OEM support package.
The Alcor Micro FA00/FA04 error is a classic example of a simple hardware component getting lost in the shuffle of modern operating systems. It is rarely a hardware failure; it is simply a communication breakdown between your SD card slot and Windows.
By identifying it as the Card Reader and grabbing the manufacturer's driver, you can clear that yellow exclamation mark and get your card reader back in action in under five minutes.
Have you encountered this issue on a specific laptop model? Let us know in the comments if the standard fix worked or if you had to use a workaround!
Troubleshooting Alcor Micro "Unknown [FA00]" Firmware Errors
The Alcor Micro Unknown [FA00] error typically appears when a flash drive's controller is bricked, or the production software cannot identify the firmware (often showing as F/W FA04 or FA05). This usually indicates a firmware mismatch or a fake drive where the reported capacity doesn't match the hardware. Why the FA00 Error Occurs
Controller Mismatch: The production tool (AlcorMP) is looking for a specific controller ID (like AU6989SN), but the chip returns a generic or corrupted "FA00" code.
Hardware Failure: Physical damage to the USB port or the flash chip itself can prevent the controller from sending a proper "Device Descriptor".
Fake Flash: Inexpensive drives often use modified firmware to report fake sizes. When these fail, they revert to a raw "Unknown" state. How to Fix the "Unknown FA00" Issue
To resolve this, you must "force" the drive into a mode where it can be reflashed with the correct firmware. Repair of damaged flash drives - elektroda.com
The error "Alcor Micro Unknown [FA00] - F/W FA04" indicates a firmware or controller issue on a USB flash drive, typically identifying it as an AU6989SN-TA or AU6989SNCS-TA controller. This error usually occurs when the drive's firmware is corrupted, leading it to report generic identifiers like VID 058F and PID 1234 instead of its actual specifications. Troubleshooting Steps
To resolve this using AlcorMP (Mass Production Tool), follow these specific actions: Configure Driver Settings: Open AlcorMP and locate the Driver button.
Manually enter the VID/PID as 058F and 1234 (or the specific IDs shown by your device). Click Add VID/PID, then select Save InstallDrive. Detection & Test-Mode: Plug the USB drive into your computer.
If the drive is not detected, you may need to manually switch it into "test-mode" (this often involves shorting specific pins on the controller chip, though this is risky and usually a last resort). Click Refresh (R) in AlcorMP if it still doesn't appear. Firmware Repair:
Once detected, use AlcorMP to perform a High Level Format or Low Level Format.
Note: Low-level formatting may significantly reduce reported capacity if the tool detects bad sectors. Common Causes
Firmware Mismatch: The controller "FA00" is often a placeholder for unknown or generic Alcor controllers.
Hardware Failure: If AlcorMP cannot identify the Flash ID (FID), the drive may have a mechanical or electrical failure that software cannot fix.
Counterfeit Hardware: Some drives reporting these generic IDs are "no-name" or fake capacity drives that use Alcor controllers to spoof storage limits.
For standard drive errors without firmware corruption, tools like DiskGenius can be used to check for bad sectors or rebuild partitions.
Do you have the Flash ID (FID) or the specific VID/PID from a tool like ChipGenius to help identify the exact firmware needed? fake HP usb flash drives - HP Support Community - 5995925
Resurrecting Your "Unknown" Alcor Micro USB: Solving the FA00/FA04 Error
Have you ever plugged in your flash drive only to be met with a cryptic "Unknown Device" message? If you’ve dug into the hardware details and found labels like or firmware
, you’ve likely hit a wall. While these codes can seem like a death sentence for your data, they are often just a sign that your Alcor Micro controller has lost its way.
Here is how to understand—and potentially fix—this specific Alcor Micro headache. What is the FA00 / FA04 Error? In many cases, an Alcor controller reporting as
doesn't actually exist as a physical model. Instead, it is often a "dummy" or error state for controllers like the AU6989SN-TA . When the firmware (FW) displays
or the FID (Flash ID) comes back as a string of nonsense (like 898989...), the drive is essentially in a "panic mode" where it can no longer communicate with its own flash memory. The Recovery Strategy [SOLVED] How to Fix the "Alcor Micro Unknown
To get the drive working again, you typically need a "Production Tool" to reflash the firmware. Identify the Real Controller : Use a tool like ChipGenius Flash Drive Information Extractor
to find the actual VID (Vendor ID) and PID (Product ID). Even if the system says "Unknown," these tools can often pull the raw hardware IDs. Find the Right AlcorMP Version : The most reliable source for these utilities is
, which hosts a massive archive of AlcorMP and FC MPTool versions. The "Driver" Trick button and manually enter your VID/PID (e.g., Add VID/PID Save InstallDrive
Unplug and re-plug your stick. This forces the utility to recognize the "Unknown" device. Using "Test Mode" (The Last Resort)
If the software still won't see the drive, you may need to enter
. This involves carefully shorting two pins on the controller chip (usually with a needle or tweezers) while plugging it in. This bypasses the corrupted firmware and forces the controller into a state where AlcorMP can finally see it and "re-burn" the correct firmware. Important Caveats : Reflashing the firmware will wipe all data
on the drive. This is a tool for repairing the hardware, not recovering files. Fake Drives
: These errors are extremely common in "fake" high-capacity drives (e.g., a "2TB" drive that is actually 8GB). Reflashing will often reveal the true, much smaller capacity.
If you're stuck on a specific Alcor chip model, check out the specialized guides at for the most compatible firmware versions. Have you successfully flashed an Alcor drive before?
Let us know which AlcorMP version worked for your specific chip!
Alcor AU6989SN-TA Firmware Issues | PDF | 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
: 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 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