Goldshell KD-BOX Pro – Not Hashing After Setup

Full cold boot at the wall. Power off the KD-BOX Pro by unplugging the 12V barrel connector or killing the wall outlet. Wait a full 60 seconds (not 5, not 10) so PSU caps drain and every ASIC register resets to hardware defaults. Power back on. Watch fans ramp, green LED come solid, web UI load, and the hashrate climb to nameplate ~2.6 TH/s within 5-7 minutes. Cold boots clear the 2.1.x warm-reboot hung-state bug, transient kd-pro-1 chip-init stalls, and post-firmware-flash zombie states. Log wattage, ambient temp, and firmware version before moving on for any escalation.

Switch pool to Dxpool Kadena as a control test. Web UI Pool Configuration. Screenshot current settings first. Set Pool 1 URL to stratum+tcp://kda.ss.dxpool.com:5831, Worker to YOUR_DXPOOL_USERNAME.kdboxpro01, Password to x. Save. Cold boot. Wait 10 minutes. Check Dxpool dashboard for accepted shares. If shares flow, the original pool was outside the Goldshell BOX whitelist (officially Dxpool plus F2Pool only - Zendesk KB 17169151093657). NiceHash and ViaBTC Kadena often connect but never produce accepted work on Goldshell BOX firmware.

Re-type the worker name from scratch - the unsung Tier 1 fix. Worker field in Pool Configuration: delete the entry, re-type manually using only [a-zA-Z0-9.-]. Do not paste from a PDF, Discord, webmail, or Google Doc. Invisible zero-width characters and directional markers ride along on copy-paste and silently break mining.authorize at the pool. The pool says online because TCP handshake worked, but the worker never authenticates so zero shares accept. Save, cold boot, wait 5 minutes, watch the pool dashboard.

Check ambient temperature and intake airflow. The KD-BOX Pro is more prone to cold-start lockup below ~18 C ambient. Canadian basement in January? Move the miner to a warmer space for the first cold boot. Confirm rear exhaust has 15 cm clearance and front intake isn't choked with dust. A dust-clogged intake starves the hashboard of cooling and can trigger firmware-level throttle-to-zero behavior on certain Goldshell builds - the miner reports healthy but no work dispatches.

Factory reset via the web UI. Setting then Reset. Wait for the reboot. Reconfigure pool, worker, and password from scratch - do not restore from a saved binary config file. Stale entries and zero-width characters accumulate across firmware updates and migrate cleanly through binary configs while a fresh manual config doesn't carry that baggage. Screenshot your known-good text config after success so future resets are 60 seconds of typing, not an archaeology dig.

Hard-wire ethernet and disable WiFi for any firmware work. Goldshell explicitly requires ethernet for firmware upgrades and downgrades on every BOX-series miner including the Pro. The Zendesk firmware KB 16805936980633 is unambiguous. WiFi flashes brick devices mid-flash at an unacceptable rate. If your Pro is WiFi-only, run a temporary ethernet drop before touching firmware. After firmware work, you can return to WiFi for normal operation, but never flash over WiFi.

Change the default admin / 123456789 password before anything else. The KD-BOX Pro ships with this default credential and is a documented target for pool-hijack botware if port-forwarded. Multiple security researchers have written up real-world cases of attackers scanning for default-cred Goldshell miners and silently redirecting hashrate to attacker wallets. Any Pro on a home LAN with default creds is one misconfigured router away from the same. Change via web UI password change or passwd over SSH. Mining Hacker sovereignty baseline - non-optional.

Downgrade firmware to the last known-good Pro release. Pull the current known-good KDBoxPro-2.0.x family build (or whatever the Goldshell firmware GitHub currently calls stable for the Pro - verify against the issue tracker before flashing) from the official Goldshell mirror or GitHub release. Upload via web UI System Firmware Upgrade over ethernet. Wait the full flash cycle (5-10 minutes). Do not power-cycle mid-flash. After reboot verify firmware version. Cold boot. Wait 10 minutes. Hashrate climbs to nameplate. Fixes the 2.1.x-pro cgminer regression in ~70% of field cases.

Log-dive via SSH. SSH is usually enabled by default on KD-BOX Pro firmware. After changing password (Step 7): ssh admin@<miner-ip>. Once in: tail -n 200 /tmp/cgminer.log and dmesg | tail -n 100. Look for kd-pro-1 init fail, chain X disabled, ASIC detect failed, nonce out of range, I2C errors, PMIC chatter. Paste anomalies into the D-Central support Discord or Goldshell firmware GitHub issues - community pattern-matching usually identifies the failure family in minutes.

Swap PSU and 12V cable with a known-good set. Borrow a spare Goldshell brick or use a Mean Well LRS-350-12 with a DC barrel adapter sized for 18-20 A continuous. Confirm 12V line reads 12.0V plus or minus 0.2V with a multimeter under load. A sagging PSU produces chip-init failures that look exactly like firmware bugs. If the miner hashes with the known-good PSU, RMA or recycle the original. Never daisy-chain PSUs across multiple miners on the BOX line - barrel adapter contact resistance accumulates and brownouts become intermittent and impossible to diagnose.

SD-card recovery flash. If the Pro is stuck on bad firmware and won't accept a web-UI upgrade or downgrade, it's SD-card time. Email hello@goldshell.com to request the burn-kdboxpro-*.img recovery image - Goldshell does not publish these on GitHub. Write the image to a FAT32-formatted SD card with balenaEtcher or dd. Power off the Pro. Open the case (four screws on the lid). Locate the microSD slot on the control board. Insert the recovery SD. Power on. The miner auto-flashes - LED pattern follows the James Chambers SD-card recovery guide. Power off, remove SD, reassemble, cold boot.

Hashboard visual and thermal inspection. With case open and miner unplugged, inspect the kd-pro-1 ASIC and surrounding PMICs under good lighting. Photograph for documentation. Look for scorched pads, lifted components, swollen electrolytic caps, cracked solder joints near thermal-stressed areas, discoloration around the PMIC. Reflow a suspect chip only if you have a proper hot-air station and rework experience. Otherwise document findings and ship to a repair shop (D-Central or equivalent) with photos attached to the ticket.

Hashboard swap between suspect and known-good Pros. If you own two KD-BOX Pro units, swap hashboards between them - handle the FPC ribbon carefully, it tears easily. Track which chassis fails after the swap. This isolates failure to hashboard vs. control board in a single test. This is a diagnostic procedure, not a production fix. Re-seat original hashboards once you know which side is bad, then plan the replacement and source the part.

Replace the control board. If isolation points to control-board failure, replacement KD-BOX Pro control boards are available through Zeus Mining, BT-Miners, and similar parts specialists at roughly CAD $90-160. Swap is four screws and one ribbon cable. Document firmware version before and after the swap - a fresh control board usually ships with whatever factory firmware Goldshell loaded at production, which you may need to re-downgrade to a known-good Pro release immediately on first boot before pointing at a pool.

Replace the hashboard / PMIC. A failed kd-pro-1 or PMIC is a full hashboard replacement unless you have chip-level rework capability. Replacement KD-BOX Pro hashboards run roughly CAD $250-400 depending on supplier and revision. At that cost, compare against a used KD-BOX II market price (~CAD $500-750) before committing. For many owners, a used KD-BOX II is the more economical path than repairing a Pro with a dead hashboard.

Ship to D-Central ASIC Repair if Tier 1-2 fixes are exhausted, SD-card recovery is required but you lack bench tools, the hashboard shows visible damage, or per-chip isolation suggests reflow territory. D-Central offers diagnostic plus repair for Goldshell BOX-series including the Pro, with flat-rate diagnostic fees and Canadian-dollar pricing - effectively zero Canadian competition in this repair vertical. Book a repair slot at d-central.tech/services/asic-repair/ or open a ticket with model, firmware version, symptoms, wattmeter reading, and a cgminer log excerpt.