The USB Device ID VID FFFF / PID 1201 indicates that your flash drive's controller is currently in Test Mode or Bootloader Mode. This typically happens when the production firmware is corrupted or missing, causing the device to identify itself using the generic default values of the controller. 🛠️ Root Cause
Corrupted Firmware: Often caused by sudden power loss during a write operation or aging memory chips.
Uninitialized Controller: The drive is communicating, but it has no "instructions" on how to manage the memory storage.
Hardware Identifier: This specific VID/PID combination is almost exclusively associated with FirstChip controllers (specifically models like FC1178, FC1179, or YC2019). 🔧 Recovery Guide
Standard Windows formatting will not work because the drive currently has "0GB" capacity. You must use a Mass Production Tool (MPTool) to re-flash the firmware. 1. Identify the Exact Controller
While the VID/PID suggests FirstChip, you should confirm the specific controller model and Flash ID: Download ChipGenius or Flash Drive Information Extractor.
Run the tool and look for Controller: FirstChip (e.g., FC1178BC) and the Flash ID code. 2. Download the Correct MPTool
Go to the FirstChip FC1179/FC1178 MpTools page or USBDev.ru to find the matching software. 3. Flash the Firmware
Extract and Run: Open the MPTool executable as an Administrator.
Detection: If the drive does not appear, try a different USB port (ideally USB 2.0). Settings: usb device id vid ffff pid 1201
Click on Settings (usually password-protected; try leaving it blank or using 123456).
Set the Scan Mode to "Standard Scan" or "Factory Scan" depending on the tool version.
Start: Press Start to begin the low-level formatting and firmware restoration.
Completion: Once finished (the box should turn green), unplug and replug the drive. ⚠️ Important Considerations
Data Loss: This process is destructive. All data currently on the drive will be permanently erased.
Fake Capacity: Many "fake" high-capacity drives (e.g., a 2TB drive that is actually 16GB) use these controllers. Flashing the drive will likely restore it to its true capacity.
Hardware Failure: If the MPTool cannot read the Flash ID, the memory chip itself may be physically dead, and software recovery will not be possible.
If you'd like to proceed, let me know the Controller Model and Flash ID reported by ChipGenius so I can help you find the exact version of the tool you need.
FirstChip FC1178BC MpTools V1.0.2.10 2018-04 ... - USBDev.ru The USB Device ID VID FFFF / PID
The USB Device ID VID FFFF PID 1201 typically identifies a generic USB mass storage device often utilizing a FirstChip (FC) controller, such as the FC1178BC.
The Vendor ID (VID) FFFF is an unofficial, frequently obsolete code often associated with Taiwan OEM manufacturers or unbranded, generic flash drives. Because this ID is commonly used by low-cost or "no-name" vendors, these devices are sometimes prone to firmware corruption or capacity reporting issues. Identifying the Device
USB devices use 16-bit identifiers to communicate with a host:
Vendor ID (VID): Identifies the company that manufactured the hardware.
Product ID (PID): Identifies the specific model or product type. To confirm these IDs on your own system: HDD GURU FORUMS • View topic - FirstChip FC2279 BA7
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: Step 2: Windows Registry Sweep (via Device Manager)
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:
USB Flash Drive Speed Tests - VID = ffff, PID = 1201 - NirSoft
The USB Vendor ID (VID) 0xFFFF and Product ID (PID) 0x1201 combination represents a unique and noteworthy case in USB device identification. Unlike standard commercially assigned VIDs (managed by the USB Implementers Forum), 0xFFFF falls into a reserved or “invalid” vendor ID range. This paper provides a comprehensive analysis of the devices bearing this VID/PID pair, their common origins (primarily Chinese system-on-chip vendors), their typical functions (UART, JTAG, or flash programming interfaces), associated drivers (especially usbser.sys / ch340.sys), security implications, and troubleshooting methodologies.
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.
If device is a CH340 clone, use the official WCH driver but modify the .inf:
[CH341SER.NT]
%USB\VID_1A86&PID_7523.DeviceDesc%=CH341SER, USB\VID_1A86&PID_7523
; Add this line:
%USB\VID_FFFF&PID_1201.DeviceDesc%=CH341SER, USB\VID_FFFF&PID_1201
Before solving the problem, we must understand the language. USB devices do not identify themselves by brand names like "SanDisk" or "Sony" to the operating system. Instead, they use two unique identifiers:
VID_0781 belongs to SanDisk, VID_13FE belongs to Kingston, and VID_0BDA belongs to Realtek.