[deebow]

Hi
need some help on the virginizing process.. Got a 6wa for a bmw f15 x5, part number 6802332.  
It contains the 160d0wt and the 95320wt chips. I did my normal process of using vvdi to read and then fff out the vin. mileage is higher on the car so i left the original mileage on the chips.
. 
when i fitted the chips back to the clock it showed the mileage as 999999 alongside a red dot. Now i tried using the x horse 35160 chip and that was having the same issue with the mileage and the red dot. I then wrote back the original dump to the 35160 chip and the 95320. Mileage has gone to what it was originally (62k) but the red dot is still there. I've attached my dump(zip file) . is anyone able to have a look at the dump and advise if something looks wrong?


thanks

---

also when i try writing the original dump back to the 160 chip, it fails on the verify check. there is one byte difference. the file titled "d160 CURRENT" is a dump of that. is there a chance that during the first read vvdi didnt read something properly and the dumps have been corrupted

[deebow]

UPDATE

Officially confused with this one. i rewrote the original read to both the d160 and the 95320 and then fitted back to the clock. the mileage showed correct but i still got the red dot error straightaway.

someone else mentioned to try add the vin of the car its going to and see if that works so edited the binx with the new vin and used the x horse 35160 chip instead of the original d160 and the clocks now back to showing red dot and mileage at 99999. Is anyone able to advise where they might think ive gone wrong? currently scratching my head on this

[cipi gutuie]

Have you think that after you blank vin in eeprom and install cluster on need coding??? Or you think that is enough to blank vin and put on car????
After coding cluster will adapt mileage from bdc if bdc is higher or bdc adopt mileage from cluster if cluster have higher mileage
And if your unchangeable byte is in mileage rows meaning the first 2 rows that means this memory is f7cked...

[deebow]

hi that's not the case. i am aware it needs to be coded as i have done the whole process before with success.

Usually once the cluster is virginized, on my bench when i power it up to make sure it works i would see the mileage. in this case im seeeing a red dot and the mileage showing 999999. Once fitted in the car is where the red dot would usually come on for me.

the unchangeable byte issue was on the original chip and thats towards the end. on the x horse chip and the 95320 the read is matching the original chips just with different vin.

[cipi gutuie]

hi that's not the case. i am aware it needs to be coded as i have done the whole process before with success.

Usually once the cluster is virginized, on  my bench when i power it up to make sure it works i would see the mileage. in this case im seeeing a red dot and the mileage showing 999999. Once fitted in the car is where the red dot would usually come on for me. 

the unchangeable byte issue was on the original chip and thats towards the end. on the x horse chip and the 95320 the read is matching the original chips just with different vin.

999999 is there when eeprom memory is not solder good also
and your eeprom files are not loaded here
check what you have upload

[deebow]

if you change the extension to zip it should work. my bad forgot to put that and i will double check the solder.

[cipi gutuie]

if you change the extension to zip it should work. my bad forgot to put that and i will double check the solder.

And do coding on car
If somrthing is wrong coding is not accepted
And reupload files how should be as rar files not text

[deebow]

try this thanks

[cipi gutuie]

try this thanks

try it 

x5mod.rar
File Type:
Downloaded:	6 times
Size:	2.79 KB

write and code with esys
and one more thing....if you change the memory i hope that you transfer id from original to china eeprom memory

[cipi gutuie]

No thanks...no feedback reply