[premium89]

Hello guys,

done many clusters of that type, always went easy.
Yesterday i wrote D160 in VVDI-prog, verified dump after write, soldered back to PCB, attached cluster to car and shows 0km, red dot and no coding possible.
I disassembled cluster again, desoldered D160, tried to read and no read possible, so eeprom dead. Tried to read over 100 times, no luck, always "Chip not connect", even while heating it, then it reads all lines with 00

I wrote org D160 eeprom dump to vvdi 35160 emulator, again 0km, red dot, no coding possible. Then i wrote full 35160wt dump with long ID from other car to emulator with just vin an km changed and then shows good km, but red dot.

How can I get rid of the red dot? Does the D160 also have a longid section? I have a vvdi prog backup of org D160DOWQ read as D160, reading range from 0 - 7FF0 
The 35160 emulator has 4 lines more, where the ID is located.

Any help to make the red dot disappear would help, thank you guys.

[foxportal]

From version 21.08.28 Bmw-explorer has the ability to disable ID Eeprom check in BMW F series panels

[premium89]

Ok, thanks for your help.
But I assume if the car gets one day an update from dealer, the red dot will return.
Is there any other solution? Like generate ID from MCU or clone full backup from other dashboard.

[pepi]

I believe you did not save eeprom ID with vvdi or it was bad reading . I had some cases when I could not write back eeprom , writed saved dump with long ID and everything was OK.
The long ID from other car will not work at your car.
You will have to reflash cluster with ESYS.