Bitaxe Firmware Update Guide: OTA, Web Flasher, CLI & Building from Source

Why Update Your Bitaxe Firmware?

Your Bitaxe is a tiny, open-source Bitcoin mining machine. Under the hood, it runs AxeOS — an open-source firmware built on the ESP32-S3 microcontroller that handles everything from ASIC chip communication to WiFi networking to the web dashboard you use to configure your miner. Like any actively developed open-source project, AxeOS receives regular updates from the community, and those updates matter.

Firmware updates can deliver measurable hashrate improvements through better ASIC tuning algorithms, new features like TLS-encrypted pool connections and hashrate graphing, bug fixes that eliminate crashes or connectivity issues, and hardware support for newer Bitaxe models. Running outdated firmware means leaving performance on the table — and in solo mining, every fraction of a gigahash counts. A single firmware update has been known to unlock 10-15% more hashrate on certain models just through improved voltage regulation and frequency management.

This guide covers every method for updating your Bitaxe firmware: the quick OTA (Over-The-Air) update through your browser, the browser-based Web Flasher for recovery situations, the command-line bitaxetool for power users, and building from source for developers. If your device is completely unresponsive, also see our SD Card Recovery Guide. Whether you are running a Bitaxe Supra, Ultra, Gamma, Hex, GT, or any other variant (explore them all on our Bitaxe Hub), the process is fundamentally the same — and we will walk you through all of it.

D-Central Technologies has been a pioneer in the Bitaxe ecosystem since its earliest days. We created the original Bitaxe Mesh Stand, developed custom heatsinks and accessories, and stock every Bitaxe variant alongside the full open-source miner lineup. We have flashed firmware on thousands of Bitaxe devices. This guide is written from hands-on experience, not secondhand documentation.

Bitaxe Model & Firmware Reference

Every Bitaxe model runs the same ESP-Miner firmware, but each model requires a model-specific firmware binary that matches its hardware revision number. Flashing the wrong binary for your board will not damage it — the device simply will not boot correctly — but you will need to reflash with the correct file. Here is the complete mapping of Bitaxe models to their hardware revision numbers and firmware files:

When downloading firmware, you will see two types of .bin files on the GitHub releases page:

• esp-miner-factory-XXX-vX.X.X.bin — A complete factory image that includes the bootloader, partition table, AxeOS web interface, and the mining firmware. This is what you use with USB flashing tools (bitaxetool, Web Flasher) and when doing a full reflash.
• esp-miner.bin — The firmware-only binary used for OTA updates through the AxeOS web interface. This file does not include the bootloader or partition table, because those are already on your device.

For standard OTA updates (Method 1), you only need the esp-miner.bin file. For USB recovery or first-time flashing, you need the factory image matching your specific board revision.

Before You Update

Firmware updates on the Bitaxe are low-risk — the ESP32-S3 has a dual-partition scheme, meaning it writes the new firmware to a separate partition and only switches to it after verifying the write was successful. If something goes wrong mid-flash, the device boots back to the old firmware. That said, a few minutes of preparation will save you time and frustration.

Check Your Current Firmware Version

Before updating, confirm what version you are currently running. Open your web browser and navigate to your Bitaxe’s IP address (shown on the device’s OLED screen). In the AxeOS dashboard, look at the bottom of the page or under the System tab. You will see the current firmware version displayed as something like v2.12.2. Compare this against the latest release on GitHub to determine if an update is available.

Method 1: OTA Update via AxeOS Web Interface (Recommended)

This is the simplest and safest method. It takes about five minutes, requires no cables or tools, and preserves all your mining settings. If your Bitaxe is already running AxeOS and connected to your WiFi network, this is the method you should use.

Step 1 — Open the AxeOS Dashboard

On a computer or phone connected to the same WiFi network as your Bitaxe, open a web browser and type the Bitaxe’s IP address into the address bar. This is the IP address shown on the device’s OLED display. It will look something like 192.168.1.42. The AxeOS dashboard should load, showing your miner’s current hashrate, temperature, and status.

Step 2 — Navigate to Settings

Click the Settings tab (gear icon) in the AxeOS navigation. Scroll to the bottom of the Settings page. You will find the firmware management section, which shows your current firmware version and provides options to check for updates and upload firmware files.

Step 3 — Check for Latest Release

AxeOS can check GitHub directly for the latest available firmware. Click the “Check” button next to “Latest Releases.” AxeOS will query the ESP-Miner GitHub repository and compare the latest release against your installed version. If a newer version exists, it will indicate that an update is available and provide a download link.

Alternatively, you can manually download the firmware file:

1. Visit https://github.com/bitaxeorg/ESP-Miner/releases
2. Find the latest stable release (not a beta/pre-release, unless you want to test bleeding-edge features)
3. Download the file named esp-miner.bin — this is the OTA update binary

Step 4 — Upload the Firmware

In the AxeOS Settings page, locate the “Update Firmware” section. Click the “Browse” button and select the esp-miner.bin file you downloaded. AxeOS will begin uploading the firmware to your Bitaxe over your local network. This process typically takes 30 to 60 seconds depending on your network speed.

Step 5 — Verify the Update

When the upload completes, you should see a green “Success! Firmware updated” message. The Bitaxe will automatically reboot with the new firmware. The AxeOS web interface will also update itself and reload the page. This may take an additional 15-30 seconds.

After the reboot:

1. Refresh the AxeOS dashboard in your browser
2. Navigate to the System section and confirm the firmware version now shows the new version number
3. Check that your hashrate is normal and the ASIC temperature is within expected range
4. Verify your mining pool connection is active and shares are being submitted
5. Confirm your wallet address and pool settings are unchanged

That is it. Your firmware is updated, your settings are preserved, and your miner is back to hashing. The entire process takes less than five minutes.

Step 6 — Update the Web Interface (Optional)

In some cases, the AxeOS web interface (the HTML/JavaScript frontend) is updated separately from the mining firmware. If you notice the web interface looks outdated or a release notes mention “www” changes, you can update the web interface independently. In AxeOS, look for the “Update WWW” section in Settings and upload the www.bin file from the same release. This updates only the dashboard UI — the mining firmware remains untouched.

Method 2: Bitaxe Web Flasher (Recovery & First-Time Flash)

The Bitaxe Web Flasher is a browser-based tool that connects directly to your Bitaxe’s ESP32-S3 chip over USB serial. It is the go-to method when your Bitaxe is not connecting to WiFi (so OTA is not possible), when the AxeOS web interface is corrupted or inaccessible, when you are setting up a brand-new bare board for the first time, or when you need to recover a bricked device.

The Web Flasher uses the Web Serial API, which is supported in Google Chrome and Microsoft Edge. Firefox and Safari do not support Web Serial — use Chrome or Edge for this method.

Requirements

• USB-C data cable — Must be a cable capable of data transfer, not a charge-only cable. If your cable only charges your phone, it will not work here. Look for USB cables labeled “data” or “sync.”
• Google Chrome or Microsoft Edge — The Web Flasher requires the Web Serial API.
• Power supply for your Bitaxe — The device needs external power; USB alone is not sufficient for operation. Standard models use a 5V barrel jack (5.5×2.1mm), while the Hex, SupraHex, and GT use 12V XT30 connectors.
• USB serial driver — Your computer may need a driver for the USB-to-serial chip on the Bitaxe. See the driver section below.

USB Serial Driver Installation

The Bitaxe uses either a CP2102 (Silicon Labs) or CH340 (WCH) USB-to-serial bridge chip, depending on the board revision. Your operating system needs the correct driver to communicate with the chip over USB.

How to tell which chip your board uses: Plug the Bitaxe into your computer via USB-C. On Windows, open Device Manager and look under “Ports (COM & LPT)” — you will see either “Silicon Labs CP210x” or “USB-SERIAL CH340.” On macOS, open Terminal and run ls /dev/tty.usb* — you should see a device listed. On Linux, run dmesg | tail after plugging in to see which driver loaded.

Step-by-Step: Flashing with the Web Flasher

1. Power on your Bitaxe using its normal power supply (5V barrel jack or 12V XT30, depending on your model). The device needs power to be flashed — USB alone does not provide enough.
2. Open the Web Flasher in Chrome or Edge: bitaxeorg.github.io/bitaxe-web-flasher/
3. Enter bootloader mode on your Bitaxe:
   • Locate the Boot button on the left side of the device (near the fan/heatsink)
   • Press and hold the Boot button
   • While still holding Boot, press and release the Reset button (located above the Boot button)
   • Release the Boot button
   • The device is now in download mode, ready to accept a flash
4. Connect the USB-C cable from your Bitaxe to your computer
5. In the Web Flasher, click “Connect” — a popup will show available serial ports. Select your Bitaxe (it will appear as a COM port on Windows, or a /dev/ttyUSB device on Linux/macOS)
6. Select your model type and board version from the dropdown menus in the Web Flasher. Match these exactly to your hardware revision number.
7. Select the firmware version you want to flash. The Web Flasher pulls releases directly from GitHub.
8. Click “Start Flashing” and wait. Do not disconnect the USB cable, do not close the browser, do not unplug power. The flash process takes 1-3 minutes.
9. When you see a “Flash Complete” or “Done” message, the flash is finished. Disconnect the USB-C cable.
10. Press the Reset button on your Bitaxe (or power-cycle it) to boot with the new firmware.

Method 3: Command-Line Flash with Bitaxetool (Power Users)

For those who prefer the terminal — or need to script firmware updates across multiple Bitaxe devices — bitaxetool is the official command-line utility. It is a Python wrapper around esptool.py that abstracts away the low-level flash offsets and chip configuration, making the command-line flash as simple as specifying a port and a firmware file.

Install Bitaxetool

You need Python 3.4+ and pip installed on your system. Then install bitaxetool from PyPI:

pip install --upgrade bitaxetool

Identify Your Serial Port

Connect your Bitaxe via USB-C and identify the serial port:

# Windows — check Device Manager, or:
mode

# macOS:
ls /dev/tty.usb*

# Linux:
ls /dev/ttyUSB* /dev/ttyACM*

Your Bitaxe will typically appear as COM3, COM6, etc. on Windows, /dev/tty.usbserial-XXXX on macOS, or /dev/ttyUSB0 on Linux.

Flash the Firmware

Put your Bitaxe into bootloader mode (hold Boot, press Reset, release Boot), then run the flash command. Replace the port and firmware filename to match your setup:

# Flash firmware only (factory image):
bitaxetool --port COM6 --firmware ./esp-miner-factory-401-v2.12.2.bin

# Flash firmware with config file:
bitaxetool --port COM6 --config ./config-401.cvs --firmware ./esp-miner-factory-401-v2.12.2.bin

# macOS / Linux example:
bitaxetool --port /dev/ttyUSB0 --firmware ./esp-miner-factory-601-v2.12.2.bin

Bitaxetool will automatically detect the ESP32-S3, upload the flashing stub, erase the flash, and write the firmware. You will see progress output in the terminal. When it completes, press the Reset button on your Bitaxe to boot with the new firmware.

Alternative: Direct esptool.py (Low-Level)

If you prefer to use esptool.py directly without the bitaxetool wrapper, you can flash the factory image at address 0x0:

esptool.py --port COM6 --baud 230400 write_flash 0x0 ./esp-miner-factory-401-v2.12.2.bin

This is the same thing bitaxetool does under the hood, but it gives you full control over baud rate and flash parameters. Useful if you encounter communication issues and need to try different baud rates (115200, 460800, 921600).

OTA Update via API (Headless/Remote)

If you want to update your Bitaxe firmware remotely without opening a browser — for example, in a scripted environment or over SSH — you can POST the firmware binary directly to the AxeOS API endpoint:

# Update mining firmware:
curl -X POST -H "Content-Type: application/octet-stream" 
  --data-binary "@esp-miner.bin" 
  http://192.168.1.42/api/system/OTA

# Update AxeOS web interface:
curl -X POST -H "Content-Type: application/octet-stream" 
  --data-binary "@www.bin" 
  http://192.168.1.42/api/system/OTAWWW

# Restart after update:
curl -X POST http://192.168.1.42/api/system/restart

Replace 192.168.1.42 with your Bitaxe’s actual IP address. This is particularly powerful if you are running a fleet of Bitaxe devices — you can script the update to roll firmware across all of them in sequence.

Method 4: Building from Source (Developers)

ESP-Miner is fully open-source. If you want to customize the firmware, add features, fix bugs, or just understand how the sausage is made, you can build it from source. This is the cypherpunk way — don’t trust, verify. And modify.

Prerequisites

• ESP-IDF toolchain — Espressif’s official development framework for the ESP32 family. Follow the Espressif ESP-IDF installation guide for your platform.
• Node.js and npm — Required for building the AxeOS web interface frontend.
• Git — For cloning the repository.
• Python 3.4+ — Required by the ESP-IDF toolchain and bitaxetool.

Clone, Build, Flash

# Clone the repository:
git clone https://github.com/bitaxeorg/ESP-Miner.git
cd ESP-Miner

# Initialize ESP-IDF environment (path depends on your install):
. $HOME/esp/esp-idf/export.sh

# Build the firmware:
idf.py build

# Create a merged factory binary:
./merge_bin.sh ./esp-miner-merged.bin

# Flash to your Bitaxe (replace port and config as needed):
bitaxetool --port /dev/ttyUSB0 --config ./config-401.cvs --firmware ./esp-miner-merged.bin

The merge_bin.sh script combines the bootloader, partition table, and application binary into a single factory image that can be flashed in one pass.

Docker Build (Alternative)

If you do not want to install the full ESP-IDF toolchain on your host machine, the ESP-Miner repository includes a Docker-based development container:

# Build the Docker image:
docker build -t espminer-build .devcontainer

# Run the build inside the container:
docker run --rm -it -v $(pwd):/workspace espminer-build /bin/bash
git config --global --add safe.directory /workspace
idf.py build

This is the cleanest approach if you want a reproducible build environment without polluting your system with toolchain dependencies.

Firmware Version History

The ESP-Miner project moves fast. Here are the major releases and what they brought to the table:

For the complete changelog with every commit, bugfix, and contributor credit, check the ESP-Miner releases page on GitHub. This is open-source software maintained by a community of Bitcoiners who believe in decentralized mining. Every contribution makes the ecosystem stronger.

Model-Specific Notes

While all Bitaxe models run the same ESP-Miner firmware, there are hardware differences that affect the firmware update experience. Here is what to watch for on each model family:

Bitaxe Supra, Ultra & Gamma (Single-Chip Models)

These are the standard single-ASIC Bitaxe devices. They all share the same form factor, use a 5V barrel jack (5.5×2.1mm) for power, and have the Boot and Reset buttons in the same positions. The firmware update process is identical across all three — the only difference is which firmware binary you download (match the 3-digit hardware revision number). These models are the simplest to update and the most forgiving if something goes wrong.

Bitaxe Hex (UltraHex) & SupraHex (Multi-Chip Models)

The Hex variants pack six ASIC chips onto a single board, delivering significantly more hashrate. They use a 12V DC XT30 connector for power — not the 5V barrel jack used by single-chip models. Make sure you are providing 12V power during USB flashing. The firmware update process is otherwise the same, but flash times may be slightly longer due to the larger configuration footprint. When selecting firmware, use the 300-series binary (UltraHex) or 700-series binary (SupraHex).

Bitaxe GT (Gamma Turbo)

The GT is the highest-performance single-board Bitaxe, running dual BM1370 ASIC chips at over 2 TH/s. Like the Hex variants, it uses a 12V DC XT30 connector for power. The GT was added as a supported device model starting with firmware v2.12.2 (800-series hardware revision). If you are running a GT, make sure your firmware is v2.12.2 or later for proper hardware support including self-test functionality.

Troubleshooting

For general Bitaxe hardware and connectivity issues beyond firmware, see our Bitaxe Troubleshooting Guide.

OTA Update Fails or Times Out

If the OTA upload stalls, fails, or the browser shows a timeout error:

1. Check your WiFi signal. A weak or unstable connection between your computer and your Bitaxe can cause the upload to fail. Move your Bitaxe closer to the router, or move your computer closer to the Bitaxe. They must be on the same local network.
2. Try a different browser. Some users report better results with Chrome over Edge, or vice versa.
3. Verify the firmware file. Make sure you downloaded the correct esp-miner.bin file (not the factory image, which is larger). If the file is corrupted or incomplete, the upload will fail. Re-download it from GitHub.
4. Power-cycle and retry. Unplug your Bitaxe, wait 10 seconds, plug it back in, wait for it to boot and reconnect to WiFi, then try the OTA update again.
5. Try the curl API method. If the browser-based upload keeps failing, use the curl command to POST the firmware directly to the OTA endpoint. This bypasses any browser-related issues.
6. Use the recovery page. If the AxeOS web interface is partially corrupted, try accessing http://<IP>/recovery — this is a minimal recovery page built into the firmware that provides basic flash functionality even when the main AxeOS interface is broken.

Device Not Detected on USB

If your computer does not recognize the Bitaxe when connected via USB-C:

1. Verify you are using a data cable. Many USB-C cables are charge-only and lack data wires. Try a cable you have used for phone data transfer or file sync.
2. Install the correct serial driver. Check Device Manager (Windows), System Report (macOS), or dmesg (Linux) to see if the CP2102 or CH340 chip is being recognized. Install the appropriate driver if not.
3. Try a different USB port. Some USB hubs and USB 3.0 ports can cause issues. Try a direct USB-A port on your computer (using a USB-A to USB-C cable if needed).
4. Confirm the device is powered. The Bitaxe needs external power from its barrel jack or XT30 connector — USB alone does not power it sufficiently for serial communication in all cases.
5. Enter bootloader mode. Hold Boot, press Reset, release Boot. The device may not show up as a serial port until it is in bootloader mode.

Bricked Device Recovery

A “bricked” Bitaxe is almost always recoverable. The most common cause is flashing the wrong firmware binary (e.g., flashing a 401 image on a 601 board). The hardware itself is fine — you just need to reflash the correct firmware.

1. Enter bootloader mode using the Boot + Reset button sequence described above.
2. Use the Bitaxe Web Flasher at bitaxeorg.github.io/bitaxe-web-flasher/ to flash the correct factory image for your board revision.
3. If the Web Flasher does not detect the device, use bitaxetool or esptool.py from the command line. These tools communicate at a lower level and can sometimes detect devices that the Web Flasher misses.
4. As a last resort, try erasing the flash completely before reflashing:

# Erase the entire flash:
esptool.py --port COM6 erase_flash

# Then reflash with the correct factory image:
bitaxetool --port COM6 --firmware ./esp-miner-factory-601-v2.12.2.bin

Settings Lost After Update

If your mining settings (pool, wallet, frequency) disappeared after an update:

• You likely used a factory flash method (Web Flasher, bitaxetool, or esptool) instead of OTA. Factory images overwrite NVS storage where settings are kept.
• Re-enter your settings through the AxeOS web interface. This is why we emphasize backing up your configuration before any update.
• For future updates, use the OTA method (Method 1) which preserves your settings.

WiFi Not Connecting After Update

If your Bitaxe is not connecting to WiFi after a firmware update:

• Check your WiFi frequency. The Bitaxe only supports 2.4 GHz networks. If your router combines 2.4 GHz and 5 GHz under one SSID, the Bitaxe may try to connect to the 5 GHz band and fail.
• Check your router’s security features. Some ASUS and TP-Link routers have “AiProtection” or “IoT Guard” features that block mining traffic. Disable these if your Bitaxe shows zero hashrate or cannot connect.
• Factory flash resets WiFi. If you factory-flashed, the Bitaxe will broadcast its own WiFi hotspot (AP mode) so you can connect and configure it. Look for a network named “Bitaxe” or similar in your WiFi settings.

Overclocking Settings After Update

If your overclocked frequency and voltage were reset to defaults after an OTA update:

• Some firmware updates may reset overclocking parameters to safe defaults, especially if the update changes the ASIC driver or power regulation logic.
• Re-enter your overclock settings in AxeOS. Navigate to Settings and append ?oc to the URL to unlock the frequency and voltage fields.
• Test gradually. After a firmware update, the ASIC tuning may behave differently. Start at stock settings and work your way up to your previous overclock to ensure stability.

Frequently Asked Questions

When to Contact D-Central

Most firmware updates are straightforward, but occasionally hardware issues masquerade as firmware problems. If your Bitaxe will not boot after multiple flash attempts with the confirmed correct firmware, if the OLED screen stays blank even after a successful flash, if the USB-to-serial chip is not being detected by any computer, or if the device shows signs of physical damage — it is time for professional diagnosis.

D-Central has repaired over 2,500 mining devices since 2016. We know the Bitaxe hardware intimately — we have been building and selling these devices since the earliest days of the project. If your Bitaxe needs repair or you have exhausted all the troubleshooting steps in this guide, reach out to us.

Why D-Central Technologies

D-Central Technologies has been building, repairing, and supporting Bitcoin mining hardware since 2016. We are not resellers copying product descriptions from a manufacturer’s website. We are Bitcoin Mining Hackers — taking institutional-grade mining technology and making it accessible to home miners, one hash at a time.

In the Bitaxe ecosystem specifically, D-Central is a pioneer. We created the original Bitaxe Mesh Stand — the very first commercially manufactured stand for Bitaxe devices. We developed custom heatsinks for both standard Bitaxe and Bitaxe Hex models. We stock every Bitaxe variant — Supra, Ultra, Gamma, Hex, SupraHex, GT — alongside the full open-source miner lineup including NerdAxe, NerdNOS, Nerdminer, and NerdQAxe, with many more always in the pipeline.

When you buy a Bitaxe from D-Central, you are buying from a team that has flashed, tested, overclocked, repaired, and pushed these devices to their limits. This guide exists because we have done every step in it thousands of times. Our mission is the decentralization of every layer of Bitcoin mining — and keeping your firmware updated is part of that mission.

Every hash counts.