VAG-COM/VCDS EVERYTHING

[blackworms]

See post #9137- download zip file.
There you will find hwtype tool
Connect your vcd$ to car + your laptop
open/run hwtype and scan your tool- post here results- picture.

The picture you posted above are not clear enought to see what is writen on the pcb parts, so , read / look for Atmel Atmega 162 Au, if you find it let us know.

2B999F8C-4E10-4C92-96D0-845AB3969C1B.jpgCA5454A2-9002-4DE4-8A9E-FF6604BF8747.jpgAdsız.jpg

I wrote the individual chips because the picture is not clearly read. it doesn't work when i connect it to the car like in the picture. com does not see 1-2-3-4 ports. vagcom 18.9 EN + DE HEX-V2 - 2018 release. I have to polish it again, but I don't know how. I need all the polishing files in usb and com port files

[Xaby]

If bootloader is unlocked, download v9.2 from kolimer after that write with VAGCOM_EEWriteLang polish language, than you install vcds poland and update firmware.

[blackworms]

If bootloader is unlocked, download v9.2 from kolimer after that write with VAGCOM_EEWriteLang polish language, than you install vcds poland and update firmware.

Can you send me the files ?

CA3DEC1D-390A-41B3-80AF-F8EED45EA85C.jpg

[rak183]

Can you send me the files ?

https://www.digital-kaos.co.uk/forum...=1#post3714915

[blackworms]

https://www.digital-kaos.co.uk/forum...=1#post3714915

I'm trying a Vw polo 6n. vcds 18.9 + loader v7.0 was successfully written and vcds approved the license but did not work when I installed it in the car. Will the update be the solution? raise loader 9.2

Adsız.jpg

[rak183]

Use loader 9.2. Y have to flash your cable. See read me file inside loader.

[blackworms]

Use loader 9.2. Y have to flash your cable. See read me file inside loader.

From the loader file you mean boom

B7D28D1F-B2A1-4B70-92A5-6498FDAF60FF.jpg

[jan4]

From the loader file you mean boom

B7D28D1F-B2A1-4B70-92A5-6498FDAF60FF.jpg

read your pm

[Col19]

Hi friends,

I see that the cable with STM32 is out but the manufacturer of this clone is as greedy as ro$$teak In short, i prefer to stay with my atmega162 enough for my stuff.

Exactly i would like to ask a question to the experimented, which version is really functional with this He><V2 ? the 19.6 is not stable at home, the 18.9 is stable but as a lock, it is necessary to choose an even older version for the encodings... ?

Thanks and respect to the forum and friends such as Kolimer and all the big the sharing.

[winamax69]

Hello everybody,

Is this cable upgradeable?77002183_544144789466172_648393100800032768_n.jpg72758198_2433009816810473_4069973136391536640_n.jpg

Cable is blocked because of Internet connection.
C-test shows: Atmega162 Read error.

regards winamax69

[alexm1]

Yes, Will do by usb using "things" from Kolim3r zip or by usbasp.

[winamax69]

VAG-Com HWType:
VID / PID : 0403 / FA24
FT Serial : RT3S7QOI
FT Description : Ross-Tech HEX-USB
FT Chip ID : 0x503E8C25
FW Version : 1.78
HW Version : 0x44
Identification : ROSSTECH
SN : 0x00A8F2A9D716
Language : Chinese - ZHS
Bootloader : Enabled


but

I tried to write eeprom and I get this message: Writing firmware failed. Invalid bootloader?.

I think I must flash Atmega with USBASP. Am I right?

Cable has no GAL chip, but HWType shows: 0x44

How can I identify 100% is a 0x44 hardware typ?

[bajticzek]

Hello, can anyone tell me which cable should I get? Is V1 with M162 good enough? Right now I have prehistoric v11.11. It works fine, but you know, maybe a little updated version would be better. If I understand correctly, V1 doesn't support whole MQB platform, so does it mean all cars listed under wikipedia.org/wiki/Volkswagen_Group_MQB_platform are no go with V1?

Either way, is this version ok? https://imgur.com/9I7KOTH

Thanks for any info...

[alexm1]

VAG-Com HWType:
VID / PID : 0403 / FA24
FT Serial : RT3S7QOI
FT Description : Ross-Tech HEX-USB
FT Chip ID : 0x503E8C25
FW Version : 1.78
HW Version : 0x44
Identification : ROSSTECH
SN : 0x00A8F2A9D716
Language : Chinese - ZHS
Bootloader : Enabled


but

I tried to write eeprom and I get this message: Writing firmware failed. Invalid bootloader?.

I think I must flash Atmega with USBASP. Am I right?

Cable has no GAL chip, but HWType shows: 0x44

How can I identify 100% is a 0x44 hardware typ?

Has no GAL but there is ATF(same thing).
So, if reflash by usb failed, try with usbasp.
Pay attention with fuse bits and choose 0x44 dump.

[winamax69]

Thank you, I'll try it with usbasp.

Updated:

With Usbasp I flashed Atmega then With Mprog the FTDI chip. And with Hw write the eeprom with own language file. Now work like a charm with KLo@der 9.2.

Thank you very much.

Tapatalkkal küldve az én SM-G920F eszközömről