Antminer L9 and S21 Firmware Update Guide

An Antminer L9 and S21 firmware update must be treated as two model-specific changes, not one interchangeable procedure. The L9 is a Scrypt miner and S21-family units are SHA-256 miners with several air, hydro and immersion variants. Record the exact model, control board and installed version, download only the matching official Bitmain release, back up pool settings, provide stable power and test one unit for at least 24 hours before a wider rollout. Never cross-flash an L9, S21, S21 Pro, S21 XP or liquid-cooled image.

Separate the L9 and S21 change plans

Reassess Antminer L9 and S21 firmware update whenever network conditions, firmware, tariffs or official guidance changes.

The Antminer L9 mines Scrypt and Bitmain specifies the common 16 GH/s version at a typical 3,360 W. The S21 family mines SHA-256 and contains materially different models and cooling systems. A shared maintenance window does not make their firmware interchangeable.

Create one change record for each exact model, hardware version and control-board type. Include the installed firmware string, release type, serial, pool, working mode, network settings, baseline hashrate, temperature and known faults.

Do not update a miner merely because a newer date exists. Read the release notes and identify the security fix, compatibility change or fault that justifies the risk. A stable production miner can reasonably wait while a release is tested on a representative spare or small group.

Identify the complete model and control board

When reviewing Antminer L9 and S21 firmware update, separate measured facts from forecasts so the result can be reproduced.

Read the chassis label and the management interface. Distinguish L9 from L7 and distinguish S21 from S21 Pro, S21 XP, S21 Hyd, S21 XP Hyd and immersion products. Air-cooled and liquid-cooled packages can use different controls and recovery images.

Record the control-board identity where Bitmain’s release or recovery instructions require it. An SD-card image for one controller can fail on another even when the front of the chassis carries the same product family name.

If the label, interface and seller record disagree, stop and obtain evidence from Bitmain or a competent repair provider. Do not use trial and error to discover which image boots.

Download only the matching official release

No conclusion about Antminer L9 and S21 firmware update should rely on a single revenue snapshot or an undated specification.

Use the current Bitmain support page for the exact L9 or S21 model and follow its firmware link. Confirm the domain, model name, cooling variant, release date, filename and release notes. Retain the downloaded package and its published checksum if Bitmain supplies one.

Do not install firmware from a marketplace seller, chat attachment, file-sharing site or another miner. Bitmain warns that unauthorised third-party firmware may affect security and warranty. A familiar filename is not proof that a file is authentic.

Bitmain describes normal customer firmware as Release type. Factory firmware may be intended for production testing and can restrict pool changes. If the interface shows an unexpected type, document it and follow the manufacturer’s current correction process rather than forcing an arbitrary downgrade.

Prepare settings, power and rollback

The practical value of Antminer L9 and S21 firmware update comes from testing the claim against current data and full operating costs.

Export or record pool hostnames, ports, worker names, optional passwords, network settings, working mode and administration access. Do not place payout addresses or credentials in an unprotected ticket or screenshot.

Understand the update option that retains miner settings. Bitmain notes that an update without retained configuration can remove pool information, while retaining configuration normally preserves it. The wording can vary by firmware, so read the live interface before confirming.

Provide stable electrical power and wired Ethernet for the whole update and first reboot. Suspend automatic restarts, remote controllers and curtailment actions that could interrupt flashing. Keep the correct factory-reset and model-specific recovery instructions available, but do not assume an SD image works across models.

Update one representative miner

Keep the evidence used for Antminer L9 and S21 firmware update, including the applicable date, model, configuration and decision boundary.

Choose a healthy unit that represents the target hardware. Do not use a miner with missing boards, unstable power, overheating, storage errors or an unknown current image as the first test.

Open the authenticated local interface, select the official package and review the retain-settings choice. Start the update once and leave the browser, miner, network and power undisturbed. Do not refresh repeatedly or remove power because the progress display pauses.

Wait for the documented reboot period, then rediscover the IP if DHCP or reset behaviour changed. If the interface does not return, follow the exact model’s official recovery flow rather than uploading another random package.

Verify the L9 after firmware update

Confirm the interface identifies an L9 and shows the intended official firmware. Check all expected hashboards, chips, fans, temperatures and the selected Normal or Sleep state. The L9 manual describes three pool entries in descending priority and automatic fan control.

Verify the Scrypt pool host, worker and payout account independently. Confirm accepted shares and a stable pool average. Do not compare an L9’s GH/s figure with a SHA-256 miner’s TH/s figure as though the units or algorithms were equivalent.

Compare wall power, rejects, hardware errors, temperature and restarts with the pre-change baseline. An update that boots but loses a board or sends work to an unexpected pool has not passed.

Verify the S21-family miner after update

Confirm the complete S21 model and cooling type, firmware and working mode. On air-cooled units, check board and chip detection, fans, inlet and outlet temperature and real board hashrate. On hydro or immersion models, follow the separate liquid-system checks and facility interlocks.

Verify all three pool entries and accepted SHA-256 shares under the intended worker. Allow the pool averaging period before judging hashrate. Record rejects, stale shares and any change in efficiency or power.

Test administration, monitoring and alerts without exposing the interface publicly. Confirm passwords and network restrictions survived or were deliberately restored after a reset.

Observe before a fleet rollout

Bitmain’s firmware guidance recommends trying a small number first and observing the update for at least 24 hours before a wider deployment. For a mixed fleet, use a separate pilot for every model and control-board group.

Define pass criteria before the pilot: correct official version, all boards present, expected accepted hashrate, no abnormal temperature or power, no unexpected restart, correct pools and successful management and recovery checks.

Roll out in batches small enough that the remaining fleet can carry operations and staff can diagnose failures. Pause the batch if one unit breaches a criterion. Do not let central management turn a wrong model selection into a fleet-wide outage.

Recover from a failed or unsuitable update

First preserve evidence: status, logs, LEDs, network lease, exact package and the point of failure. Check stable power, Ethernet and address discovery before assuming the control board is corrupted.

Use factory reset only when the model documentation supports it and pool or network settings are ready to be restored. Use SD-card recovery only with the correct product and controller image. Stop if the instructions do not match the hardware.

If the miner is under warranty or the control board remains inaccessible, contact Bitmain or an authorised repair route before opening or repeatedly flashing it. Repeated attempts can erase evidence and increase damage.

When a firmware update makes sense

A justified controlled change

Update when an official release fixes a relevant security or operational issue, supports the exact hardware and can be tested with stable power, monitoring and rollback.

A written pilot and pass criteria make the decision repeatable across a hosted fleet.

Reasons to postpone

Postpone when the model or control board is uncertain, the release notes do not apply, power is unstable, the miner already has a fault or no matching recovery path exists.

Do not update solely to improve a dashboard version number.

Common L9 and S21 firmware mistakes

• Treating every S21 variant as the same model.
• Cross-flashing an L9 and an S21-family package.
• Downloading firmware from a seller or file-sharing link.
• Interrupting power because the progress display appears slow.
• Forgetting that an update without retained settings can remove pools.
• Rolling out to the full fleet before a 24-hour representative pilot.
• Calling a booting miner successful without verifying accepted shares and every board.

Frequently asked questions

Can I use S21 firmware on an S21 XP?

No. Use the exact package for the complete model and cooling variant. Similar family names do not make images interchangeable.

Can an L9 use S21 firmware?

No. They use different algorithms and hardware. Cross-flashing can make the miner unusable.

Should I keep settings during an update?

It can preserve pools and configuration, but read the exact release and interface. Keep a protected manual record either way.

How long should I test new firmware?

Bitmain recommends a small pilot and at least 24 hours of observation before a wider rollout.

What does Release firmware type mean?

Bitmain identifies Release as the normal official customer firmware type. Unexpected Factory or other types need documented correction.

Will third-party firmware affect warranty?

It can. Review the current manufacturer and seller warranty before installing any unauthorised firmware.

Conclusion

A safe Antminer L9 and S21 firmware update is a set of model-specific controlled changes. Identify the complete miner and control board, obtain only its official image, record settings and baseline, maintain stable power and test one representative unit. Success means the correct release type, every board and cooling component healthy, the intended pools receiving accepted work and at least 24 hours of stable operation. Only then should a documented batch proceed.

Next steps

Review The Mining Shop UK’s security, warranty and repairs guidance before updating an Antminer fleet, and contact the team when a model, control board, third-party image or recovery route is uncertain.