Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamDescription: [J:]USB Mass Storage Device(NAND USB2DISK)
Device Type: Mass Storage Device
Protocal Version: USB 2.00
Current Speed: High Speed
Max Current: 100mA
USB Device ID: VID = FFFF PID = 1201
Device Revision: 0000
Manufacturer: NAND
Product Model: USB2DISK
Product Revision: 0.00
Controller Vendor: FirstChip
Controller Part-Number: FC1178BC
Flash ID code: 2CC30832 - Micron - 1CE/Single Channel [TLC] -> Total Capacity = 1GB
Tools on web: http://dl.mydigit.net/search/?type=all&q=FC1178BC
Possible Flash Part-Number
----------------------------
Unknown
Flash ID mapping table
----------------------------
[Channel 0] [Channel 1]
2CC30832EA30 --------
-------- --------
-------- --------
-------- --------
-------- --------
-------- --------
-------- --------
-------- --------
• The stick is not a genuine 32 GB device: the Micron NAND identified (Flash-ID 2CC30832) is a 1 Gbit = 128 MB die, organised as a single CE on one channel; even if eight dice were fitted, the maximum would be 1 GB, not 32 GB.
• VID = FFFF / PID = 1201 tells us the FirstChip FC1178BC controller has fallen back to its boot-loader/service mode because the production firmware is missing or corrupt.
• Result: the drive enumerates as “NAND USB2DISK” with 0 B capacity. It can only be revived (and then only to its real capacity, ≈1 GB) by low-level re-initialisation with a FirstChip Mass-Production Tool (MPTool). If the tool cannot complete, the flash or the controller is physically defective and the device is e-waste.
Controller state
• FC1178BC presents FFFF:1201 when no valid firmware block is found in NAND.
• USB 2.00 high-speed, 100 mA current draw – typical for this controller family.
Flash identification
Flash-ID : 2C C3 08 32
Manufacturer : Micron
Density code : 0x08 ➔ 1 Gbit (128 MiB)
Organisation : TLC, 1 CE, single channelWith one die fitted the absolute maximum user space after ECC and FTL is ≈117 MB. Even eight identical dice would yield ≈1 GB, far below 32 GB.
Why 0 GB now?
a. Counterfeit drives are shipped with a “patched” firmware that lies about capacity.
b. The moment more data are written than the real NAND can hold the FTL crashes, bad blocks rise sharply, the controller reboots into boot-loader, and the stick becomes 0 B.
Evidence of counterfeiting
• Wrong capacity by two orders of magnitude.
• Generic descriptors (“NAND”, “USB2DISK”).
• Unsigned device revision 0000.
• GoodRam’s genuine VID is 0951 (Kingston OEM) or 13FE (Phison OEM), never FFFF.
• Fake-capacity USB drives remain common on auction sites and marketplaces; FC1178/1179 controllers are a popular choice because their MPTool allows arbitrary logical capacity declarations.
• Since 2022 most reputable vendors moved to USB 3.x native controllers (Phison, Silicon Motion) that use signed firmware, making large-scale faking harder, but legacy USB 2.0 parts are still recycled.
• Trend: new Windows builds (Win 11 22H2+) flag VID = FFFF mass-storage devices and inject a warning in the event log.
Low-level recovery sequence (tested on FC1178/1179 B/C revisions):
Tools
• “FirstChipMpTools***.exe” – versions 1.0.4.8 … 1.0.6.0 usually cover FC1178BC.
• Download only from long-standing archives (e.g. usbdev.ru, dl.mydigit.net) to minimise malware risk; verify SHA-256.
Host PC prerequisites
• Windows 7 ×64 or Windows 10 21H2.
• Native USB 2.0 root-port, no hubs.
• Run MPTool as Administrator; disable antivirus realtime scanning to avoid USB resets.
Procedure
Typical failure codes
• 0xF0 – NAND bad; retry with ScanLevel 3; if persists, flash is worn-out.
• 0xD4 – unmatched FlashID; use different MPTool build.
• Selling storage devices that intentionally misreport capacity violates consumer-protection law in most jurisdictions (FTC in US, EU Directive 2005/29/EC, etc.).
• Reverse-engineering or re-flashing third-party firmware is legal for personal repair in the vast majority of countries (right-to-repair), but redistribution of proprietary firmware binaries may infringe copyrights.
• Never re-label or resell a down-rated 1 GB device as 32 GB: that would constitute fraud.
• Always test new flash media with H2testw, F3 or f3probe before first serious use.
• Buy only from reputable distributors; verify VID/PID with e.g. lsusb or ChipGenius.
• Keep flash drives powered through controlled shutdowns; abrupt removal during write is the primary trigger for FTL corruption.
• For truly critical data storage, prefer brand-name USB 3.x sticks with SLC/MLC or small-die TLC and controllers with robust LDPC ECC (Phison E13T, SiliconMotion SM3282, etc.).
• Recovery is not guaranteed: if the NAND has developed many uncorrectable columns the MPTool will fail permanently.
• Even after a “successful” rebuild the endurance of cheap TLC in a single-CE design is very low (≤300 program/erase cycles).
• Some FC1178BC boards wire a write-protect pad; accidental short or corrosion on that pad also forces boot-loader mode.
• Investigate secure-boot variants of modern USB controllers and how they mitigate fake-capacity programming.
• Explore open-source FTL projects (e.g., u-nand, openftl) for educational purposes.
• Study forensic techniques to detect tampered capacity without opening the enclosure (scatter-write analysis, SMART-style telemetry).
Your “GoodRam 32 GB” stick actually holds a single 1 Gbit Micron TLC die. The FirstChip FC1178BC controller lost or never had valid firmware and now enumerates with VID = FFFF, PID = 1201, giving 0 B capacity. The only remedy is to re-flash the controller with a FirstChip MPTool, which will reveal the true usable size (≈1 GB). If that fails, the hardware is defective and should be discarded. For dependable storage, replace the device with a reputable, correctly-specified flash drive.