A replacement engine module that cranks the engine but will not let it fire almost always means one of six things — and only two of them are fixed by a file. As of July 2026 the correct fix ranges from free (a coding step you already have the tool for) to $250 (a mail-in clone), and the expensive mistake is buying the wrong one first.
This is a decision tree, ordered by how cheap each cause is to rule out. Work it top to bottom. Most jobs resolve in the first three steps, and the ones that do not are usually not module problems at all.
Before anything: confirm the symptom precisely
“Won't start” describes at least four different faults, and the distinction narrows the search enormously.
- No crank at all.Usually not the engine module. Start at battery, starter, ignition switch, neutral safety, and the body module's crank-enable path.
- Cranks, no fire, no fuel pump prime.Strongly suggests immobilizer or authorisation — the module is being told not to run.
- Cranks, fires briefly, dies within a second or two. Classic immobilizer signature on several platforms: the engine starts and authorisation fails a moment later.
- Cranks, no fire, and no communication with the module at all. Now suspect power, ground, or a dead module before anything software.
Note which one you have. The tree below assumes the engine cranks.
Cause 1: power, grounds and the harness
Cheapest to rule out, most frequently skipped. A replacement module with a marginal ground, a corroded connector pin, or a harness damaged during the original incident produces symptoms that look exactly like a software fault — including intermittent communication that convinces you the module is “half working”.
Check module power at the connector under crank, not at rest. Voltage that sags heavily during crank produces a module that boots and then loses its mind at precisely the wrong moment. If you take one habit from this entire guide, make it this one: prove the electrical side before you spend anything on software.
Cause 2: immobilizer pairing — the donor module problem
This is the single most common reason a swapped module will not start a car. The replacement carries the donor vehicle's immobilizer pairing, so when the key presents itself the module does not recognise the response. Nothing is mechanically wrong; the module is refusing on purpose.
There are two legitimate fixes, and which one is right depends entirely on whether your original module can still be read:
- Clone— if the original is readable but the hardware is dead. The VIN, immobilizer data and configuration move onto the donor and the vehicle keeps its own identity. $250 mail-in, both modules required.
- IMMO-OFF— if there is no original to clone from. The immobilizer-validation routine is disabled so the engine runs. $100 instant on supported variants, returned in seconds against your own read.
Our IMMO-OFF coverage is per-variant and published honestly: eight variants sit at Live as of July 2026 — Saab Trionic 5 and 7, Bosch ME7 on the 95040 / 95080 EEPROM, Bosch ME7.5.20, and BMW MS43 in the ca430037, ca430056, ca430066 and ca430069 revisions — with three more at Beta and the rest Soon or Manual. What those words mean is set out in the coverage-status guide, and the full table is on the coverage matrix.
Two platform-specific notes. On BMW M52/M54 cars the operation is an EWS-delete and the software revision decides everything — see the M52 / M54 identification guide before ordering. On VAG 1.8T cars the immobilizer data lives in a small external EEPROM, not in the main flash, which means an OBD flash read is the wrong file entirely; the ME7 identification guide covers it.
Cause 3: VIN lock and module-to-vehicle pairing
Distinct from the immobilizer, and often mistaken for it. Many modern modules refuse to operate until they have been programmed with the vehicle's VIN and configuration by the manufacturer's own software. A used module from another car arrives holding somebody else's configuration; a new module arrives blank.
There is no file patch for this and there should not be — the correct operation is OE programming and adaptation. We run those remotely into your own J2534 device across eight platforms: GM ($100), Ford/Lincoln, Nissan/Infiniti and Mazda ($150), and Volvo, Toyota/Lexus, VW/Audi and Chrysler/Dodge/Jeep/Ram ($250). Sessions run 30–60 minutes, 9 AM to 9 PM Central, seven days — the car never leaves your bay. The workflow is in our remote programming guide.
Cause 4: the module is protected and was never properly read
A subtler failure and a maddening one, because everything appears to have gone right. Some families will not hand over their contents to a generic pass-thru at all; the Chrysler GPEC2 and GPEC2A families are the well-known case. If a partial or protected image was written back, the module can end up in a state that neither runs nor communicates properly.
The tell is usually in the read stage: a file whose size does not match the family's expected image, or two consecutive reads that are not byte-identical. Our read-methods guide covers the read-twice-and-diff discipline that catches this before anything is written. The fix on GPEC families is the unlock operation — $150 instant against your read or $250 mail-in with no tool required, detailed in the GPEC unlock guide.
Cause 5: stale checksums after a modified write
If anyone modified the file — a patch, a calibration change, even a single corrected byte — and the checksums were not recovered, the module will refuse to boot the application firmware. From the driver's seat that is indistinguishable from every other no-start.
This is a solved problem on most families and it is cheap. Our checksum coverage runs Live across ten of the twenty catalog entries and Beta on seven more, using family-appropriate algorithms rather than one generic routine — Saab Trionic in particular uses its own scheme that generic tools do not cover. The checksum repair guide explains what the operation involves; for Saab specifically, the Trionic guide covers why generic tooling struggles there.
Cause 6: the module itself has failed
Last on the list because it is the most expensive to conclude, but it does happen — particularly on a module that has been through a collision, a flood, or a jump-start reversal. Cracked solder under the driver chips, a failed voltage regulator, corroded pins. No file fixes hardware.
If the module reports an internal-performance fault, work our P0606 decision tree before buying anything. It separates the genuinely-failed-hardware cases from the ones that look like hardware and are not.
The decision tree in one table
| Cause | Tell | Fix | Typical cost |
|---|---|---|---|
| Power / ground / harness | Voltage sags under crank; intermittent comms | Repair the electrical fault | Shop time |
| Immobilizer pairing | Cranks, no fire, or fires and dies in ~1 s | Clone (original readable) or IMMO-OFF | $100–$250 |
| VIN lock / configuration | Module talks but refuses to operate | OE programming + adaptation | $100–$250 |
| Protected / partial read written back | Read size wrong; two reads differ | Unlock, then re-read and rewrite | $150–$250 |
| Stale checksums | File was modified; module won't boot | Checksum recovery | Included with our files |
| Failed module hardware | Internal-performance fault; no comms at all | Replace or repair, then program | Parts + session |
The two mistakes that cost the most
First: binning the original module before reading it. A module that will not run the car may still hand over a complete image, and if it does, a clone preserves the vehicle's own identity for $250. Once the original is gone, you are into OE programming and a parts hunt. Our salvage rebuild playbook sequences this properly.
Second: buying an IMMO-OFF because it is the cheapest line on the menu. If the original is readable, cloning is the better engineering answer — it keeps the immobilizer chain intact rather than removing a check. A technician who does this work daily put it bluntly:
“Everyone wants the hundred-dollar answer. Half the time the two-hundred-fifty-dollar answer is the one that leaves them with a car that still works properly in three years. Read the old module first — that one decision decides the whole job.” — Independent electronics technician
What we will not do
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.
Restoring an immobilizer chain after a module swap is ordinary repair work. Removing an emissions control is not, and Section 203(a)(3) of the federal Clean Air Act prohibits both tampering with those controls and the sale of any defeat device, software included. We also require that ownership can be documented before any immobilizer work — the National Automotive Service Task Force maintains the industry framework for vehicle-security work precisely so that legitimate repair and theft-enabling work stay distinguishable.
On the warranty question that always follows: per the Federal Trade Commission, the Magnuson-Moss Warranty Act means a manufacturer cannot void a warranty merely because an independent did the work — though it may deny a specific claim it can show the work caused.
The short version
Prove the electrical side first. Then determine whether your original module can be read, because that single fact decides between cloning and IMMO-OFF. If the module needs to learn the vehicle rather than skip a check, that is OE programming and there is no file for it. Checksums and read quality account for most of the remaining cases, and genuine hardware failure is last because it is the most expensive conclusion to reach wrongly.
Start free: upload the dump to the identifier and see which variant you have and what its real status is. Then check the posted price, book a remote session, or ask uswhich of the six this actually is — we would rather route you correctly than sell you the wrong operation.