VW Smart Key Programming Gone Wrong (Part 1) 

Thank you for your advice. I started doing that since then. However, that was not the problem because if it was it would have failed for the first original key and the key i ordered for the customer; only the third amazon key was not accepted because he probably received a key with the wrong fccid because vw and audi have a variety of keys for same vehicles; i always call the dealer to get the part number then i convert it into the right fccid in my key database before i look for it on suppliers websites.

@@DFWAuto_Hack ok thanks

Thank you. If it had not programmed key 1, it would not prompt me to learn key 2 & if it had not sensed and learned key 2, it would not have prompted me to move on to the last key per the programmer say; while i dont argue that the key should be held at the while pressing okay sensing area to prevent any risk, i am positive that it must have sensed and learned the first two keys for prompting for the next each and everytime. If that was the problem then key 1 would not be sensed hence not learn so it would not have asked for key 2 and vice versa. My thought process is there must be a time frame within which the programmer recalls the key data but this must also be subject to key quality and / or type (wrong fcc ir no); But I got your point and understand it is just better to keep it there while pressing okay. Anything happening for a reason, i am glad it happened that way because it forced me to get out of trouble by myself in a pretty intense situation & since it was not as easy as loading immodata and done, it was perfect for a part 2 video on how to recover manually. Thanks a lot for your advice and God bless you and your family

@DFWAuto_Hack I had similar problems with tiguan. One I had to remove cluster to get to eeprom, the other since I used a different programmer I was able to read pin code and took a picture of it and luckily I was able to do akl with with the im608 and the pin code from the other programmer. I haven't seen your part 2 video, but I'm going to look at it. Thanks and great work.

@@car-key-programming Nice job on the eeprom; had you used vvdi prog? I use vvdi prog and vvdi2 on eeprom but i have had a lot of issues with a 2016 Tiguan clustered i purchased online to self train at the office. I am not sure about the eeprom type. Keytoolplus says 24C64 and another programmer says 24C32 so i am very confused but it is not a customer job so every night i try till im able to get it lol. About part 2 sorry it is far away from Part1 because i did not realise that the setting of part 1 was not visible when i made both videos so part 2 was published several months ago but i only realised the problem yesterday which is why part 1 came out after part 2; i dont even remember if i was able to video the whole recovery step by step (i was sweating in the car lol)

@@DFWAuto_Hack u are wrong u need to hold key while pressing okay it didn’t sense the key I promise u if it did then the number on the dash would change to 1-3 and then 2-3 and with the final key 3-3 which it didn’t do for u trust everyone when they say that’s what u did wrong I’ve gone hundreds of VW and on all of them u have to hold key while pressing okay go back and try it this way and see it will work

@@DavidPetrisor thanks i already corrected what is wrong and i dont make this mistake anymore. This video was made several months ago. Just posted now because i did not realise it had never posted. I guess i was too focused on the programmer screen to notice the dashboard 1/3, 2/3 & 3/3; I did not do as many vw but i knew about the dash and i just never watched the dash; i might ve been too tired because i remember having fell asleep behind the wheel on my way to this customer. Thanks a lot. Another thing that kept me not realise my mistake is the programmer kept telling me to try the 2nd key after the first one so im still wondering why it did if it did not sense it. Time to look through my video to see what i did when relearning the two keys successfully without the Amazon key. Thanks again for your contribution.