Vehicle Module Update Procedure When Asbuilt Retrieval Fails

1. This vehicle module update procedure is only applicable when Asbuilt data retrieval has failed and the current vehicle module needs to be updated.
2. If Asbuilt data is retrieved successfully, clicking Request will run the original default update procedure instead of the alternative procedure described here.

Function path: Home -> Functions -> ECU Flash

1. If you need to perform the operation for the GWM module, select: Only Supports GWM Falsh
2. If you need to perform the operation for modules other than GWM, select: All Modules Flash
3. Dedicated module update procedures are not supported here, such as: IMC, ICCM, ICCMB, ISC, EVA2 type TCU, and other previously declared modules.

ECU Flash function entry. Select the GWM flash function or the all-module flash function as required.

1. After clicking to execute, a new operation screen will appear.
2. According to your requirement, select the module you need to query from the drop-down list in the ECU Address field.
3. After selecting the module, click the Request button.
4. The message log area on the main screen will start displaying the vehicle module reading process and query results.

Select the module in the ECU Address field and click Request. The system will read the vehicle module and query available results.

1. Once results are found, they will be loaded into the Assembly list.
2. You can select the version you want to execute from the drop-down list.
3. If you need all available update versions, including previous old versions, modify the last digit of the queried IVS code to A, then click Request again.
4. The system will query all available versions based on this IVS code, up to the latest version, and load them into the list for selection.

Query results are loaded into the Assembly list. Select the version to be executed from the drop-down list.

When Asbuilt retrieval fails, the following two functions will be affected:

1. Anti-theft integrity configuration
2. Replacement of a brand-new module

1. If the original module can still communicate, first use the procedure above to obtain and record the corresponding Assembly code of the original module. After installing the brand-new module, run this function again, manually select the original module address, enter the previously recorded Assembly code, and click OK to execute. Do not click Request. This will write vehicle-applicable data into the new module.
2. If the original vehicle module no longer exists or cannot communicate, send an email to support to query the available module Assembly code. The email must include the vehicle VIN, required module, and repair content, so that support can reply with a complete solution in one response.

The following procedure applies to anti-theft integrity configuration involving replacement of BCM / GWM / KVM.

1. First back up the original vehicle CCF. This can be done through Home -> Functions -> CCF Modify -> CCF Parameter Changes -> Backup, or by clicking Read CCF on the CCF Flash page. After completion, select the current vehicle type parameter in Save CCF type, then click Save CCF in the lower-right corner to save the data.
2. Use the Asbuilt-failure query procedure above to read and record the Assembly codes of the current vehicle. The modules that must be recorded are: BCM, GWM, and KVM.
3. After installing the brand-new BCM and KVM, enter the recorded Assembly codes according to this procedure and update BCM, GWM, and KVM.
4. Load the backed-up local CCF file through the CCF Parameter Changes or CCF Flash page, then perform CCF restore or CCF write to write the CCF data into the brand-new BCM module.
5. Optional: If the installed BCM is a used unit and contains another vehicle VIN that does not match the current vehicle, before performing step 3 you may use Functions -> Module Calibrate -> BCM Rest to restore BCM EEPROM and clear the VIN record. If this function fails, it means the BCM software version may be the latest version and JLR has disabled this function. You may try downgrading the BCM version first and then performing this function again. For BCMs from 2026 onward, this function has already been disabled in the initial version and cannot be used.
6. Optional: If you also replaced the smart key, check whether the new smart key configuration is compatible with the vehicle. If UWB / STA is enabled in the vehicle CCF, you need to prepare a brand-new high-specification D-type smart key. Otherwise, disable the UWB function in the CCF before continuing. The smart key mentioned here refers to the new-style key, not the 2010-2017 smart key.
7. Execute Home -> Functions -> Anti-theft Matching -> Immobilization to synchronize the vehicle anti-theft identifiers.
8. Execute Home -> Functions -> Anti-theft Matching -> Keys Matching, and select brand-new keys inside the function for configuration.

The above instructions describe the vehicle module update solution when Asbuilt retrieval fails, as well as the recommended handling procedure for complete anti-theft configuration. Select the proper workflow according to the actual repair content, and confirm stable vehicle power supply, normal module communication, and complete recorded information before flashing or configuration.