MQB Key Programming Experience with Xhorse, Autel IM608, Xtool

Available with VAG MQB Key Programming experience with Xhorse VVDI2, Autel IM608, Xtool X100 Pad2 etc. How the user happy with any of these key programmer for VAG MQB? Go on reading.

 

Happy Experience with Xhorse VVDI2:

1)

I did successfully with Xhorse vvdi2 one Polo MQB and 2 Golf VII MQB, immo and remote works fine. I used cheap china keys, non keyless, half smart.

The key learning procedure is a bit specific:
Choose right Immo type (automatically)
Read EEprom – save
Read Immo – save
Make Dealer key (needs original key put in programmer to read syncdata, then put in blank key)
Then press ADD KEY button and choose the last point (requires loading immodata)
Put in key numbers to learn (2 if you add one key)
Proceed with giving ignition with both keys, after last ley is learned (you see status 2/2 in dash) press ok — That’s it, starting car and remote should work.

 

2)

Hello! I make keys for vag digital dash all the time using vag helper and vvdi2 and xhorse remotes..
For me, remote fails if the keyprecode inst done successfully.. verify the precode precedure and you will be fine.

 

3)

Today i make new key for Skoda kodiaq 2018 keyless Virtual dashboard without problem. Read immodata with Vag obd helper, make dealer key and learn keys with vvdi2

 

4)

VW Golf 7 , Johnson Control , one token to obtain Immo Data & add key using obd helper and vvdi2 …

 

5)

MQB VVDI2 add key 2015 Golf (no kessy) USA 315mhz- After learning keys (2) neither remote works.
Steps followed – 1.read eeprom 2. read immo 3. Save data 4.prepared normal dealer key using Xhorse model xsmqb1en smart proximity key 5. choose audi as the immo also identifies as audi 6. choose learn key with immo data (the last of the three options) and loaded immo data to make key. Not keyless. Make key successful. 7. reset instrument cluster 8.add key with working key, 2 total, went through the 1 of 2, then 2 of 2 ok. Both learned.
Started car after process both started the car but neither remote worked. Also tried resync with exterior drivers door lock – clicking unlock then unlocking manually and relocking. Didnt work. Confirmed both keys 315mhz including Xhorse MQB key.
Went back to add a key, clicked one, then relearned just the original key and the original key and remote work fine (restored).

 

6)

Vvdi2 experience ::
Yesterday I added key successful on VW TIGUAN MQB (2015)
1)read & save eeprom
2)read &save immo data
3) make dealer key
4) reset…..
5) add key :
a) method 1
b) give ignition with each key
6) reset
WORK DONE on 15 minutes
7.VW ARTEON 2019+ NCF Transponder – MQB49/5C Key Programming – Spare Key (Add Key)

8.

VW Polo model year 2014 replacement key
MQB system done by vvdi2 and KEYDIY folding key

9. Skoda Octavia MQB 2017 Remote key programming Xhorse Smart Key MQB – SA1896-1

 

10. 2019 VW ATLAS MQB TUTORIAL ALL KEY LOST USING VVDI 2 success

 

11. Golf Plus year 2010 UDS All keys lost
Program keys with VVDI2 and VAG Helper cables

Program VW MQB NEC35XX Smart key using VVDI2 Key Programmer

Happy Experience with Xhorse VVDI Key Tool Plus:

1.2019 VW POLO MQB49/5C add key success!

Used KTP for the whole process. Read data with pad, then sent it for online calculation (cost 1 token – must be charged before).
After 3 minutes I got immo data file which automatically saved into device. After that you make dealer (used Xhorse proxy MQB style) and programmed to the car as usual.

 

2. New beetle mqb proximity, program remote obd using xhorse 315mhz MQB key in 8 minutes

 

3. 2013 Volkswagen Passat Keyless Go- All Keys Lost with Key Tool Plus/Vag Helper

 

4. add MQB49 key VW Sagitar with key tool plus pad success

 

5. Done a 2014 VW Jetta AKL using xhorse pad and vag helper without issue

 

6. mqb Skoda Octavia 2015 build year MQB AKL situation, all done via VVDI key tool plus
Read calculate anti-theft data and synchronization data ,send it online, get online calculations , prepare dealer key and programmed it successfully, car runs and everything working great.
Full work about 15-20min, but before I get information where to send data and get correct contacts who make the online

 

Guide:

Program VW MK7 2014- MQB Key with Xhorse VVDI Key Tool Plus

 

 

Happy experience with Xtool X100 Pad2 + KC100/X100 PAD3/PAD ELITE:

1. Golf 7 2016 i have done in few minutes with X100 Pad2.
Reading immo data via OBD, pre-code an empty key with KC100

 

2.

Programming GOLF VII 2015+ (VW-CIR26) with X100 PAD ELITE success

 

3.Use the Xtool x100 Pad2 to add a new MQB key for the 2015 Volkswagen Lamando success

 

4. duplicate Seat Leon MQB Key with x100 pad2 and kc100 without problem

How to Get Xtool VAG Access Code for VAG 4th 5th IMMO & MQB AKL?

Happy experience with Autel IM608/IM508:

1. Seat Leon 2014 – MQB chip
(VW GOLF7-AES BA SERRIES  AUTEL)

2. Skoda Fabia , 2018 mqb, obd, add autel im 608

3. Golf VII MQB 2016 Add key with  im508+xp400
Read immo success
Calculating time about 3min
Make dealer key success
Adapt new key failed – because I had no battery inside key.
I put battery inside and learning ok.
Whole procedure about 12min.
Used chinesee aftermarket key.
4.Seat Ibiza FR 2016 mqb. Key programming with im508 and xp200! Realy easy job 5 min.

5.

VW Golf 2017 MQB
Read immo data
Calculation
Make OEM dealer key in XP400
Add key (is free)
Done

6.

Just done my first Vw golf 2016 mqb with Johnson’s controller. Start to finish wast 20
Min. Online calculation was 5 minutes even though it warned it could be between 1-72 hours. Would not pre code an Xhorse remote but would a normal one with correct matching part number.
7. 2015 vw polo add key (mqb) succes by im608, read password- make dealerkey- keylearning. No charging, paid nothing, only akl is costs
8. Success on a 2016 Audi S3 MQB Prox key. Took less than 5 minutes to make dealer key and program under advanced mode.
9.VW Polo 2016 year MQB system All Key Lost successful by OBD
10. Job done in less than 3 minutes with IM508! Seat Leon 2014, MQB system, Zedfull failed to read data

Autel IM608 Program Jetta 2017 Kessy MQB All Keys Lost via OBD

Not very happy experience with Xhorse VVDI2:

I had golf 7 mqb dash JC
Adding key blade not proximity , vvdi2 not support to read this dash , used vaghelper to obtain data and then all done by vvdi2
The only problem is remote function didnt work
I tried all mkb keys in xhorse same problem in remote , after few research i found that many people having same problem
Hope it help someone

 

All mqb on xhorse been tested also bring original key but last letter was different 202 e i found a as i remember
Also i changed places of keys 2 in place of 1 and both remotes not function
I tried the door lock synchro no luck
I reput keys prig to its place 1 and remote is functioning again
Strange maybe now after xhorse update data base maybe they make compatible remote ???

 

To be updating…

 

www.obdii365.com

OBDII365