“I need my ECU done” describes at least seven different operations, and picking the wrong one is the most expensive mistake in this whole field. Clone, IMMO-OFF, virginise, unlock, checksum repair, PIN or security-code extraction, and OE programming are not interchangeable. They solve different problems, run through different routes, and cost anywhere from nothing to several hundred dollars. This page is the decision tree.
Read the symptom column first. Almost everybody arrives with a symptom, decides for themselves which operation it implies, and then orders that operation. Roughly a third of the time the self-diagnosis is wrong, and the money spent buys a correctly executed solution to a problem the car did not have.
The seven operations at a glance
| Operation | What it does | Typical trigger | Route with us |
|---|---|---|---|
| Clone | Copies the original module's identity into a donor | Original module failed, still readable | Network |
| IMMO-OFF | Disables the module's immobilizer check | Donor module, original unreadable or gone | File service, $100 |
| Virginise | Returns a used module to an unmarried state | Used module to be re-paired by OE software | Network |
| Unlock | Removes read/write protection so the module can be accessed | Tool returns a partial or protected image | File service, $150 |
| Checksum repair | Recalculates validation blocks on a modified image | Modified file refuses to write or boot | File service, $100 |
| PIN / security code | Recovers the code a programming tool asks for | Key or module programming prompts for it | Network |
| OE programming | Manufacturer software teaches a module the vehicle | New or replacement module fitted | Live session, $100–$250 |
Two of these we automate as file operations today: IMMO-OFF and checksum repair, on the variants listed in our coverage matrix. Unlock is a separate file product on the Chrysler GPEC families. OE programming is a booked remote session. Clone, virginising and PIN work go to the specialist network— and saying which is which is more useful to you than claiming we do all seven.
Clone versus IMMO-OFF — the decision that matters most
This is the fork that catches the most people, so it is worth slowing down on.
A clonereads the original module and writes its contents — calibration, immobilizer secrets, VIN, adaptation values — into a physically identical donor. The car cannot tell the difference. The immobilizer chain stays intact, the vehicle's identity is preserved, and nothing about the security system has been weakened. It requires that the original module is still readable, which is the whole catch.
IMMO-OFF takes the donor module and disables its side of the immobilizer handshake, so it will run the engine without ever satisfying a challenge from the vehicle. This is the answer when the original module is dead, missing, water-damaged, or was already thrown away by whoever had the car before you.
The engineering preference is clear and we state it against our own commercial interest: if the original module can still be read, clone it. A clone keeps a theft deterrent working. An IMMO-OFF removes one. Both make the car start; only one leaves it the way the factory intended.
Where IMMO-OFF is genuinely the right call — and it often is — it is a $100 file operation against your own read on a covered variant, returned in seconds. Our IMMO-OFF cost guide covers the pricing and the qualifying conditions in full.
Virginising — the third option people forget
Virginising resets a used module to the state it was in before it was married to any vehicle, so manufacturer software can pair it to the new car normally. On platforms that support it, this is the cleanest possible outcome for a used-module swap: no patch, no removed security, and the module ends up genuinely belonging to your vehicle rather than pretending to.
The reason it gets forgotten is that it usually needs both halves of a two-step job — the virginising itself and then an OE programming session to complete the pairing. People price the two steps separately, compare each against a single $100 patch, and pick the patch. Sometimes that is right. On a late-model car with a component-protection scheme, it usually is not, because a patched module that never gets adopted by the vehicle produces a second round of faults nobody budgeted for.
Unlock is not the same as IMMO-OFF
An unlock removes read/write protection so the module can be accessed at all. It does not modify calibration and does not touch the immobilizer. It is the step before the work, not the work.
The best-known case is the Chrysler GPEC2 and GPEC2A families, where the module returns a protected or partial image until it has been unlocked. Our GPEC unlock guide covers which vehicles carry those modules, the read methods that work, and both routes — the $150 instant file operation if you can read the module yourself, or the $250 mail-in if you cannot.
If a tool reports a suspiciously small file, or a read completes far faster than the family should allow, protection rather than immobilizer pairing is the likely story. The size check is in our read-methods guide along with the read-twice-and-diff habit that catches the rest.
Checksum repair — the one nobody orders on purpose
Nearly every checksum job arrives as a complaint about something else. A tuner sent a file back and the tool refuses to write it. Or it wrote and the module will not boot. Or it boots and immediately throws an internal-performance fault.
Modules validate their own contents. Change a byte and the arithmetic no longer agrees, so the module rejects the image as corrupt — which, from its point of view, it is. Checksum repair recalculates those blocks so a legitimately modified file passes its own integrity test. It does not change what the modification does; it just makes the module willing to accept it.
Ours runs at $100with per-family algorithm support — ME7 for the older VAG modules, the MEDC17 library for Bosch MED17 and EDC17, the Trionic implementation for Saab, and in-house work on the BMW Siemens entries. Details are in the checksum repair guide. Always send the untouched original alongside the modified file: verification against an original is the difference between a repair and a guess.
PIN and security-code recovery
Some programming procedures will not start without a numeric code held in the vehicle — asked for by name in the tool, and readable only from the right module region. Extracting it is a distinct skill and a distinct product line, and it is one we route to the network rather than automate.
It also carries the same ownership requirement as anything else touching a security chain. We require proof of ownership for these operations and decline the job when it is not forthcoming, on every make, without exception.
OE programming — when no file is involved at all
If a brand-new module has been fitted and simply needs to learn the car, there is nothing to read, patch or repair. The manufacturer software talks to the module and configures it. That is a booked remote session: $100 on GM, $150 on Ford, Nissan and Mazda, $250 on Volvo, Toyota, VW/Audi and Mopar, run against your own J2534 device over a bridged connection with a video call alongside.
The pass-through standard the whole arrangement depends on is SAE J2534, which exists precisely so that independent shops can reprogram modules with manufacturer software. The National Automotive Service Task Force maintains the channel through which independents obtain the service information and vehicle-security credentials that go with it.
The symptom-to-operation shortcut
If you only remember one thing from this page, make it this mapping:
- New module fitted, cranks but will not start. Usually OE programming. If the module is used and the original is readable, clone. If the original is gone, IMMO-OFF. Work the full tree in our swapped-ECU guide first, because immobilizer pairing is only one of six causes of that exact symptom.
- Tool cannot read the module properly. Unlock, or the wrong read method. Not IMMO-OFF.
- Modified file will not write or will not boot. Checksum repair.
- Tool is asking for a security code. PIN recovery. Not IMMO-OFF.
- Internal-performance fault code on the original module. Possibly nothing software can fix. Work the P0606 decision tree before spending money on a file or a donor.
A specialist who takes in other people's failed jobs described the pattern this way:
“The job that lands on my bench is almost never the job the customer ordered. They ordered the thing they read about at two in the morning. The car needed something adjacent to it, and now there are two problems: the original one, and a module somebody modified for no reason.” — Independent ECU repair specialist
What none of these operations are
We do not provide emissions defeat, delete files, or services intended to bypass emissions laws. Our services exist for tuning preparation, diagnostics, repair, motorsport, and off-road use where legally permitted. Customer is responsible for confirming legal use in their location and application.
None of the seven alters fuelling, ignition timing, boost or any emissions monitor, and none affects OBD-II readiness. Restoring a vehicle to running condition after a module failure is ordinary repair work. Section 203(a)(3) of the federal Clean Air Act addresses tampering with emissions controls and the sale of defeat devices, which is a category we decline outright.
Settling it in under a minute
Every one of these decisions gets easier once the module has actually been read. Upload the dump to the free variant identifier— no card, no account required — and it reports the exact variant plus whether it is Live, Beta, Soon or Manual on our side. Cross-check against the coverage matrix, and if the operation you need is not one we run, post it on the specialist network where someone who does run it can bid.
The five minutes that costs is the cheapest insurance available against ordering a correctly performed operation on the wrong problem.