User question
I need software for this flash
Artificial Intelligence Response
Direct answer to the question
- Use the Alcor Micro Mass Production utility (AlcorMP) to repair/reinitialize a USB flash drive identified as VID 058F, PID 6387 (Alcor controller).
- Key points:
- Identify the exact controller (e.g., AU698x/AU699x) and NAND ID first.
- Choose an AlcorMP version that matches your controller/NAND.
- The MP process will erase all data and will set the true physical capacity (may be less than 128 GB on counterfeits).
- Validate the result with a full-capacity test (H2testw/F3).
Detailed problem analysis
- Why AlcorMP: Alcor controllers store firmware, timing, and Flash Translation Layer (FTL) parameters internally. Corruption, bad-block growth, or fake-capacity programming causes write/read failures and “write-protected” states. AlcorMP can:
- Re-detect NAND type and CE configuration.
- Rebuild the bad-block map.
- Recreate the FTL and repartition.
- Program correct VID/PID and device strings.
- What must match:
- Controller family/revision (e.g., AU6989SN-GT, AU6998).
- NAND characteristics (vendor, die count, interleave, page/block size, TLC/MLC/QLC).
- Some tool builds (U2/U3 lines and specific versions) include NAND tables supporting only certain Flash IDs. Mismatch yields “No Support Flash” or “Init Fail”.
Current information and trends
- AlcorMP releases come in series (commonly 13.xx, 14.xx, 15.xx, 19.xx). Newer builds broaden support for newer AU698x/AU699x and 3D TLC NAND, but older sticks sometimes work only with earlier builds. It’s normal to try 2–3 adjacent versions to find one that recognizes your NAND.
- Increasing numbers of “128 GB” drives are reprogrammed fakes. After a proper MP, capacity often drops to the real size (e.g., 8–64 GB). This is expected and indicates the controller is now correctly mapped.
Supporting explanations and details
- Terminology
- FTL (Flash Translation Layer): Maps logical sectors to physical NAND pages/blocks while managing wear-leveling and bad blocks.
- NAND ID/Flash ID: JEDEC-like code read from the NAND that determines vendor and geometry.
- CE/Interleave: Number of chip enables and parallelism lanes; affects timing and performance.
- Typical messages
- “No Support Flash”: The loaded NAND table doesn’t include your Flash ID; try a different AlcorMP version.
- “Read DCR/Init Fail”: Power/USB signal quality issue, or incorrect timing; use a short cable and a motherboard port.
Ethical and legal aspects
- The MP process voids typical retail warranty and wipes all data.
- Use trusted sources for tools to avoid malware; MP utilities are OEM-oriented and not officially distributed to end users.
- Do not reprogram drives to misreport capacity; that is deceptive and can cause data loss for others.
Practical guidelines
- Before you start (data first)
- If you need files, attempt data recovery before any MP action. Imaging tools: ddrescue (Linux) or hardware imagers; logical recovery: R‑Studio, DMDE. MP will irreversibly erase.
- Step-by-step repair workflow
- Identify hardware
- Run ChipGenius or Flash Drive Information Extractor.
- Record: Controller PN (e.g., AU6989SN), firmware string (e.g., FA00), Flash ID (hex), reported VID/PID (058F/6387).
- Obtain AlcorMP versions
- Acquire 2–3 nearby versions known to support AU698x/AU699x (for example a mid 14.xx and a later 15.xx/19.xx build). Use reputable community repositories.
- Prepare environment
- Windows PC with admin rights; plug directly into a rear motherboard USB port (no hubs).
- Close other USB storage operations; ensure stable power.
- Configure AlcorMP
- Open settings; set VID=058F, PID=6387; single removable LUN; one public partition.
- Enable Full Scan/Capacity Optimize; Auto-detect NAND where available.
- Leave passwords at default if prompted; do not alter advanced timings unless necessary.
- Run process
- Start low-level format; allow full bad-block scan and FTL build to finish.
- On errors, try the next AlcorMP version; re-read Flash ID each time to confirm recognition.
- Verify outcome
- Replug the drive; quick format NTFS or exFAT.
- Run H2testw (Windows) or F3write/F3read (macOS/Linux) across 100% of capacity. Expect 0 errors on a stable result.
- Troubleshooting
- Persistent “write protect”: Some sticks require a special flag clear; use the same AlcorMP version that recognizes your NAND and enable “Clear Write Protect/Force MP”.
- Capacity unexpectedly small: This reflects true NAND size on fake-capacity products; this is normal after a correct MP.
- Device drops during scan: Try a different USB port, shorter cable, or a powered USB add-in card.
Possible disclaimers or additional notes
- Success is not guaranteed; severely worn or mismatched NAND, or damaged PCBs, will fail MP.
- Cross-flashing with the wrong MP build can brick the controller until power-cycled; always proceed incrementally and note original parameters.
- Antivirus may flag MP tools because of driver components; verify hashes and scan with multiple engines.
Suggestions for further research
- Share these details and I can pick an exact AlcorMP build and provide a ready .ini:
- Controller PN/revision, firmware string, Flash ID, number of CE/dies (if shown), and any current error messages.
- If MP fails across versions, consider:
- Dumping the NAND via a programmer (e.g., RT809H/TL866 + TSOP adapters) for chip-off analysis.
- Evaluating solder quality and connector integrity under magnification; intermittent VBUS/D+ can mimic NAND faults.
Brief summary
- For an Alcor-based USB flash drive with VID 058F, PID 6387, the correct software is AlcorMP. Identify the exact controller and NAND first, choose a matching AlcorMP version, run a full MP/low-level format to rebuild the FTL, and validate with H2testw/F3. Expect true capacity to be enforced after repair, which may be lower on counterfeit or degraded media.
If you provide the ChipGenius/FDIE readout (controller model, Flash ID, firmware code), I’ll recommend the specific AlcorMP version and supply a step-by-step configuration for your unit.
Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.
