VVDI Key Tool Max Pro Firmware Update Stuck Solution

 Problem:

Brand new xhorse vvdi key tool max pro just going through the set up. Been stuck on this screen for 20 mins. Any suggestions?

Solution:

Network issue.

Get a faster internet connection or use WiFi hotspot.

Or turn it off, and downloaded again. It works out just fine.

User feedback:

Just had to turn it off and try again. It worked.

VVDI MLB Tool KYDZ Key Not Found or Locked?

Problem:

I cannot program the generated file in the new (KYDZ MLB) key. The Xhorse VVDI MLB Tool adapter recognizes the key, but at the time of programming it shows that it is not found or blocked. When I simply check the key, that see it.

Solution:

You can’t generate dealer key on kydz key with vvdi tool. If you want to use vvdi MLB tool only OEM virgin key or vvdi special key. Kydz works only with kydz MLB tool.

Xhorse MLB specialized key is not yet released. So use original key.

www.vvdishop.com

Can I Generate VW MQB48 Transponder via Xhorse XT27B

 Question: Is it possible to generate MQB48 transponder from xt27A or xt27B vvdi super chip to be used in VW cars post-2018 to star the car? Pic is from Xhorse VVDI Key Tool Max Pro.

Solution:

Xt27b is on available in the b5 remote version. You won’t find the transponders alone.

At the moment xt27b are inplemented on board XHORSE XEB510EN B5 Super Remote with XT27B Super Chip. Or buy XHORSE XT1M Chip they are MQB Chips.

They have XT27B chip inside.

VVDI Key Tool Plus 2021 VAG RH850 Calculate Failed 10102

 Problem:

I have problem with KM repair on VW Transporter 2021 rh850 cluster. I read processor 3 times but every time i get error on picture… calculate failed error code 10102. I work with xhorse vvdi key tool plus. rh850 is under that menu.

Solution:

This is mqb49 5c type it’s not supported.

Mileage correction is not supported for MQB49/5C.

VVDI Key Tool Plus VAG IMMO4 Service Mode All Keys Lost Guide

 If you encounter issues while using Xhorse VVDI2 or VVDI Key Tool Plus in service mode AKL, there’s no need to worry! Here we’ll guide you through the operating methods and essential precautions to help you navigate the process smoothly.

The following login modules are supported for 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 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 original EEPROM dump, activate the car’s OBD, 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 immo data, save file to generate a dealer key. Add the dealer key and reset the dashboard(for smart keys, learning is required).

Step8. If ABS lost coding, restore it.

Step1 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 step1 to step4, ensure you select the correct module and proceed with reading as normal. Typically, this should not present any issues, but make sure to 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 step5, 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 step5, you select the TFT color display(-2012), you will encounter a failure prompt in step6. In this case, re-diagnose the dashboard to determine the correct type, select the corresponding type, enter more function and write EEPROM to resolve the issue.

Note2.

After writing the original EERPOM 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 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 EERPOM 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.

https://www.vvdishop.com/service/vvdi-key-tool-plus-vw-immo4-akl-service-mode-guide.html