VAG-COM/VCDS EVERYTHING

[kiruxxx]

Hi. how I can update my vcds 12.12 to new version? What need soldering or make bridge? And wahat chip is missing? thanks vcds1.jpgvcds2.jpg

[xoom]

Hi. how I can update my vcds 12.12 to new version? What need soldering or make bridge? And wahat chip is missing? thanks vcds1.jpgvcds2.jpg

It's NEC mcu.. there is nothing you can do..

[kiruxxx]

ok thanks

[cybermaus]

So, after reading, studying and soldering, I think I am now ready to flash/repair my VAG912 cable.
It is a type-2 or HW 0x46 cable, including STC chip, the exact image of the Info.pdf doc.


I have a STK500 programmer clone, not a USBASP. I installed AVR Studio 4, and I successfully wired it up, I can verify its a 162 and read fuses and lockbits. Its all responding well, I feel pretty confident that if I press "write" the STK500 will write flash and eeprom.


I plan to upload not the latest image with VCDSLoader.exe, but this cracked V16.8.0 from Feb 2017. Because I am getting Virus warnings on the newer Loader and HWType programs.
As much as I like to ignore them, virustotal is telling me 19 out of 67 virus engines see the VCDSLoader.exe as infected. That's a bit too much to write off as a false positive.


So before I press write on the V16.8.0, I have a question or two:


Q1:
The Fuse bits advised for HW 0x46 are E: F9, H: DA, L: CD
But the ones I currently read from my cable are E: F9, H: DC, L: CD
Which are the ones advised for HW 0x44. I am however quite sure I have 0x46. Foto is exactly that of the info.pfd and there are no connections on pin 34+35

Should I worry about that? Which fuse bits should I use?
Unfortunately, I could not find lock bits for the V16.8.0 file specifically

Q2:
The later info.pdf for the VCDSLoader method suggest to disconnect the STC chip. Is that also relevant for the previous method of using hacked V16.8.0?
What is the STC chip anyway?

Q3:
Do I need to change the VID/DEV for the V16.8.0? Currently my cable is FA24?


Many thanks.

Edit: AVR Studio has text for the fuse bits, and they explain the difference:
xDC = Boot flash size $256 with start address $1F00
xDA = Boot flash size $512 with start address $1E00
So obviously you need to change because kolimer bootloader needs more space

[hid3]

I think this hasn't been discussed yet (rather than "how do I flash my cable" in every 3rd post).
So let's discuss the viruses topic.
There are two points.
First. It might detect it as a "virus" because in fact loader is something what starts before an application and later on loads another application. The activity algorythm is considered suspicious, so that's why it is being marked as a virus.
Second. The German Professor (or more likely his team) is monitoring this thread very attentively (greetings Andy, your "support" really sucks TBH). Once they find the loader published, they submit it to various antivirus companies claiming it's a loader and something what spoils their application. Some/most manufacturers accept it and further mark the loader (by it's MD5sum, SHA1sum or <anyother>sum) as infection.

Funny thing, some antivirus programs were marking \/(DS application itself as an infection; most likely because of its certain actions too. Someone had to sweat convincing the antivirus companies it's not

In conclusion, the loader is safe. But if you want, you can use any legacy version, of course. In Russian, there's a very good proverb - "Everyone w_a.nks as he wants" (Каждый дрочет как он хочет).

[kaalis]

So, Kolimer could upload new loader to virustotal.com before releasing next version and compare results later after RT submits it's next false positive.

[vaicekas]

I got into an unpleasant situation with Loader 6.3. When the antivirus program started to delete it, I pointed out the loader to the list of exceptions. However, when I starting the loader -Windows reboots. And from that point, windows reboots by launching almost all exe files. Helped only clean windows installation. I did not start the loader anymore.
Has anyone happened like this?

[bibkare]

I got into an unpleasant situation with Loader 6.3. When the antivirus program started to delete it, I pointed out the loader to the list of exceptions. However, when I starting the loader -Windows reboots. And from that point, windows reboots by launching almost all exe files. Helped only clean windows installation. I did not start the loader anymore.
Has anyone happened like this?

For me loader 6.1 works best, NOD AV program doesn't recognized it as a potential threat and also starts excellent on win XP and other OS

[Polocarr]

Hi guys
How can I update the cloned VCDS HL008 ARM Chip from 17.1.3 to 18.1.0

http://zupimages.net/viewer.php?id=18/14/8t5m.jpg

http://zupimages.net/viewer.php?id=18/14/ay3j.jpg

Thnks

[hid3]

Impossible. This interface is total crap. Firstly, no ATmega162 chip there. Secondly, there is MCP2561 chip which goes into sleep mode and there's no way it could be compatible with this setup. Besides, I really doubt that your 17.1.3 works correctly (License Valid is NOT an indicator).

All you can do with the above interface is this:
-Return it to the seller and request for a refund if you bought it recently;
-Keep it for spare parts;
-Give it as a gift for a neighbour's kid.

And for yourself you could buy some quality one. I have posted at least 10 times in this thread on where to get quality ones for affordable price, do some search.

[Tib82]

Hi guys,

I bought a good-looking cable for the VCDS 17.8.x, what I think is a HEX-CAN cable but looks like HEX-V2
IMG_20180402_111924.jpgIMG_20180402_112131.jpgIMG_20180402_112229.jpgIMG_20180402_112321.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

So it came with the VCDS 17.8.1 and 2 additional files (a DLL and a loader EXE), and for the first look it works well. For the 1st look... Because in the VCDS 17.8.1 (and with a 2005 Audi A4 b7) if I enter the "Select Control Module" menu and I want to open the "56 Radio" option, the programs says "No response from controller". I'm angry because if I use my old fashioned & cheap blue KKL cable with the totally free VCDS-Lite program I can reach the "56 Radio option" and I can configure it too...
cables.jpg

I also tested it with a 2010 Audi A6 4f and when I tried to read out the total mileage, the VCDS said the program cannot communicate with the ECU.

My questions are:
- Can you tell me please how can I solve the communication problem (e.g.: "56 Radio" option)?
- How can I check the version of my loader? And where can I find an another version of the Loader?
- Is there any chance to use it with a VCDS 18.x.x?

Thanks for your help!

[Tib82]

What do you think which is the better?

Fake HEX-V2 above
IMG_20180402_112229.jpg
Firmware version: 1.96
Printed circuit board: MCP2515 17200TW + FTDI 1120-C NO81471 PT232RQ + HL008 738GC 2714B014 ARM + TLE6250G 28D G1240

Special Features:

1. Sofware version: VCDS 17.8.1
2. Languages: German / English / Hungarian / Romanian (and so much more)

OR

HEX-CAN interface + VCDS 17.1.3
atmega.jpg
Firmware version: 1.96
Printed circuit board: ATMEGA162 + 16V8B + FT232RL

Special Features:

1. Sofware version: VCDS 17.1.3, can not update.
   
2. Languages: German / English (without other languages)
   
3. Not supported -- K2 protocol unit, USB 3.0. Must be USB 2.0 !

OR

HEX-CAN interface + VCDS 17.8.0
atmega2.jpg

Firmware version: 1.96
Printed circuit board: ATMEGA162 + 16V8 + FT232RQ

Special Features:

1. Sofware version: VCDS 17.8.0, can not update.
   
2. Languages: English / Hungarian (can not Support other languages)
   
3. Not supported USB 3.0. Must be USB 2.0

OR

HEX-CAN interface + VCDS 17.8.0
nec.jpg

Firmware version: 1.96
Printed circuit board: NEC + FT232RQ

Special Features:

1. Sofware version: VCDS 17.8.0, can not update.
   
2. Languages: English / Hungarian (can not Support other languages)
   
3. Not supported USB 3.0. Must be USB 2.0

If the second option, is there any chance to use it with the 17.8.3 version?
If no way to use it, has anyone VCDS 17.1.3 in Hungarian (VCDS-HGJ) language?

What is the difference between the last 3 cable PCB's chips?

• ATMEGA162 + 16V8B + FT232RL
• ATMEGA162 + 16V8 + FT232RQ
• NEC + FT232RQ

[safm]

What do you think which is the better?

Fake HEX-V2 above
IMG_20180402_112229.jpg
Special Features:

1. No need disconnect internet, no need change date.
2. Sofware version: VCDS 17.8.1
3. Languages: German / English / Hungarian / Romanian (and so much more)

Firmware version: 1.96

OR

HEX-CAN interface + VCDS 17.1.3
atmega.jpg

Special Features:

1. No need disconnect internet, no need change date.
   
2. Sofware version: VCDS 17.1.3, can not update.
   
3. Languages: German / English (without other languages)
   
4. Not supported -- K2 protocol unit, USB 3.0. Must be USB 2.0 !

Firmware version: 1.96

Printed circuit board: ATMEGA162 + 16V8B + FT232RL

If the sesond option, is there any chance to use it with the 17.8.3 version?
If not way to use it, has anyone VCDS 17.1.3 in Hungarian (VCDS-HGJ) language?

IMO the second one it's better, with Kolimer loader can you update it

[Tib82]

Thanks

I updated my post with a 3rd cable Can you check it and give an advice please?

1. VCDS 17.8.3 + Fake HEX-V2: FW1.96 + MCP2515 17200TW + FTDI PT232RQ + HL008 738GC 2714B014 ARM + TLE6250G
2. VCDS 17.1.3 + HEX-CAN: FW1.96 + ATMEGA162 + 16V8B + FT232RL
3. VCDS 17.8.0 + HEX-CAN: FW1.96 + ATMEGA162 + 16V8 + FT232RQ
4. VCDS 17.8.0 + HEX-CAN: FW1.96 + NEC + FT232RQ

With almost the same prize is the 3rd the best buy or the 4th?
Is it better than the fake HEX-V2 only because I can update it? Or... Is there any other thing (like better cummunication / faster data / etc.) why is it better?

[hid3]

Regarding your "HEX-V2" see my post just above your first post here. Everything stated there applies to you too.
And as for "which cable should I buy", this also has been discussed tens of times, if not more, please do some search or go a few pages back.