VAG-COM/VCDS EVERYTHING

**beli123** · 6th February, 2011, 10:26 PM

thanks man

**mattydr67** · 6th February, 2011, 10:27 PM

Originally Posted by ~~~tak

In my VCDS908 i have sma problem before.After change 1 digit in RT-USB driver from 0 to 1 .This stops FTDI chip to write own VID and PID.After that i do not problem with unplug cable from usb.This is solution that i read in forum but i dont remember who is write it.Maybe help to you.Best Regards

Do you mean this:
RT-USB.NT.HW.AddReg]
HKR,,"ConfigData",0x00010001,0
like this:
RT-USB.NT.HW.AddReg]
HKR,,"ConfigData",0x00010001,1
??????????????
Good luck

**beli123** · 6th February, 2011, 10:37 PM

Originally Posted by bibkare

Beli my friend reflash atmega with new dump and also reflash ftdi with new eeprom, you have everything here at least for version 908

can you look your pm bibkare? pls

**beli123** · 6th February, 2011, 10:43 PM

Originally Posted by mattydr67

You need to reprogramm it.
Our friend Aminebot it is expert in this and he explain here why it happend to you this.
Just becasue you need to stop ross-tech to check your "licence"
Is it in this forum an .bat file which can do this. It is named " disable updates" and it put a file name "hosts" in this 2 directoies C:\windows and in C:\windows\system32\drivers\etc
Inside this file it writes like this:
127.0.0.1 update.ross-tech.com
I will share this file if you want to pt it manually in that 2 directories befor starting first time an internet sesion after the VCDS instalation.
Good luck

but i have problem... i followed tutorial... i used program vippidfix like in tutorial... it doesnt register any pluged cable... also mprog doesnt register anything pluged...

**bibkare** · 6th February, 2011, 11:07 PM

Originally Posted by beli123

but i have problem... i followed tutorial... i used program vippidfix like in tutorial... it doesnt register any pluged cable... also mprog doesnt register anything pluged...

i replied you, first create drivers with UD fixer ( respect to XOOM) then vidpid fix will be able to recognize your interface

**beli123** · 6th February, 2011, 11:22 PM

Originally Posted by bibkare

i replied you, first create drivers with UD fixer ( respect to XOOM) then vidpid fix will be able to recognize your interface

here are pics of the error

**PEDRO4053** · 7th February, 2011, 12:12 AM

Originally Posted by bibkare

Pedro what the f.u.c.k. you uploaded, those are not full size pictures, reupload then we will talk

Ok Bibkare

**PEDRO4053** · 7th February, 2011, 12:17 AM

Originally Posted by bibkare

Pedro what the f.u.c.k. you uploaded, those are not full size pictures, reupload then we will talk

Ok Bibkare

Another side of the plate.

**coolk0415** · 7th February, 2011, 06:27 AM

Hello everybody!

Who can provide, write, ATMEGA162, flash, eeprom183. version or higher

Or there (VCDS812.4 Edition), registration / activation code to write, ATMEGA162, flash, eeprom ....

I have 908 DUMP, but VCDS908.0 English, translation, difficulties

Thank you! My English is not my strong suit. Sorry!

**coolk0415** · 7th February, 2011, 06:56 AM

Ask you
ATMEGA162 flash + eeprom 183, can activate the Chinese VCDS 908.1 version?

**max4ever** · 7th February, 2011, 09:11 AM

Hi! I have chinese version 908 with FTDI 232BL chip.I write FTDI chip with 908 dump english.Is ok, but after autoscan 2-3 modules show "License is broken" or something also. What should I write, which chips? Only FTDI or must write ATMEGA 162? Or ATF16V8B?

Soory for my bad english!!!!

**bibkare** · 7th February, 2011, 09:20 AM

Originally Posted by beli123

here are pics of the error

you need to provide additional ftdi driver files because xoom's ud fixer only creates 2 files, try this with windows xp

**bibkare** · 7th February, 2011, 09:25 AM

Originally Posted by PEDRO4053

Ok Bibkare

Another side of the plate.

correct me if i am wrong but this interface has no transistors which means that you are lucky, also i couldn't see STC chip so you only should reflash atmega and you are good to go