Antminer Firmware Downloads for BTC and LTC Miners

Antminer firmware from us means Vnish custom firmware, distributed under an official partner agreement in the USA. Use v1.3.5: one build covers most models and identifies the hardware at boot. v1.2.7 remains for setups that need a separate per-model file. Both add per-chip tuning, watchdog protection and control over a degraded miner.

Which firmware for your model

Both archives below are complete packages with the installation tools included, hosted on our own server rather than a third-party file share, and they are built differently in a way that matters. v1.2.7 is the last release that ships a separate firmware file for every model — you pick the file that names your miner. v1.3.5 is the current release: one build can serve several models and identifies the hardware itself at boot, which makes it the safer choice on newer machines. It also drops some of the visual settings the 1.2 branch had. In both cases the file still has to match your control board family.

Download Antminer Repair Firmware v1.3.5 – current release, full archive with installation tools

Download Antminer Repair Firmware v1.2.7 – previous branch, one file per model

Check what you downloaded before you flash it. SHA-256 of antminer-repair-vnish-1.3.5.zip is 34b81cb46534208d687dd2bdba893516e38a8bd01104f42ab790f48e82ab07f9; SHA-256 of antminer-repair-vnish-1.2.7.zip is b8e75575b004127860fc2e47c31ab4d6267801229ae1ef01947e3116aa8cafbd. If your file does not match, it did not come from us intact — download it again rather than flashing it.

Antminer model Recommended v1.2.7 also works Notes
S19, S19 88, S19 126, S19i, S19+ v1.3.5 Yes The 126-chip S19 on a Xilinx control board is only recognised from v1.3.5.
S19 Pro, S19 Pro A, S19a, S19a Pro v1.3.5 Yes Auto-detection of the 114-chip S19 Pro was corrected in v1.3.5.
S19j, S19j+, S19j Pro, S19j Pro+, S19j Pro A, S19j XP v1.3.5 Yes The most common family we see. Either build runs it.
S19k Pro v1.3.5 Yes Amlogic, CVITEK and Xilinx boards. One stock build, FR-1.28 (251010-S19k Pro), blocks the normal install and has to be cleared first — an SSH error, not a damaged miner; see below.
S19 XP, S19 XP+ v1.3.5 Yes Air-cooled S19 XP+ and S19 XP+ Hydro support was added in v1.2.7. The 1.3 branch did not add the model — it rebuilt its presets in v1.3.4.
T19 v1.3.5 Yes T19 auto-detection was worked on across the 1.3 branch — improved in v1.3.4 and fixed again in v1.3.5; older archives can misread the chain.
S19 Hydro family, including S19 Pro Hydro, S19 XP Hydro, S19 XP+ Hydro, U3S19XPH v1.3.5 Partly Hydro sub-models were added in stages. Send us the sub-model code before flashing an older build.
S21, S21+, S21 Hydro, S21 Immersion, T21 v1.3.5 Yes T21 ships on Amlogic, Xilinx and CVITEK boards — three different files for one model name. On Amlogic boards a recent stock build can lock the miner before you get this far: see S21 firmware unlock and recovery.
S21 Pro, S21 XP, S21 XP Hydro v1.3.5 Mostly Some board revisions are only recognised from the 1.3 branch. Presets for these models were rebuilt in v1.3.4, so plan a full retune after updating.
S21 Pro+ v1.3.5 No Support added in v1.3.4. v1.2.7 does not know this model.
S21++ v1.3.5 No Support added in v1.3.5, the newest addition to the branch. v1.2.7 does not know this model.
L7 (Scrypt) v1.3.5 Yes Xilinx control board. The developer fee is the same 3% as on every other model — there is no lower rate for the L series.
L9 (Scrypt) v1.3.5 Yes Amlogic and CVITEK boards. Stock build FR-1.19 (260302-L9) blocks the normal install — an SSH error, not a damaged miner; see below. Presets were rebuilt in v1.3.4, so plan a full retune after updating.
U2L9H v1.3.5 No Support added in v1.3.5.
S9 Neither No We see no current Vnish release published for the S9 — it is absent from the 1.2.7, 1.3.5 and 2.0.x lists alike. Do not flash a 19 or 21 series file onto one; ask us before you try anything.
S17, S17+, S17 Pro, T17, T17+ Neither No These run on a separate Vnish line with its own 2.0.x numbering, currently 2.0.4-stable dated 29 June 2026 — a separate line, not an abandoned one. Do not flash a 19 or 21 series file onto them — ask us for the right one.
23 series, L11 Not yet No No released custom firmware at the time of writing.

Two things decide the file, not one. Pick the version from the table, then pick the build for your control board family — BeagleBone, Xilinx, Amlogic or CVITEK. The slot placement identifies it: Xilinx and CVITEK put the SD slot on the outside, BeagleBone keeps it inside on the board, Amlogic has a micro USB port and no SD slot. Flashing a file built for a different board family is the most common way a working miner becomes a bench job. If the marking on your board does not match anything on this page, send us a photo of it first.

Version 1.3.4 rebuilt the tuning presets for the L9, the S19 XP+, the T21 and the whole S21 family — S21, S21+, S21 Hydro, S21 Pro and S21 XP. If your miner is one of those, plan a full preset retune after updating: the old tune is not carried over.

Before the first install, check what stock firmware is on the miner. Signature checking is not new: Bitmain's signed security firmware goes back to April 2019, and its symptom — an upgrade that fails complaining it cannot find a signature — has been around ever since. What began in March 2024 is a different mechanism: Bitmain started shipping Amlogic control boards with a firmware lock that blocks third-party images. Two mechanisms, two dates, and treating them as one sends you looking for the wrong fix.

Vnish installs on stock firmware of any date, with three exceptions. They are a closed list, not a general rule: an Antminer L9 on stock build FR-1.19 (260302-L9); an Antminer S19k Pro on stock build FR-1.28 (251010-S19k Pro); and Amlogic (a113d) control boards running stock firmware from September 2025 or newer, where the micro USB port is switched off. Everything else goes in normally, provided the installer is Hashcore Toolkit 1.7.1 or newer — an older toolkit fails for its own reasons and the failure looks exactly like a lock. Note that the FR- numbering runs per model rather than across the range, so FR-1.19 on an L9 and FR-1.28 on an S19k Pro are not two points on one scale: comparing your build number with one quoted for another miner tells you nothing.

On the first two, “blocks” means the installer cannot get in — not that anything is broken. Those builds close the SSH path the toolkit uses to push the image, so what you get is an SSH error rather than a signature error, and the miner itself is intact. Whether there is a way back is decided by the control board, not by the model: an S19k Pro ships on Amlogic, CVITEK and Xilinx boards and an L9 on Amlogic and CVITEK, and on CVITEK and Xilinx the stock recovery route is still open. Send us the model, the stock build number and a photo of the board marking, and we will tell you which of those you are holding.

The third case is the one with no software way out. On an Amlogic board running September 2025 or newer stock the downgrade route is gone, and re-opening it is bench work on a live control board rather than a field procedure — there is no image you can download that undoes it. On a 21-series miner that is Antminer S21 firmware unlock and recovery. On other models, message us with the model and the stock build number before you start, and we will tell you what it takes.

Antminer S9, S17, S17 Pro and T17: the separate 2.0.x line

Neither file on this page fits these four models. S17, S17 Pro and T17 are served by a separate Vnish line with its own 2.0.x numbering, currently 2.0.4-stable dated 29 June 2026 — a line of its own, not an abandoned one, and not inside either archive above. For the S9 we can find no current Vnish release at all: it appears in no version list we can check. The 1.2 and 1.3 branches do not know this hardware at all, and a 19-series or 21-series file written to a 17-series control board is the most common way one of these machines stops being a miner.

We do not hand out the 2.0.x builds. They are not inside either archive above and this page does not link to them, so downloading the archives and hunting through their contents will not turn one up. What we can do, from the model and a photo of the control board marking, is tell you which board family you have and whether the machine is worth touching at all.

Before you flash anything on this generation. These machines are six to eight years old, and most of them have been sitting somewhere warm and dusty. The failure that looks like a firmware problem is often a dried-out capacitor, a fan that stopped, or a supply that no longer holds under load. Firmware does not fix any of those, and a flash interrupted by a machine that browns out mid-write leaves the control board needing a service centre rather than a retry.

What is worth repairing here, honestly. S17, S17 Pro and S17+ hashboards we do repair at component level: Antminer S17 and S17 Pro hashboard repair and Antminer S17+ hashboard repair. On the S9 the arithmetic has moved against the repair: a working machine costs less today than a board-level repair is worth, so we do not offer S9 hashboard repair, and we would rather say so on this page than take the board and tell you afterwards. What still makes sense on an S9 is the cheap end of it - a control board or a power supply unit - and that work we do.

What Vnish firmware actually changes

Stock firmware gives you one frequency for a whole chain and board-level averages to look at. Vnish tests every ASIC on every hashboard on first boot and then sets frequency and voltage per chip, giving the stronger chips more and the weaker ones less. That first tuning run takes about three to four hours. Afterwards you get per-chip hashrate, temperature and error counts instead of a board average.

On efficiency, the honest numbers are narrower than the marketing. Autotuning against stock is generally worth somewhere around 5 to 15 percent in joules per terahash. The large power reductions people talk about come from choosing a lower watt target, not from tuning: an S19j Pro class miner can be brought from roughly 3,068 W down to around 1,740 W, and the hashrate comes down with it. On a few models, including some hydro units, underclocking makes the J/TH figure worse rather than better. It is worth setting the target per machine and measuring, not copying a preset from a forum.

The protection settings matter more than the tuning on hardware that is already marginal. Vnish will restart on a hashrate drop with a capped number of attempts, halt mining at a critical chip temperature, shut down a board that stops responding to the integrity check, balance voltages, lower the performance profile automatically when the miner overheats or errors, and retune by itself when a chain breaks. It also has an immersion mode that disables fan monitoring and fan-dependent shutdowns, and a one-click return to stock from the miner's own menu.

Running a miner that has lost a hashboard

This is the part that matters when something has already gone wrong. Stock firmware treats any deviation on a chain as a reason to stop the machine. One board out of three failing to report its full chip chain is enough — the whole miner stands still. Not a third of the hashrate lost: all of it.

Vnish does not do that. You disable the failed board, tell the firmware how many chains are working, and the miner keeps hashing on the boards that are healthy. A three-board S21 with one dead board carries on earning at roughly two thirds of its rate while the third board sits on our bench instead of the machine sitting idle in your shed.

Antminer S21 mining on two hashboards with one board failed on Vnish firmware
One dead hashboard, miner still earning: Board 1 reports Failed to detect ASIC chips at 0.00 H/s while Boards 2 and 3 keep hashing for a combined 123.47 TH/s on our firmware

When that third board leaves for the bench, close the slot it came out of before you power the machine back up. An open slot is the path of least resistance, and the boards you kept get less air than they had with the full set — the dashboard will not tell you, the chip temperatures will. Running an Antminer with a hashboard removed shows what to cut, from what, and what it changes.

That is the good case, where the miner still runs. On the 21 series the stock firmware can take the opposite path: once it has marked a chain out it refuses to start at all, and there is no interface left to install anything through. If your log ends on Not enough chain, exit. or names a chain with you should send it to repair, the board is often healthy and the verdict is the problem — that is S21 firmware unlock and recovery, and it is worth settling before you order anything.

What no firmware can do is work around a dead chip. The chips sit in a chain, and a chain with a dead chip will not initialise at all — the board is either alive or it is a repair. So this is a way to keep earning during the repair window, not a substitute for the repair. A chain that has failed once does not recover on its own, and running a degrading board hot next to good ones is how a repairable board becomes an unrepairable one. When you are ready, send it in — we do component-level Antminer hashboard repair in the USA and test every board under real mining load before it goes back.

Updating firmware on the control board

Worth clearing up first: hashboards do not run firmware. The firmware lives on the control board, which is the small computer that runs the miner. A hashboard carries an EEPROM instead, holding its identity and configuration — serial number, chip count and mapping, voltage domains, frequency tables, hardware revision. When that EEPROM is unreadable the control board misreads the chain, and the symptom looks like a firmware problem while the cause is on the board. That case is EEPROM repair, not a reflash.

For the control board itself there are two routes, and they are not interchangeable:

Web interface upgrade Flashing the control board
Where it happens The miner's own System > Upgrade page From an SD card or over USB, at the board
Miner has to boot Yes, and be reachable on the network No
What it writes An update package on top of an intact bootloader and root filesystem The whole stack, bootloader included
Signature check Enforced on recent stock builds, which is what blocks downgrades Bypassed on most generations, where the port is still open
File Web update package A full board image — a different file entirely

Which route applies to you is decided by the control board family. Amlogic boards take the file straight from the miner's interface. BeagleBone and Xilinx boards have historically needed the SD route for a first install, and the SD image is not shipped with every release, so ask us which image goes with your board rather than assuming the archive contains one.

If the miner no longer boots at all — no interface, no IP, no response to the IP reporter — that is past the point where a firmware page can help. One fork before you go further: on a 21-series miner the same silence is very often the stock firmware refusing to start after it marked a chain out, not a dead board. If the last thing in the log is Not enough chain, exit., start with S21 firmware unlock and recovery — it is the cheaper question and it settles the expensive one. Otherwise nobody can tell from a description whether it needs a restore or a new board, and that is a diagnosis, not a download: start with Antminer control board replacement.

Fees, warranty and what can go wrong

This firmware carries a 3% developer fee. It is taken as hashrate redirected to the developer pool while the miner runs, not billed to you, and for most operators it is covered several times over by the electricity saved. We state it here because a firmware page that leaves the fee out is hiding part of your cost per terahash.

On warranty, Bitmain's position is unambiguous: installing unauthorised third-party firmware voids it. Vnish can be rolled back to stock from the miner's own menu, but a rollback is not the same as the warranty surviving, and on recent Amlogic boards running security firmware the downgrade path may be closed to you. If a miner is still inside its warranty window, that is a real cost to weigh, not a formality.

The other honest risk is the install itself. An interrupted write — power cut, storage device pulled, cancelled halfway — can leave the control board without working low-level software, and at that point it is a service-centre job rather than something you retry. Pushing voltage and frequency hard also trades chip lifespan for hashrate; sustained high temperatures shorten it measurably.

Disclaimer: We are not responsible for any issues resulting from firmware installation if it is performed by third parties or not according to our instructions. Installing third-party firmware may void your factory warranty.

5% repair discount after 30 days

Run our firmware for 30 days or more and your next repair with us costs 5% less. The condition is simple and we check it ourselves: the miner log has to show the first launch date of our firmware at least 30 days before the repair request. Mention the discount when you send the request so it lands in the quote rather than as a refund afterwards.

The reason it exists is worth saying plainly. Our logo is in the build, so when something does go wrong on a miner running our firmware, you already know where to send it — and we would rather that be a discounted repair than a search engine result.

Prefer we do it?

If your miner runs normally and you would rather not do the first install yourself, Remote Miner Diagnostics and Firmware Upgrade is the paid service for it. We connect to the miner, confirm the model and the control board family, install the correct build and set a tuning profile that suits your cooling rather than a preset copied from somewhere else. For background on what tuning is worth on a specific model, we wrote up the S19j Pro custom firmware case in more detail.

That route needs a miner we can reach. If the stock firmware has already locked the board — nothing you save is kept, or the miner will not finish starting — there is nothing on the other end for a remote session to work through, and no amount of network access changes that. On the 21 series that is S21 firmware unlock and recovery, and it is done on the bench.

Antminer Repair Firmware Vnish partner builds v1.2.7 and v1.3.5

Downloaded it. Now what do all these screens do?

The interface that comes up after the flash is Vnish's own, and the archive does not explain it. We put a working S21 Pro on the bench, captured every screen of v1.3.5 and marked up every control on them: the Vnish interface, screen by screen. Click the menu and the tabs inside the screenshots and the guide follows, the way the miner does. Real screens with the pool details blanked out rather than a written summary, and that includes the log tabs, where a failing chain is usually visible long before it shows up as lost hashrate.

Contact

Not sure which file you need? Send us the model and a photo of the control board marking and we will tell you which build to use. Message us on Telegram, on WhatsApp, or through the form on our contact page. You'll be chatting with a real person, not a bot — we respond during Florida daytime hours. If it's night here, replies may be delayed.

Technical FAQ

Q: Which Vnish firmware version do I need for my Antminer model?
A: Use v1.3.5 unless you have a specific reason not to. The two branches are built differently: v1.2.7 is the last release with a separate firmware file for each model, so you pick the file that names your miner. v1.3.5 is the current release — one build can cover several models and identifies the hardware at boot, and it drops some of the visual settings the 1.2 branch had. The newest hardware exists only in the 1.3 branch: S21 Pro+ from v1.3.4, S21++ and U2L9H from v1.3.5, and the 126-chip S19 on a Xilinx controller from v1.3.5. The model table above lists coverage per family.
Q: Where can I download Antminer firmware for these models?
A: From the two links in the model section of this page. Both archives sit on our own server at files.antminer-repair.com, with the version in the file name, so you can see exactly which build you are getting before you download it, and the SHA-256 checksum of each archive is printed next to the download links so you can confirm the file arrived intact. Each one is a full package with the installation tools included, distributed by us as an official Vnish partner. If you are not sure which file inside the archive matches your miner, send us the model and the control board marking before you flash anything.
Q: Does this firmware cover the Antminer S9, S17, S17 Pro or T17?
A: No, and the two halves of that question have different answers. The 17 series — S17, S17+, S17 Pro, T17 and T17+ — is served by a separate Vnish line with its own 2.0.x numbering, currently 2.0.4-stable dated 29 June 2026: a separate line, not an abandoned one, and neither v1.2.7 nor v1.3.5. For the S9 we see no current Vnish release published at all — it appears in no version list we can check. Do not flash a 19-series or 21-series file onto 17-series or S9 hardware. Message us and we will tell you what exists for your machine.
Q: What is the difference between a web interface firmware upgrade and flashing the control board?
A: A web interface upgrade uses the miner's own System > Upgrade page. The miner has to boot and be reachable on the network, and the package it accepts is a signed update that sits on top of an intact bootloader and root filesystem. Flashing the control board writes the whole stack from an SD card or over USB and does not need the miner to boot at all. They are different files. A web update package will not recover a board that no longer starts.
Q: Why does my Antminer refuse to accept custom firmware?
A: Almost always the stock firmware already on it, and two separate mechanisms get blamed for each other. Bitmain's signature checking dates from April 2019 and shows up as an upgrade that cannot find a signature; the Amlogic control board lock is a different thing that began in March 2024, and Amlogic boards on September 2025 or newer stock also have the micro USB port switched off. In practice Vnish installs on stock of any date except three: an L9 on FR-1.19 (260302-L9), an S19k Pro on FR-1.28 (251010-S19k Pro), and Amlogic boards on September 2025 or newer stock — and the installer has to be Hashcore Toolkit 1.7.1 or newer. In the first two “blocks” means an SSH error and an intact miner, and whether there is a way back depends on the control board family. The third has no software route at all: on the 21 series that is S21 firmware unlock and recovery, a bench job on the control board; on other models, send us the model and the stock build number and we will tell you what it takes.
Q: Can Vnish keep my Antminer running when a hashboard has failed?
A: Yes, and this is the practical reason to install it on a machine that is already misbehaving. Stock firmware stops the whole miner on any deviation from normal: one board out of three failing to report its full chip chain is enough to put the entire unit at zero. On Vnish you disable the failed board, set the working chain count, and the miner keeps hashing on the remaining boards while the failed one is repaired.
Q: Can an Antminer run on only two working hashboards?
A: Yes. Disable the failed board, set the working chain count to two, and the miner runs at what those two boards can deliver — on a three-board machine, roughly two thirds of its normal rate. What you cannot do is nurse a dead chip: the chips sit in a chain, and a chain with a dead chip will not initialise at all, so the board is either alive or it is a repair job. Treat two-board operation as a way to keep earning during the repair window, not as a fix.
Q: Does Vnish firmware reduce power consumption on Antminer S19 and S21?
A: It gives you the controls to reduce it. Independent write-ups put the typical efficiency gain from autotuning at roughly 5 to 15 percent in joules per terahash against stock. Large power reductions come from choosing a lower watt target, not from tuning alone: an S19j Pro class miner can be brought from about 3,068 W down to roughly 1,740 W, but the hashrate drops with it. On a few models, including some hydro units, underclocking makes the efficiency figure worse rather than better, so the target is worth checking per machine.
Q: What exactly does per-chip tuning do?
A: Vnish tests every ASIC on every hashboard and then sets frequency and voltage per chip, giving the stronger chips more and the weaker chips less, instead of applying one setting to the whole chain. The first tuning run takes roughly three to four hours. It also gives you per-chip telemetry — hashrate, temperature and error counts per chip — where stock reports board averages.
Q: What does the Vnish watchdog actually do?
A: It is a set of protections in the advanced mining settings rather than one switch: restart on low hashrate with a capped number of attempts, a critical chip temperature that halts mining, a circuit integrity check that shuts down a board that stops responding, voltage balancing, automatic reduction of the performance profile when the miner overheats or errors, and automatic retuning when a chain breaks.
Q: How much is the developer fee on this firmware?
A: 3 percent, the same on every model we cover — there is no separate rate for the L series or for Scrypt. It is taken as hashrate redirected to the developer pool while the miner runs, not as an invoice, so you will see it as a small share of the total rather than a charge. The disclosure is deliberate: a firmware page that hides the fee is hiding your real cost per terahash.
Q: Will my Bitmain factory warranty remain valid after installing custom firmware?
A: No. Bitmain states plainly that installing unauthorised third-party firmware voids the warranty. Vnish can be rolled back to stock from the miner's own menu, but a rollback is not the same thing as the warranty surviving, and on recent Amlogic boards with security firmware the downgrade path can be closed to you. If the miner is inside its warranty window, decide with that in mind.
Q: Do Antminer hashboards have their own firmware?
A: No, and this is the single most common misunderstanding behind firmware-on-the-board searches. The firmware lives on the control board. A hashboard carries an EEPROM holding its identity and configuration — serial number, chip count and mapping, voltage domains, frequency tables, hardware revision. If that EEPROM is corrupt the control board misreads the chain, which looks like a firmware fault and is not one. That is a repair, and we do it as EEPROM repair for Antminer hashboards.
Q: How do I know which control board my miner has?
A: By the marking on the board itself. The four families you will meet are BeagleBone, Xilinx, Amlogic and CVITEK, and the SD or USB slot placement usually gives it away: Xilinx and CVITEK have the SD slot on the outside, BeagleBone has it inside on the board, Amlogic has a micro USB and no SD slot. The firmware file has to match the board family, not just the miner model. Flashing a file built for another board family is the most common way people brick a control board.
Q: What happens if a firmware update is interrupted?
A: It can leave the control board without working low-level software, and Vnish's own documentation says that in that state the board is a service-centre job. Do not power the miner off, unplug it or pull the storage device mid-write. If it has already happened, the miner is a diagnostic case rather than a reflash case — see Antminer control boards.
Q: Can you install the firmware for me?
A: Yes, when the miner still runs and we can reach it: Remote Miner Diagnostics and Firmware Upgrade is a paid service where we connect, confirm the model and control board, install the correct build and set the tuning profile. If the stock firmware has already locked the board, remote access has nothing to work through — on the 21 series that is S21 firmware unlock and recovery, done on the bench.
Q: My S19 or S21 started overheating after the firmware upgrade. What should I check?
A: The performance profile first, then the fan settings and the critical chip temperature, in that order. Autotuning is the safe starting point for a new cooling environment; a preset copied from another site or another machine is not. If temperatures still climb on a conservative profile, the cooling or the board is the problem rather than the firmware.
Q: How does the 5 percent repair discount work?
A: Run our firmware for 30 days or more and your next repair is 5 percent cheaper. We confirm it from the miner log, which records the date our firmware first started. Mention it when you send the repair request so we apply it to the quote rather than refunding afterwards.