ALOA ICPL study materials
ALOA ICPL study resources

The Vehicle That Won't Accept Its Own Key

ALOA ICPL · Put your knowledge to work in context.

All case studies

The Vehicle That Won't Accept Its Own Key

A customer's late-model vehicle with a transponder-based immobilizer will not start. The mechanical key turns the ignition but the engine cranks and dies immediately - the classic immobilizer no-start. The customer has one working key (which now also fails) and one spare that was never programmed. A previous shop replaced the ignition cylinder and, the customer believes, 'reset the computer.' You have a capable diagnostic tool and a key programmer. The vehicle is in a parking garage two levels down with no power outlet nearby. The customer is pressing for you to 'just program a new key and get me going.'

1. Before programming anything, what must you establish about the vehicle's immobilizer state, and why does programming first risk making things worse?

Read the worked answer

You must establish the current immobilizer/key inventory state: how many keys the immobilizer module currently believes are valid, whether the module is in a learned state or has been reset/erased, whether the previously replaced ignition cylinder is matched to the vehicle, and whether the no-start is an immobilizer rejection or a separate fault (the crank-and-die pattern is consistent with immobilizer, but you confirm it with the tool rather than assume).

Programming first is risky because many immobilizer systems have a fixed maximum number of key slots and some procedures erase all existing keys as a step. If the module has already been reset by the previous shop, or if you begin a learn procedure and it is interrupted (dead tool battery, lost communication in a parking garage), you can leave the vehicle with zero valid keys - turning a no-start into a tow to a dealer for a module-level recovery. Establishing state first tells you whether you are adding a key, restoring erased keys, or dealing with a module/cylinder mismatch, and each of those is a different job.

2. The garage has no power and the tool runs on battery. What operational decisions does that force, and how do you sequence the work?

Read the worked answer

Battery-only, no-outlet conditions force you to treat tool power and communication stability as first-class constraints. Decisions: (1) charge and verify the programmer and diagnostic tool before descending - do not start a learn procedure on a marginal battery; (2) confirm the vehicle battery is healthy, because a voltage sag mid-procedure can abort a learn and, on some systems, strand the module; bring a jump pack and use it if needed; (3) plan the procedure so the longest, most interruptible step (key learning) happens once, with everything staged, rather than being restarted repeatedly.

Sequence: diagnose and record immobilizer state first (read-only, low risk); confirm the mechanical/cylinder situation; then, only with stable power on both tool and vehicle, run the learn/program procedure in one pass; immediately verify by starting the vehicle with each key; then document the final key inventory. If at any point power or communication looks unstable, you stop before the destructive step and either stabilize power or move the vehicle - you do not gamble a module on a weak battery.

3. The customer wants 'a new key programmed' and nothing else. How do you scope and price the job honestly?

Read the worked answer

You explain that 'program a new key' is the last step, not the whole job, and that the no-start has to be diagnosed before a key can be trusted to fix it. You scope it as: diagnostic to establish immobilizer state and confirm the fault; then either a key add/restore or a cylinder/module reconciliation depending on what the diagnosis shows; then programming and a start-test with every key; then a written record of the key inventory.

On price, you quote the diagnostic as its own line and the programming as contingent on the diagnosis, rather than quoting a flat 'new key' price you cannot stand behind. You tell the customer plainly that if the previous shop left the module erased or mismatched, the job is larger than a key, and you will tell them the number before doing that work. This protects both of you: the customer is not surprised, and you are not pressured into a partial job that leaves them with a vehicle that still won't start and a bill for a key that didn't fix it.