Unplugging the drive while it is actively writing data corrupts the file allocation table or the controller's internal configuration blocks.
The "story" of Alcor Micro Unknown FA00 - F/W 3613 is one of a digital identity crisis. This specific error message often appears when a USB flash drive with an Alcor Micro controller suffers from a firmware failure or hardware degradation, leaving it unrecognizable to the operating system. 1. The Mysterious "FA00" Controller
Alcor Chips [Ремонт флешек на базе Alcor контроллеров]
Extract the AlcorMP ZIP archive to a folder on your local C:\ drive. Right-click AlcorMP.exe and select . alcor micro unknown fa00 - f w 3613
Since specific technical documentation for "Alcor Micro FA00 - F W 3613" is scarce (likely indicating a specific internal firmware revision for a USB flash controller or card reader), this blog post is tailored for an who have encountered this specific string in their logs or hardware tools.
Right-click the executable file (usually AlcorMP.exe ) and select .
It was a ghost in the machine. Alcor chips were supposed to be mundane—the cheap, plastic brains inside USB sticks and card readers. But the FA00 series didn’t exist in any official catalog, and the 3613 firmware was signed with a cryptographic key that predated the company itself. Unplugging the drive while it is actively writing
Download a different version of AlcorMP or locate the text database file ( AlcorMP.ini or flash list files) to insert your specific Flash ID manually. Hardware Test Mode (The Last Resort)
for your specific model (e.g., T14, X1 Carbon) and download the .
This indicates the controller hardware ID. While the software labels it "Unknown," the FA00 tag is specifically associated with the AU6989SN series of Alcor Micro controllers. Since specific technical documentation for "Alcor Micro FA00
The controller is completely frozen or stuck in a hard loop.
| Symptom | Likely Cause | Solution | |---------|--------------|----------| | MPTool shows “Not support flash” | NAND chip is dead or not in tool’s DB | Replace NAND (not worth it for cheap drives) | | MPTool hangs at “Check ID” | Short circuit or damaged controller | Discard drive | | Drive disappears after eject | Poor solder joints | Reflow controller with hot air (advanced) | | PID remains FA00 after MP | Wrong firmware version | Try older MPTool (v13.01 for 3613) | | Only 8MB capacity after repair | NAND failed, controller in ROM mode | Drive is dead |