ECU access, unlocking & recovery guides
Protected-controller access and failed-programming recovery need exact identification, suitable files and a supported operation.
Plan the enquiry around the actual job.
Keep original reads, attempted writes and logs separate. Explain which files were real reads or supplied files and what happened at each step. A file called “stock” or “full” does not establish its content or suitability.
OBD, bench, boot and specialist protected-access workflows are application-specific. A tuning protocol does not automatically establish a cloning or recovery route. These guides help scope the intended outcome before an ECU is removed or another programming attempt is made.
View the related service and its assessment process, or use the enquiry finder if you are unsure which route fits.
Read what helps your next step.
Hyundai & Kia SIM2K510: new Flex release and full model list
Hyundai and Kia SIM2K510 tuning: Flex 8.28 OBD support, all 25 listed variants, CAN-FD requirements and vehicle-specific quotes from Northern Calibration.
Read the guideOBD, bench, boot and ECU unlocking: what changes between the methods?
The right access method depends on the controller and the operation. Tuning, cloning and recovery may need different levels of access.
Read the guideBMW and MINI MD1 / MG1: confirm the access route before sending your ECU
Selected protected BMW and MINI controllers now have closed-unit bench routes. The exact ECU and requested operation still decide the job.
Read the guideMercedes MD1CP001 and MG1CP002: planning specialist ECU access
What to include in a protected Mercedes ECU enquiry, and why specialist access, software recovery and cloning have different scopes.
Read the guideECU recovery after a failed remap or interrupted software write
What to preserve after an interrupted ECU write, which details make a recovery enquiry useful, and how the next step is assessed.
Read the guideECU cloning support: why a tuning protocol does not confirm a clone
Tool coverage has to match the operation. A controller may support calibration work while replacement-data transfer has different requirements.
Read the guideECU backups: which files and records should you keep?
A file called “original” may be a calibration read, a virtual file or a wider backup. Preserve its source and operation so recovery can be assessed.
Read the guideBattery support during ECU programming: why the setup matters
Programming needs the correct power conditions for the vehicle and tool procedure. Keep voltage events and logs if a write is interrupted.
Read the guideFlex cloning statuses: what 1-to-1, staff, service and not tested mean
Use cloning-status labels as operation guidance, then check exact controller identity, donor conditions and the required handover before booking.
Read the guideVirtual read or real ECU read: what does the file prove?
Identify how a programming file was obtained before treating it as original data for recovery or cloning. A supplied matching file and a memory read have different scopes.
Read the guideStellantis MD1CS003 and Korhex: what to send for an access enquiry
Selected Stellantis Bosch MD1CS003 access has a published Korhex route. Identify the controller and intended operation before acceptance or dispatch.
Read the guideSimos petrol ECUs: a tuning file is not a replacement plan
Prepare a Simos enquiry with the exact controller, file operation and current vehicle state. Calibration support and replacement-data coverage are separate checks.
Read the guideKorhex and Flex protected ECU recovery: why exact protocol support matters in 2026
Recent protected-controller updates make access stronger on selected ECUs, but recovery still depends on the exact hardware, files and failure sequence.
Read the guideAutotuner OBD, bench and boot planning: choose the method around the job
OBD, bench, boot and post-unlock routes serve different purposes. A useful tuning or recovery enquiry names the controller, goal and risk history.
Read the guideAsk about your vehicle.
Send the registration, postcode and the evidence described in the relevant guide.