VAG-COM/VCDS EVERYTHING

**flyfvdi** · 23rd January, 2021, 05:05 AM

There are two copy vcds hex-v2. one is good , another is bad.

Fake 405-2.jpg

True 405-1.jpg

**cebbes30** · 23rd January, 2021, 01:28 PM

Can anyone tell me if the clone hex v2 offered here by fly or others also works on a vw golf 8.

Can someone confirm this with a vcds scan

**badrax** · 23rd January, 2021, 01:49 PM

Originally Posted by flyfvdi

There are two copy vcds hex-v2. one is good , another is bad.

Fake 405-2.jpg

True 405-1.jpg

Yes. That's what I been trying to say all the time.
Finally we agree on something

But the one you call "not good" also support upgrades just like the 415!

**badrax** · 23rd January, 2021, 02:48 PM

Hi
Some update on my work on upgrading the 415

I have made a new "firmware" / code to dump the whole 415 chip so that we can see what version of the bootloader is installed.
This is coz I see that there are different version of it from feedback I have received from some forum test users.

The bootloader I have on my 415 is verifying some code at address 0x08040000 and when crc8 is verified it reads the reset vector from it and jumps to this address. This code at 0x08040000 is actually a unmodified (or I believe this) firmware that contains the correct checksum and it's base address is actually 0x08010000. Now at this address 0x08010000 is a patched version of the firmware but it is using the same reset vector so when the bootloader jumps to it then all is good. My firmware is also patched to read the UID (AES encryption key) from the bootloader section which makes my firmware and bootloader compatible with each other (Use a common key).
My patched firmware at 0x08010000 also calls a function at address 0x08060000 just to receive the base address used to set the VTOR register in the 415.

So we have these four things that need checking:

1. Firmware code verifier
2. Reset vector to jump to
3. What UID to use
4. Get VTOR address

From forum testers I have seen changes on 1, 3, 4. Until I see some other bootloaders I cant tell if 2 also is different.

My firmware dumper could potentially handle all four of these tests but number 1 might require brute forcing if crc8 is different then mine.

So as you can see. This is not strait forward and for all of you asking to test "upgrading" please be aware that flashing could brick your cable and make it unusable.
And when I say "upgrading" that is to flash my dumper code or to flash the 4508 firmware only available atm.

(Still reading? Good

)
Dumper code. (For you that are willing to do testing and to brick your cable)

My dumper code behaves like a new firmware and when started by the bootloader it converts the cable into a USB mass storage device for you to access from your OS. You will see that one of your cables LED turns solid white and you will also see a new drive letter with the name FLASH.
On this device there will exist two files:
"extra.bin" which is the OTP area (One Time Programmable)
"flash.bin" which is the whole flash memory of 1 meg.
It will stay this way for 2 min and after this you will see the LED blinking yellow for 10 sec for so to start the bootloader again and wait for a new firmware upgrade.
If you run out of time then just disconnect and connect your cable again and you will have 2 more min.

Copy these files or make a zip container for so to send to me
Your cable will now stay like this until you receive a new firmware from me after I have looked at the bootloader.

regards

**Ganja47** · 24th January, 2021, 10:59 AM

Dumped and sent to you.
Thanks for all the hard work you are putting into this, much appreciated

**badrax** · 24th January, 2021, 02:00 PM

Originally Posted by Ganja47

Dumped and sent to you.
Thanks for all the hard work you are putting into this, much appreciated

Awesome. Thanks for being the first guinea pig

Will send you a firmware you can flash back to so you can use your cable again.

**Ganja47** · 24th January, 2021, 03:08 PM

no worries. worked a treat, cable back to normal if anyone else needed reassurance to participate

**bg17aw** · 24th January, 2021, 05:03 PM

What did I do wrong during installation?

When Windows starts, it seems it is running an update service.

Kolimer loader was of course not running at Windows start-up

**mrben** · 24th January, 2021, 05:35 PM

VCDS is setup on startup, i saw that after instalation vcds set startup command, and probably check for updates...

Sent from my SM-G970F using Tapatalk

**thedemonduck** · 24th January, 2021, 07:03 PM

Post for Download

**szpectronik** · 24th January, 2021, 11:21 PM

there is probably a newer loader than the one provided in the flyfvdi post, please link maybe someone has the file rar password
https://www.chinaobd2.com/service/vc...ownload-7.html
https://mega.nz/file/sHRBRCyK#QXsDcm...BBT67mTUs2Nxyg
VIIPlusLoader-08.021.02-EN-Installer

**crouchinggerbil** · 24th January, 2021, 11:24 PM

Originally Posted by szpectronik

there is probably a newer loader than the one provided in the flyfvdi post, please link maybe someone has the file rar password
https://www.chinaobd2.com/service/vc...ownload-7.html
https://mega.nz/file/sHRBRCyK#QXsDcm...BBT67mTUs2Nxyg
VIIPlusLoader-08.021.02-EN-Installer

https://www.digital-kaos.co.uk/forum...UAL-NO-PASS!!!

**crouchinggerbil** · 24th January, 2021, 11:28 PM

Originally Posted by bg17aw

What did I do wrong during installation?

When Windows starts, it seems it is running an update service.

Kolimer loader was of course not running at Windows start-up

That is because the software is updatable. The loader does not affect updates.