VW Golf 6 MK6 Key Programming by Xhorse VVDI2

 VW Golf 6 MK6 has a working key and need to add a new spare key using xhorse vvdi2 key programmer. Check instructions below.

Procedure:

Connect by obd2 on car.
Ignition is on with a working key.

Run VVDI2 software, select VW->Diag
VVDI2 detects instrument type TFT color display NEC 24C64 (-2012)
Read EEPROM/Flash->Read EEPROM

Switch on with the working key before press OK

But it says non-standard login failed
This time we choose manually
Go to Key Learn->4th Immobilizer system VW/Skoda/Seat->Instrument with NEC+24C64
Read EEPROM/Flash->Read EEPROM->Login Method 2

Reading data
Reading data success

Save eeprom data
Then Read Immo Data->Login Method 2
Read Immo data success and save data

Select Make Dealer Key and Login Method 2
Put new key into vvdi2 vag coil

Prepare VW normal dealer key and press NEXT

Make dealer key ok and locked
Then Add key

You should backup eeprom and immo data before learn key.
Select Learn key with security code from immo data, put key into the ignition switch.

Load immo data and input 2 keys to be learned
Select No this car does not have keyless.

Insert the dealer key into car and switch on for at least 2 seconds. The time for change key should less than 5 seconds.
Wait till appear 1-2 on cluster, then ignition on with second key.
Now 2-2, then ok
All keys were successfully learned.
Reset instrument.

Done.

www.vvdishop.com

Xhorse VVDI2 Program VW Passat CCM All Keys Lost

 Here’s the trick to programming VW Passat with Comfort Module (CCM) all keys lost by xhorse vvdi tools (VVDI2 and VVDI Key Tool Plus).

1.OBD method

There is MUCH easier way to do these Passat and CC with CCM.

Simply, open fuse box cover on driver’s side

30A fuse will be hot

Put wire, preferably with switch in between 30A hot fuse and 5A fuse

This will force ignition on

Then read immo data

Make dealer key

Adapt key

Remote will need to be programmed separately.

This trick is good but only works on some ECUs. Some totally, some partially (6 bytes out of 7), some not.

This way can work only on edc16 (only some this ecu got 7 byte) rest ecu only 6 bytes and even if fits PCR2.1 you can’t get any cs by obd. So classic way is still best because the results is 100%.

2.

You can disassemble the CCM, remove the immo data eeprom and program key via dump.

For example, it can be done by xhorse vvdi key tool plus or vvdi2.

Remove glovebox, to access module. Remove and desolder chip read and make dealer key. Refit then learn to car via obd.

Xhorse VVDI2 V7.3.0 Adds Motorcycle Key Programming

 Xhorse VVDI2 key programmer released new software V7.3.0 on Jan. 7th, 2023.

*** 2023-01-07
*** Require firmware V7.3.0
************************************************************************

!!!This version require update firmware V7.3.0!!!

===== VAG V7.3.0 =====
1. Improvement autodetect for VAG immobilizer system
2. Bugfix

===== BMW V7.3.0 =====
1.Support make dealer key for motorcycle (Contact vvdishop.com for license)
1). Support 8A smart key via OBDII (Require XM38 motor remote)
2). Support 4D+ transponder key via OBDII (Require VVDI super chip)
2. Bugfix

===== Porsche V7.3.0 =====
1. Bugfix

===== PSA V7.3.0 =====
1. Bugfix

===== Transponder Programmer V7.3.0 =====
1. Improvement prepare remote function
2. Immobilizer data tool: Euro->Opel->IMMO-1->68HC05 bugfix
3. Bugfix

===== Copy 48 (96 bits) V7.3.0 =====
1. Bugfix

===== J2534 V7.3.0 =====
1. Bugfix

===== Online Upate Tool V7.3.0 =====
1. Bugfix

===== Quick Start V7.3.0 =====
1. Bugfix

How to Fix VVDI2 Cannot Read Kline VW Polo Golf4

 Here comes the DIY solution to xhorse vvdi2 unable to read VW K-line dash problem.

Unable to read k-line polo, golf4 VDO dash but able to read Sharan k-line edc15 ECU but unable to learn keys to the very same car (can’t connect to immobox or similar error).  Took apart but there is no burnings.

It was id44. Separated immobox behind the odo with edc15. Pin from ecu, precode 7935 to VAG id44 and learn thru channel 25.

DIY Solution:

The vvdi2 is working again. Here is the solution

After disassembled the vvdi you MUST be extremely careful with the big yellow backup battery pins!! If you connect them the DALLAS (security chip) will be deleted immediately and you have to send back to china to reprogramming. There is no other way to repair!!! YOU HAVE BEEN WARNED!!!

1: Remove the cable from the vvdi and check the connection with multimeter. This two pins on the first picture must be connected

2: Disassembly the vvdi2 vag and attach the cable to the vvdi and check with multimeter the connection between the obd plug pin #7 and the marked pin on the pic

3: There is a MOSFET relay which is switching the port. Check for burning marks Here is the datasheet

4: On the third picture there is a multiplexer. Because only one kline driver working in the vvdi2 if any other pin using the kline somehow able to switch to pins. This multiplexer doing this. Here is the datasheet Mosfet pin #4 connected to ADC1606 pin #22

5: UART to Kline bus driver. This device is “translate” between the car kline network and the vvdi2 MCU. Here is the datasheet ADC1606 pin #28 connected to KLine driver pin #6

You can’t really test the switching components. The only sure way when you replace them. You can replace the mosfet from any other neighboring one, but the multiplexer isn’t available for me thus i skipped that part. Instead of i replaced the Kline bus driver, after the change my vvdi is able to communicate on kline again.
Hope it helps.

Credit to DK Veteran.

www.vvdishop.com

How to Adapt Used Porsche BCM with VVDI Prog and VVDI2

Information: what programmers to use and from which to stay away when doing Porsche front and rear BCM modules on Cayenne, Macan, Panamera and others.

How to back up MCU memories – D-Flash and P-Flash, read IMMO/Key/CS related information and how to adapt used BCM and ECU modules to the car.

When you are trying to read/unlock/write BCM is dead after.
MCU’s used in these BCM’s is very sensitive (Motorola MC9S12 – 1L15Y, 1N35H, 2M25J, 5M48H)
and some programmers when trying to ID/Read/Unlock/Write these MCU’s tend to corrupt or erase the memories in these MCU’s.
From what we have experienced it is the D-flash and Partition configuration that tends crash.

Here’s the user working experience:

“I have from scrap Cayenne 2014 4.2 diesel – front and rear BCM modules and both ECU’s EDC17CP44
and I also bought used BCM from Macan 2017 to play with.

BCM reading/unlocking:
Cayenne Front BCM with 5M48H MCU, rear BCM with 2N25J MCU and Macan front BCM with 1N35H MCU.
All 3 BCM modules i successfully read with Xhorse VVDI Prog. I removed the diode, 0 ohm resistor,
made the cut to crystal connection and i prefer to desolder the crystal too and 12V power supply to programmer connected.
It had no problem reading the backup of Dflash and Pflash. It did the UNLOCK function without problem.
From there is started to experiment what could be the reason for corrupting these memories.
Using VVDI Prog i used LOCK function to lock back these MCU’s where locked byte is 7D (FE for unlocked).
I have Autel IM608 with XP400Pro programmer and I tried to use that for reading these BCM’s. 2M25J was OK. 5M48H was OK. 1N35H – DEAD.
Autel could not do the backup of the 1N35H, it was unsuccessful unlocking the MCU. After that VVDI Prog could not unlock it too because something in that MCU was already corrupted by Autel programmer.
Had to use “Force Unlock” with VVDI Prog and it worked but Dflash was already wiped, partition config was wiped and Pflash was seriously corrupted.
So i revived that 1N35H memories with what i had backed up before, did the LOCK again and tried again with Autel.
Autel killed it again. I don’t know about other people experience but mine Autel XP400Pro is a “No GO” fot 1N35H MCU.
I am not saying VVDI Prog is the golden tool because some people using VVDI Prog have killed the BCM’s.
For example i tried to read the 1M35H and 5M48H mcu with VVDI Prog but 12V power supply disconnected – it did not read anything. But it also killed these memories like Autel.
Maybe Autel has bad power delivery to MCU where 5M48H tends to survive but 1N35H is way too sensitive and dies.

Immo/ECU/BCM CS:
Since i have both BCM’s and ECU from the same car i did some research on IMMO CS information.
These are only my findings and I have no idea but maybe it can help to adapt used module to the car for someone using this info.

ECU is EDC17CP44 like VAG cars i tried to use VVDI2 to calculate CS from eeprom and flash and it worked.

In front BCM Dflash there are 2 CS. 1 for KEY programming and 1 that is exactly the same as VVDI2 calculated ECU CS.
In rear BCM Dflash there are 1 CS that is a MIX from both ECU CS and Key programming CS.
CS:
1B EE E3 28 DB 1A 39 7F 04 FA 01 A8 F2 8C E4 F7 – ECU (EDC17CP44) CS calculated with VVDI2 software 
A1 64 65 AE F1 B7 0A 3A 6C EB 56 7E A1 34 92 BD – Front BCM CS for key programming (located in Dflash 0x0021D and 0x0211D)
1B EE E3 28 DB 1A 39 7F 04 FA 01 A8 F2 8C E4 F7 – Front BCM CS for ECU sync (located in Dflash address 0x0022D and 0x0212D)
1B EE E3 28 F1 B7 39 7F 04 FA 56 7E F2 8C E4 F7 – Rear BCM CS (located in Dflash 0x00202 and 0x02402) is a mix
where 5th, 6th, 11th and 12th byte are from key programming CS and other bytes are from ECU sync CS