Goldshell KD-MAX – Firmware Version Mismatch

Identify the exact running firmware version. Browse to `http://<miner-IP>` and open the System tab. Note the version (e.g. `2.1.x` or `2.2.4`). Note your hardware revision sticker on the back of the unit. Take photos of both. This is the baseline you return to if anything goes sideways during the upgrade or recovery.

Download the correct `firmware-Goldshell-KDMAX-*.cpb` from the official Goldshell GitHub at github.com/goldshellminer/firmware. Look in the KDA-Miner directory for `firmware-Goldshell-KDMAX-2.2.4.cpb` (current as of 2026). Verify the filename contains `KDMAX` exactly - not `KD5`, not `KD-BOX`, not `CK-LITE`. Download to your laptop, not direct to the miner.

Hard power-cycle the miner before any upgrade. Power off at the breaker for 30 seconds. Power on. Wait 5 minutes for the eMMC filesystem check to complete. Confirm the dashboard returns to its pre-upgrade state. This clears any wedged daemon state from prior failed attempts and gives the upgrade a clean baseline to write to.

Disable WiFi entirely if the miner has it configured. System → Network → delete WiFi config. Confirm the unit is on Ethernet with a wired DHCP lease. WiFi-initiated upgrades are the single largest source of mid-flash bricks across the entire Goldshell lineup, KD MAX included. Goldshell's Zendesk requires Ethernet for upgrades for exactly this reason.

Confirm the miner is on a UPS or at minimum a stable circuit. A KD MAX pulls 3350 W steady-state. Line sag during the flash is enough to corrupt the eMMC. Without a UPS: schedule the upgrade for a low-grid-load window and unplug other heavy loads on the same circuit during the flash window.

Upload the correct `KDMAX` `.cpb` via the local web UI, NOT Goldshell Hub. Navigate to `http://<miner-IP>` → System → Upgrade Firmware → upload the file → Update. Wait 5-10 minutes for the flash and reboot to complete. Watch the LED. Do NOT touch the power, network, or browser tab during the flash window.

After reboot, verify the dashboard reports the new version. The System tab should show `KDMAX 2.2.4` (or the version you flashed). If the version did not increment, the upgrade did not commit - the unit booted the prior partition. Try again from Step 6 with the unit fresh-rebooted. If repeated attempts fail to increment the version, eMMC corruption is suspected - escalate to Tier 3.

Confirm all hashboards report `normal` post-upgrade. Browse to the dashboard's hashboard view. Expect the full configured count of hashboards present and reading nameplate frequency. Any hashboard reading `abnormal` or zero hash is the firmware-mismatch tell - go to Tier 3 if cross-flashing of a wrong-model image is suspected, or to per-hashboard hardware diagnostics if the firmware is confirmed correct.

Let the miner stabilize for 30 minutes at full hashrate before declaring victory. Watch the pool side: hashrate should converge to nameplate (40.2 TH/s ± 5%) within 15-20 minutes. If hashrate sits at exact 75%, 50%, or 25% of nameplate, you have lost one or more hashboards - go back to Step 8 and confirm the dashboard hashboard count.

Document the working firmware version in a permanent location. D-Central recommends a sticker on the chassis with: model, serial number, firmware version, date flashed, hardware revision, MAC address. Future upgrades depend on this baseline. Without it, you'll be reverse-engineering the install state next time something breaks.

Email Goldshell support for the `burn-KDMAX.img` recovery image. Subject: `KD MAX SD-card recovery image request - SN: <serial>`. Body: model exactly as printed on the sticker, serial number, the firmware that was being flashed when the brick happened, the symptom you're seeing now (CPBO failed, no network, hashboards missing). Response: 24 hours to 2 weeks depending on Chinese holidays. Start the email clock now while you prepare the SD card.

Prepare a quality 8-16 GB microSD card. Samsung EVO Plus or SanDisk Industrial. Class 10 / U1 minimum. Cheap Class 4 cards corrupt mid-write on the recovery flash and add a second brick on top of the first. Cost: $10-20 CAD. If you run a home lab you probably have one in a drawer; if not, order before the recovery image arrives.

Flash the `burn-KDMAX.img` to the microSD with balenaEtcher (etcher.balena.io). Click `Flash from file` → select the image → `Select target` → triple-check the target is the SD card and not your laptop's SSD → Flash. Etcher verifies the write automatically. A red X means a bad card - get a better one and retry. Eject when complete.

Insert the SD card into the KD MAX control board's microSD slot, power-cycle, wait 10-20 minutes for the recovery script to complete. The slot is on the control board - opening the chassis is required (4-8 Phillips screws on the top cover). Power off at the breaker, insert the card fully seated, power on, do NOT plug Ethernet yet. Watch for an LED pattern change indicating the recovery script is rewriting the eMMC. Recovery completes when LEDs go dark or revert to a normal pattern.

Remove the SD card, cold-boot, verify on `find.goldshell.com`. Power off, physically remove the SD card, power on, wait 2 minutes. Run the discovery tool - the unit should appear on the LAN with a fresh DHCP lease. Browse to its IP, log in with default credentials (`admin` / `123456789`), immediately change the password, then verify firmware version and hashboard count. If everything looks correct, run the Tier 2 burn-in to confirm stability.

When to stop DIY. Tier 4 territory if: (a) two or more SD recovery flashes fail to complete with quality cards, (b) the eMMC shows visible damage or repeated corruption indicating cell wear, (c) the control board has compound failures (dead Ethernet PHY, dead fan connector, no power LED on control), (d) you cross-flashed a CK LITE image and the unit no longer responds to SD recovery, or (e) the hashboards themselves are damaged from running with wrong drivers (overcurrent on chip rails is a real outcome of a wrong-file flash).

What D-Central does at the bench. We maintain a verified `KDMAX` firmware archive across the supported version range, a known-good `burn-KDMAX.img` library, BGA rework gear for eMMC chip-level swaps when SD recovery fails, and a programmable bench load fixture for hashboard validation post-recovery. We're the only Canadian shop documenting Goldshell-specific repair on the KD MAX. No 6-week China-ship turnaround. No 'we don't service Goldshell' tickets.

Ship safely. ESD bag the control board; foam-cradle the chassis; double-box with at least 5 cm of foam on every side. Include a note: model, serial, firmware version that was being flashed, what error you saw, whether you tried Tier 3 SD recovery (we'll know from slot wear), and your contact info. Ship to D-Central HQ. Typical turnaround 5-10 business days from receipt for KD MAX firmware repairs given the `burn-*.img` email loop with Goldshell support.