The Solo Satoshi Bitaxe Web Flasher installs verified AxeOS firmware for supported Bitaxe, BitForge, NerdAxe, and NerdNOS miners directly from a desktop browser. It combines exact hardware matching, file-integrity checks, recovery tools, optional settings preservation, Bitaxe Turbo Touch screen updates, and local custom firmware flashing in one guided interface.
Firmware is the layer that turns an open-source Bitcoin miner from a collection of components into a working machine. It controls the ASIC, power system, cooling behavior, network connection, pool communication, and the AxeOS dashboard. Keeping that software current matters, but choosing the wrong file or interrupting an installation can also create avoidable recovery work.
This guide explains the live flasher’s current features, how its verification workflow works, when to use it instead of the AxeOS updater, what Preserve miner settings means, and the precautions every home miner should take before writing firmware.
When you are ready to install firmware, open the live Solo Satoshi Web Flasher. This article remains an educational reference for understanding the process and choosing the correct workflow.
Table of contents
- What Is a Bitaxe Web Flasher?
- Why We Built the Solo Satoshi Web Flasher
- What the Web Flasher Does
- Supported Hardware and Flashing Modes
- How to Use the Bitaxe Web Flasher
- What Verified Firmware Means
- Preserve Settings or Perform a Clean Install?
- Web Flasher vs. AxeOS Update
- Browser, Privacy, and Security
- Recovery and Troubleshooting
- Open Source and Transparent
- Bitaxe Web Flasher FAQ
What Is a Bitaxe Web Flasher?
A Bitaxe web flasher is a browser application that communicates with the ESP32-S3 controller in a miner over USB. Instead of installing a desktop flashing utility and manually assembling command-line arguments, the browser guides you through selecting the hardware, choosing a compatible release, approving the USB serial connection, and writing the firmware.
This is different from visiting AxeOS over Wi-Fi. AxeOS is the web dashboard served by the miner itself. A web flasher runs on your computer and communicates with the miner’s bootloader over a USB data cable. That distinction makes USB flashing especially useful when the dashboard is unavailable, Wi-Fi settings are unknown, an OTA update failed, or the miner needs a clean factory installation.
If you are new to the hardware, start with our explanations of what a Bitaxe is and how AxeOS works. The flasher is an installation and recovery tool; AxeOS remains the operating interface you use after the miner boots.
Why We Built the Solo Satoshi Web Flasher
Open-source mining moves quickly. New firmware can add hardware support, improve stability, correct device presets, update pool protocols, refine thermal behavior, or resolve bugs. That pace is valuable, but it also creates a practical problem: release pages can contain many factory images for different board revisions, and similar filenames are not interchangeable.
The goal of the Solo Satoshi Web Flasher is to put the important decisions in a clear sequence:
- Connect the miner you intentionally selected.
- Choose the correct firmware family.
- Match the exact model and printed board revision.
- Show only releases that contain a compatible factory image.
- Verify the downloaded file before it is written.
- Verify the completed write and manage the restart sequence.
The result is a focused workflow for home miners, not a promise that firmware installation is risk-free. Hardware identification, stable power, a reliable data cable, and careful release selection still matter.
What the Web Flasher Does
Discovers Current Compatible Releases
The firmware service monitors approved upstream release sources for Bitaxe, BitForge, NerdAxe, NerdNOS, and Bitaxe Turbo Touch screen firmware. Stable releases are the default. When an eligible prerelease is newer than the latest production release, the interface can expose it as a separate testing channel instead of presenting experimental code as the normal choice.
The newest compatible stable release and a limited set of earlier stable versions are available for supported boards. This provides a controlled rollback path while preventing a newer miner from selecting firmware released before that board existed.
Matches Firmware to the Hardware
The installer separates firmware family, release channel, model, board revision, and version into explicit choices. The exact board number matters because miners that look similar can use different voltage regulators, sensors, displays, ASIC arrangements, or configuration defaults.
Checks the File Before Flashing
For verified releases, the flasher checks the expected file size and SHA-256 digest before opening the installation path. A SHA-256 digest acts like a fingerprint: if the downloaded bytes do not match the digest associated with that release asset, the file is rejected instead of being written.
Verifies the Write and Restarts the Miner
After writing, the application checks the completed ESP flash operation, initiates a normal restart, detects the expected USB disconnect, and waits for the restart sequence to finish. A disconnect during this controlled reset is normal; disconnecting power or USB earlier is not.
Offers Optional Settings Preservation
Verified Bitaxe and NerdAxe factory images can be installed while skipping the designated settings partition. This can retain Wi-Fi, pool, and miner configuration. Preservation is convenient, but it is not a backup and it is not always appropriate when recovering from corrupted or incompatible settings.
Supported Hardware and Flashing Modes
The live firmware manifest, rather than a fixed list in this article, is the source of truth for available model, board, and release combinations. The verified catalog includes supported Bitaxe and BitForge boards, NerdAxe and NerdNOS families, and the Bitaxe Turbo Touch screen controller when a matching approved factory image is available. This includes single-ASIC and multi-ASIC models across the Max, Ultra, Supra, Gamma, Gamma Duo, Gamma Turbo, Hex, SupraHex, Naja Duo, GammaHex, NerdAxe, NerdQAxe, NerdQX, NerdEKO, NerdHaxe, and NerdOCTAXE families.
Verified Releases
This is the recommended path for most users. It presents approved upstream factory images, filters them by hardware compatibility, checks their published digest, and allows settings preservation where supported. If your goal is a normal update, rollback, or recovery, begin here.
BitForge and NerdNOS Firmware Updates
To update BitForge firmware or flash a BitForge Nano, choose the BitForge family and the verified image offered for that hardware. BitForge Nano enters its bootloader through USB automatically, so a normal update does not require opening the enclosure or using a manual BOOT and RESET sequence.
To update NerdNOS firmware or flash NerdNOS, choose the NerdNOS family and its matching board in the verified workflow. If normal flashing does not start, disconnect USB, hold the lower-right button, reconnect USB while continuing to hold the button, then release it and retry. The flasher still checks the approved image, file size, SHA-256 digest, and connected ESP32-S3 before writing.
Bitaxe Turbo Touch Screen Firmware
A Turbo Touch contains two distinct targets: the Bitaxe miner and the touchscreen controller. The Bitaxe Turbo Touch: Screen Only option updates the display controller through its dedicated USB-C port; it does not update the AxeOS firmware running on the miner. Review our Bitaxe Turbo Touch setup guide before choosing a port.
Advanced Custom Firmware
Advanced mode flashes a local merged, bootable ESP32-S3 .bin image built for address 0x0, up to 32 MB, directly to the connected miner’s ESP32-S3 controller. Before writing, the browser checks the basic image structure, calculates its SHA-256 digest locally, and confirms that the connected chip identifies as an ESP32-S3.
This makes the Advanced tool useful for developers building custom Bitcoin mining firmware, including people using AI coding tools to design, modify, debug, or document their firmware. AI-assisted source code must still be reviewed, compiled into the correct merged image, tested for the intended board, and used with a recovery plan. The flasher cannot determine whether generated code is secure, correct, or compatible, and it does not authenticate the publisher. Advanced mode writes the complete image and does not preserve settings.
Developers compiling ESP-Miner can review the upstream project’s build and merged-image documentation. An OTA-only esp-miner.bin, a standalone application binary, and separate bootloader or partition files are not substitutes for the merged image Advanced mode expects.
Hardware Shopping and Support
The live navigation includes a Shop Hardware menu for Bitaxe miners, NerdAxe miners, and the complete Solo Satoshi shop. Each destination opens in a new tab, so the configured flasher session remains open. A language selector makes the guided interface and its safety instructions available in the supported translations.
How to Use the Bitaxe Web Flasher
For a complete illustrated walkthrough, use our dedicated step-by-step Bitaxe firmware update guide. The core workflow is:
- Use a supported desktop browser. Open a current version of Chrome, Edge, or Brave on a desktop or laptop.
- Prepare stable power and a USB data cable. A charging-only cable will not provide the serial connection.
- Open the installer. Visit flash.solosatoshi.com and leave Verified releases selected for a normal installation.
- Connect the miner. Select Connect and approve the correct USB serial device in the browser prompt.
- Choose the family, model, and board. Match the board revision printed on the PCB. Never choose a similar model by appearance alone.
- Select a compatible version. The latest stable release is recommended unless you have a specific testing or rollback reason.
- Choose whether to preserve settings. Leave it off for a clean installation or enable it to skip the designated settings partition.
- Start flashing and wait. Keep the browser open, USB connected, and the correct power supply attached until writing, verification, reset, USB disconnect detection, and restart are complete.
Note: Some boards enter the ESP bootloader automatically. If the connection opens but flashing cannot begin, hold BOOT, press and release RESET while continuing to hold BOOT, then release BOOT and retry.
What “Verified Firmware” Means
“Verified” describes a chain of technical checks; it does not mean that software can never contain a bug.
- Approved source: the release is discovered from a configured upstream open-source firmware repository.
- Factory-image filtering: only expected full factory-image formats and reasonable file sizes enter the verified release catalog.
- Digest matching: the downloaded bytes must match the SHA-256 digest associated with the release asset.
- Hardware filtering: the interface presents firmware compatible with the selected family, model, board, channel, and version.
- Write verification: the ESP flashing process verifies the completed write before the restart sequence is reported as complete.
These controls reduce common selection and transfer errors. They cannot eliminate bugs in upstream firmware, mistakes in identifying physical hardware, unstable power, cable failures, or risks introduced by prerelease and custom builds. You can inspect current upstream Bitaxe releases on the ESP-Miner releases page and learn why transparent firmware matters in our guide to open-source Bitcoin mining firmware.
Preserve Settings or Perform a Clean Install?
| Choice | Best used when | What to expect |
|---|---|---|
| Preserve miner settings | The miner is healthy and you want to keep its Wi-Fi, pool, and saved configuration. | The designated settings partition is skipped. This is convenient, but it is not a backup and old settings can still be incompatible. |
| Clean factory installation | You are recovering from corrupted settings, changing firmware families, troubleshooting persistent problems, or want a known-clean state. | The complete factory image is written. Plan to reconnect and complete first-time setup afterward. |
| Advanced custom installation | You built or intentionally obtained a compatible merged ESP32-S3 image and accept full responsibility for it. | The complete custom image is written. Settings are not preserved, and release authenticity or board compatibility is not guaranteed. |
After a clean installation, follow our Bitaxe setup guide to reconnect Wi-Fi, configure a pool, and verify normal operation.
Web Flasher vs. AxeOS Update
| Situation | Recommended method | Why |
|---|---|---|
| AxeOS opens and the miner works normally | AxeOS OTA update | It is the simplest path and does not require USB. |
| AxeOS will not open or Wi-Fi details are unavailable | Solo Satoshi Web Flasher | USB flashing does not depend on the miner’s existing network configuration. |
| An OTA update failed | Solo Satoshi Web Flasher | A full factory image can restore the bootable firmware layout. |
| You need a clean reset or compatible rollback | Solo Satoshi Web Flasher | The installer offers complete factory images and eligible earlier releases. |
| You compiled a merged ESP32-S3 image | Advanced mode | It accepts a local bootable image built for address 0x0. |
Do not use USB flashing simply because it sounds more complete. When AxeOS is healthy, its built-in updater remains appropriate. When the dashboard is inaccessible or a full factory image is required, the browser flasher becomes the better recovery tool.
Browser, Privacy, and Security
Why a Chromium Desktop Browser Is Required
The verified and Advanced ESP paths use the browser’s Web Serial capability. Web Serial requires a secure HTTPS context and is not supported by every browser. Use a current desktop version of Chrome, Edge, or Brave; Safari, Firefox, phones, and tablets are not supported for flashing. On an incompatible browser or mobile device, the site displays compatibility guidance while keeping the guide, hardware links, language selector, and issue-report option available. The MDN Web Serial documentation explains the browser API and its availability limitations.
What Stays Local
- You choose the USB device through the browser’s permission prompt.
- USB communication occurs between the browser and the selected local device.
- Preserving settings skips the settings partition; it does not read or upload Wi-Fi credentials, pool details, or saved configuration.
- Custom firmware files are read into browser memory, checked locally, and written to the selected device without being uploaded to Solo Satoshi.
- The on-screen technical log remains in the current page session.
Reporting a Firmware Issue
If flashing does not work as expected, select Report an issue and include the miner model, board number, what happened, and what you expected. Add a reply email so the Solo Satoshi support team can follow up. Do not include passwords, Wi-Fi credentials, private keys, seed phrases, or other sensitive information.
Recovery and Troubleshooting
No Serial Device Appears
- Confirm that the cable supports data, not charging only.
- Try another USB port or a known-good cable.
- Close terminal programs or other software that may already hold the serial port.
- Use a supported Chromium-based desktop browser and reload the page.
The Miner Does Not Enter Bootloader Mode
Hold BOOT, press and release RESET while still holding BOOT, release BOOT, and then choose Retry flashing. Exact button placement varies by board, so do not press components or short pins with conductive tools.
The Board Number Is Unclear
Stop before flashing. Inspect the revision printed on the PCB and compare it with the installer’s model and board choices. If the case blocks the marking, consult the manufacturer or seller rather than guessing.
The Miner Still Will Not Boot
Repeat the verified-release path with the exact board selected, settings preservation disabled, stable power, and a known-good cable. If the device remains unresponsive, follow our more detailed Bitaxe recovery and unbricking guide before assuming that the mining ASIC itself has failed.
Open Source and Transparent
The browser application is licensed under GPL-3.0-only, and its production source is available in the Solo Satoshi Web Flasher repository. Firmware remains under the licenses chosen by its upstream projects. The flasher publishes attribution and dependency information on its Licenses & source page.
That separation matters. Solo Satoshi operates the installation interface and verified delivery workflow, while projects such as bitaxeorg/ESP-Miner, ESP-Miner-NerdQAxePlus, and BAP-GT-TOUCH develop the upstream firmware. Open source allows miners, developers, and researchers to inspect the code and understand where each component originates.
Start With the Right File and a Clear Process
A reliable flashing workflow is not about adding complexity. It is about making the consequential choices visible: the exact hardware, the source of the firmware, the integrity of the download, whether settings should survive, and when it is safe to disconnect the device.
The Solo Satoshi Web Flasher brings those choices into one guided browser interface for supported open-source miners. Prepare a good data cable, confirm the board number, use stable power, and take the time to read each selection before installing.
When you are ready, launch the Solo Satoshi Bitaxe web flasher in a supported desktop browser.
Need hardware first? Browse Bitaxe miners, NerdAxe miners, or the complete Solo Satoshi shop. Each link opens in a new tab so you can keep the flasher available.
Bitaxe Web Flasher FAQ
Is this the official Bitaxe flasher?
Does the flasher work with NerdAxe miners?
Can I use the web flasher on a phone or tablet?
Will flashing delete my settings?
Can the web flasher guarantee custom firmware is safe?
What if I select the wrong board?
Does the web flasher send my miner settings to Solo Satoshi?