When an engine controller throws a fault that won't clear, the question is rarely "is it broken?" — it's "is this a software problem or a hardware problem?" The answer decides whether you spend a couple hundred dollars or a couple thousand.
What a reflash actually fixes
Reflashing rewrites the calibration and firmware on a module whose hardware is fine. It's the right call when the fault is in the software layer: a corrupted or interrupted update, an outdated calibration causing driveability complaints, a known TSB reflash, or a unit that locked up mid-program. The silicon is healthy — it just needs the correct, VIN-matched data written back to it.
When you actually need a replacement
Hardware failures don't reflash away. Cooked output drivers, a shorted internal power supply, physical board damage, or memory that won't hold a write are replacement (or repair) territory. We confirm this on the bench rather than guessing — if the module won't accept and verify a clean write, no amount of reprogramming will save it.
The cloned-unit middle ground
Between "reflash" and "buy new and program" sits cloning. When a replacement is discontinued, or the original can't be programmed online because it's security-locked, we read the data off your original and write it to a matched donor — so the new unit comes up VIN-correct and plug-and-play. For a lot of older or NLA modules, that's the only path left.
What it saves
A reflash or board-level repair is a fraction of a dealer-supplied, programmed module — and it keeps the original, matched unit in the car. We bench-test every write against spec before it ships back.
Send us the module and the symptom. We tell you which path it actually needs — with a signed report.
Got a module that won't cooperate?
Mail-in diagnostics, reflashing, restoration, and custom engineering — nationwide, with a signed report on every job.
