VVDI 2 new tool arrived

**amigokola** · 17th May, 2018, 01:39 PM

Guy's I have Octavia III MQB for a spare key. Original key number is: 5E0959752D and got info that 6V0959753D should work.
Anybody could confirm ??
Rgs.

**HeXeN** · 17th May, 2018, 01:45 PM

Originally Posted by amigokola

If it pulls out good 7 bytes CS ans PIN from EDC17 then it can.

VVDI2 cant read data from EDC17.

**amigokola** · 17th May, 2018, 01:51 PM

You asked about Abrites... With VVDI2 need to pull out CCM for sure. I know that Abrites most of the time can read data good from EDC17.

Originally Posted by HeXeN

VVDI2 cant read data from EDC17.

**GeminiAutoLock** · 17th May, 2018, 09:04 PM

Since purchasing VVDI2 it has failed on all MQB vehicles I have tried to program with keys bought from outside the dealer network.

I have successfully programmed numerous Golf’s and an Audi SQ3, all had a working key and all the new keys were ordered from the dealer (TPS). Process was flawless except for one of the Golf’s which had a Johnson controls dash and VVDI gave me a message that this was in development so I programmed this with ODIS.

The issues with programming spare keys on the vehicles I have tried vary, I purchased a key from 3D for an Audi A3 2016 model, part number
8V0 837 220 D , with VVDI it identified the correct dash, read the eeprom, read the immo data without any issues, when it came to making the key it knew there was a key in the reader, it kept failing to write the transponder.

On the 4-5 different Golf’s I’ve tried all of them fail at the same point , VVDI fails to recognise that there is a key in the reader. Part numbers were

5G0 959 752 BA

I have a 5G6 959 753 AG to try on Friday, I believe this is from Autokeys.us, it was given to me by another locksmith who has been told it will work so fingers crossed.

I just need a reliable source for these keys as I am turning these away on a weekly basis.

Andy

**zippy82** · 18th May, 2018, 11:47 AM

I always connect vvdi first and see if i can read the dash before cutting a key and if it works I save it and reset dash and go and cut the key and then start again, if it doesn't it's a TPS key and odis

I've done 3 A3 with vvdi and 3D keys no problem but then had 2 2013 that I couldn't read the dash so wasn't a key issue and also I've done 2 polo and 2 golf with keys from NW Keys and another golf with a china ordered key

I haven't had it fail on generating a key yet, are you generating a new key that the dealer will not be able program? I tried to copy a working key and that didn't work, it's the middle selection on vvdi I use, then it warns about bcm and gateway and loads of other stuff but I think it just means dealer will not be able to program the key

**GeminiAutoLock** · 19th May, 2018, 08:46 AM

Yep I too plug VVdi first to see if it recognises the dash, the A3 and Golfs all read the dash, eeprom and immo data, all failed when generating the key.

Yes the middle option is what I use.

The golf yesterday wasn't ready to try but I have a few to do over the next few days so will post results.

**zippy82** · 19th May, 2018, 09:01 AM

I heard there was problems with other mqb tools not being able to use some keys but luckily I haven’t had that problem with vvdi, I’ve got 5 3D A3 8V remotes left so hopefully they will work

**rob h** · 19th May, 2018, 05:09 PM

I am trying to create a Crafter remote key.
2E0959753A
Still not able to figure out which one to choose.
Language is still Chinese to me!

**szengen** · 20th May, 2018, 04:14 AM

am trying to create a Crafter remote key.
2E0959753A
Still not able to figure out which one to choose.
Language is still Chinese to me!
150 S extra
wait be patient

**drugowaz** · 20th May, 2018, 07:31 AM

Originally Posted by autoTkey

Anybody tried to program Passat B8 keyless with VVDI2? I just heard(can't confirm) that AVDI has some bugs and often damages the car because it hangs while programming procedure is running with this car.

You tested already? If key is keyless and do by dump keyless will not work?

**obeids** · 20th May, 2018, 09:33 AM

Hi there

1) So still no progress on the MQB all keys lost even if dealer supplied keys?

2) There is a problem / Bug on the Transponder maker with the Isuzu Module. I have one with 93LC66A Tokai Rika Module which usually uses the 4D64 / 4E transponder. It opens the file under the Isuzu 1998 / Trooper 93C66. The you press make key and it generates a new file. Load this new file in VVDI2 again and it now says "UNKNOWN VERSION".
Write new dump back and car will not start!
Tried different eeprom readers and different transponders and all give the same problem. Seems vvdi 2 isn't writing chip info correctly.
Could somebody who has TANGO check and confirm if the data writes the same as VVDI2 or not.
I have attached herewith the original dump from the vehicle....

**castin** · 21st May, 2018, 05:09 PM

Originally Posted by obeids

Hi there

1) So still no progress on the MQB all keys lost even if dealer supplied keys?

2) There is a problem / Bug on the Transponder maker with the Isuzu Module. I have one with 93LC66A Tokai Rika Module which usually uses the 4D64 / 4E transponder. It opens the file under the Isuzu 1998 / Trooper 93C66. The you press make key and it generates a new file. Load this new file in VVDI2 again and it now says "UNKNOWN VERSION".
Write new dump back and car will not start!
Tried different eeprom readers and different transponders and all give the same problem. Seems vvdi 2 isn't writing chip info correctly.
Could somebody who has TANGO check and confirm if the data writes the same as VVDI2 or not.
I have attached herewith the original dump from the vehicle....

Tango see 3 key, login 8799/9987