The operation is still running
Check the operation status rather than judging progress from a browser tab alone. While firmware is being written, keep power and the network connection in place and avoid launching another operation. Record the operation and messages if progress stops changing. A universal timeout would be a guess without the device and log.
For a planned web update, confirm the displayed model, controller and installed version before submitting the package. Current update interfaces include an option to retain settings. Check that choice deliberately rather than assuming an old configuration will always return.
The package was rejected and the miner is still available
Keep the rejection text and compare the package with the exact model and board. If the miner is on stock Bitmain firmware, our VNISH archive should not be sent through its stock web updater. If VNISH is already running, use the applicable update route.
Toolkit installation and Toolkit update are separate operations. An archive belongs in the selected firmware directory without unpacking or renaming. Fix a confirmed selection mistake before retrying; a rejected file does not by itself require board recovery.
It restarted, but the result is different from the plan
Read the version actually running and check that you are opening the intended device. Compare it with the completed operation and selected package. If the miner is CVITEK and starts stock after a restart, check the exact version's launch instructions. Toolkit Restore firmware can launch VNISH on applicable CV devices; that name does not mean restoring factory stock. It is not a generic command for every board or every boot failure.
If the interface runs but a board, cooling condition or pool result is wrong, use the first-boot checks. Keep that problem separate from a machine that does not boot at all.
The miner no longer reaches its normal interface
Record the last completed action, the model and board, the previous firmware and the file used. Note whether the device is found on the local network and what its indicators do. A board-specific service route may now be needed, but those observations must select the image and method.
Send the details to our support team before trying images for similar models. This is the recovery branch. If your aim is simply to remove VNISH from a working miner, use our separate return-to-stock guide instead.
Questions and answers
Should I cut power when an update seems slow?
Do not interrupt an active firmware write to test that idea. Check the operation status and keep the messages for a device-specific next step.
Does Restore firmware in Toolkit mean return to Bitmain stock?
Not necessarily. Current Toolkit documentation uses Restore firmware for launching VNISH on CVITEK after restart. Read the operation description and the route for the exact device before confirming.
Can I use a recovery image from a similar S19 or S21?
Choose the exact model and control-board route. A similar family name does not establish that the recovery image matches your hardware.
Tell us the state after the last operation
The model, board, package, final message and current boot state let us choose the next step without guessing.