Patching is only required for some Advanced protocols! Basic protocols never need patching.
Select your ECU and tool:
Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x14000 with 0xBFBFBFBF. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.0xBFBFBFBF from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to the file you use to flash via OBD.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to the full virtual read.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x14000 with 0xBFBFBFBF. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.0xBFBFBFBF from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.WARNING! PLEASE READ! As there are no bench/boot protocols publicly available at the time of writing, if the ECU gets bricked, then you need a new one or you will have to send it to your flash tool manufacturer for recovery (if they even offer that service).
While the risk is very low that the ECU ends up in a reset loop (a non-essential service is being patched, that is never called by any flash tools or in normal operation), there is always a risk flashing any modification into any ECU for which no recovery method is available. This also includes calibration changes (e.g. wrong monitoring checksum, bad axis modification).
If you manage to brick your ECU, there will be no responsibility or help that will be offered on behalf of VehiCAL. Do this only if you are willing to accept the risk.
Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x0000 with BF BF BF BF B0 B1 B2 B3. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.BF BF BF BF B0 B1 B2 B3 from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x00000 with 0xBFBFBFBF. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.0xBFBFBFBF from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x14000 with 0xBFBFBFBF. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.0xBFBFBFBF from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x0000 with 0xBFBFBFBF. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.0xBFBFBFBF from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.WARNING! PLEASE READ! As there are no bench/boot protocols publicly available at the time of writing, and only private tools support full OBD write, if the ECU gets bricked, then you need a new one or you will have to send it to your flash tool manufacturer for recovery (if they even offer that service).
While the risk is very low that the ECU ends up in a reset loop (a non-essential service is being patched, that is never called by any flash tools or in normal operation), there is always a risk flashing any modification into any ECU for which no recovery method is available. This also includes calibration changes (e.g. wrong monitoring checksum, bad axis modification).
If you manage to brick your ECU, there will be no responsibility or help that will be offered on behalf of VehiCAL. Do this only if you are willing to accept the risk
Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the iflash file, it must contain all the iflash files combined in the backup, if there are more than one.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger file.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger file.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. The logger will notify you of the patch status.0x77F000 to 0x560x7FF000 to 0x56Initialize again. The logger will detect that the patch has been activated.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x00000 with 0xBFBFBFBF. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.0xBFBFBFBF from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button and point the Logger to your .bdc file.0x14000 with 0xBFBFBFBF. This will force bFlash to make a full flash of the ECU, rather than only doing a cal write.0xBFBFBFBF from your file. Otherwise every time you flash, bFlash will make a full flash.Initialize again, the Logger will detect that the ECU is patched.Initialize. If the ECU is not patched and you have a valid license, the Patch file button will become active.Patch file button is active!Patch file button in the Logger, and give the Logger the IROM file. If your tool splits the IROM in two halves, first put them together to get a single file.Initialize again, the Logger will detect that the ECU is patched.