User question
Help, I need firmware for this flash drive.
Volume: G:
Controller: Alcor 0xFA00
Possible Memory Chip(s): Not available
Flash ID: 98E79432 7655
Flash CE: 1
Chip F/W: F843
Group: 98
VID: 058F
PID: 1234
Manufacturer: Alcor Micro
Product: Mass Storage Device
Query Vendor ID: Generic
Query Product ID: USB Flash Disk
Query Product Revision: 7.76
Physical Disk Capacity: 0 Bytes
Windows Disk Capacity: 0 Bytes
Internal Tags: AZAH-AAG2
USB Version: 2.00
Declared Power: 100 mA
ContMeas ID: 5669-19-00
Microsoft Windows 7 SP1 x64 Build 7601
------------------------------------
http://www.antspec.com/usbflashinfo/
Program Version: 9.4.0.645
Artificial Intelligence Response
Direct answer to the question
- Your stick is an Alcor‑based UFD reporting controller code FA00, firmware tag F843, and NAND Flash ID 98 E7 94 32 76 55 (Toshiba/Kioxia vendor code 0x98). The correct path is not a “firmware file,” but running Alcor’s Mass‑Production utility (AlcorMP) to reinitialize the controller and rebuild the Flash‑Translation‑Layer (FTL). (flashboot.ru)
- Use an AlcorMP build that supports AU698x/FA00 family; start with U2-line versions around 16.xx–17.xx, and if they don’t enumerate your NAND, try a later U2 build (e.g., 20.09.16). Run on Windows as Administrator, enable Full/Low‑Level Scan, and keep VID=058F / PID=1234 unless you purposely change it. All data will be destroyed. (elektroda.com)
Key points
- 0‑byte capacity = corrupted internal tables (FTL) or unsupported NAND map; OS formatting cannot fix it. Only the AlcorMP mass‑production (MP) process can. (elektroda.com)
- 0x98 = Toshiba/Kioxia NAND vendor; FA00 commonly maps to the AU6989(AU698x) family in field repairs. (flashboot.ru)
Detailed problem analysis
- What the readout means
- Controller code: FA00 is a family identifier seen on AU698x (often AU6989SN/SNL/SN‑GT revisions). When the FTL is corrupted, tools and ChipGenius frequently show generic IDs (VID 058F / PID 1234) and 0‑byte capacity. (elektroda.com)
- NAND: Flash ID starts with 0x98 (Toshiba/Kioxia). Similar IDs (98 D7/E7 94 32 …) are documented on flash databases, confirming vendor and page geometry families used by MP tools. (flashboot.ru)
- Why capacity is 0 bytes
- The mapping between logical sectors and physical NAND pages (FTL), along with bad‑block/ECC tables, resides in reserved NAND areas managed by the controller. If these tables are corrupted or the tool build lacks a matching Flash table, the device enumerates but exposes no LUN capacity. MP re‑creates these tables after scanning the NAND. (elektroda.com)
- Version‑to‑NAND fit matters
- AlcorMP releases are segmented (13/14/16/17/20 series). AU6989‑era sticks often respond to 14–16 series; newer releases broaden support for newer 3D TLC but some older sticks initialize only with earlier toolsets. It’s normal to try 2–3 adjacent versions. (elektroda.com)
Current information and trends
- Tooling: Community builds of AlcorU2MP 16.xx–20.xx target AU6989/AU6998 families; later sets include expanded NAND tables. (files.elektroda.pl)
- Practical field guidance emphasizes choosing MP builds that explicitly list FA00/AU698x in their notes and using Full Scan/Capacity‑Optimize for stable mapping. (elektroda.com)
- Counterfeit‑capacity sticks are common; after a correct MP cycle, capacity may drop to the true physical size. This is expected behavior. (elektroda.com)
Supporting explanations and details
- MP workflow (what happens under the hood)
- Installs a vendor driver, loads a RAM loader, interrogates NAND (die count/CE/page, etc.), performs erase/LLF, builds a bad‑block map, selects ECC, then writes a fresh param block and exposes a logical LUN. (elektroda.com)
- VID/PID handling
- Many AlcorMP packages ship a “LoadDriver/Change VID/PID” helper to install the service driver and set default IDs (often 058F:6387). For your stick, keep 058F:1234 unless the tool requires the default; some tutorials show changing the PID to match the device so the service can grip it. (upantool.com)
- Identifying your NAND
- The iflash database and community logs list Toshiba/Kioxia entries with 98E79432 variants, corroborating that 0x98 is Toshiba. You don’t need the exact part number—AlcorMP will select a compatible Flash table if the build contains it. (flashboot.ru)
Ethical and legal aspects
- Source hygiene: Many MP tool archives are hosted on third‑party forums. Use reputable communities and scan downloads with updated AV; prefer read‑only test VMs if possible. (files.elektroda.pl)
- Data privacy: MP fully erases the NAND. If any private data might still reside, consider secure disposal instead of reuse.
- Licensing: These are factory service utilities intended for OEM/ODM use; distribution is community‑driven.
Practical guidelines
Implementation (Windows 7 SP1 x64 per your note)
1) Preparation
- Use a native USB 2.0 port on the motherboard (avoid hubs). Disable other USB storage to keep the MP slot list clean.
- Extract a suitable U2 AlcorMP build (start with ~16.11.01.00 or 17.05.02.00; if unsupported NAND, try 20.09.16). (flashboot.ru)
- Right‑click AlcorMP.exe → Run as Administrator. If a password prompt appears, typical packages accept blank or simple defaults (varies by build). (elektroda.com)
2) Driver/IDs
- If the tool doesn’t see the stick, run its LoadDriver/Change VID‑PID helper and ensure the config carries VID=058F and PID=1234 (matching your device). (upantool.com)
3) Settings (inside Setup)
- Mode: Low‑Level Format / Full Scan (or “Capacity‑Optimize”).
- ECC: Auto; Power limit: start at 200 mA, raise to 500 mA only if the tool advises. (elektroda.com)
- Partitions: Single public removable LUN unless you need more.
4) Run
- Click Start and wait; Full Scan can take 10–30+ minutes depending on NAND.
- On success (green), safely remove and reinsert; allow Windows to quick‑format (FAT32/exFAT as needed).
5) Validate
- Run H2testw/F3 to verify the resulting capacity is error‑free. If capacity is smaller than the label, the media may be worn or the original label was inflated. (elektroda.com)
Potential challenges and remedies
- Not detected by AlcorMP: verify VID/PID in the tool, try an adjacent MP version family, or a different PC/OS session. (files.elektroda.pl)
- “Flash Not Support” / “Init Fail”: you’re on a build that lacks a table for your NAND; move to a different nearby build (e.g., 16.xx → 17.xx → 20.xx). (elektroda.com)
- Success but small capacity or errors: repeat with Full Scan enabled and Auto‑ECC; if bad‑blocks exceed limits, the NAND is worn‑out—replace the drive. (elektroda.com)
Possible disclaimers or additional notes
- MP is destructive—if you need files, stop and consult a professional chip‑off lab (e.g., AU6989 families are well‑covered in pro tools). (rusolut.com)
- Forcing ISP/Test modes via hardware tricks is advanced and risky; do not attempt without service documentation and proper ESD tools.
Suggestions for further research
- Look up Alcor U2 MP archives and support PDFs that list AU6989/AU6998 coverage, plus release‑note “Flash Support Lists” within each package. Try a few adjacent builds. (files.elektroda.pl)
- Community repair threads discussing FA00/AU698x cases can provide working parameter sets and error‑code interpretations. (elektroda.com)
Brief summary
- You don’t need a standalone “firmware file.” Use the AlcorMP U2 tool to reinitialize the FA00/AU698x controller and rebuild NAND maps. Start with 16.xx–17.xx builds; escalate to 20.xx if needed. Expect total data loss and validate the restored capacity after MP. If multiple versions fail or the stick returns with heavy bad‑block counts, the NAND is at end‑of‑life—replace the drive. (elektroda.com)
If you want, I can tailor exact AlcorMP settings for your log (FA00, F843, 1‑CE Toshiba), and walk you through a run while you share the tool’s status messages.
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.
