Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tami need help help . flash 64gb no media
Description: [F:]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: chipYC2019
Flash ID code: 453E98B37672 - SanDisk - 1CE/Single Channel [TLC] -> Total Capacity = 64GB
Tools on web: http://dl.mydigit.net/search/?type=all&q=chipYC2019
• The “No Media / 0 bytes” symptom on a FirstChip chipYC2019-based 64 GB USB flash drive means the controller firmware cannot initialise the SanDisk TLC NAND.
• The only realistic DIY fix is to reload the controller firmware with a FirstChip Mass-Production Tool (MPTool) that explicitly supports the chipYC2019 and Flash ID 453E 98B3 76 72.
• All data will be lost; if you need the files, stop here and use a professional chip-off data-recovery lab.
Electronic cause
• VID FFFF / PID 1201 = FirstChip “factory mode” (boot-ROM only).
• Firmware area in the controller is corrupt, or bad-block map on the NAND is unreadable, so the controller never exposes logical LUNs → OS shows “No Media”.
Hardware involved
• Controller: FirstChip FC1179 / FC8308 family, marketing name chipYC2019.
• Flash: SanDisk 3-bit-per-cell (TLC) single-die, single-channel, 64 GB raw.
Why OS tools fail
• Partitioning/formatting programs talk to the logical block device; here no LBA space exists, so they only see a 0-byte phantom.
Recovery theory
• MPTool supplies a new controller firmware, scans the entire NAND, builds a new FTL (Flash Translation Layer) and creates one or more partitions.
• If the NAND has too many bad blocks or the controller ASIC is damaged, MPTool will abort with a HW error.
• Latest public tool set (Feb 2024): FC1179/YC2019 MPTool v1.0.7.2 – supports all known chipYC2019 steppings and auto-detects the SanDisk 0x453E-class flash.
• Reputable download mirrors:
– mydigit.net (Chinese electronics forum)
– usbdev.ru (Russian USB controller database)
– elektroda.com (Polish EE forum – English section has direct links)
• Trend: newer FirstChip controllers use signed firmware; chipYC2019 is still unsigned, so end-users can re-flash without an OEM key—take advantage while possible.
Preparations
• Windows 7/10/11 PC, admin rights.
• Disable AV for the flashing session.
• Plug drive directly into a USB 2.0 port on the motherboard (no hubs, no front panel).
• Remove every other USB storage device.
MPTool workflow (generic, variant names differ slightly)
a. Extract archive; run APTool.exe (or UTools.exe) as Administrator.
b. Slot view appears; your stick should be listed with VID FFFF PID 1201.
c. Enter Settings (password: 123456 or empty).
– Confirm Flash-ID auto-detects 453E98B37672 (SanDisk 64 GB TLC).
– Leave “Flash Type” on Auto; channel = Single, CE = 1.
– ECC: default (usually BCH-24 or LDPC-8).
– FullScan: enable (thorough bad-block map).
– VID/PID: you may replace with something sane (e.g. VID 0x0781, PID 0x5591 for SanDisk) or keep default.
– File-System: exFAT 32 kB cluster, single LUN.
d. Save/OK → back to main window; status changes to “Ready”.
e. Press Start. Stages: Erase → BurnFW → Verify → Scan → Format.
f. If the final column turns Green / PASS, eject safely, re-insert. Windows should show a healthy ≈ 59 GB exFAT volume.
g. Run H2testw or F3 to perform a full write/read test; abort on first error.
Typical error codes
• 0x94 – Flash ID mismatch → wrong tool version.
• 0xA1 – Too many bad blocks → worn-out NAND.
• 0x51 – Firmware burn fail → poor USB power; try another port or PC.
• MPTools are factory utilities, leaked under various licences—use at your own risk; distribution of modified packages may violate copyright.
• If the stick contains other people’s data, obtain explicit permission before erasure.
• Observe WEEE / RoHS regulations when disposing unrecoverable devices.
• Always test recovered capacity with H2testw/F3; counterfeit sticks frequently report false size and will corrupt data after 8–32 GB.
• Keep critical documents on at least two physically independent media; USB flash is consumable, not archival.
• If MPTool reports physical failure, do not keep re-flashing—it accelerates wear; decide between professional recovery or scrapping.
• Success rate for firmware-only faults ≈ 70 %.
• Recovery is destructive; if data matters, send to a lab first.
• chipYC2019 does not support secure firmware signing; future FirstChip releases (YC2022+) do—DIY flashing will become impossible.
• Investigate open-source flash emulators (FlashSim, open-FTL) for forensic reconstruction after chip-off.
• Monitor usbdev.ru forum for updated YC-series tools.
• Study LDPC vs. BCH ECC trade-offs in TLC NAND endurance for custom firmware projects.
The “No Media” state means your FirstChip chipYC2019 controller lost its firmware or NAND map. Re-flashing with a dedicated FirstChip MPTool v1.0.7.x that recognises Flash ID 453E 98B3 76 72 is the standard remedy. Follow the step-by-step procedure above; if the tool refuses to pass, the hardware is physically defective and only a professional chip-off service can help.