If you have issues while using Xhorse VVDI2 or Key Tool Plus in service mode, All Keys Lost, there’s no more to worry about! This guide will guide you through the operating methods and essential precautions to help you navigate the process smoothly.
The following login modules are supported for the service model AKL.
CDCXX+24C32, NEC24C64(2013-)
A3/TT/R8(CDC32XX), AUDI A1, AUDI Q3
NEC24C32
NEC24C64
NEC24C64 USE TFT COLOR DISPLAY(-2012)
NEC24C64 USE TFT COLOR DISPLAY(2013-)
Without the car key, these login modules cannot obtain immo data from the dashboard. The specific operating methods are as follows:
Step1. Backup ABS coding
More functions >> ABS Coding >> Backup
Step2. Remove the chip, read the data
Remove the 24C32 or 24C64 chip from the dashboard, read the EEPROM data with the VVDI PROG programmer, and save the dump file.
Step3. Generate service EEPROM
Service Mode >> BDM Method: Prepare service mode EEPROM >> Generate service EEPROM
Step4. Write service EEPROM dump to the chip
Write service EEPROM dump to the dashboard’s 24C32 or 24C64 EEPROM chip.
Step5. Restore the dashboard, select the login module
Restore the dashboard to the car and select the correct login module.
Step6. Load original EEPROM dump, activate OBD, write EEPROM
Load the original EEPROM dump, activate the car’s OBD, and write it back to the car via OBD.
More functions >> Write EEPROM
Step7. Read and save immo data, prepare a dealer key, add the key, reset the dashboard
Read the immo data and save the file to generate a dealer key. Add the dealer key and reset the dashboard(learning is required for smart keys).
Step8. If ABS lost coding, restore it.
Step 1 reminds you that ABS backup is necessary. If coding is lost, enter more functions to restore ABS.
More functions >> ABS coding >> Restore
IMPORTANT NOTES
Note1.
During step 1 – step 4, ensure you select the correct module and proceed with reading as normal. Typically, this should not present any issues, but save the original data first. Never write service mode data without first backing up the original data.
To differentiate between files, it’s advisable to use distinct file names for the service mode file and the original data. After writing the service mode data, compare it with the generated service mode file to ensure it can be written correctly.
In step 5, confirm that you select the correct login module. It’s recommended to take a photo of the automatic diagnostic type when initially connecting the devices for automatic diagnosis.
For example, if the device automatically identifies as 24C64(2013-), but in step 5, you select the TFT color display(-2012), you will encounter a failure prompt in step 6. In this case, re-diagnose the dashboard to determine the correct type, select the corresponding type, enter more functions, and write EEPROM to resolve the issue.
Note2.
After writing the original EEPROM data, the device will prompt you to restore the dashboard(as if typically requires a reset after writing the original EE). However, since this is for service mode AKL, the dashboard can only be restored after reading the immo data.
Therefore, do not tap on reset at this point, or it will indicate that the car key is not detected during immo data reading.
This is a common issue, so you must be cautious. The restoration can only be done after reading the immo data. If this step is accidentally performed incorrectly, the solution is to repeat the process: generate the service mode file, write it again, and then perform the OBD write back to the EEPROM operation.
Note3.
When writing original EEPROM data, follow the prompts.
For mechanical keys, insert the key to turn on the dashboard and write the original EEPROM data via OBD.
For smart keys, short-circuit OBD pin1 and pin16, then turn on the dashboard and write the original EEPROM data via OBD.
Additionally, the Audi Q3 has specific requirements. In this case, you need to short-circuit the ELV, then turn on the dashboard and write the original EEPROM data via OBD. Otherwise, an error message stating “car key required” will be displayed, preventing writing via OBD.
