GUIDE 05 / RECOVERY
Recover a machine that will not boot
Signature locks, failed flashes and silent controllers. Almost every case is recoverable, and none of them need soldering.
First, rule out the boring causes
- The machine took a new DHCP address - scan the range again
- The network cable moved during the flash
- The PSU tripped - listen for the fans on power-up
Case 1 · Toolkit reports an ssh error
Stock firmware from March 2024 or newer carries Bitmain signature locks. Update the miner with the newest stock web update first, then retry the toolkit flow with version 1.7.1 or newer.
Case 2 · USB port locked (Amlogic, stock from September 2025)
These boards lock the USB port as well. It has to be unlocked before anything else works. Write to support with the model and the stock build date - we hand you the verified files and stay with you until it mines again.
Case 3 · Controller silent after a flash
- Write a recovery SD cardUse Rufus with the recovery image for your control board
- Insert and power onThe board boots from the card, not from NAND
- Wait for the LED patternThen power off and remove the card
- Scan the networkThe machine answers on its address again
What not to do
- Do not cut power in the middle of a flash - that is what creates most of these cases
- Do not flash a file for a different board because "it looks the same"
- Do not keep retrying a failing flash before you know why it failed
When to write to us
Any persistent mismatch, any signature or USB lock, any machine that needed two recovery attempts. Send the model, the control board, the stock build date and what you saw. Never send credentials or production access details.