[Spitfire555]

So no solution for this cluster ? Dead ?

That's the sad truth. Nevertheless, you have three options:

1. Live with red dot and fault entry on instrument cluster
   
2. Use a 35160DWT from VVDI
   
3. Use modified software for instrument cluster from BMW Explorer in conjunction with a new 35160WT
   

[smilo]

So no solution for this cluster ? Dead ?

That's the sad truth. Nevertheless, you have three options:

1. Live with red dot and fault entry on instrument cluster
   
2. Use a 35160DWT from VVDI
   
3. Use modified software for instrument cluster from BMW Explorer in conjunction with a new 35160WT
   

Thanks !
“ Use a 35160DWT from VVDI” it will need original 35160WT ID - That I can’t read unfortunately, due to EEPROM Damaged using CG Pro…
Do you confirm ?
BMW Explorer, the solution is reliable ? No ISTA error or communication fail with other ECU ?

I need BMW Explorer or VVDI in any way

[Jartsa]

Is there more info about the bmw explorer solution?

[larshutten]

@smilo only solution I think is explorer check id off.

Their website gives all the info you need. Since it’s been a while 6wb got update I would say save to use .

[foxportal]

@SMILO
The solution with the explorer is working !!!
PS description taken from the site:

Many have come across a situation when a red dot lights up on the dashboard when replacing the Eeprom 35160.
Previously, the only solution was to install an Eeprom emulator, which very often fail, or work very clumsily.
From version 21.08.28 Bmw-explorer has the ability to disable ID Eeprom check in BMW F series panels.

1.Replace the EEprom in the instrument cluster.
2. Go to the dashboard, then to additional options and click the "Erase ID Eeprom" button.
3. Further, if the program asks to connect the ENET adapter, connect it.
4. Program the instrument cluster.
5. Code if necessary.

The red dot will go out. But if you program the instrument cluster with the original firmware, then you will see a burning dot on the instrument cluster again.

[Fatalix]

Uploaded 95320rt and 35160wt readout with hextag.
Looks fine to me, VIN is 0C50471 and entered 2 times in 35160 and once in 95320rt. Anybody confirm?

[chang2]

Is there more info about the bmw explorer solution?

hello,

bmw-explorer works fine.

[andriusx]

So no solution for this cluster ? Dead ?

That's the sad truth. Nevertheless, you have three options:

1. Live with red dot and fault entry on instrument cluster
   
2. Use a 35160DWT from VVDI
   
3. Use modified software for instrument cluster from BMW Explorer in conjunction with a new 35160WT
   

Thanks !
“ Use a 35160DWT from VVDI” it will need original 35160WT ID - That I can’t read unfortunately, due to EEPROM Damaged using CG Pro…
Do you confirm ?
BMW Explorer, the solution is reliable ? No ISTA error or communication fail with other ECU ?

I need BMW Explorer or VVDI in any way

Post your bin file I will check if it contains eeprom id

[Fatalix]

So no solution for this cluster ? Dead ?

That's the sad truth. Nevertheless, you have three options:

1. Live with red dot and fault entry on instrument cluster
   
2. Use a 35160DWT from VVDI
   
3. Use modified software for instrument cluster from BMW Explorer in conjunction with a new 35160WT
   

Thanks !
“ Use a 35160DWT from VVDI” it will need original 35160WT ID - That I can’t read unfortunately, due to EEPROM Damaged using CG Pro…
Do you confirm ?
BMW Explorer, the solution is reliable ? No ISTA error or communication fail with other ECU ?

I need BMW Explorer or VVDI in any way

Post your bin file I will check if it contains eeprom id

Can you check mine also? Microtronik says it is not possible to use hextag for 35160 read write as file is too small? It might corrupt the data if i try upload they say. 
Some say it works fine though?

[andriusx]

So no solution for this cluster ? Dead ?

That's the sad truth. Nevertheless, you have three options:

1. Live with red dot and fault entry on instrument cluster
   
2. Use a 35160DWT from VVDI
   
3. Use modified software for instrument cluster from BMW Explorer in conjunction with a new 35160WT
   

Thanks !
“ Use a 35160DWT from VVDI” it will need original 35160WT ID - That I can’t read unfortunately, due to EEPROM Damaged using CG Pro…
Do you confirm ?
BMW Explorer, the solution is reliable ? No ISTA error or communication fail with other ECU ?

I need BMW Explorer or VVDI in any way

Post your bin file I will check if it contains eeprom id

Can you check mine also? Microtronik says it is not possible to use hextag for 35160 read write as file is too small? It might corrupt the data if i try upload they say. 
Some say it works fine though?

Yes just checked your 35160WT is full read apart from eeprom id, vins are in 01D0 line and 0F60. Your 95320 eeprom is full read and vin is in 0790 so you can FF vins and write them back using same options and you will be fine