VAG-COM/VCDS EVERYTHING

**heshamzn** · 26th August, 2019, 02:42 AM

Today I manage to flash my vcds 12 with the latest files with my pc and usb only and didn't connect the cable to 12 v or to the obd2 and done successfully

**alexm1** · 26th August, 2019, 06:22 AM

When you conect usb to your PC, led is on?

**drag00n** · 26th August, 2019, 07:43 AM

Hi, I've been reading this forum for some time. I have 2 clone RT from Ali. I'm thinking if I can upgrade it to latest version (if upgradable or should I buy a better clone. Thanks in advance.

Sent from my SM-N935F using Tapatalk

**alexm1** · 26th August, 2019, 07:53 AM

You can try to update the "red" one(pcb). Try first to see if your bootloader is enabled, if not you need usbasp programmer. And you need to do your homework reading Info/read me pdf file from Kolimer.s zip, you have there STC on the PCB so you have to cut circuit to R50.

**heshamzn** · 26th August, 2019, 08:09 AM

Originally Posted by alexm1

When you conect usb to your PC, led is on?

red led not green but it worked ok

**alexm1** · 26th August, 2019, 08:19 AM

There are some old cables without LM 7805 voltage regulator and Atmega is powered from PC usb. That.s why you do not need 12 v.

**msemafor** · 26th August, 2019, 10:51 AM

Just to ensure myself - now I have a cable with chip ATMEGA 162, FW version: 1.96, HW version: 0.44, Identification: ROSS-USA, Bootloader: enabled. Use it with 17.1.3. Can I safely use VAGCOM_EEWriteLang from K0limer's pack 9.2 (huge thanks) to update cable firmware and then connect to Octavia 3 1.4 TSI 150 PS CZDA MY2016 with version 19.6.1? Maybe I don't even have to update firmware - just install newest version, save loader in appropriate folder and start it? Won't it brick my cable?

**kaalis** · 26th August, 2019, 11:39 AM

You have to update firmware, otherwise 9.2 loader won't function as it should.

**msemafor** · 26th August, 2019, 12:14 PM

Originally Posted by kaalis

You have to update firmware, otherwise 9.2 loader won't function as it should.

Thanks kaalis. Are parameters i mentioned above make my cable ready for firmware update without risk of destroying it? I wouldn't like to stay with nothing except need to buy another one.

**kaalis** · 26th August, 2019, 12:24 PM

Just try updating it and don't you worry.
Post pictures of PCB both sides and then we can tell in detail how good/bad/so-so is it.

**msemafor** · 27th August, 2019, 06:26 AM

Originally Posted by msemafor

Just to ensure myself - now I have a cable with chip ATMEGA 162, FW version: 1.96, HW version: 0.44, Identification: ROSS-USA, Bootloader: enabled. Use it with 17.1.3. Can I safely use VAGCOM_EEWriteLang from K0limer's pack 9.2 (huge thanks) to update cable firmware and then connect to Octavia 3 1.4 TSI 150 PS CZDA MY2016 with 19.6.1? Maybe I don't even have to update firmware - just install newest VCDS, save loader in appropriate folder and start it? Won't it brick my cable?

Would like to confirm that I succesfully updated firmware taken from K0limer's pack 9.2 and installed version 19.6.1 AKP. Works great with two Octavias 3 1.4 TSI 150 PS CZDA MY 2016 and MY 2017. Big thanks to all, who adviced me and even bigger thanks to k0limer.
Unfortunately in module "Engine" button "Measuring blocks" is inactive in both mentioned cars. Maybe anyone knows why is that?

**alexm1** · 27th August, 2019, 07:07 AM

Same thing with Adv. Meas. Values?

**msemafor** · 27th August, 2019, 07:30 AM

Originally Posted by alexm1

Same thing with Adv. Meas. Values?

Nope, Adv. Meas. Values are active and show actual data.

**alexm1** · 27th August, 2019, 08:11 AM

In this case is a normal behaviour...

**jach0o** · 28th August, 2019, 10:22 PM

blad mib22.png
after flashing 9.2 loader i got problem "no coding information" for 5F in A6 C7.5 MY2018 witch was working before(long coding helper). Currently even if i restore to lower loader with different (lower vcds) it still drops same error?? what should i do ?
to be honest 5f is one of most tweaky driver so its importat for me to have possibility to see codings

blad mib2.jpg