VAG-COM/VCDS EVERYTHING

[networkers]

No doubt, i don't know why the loader needs more "start tries". Windows 7 seems to work a lot better.

[Mario6]

No doubt, i don't know why the loader needs more "start tries". Windows 7 seems to work a lot better.

Hi. I had the same problem on Windows XP. After installing dotnetfix 4.0, the problem disappeared.

[alexm1]

Sometimes happens in win 7 too... usualy at first start on a new pc.

[AndreaEl]

I see that on some HQ china start ti appear the newer version (v18.1.0). Have you some news about loader, dump for this newer version?

[Triquepas]

A few page back you will find all you need or just click below...
Enjoy kolimer's work.

https://www.digital-kaos.co.uk/forum....php?p=3185666

Thank you alexm1 for the Link
Unfortunately VAGCOM_HWType.exe report "no response" of my cable, it's however detected by windows 7 ?!?
I don't know if I can still try to flash anyway and without hardware changes. I don't have on my PCB, protection diode and L9637D driver instead of
transistors. It's the same hardware of alexm1 's cable http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3207108&viewfull=1#post3207108

@Alexm1
If it worked for you, can you explain your VAGCOM_eewrite settings that you used, because I don't know what HW type should I choose (not detected for me).

Thank you for your help.

[networkers]

Thank you alexm1 for the Link
Unfortunately VAGCOM_HWType.exe report "no response" of my cable, it's however detected by windows 7 ?!?

You need to supply 12V to the cable or connect it to a car.
vcds-obd-12v.jpg

[alexm1]

Make sure your cable is seen in dev. Manager as Ross...cable interface/ hex...etc

Power up with 12 your cable via obd or direct to LM7805

Run Vcds...test.

After that run hwtype.exe

But if your is cable has a old vers of vcds...there is no chance to write dumps via usb. You need a Usbasp programmer.

To see what type of hw you have, read pdf file from the archive.

[liviudiaconu]

Sometimes happens in win 7 too... usualy at first start on a new pc.

Yes, at first start maybe because loader first time change the extension.
Second time launch OK.

[engycz]

Here you can see how it happened (see file attached).


In two words: after trying to chang byte 27 from 00 to 04 it has changed acording to coding debug file to D0. After this I got a lot of faults in BCM but haven’t time to find out the reason. In couple a days I'v get back to the issue and saw completely wrong coding in BCM!

41190B218D260FC1458901C132010EC54E7E9189426E8661E5 85C80E0142 instead of
40180A208C250EC0448800C031000DC44D7D9088416D8560E4 84C7040041

Which VCDS version?

[hid3]

Happens with all of them.

Ha ha

[Vet]

Which VCDS version?

17.8.1_En with Loader V5

[engycz]

17.8.1_En with Loader V5

There are at least two versions of 17.8.1. https://mega.nz/#F!or5AQTwY!GxLeQwZkfOaogV0HCERViA One (V1) is working with V5 loader, second (V2) is not working correctly and it's dangerous to use it.

[alexm1]

V1 has 37.5 mb and v2 37.4 mb?


L.e. I see the complete name after download, now is clear.

[networkers]

Both Versions are original/unmodified RT Installer.

v1 has Signing date 10:08 PM 12/1/2017
v2 has Signing date 12:16 AM 1/13/2018

sha256 hashes:

a9943631c1a7a7fe47f075ccbc5a69b04aa4a3ea97c0ca496c 652c074bad49d1 VCDS-Release-17.8.1-Installer_v1.exe
8e123d05455438a1d6cbf52543181f41aef9d0267dac0cd855 baab48964d926b VCDS-Release-17.8.1-Installer_v2.exe

[gerar19]

Cracked VCDS 16.8.0 (Exe only) and ATMega dump (FW for HW type 1 & 2 + EEPROM). Dissabled marriage with FTDI Chip ID and cleared blacklisted serials. Original VCDS 16.8.0 installation can be found here https://link-4share.com/download/jl3...aller_rar.html.

Copy cracked VCDS vcds_dump_16.8.0_crack.exe to the directory where vcds is installed and run it.

Attachment 425389

thank you! I try later.