The USB device ID VID: FFFF, PID: 1201 typically indicates a corrupted or uninitialized USB flash drive controller , rather than a specific brand or manufacturer.
While these IDs are not assigned to a legitimate manufacturer in official databases like Linux usb.ids , they are frequently seen in the following scenarios: Firmware Failure:
The drive's controller has entered a "fail-safe" or "test" mode because it cannot load its primary firmware or communicate with the NAND memory chip. Hardware Issues: This ID often appears on drives using the controller (e.g., FirstChip) or some
models when they become unreadable or "brick" due to electrical failure or poor physical contact. Generic/Fake Drives:
Many low-quality or "fake" USB sticks default to this generic VID/PID pair when they fail. Potential Fixes
If you are seeing this ID, your computer likely recognizes the device as a "USB Mass Storage Device" with 0MB capacity . You can try: Mass Production Tools (MPTools): Use specialized software like ChipGenius
to identify the exact controller (e.g., Alcor, FirstChip, or Phison) and then find the corresponding "MPTool" to re-flash the firmware. Uninstall and Re-detect: Right-click the device in Device Manager
, select "Uninstall," and then "Scan for hardware changes" to force Windows to re-attempt a handshake. Physical Check:
Try a different USB port or a different computer to rule out power-supply issues.
If these steps fail and the capacity remains 0MB, the drive has likely suffered a permanent hardware failure. specific recovery tool for the controller chip inside your drive? usb device id vid ffff pid 1201
The USB device with almost universally identified as a generic, unbranded, or "Taiwan OEM" USB flash drive
. In many cases, these specific IDs appear when a name-brand drive (like SanDisk) has suffered a firmware corruption
or hardware failure, causing it to default to these generic controller identifiers. Device Identification & Technical Specs Manufacturer/Vendor:
Often listed as "Taiwan OEM" (now considered obsolete) or "NAND". Controller Vendor: Most frequently uses a controller (specifically model Product Name:
Commonly appears as "USB Mass Storage Device," "NAND USB2DISK," or "Disk 2.0". USB 2.0 (High Speed) with a max current of 100mA. Common Issues & "Red Flags"
If your computer is showing these IDs, it often indicates one of three scenarios: Firmware Corruption:
The drive's internal controller has lost its identity. Users often report the drive appearing as "removable" but with "no media" or a size of 0 bytes. Counterfeit/Fake Hardware:
These IDs are frequently associated with "fake" high-capacity drives (e.g., a 2TB drive that is actually only 16GB). Hardware Failure: A physically damaged NAND flash chip or controller. Recommended Fixes
If the drive is inaccessible, the following steps are typically recommended by tech communities: The USB device ID VID: FFFF, PID: 1201
USB Flash Drive Speed Tests - VID = ffff, PID = 1201 - NirSoft
The USB Device ID VID FFFF PID 1201 typically indicates a generic or unbranded USB flash drive that is either in a "factory" state or has corrupted firmware. What the ID Means
VID FFFF (Vendor ID): This is not a registered manufacturer. It is often used by Taiwan OEM manufacturers or as a placeholder when a device has no production firmware.
PID 1201 (Product ID): This ID is frequently associated with drives using FirstChip controllers (specifically models like FC1178BC, FC1179, or YC2019).
Common Name: These devices often identify themselves as "NAND USB2DISK" with a capacity that might show as 0GB when failing. Why You Are Seeing This
If your drive was previously working and now shows this ID, it usually means:
Firmware Corruption: The controller has lost its production firmware (often after a power loss) and has reverted to a "bootloader" or "test" mode.
Counterfeit/Fake Drive: Many low-cost or counterfeit drives use these generic IDs. They may claim a high capacity (like 128GB) but actually contain much smaller NAND chips.
Hardware Failure: While the controller might still be communicating (allowing the PC to see the ID), the NAND flash chip itself may be damaged. How to Fix or Recover the Drive Test immediately with H2testw (Windows) or F3 (Linux/Mac)
Because the drive is in a low-level state, standard Windows formatting usually fails. You typically need a Mass Production Tool (MPTool) specific to the controller.
Identify the Controller: Use a tool like ChipGenius or Flash Drive Information Extractor to confirm if the controller is indeed a FirstChip (e.g., FC1178 or FC1179).
Find the MPTool: Look for FirstChip MpTools (e.g., V1.0.5.2) on sites like USBDev.ru or FlashBoot.ru.
Re-flash the Firmware: Running the MPTool can "re-manufacture" the drive, mapping out bad sectors and restoring a usable capacity.
Note: This process will permanently erase all data on the drive. Warning on Data Safety
FirstChip FC1178BC MpTools V1.0.2.10 2018-04 ... - USBDev.ru
The best fix is avoiding VID_FFFF entirely. Here is how to spot fake drives before they fail:
Rarely, the issue is not the device but the host controller. A malfunctioning USB root hub on your motherboard can scramble incoming data streams. However, if you test the device on another computer and still see VID_FFFF, the device itself is the culprit.