Cranks But Won't Start: How to Tell If It's the Immobilizer

A car that cranks strongly, fires for about a second, and dies is one of the most misdiagnosed faults in the trade. It gets blamed on fuel pumps, crank sensors, and ignition coils — all of which are expensive, and none of which are usually the problem.

That specific pattern, especially with a blinking security light, is close to a textbook immobilizer refusal. The engine is mechanically fine. It is being told it is not allowed to run.

The signature to look for

Immobilizer faults have a distinctive fingerprint. Check these against what your car is doing:

• It cranks normally. Strong, steady cranking rules out a flat battery and a failing starter.
• It fires briefly, then dies. Usually one to two seconds. The engine proves it has compression, fuel, and spark — then loses one deliberately.
• There is a security or key-shaped light on the dash. Often flashing rather than steady. This is the single most useful clue.
• It is consistent. It fails the same way every time, rather than intermittently.
• It began suddenly. No gradual rough running beforehand. Immobilizer faults do not creep up on you the way fuel delivery problems do.

The five things that actually cause it

1. A failed transponder in the key

The chip in your key head can fail, usually after physical shock — a hard drop, a trip through the washing machine. The fastest test costs nothing: try your spare key. If the spare starts the car, your primary key's chip has died and the fix is a new key.

2. A failed antenna coil

A ring-shaped antenna around the ignition cylinder energises the chip and reads its response. When that coil fails the key is fine but the car cannot hear it. This is a comparatively cheap repair, which is why it is worth checking before anyone talks about modules.

3. Lost synchronisation after a battery event

This one catches people out. A deep discharge, a sloppy jump-start, or a battery replacement can drop the sync between the immobilizer and the engine module, or corrupt stored data. If your no-start began immediately after any battery work, say so when you call — it points straight at the likely cause and saves diagnostic time.

4. Corrupted security data

Module memory can degrade or corrupt. This is often repairable at chip level — reading, correcting, and rewriting the data — which avoids replacing the module entirely. Dealerships typically resolve this by fitting a new module because that is the sanctioned repair, and it is substantially more expensive.

5. Aftermarket alarm or remote start interference

Badly installed aftermarket systems interpose themselves in the starting circuit and fail in exactly this way. If your car has an aftermarket alarm or remote start, mention it — it moves right up the suspect list.

What to try before you call anyone

1. Try your spare key. Free, takes ten seconds, and resolves the question of key-versus-car immediately.
2. Take other keys and fobs off the ring. Two transponders near the reader can interfere with each other. Isolate the key you are using.
3. Check the battery terminals. Corroded or loose terminals cause voltage drops that upset security modules. Clean and tight is the standard.
4. Wait ten minutes. Some systems enter a timed lockout after repeated failed attempts. If it starts after a wait, that was a lockout — but find out why it triggered.
5. Note the security light behavior. Steady, flashing, or off? Tell whoever you call. It genuinely narrows the diagnosis.

Why a general mechanic often can't fix this

A good mechanic has a good scan tool, and a good scan tool reads engine codes. Immobilizer faults frequently log nothing on the powertrain side — the fault lives in the body or security module, which many general-purpose tools do not address.

That is how a healthy car ends up with a new fuel pump and the same symptom. If your shop has replaced parts and the car still stalls after two seconds with a security light on, stop spending money on fuel and ignition components and get the security system read.