[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 bosch 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...