Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamavec quel logiciel je dois utiliser pour reparer ma cle 32 go
Description: [E:]Dispositif de stockage de masse USB(Generic Flash Disk)
Device Type: Mass Storage Device
Protocal Version: USB 2.00
Current Speed: High Speed
Max Current: 200mA
USB Device ID: VID = 058F PID = 6387
Serial Number: C45A1D61
Device Vendor: Generic
Device Name: Mass Storage
Device Revision: 0100
Manufacturer: Generic
Product Model: Flash Disk
Product Revision: 8.07
Controller Vendor: Alcor Micro
Controller Part-Number: Unknown [FA00] - F/W F103
Tools on web: http://dl.mydigit.net/special/up/alcor.html
• Use AlcorMP (Alcor Mass-Production Tool) / AlcorMP_UFD_F103 – the factory utility that supports the Alcor Micro FA00 controller and firmware branch F103 found in your 32 GB flash drive.
• Download a version that explicitly lists FA00 / AU698x support (e.g. v16.09.30.00, v17.03.07.00).
• Run the tool under Windows as Administrator, perform a Low-Level Format / Capacity Optimise cycle, then re-create a single public partition.
Controller identification
• VID/PID = 058F:6387 → Alcor Micro Corp.
• Controller code = FA00, Firmware = F103 → Same family as AU6984/AU6987/AU6989.
• Symptoms usually observed:
− Permanent “write-protected” state
− Reported capacity fluctuates or is 0 B
− Windows refuses to format or assigns RAW file-system
Why normal tools fail
The defect is inside the micro-controller’s firmware or in the NAND flash’s internal mapping tables (FAT/LUT). OS-level formatters (Windows, macOS diskutil, Linux mkfs) operate above this layer and cannot fix a corrupted internal translation table. A Mass-Production (MP) utility re-initialises the controller, tests every physical block, builds a fresh bad-block table and rewrites the firmware header.
How AlcorMP works
• Detects NAND ID → selects timing & ECC parameters
• Performs optional full‐scan (Scan4) → remaps bad blocks
• Re-programs descriptor strings (VID, PID, Serial, Manufacturer, Product)
• Creates the user partition(s) and writes the boot sector / file-system
| Version selection logic | AlcorMP build | Release year | FA00 support note | Typical filename |
|---|---|---|---|---|
| 15.12.26.00 | 2016 | AU698x inc. FA00 | AlcorMP_15.12.26.zip | |
| 16.09.30.00 | 2017 | “AU6984/87/89/FA00 full” | AlcorMP_v16.09.30.00.rar | |
| 17.03.07.00 | 2019 | Lists FA00 in INI |
AlcorMP_v17.03.07.00.7z |
Newer builds add updated NAND tables (SM2259XT, TLC/QLC support) but still maintain legacy FA00 sections. Always check Setting.ini (or Parameter.ini) for the line Controller IC = FA00.
• Community repositories such as usbdev.ru, flashboot.ru, and mydigit.net continue to curate MP packages; the last publicly leaked AlcorMP build (as of 2023-Q4) is v17.03.07.00.
• Modern NAND (3D-TLC/QLC) increases bad-block count; hence MP tools now default to Capacity-Optimise rather than pure Speed-Optimise.
• Many low-cost 32 GB drives on the market are “re-labelled” smaller dies; MP tools can expose the genuine capacity during Scan4.
Example “quick” configuration inside AlcorMP (Setup → All):
• Flash Type = AutoDetect
• Scan Level = Full Scan4 (deep)
• Mode = Capacity Optimise + ECC Force
• Partition = 1 public, File System = FAT32 (you may choose exFAT)
• VID/PID = 058F/6387 (keep original for driver compatibility)
Process diagram:
• Data destruction: the low-level operation is irreversible; obtain user consent if the drive contains third-party data.
• Warranty: rewriting firmware may void manufacturer warranty; check local consumer law.
• Malware: MP packages are unofficial leaks; always hash-check downloads (SHA-256) and run on an isolated VM or offline PC to mitigate trojan risk.
Preparations
– Windows 7/10 32- or 64-bit PC, local administrator rights
– Direct USB-A port on motherboard (avoid hubs)
– Disable power-saving on USB root hub (Device Mgr → Power Mgt)
Execution steps
a. Extract tool to C:\AlcorMP\ (no spaces in path)
b. Right-click AlcorMP.exe → Run as Administrator
c. When prompted for password, leave blank or use MP/1234
d. Configure as above, press Start, wait (10-60 min)
e. When green, close program → safely eject → re-insert drive → run OS format if requested
Troubleshooting
• Drive not detected → try Driver\LoadDriver.exe, another USB port, or a Win 7 laptop (older stack sometimes works better).
• Error 30100/Flash Not Found → hardware failure (unsoldered NAND, dead chip); software repair impossible.
• Capacity < 8 GB after scan → counterfeit flash; either accept reduced size or discard.
• Repeated failures in two different AlcorMP versions almost always indicate a physical defect.
• Some FA00 controllers are epoxy-glob top; reflow or board-level repair is impractical.
• If the stick contained critical data, professional NAND off-chip extraction is the only (costly) option; MP actions will preclude subsequent recovery.
• Track the AU6990 successor series; Alcor has started migrating older FA00 builds to a unified “AMFU” tool (beta leaks expected).
• Explore open-source frameworks such as Flash-Forge or flashrom which aim to provide vendor-independent NAND testing routines.
• Investigate counterfeit-capacity detection algorithms and anti-rollback fuses in modern USB MSP430/8051 MCUs.
Your 32 GB flash drive uses an Alcor Micro FA00 controller whose firmware is corrupted. A standard OS format cannot help; you must employ the manufacturer’s AlcorMP Mass-Production utility that matches controller code FA00 and firmware branch F103. Download a recent build (≥ v16.09.30.00) from a trusted repository, run it as Administrator, select Low-Level Format / Capacity-Optimise, and let the tool rebuild the flash translation layer. This will erase all data but, if the NAND is still healthy, should return a fully functional—though possibly slightly smaller—USB drive.
User question
how can l repair this USB with the following properties Description: [F:]USB Mass Storage Device(Generic Flash Disk) Device Type: Mass Storage Device Protocal Version: USB 2.00 Current Speed: High Speed Max Current: 200mA USB Device ID: VID = 058F PID = 6387 Serial Number: 18EBAC7E Device Vendor: Generic Device Name: Mass Storage Device Revision: 0100 Manufacturer: Generic Product Model: Flash Disk Product Revision: 8.07 Controller Vendor: Alcor Micro Controller Part-Number: Unknown [FA00] - F/W 3F13 Flash ID code: ECDE98DE94C5 - Samsung - 1CE/Single Channel [TLC] -> Total Capacity = 8GB Tools on web: http://dl.mydigit.net/special/up/alcor.html Possible Flash Part-Number ---------------------------- Unknown Flash ID mapping table ---------------------------- [Channel 0] [Channel 1] ECDE98DE94C5 -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- --------
Artificial Intelligence Response
Direct answer to the question
• The ONLY realistic way to revive an Alcor-Micro FA00 USB stick is to re-initialise the controller with the factory Mass-Production software “AlcorMP”.
• Download a build that explicitly lists FA00 support (e.g. AlcorMP v16.09.30.00 or any newer revision that still supports FA00).
• Run the tool under Windows with administrator rights, choose “Full Scan / Capacity-Optimise”, keep VID 058F PID 6387 unchanged, and let the utility rebuild the Flash-Translation-Layer (FTL).
• All user data will be destroyed; the drive will come back as its true physical capacity (≈7.6 GB) only if the NAND and the controller are still healthy.
Key points
– Controller: Alcor Micro FA00, F/W 3F13 – NAND: Samsung TLC, 1 CE, 8 GB
– Standard OS formatting cannot fix firmware/FTL corruption.
– If AlcorMP fails (red slot) the device is physically defective → replace.
Detailed problem analysis
Hardware synopsis
• VID/PID 058F/6387 → Alcor Micro Corp.
• Internal code FA00 (same silicon family as AU6989SN), firmware string 3F13.
• Flash ID EC DE 98 DE 94 C5 → Samsung TLC, single-channel, 8 GByte raw.
• Current symptoms (write-protect, RAW partition, wrong size, etc.) are classic signs of a corrupted FTL or bad-block table inside the controller.
Why common formatting fails
The mapping between logical sectors and physical NAND pages is stored inside the controller’s SRAM/Flash; when that map is broken, the USB device still enumerates but every I/O fails. OS-level formats only rewrite the partition table on the logical side and therefore cannot touch the damaged map.
Principle of the Mass-Production (MP) tool
AlcorMP uploads a temporary loader, erases the internal firmware region, scans every physical block, classifies good/bad blocks, rebuilds ECC tables, writes new firmware parameters, then low-level formats the user partition. The procedure is invariably destructive but is the only factory-approved recovery path.
Capacity issue & counterfeit angle
Your scan shows only one 8 GB TLC die. If the stick was sold as 16/32 GB, it is a fake. AlcorMP will reveal its honest size (≈7.6 GB). Trying to force 16 GB will inevitably produce errors and data loss.
Current information and trends
• Latest public builds: v16.09.30.00, v17.03.07.00, v19.05.17.00; all contain FA00 in their INI tables.
• Community mirrors: flashboot.ru, usbdev.ru, mydigit.net (link you already have).
• Recent Alcor generations (AU6989SN-GT) moved to USB 3.0 and different tools (U2 MP); those builds do not* work on FA00.
• Growing number of counterfeit sticks still ship with AU/FA controllers; MP tools remain the standard mitigation.
Supporting explanations and details
Recommended AlcorMP settings
Typical workflow
C:\AlcorMP\; runAlcorMP.exeas administrator.MP,1234.Analogy: think of the controller as a tiny SSD. When its firmware table is shredded, the only cure is to reflash at factory level—exactly what AlcorMP does.
Ethical and legal aspects
• The procedure voids any remaining warranty.
• Firmware images shipped with leaked MP tools are company confidential; distribution may violate licensing.
• If the stick contains third-party data, wiping it without consent could breach data-protection laws (GDPR, etc.).
• Always virus-scan MP packages; many are posted on grey-market forums.
Practical guidelines
Do
✓ Use a dedicated, offline or virtual Windows install.
✓ Keep mains power stable; a power loss during MP can brick the controller.
✓ Accept the 8 GB final capacity; use
h2testworF3to verify integrity.Don’t
✗ Attempt MP flashing on a system you rely on for daily work.
✗ Change advanced INI values (Timing, CE mapping) unless you have the NAND datasheet.
✗ Use the stick for critical data after repair; TLC + single-channel + ageing → limited endurance.
Potential challenges
• Tool refuses to start under Win 11 → run in compatibility or use Win 7 VM + USB passthrough.
• “Device not detect” → run
Driver\LoadDriver.exe, switch USB ports, avoid USB 3 hubs.• Multiple identical sticks → process ONE at a time; MP tools bind to the first enumerated device.
Possible disclaimers or additional notes
• If data recovery (not functional repair) is the priority, STOP: MP will make recovery impossible. Seek a forensic lab that reads NAND off-board.
• Some FA00 lots suffer from internal mask ROM faults; even MP may not revive them—nothing short of replacing the controller helps.
Suggestions for further research
• Study AlcorMP INI structure to tailor timings for marginal NAND.
• Explore open-source alternatives (e.g., Sigrok with NAND-reader) for academic purposes.
• Track new FA-family successors (FA15, AU699x) and corresponding MP tools to maintain service capability.
Brief summary
Your flash drive’s controller (Alcor FA00) can only be resurrected with the factory “AlcorMP” Mass-Production utility. Obtain a build that lists FA00, run it under Windows with administrator rights, let it perform a Full Scan + Capacity Optimise. Expect the drive to come back as a stable ~8 GB device; if the process aborts, the hardware is beyond economical repair. Always back up data first, verify tool integrity, and be aware that the operation voids warranties and destroys existing data.