The controller chip gets confused when the drive is unplugged incorrectly or suffers a power surge. It forgets how to talk to the memory cells. The code [FA00] is a generic error name, and F/W 3613 is the version number of the broken software inside the chip. Step 1: Use Diskpart to Clear the Drive
Insert the faulty Alcor Micro flash drive into a directly connected to your motherboard. Avoid using front-panel case ports or unpowered external hubs.
Warning: This section is for technicians only. Proceed at your own risk.
If you run into any road blocks while configuring the utility, tell me (e.g., 50400, 30700) AlcorMP shows, or provide the Flash ID (FID) string from ChipGenius. I can give you the exact settings changes to fix it! Share public link alcor micro unknown fa00 f w 3613 updated
The 058F:3613 USB ID is infamous. Unlike standard webcams or keyboards, Alcor readers do not have a unified driver. Windows 10 and 11 often misidentify this chip or refuse to load a driver because the default USBSTOR.SYS (Microsoft’s generic storage driver) fails the validation check against the chip's response.
Look for "L74" or "D3/eD3" specialized editions if you are using high-capacity Transcend or generic 32GB/64GB drives. : Run the AlcorMP utility as an Administrator.
Click , then click Save InstallDrive to force-register the controller. Step 2: Connect the Drive The controller chip gets confused when the drive
[ Unpack AlcorMP ] ──> [ Run AlcorMP.exe as Admin ] ──> [ Click Setup ] │ ▼ [ Select Flash Type / ECC ] <── [ Configure VID/PID ] <── [ Password: Empty ] Right-click AlcorMP.exe and select .
| Error Message | What It Means | Potential Solutions | | :--- | :--- | :--- | | | The tool cannot identify or communicate with your flash memory chip. | Verify your Flash ID code against the tool's database; try a different AlcorMP version; check for physical chip damage. | | Drive Not Detected | The computer is not reading the drive at all. | Try a different USB port or computer; short the controller's test points; consider more advanced hardware repair. | | Erroneous Capacity | The tool detects a larger capacity than expected (e.g., 64GB vs 32GB). | Incorrect settings. You may need to manually adjust the capacity settings within the AlcorMP tool. | | Tool Crashes or Stalls | The process hangs or ends unexpectedly. | Re-run the tool; try a different version; ensure no other USB devices are interfering; run on a different PC. |
If your telemetry data points to a dual-channel memory structure but fails during execution, switch this parameter to Single Channel . While this reduces the overall final capacity of the drive by half, it safely isolates the broken physical memory die and allows the remaining half to work. Step 1: Use Diskpart to Clear the Drive
series, which supports various NAND flash types, including BGA and TSOP48 form factors. II. Identification of the "Unknown" State
Older tutorials recommend outdated tools like AlcorMP version 8.x or 6.x. However, for firmware 3613 , you need versions. Using the wrong version will result in a "Device Not Match" or "Not Ready" error.
If the drive is completely dead and not even detected by ChipGenius, you may need to disassemble the plastic casing and manually short-circuit two data pins on the controller chip while plugging it in. This forces the chip into "ROM mode," allowing the MPTool to see it and force a firmware update. Conclusion
The baseline firmware version or configuration signature programmed into the controller chip during manufacturing.