is there a good DIY out there for using Vag EEPROM 1.19 to retrieve SKC's

[Luxus Panzer]

I played with it a bit today coupled using a Chinese ODB2 cable and was able to read my encrypted eeprom...but from there I was lost and threw in the towel.

[hightime80]

Hollar at Cschuster. He is the man with vag eeprom programer. It was thanks to him I made my s4 cluster work.

[Luxus Panzer]

Hollar at Cschuster. He is the man with vag eeprom programer. It was thanks to him I made my s4 cluster work.

Thanks. I will try to find him/her

[eljay]

Here you go®.

[cschuster]

Link

This has everything you need. There is also a fresh color cluster backup file there in case you manage to damage yours.

[Luxus Panzer]

Link

This has everything you need. There is also a fresh color cluster backup file there in case you manage to damage yours.

Thanks.

In your "how to", where did you get 01412 (1412) from??

[cschuster]

Sorry, ignore that...its probably my skc. Must have been a brain fart when putting that together.

Sent from my LG-H830 using Tapatalk

[cschuster]

Or that's the skc of the backup file in the folder

Sent from my LG-H830 using Tapatalk

[Luxus Panzer]

Or that's the skc of the backup file in the folder

Sent from my LG-H830 using Tapatalk

Seen.

I am trying to get a good write up covering 2 things....

1st... how to retrieve the SKC with this program.

2nd... How to retrieve the SKC from a donor cluster with this program. (I imagine it is the same process, one just swaps the donor cluster in first.)

[EuroxS4]

SKC is cake if you have the right tools.The backup file is nice but may not work for every cluster.If you damage the encrypted data you will need some expensive tools to repair the cluster.Your best bet is to make a decrypted backup.You can flash a decrypted backup to a cluster.If you flash a encrypted dump to a cluster you will need a new cluster or expensive repair.Sent from my iPhone using Tapatalk

[cschuster]

Seen.

I am trying to get a good write up covering 2 things....

1st... how to retrieve the SKC with this program.

2nd... How to retrieve the SKC from a donor cluster with this program. (I imagine it is the same process, one just swaps the donor cluster in first.)

The link that eljay posted has the whole process in it. To quickly answer your questions....

1) With original cluster in, set to newmode. Then read eeprom (decrypted). A 4 digit number appears in the "Immobilizer" box. Put a 0 in front for your whole 5 digit SKC. Ex: 1111 in box, 01111 is SKC

2) With donor cluster installed, same process as above.

There are 2 ways to adapt, I only covered one in the linked post. The other way is to go into new mode on new cluster, set miles to 0, then leave it in new mode. Adapt with Ross Tech procedure.

[diagnosticator]

How is "New Mode" set?

[cschuster]

How is "New Mode" set?

Through the RB4 dropdown list. There's an option for "set new mode". When the mileage is set to 0 and left in new mode, the cluster is virgin and can be adapted to with VCDS without the SKC of the donor cluster.

Sent from my LG-H830 using Tapatalk

[Luxus Panzer]

Through the RB4 dropdown list. There's an option for "set new mode". When the mileage is set to 0 and left in new mode, the cluster is virgin and can be adapted to with VCDS without the SKC of the donor cluster.

Sent from my LG-H830 using Tapatalk

WOW!

So one can plug in a cluster from a wreckers that they do not know the SKC for, use the RB4 dropdown list and "set new mode" , then install in their car using VCDS?

EDIT, sorry this was already addressed in this post. Answer = YES

[cschuster]

WOW!

So one can plug in a cluster from a wreckers that they do not know the SKC for, use the RB4 dropdown list and "set new mode" , then install in their car using VCDS?

EDIT, sorry this was already addressed in this post. Answer = YES

Correct. The linked post explains it pretty well if reviewing the ross tech procedure on their website at the same time.

With eeprom programmer, it doesn't matter where the donor cluster comes from. You have to set it to virgin anyways, so reading its SKC is just a click away.

You can also change your mileage to whatever you want, not that I'm condoning that in any way.

[Luxus Panzer]

You can also change your mileage to whatever you want, not that I'm condoning that in any way.

I thought the ECU and cluster had to agree on mileage, thus changing it on the cluster would not jive with the ECU and cause problems.

[cschuster]

I thought the ECU and cluster had to agree on mileage, thus changing it on the cluster would not jive with the ECU and cause problems.

Not sure how that works. What I can tell you is that I changed my mileage a bunch of times. From a few thousand miles to above what is really on the car, and then some in between until leaving it at the real mileage. It ran as normal.

[Matt Devo]

I thought the ECU and cluster had to agree on mileage, thus changing it on the cluster would not jive with the ECU and cause problems.

the ECU has no knowledge/concern of the mileage, that's exclusively the domain of the cluster

[Luxus Panzer]

the ECU has no knowledge/concern of the mileage, that's exclusively the domain of the cluster

Roger.

[Luxus Panzer]

I am attempting to put together a good DIY for all things VAG EEPROM so it is all in one place.

I will have a few questions along the way.... here is the 1st 2 questions.......



1: Read encrypted cluster .bin file. Save file for backup. Label all .bins so you know what they are.

***If you somehow manage to brick the original cluster, put it in mode 6 (adapted) and write the backup encrypted file to it. It should go back to functioning normally. If it does not write the first time, try a few more times. Start over again.***

QUESTION – when you read then save the encrypted .bin file, is it still encrypted and able to be written directly to a “bricked cluster?2: Put in mode 4 (virgin/new).

3: Read decrypted .bin. At the bottom it will display a 4 digit number (ex. 1111). Put a 0 in front of it, and this is your SKC (ex. 01111). This number will be adapted to the new cluster so it matches the ECU. Write it down. You are now done with the original cluster.

QUESTION – when cluster is put in Mode 4 (virgin) the .bin file automatically becomes decrypted?

[cschuster]

1) Yes. When in mode 6 (adapted) you can only read and write encrypted files. When in mode 4 (virgin/new), you can only read and write decrypted files.

2) Yes. I'm no software engineer, but selecting mode 4 must decrypt the eeprom so it can be modified.

Sent from my LG-H830 using Tapatalk

[Luxus Panzer]

Link

This has everything you need. There is also a fresh color cluster backup file there in case you manage to damage yours.

Is that "how to" .pdf for resurrecting a "bricked" cluster using the EncrypetdDump.bin file in the same directory?

[cschuster]

Is that "how to" .pdf for resurrecting a "bricked" cluster using the EncrypetdDump.bin file in the same directory?

You can use yours, but if you screw that up too, then there's another backup just in case.

Sent from my LG-H830 using Tapatalk

[EuroxS4]

you cannot write a encrypted file to bricked cluster it will only make things worse.Your supposed to set to new mode and back up decrypted dump of cluster.If cluster is for any reason bricked you can write a decrypted file to it.This is mostly because you cannot make changes to the cluster while its in encrypted immobilizer status mode 6.So I dont see how you would be able to reflash in mode 6.Its just not possible.No changes can be made in mode 6.

[Luxus Panzer]

Sorry all. I got a bit distracted by life. Now back to creating a VAG EEPROM DIY article.

So far I have 5 things I would like to cover in the DIY...
1. Retrieve a SKC from cluster.

2. Set cluster to “new mode”

3. Save a decrypted .bin file for backup purposes.

4. Use decrypted .bin file to recover a “bricked” cluster

5. Adapt cluster to car

Here is what I have so far........




1. Retrieve a SKC from cluster.



2. Set cluster to “new mode”



3. Save a decrypted .bin file for backup purposes.



4. Use decrypted .bin file to recover a “bricked” cluster.

1. Open .bin file. Write EEprom (Encrypted). Hopefully this clears the error and you can continue.
2. Set Newmode. In this mode, you can read SKC if you Read EEprom (Decrypted).
3. Convert current mileage into kilometers. Enter in lower right box.
4. Set Kilometer.
5. Set Back to Adapted Again.
6. Go through VCDS to adapt. SKC for new cluster is 0XXXX.








5. Adapt cluster to car (ROSS TECH / VAG COM NEEDED FOR THIS TASK)

In VCDS, go into engine and write down IMMO ID. Go into instruments and do the same thing. Numbers will match. Ross tech explains this well.

Original Cluster
1: Open Vag EEPROM Programmer. For future steps, always use the RB4 dropdown list (tabs at top) instead of the buttons. I don't know if they change depending on what mode the cluster is in.

1: Read encrypted cluster .bin file. Save file for backup. Label all .bins so you know what they are.

***If you somehow manage to brick the original cluster, put it in mode 6 (adapted) and write the backup encrypted file to it. It should go back to functioning normally. If it does not write the first time, try a few more times. Start over again.***

QUESTION – when you read then save the encrypted .bin file, is it still encrypted and able to be written directly to a “bricked cluster?

ANSWER (from Audizine user CHCHUSTER) Yes. When in mode 6 (adapted) you can only read and write encrypted files. When in mode 4 (virgin/new), you can only read and write decrypted files.


2: Put in mode 4 (virgin/new).

3: Read decrypted .bin. At the bottom it will display a 4 digit number (ex. 1111). Put a 0 in front of it, and this is your SKC (ex. 01111). This number will be adapted to the new cluster so it matches the ECU. Write it down. You are now done with the original cluster.

QUESTION – when cluster is put in Mode 4 (virgin) the .bin file automatically becomes decrypted?

ANSWER (from Audizine user CHCHUSTER) Yes. I'm no software engineer, but selecting mode 4 must decrypt the eeprom so it can be modified.

New Cluster
1: Disconnect battery, install.
2: Read encrypted .bin. Save as backup.
3: Put in mode 4 (virgin/new).
4: Read decrypted .bin. Write down SKC, using same method as above. For this example, we will use 02222.
5: Convert current mileage to km, enter it into the box in the lower right. Using the RB4 drop down menu, click Set Kilometers. Mileage is now set. If you are using km, obviously no conversion is needed.
6: Put back into mode 6. (Note: I first tried using virgin mode to adapt, but wasn't clear on the rest of the process and messed up. You can adapt using VCDS if you have both SKC's anyways)
7: Exit Vag EEPROM Programmer. Open VCDS. Ross Tech has an instruction and video on how to do this as well. This is just summarized from them.

8: Login to instruments using new cluster SKC (02222). Cluster is not adapted yet and still uses its own SKC.

9: Go to adapt. Read channel 50. Value should be 32000. In the test box, enter original SKC (01111). Click test, then save. Close controller, remove key from ignition for 1 min.

10: Turn key back on. Check IMMO ID of cluster and ECU. Both should match now. You will also see the new cluster's VIN to the right of the IMMO ID. If not, figure out where you went wrong.
***If you mess up bad enough to brick the cluster, simply put it back in mode 6 and write your new cluster encrypted backup .bin to it. Start over at step 1.***

11: Login to instruments using original SKC (01111). This will work now because the new cluster's SKC has been changed to the original SKC.

12: Follow Ross Tech's instructions to reprogram keys (see below). Check instrument soft coding to make sure it is correct for your car.

13. Start car. My traction control and seatbelt lights were on, but turned off after a min. You may also have to enter the radio code to get it out of safe mode. Boom, enjoy!






Can you guys help me fill in the blanks. I do not have a spare cluster to mess around with.

[EuroxS4]

I dont think you can write a encrypted dump to a cluster.It will only damage the cluster further.Cluster needs to be in mode 4 to make changes and write new dump to cluster.

[cschuster]

I brought back my old cluster from being bricked in mode 6 with the encrypted file while playing around.

Sent from my LG-H830 using Tapatalk

[Luxus Panzer]

Does anyone have a spare cluster to play around with and grab some screen shots to fill in the blanks in the document above?

[Luxus Panzer]

Lookie what I got ;) A spare cluster.

I have a super busy next few weeks, but I am going to play around when I find time and attempt to update this thread and eventually Finnish this how-to.

[Luxus Panzer]

Ok. I think I have it all figured out. No where near as confusing as it feels when you first dive in.

Here is my "cheat sheet" I made for myself, including all my dumb questions I asked...just in case someone has the same questions.


1. Retrieve a SKC from cluster.

- Open Vag EEPROM Programmer. For future steps, always use the RB4 dropdown list instead of the buttons. I don't know if they change depending on what mode the cluster is in.
- Read encrypted cluster .bin file. Save file for backup. Label all .bins so you know what they are.
***If you somehow manage to brick the original cluster, put it in mode 6 (adapted) and write the backup encrypted file to it. It should go back to functioning normally. If it does not write the first time, try a few more times. Start over again.***
- Put in mode 4 (virgin/new).
- Read decrypted .bin. At the bottom it will display a 4 digit number (ex. 1111). Put a 0 in front of it, and this is your SKC (ex. 01111). This number will be adapted to the new cluster so it matches the ECU. Write it down. You are now done with the original cluster.
If keeping this cluster in car, put back in mode 6 (adapted)

(confirmed works. Will throw a bunch of communication codes, use Vag Com to clear them.)




2. Set cluster to “new mode”

This is done via the RB4 drop down menu in Vag EEPROM 1.19

3. Save a decrypted .bin file for backup purposes.

This is done via the RB4 drop down menu in Vag EEPROM 1.19


4. Use decrypted .bin file to recover a “bricked” cluster.

1. Open .bin file. Write EEprom (Encrypted). Hopefully this clears the error and you can continue.
2. Set Newmode. In this mode, you can read SKC if you Read EEprom (Decrypted).
3. Convert current mileage into kilometers. Enter in lower right box.
4. Set Kilometer.
5. Set Back to Adapted Again.
6. Go through VCDS to adapt. SKC for new cluster is 0XXXX.








5. Adapt cluster to car (ROSS TECH / VAG COM NEEDED FOR THIS TASK)

In VCDS, go into engine and write down IMMO ID. Go into instruments and do the same thing. Numbers will match. Ross tech explains this well.

Original Cluster
1: Open Vag EEPROM Programmer. For future steps, always use the RB4 dropdown list (tabs at top) instead of the buttons. I don't know if they change depending on what mode the cluster is in.

1: Read encrypted cluster .bin file. Save file for backup. Label all .bins so you know what they are.

***If you somehow manage to brick the original cluster, put it in mode 6 (adapted) and write the backup encrypted file to it. It should go back to functioning normally. If it does not write the first time, try a few more times. Start over again.***

QUESTION – when you read then save the encrypted .bin file, is it still encrypted and able to be written directly to a “bricked cluster?

ANSWER (from Audizine user CHCHUSTER) Yes. When in mode 6 (adapted) you can only read and write encrypted files. When in mode 4 (virgin/new), you can only read and write decrypted files.


2: Put in mode 4 (virgin/new).

3: Read decrypted .bin. At the bottom it will display a 4 digit number (ex. 1111). Put a 0 in front of it, and this is your SKC (ex. 01111). This number will be adapted to the new cluster so it matches the ECU. Write it down. You are now done with the original cluster.

QUESTION – when cluster is put in Mode 4 (virgin) the .bin file automatically becomes decrypted?

ANSWER (from Audizine user CHCHUSTER) Yes. I'm no software engineer, but selecting mode 4 must decrypt the eeprom so it can be modified.

New Cluster
1: Disconnect battery, install.
2: Read encrypted .bin. Save as backup.
3: Put in mode 4 (virgin/new).
4: Read decrypted .bin. Write down SKC, using same method as above. For this example, we will use 02222.
5: Convert current mileage to km, enter it into the box in the lower right. Using the RB4 drop down menu, click Set Kilometers. Mileage is now set. If you are using km, obviously no conversion is needed.
6: Put back into mode 6. (Note: I first tried using virgin mode to adapt, but wasn't clear on the rest of the process and messed up. You can adapt using VCDS if you have both SKC's anyways)
7: Exit Vag EEPROM Programmer. Open VCDS. Ross Tech has an instruction and video on how to do this as well. This is just summarized from them.

8: Login to instruments using new cluster SKC (02222). Cluster is not adapted yet and still uses its own SKC.

9: Go to adapt. Read channel 50. Value should be 32000. In the test box, enter original SKC (01111). Click test, then save. Close controller, remove key from ignition for 1 min.

10: Turn key back on. Check IMMO ID of cluster and ECU. Both should match now. You will also see the new cluster's VIN to the right of the IMMO ID. If not, figure out where you went wrong.
***If you mess up bad enough to brick the cluster, simply put it back in mode 6 and write your new cluster encrypted backup .bin to it. Start over at step 1.***

11: Login to instruments using original SKC (01111). This will work now because the new cluster's SKC has been changed to the original SKC.

12: Follow Ross Tech's instructions to reprogram keys (see below). Check instrument soft coding to make sure it is correct for your car.

13. Start car. My traction control and seatbelt lights were on, but turned off after a min. You may also have to enter the radio code to get it out of safe mode. Boom, enjoy!




Immobilizer III Key Matching (Cluster)
This procedure details how to match new keys to VW/Audi/Seat/Skoda vehicles with with Immobilizer III, where the immobilizer control module is integrated in the instrument cluster. See the seperate instructions for models where the immobilizer control module is integrated in a separate immo box or where the immobilizer control module is integrated in kessy (Keyless Entry and Start SYstem).


Determining IMMO-ID & VIN
[Select]
[17 - Instruments]
Look at the first "Extra" field. The first 17-digit string is the VIN. The second 14-digit string in the Immo-ID.
[Close Controller, Go Back - 06]
---OR---
[Select]
[17-Instruments]
[Meas.Blocks-08]
Select.Block-081.
[Go!]
The.first.17-digit.string.is.the.VIN..The.second.14-digit.string.is.theImmo-ID..
[Done,Go.Back]
[Close Controller, Go Back - 06]

Key Matching
Prerequisites:
 All keys are either new or were adapted to this car (IMMO-ID) before.
 You can match up to 8 keys.
 While adapting each key, make sure to place the other keys away from the ignition lock (reader coil). The passenger seat is an adequate place.
 Battery voltage at least 12.5 V.

[Select]
[17-Instruments]
[Meas.Blocks-08]
Select.Block.022.
[Go!]
The.value.in.field.3.must.be.1.__If.value.is.not.1 ,the.key.is.not.capable.of.being.adapted.to.Immobi lizer.
You can check each key in this manner.

Select.Block.024.
[Go!]
Make sure the shown lock times in field 1, 2 and 3 are 0 (each field represents a time in minutes).
 If the lock times are NOT 0:
 Do NOT switch off the ignition!
 Allow the car to sit for AT LEAST the number of minutes that were indicated by the fields 1-3.
[Done, Go Back]

[Login - 11]
 4-digit PIN
 Enter zero followed by the 4-digit PIN. For example, if your PIN is 1234, enter 01234.
[Do it!]
[Adaptation-10]
Enter.21.in."Channel.Number".
[Read]
The."Stored.Value".is.the.number.of.keys.currently .matched.
Enter a "new value" corresponding to the total number of keys to be matched, including any existing keys.
Any old keys are automatically being cleared. All keys, including existing keys, must be matched at the same time.
[Save]
[Done,Go.Back]
[Close Controller, Go Back - 06]
 Repeat the following steps until all Keys have been matched:
 Switch Ignition OFF and remove Key.
 Insert the next Key and switch Ignition ON.
 The Immobilizer Warning Light will light up for ~2 seconds, wait until it goes out, indicating that the key has been matched.
Note: The above steps must be completed within 60 seconds after saving the Adaptation!
Video Link
Immobilizer Gen 2 and 3 Key Adaptation

http://www.youtube.com/watch?v=Wj3K04eMV7w

[Osher67]

Don't really want to start a new thread I maybe stupid but I keep trying to open EePROM and it says cannot open codes.dat on Windows 7 not too sure how to get it to open ? Do I need my cable hooked up?

[Luxus Panzer]

Don't really want to start a new thread I maybe stupid but I keep trying to open EePROM and it says cannot open codes.dat on Windows 7 not too sure how to get it to open ? Do I need my cable hooked up?

If you are using Vag EEPROM, then I would start by hooking up the cable.

[AudiNike12]

Bumping this. I'm getting "No ECU found" when I'm trying to connect. Am I doing something wrong? I'm using Win7 64bit

Edit: I don't think I've the right cable. I've a VCDS clone. Also, does it work on Audi A6 C5?

[Luxus Panzer]

Bumping this. I'm getting "No ECU found" when I'm trying to connect. Am I doing something wrong? I'm using Win7 64bit

Edit: I don't think I've the right cable. I've a VCDS clone. Also, does it work on Audi A6 C5?

This is for a B6 A4. No clue about a C6 A5...but my GUESS is no.

[ApexIt]

Bumping this. I'm getting "No ECU found" when I'm trying to connect. Am I doing something wrong? I'm using Win7 64bit

Edit: I don't think I've the right cable. I've a VCDS clone. Also, does it work on Audi A6 C5?

Do you have VCDS installed on your computer? The EEPROM should still work with a generic, non-VCDS cable but you need to either edit the port settings or uncheck a box within the VCDS software. From the DIY linked above:

For those that are using the Genuine Ross-tech cables with VAG EEPROM Programmer to access their clusters and are running into problems connecting to the ECU, try this:

In the Ross-tech software, in the connection settings, there is a box that is likely checked called 'Start up in Intelligent mode' or something to that effect. Uncheck that, test the connection settings and save them. Now open VAG EEPROM Programmer, attempt to connect to the Cluster (encrypted) and it should work.

I was constantly getting the error that it could not find the ECU until I changed these settings.

When you go back to VCDS, you can re-check the box.

If you're doing an S4 cluster swap, make sure to read all posts in that thread. They helped me immensely when I did mine.

[AudiNike12]

Do you have VCDS installed on your computer? The EEPROM should still work with a generic, non-VCDS cable but you need to either edit the port settings or uncheck a box within the VCDS software. From the DIY linked above:



If you're doing an S4 cluster swap, make sure to read all posts in that thread. They helped me immensely when I did mine.

I've VCDS on my computer but it's not genuine. It's a clone/aftermarket but not VCDS-lite either. It's not through a COM-port, it's USB. So I don't know if I have that box to check in VCDS but I'll take a look. Thanks :)

Edit: I do have that box. I'm gonna uncheck it and see what happens

[ApexIt]

I've VCDS on my computer but it's not genuine. It's a clone/aftermarket but not VCDS-lite either. It's not through a COM-port, it's USB. So I don't know if I have that box to check in VCDS but I'll take a look. Thanks :)

Edit: I do have that box. I'm gonna uncheck it and see what happens

Hopefully that fixes it for you. Just an FYI, each USB port is assigned a COM port number. You can edit the settings for each of these in the device manager. So if unchecking that box doesnt work for you, take a look at the settings for these.

[AudiNike12]

Hopefully that fixes it for you. Just an FYI, each USB port is assigned a COM port number. You can edit the settings for each of these in the device manager. So if unchecking that box doesnt work for you, take a look at the settings for these.

It didn't work and I don't have any COM-ports in the device manager. I've tried other software aswell. Like VagDashCan and VagDashCom. Couldn't find the interface. So I think it's the cable. What cable works with EEPROM?

[DPDISXR4Ti]

What cable works with EEPROM?

My plan is to use a 409.1 silver cable w/ blue connector purchased a couple months ago on eBay. Backup plan is to use VCDS HEX+CAN cable in "dumb" mode. I'll update this thread with results soon (I hope!).

[Luxus Panzer]

My plan is to use a 409.1 silver cable w/ blue connector purchased a couple months ago on eBay. Backup plan is to use VCDS HEX+CAN cable in "dumb" mode. I'll update this thread with results soon (I hope!).

I had problems with putting my genuine vag com in "dumb" mode, so I use my 10$ eBay cable for SKC extraction and my vag com for FOB programming