Program Used JLR Modules – KVM, BCM, ECU
The Short Answer
Yes — you can program used JLR modules and fit them successfully, but not by simply plugging them in. JLR modules are locked to the donor vehicle's VIN, immobiliser data and configuration. To make a used module work you must virginise it (reset it to a factory-new state) or clone it (copy the original module's data across), then program it to the car. Dealer software will not do this for you; you need an engineering tool such as JET Master or a UDS-level engineering application.
Done properly, used-module programming saves customers hundreds of pounds per repair and opens a profitable line of work most workshops turn away. This guide covers the principles, the module-by-module reality, and the safe workflow.
Why Used Modules Do Not Just Work
Every significant JLR module stores at least three things that tie it to its original vehicle: VIN, immobiliser data and configuration — until all three are dealt with, the donor module will refuse to work in your car:
- VIN and as-built configuration. The module's Car Configuration File (CCF) segment or internal data describes the donor car — wrong options, wrong market, wrong calibration.
- Immobiliser pairing. Security modules (KVM, BCM, engine ECU, instrument cluster on some platforms) share rolling immobiliser security data. An unpaired module will immobilise the car or throw permanent faults.
- Component protection / secure gateway locks. On DoIP-era vehicles, many modules refuse to accept new software or configuration without an authenticated online session.
A dealer's answer is always "fit a new module" — at new-module prices. The engineering answer is to reset the used module correctly.
Virginise vs Clone: Two Different Jobs
Virginising wipes the module's learned data back to its delivery state: VIN cleared, immobiliser data blanked, odometer/sync data reset. After virginising, the module behaves like a new part and is programmed to the car in the normal way (SDD or Pathfinder/TOPIx "new module" routine). Virgin files are module- and part-number-specific — a file for an FK72-19H440 KVM is not interchangeable with a DPLA or JPLA variant.
Cloning copies the complete data image from the old module to the replacement. The car never knows anything changed — no re-programming, no immobiliser relearn, no online session. Cloning is ideal when the original module is readable (water damage permitting) and you want a plug-and-play result.
| Situation | Correct approach |
|---|---|
| Original module readable, customer wants minimal downtime | Clone old → donor |
| Original module dead/unreadable, donor available | Virginise donor, then program to car |
| KVM/BCM replaced, keys must keep working | Virginise + full immobiliser relearn, or clone |
| Donor module has different part number suffix | Check compatibility first; often needs virginise + correct calibration flash |
Module-by-Module Reality Check
Not all modules are equally stubborn: some accept a straightforward virginise, others guard immobiliser data much more aggressively. Check the module you are holding against this reality list.
KVM (Key Vehicle Module) / RFA
The KVM is the immobiliser heart: it holds key data, and on keyless vehicles pairs with the RFA (Radio Frequency Antenna/Receiver module on some platforms). Part-number families you will meet constantly include FK72-19H440, DPLA-19H440 and JPLA-19H440, in 2-plug (pre-DoIP) and 3-plug (DoIP-era) variants. A used KVM must be virginised with the matching file set and then programmed with an online session — or cloned from the original. On all-keys-lost jobs the KVM is the module that matters; see our remote key programming guide.
BCM (Body Control Module)
BCMs store VIN, central locking/alarm pairing and large chunks of vehicle configuration. A used BCM fitted straight in typically gives you a no-start or a Christmas-tree dashboard. Virginise, flash the correct calibration for the vehicle's VIN, then run the CCF/as-built write. Battery-disconnect damage on Jaguar XF-era BCMs is a classic candidate for this workflow.
Engine ECU (ECM/PCM)
Used engine ECUs carry immobiliser pairing with the original car's KVM/BCM. Clone where possible; otherwise virginise and perform the full immobiliser synchronisation (which requires security access — online session or engineering tool). Also verify the calibration matches engine, gearbox, emissions market and injector coding.
TCU (Telematics Control Unit)
The TCU is tied to the donor's InControl account and SIM/eSIM profile. Used TCUs need account de-registration and reprovisioning, plus the backup-battery check that most people forget — a dead TCU backup battery triggers "SOS System Inactive" warnings even in a healthy replacement unit.
Instrument clusters and others
Clusters store odometer values and immobiliser data on many platforms; treat odometer correction lawfully and document everything. Suspension, steering and parking-brake modules are usually straightforward calibration flashes once virginised.
The Safe Workshop Workflow
A repeatable process is what turns used-module work from gambling into margin: identify, back up, reset or clone, then program. Follow this order on every job.
- Identify exactly. Read the donor and vehicle part numbers. Confirm hardware compatibility (plug count, platform, market) before spending a minute on software.
- Read the original module if alive. Save its full flash/EEPROM data. This is your fallback and your clone source.
- Virginise or clone the donor on the bench where possible — bench flashing with a stable PSU removes vehicle-side risks entirely.
- Fit and program. Run the new-module routine in SDD (pre-2017) or Pathfinder with a TOPIx Cloud session (DoIP era), then write the correct CCF/as-built data by VIN.
- Synchronise security. Immobiliser relearn, key pairing, steering-lock pairing where fitted.
- Verify. Full fault-code sweep of every module, not just the one you touched. Function-test everything the module controls.
- Document. Record donor part number, work performed and data sources. Your future self — and your customer — will thank you.
What Happens If You Get It Wrong
A half-virginised KVM can immobilise the vehicle with no keys recognised; an interrupted BCM flash can leave the car dead on the ramp. Most bricked-module cases we recover remotely trace back to used-module work attempted without bench verification or without stable voltage. Read our programming mistakes guide before your first job, and know that bricked-module recovery exists if the worst happens.
The Economics: When Used Makes Sense
A new BCM or KVM from a dealer can cost four figures before programming labour; the same module from a reputable breaker is often a tenth of that. For vehicles past their prime — a 2012 Range Rover with a water-damaged BCM, an XF with a failed KVM — used-module repair is frequently the difference between an economical fix and an insurance write-off. Customers understand this instantly when you present both options on the estimate.
When to say no:
- Physical or water damage to the donor. Corroded boards and flood history are not software problems. Inspect before you buy.
- Unknown provenance. Modules of dubious origin create legal and security exposure. Buy from documented breakers with part-number records.
- Wrong part family. No amount of programming makes a 2-plug pre-DoIP KVM behave like a 3-plug DoIP unit.
When to say yes enthusiastically: clean donors with matching part numbers, on vehicles where new-part pricing has made the dealer route uneconomic. That description covers a large and growing slice of the JLR parc — which is why workshops that program used JLR modules see one of the fastest paybacks in this trade.
Frequently Asked Questions
Can I program a used JLR module without a TOPIx Cloud subscription? In many cases, yes. Virginising and cloning are done with engineering tools (JET Master or UDS-level applications) on the bench, independent of TOPIx. Where you will still want online access is the final "new module" programming and immobiliser synchronisation on DoIP-era vehicles — a short-duration TOPIx pass or a remote programming session covers that.
What is a KVM virgin file? A data image that resets a specific KVM part number to its factory-new state, clearing VIN and key data so the module can be programmed to a different vehicle. Files are part-number-specific — FK72, DPLA and JPLA families each need their matching file, and 2-plug vs 3-plug hardware matters.
Is cloning better than virginising? When the original module is readable, cloning is faster and safer — the car accepts the donor as if nothing changed. Virginising is the route when the original is dead, when you cannot read it, or when you deliberately want a clean, correctly-configured module.
Will a used module from a different model year work? Sometimes. Hardware part numbers are the truth, not model years. Match the part number and plug configuration, then flash the correct calibration for your vehicle's VIN. When part numbers differ, check compatibility documentation before buying the donor.
Do I need to tell the customer it is a used part? Yes — always. Used-module repairs are legitimate, cost-effective and environmentally sound, but they must be transparent on the invoice, and any odometer-related work must comply with your local regulations.
How long does a used-module job take end to end? A straightforward clone with a readable original: one to two hours including verification. A virginise-plus-program job with an online session: typically two to three hours. Bench-first preparation, correct files staged in advance, and a booked online session window are what separate a profitable two-hour job from an all-day saga.
Can every JLR module be virginised or cloned? The mainstream modules — KVM/RFA, BCM, engine ECUs, TCU, clusters and most chassis controllers — are well covered by current engineering tooling. Edge cases exist: a few latest-generation security modules have narrower support, and physically damaged boards are a hardware repair question, not a software one. If you are unsure about a specific part number, check the compatibility documentation at kb.sx-tool.com before buying the donor — a two-minute check beats a shelf of unsuitable modules.
Equip Your Workshop for Used-Module Work
JET Master handles virginising, cloning, VIN overwrite and CCF engineering across the JLR range, and pairs with the SX-Tool interface for the in-car programming steps. Explore bundles at sx-tool.com/en/shop and step-by-step procedures at kb.sx-tool.com.