What module cloning actually is
Every control module on a modern vehicle stores two kinds of data: the program (flash) and the vehicle-specific data (EEPROM) — VIN, immobiliser keys, configuration bytes, learned adaptations and sometimes mileage. A clone copies both onto a donor module with matching hardware, so from the vehicle's point of view nothing has changed except that the hardware now works.
1:1 copy of your data onto a matched donor. No dealer session, adaptations preserved, plug-and-play.
New or virginised module coded to your VIN. Needed when the original memory is unreadable.
Board-level fix: power stages, drivers, corroded tracks, dry joints. Cheapest when the fault is hardware and localised.
Off-road use only. Sometimes the only route on obsolete modules with no donor availability.
Which modules we clone and why they fail
| Module | What it controls | Typical failure | Cloning outcome |
|---|---|---|---|
| ECU / DME / EDC | Engine management | Non-start, injector driver failure, bricked flash | Immobiliser sync and tuning state retained |
| TCU / TCM / Mechatronic | Gearbox control | Limp mode, harsh shifts, no drive | Adaptations and clutch data kept, no relearn wipe |
| BCM / BSI / SAM | Body electronics | Dead after jump-start, water ingress, lights/locks/wipers faults | Config and key data retained |
| KVM / RFA | Keyless entry & start | No key detected, comfort access failure | Key set preserved, no dealer key re-issue |
| CAS / FEM / BDC | BMW access & immobiliser | No crank, no key recognition, coding corruption | ISN aligned to DME, keys retained |
| EIS / EZS & ESL | Mercedes ignition & steering lock | Key won't turn, ESL jam, no start | Cloned pair keeps existing keys working |
| Instrument cluster | Immobiliser data on many platforms | Dead display, immobiliser lockout | Mileage and immobiliser data carried over |
Cause is usually one of four things: voltage abuse (jump-starting, welding, flat-battery cranking), water ingress, a failed dealer or aftermarket flash, or a theft attempt that damaged the security module. All four are cloneable in most cases.
Bench, boot mode and OBD — how the data is reached
| Route | Module state | When it's used | Risk profile |
|---|---|---|---|
| OBD | Fitted, communicating | Coding, adaptation, some flash writes | Low, but limited access to secured areas |
| Boot / bootloader mode | Fitted or on bench, pin pulled | Full flash + EEPROM on many modern MCUs | Medium — correct pinout is essential |
| Bench (connector harness) | Removed, powered on bench | Locked or non-comms modules, cloning | Medium, controlled and repeatable |
| Direct chip (EEPROM/CPU) | Removed, clipped or desoldered | Dead boards, protected data, ESL/ELV units | Highest skill, best recovery odds |
A cloning job, step by step
- 1.Diagnose the network, not just the code
Full topology scan, supply and CAN integrity checks so the failed node is confirmed before anything is removed.
- 2.Remove the module
Module extracted with battery support and correct disassembly; connectors and coding labels photographed.
- 3.Read on bench or in boot mode
EEPROM and flash extracted with a regulated supply and the correct pinout, and a backup archived.
- 4.Match and prepare the donor
Donor verified by hardware and software number, then erased ready for the 1:1 write.
- 5.Write and verify checksums
Data written, checksums and VIN verified, immobiliser and component protection handled as required.
- 6.Bench test, refit, road verify
Comms and start-enable tested on the bench, then refitted and confirmed live with adaptations intact.
Module removal, done without creating new faults
Module removal is where avoidable damage happens: snapped connector locks, disturbed earth points, lost configuration and, on some platforms, a stored fault that then needs clearing with an online session. The sequence matters.
Memory-keeping supply fitted, or a documented full power-down where the platform requires it.
Connector positions, hardware/software labels and loom routing captured before disassembly.
Trim clips released in the designed sequence — cheaper than replacing a cracked scuttle panel.
Boards handled by the edges on a mat; a cheap habit that prevents a very expensive one.
Water path, chafed loom or failed fuse feed identified, or the replacement module fails the same way.
Adaptations, DTC clear-down and a live road check to confirm the whole network is healthy.
If you are not sure which module is at fault, start with diagnostics and topology scanning — it is the cheapest step in the whole process.
Mobile ECU service vs postal cloning
| Mobile ECU visit | Postal cloning | |
|---|---|---|
| Best for | Vehicle immobile, module still fitted, diagnosis needed | Module already out, or you're outside the West Midlands |
| Coverage | Wolverhampton, West Midlands and surrounding counties | UK-wide |
| Turnaround | Same visit in most cases | 24–48 hours from arrival |
| Includes | Diagnosis, removal, clone, refit, road verify | Read, clone, checksum verify, bench test, return |
| You provide | Reg, VIN, postcode, access | Module, part numbers, reg/VIN, fault description |
Costs and turnaround
| Work | Typical time | From |
|---|---|---|
| Module clone, module supplied to us | 1–2 hrs bench | £180 |
| Clone plus donor sourcing | 1–3 days incl. sourcing | Quoted per part number |
| Mobile removal, clone and refit | 2–4 hrs on site | Quoted per vehicle |
| Diagnostics and topology scan | 1 hr | From £60 |
| Stage 1 remap | 1–2 hrs | £200 |
| ESL/ELV repair or clone (Mercedes) | 2–3 hrs | Quoted per VIN |
Cloning is normally well below the cost of a new module plus a dealer coding session, and it avoids the parts-availability lottery on discontinued modules.
Brand-specific notes
DME/DDE ISN alignment to CAS/FEM/BDC; FEM and BDC read on the bench. Cloned units keep existing keys working.
Component protection handled during the clone; MQB and MQB48 data pulled from cluster, ELV or gateway as required.
EIS/EZS and ESL/ELV usually treated as a set; cloning keeps the existing key set rather than issuing new keys.
KVM/RFA and BCM cloning avoids dealer key re-issue and online sessions on JLR platforms.
BSI, BCM and PCM cloning is mostly straightforward, and donor availability is good, which keeps costs low.
Transit, Sprinter, Crafter, Ducato-family BCM and ECU cloning — downtime is the priority, so mobile work is usually best.
The expensive mistakes we're asked to undo
A second-hand ECU with another VIN inside will not run the car and can lock the immobiliser. Clone first, then fit.
Voltage sag during a write bricks modules. Every failed-flash recovery we do starts with this.
A missing node is often wiring, power or ground. Topology scan first — modules are the expensive guess.
Partial reads produce a module that boots but drops out under load. Full flash plus EEPROM or nothing.
Without the original dumps a recoverable job becomes a virgin-and-code job with dealer involvement.
Clone the module, leave the leak, fail again in weeks. Fix the cause in the same visit.
Frequently asked questions
Q.What is module cloning and how is it different from coding a new module?
Cloning writes a bit-for-bit copy of your original module's memory onto a donor with matching hardware, so the car sees the same module it always had. Coding a brand-new module means the dealer writes your VIN and configuration into a virgin unit, usually requiring an online security session and sometimes component protection removal.
Q.Can you clone a dead or water-damaged module?
Often yes. If the memory devices survived, the data can still be read in boot or bench mode even when the module will not communicate over OBD. Full board failures where the EEPROM itself is destroyed are the exception, and in that case a virgin module with correct coding is the fallback.
Q.Does cloning keep mileage, VIN and immobiliser data?
Yes — that is the point. A full EEPROM plus flash clone keeps VIN, immobiliser pairing, mileage where the module stores it, and learned adaptations such as throttle, transmission and body configuration.
Q.Is module cloning legal?
Cloning your own module onto a donor for repair is legitimate repair work. We verify ownership for every job, keep records of VIN and part numbers, and do not perform work that misrepresents a vehicle's mileage or identity.
Q.Do you supply donor modules?
Yes. Donors are sourced by hardware and software number so the clone is genuinely compatible, then cloned and bench-tested against your data before dispatch.
Q.Can ECU work be done mobile, or does the module have to be posted?
Both. Around Wolverhampton and the West Midlands we come to the vehicle, remove the module, read and write it on site and refit. UK-wide, customers post the module in and we return it cloned and bench-tested, usually within 24–48 hours of arrival.
Q.What about VAG component protection or BMW ISN alignment?
Component protection on VAG modules is removed or transferred as part of the clone so no dealer online session is required. On BMW, the ISN in a replacement DME/DDE is aligned to the CAS/FEM/BDC so the immobiliser accepts it.
Q.How do I know which module has failed?
A topology scan and network read tells you which nodes are missing, whether the fault is a module or the wiring/power feeding it, and whether a bus is shorted. Replacing a module that was never the fault is the most common expensive mistake we see.
Got a failed module?
Send the reg or VIN, the module's hardware and software numbers and a description of the fault. We confirm whether it clones, repairs or needs a donor before you spend anything.