Please read and understand all instructions before using the tools.
Everything below is the result of real workshop experience. Reading it carefully will save you time, money and dead ECUs.
IMPORTANT !!!Most failed jobs are answered by these questions. Please check them before starting immo off or contacting support:
When OtoCheck performs immo off, it uses the ECU's ORIGINAL MCU ID serial number and also its ORIGINAL password. If such an operation (clone, wrong immo off, file editing) was already done on this ECU before, immo off will not work.
On new-type ECUs, immo off is ONLY for ECU REPLACEMENT — not for lost key, all-keys-lost, etc.
If the vehicle does not start, or the windows / comfort functions do not work after immo off, then the KEY and the DASH (or BCM) are not matched. The key must be coded / synchronised to the BCM or dashboard — otherwise the windows will not work.
KESS3 and TRASDATA have many bugs (PCR 2.1 different format, bad MCU ID and some others).
FLEX bug in Simos 6, 8, 10, 11, 12, 16, 18.xx checksum.
ALL other flashers found bad MCU ID — you can check your MCU ID in our MCU ID detector: www.otocheck.com/online/mcuid.php
Autotuner reading split files + checksum problems.
FIRST BE SURE you have an IMMO problem or any external problem like fuel pump, injectors or RPM sensor. You can check live data (RPM sensor and others) in diag tools.
Please listen to the car's error history and understand the problem. If the car stopped during the road it is not an immo problem. Immo never cuts a working engine — immo is only for starting the car.
You can compare the files you read and write to understand how your flasher reads them and use them with other devices. But the general rule is: write with whatever flasher you read with, and always do Checksum.
Because this is immo off. If you don't want abnormal status, please repair the immo system.
There may be more than one reason why the "SAFE" message appears on the screen after the immo off process in VAG group vehicles. But usually the main reason comes from a communication failure between the BCM or DASH and the KEY.
The reason for the error messages on the screen is 99% not caused by the ECU. If you do not want such messages, you will need to add a key to the BCM or DASH, or repair the BCM/DASH-to-key communication.
This message may also appear in some cases with an incompatible engine ECU type. It could also happen if only flash immo-off is done on old-type VAG ECUs — in these ECUs you may prefer to perform immo-off in EEPROM. The same applies to PSA and other brands.
Some immo off operations (especially new generation ECUs) need the MCU ID to be performed. You cannot change the MCU ID — it is OTP (One Time Programmable). You can see the MCUID on the main screen or in the file name while reading the ECU with the flasher.
It can look like 400XXX ... 0000, usually 16 or 32 hexadecimal characters. This information can also be encrypted in the files. Some devices show the MCUID incorrectly — in this case the immo off file does not work in the vehicle and it closes the ECU communication.
4B46915100001820 is not a valid MCUID! Some tools label this as a CHIP/CPU ID, but you need the MCUID, which is unique and in MD1/MG1 units begins with 40xx, 43xx etc. The MCU ID is usually 16 or 32 characters long. It contains only hexadecimal characters — IDs containing any other characters are definitely corrupt.
Examples
The immo systems in new vehicles are not as old-fashioned as before. In classic old vehicles, even with a key fault, you could start by disabling the immo — but new systems are not like this. For the vehicle to work, the key must be synchronously matched with the BCM or dashboard.
In addition, the steering column lock (ESL / SCL) must also fully work or be deactivated with an emulator, or cancelled from the BCM unit. Remember: if the vehicle does not CRANK (starter motor not turning), the immo-disabled ECU will not be activated and the vehicle will not start.
Every flasher uses different read/write methods. For example KESS3 has many bugs after the last update (PCR 2.1, MD1CS003 etc). Autotuner does not make checksum and does not properly perform the procedure to flash back the whole ECU backup.
KT200 may read a bad MCUID. OBD read files / partial virtual files do not include immo blocks. We prefer Flex / PCMFlash flashers for the cleanest dump files, and good well-known programmers for external EEPROM reading when needed (older ECUs).
Valeo 56.xx are very sensitive ECUs. First thing: original and used parts MUST have the same numbers AND same CODING — please compare both ECU label photos and codings. Which flasher was used for reading and writing? Every flasher reads and writes differently. We prefer Autotuner Boot mode or Flex (unlocked mode).
Are you sure the MCU ID is valid? Has anyone touched the files before? Did you try cloning before? If someone tried to clone before, the ECU can be killed and give "INTERNAL ERROR". Please see "Why does IMMO OFF not work?".
MD1CS006 and MD1CS016: Virgin available only for original ECUs, not for used ECUs (because of the SHE module).
Renault / Nissan BCM: If you delete the keys in the BCM key codes, the vehicle will not start — immo off will not help. This is a COMMON PROBLEM in Renault/Nissan; you need to bypass the starter relay and modify wiring to start.
As a general rule…
Read/write as 16-bit if: pin 6 (ORG) is connected to pin 8 (VCC), or pin 6 (ORG) is left unconnected.
Read/write as 8-bit if: pin 6 (ORG) is connected to pin 5 (GND).
Best wishes,
OTOCHECK Team