Solo Satoshi

Solo Satoshi Web Flasher

Flash Bitaxe and NerdAxe AxeOS firmware directly from your browser.

A browser-based AxeOS web flasher for verified Bitaxe and NerdAxe releases, Turbo Touch screen firmware, and local custom Bitcoin mining firmware.

Supported firmware and hardware

The AxeOS flasher supports Bitaxe Max 102; Ultra 201, 202, 203, 204, 205, and 207; Hex 302 and 303; Supra 400 through 403; Gamma 601 and 602; Gamma Duo 650; SupraHex 701 and 702; Gamma Turbo 801; GammaHex 1300; Naja Duo 1201; and the GT-TOUCH display. It also supports NerdAxe, NerdAxe Gamma, NerdEKO, NerdHaxe Gamma, NerdOCTAXE Gamma, NerdOCTAXE+, NerdQAxe+, NerdQAxe++, NerdQX, Q1370, and Q1373. The flasher automatically discovers official releases and offers the newest stable release plus up to five earlier stable versions only when each release contains a factory image for the selected hardware. New hardware cannot be rolled back to firmware released before support for that hardware was added. Turbo Touch screen firmware updates only the display controller, not the Bitaxe GT miner inside the unit.

How the browser flasher works

  1. Connect the miner and approve its USB serial device.
  2. Choose Bitaxe or NerdAxe.
  3. Choose the latest-release or prerelease channel.
  4. Select the exact miner model.
  5. Match the Bitaxe board revision or review the automatically matched NerdAxe board.
  6. Select a compatible firmware version.
  7. Choose whether to preserve miner settings.
  8. Install the verified release and maintain USB and power until the miner restarts.

After a compatible version is selected, the browser prepares and verifies that matching firmware. Changing the hardware or version prepares the newly matched file.

Verification and source transparency

For listed releases, release automation checks the approved upstream repository, expected file, size, and SHA-256 digest published by GitHub. The browser checks the size and SHA-256 again before writing, and the ESP flashing library verifies the completed write. These checks confirm that the bytes match the listed release; they do not guarantee that firmware is bug-free or suitable for every configuration. Corresponding source archives and upstream release pages are linked for inspection.

Advanced custom firmware

Yes. Advanced accepts a local merged, bootable ESP32-S3 .bin built for address 0x0, up to 32 MB. The browser checks its basic image structure and confirms that the connected chip is an ESP32-S3 before writing. The file is never uploaded, but its authenticity, safety, and hardware compatibility cannot be verified. Advanced replaces the complete image without preserving settings, and you are solely responsible for using it.

Frequently asked questions

How is firmware verified before flashing?

For listed releases, release automation checks the approved upstream repository, expected file, size, and SHA-256 digest published by GitHub. The browser checks the size and SHA-256 again before writing, and the ESP flashing library verifies the completed write. These checks confirm that the bytes match the listed release; they do not guarantee that firmware is bug-free or suitable for every configuration.

Can I test prerelease firmware?

Yes. When an official prerelease is newer than the latest production release, select Prereleases. If no eligible prerelease exists for that firmware family, the option is disabled and Latest Releases is selected automatically. Prerelease firmware may contain bugs or require recovery.

What happens if I change my firmware selection?

The Flash firmware button always uses the image matched to the current family, channel, model, board, and version. Changing a selection prepares and verifies the newly matched image. A previously verified image may be reused from memory or the browser cache, but its file size and SHA-256 must still match before it can be written.

Can I flash my own compiled firmware?

Yes. Advanced accepts a local merged, bootable ESP32-S3 .bin built for address 0x0, up to 32 MB. The browser checks its basic image structure and confirms that the connected chip is an ESP32-S3 before writing. The file is never uploaded, but its authenticity, safety, and hardware compatibility cannot be verified. Advanced replaces the complete image without preserving settings, and you are solely responsible for using it.

How do I put my miner into bootloader mode?

Bootloader recovery depends on the hardware. For Bitaxe and NerdAxe, hold BOOT, press and release RESET while continuing to hold BOOT, then release BOOT. BitForge Nano uses automatic USB bootloader entry and should not be opened. For the NerdNOS LilyGO screen, unplug USB, hold the lower-right button, reconnect USB while continuing to hold it, then release the button. Use these recovery steps only if normal flashing does not start.

Does Turbo Touch screen firmware update the miner inside it?

No. Bitaxe Turbo Touch (Screen Only) updates the touchscreen ESP32-S3 controller through the screen USB port. It does not update the Bitaxe GT miner inside the unit. To update the miner, select the matching Bitaxe model and board in Verified releases and connect the miner USB port.

What happens after an ESP firmware image is written?

The flasher reports four post-flash stages: firmware written and verified, device restarting, USB disconnect detected, and restart complete. Keep USB and power connected until all four stages finish. The USB disconnect shown during the automatic reset is expected.

What is sent when I report an issue?

The reply email and description you enter are sent to Solo Satoshi support. The email is used only to respond about that report and is not added to a marketing list or separate flasher contact database. Cloudflare processes ordinary request data for rate limiting and Turnstile bot protection, and Proton delivers and stores the support email. Never include passwords, Wi-Fi credentials, private keys, seed phrases, or other sensitive information.