VAG-COM/VCDS EVERYTHING

[angelx431]

I'm searching EPT file FT232BL for version 17.1.3.
Thanks!

[absetup]

hello
i have and old head 12.10 with ft232RL , atmega162, can i flash it to a newer version ? if yes pls give me flash and tool for that

Thank you

[flavitm]

Angelx431 try this ept file

[Domi]

...........................

[Moldovan1]

somebody try with lock bits: CF? works?
i have to wait for my atmega162, cant try it

As Kolimer say:firmware do not check lock bits, so with FF work very-very good, tested by me!

[Moldovan1]

I want to send feedback about this firmware, posted in this thread: I tested on Skoda Citigo, 2014. Work very-very good. Stable connection, long coding work perfect, adaptation - same way. Perfekt! Thanks again Kolimer! Made a great work!
PS My VCDS is HW46 (but Kolimers identify soft say wrong HW44), reflashed from 12.12 to 17.1.3 with Xprog 5.51.

[suntester]

Regarding adapters with FTDI 232 BL chips inside.Follow at your own risk.
1.Create a fully working adapter with version 11.11.0 from this forum
2.Create a restore point on your computer
3.Uninstall any existing VCDS version and driver from your computer,possibly clean your registry of vcds staff
4.Disable your network adapter
5.Install all the nessesery and in the right order as described in VCDS 17.1.3_v2.zip Kolimer
6.Connect the adapter to the diagnostic socket of the car,put the adapter in a USB port of the computer and let the system install the nessessery driver in automatic mode
7.Start the vcds 17.1.3_cracked. exe and let the program update your firmware
8.After that perform the tests and you may have e licensed working adapter
I dont know what will hapen after you enable your network adapter again
Long live kolimer !

[Moldovan1]

Regnecessaryadapters with FTDI 232 BL chips inside.Follow at your own risk.
1.Create a fully working adapter with version 11.11.0 from this forum
2.Create a restore point on your computer
3.Uninstall any existing VCDS version and driver from your computer,possibly clean your registry of vcds staff
4.Disable your network adapter
5.Install all the nessesery and in the right order as described in VCDS 17.1.3_v2.zip Kolimer
6.Connect the adapter to the diagnostic socket of the car,put the adapter in a USB port of the computer and let the system install the nessessery driver in automatic mode
7.Start the vcds 17.1.3_cracked. exe and let the program update your firmware
8.After that perform the tests and you may have e licensed working adapter
I dont know what will hapen after you enable your network adapter again
Long live kolimer !

Point 1-3 is absolutely not necesary. Software 17.1.3 work great on computer with installed 11.11.5, 12.12, 15.7. No problem and no collision. Point 7 - soft do not update firmware. In point 5 you already made update of firmware by flashing Atmega. In rest is ok.

[suntester]

My initial point was to create a working 11.11.0 adapter It has had a 1.84 firmware.The installed ver.17.1.3 offered to update the firmware.It becomes 1.96 without any programer,just
right from installed program.I wanted to help the owners of the FTDI 232 BL chip.In Kolimers instruction there is not a word about FTDI 232 BL.There are dozens of questions about that
in the forum.I have not used any programer to upgrage from 11.11.0 to 17.1.3 as you mentonied in your post.I supose the goal is to use the latest possible version and to avoid a possible colision
with older versions and drivers for them-thats the reason of p.3.This is a solution what works for me and possible for the members who have FTDI 232 BL adapters

[Moldovan1]

My initial point was to create a working 11.11.0 adapter It has had a 1.84 firmware.The installed ver.17.1.3 offered to update the firmware.It becomes 1.96 without any programer,just
right from installed program.I wanted to help the owners of the FTDI 232 BL chip.In Kolimers instruction there is not a word about FTDI 232 BL.There are dozens of questions about that
in the forum.I have not used any programer to upgrage from 11.11.0 to 17.1.3 as you mentonied in your post.I supose the goal is to use the latest possible version and to avoid a possible colision
with older versions and drivers for them-thats the reason of p.3.This is a solution what works for me and possible for the members who have FTDI 232 BL adapters

I did not know what could be done in that way. If you test VCDS on car and perform for example auto-scan and ALL is ok, then is very good idea to upgrade firmware without programmer. Please test on car and if all is ok, I`ll try with another adapter to make same manipulation, without programming Atmega.

[suntester]

I have tested on a car that has a OBD II engine management,not on VAG car,my VW is gone.The adapter is homemade one,build 2008 or 2009 I think and until last week it was powered only from VCDS 805

[liviudiaconu]

[...]
PS My VCDS is HW46 (but Kolimers identify soft say wrong HW44), reflashed from 12.12 to 17.1.3 with Xprog 5.51.

And after reflash? What kind of HW say kolimer's tool?

[alexm1]

I tried kolimer's dumps (v1..v2) on two different cables, same troubles with both: autoscan does not work; if I try to acces Engine module- no message as espected: No fault ... all buttons are grey only Done, Go back is available.
Anyone else in this situation?

[Moldovan1]

I tried kolimer's dumps (v1..v2) on two different cables, same troubles with both: autoscan does not work; if I try to acces Engine module- no message as espected: No fault ... all buttons are grey only Done, Go back is available.
Anyone else in this situation?

Seems to be wrong fuses, or? I repeat: frimware from Kolimer work on car VERY-VERY GOOD, inclusive Auto-Scan on CAN-UDS blocks.Tested. And dont loose connection as 12.12, that I have before.
PS Verifica fuse, acolo poate fi problema.

[1 6 D]

I you doesn't have problems with UDS, I will try to flash second flash to me VCDS cable and check it.