The problem? These controllers have notoriously bad wear leveling, aggressive power management, and a tendency to corrupt their own firmware tables when improperly ejected. The result: a bricked drive that Windows can see but can’t talk to.
The interface is archaic by modern standards. It looks like a piece of software straight out of Windows 98.
| Version | Date | Key Improvements | |---------|------|------------------| | 20190228 | Feb 2019 | Fixed multi-CE detection; merged Toshiba/SanDisk capacity/speed tools | | 20190506 | May 2019 | Fixed USB detection under XP; improved Hy 3D yields | | 20190725 | Jul 2019 | Enhanced Toshiba/SanDisk 3D Flash support; added FC1179S | | 20200408 | Apr 2020 | Added FC1179AB; improved Micron 3D speed/stability; added Samsung 3D Flash | | 20201118 | Nov 2020 | Major UI refresh; enhanced multi-device support | | v1.0.5.2 | ~2021 | Unified FC1178/FC1179 database; enhanced SanDisk TLC scanning | | 20211024 | Oct 2021 | Comprehensive update; deep SanDisk OEM support; multi-port batch production | | 20220604 | Jun 2022 | Latest stable version referenced in community forums | firstchip fc1178 fc1179 mptools v1052
This is the primary use case. If a drive is write-protected, shows 0 bytes, or is not recognized by Windows, the "Burn" button initiates a low-level format.
Allows you to change the Vendor ID (VID), Product ID (PID), and manufacturer strings. How to Use FirstChip FC1178/FC1179 MPTools 1. Identification The problem
The status bar in the grid slot will turn yellow or blue while working. Do not touch the computer or disconnect the drive during this phase.
: It can fix "No Media," "Zero Capacity," and "Unrecognized Device" errors by reflashing the drive's firmware. The interface is archaic by modern standards
Open the folder and look for the main executable file, usually named FirstChip_MpTool.exe or MpTool.exe . Right-click the file and select . Step 3: Device Detection
Firmware download to controller fails – often due to communication issues.
