Remapping after a dealer software update

After the ECU has been updated at a dealership, never write an old file back without first having its compatibility checked against the software now installed. This applies to a tuned file just as much as to an original file saved before the update.

The vehicle and its VIN are unchanged, but its software configuration may have changed. A file that worked before the update is therefore not automatically compatible afterwards: a fresh read is essential.

What an ECU actually contains

An ECU holds more than maps. Depending on its architecture, it typically contains:

The bootloader, involved in starting the ECU and in programming operations.
The application software, which runs the engine management strategies.
The calibration data, which sets the parameters of those strategies: targets, limiters, axes, coefficients, thresholds and so on.
The non-volatile data, which may hold vehicle-specific information, adaptations or security data.

These elements must stay consistent with each other. A file obtained with a tuning tool is not necessarily a full backup: what it contains depends on the ECU, the protocol and the read method. AutoTuner, for instance, distinguishes OBD reads from its Bench or Boot backups. [1]

Why an old calibration can become incompatible

Maps are tied to a specific software version. They have memory addresses, dimensions, axes, data types and conversion rules that the program uses to interpret them. These characteristics are part of what A2L files describe. [2]

A software update can change this layout. Data sitting at a given address in the old version does not necessarily do the same job in the new one. Development tools accordingly provide for updating addresses and data types after the software is recompiled. [3]

A simplified example: a calibration was built for software A. The dealership installs software B. If the next write only replaces the calibration with the one built for A, the ECU can end up running program B with data meant for A.

Why reflashing does not necessarily put everything back

Writing a tuning file does not necessarily overwrite every memory area of the ECU. Depending on the protocol, some areas are written and others are left as they are. Writing an old file back therefore does not guarantee that a complete, consistent software set is restored.

Going back to an earlier version may be possible when it is explicitly supported, with a compatible file and the right procedure. Some FRF writing functions for VAG ECUs make exactly this distinction between update, return to original and downgrade. That does not make an improvised reuse of an old map file acceptable. [4]

Why a correct checksum is not enough

Correcting the checksum does not turn an incompatible file into a compatible one.

A valid integrity check confirms a property of the data it checks. On its own, it does not guarantee that the calibration matches the program present, that the areas not rewritten are compatible, or that the file suits the vehicle's current configuration.

File integrity and software compatibility are two different things.

Possible consequences

Depending on the ECU, the checks it runs and the areas written, an outdated file can lead to a refused write, malfunctions or a software lock.

At worst, the vehicle may not start and the ECU may stop communicating over OBD. AutoTuner explicitly warns about these risks when an old file is written after a manufacturer update. [5]

A lock does not happen every time. But the fact that one vehicle had no problem is no guarantee for the next.

What to do before writing again

Identify the ECU again with your tool.
Make a new read using the supported method.
Send us this read and the available identifiers, stating that the vehicle was updated at a dealership.
Wait until the file matching the current version has been prepared or validated.

With a virtual read: identify the ECU again and download the file that matches the current version. A virtual read downloads an original file linked to the software identification; it does not copy what is actually in the ECU. Reusing a file you downloaded earlier does not replace this step. [6]

Without this new information, we cannot check whether an old file is compatible with the ECU as it stands now.

You have already written the wrong file

We offer a restore service to handle exactly this kind of situation.

If you wrote an old file back after an update and the vehicle now has a problem, avoid trying one file after another. Open a restore request with our team so that we can analyse the situation and work out the right recovery solution.

What to include in your restore request

The vehicle concerned and its exact VIN.
The tool used and the write method: OBD, Bench or Boot.
The ECU identifications before and after the update, if available.
The file you wrote and any reads or backups you have.
The tool logs, the error messages and the symptoms observed.
The exact order of events: initial read, dealer update, then write.

The recovery method depends on the ECU, its condition and the data available. A restore request lets us assess whether we can help; it does not guarantee recovery over OBD in every case.

After an update, start again from the ECU's current version: new identification, new read, then a matching file.