VAG-COM/VCDS EVERYTHING

[liviudiaconu]

Hi guys.
I have 21.9 v2 cable with atmega 162 inside with license revoked error and for some reason it fails in the end when i try to flash to any language with VAGCOM_EEWriteLang.exe (invalid bootloader).
[...]
Thanks.

1. I think you need external programmer if bootloader is corrupt
2. Stop dream. My last good version was 20.4.1 EN and 20.4.2 ROJ. 20.12 said "license revoked" after few use. And yes, my PC is protected against vcds.exe or another .exe from RT access internet.

[bg17aw]

Anyone got a link to 21.9 English please? Seems like 21.9 is the best for ARM interfaces

[mrle9]

Hi,

VCDS-Release-21.9.0-Installer

https://mega.nz/file/pNNhSYCL#tHgshX...gfGYCq89OJgoi4

Bye

[ALVINKONG]

ATMEGA162 16U-TH is a fake chip.

[hid3]

Indeed, agree with the post above.
If you take photos of older-generation cables, produced before ~2019 (before all that shortage, global reset and fake chips issue started) you'll notice totally different markings on them.
To remind you, chinese used to write VCDS version with a pencil on ATmega chip itself. This tendency was there without exception dating back to 805 VCDS version (back in 2008) up until 18.9 or so. Nowadays this has either become rare or disappeared at all. So something must have changed, eh? Or just chinese guy who was doing that, has died?

First fake chips appeared in "fake-V2" cables - chinese started putting fake ATA6561 (or was it NXP 1057?) CAN chips which died after several uses. I personally myself suffered from this issue.

Another batch - STM405/415 with burning out voltage regulators. Same thing - fake regulators which burn out after serveral uses.

A few more things I'd like to add:
- usually manufacturers use some markings in red to denote either rejection after quality inspection or not full package of the item; (pay attention to red dot on ATmega)
- among datasheets I cannot find any 16U-TH....
- proper ATmega162 marking were "16AU" with datecode afterwards, in the same line. This was the last line, there shouldn't be any furhter markings below. However, looks like Microchip (after acquiring Atmel) has changed their marking system a little bit. More info here: https://www.microchip.com/mymicrochip/Data/GBNG-15KQFZ896/pcn_gbng-15kqfz896_part%20marking%20guideline_part2.pdf

[drto]

Can you help me? Atmega 162 16U-TW FTDI FT232RQ. vcds.jpg

[bg17aw]

I tried to make a list for antivirus exceptions in Windows10 (Windows Defender) for Kolimer 9.2 loader (for Atmega interfaces)

1) folder C:/Ross-Tech
2) folder C:/Users/username/AppData/Local/Temp
3) block vciconfig.exe in firewall


This is what I got so far. If anyone else can contribute.

[kaalis]

2) instead of whole ℅temp℅ folder, i would add just 2 files (dll and exe) in that folder after loader has launched. Sort it by date and you will see.

Sent from my VOG-L29 using Tapatalk

[Billyym]

I tried to make a list for antivirus exceptions in Windows10 (Windows Defender) for Kolimer 9.2 loader (for Atmega interfaces)

1) folder C:/Ross-Tech
2) folder C:/Users/username/AppData/Local/Temp
3) block vciconfig.exe in firewall


This is what I got so far. If anyone else can contribute.

Install vcds.

Then

1) folder C:/Ross-Tech/Vcds/Vcdsloader.exe

2)Then I will go into firewall and block vcds.exe, vciconfig.exe inbound and outbound

Load up vcds loader. So the Vcdshook.dll goes into temp folder.

Then below.

3) folder C:/Ross-Tech
2) folder C:/Users/username/AppData/Local/Temp/VcdsHook.dll

And I've never had an issue with Cables being revoked.

[Turbz]

Have tried VIIPlusLoader-08.022.09.003(BETA) on 22.9 and 22.3.1 everything works. However, still has security access issues.

Works on 21.9 with no issues.

Hi I'm so glad I saw this as I'm quite new to vcds and I had spent a day trying to enter security code and always failed to accept with code 00 unknown. 21.9 done the job no problem and works well. Thank you very much

[Turbz]

Also does only the genuine cable show up as an interface in config as mine is empty in the drop list and tells me interface must be connected by usb to use this program. Mine is an 429 chip

[sszwagier]

I have an interface on ATMEGA162.


I bought a dead one. I replaced Atmega162 and FTDI.
After programming (At162 and FTDI) i put 12v on OBD and i have green and red LED for moment , after only flashing red.
HWType doesn`t see , VCDS not connect to car, EEWrite too.
MCP2515 is warm.
LM works correctly 12v gnd 5v.


Some solutions?


IMG_20221026_114117.jpgIMG_20221026_114123.jpg

[crouchinggerbil]

I have an interface on ATMEGA162.


I bought a dead one. I replaced Atmel162 and FTDI.
After programming (At162 and FTDI) i put 12v on OBD and i have green and red LED for moment , after only flashing red.
HWType doesn`t see , VCDS not connect to car, EEWrite too.
MCP2515 is warm.
LM works correctly 12v gnd 5v.


Some solutions?


IMG_20221026_114117.jpgIMG_20221026_114123.jpg

Did you check for shorts to ground? Have you another 2515 to replace with?

[zecas]

hi
anyone tested kolimer loader with 22.9?

[DeLuXe]

Hi,

I got a big big big issue with my VCDS. It is 20.4.2 version. Before when starting kolimer software it shows "x64" but now it shows x86 but all the long code helper text/info about each bit is away, in not only ABS but EVERYTHING.

Please how do i solve this? anyone with knowledge? I tried removing the software, re-install it in not only 1 but 2 win 10 64bit laptops with cable connected to car and without. It still dont show me long code helper texts on each bit. This happen after i had the car plugged in to a Golf 7, but it was working by the time, after that i have no idea what happen and now its stuck like this :/

Thanks for all the help!

Best regards,
DeLuXe