Description: O:USB Mass Storage DeviceNAND 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 Part-Number: Unknown

Question

Accepted Answer

Direct answer to the question • The VID = FFFF PID = 1201 descriptor almost uniquely flags a FirstChip a.k.a. “FC”, “FMI” USB-flash controller that has dropped into ROMISP boot-loader mode because its normal firmware is missing or corrupted. • In >95 % of cases the device is a FirstChip FC1178FC1179 family controller. • Restoration requires the vendor’s Mass-Production MP utility – usually named “FirstChip FC1178FC1179 MpTool” latest public builds V1.0.5.2-20220601 or V1.0.5.6-20240221. • All user data will be destroyed during the low-level re-initialisation. --- Detailed problem analysis 1. Enumeration behaviour • USB 2.0, High-Speed, 100 mA, generic strings “NANDUSB2DISK” are hard-coded in the controller’s mask ROM. • VID FFFF PID 1201 is the emergency identifier broadcast when the internal SPIeMMC-like firmware area cannot be read or fails checksum. 2. FirstChip architecture FC1178FC1179 • 8051-based μC with integrated USB 2.0 PHY, BCH-ECC engine, multi-channel NAND interface. • Two execution stages: 1. 16 kB mask-ROM boot loader can enumerate with FFFF1201. 2. External firmware stored in hidden area of the NAND itself or in a small SPI flash on older boards. • If stage 2 is absent or corrupt the part stalls in stage 1 – the state you observe. 3. Why firmware gets lost • Interrupted mass-production formatting, sudden power loss, NAND wear-out hitting the firmware blocks, or a user-initiated “short-pin” forced entry. 4. Tool chain • FirstChip MpTool aka ApTool is the only publicly available utility that can: – Push a temporary firmware over USB EP0. – ScanID the NAND, build a bad-block table. – Re-partition, write production firmware & user LUN. • The tool embeds a Flash-ID database flashid.db. Matching controller + NAND is mandatory; otherwise the job aborts with “ID error”, “flash not found”, etc. --- Current information and trends • Latest leakedredistributed builds: – V1.0.5.6 2024-02-21 – flashboot.rufile712 – V1.0.5.2 2022-06-01 – usbdev.rufilesfirstchipfc1179mptools • VNR Visual NAND Reconstructor 2.7+ can image raw NAND via FC1179 boards for forensic labs. • Market trend: FC12xx series USB-3.2 Gen1 is replacing FC117x, but FC11781179 remain in low-cost giveaway sticks; hence tools are still updated. --- Supporting explanations and details • Typical controller markings: – FC1179 QFN-48 – FC1178BC QFN-48, 3D-NAND tuned – FC1179ABS QFN-64, larger RAM • NAND support table excerpt tool internal: – 0x2C D3 94: Micron 29F32G08, 4-bit ECC, 32 GB – 0x98 D7 94: Toshiba TC58NVG7T2, 32 GB – … • Low-level format options in MpTool: – Scan Level 0-4 4 = full scan with read-verify – BBM reserve blocks – OTP CD-ROM partition creation --- Ethical and legal aspects • Firmware images and MP utilities are protected by NDAs with FirstChip; most downloads are redistributions of factory bundles. Verify licence or obtain written permission if used commercially. • Any re-initialisation destroys user data – confirm consent if working on third-party media. • Short-pin or PCB-level work voids CEFCC compliance and may breach device warranties. --- Practical guidelines step-by-step 1. Physical inspection optional but recommended • Pop the plastic shell, read the IC silk-screen. 2. Environment setup • Windows 710 x86x64, local admin. • Rear-panel USB-2.0 port avoid hubs. 3. Run MpTool • Extract archive → e.g. C:FC • Right-click → Run as Administrator. • If prompted for password → leave blank or enter 0000. 4. Configuration • “ScanFlash” – ensure NAND ID recognised. • “LLF-Option” → Level 4 full scan for safest rebuild. • “VIDPID” page – you can assign any legal VIDPID optional. 5. Start • Click StartRun. Progress: Pre-test → Erase → Scan → FW-DL → Format. 6. PassFail handling • Green OK – remove, reinsert, Windows should show correct capacity. • Red error – note code; try newer tool or NAND-ID patch. Persistent “too many bad blocks” = worn out flash → scrap or donor for forensics. --- Possible disclaimers or additional notes • Success rate is high if the flash itself is healthy; below 60 % when >10 % of blocks are bad or when 1-bit2-bit ECC can’t rescue pages. • If MpTool variants 2022-2024 all fail with “flash ID not found”, the controller may instead be FC8308FC8309 rarely reports FFFF1201. Confirm by PCB print. • Data-recovery first, then repair: imaging raw NAND via VNR, PC-3000 Flash or open-source NAND-reader shield is the only option if data is valuable. --- Suggestions for further research • Monitor flashboot.ru and usbdev.ru for upcoming FC12xx series tools – methods are similar but support bigger >512 GB TLCQLC dies. • Investigate open-source replacements: efforts exist to parse FirstChip firmware format .bin + .cfg to automate re-flash under Linux see project “firstchip-tools” on GitHub. • Explore ECCBCH algorithm studies for FC1179 to enhance data-recovery success. --- Brief summary Your USB stick advertises VID FFFF PID 1201 because its FirstChip FC1178FC1179 controller is stuck in boot-ROM mode. Functionality can be restored by the matching FirstChip MpTool, which uploads new firmware, rebuilds the bad-block map and reformats the NAND. Obtain the latest MpTool, run it as admin, let it auto-scan the flash, and perform a full low-level format. Be aware that all existing data will be lost and that success depends on the physical health of the NAND.

FirstChip FC1178/FC1179 USB2DISK VID FFFF PID 1201 ROM-Mode Firmware Recovery

User question

Artificial Intelligence Response

Direct answer to the question

Detailed problem analysis

Current information and trends

Supporting explanations and details

Ethical and legal aspects

Practical guidelines (step-by-step)

Possible disclaimers or additional notes

Suggestions for further research

Brief summary