VAG-COM/VCDS EVERYTHING

**wallix89** · 10th May, 2018, 02:20 PM

Originally Posted by wallix89

Hy guys. I have a vcds 12.12 chinese clone that shows unregistered. I still can do some things with it, but not to much. Can anyone walk me through , how to reflash this tool ?The chip inside is atmega 162 (16AU 0921H) ,FTDI 1608-C CN480661 FT232RL. Thanks in advance.
Attachment 527319 Attachment 527311

i managed to make my cable registered again. i just copied the vcds loader.exe from kolimer's package to my ross tech folder. i did a test with the cable and it shows registered, and another one on the car and still registered. only problem that remains is the error for comunications "too many comunicatiions errors"

**jan4** · 10th May, 2018, 04:16 PM

follow the instructions from the pdf ,
i had similar problems before i followed the complete guide.

**Fabio89** · 11th May, 2018, 05:29 AM

Guys,

i Have a chinese hex-v2 17.8.1
it is showing "Invalid/Unauthorized
VCDS invalid.JPG

Any chance to fix it?
Thanks

**hid3** · 11th May, 2018, 06:48 AM

Pics of the Chinese hex-v2 PCB?

**peetr** · 11th May, 2018, 11:07 AM

Today I've got my Hex-V2 from obd2cartool and I don't understand one thing: They say that they use kolimers firmware and loader, but they set the atmega lockbits anyways. Therefore I couldn't read the flash and eeprom. I'm not mad at all, I just wonder why.
I wanted to backup the original firmware, in case I need to go back. It seemed that the LEDs where blinking a little bit different, maybe I imagined it, but thats why I wanted to do the backup.

Anyways, the hex-v2 works just fine with kolimers loader v6.3. Thank you veeeery much!

**alexm1** · 11th May, 2018, 11:09 AM

Usually Atmega is protected for reading....you will get some dumps but are encrypted. If you can not read at all: are you sure it is Atmega inside?

**peetr** · 11th May, 2018, 11:19 AM

I've opened it up and yep it has a atmega inside with "178" written on it. I connected my usbasp to the prog header
I could read the flash but I got either just FFs or garbage. The lockfuse was "C2" and http://eleccelerator.com/fusecalc/fu...chip=atmega162 says it means "application protection mode 3", "boot loader protection mode 3" and "further programming disabled"

**hid3** · 11th May, 2018, 12:13 PM

I think it contains V5 inside there. Don't worry, just use Kolimer's latest.
If for some reason you need to go back to "original", try contacting them, they are friendly and helpful people.

**max29** · 11th May, 2018, 06:35 PM

X fabio Copia kolimer loader nella cartella ross tech /vcds

**max29** · 11th May, 2018, 06:42 PM

Originally Posted by Fabio89

Guys,

i Have a chinese hex-v2 17.8.1
it is showing "Invalid/Unauthorized
VCDS invalid.JPG

Any chance to fix it?
Thanks

Copia kolimer loader v6.3 nella cartella ross tech /vcds

**dannyb13** · 11th May, 2018, 08:33 PM

Hi,
hoping someone can point me in the right direction. My Vag Com has stopped working been about a year since i last used it. it's showing status "Status: Not plugged into Car"
i'm guessing a solution is buried somewhere within these 417 pages, and any direction would be appreciated. it's a VAG106 photos of the board attached, tried using software 10.6

DSC_0105.JPG DSC_0106.JPG

**kaalis** · 11th May, 2018, 08:36 PM

Start reading this thread backwards. Page by page.

**peetr** · 11th May, 2018, 10:30 PM

Originally Posted by hid3

I think it contains V5 inside there. Don't worry, just use Kolimer's latest.
If for some reason you need to go back to "original", try contacting them, they are friendly and helpful people.

Alright, thank you for your answer!

Just a feedback: I've tested the interface with my golf 5 gateway+airbag testbench on my table and everything (incl. coding) seems to work just fine. I don't see any improvements in speed, but I like the case+cable and I like to have a spare interface, in case my first one dies unrepairable. I use it just for my own and friends cars, no profitable use at all.
For extra protection I've soldered a NUP2105LT1G CAN protection diode in the missing place on the pcb. They are dirt cheap and probably not needed, but I like it that way.

dannyb13, look on page 389, but keep in mind that on the way back you may find useful informations for your interface.

**rak183** · 12th May, 2018, 02:35 PM

Hello, my friend is asking if this interface a good one? Thanks.20180512_124430.jpg 20180512_124430.jpg 20180512_124452.jpg

**alexm1** · 12th May, 2018, 02:42 PM

I have an issue with an older cable updated to 18.2.0, it does not work on a laptop with win 10 64 bit in dev manager I get:
USB device is not recognized "Device Descriptor Request Failed"

On the same laptop with win 10 I tried another newer model cable with 18.2.0 and is working fine.

The older cable is the one with Atmega, Ft232RL, no Gal/Atf and this cable is working just fine on a laptop with win 7 32bit.

On the laptop with win 10 I did the steps to dissable digital driver signature enforcement. Tried to instal driver manually, no luck.

Any ideeas?