Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]

Solved ✔ 160DOWT cluster issue (F25)
31-10-2023, 12:01 PM,
Post: #1
160DOWT cluster issue (F25)
Hi,
I fitted a used cluster to an X3 because of cruise controll retrofit.
bought a used one with higher milage as car.
changed milage to 17km with CG Pro 9S12.
after mount and coding in the car i get code "0xB7F663 - Instrument panel. Redundant data adopted from partner control unit"
Milage stays always the same. Cluster shows 0000000 for a very quick time after switch ignition an and changes afterwards.

can anybody help please?

Regards Bavarian


31-10-2023, 15:12 PM,
Post: #2
RE: 160DOWT cluster issue (F25)
Post the dump 160wt dump
31-10-2023, 18:29 PM,
Post: #3
RE: 160DOWT cluster issue (F25)
Do you cleared the VIN also in M95320 EEPROM?
31-10-2023, 18:51 PM,
Post: #4
RE: 160DOWT cluster issue (F25)
damaged eep 160D0WT
after reading eep, there will be errors in the first two lines
31-10-2023, 19:03 PM, (This post was last modified: 31-10-2023, 19:13 PM by Bavarian.)
Post: #5
RE: 160DOWT cluster issue (F25)
(31-10-2023, 18:29 PM)Spitfire555 Wrote:  Do you cleared the VIN also in M95320 EEPROM?

The 160DOWT is together with 95080WT.
I only changed the mileage and VIN in 160DOWT

(31-10-2023, 18:51 PM)MaxBmw Wrote:  damaged eep 160D0WT
after reading eep, there will be errors in the first two lines

I have read the 160DOWT and changed mileage first with CG Pro. I have seen that the first two lines in the dump are got changed.
As second step I changed the VIN to FF, wrote it back to EEprom and soldered it back with hot air station (400 degrees).
After mount it back to the car, the mileage went to original KM status from car (31405km) but rot dot stayed on. I coded it with esys, red dot went off and everything looked fine. Before I moved to test drive I cleared the fault codes with ediabas. While driving, the mileage counts up. As soon as ignition is been switched of an on again, mileage showed 000000 for short time and the it jumps back to the mileage as I connected it first to the car (31405km). Fault codes comes up as well.
Removed the eeprom again. Did the dump read and recognised that mileage was messed up. Further, I am not able to write anything back to EEPROM.


01-11-2023, 06:22 AM,
Post: #6
RE: 160DOWT cluster issue (F25)
(31-10-2023, 18:51 PM)MaxBmw Wrote:  damaged eep 160D0WT
after reading eep, there will be errors in the first two lines

Is it possible to replace the chip?


01-11-2023, 10:41 AM,
Post: #7
RE: 160DOWT cluster issue (F25)
as I wrote, you damaged the eep, replace eep with eep Xhorse 35160DW
don't forget LongID
[+] 1 user says Thank You to MaxBmw for this post
01-11-2023, 13:11 PM,
Post: #8
RE: 160DOWT cluster issue (F25)
(01-11-2023, 10:41 AM)MaxBmw Wrote:  as I wrote, you damaged the eep, replace eep with eep Xhorse 35160DW
don't forget LongID

Thanks for your reply. I already ordered 160DOWT eeprom from china. Guess it takes weeks till I get it. I am only equipped with CG pro. Is it possible with this programmer as well? What do you mean with long ID? Thought it is within the dump I already got…


01-11-2023, 13:19 PM, (This post was last modified: 01-11-2023, 13:25 PM by Node.)
Post: #9
RE: 160DOWT cluster issue (F25)
Long ID is a secret number in the special area of a 160DOWT chip. AFAIK it's burnt into the chip in the factory and CAN'T be changed. It's NOT in your dump. If long ID does not match, you will NEVER get rid of a red dot (unless with cracked firmware).

P.S. don't know about CG Pro, but I doubt it can read/write this. If you bought 160DOWT, not it's emulator, then it will have different id = red dot.

P.P.S. You should REALLY READ this forum. There are already PLENTY of posts about this same thing.
01-11-2023, 13:57 PM,
Post: #10
RE: 160DOWT cluster issue (F25)
(01-11-2023, 13:19 PM)Node Wrote:  Long ID is a secret number in the special area of a 160DOWT chip. AFAIK it's burnt into the chip in the factory and CAN'T be changed. It's NOT in your dump. If long ID does not match, you will NEVER get rid of a red dot (unless with cracked firmware).

P.S. don't know about CG Pro, but I doubt it can read/write this. If you bought 160DOWT, not it's emulator, then it will have different id = red dot.

P.P.S. You should REALLY READ this forum. There are already PLENTY of posts about this same thing.

Thanks for your reply as well as all other members here. Is it possible by replacing the 160DOWT chip with Xhorse 35160DW chip and write the read dump file on it?




Possibly Related Threads…
Thread Author Replies Views Last Post
XZBMW EGS issue on F48 auto gearbox lalillo89 1 152 01-06-2024, 19:17 PM
Last Post: kimz
  The issue from the seventh circle of hell,,, 530d mj_mj_mj 24 1,503 27-05-2024, 11:21 AM
Last Post: mj_mj_mj
XZBMW ENTRYEVO Service Entry Issue mcrussell 4 193 26-05-2024, 01:50 AM
Last Post: mcrussell
  Issue with F60 Siki78 2 92 23-05-2024, 18:07 PM
Last Post: Siki78
  E85 cluster eeprom VIN location stydly 3 162 08-05-2024, 19:47 PM
Last Post: gabur431
  mini f60 countryman, mileage issues red dot after cluster replacement deutsch 6 237 08-05-2024, 11:15 AM
Last Post: EngineerX
XZBMW NBT ID4 to ID6 issue with FSC Driss2 7 314 30-04-2024, 08:02 AM
Last Post: stydly
XZBMW F20 LCI2 black panel cluster coding sqorpius 10 2,184 27-04-2024, 06:51 AM
Last Post: hamzettin
  Instrument cluster e46 mapkrk 2 220 27-04-2024, 00:33 AM
Last Post: mapkrk
XZBMW Bmw f10 6wa cluster mileage jumping 160D0WT Bavrian 4 195 24-04-2024, 09:32 AM
Last Post: Bavrian

Forum Jump:


Users browsing this thread:
1 Guest(s)

Return to TopReturn to Content