Pre-action identity tool · reviewed August 27, 2026
Use the full chassis label first. A family name or hashrate is not enough to select firmware or a repair part. Confirm the exact model, algorithm, printed hashrate variant, control-board or platform marking, and PSU branch where relevant.
Capture the complete model spelling, suffix and capitalization, printed hashrate variant, and serial number. Photograph the entire label instead of transcribing it from memory or a resale listing.
Separate SHA-256 T-series Bitcoin hardware from algorithm-specific A-series hardware. An “A” prefix is not an algorithm and does not identify Bitcoin compatibility.
If the normal interface is reachable, screenshot its complete model/build string, firmware version, build date and full platform-version text. Record board and PSU markings only when safely visible.
Use the strictest state that fits. The result identifies what is known; it does not certify a firmware file or replacement board.
The manufacturer’s legacy support selector contains T1, T2-family and T3-family records. That establishes family classification—not cross-model firmware compatibility. Exact suffixes, hashrate variants and visible platform branches still matter.
An Innosilicon A-series name does not identify a Bitcoin miner. Identify the exact model and algorithm before choosing firmware, pool settings or repair information.
This is the order and branch vocabulary still represented in the manufacturer’s legacy support catalog. It is not an assertion that firmware files are currently available. “No branch label” means only that the legacy page exposes no named branch; it does not prove one universal build.
| Selector label | Visible branch | Additional identity evidence |
|---|---|---|
| T3s | No branch labelled | Manufacturer Q&A also names T3S-39T. |
| T3+ Pro | G19 / SOC | Selector does not encode a hashrate. |
| T3+ | G19 / SOC | Legacy product category also names a 57T variant. |
| T3h | SOC | Do not silently normalize this to every T3H/T3H+ label. |
| T3-43T | No branch labelled | Exact hashrate is encoded in the selector. |
| T2Th+ | G19 / SOC | Selector does not encode a hashrate. |
| T2Thf+ / T2Thl+ | No branch labelled | Branch-independent status is not proven. |
| T2Th | No branch labelled | Manufacturer Q&A names 28T, 29T and 30T. |
| T2Thm | No branch labelled | Manufacturer Q&A names 28T, 29T and 30T. |
| T2Thf | G19 / SOC | Manufacturer Q&A names 27T, 28T and 29T. |
| T2Tz-30T | SOC | Manufacturer Q&A also names 28T and 29T. |
| T2T+(32T) | G19 / SOC | Exact hashrate is encoded. |
| T2Ts-26T | G19 / SOC | Exact hashrate is encoded. |
| T2Ti-25T | G19 / SOC | For T2Ti, the manufacturer specifically says to inspect whether the full platform-version text contains “soc”; do not generalize that rule automatically. |
| T2T-24T | G19 / SOC | Exact hashrate is encoded. |
| T2 | G19 / SOC | Selector does not encode a hashrate. |
| T1 | G19 | No SOC choice is represented; that does not establish all possible production history. |
The support estate is legacy: its pages return HTTP 200, but the firmware-data backend and tested package endpoints were unavailable during this review. A catalog record is not current download availability.
The letter A does not mean one algorithm. Use the exact model, the manufacturer’s product class, and the expected hashrate unit together.
LTCMaster / Scrypt families. The manufacturer A6 page describes it as LTCMaster. These are not SHA-256 Bitcoin miners.
DashMaster / X11 family. Do not route it to T-series Bitcoin firmware.
CryptoMaster / CryptoNight family. Algorithm identity must precede firmware or pool configuration.
ZMaster / Equihash family. The manufacturer A9++ page confirms the Equihash classification.
ETH / Ethash family. Catalog values such as 5G, 6G and 7G are memory-capacity branches—not terahashes per second.
Absent from the reviewed manufacturer legacy support catalog. Do not invent identification or firmware rules from a secondary listing.
Record the complete string, not a simplified guess. “G19” and “SOC” are branch vocabulary in parts of the catalog; neither is a universal board, firmware family or replacement-part compatibility class.
t2tz.soc package compatibility declaration. Those facts do not transfer across the family.Record PSU manufacturer, version and any visible error field when already available. Do not install an unverified tool merely to obtain them.
The manufacturer historically distinguishes QB/HK routes from GP routes. For GP, versions below 12.66 and above 12.66 use different firmware branches; exactly 12.66 is undocumented and must be escalated. One affected GP route carries a mandatory 15-minute no-operation, no-power-interruption and no-network-interruption window.
This matrix does not make the named models interchangeable and must not be generalized to other T2/T3 units.
Family name alone
Hashrate alone
Exterior case style
Release year
Default IP or credentials
A familiar filename or UI
An online parts title
One G19/SOC word
If any evidence conflicts, preserve all versions of it and use the unresolved path.
Photograph the complete chassis label and record the exact model spelling, suffix, printed hashrate and unit, and serial number. Treat the label as the first evidence field, not the final firmware decision.
Nearby models can expose different hashrate variants, G19/SOC platform branches, control boards or PSU requirements. Firmware requires the complete hardware and source record.
No. T-series records are SHA-256 Bitcoin-miner families, while A-series names span Scrypt, X11, CryptoNight, Equihash and Ethash hardware. Use exact model and algorithm documentation.
Photograph the full chassis label and, only when safely accessible with power disconnected, relevant control-board and PSU labels. Also capture the complete interface platform/version string if reachable.
Mark the identity unresolved, preserve screenshots and photographs of every conflicting field, and request identification. Do not choose the closest model or write another package.
Yes. Confirm exact model, hashrate variant, platform/control-board branch and any relevant PSU branch before evaluating a source or file.
Last reviewed August 27, 2026.Related products, repair, and setup paths