It is the natural question after a failed test: the drive is a fake, but the chip inside is real — can it be reprogrammed to report its true, smaller capacity and used honestly at that size? The honest answer is yes, technically — and no, practically, for anything that matters. This guide explains the full route, because understanding it teaches you a lot about how fakes are made, and then gives the verdict the facts support.
To be clear about roles first: FakeFlashTest only diagnoses; it does not repair. If you have not yet confirmed the drive is fake, run the test via our capacity testing guide with the tool from the download page, and if the verdict is confirmed, read Fake Drive Confirmed: What to Do Next for the safer sequence — refund and replacement come before tinkering in any sensible order.
Step one of any attempt: identify the controller with ChipGenius
A fake drive is not reprogrammed generically; it is reprogrammed with a tool matched to its specific controller chip. So the first step in every tutorial on this subject is identification. ChipGenius is the usual utility: it reads and displays the drive’s controller details — vendor and product identifiers (VID/PID) and controller/NAND information — without testing capacity itself. ChipGenius does not test or fix anything; it tells you what is inside, which determines which, if any, mass-production tool even applies to your drive.
Record what it reports carefully. The same outward drive can contain different controllers across production runs, so guides based on “the same model” may describe a different chip from yours. If identification is ambiguous, that ambiguity is itself a preview of the whole project: every subsequent step is controller-specific, version-specific, and unforgiving of near-misses.
The MPTool concept: factory tools that rewrite the lie
The reprogramming tools are called MPTools — mass-production tools. They are the factory utilities used to configure a controller in the first place: setting the reported capacity, formatting the flash, and writing the controller’s parameters. The fakes were made with exactly this class of tool, used to set a false capacity; in principle, the matching MPTool can set the true one, after which the drive reports only the capacity its chip really holds and behaves like a small, ordinary drive.
In principle is doing heavy lifting. The correct MPTool must match your controller and often its specific variant; the wrong tool can fail harmlessly or can brick the device outright, leaving it undetectable by any computer. The developer’s own tutorials in this area reflect the era these tools come from — procedures referencing XP-era tooling and environments are normal in this world, which means compatibility battles on a modern Windows PC before you ever reach the reprogramming step. Nothing about the route is a consumer feature. It is factory-floor software, leaked into hobbyist circulation, with factory-floor assumptions about the operator.
The risk nobody can remove: reject NAND
Suppose everything goes right: correct identification, correct MPTool, successful reprogramming, drive now truthfully reporting its small real capacity. The deepest problem remains untouched. Fakes are built down to a price, and the flash inside them is frequently reject-grade NAND — chips that failed quality standards for legitimate products, with weak endurance, marginal cells, and failure behaviour that no controller setting can improve. The firmware lied about capacity; the silicon itself is also the industry’s leftovers.
That is why the honest guidance, consistent with the developer’s own caution, is that even a successfully “fixed” fake should not be trusted with important data. It might work, at its true size, for a long time. It might also corrupt files next month for reasons unrelated to capacity — a marginal chip being a marginal chip. You would never know which outcome you were getting until the loss told you. Storage whose trustworthiness is unknowable is not storage; it is a gamble with a drive-shaped object.
Before you start: set the conditions for a safe experiment
If you do attempt the tinkering route, set the experiment up so failure costs nothing. Work only on a drive you have already been refunded for or written off, with no data on it that you need. Keep notes of the original ChipGenius readings and every tool version you try, so a failure is at least informative. Expect to spend real time hunting for the matching tool, and accept in advance that the drive may end the day undetectable — bricked by a mismatched tool is a known outcome, not bad luck. If any of those conditions would bother you, the experiment is telling you it is not worth starting.
The verdict: tinkering yes, reliance no
As a learning project, reprogramming a fake is genuinely interesting: ChipGenius identification, controller research, an MPTool session, and a formerly lying drive telling the truth at its real size is a satisfying afternoon for a technically curious person — on a drive they were refunded for, with nothing on it, accepting it may end bricked. As a storage strategy, it fails on economics as well as trust: the time involved exceeds the value of a small genuine drive, and the result is the least trustworthy small drive you own.
So the sequence this site recommends stands: confirm with FakeFlashTest from the download page, claim the refund with the test evidence, replace through a genuine channel, and test the replacement on arrival. If curiosity still itches afterwards, scratch it on the refunded fake as a science project — labelled, literally if you like, with its true capacity and a warning — and never let it graduate to holding the only copy of anything. Honesty about MPTools means admitting both halves: it can be done, and you should not depend on it.