golf 5 visteon 95160

**dtip** · 29th October, 2021, 07:19 PM

Anyone can make this mileage higher with good chk? Since caprog visteon tool mostly gives bad chk.
golf 5 2006 year 1K0920862K 95160

old mileage around = 184401
needed new = 243200

please someone with good tool, i have carprog small software myself, thanks

**neksus** · 29th October, 2021, 07:27 PM

Originally Posted by dtip

Anyone can make this mileage higher with good chk? Since caprog visteon tool mostly gives bad chk.
golf 5 2006 year 1K0920862K 95160

old mileage around = 184401
needed new = 243200

please someone with good tool, i have carprog small software myself, thanks

Here ..............

**dtip** · 29th October, 2021, 08:48 PM

thanks i will test on monday

**dtip** · 30th October, 2021, 11:56 AM

Got error with this, i think there is no chk calculated, anyone can check please?

**H2Deetoo** · 30th October, 2021, 12:28 PM

Here is the full immo from this cluster:
VIN: WVWZZZ1KZ6W126586
IMMOID: VWZBZ0E0269769
CS: E68445D849427F
PIN: 01204
MAC: DD190EC6
PC: FE
KEY1: A9C51B8A
KEY2: D96535D8

**H2Deetoo** · 30th October, 2021, 12:30 PM

And here is the dump with your new mileage.
Try it and report!

Rgs H2Deetoo

**H2Deetoo** · 30th October, 2021, 12:31 PM

Please note that although Codecard tools report a checksum error this wont cause a problem and will be corrected by the cluster.
It all depends on which checksum is not corrected.
But the file from neksus isn't correct though!

Rgs H2Deetoo

**dtip** · 30th October, 2021, 03:17 PM

As i said i also , like most of us, have that tool you did mileage correction and immo data... so it was unnecessary. It is bad chksumed or i am doing something wrong becouse i flash it over obd....

1.jpg

edit: i just realised that i did not try to remove battery i am not sure is it needed after correction?

**H2Deetoo** · 31st October, 2021, 09:12 AM

No you dont have that tool, look good, the Codecard tool wont show PC+MAC.
The file I uploaded has valid checksums, check it and try it.

**Dave Knapp** · 31st October, 2021, 10:21 AM

hallo you are very very good please how did you do this some guys just now how to but please show this guy haha

**H2Deetoo** · 1st November, 2021, 03:27 PM

FYI after writing eeprom by OBD no manual reset or battery disconnect is needed.

**dtip** · 4th November, 2021, 09:27 PM

I finally got this @!it done. When i got to the car firstly i tried H2Deeto file which is same as codecard visteon 95160 2.4 tool and got error on dash. Flashed back ori and all ok.

I realised that on every eep reading when turning ignition on/off i get different few bytes in dump, i guess it is clock or something like that i am not sure and i don't know if it is coverd by chk. But what i tried is reading and not switching ignition off, changing file with codecard visteon tool and flashing it back, and it worked!

**H2Deetoo** · 5th November, 2021, 07:38 AM

Ok, seems you are correct about this.

The Codecard tool always changes the 16byte checksum on address 124h. The is often the wrong address for most 95160 layouts, however your cluster *does* seem to have this particular layout.
So you are right to see that I create exactly the same result file as the Codecard tool in this case.

But that still doesnt make sense that if you write it you get an error.
Ok, every read produces a different result (indeed some timer values or changing vars) but you should be able to write any "correct" eeprom from previous reads.
What tool do you use to read/write your eeproms?

I can confirm that all checksums are correct, all changes are covered by checks.
I see no reason why my file should create an error.
Can you post your final working file here so I can check it?

Rgs H2Deetoo

**dtip** · 5th November, 2021, 03:15 PM

yes sure, this is what read and mod...

i used old quality fvdi clone 2014 from fly

**H2Deetoo** · 5th November, 2021, 03:49 PM

Thank you for the file, it is appreciated!

The first 16 bytes store the plain mileage value and a simple checksum, 2 times.

If you compare tmy file and your sat5mod fine you will see that only the byte on address 101h is different (which was already different in the source sat5 file you read).
Then the next change is a small checksum at 37Fh, to account for the change at 101h.
(And these 2 different bytes are repeated again at 4E9h and 767h.)

I have no idea what the byte at 101h means, nothing particular to immo.
But if it changes every now and then, then it is some timer or counter or so.

So as you can see the file I made should be fine as well, only that byte at 101h is different which is simply so because you read it like that.
Now I have a feeling that maybe the problem you have happens when you write a new eeprom?
Maybe some small bug or issue which causes a corrupt write or so?

What I'm saying is maybe you need to write the eeprom a couple of times with your fvdi until you have a success?
Do you still have that cluster and are you willing to do some tests writing my eeprom a couple of times and see if it will work at some point?
Also here is a new file with 243400km for testing purposes as well.

Thank you,
H2Deetoo