VAG-COM/VCDS EVERYTHING

**Tib82** · 10th April, 2018, 10:50 AM

Az I wrote in #5981 the fake HEX-V2 cannot enter the "56 Radio" option with the followings:
f1.jpg f2.jpg f3.jpg
If I saw it clearly it's mounted with the followings:

U6A - MCP2515 17200TW
IC1 - FTDI 1120-C NO81471 PT232RQ
IC2 - HL008 738GC 2714B014 ARM
IC5 - TLE6250G 28D G1240

Now I was so "lucky" to test an another fake HEX-V2. On the PCB it looks a bit different, but it's still the same $h!t... Even with this I cannot the "56 Radio" option. It works with the official software and without loader, so it's only thing why it's better than the previous one.
fake-hex-v2-cable.jpg

U6A - MCP2515 17200TW
IC2 - HL008 738GC 2714B014 ARM
IC4 - ???
IC5 - TLE6250G 28D G1240

Anyway, I bought a normal version of HEX-CAN with Atmega162 and it's on the way

**liviudiaconu** · 10th April, 2018, 07:20 PM

IC4=FT232RL. Almost sure is 232RL China Fake and bad quality.

**kaalis** · 10th April, 2018, 07:48 PM

You could test fake cables by removing pin #7 and pin #15 (remember wire colors) from OBD connector in your car, then put back wire originally from #15 position inside connector position #7. Other wire leave hanging in air while testing radio connectivity.

Or just exchange places of both wires if it's easier to understand.

**dimet** · 10th April, 2018, 09:25 PM

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

**rivit** · 11th April, 2018, 08:47 AM

I flashed v6.1 by kolimer. I did test and it is OK. Later i connect it to the car and press 'Test'. On section "about program" there is serial number but it says "unauthorized". I made simple scan, error correction, coding (not long). Everything works. Why status program is unauthorized.

**alexm1** · 11th April, 2018, 08:51 AM

Why do (all) you keep trying, making experiments with an outdated loader? Find and use the last release ::v6.3. After that share all steps you make and maybe someone will figured out what you did not do it well...

**rivit** · 11th April, 2018, 02:38 PM

I want to use 17.1.3 AKP Polish.
18.2.0 is not available in polish language yet.

Will 17.1.3 work with 6.3 loadeR?

**Tib82** · 11th April, 2018, 08:15 PM

Originally Posted by kaalis

You could test fake cables by removing pin #7 and pin #15 (remember wire colors) from OBD connector in your car, then put back wire originally from #15 position inside connector position #7. Other wire leave hanging in air while testing radio connectivity.

Or just exchange places of both wires if it's easier to understand.

Why I have to change #7 - #15 pins in the car's ODB connector, if I can do the same on the fake interface?

Anyway it's a bit frustrating that my old fashioned blue KKL cable can reach and set the "56 Radio" option with the VCDS-Lite... and a 5x expensive interface not able to do it

**kaalis** · 11th April, 2018, 08:30 PM

I'm not your mum. You can do whatever you want. You can also power up your radio outside the car and connect it to cable k line directly.

**alexm1** · 11th April, 2018, 08:58 PM

@rivit
For now you have to use what you can get...english.
You can try 17.8.1 polish ,what you have to loose?

**makadam** · 11th April, 2018, 10:14 PM

Originally Posted by xoom

Yes, it will show CAN - OK..
i'm fixing VCDS cables like for 8 year.. i have on table AirBag Module to test all communications.. for airbag you can even disconnect K line and it will talk via CAN "TP 1.6 - 1281" protocol..
Attachment 514574 Attachment 514575

Can you give me pinout from airbag module , i have one only for testing vcds can and k line?

Sent from my 2014813 using Tapatalk

**nidclt** · 12th April, 2018, 08:09 AM

Hi guys, I came here when my VCDS clone cable gave 'No .ROD file' error after I accidentally kept internet ON when using the v17.1.0 software that came with cable. I thought my cable got damaged and will need to throw it away or reprogram manually. I almost read half of this thread in two-three days. Then my friend who also has a clone cable asked me to uninstall the Ross tech USB driver along with software (I didn't try that before), then reinstall. I did the same and yes, it started working again as normal. No 'No .ROD file' or 'Licenced interface needed' errors anymore. But, by this time as I went through this whole thread, I studied many things regarding this cable, I'm here just to say thanks to the contributors.

**networkers** · 12th April, 2018, 12:46 PM

Originally Posted by rivit

I want to use 17.1.3 AKP Polish.
Will 17.1.3 work with 6.3 loadeR?

VCDS-AKP-17.8.1 should also work with the loader v6.3. Don't forget to flash eepromavr_HW_0x4X_AKP.bin.

**rivit** · 12th April, 2018, 01:58 PM

Previously i flashed eepromavr_HW_0x46.bin and i use 17.8.1 PL (yes, before i said that i used 17.1.3 but now i have 17.8.1).
Is this reason for my problem with authorization (i checked, long coding don't work)?