[laso]

But how do you know if it is mode 1 or 2? And is this valid only for the 128 chips or for 35160WT as well?

MODE_1 and / or MODE_2 is only for the M35128 EEPROM types important because they have different memory addresses.

• MODE_1: Odometer information stored only in the first 32 bytes (0x00h - 0x1Fh)
  
• MODE_2: Odometer information not (only) in the first 32 bytes.
  

Do you know the location of MODE_2? My case shows that not always the first 32bit must be FF FF.

[Spitfire555]

Do you know the location of MODE_2?  My case shows that not always the first 32bit must be FF FF.

Odometer info in MODE_2 is located from 0x40h - 0xBBh.

For my understanding the address 0x00h - 0x1Fh should be all "00h", but there are people who has (different) values in this area.

[Matthew53]

Does anyone know if Yanhua 35128 emulator works also on G serie B05cн cluster or only VDO?

[kaiserstumm]

Hello, i am a new VVDI prog user, bought the device yesterday. I am trying to retrofit ID7 to a bmw g11. The cluster had 35128WT. I read out the e2p under special_function m35160xx (memory, long ID, long ID location).
A collegue edited in NeoX the mileage from memory and i have written back the edited memory, orig Long ID and orig ID location to a new Xhorse 35160 chip. Now i need to swap and code the cluster. Will the original milleage from the car come back if i dont use a can filter or i can leave it like this.
PS I know CG PRO also can encrypt the milleage beside NEoX. Are there any other programs able to do that (perhaps some cheaper tools)
BR

[bm92]

You can't select 35160XX to read 35128WT, no the same size...

[DrifterX]

Thank you.

Unfortunately it was impossible to write the new dump:
In mode 1, I have immediately the error message: Mileage more than 800.000km is not supported
In mode 2, the process takes about 20 minutes for calculations, then I have: write failed

Except BMW Explorer, no available other solution for the chip 128WT ?

Hello, sorry to revive an old thread here - I'm a BMW owner who likes to tinker with his own car and am seeking some advice (while I wait for CGDI customer 5ёяvїcё)

I have a similar problem on my F30 6WB cluster with 35160WT... the first mileage erase/write attempt with CG Pro рдятially wrote in 00 01 in first two lines. So I attempted to erase/write again but the process failed again and it wrote in bad data and now CG Pro software detects the chip to have over 800,000km (only 0x1Eh - 0x1Fh has this high value). Did you solve the mileage issue with the first two lines on your chip with CG Pro or did you have to use another solution?