logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Corrupted USB2DISK with VID FFFF and PID 1201 Showing 0.0G Capacity on Windows 8

khdh05283 19554 13
ADVERTISEMENT
Report a violation of the law
| New topic
  • #1 21106128
    khdh05283
    Level 2  
    Posts: 4
    Rate: 8

    Hello, I have a corrupted key and when I put it on chipgenius I get this :
    Logical drive : Y: Capacity: 0.0G
    Device ID : VID = FFFF PID = 1201
    Device SN :
    Device version : 0.00

    Device vendor : NAND
    Device model : USB2DISK
    Protocol : USB2.0
    Max power : 100mA

    Partition type : Device active :
    Aligned state : Misaligned

    Network error, the request for chipmodel failed!
    OS Version : Windows 8 Professional
  • ADVERTISEMENT
  • #2 21106320
    doggyfreestart1
    Level 1  
    Posts: 1
    Rate: 9

    >>21106128>>21106128>>21106128
    So it is probably too new for ChipGenius. If you can open the drive, then you can read the chip.
    If not, then I'd just blindly download some MP tools for the most common drives like Alcor, Chipsbank, Firstchip and so on and see which one works with the drive.
  • #3 21106717
    kaleron

    HDD and data recovery specialist  
    Posts: 7028
    Help: 957
    Rate: 2316
    And what do you want to do with it? Do you want to repair it or recover its contents?
    Company Account:
    Kaleron sp. z o. o.
    Hirszfelda 4/18, Jelcz-Laskowice, 55-231 | Tel.: 713XXXXXX (Show) | Company Website: https://kaleron.pl
  • ADVERTISEMENT
  • #5 21107185
    khdh05283
    Level 2  
    Posts: 4
    Rate: 8
    doggyfreestart1 wrote:
    If you can open the drive, then you can read the chip.

    I opened the key, here is the chip
    The image shows a disassembled USB key with visible internal circuits on a wooden surface.
    Close-up of a printed circuit board inside an opened USB flash drive.

    Added after 40 [seconds]:

    kaleron wrote:
    And what do you want to do with it? Do you want to repair it or recover its contents?

    I want to repair the key

    Added after 8 [minutes]:

    firstChip and other software don't detect my key Screenshot of FirstChip MpTools software with an open dialog window.
  • ADVERTISEMENT
  • #6 21107654
    doggyfreestart
    Level 2  
    Posts: 2
    Rate: 7

    Sorry I can't read from the photo what is written on the controller (small chip)
    Can you share this information?
  • ADVERTISEMENT
  • #9 21108504
    kaleron

    HDD and data recovery specialist  
    Posts: 7028
    Help: 957
    Rate: 2316
    khdh05283 wrote:
    is this important information?
    - yes. most important. You may want to lightly grease the chip with thermal paste - this will improve the contrast. Try reading using a magnifying glass in good light.
    Company Account:
    Kaleron sp. z o. o.
    Hirszfelda 4/18, Jelcz-Laskowice, 55-231 | Tel.: 713XXXXXX (Show) | Company Website: https://kaleron.pl
  • #11 21108484
    khdh05283
    Level 2  
    Posts: 4
    Rate: 8
    doggyfreestart wrote:
    Sorry I can't read from the photo what is written on the controller (small chip) Can you share this information?

    it's written very small, I can't see exactly, is it essential information?

    Added after 2 [hours] 53 [minutes]:

    >>21108333
    pidar wrote:
    Please test the soft from my attachment -> https://www.elektroda.pl/rtvforum/topic3956610.html#20439913

    I downloaded it, it's the first one to find the key, what do I do afterwards with the software?

    Added after 24 [minutes]:

    >>21108333Many thanks, my key is working again, even though I lost 10giga out of my 128giga in the battle.
  • #12 21109347
    pidar
    Mass storage specialist  
    Posts: 11332
    Help: 1568
    Rate: 3554
    Finally, can we see the current screen after "Refresh" with -> FirstChip_MpTools_20220601 .
  • #13 21109914
    khdh05283
    Level 2  
    Posts: 4
    Rate: 8

    pidar wrote:
    Finally, can we see the current screen after "Refresh" with -> FirstChip_MpTools_20220601 .

    yes of course Screenshot of FirstChip MPtools software used for flash memory management.
  • #14 21640557
    larryongaya
    Level 1  
    Posts: 1
    Rate: 3
    After FirstChip MPTool detects the drive—what do I do next?
| New topic
Report a violation of the law

Topic summary

✨ A user is experiencing issues with a corrupted USB2DISK device, identified by VID FFFF and PID 1201, which shows a capacity of 0.0G on Windows 8. The user seeks to repair the device rather than recover data. Responses suggest that the device may be too new for ChipGenius to recognize, and recommend using various MP tools for common drives like Alcor, Chipsbank, and Firstchip. The user has opened the device and shared images of the chip, but software tools like FirstChip do not detect it. Suggestions include using thermal paste to improve chip visibility and checking detection with specific software. Follow-up images of the device's current state were also shared.
Generated by the language model.

FAQ

TL;DR: One case regained operation with a 10 GB capacity drop; "my key is working again." Use the shared MP tool approach to reinitialize. [Elektroda, khdh05283, post #21108484]

Why it matters: This FAQ helps Windows users fix USB2DISK sticks that show 0.0G and generic IDs without diving blind into random tools.

Quick Facts

How do I fix a USB2DISK that shows VID FFFF:1201 and 0.0G in ChipGenius?

Use the MP tool shared in the thread to reinitialize the controller. In this case, running the recommended tool restored functionality. The drive returned usable, though capacity decreased by about 10 GB on a 128 GB unit. After repair, verify the drive and then format as needed. [Elektroda, khdh05283, post #21108484]

Which MP tool worked in this thread?

FirstChip_MpTools_20220601 was used, with helpers asking to show the screen after pressing Refresh. That confirms detection and readiness to proceed with initialization. Use that build if your controller matches, and follow on-screen steps carefully. [Elektroda, pidar, post #21109347]

ChipGenius shows "Network error, request for chipmodel failed"—what should I do?

Assume the device is too new or generic for the database. Open the drive to read the controller, or test MP tools from common vendors. Try Alcor, Chipsbank, and FirstChip utilities until one detects the device. This approach enabled progress in the thread. [Elektroda, doggyfreestart1, post #21106320]

FirstChip MPTool detects the drive—what do I do next?

Follow this practical flow:
  1. Connect the USB, open FirstChip_MpTools_20220601, and click Refresh.
  2. Confirm the device appears, then start the initialization/repair routine.
  3. After completion, re-plug, verify capacity, and format if needed. The helper explicitly asked for the post-Refresh screen to confirm detection. [Elektroda, pidar, post #21109347]

FirstChip and other tools don't detect my key—any workaround?

Try different vendor MP tools and builds. If detection still fails, open the case and read the controller marking to pick the correct utility. Matching the tool to the controller family is the fastest route to detection and repair. [Elektroda, doggyfreestart1, post #21106320]

Do I need the controller marking? How can I read it when it's tiny?

Yes, the marking is most important for selecting the right tool. Improve legibility with light and magnification. Expert tip: "lightly grease the chip with thermal paste - this will improve the contrast." Photograph the chip once legible and note the full code. [Elektroda, kaleron, post #21108504]

Is this thread about data recovery or just repair?

Repair only. The participants focused on restoring the stick to working order, not on extracting data. If you need data recovery, stop writing to the drive and pursue a separate recovery workflow. [Elektroda, melanchel, post #21106952]

Why did the capacity drop by about 10 GB after the fix?

In this case, the user reported the drive working again with roughly 10 GB less capacity on a 128 GB unit. Capacity change can occur after controller re-initialization. Accept the stable capacity the tool sets, then test and format. [Elektroda, khdh05283, post #21108484]

What exactly did ChipGenius report in this case?

Key outputs were: VID=FFFF, PID=1201, capacity 0.0G, protocol USB 2.0, max power 100 mA, and misaligned partition state. The OS was Windows 8 Professional. These indicators flagged a corrupted or generic-identified device. [Elektroda, khdh05283, post #21106128]

Where can I download the tool referenced by helpers?

From the helper’s attachment linked in the thread. Follow the post with the shared package and test detection with that build first. Users confirmed it was the first that found the key in this case. [Elektroda, pidar, post #21108333]

Should I post screenshots or logs for better help?

Yes. Share the FirstChip_MpTools_20220601 window after clicking Refresh. Helpers specifically asked for that view to confirm recognition and configuration before proceeding. Clear screenshots accelerate accurate guidance. [Elektroda, pidar, post #21109347]

Can I fix it without opening the drive?

You can try common MP tools first. If none detect the device, open it and read the controller marking so you can match the correct utility. This step is often decisive. [Elektroda, doggyfreestart1, post #21106320]

What if no MP tool detects the drive at all?

In this thread, initial attempts failed: "FirstChip and other software don't detect my key." A later build finally detected it. Keep testing relevant vendor utilities and versions until you get recognition. [Elektroda, khdh05283, post #21107185]

Does the Windows version matter here?

The report came from a system running Windows 8 Professional. The key symptoms and tool-based approach were observed in that environment. Adjust only if your OS blocks unsigned utilities. [Elektroda, khdh05283, post #21106128]
Generated by the language model.
ADVERTISEMENT