[M11]

Been reading a lot of conflicting information about this eeprom on different forums, so thought I'd ask here.

I have a issue with 2014 F3x 6WA kombi that has 160D0WT eeprom in it. Mileage has been lowered at some point in the past and I see that the chip has been soldered. 
The problem now is that it doesn't show service information anymore and it displays lower KM for a few seconds every time you turn it on and then after a few seconds displays another higher KM number. I have found a few similar issues on the internet with this same chip model, so I'm assuming it's a problem with the chip.

Now to my questions:
1. Does this chip have the ID check or can I change this chip without getting a red dot? 
2. Can I replace the 160D0WT with 160D0WQ or does it need to be 160D0WT?


Thanks in advance!

[RuleNormaliai]

This chip has ID check and you can't just replace it with another one.

Also it is not a chip problem, just try to reset mileage and VINs one more time, and and code.

[M11]

This chip has ID check and you can't just replace it with another one.

Also it is not a chip problem, just try to reset mileage and VINs one more time, and and code.

Are you sure 2014 kombi with 160D0WT eeprom have id check? I read in this forum that it's kombi's built after 2015 06 with 35160WT chip that have the id check.


I'm quite sure it is a chip problem, I manually calculated the KM from first two rows and that is 40k km lower number I see for a few seconds after turning on the car (I'm assuming thats the number it was lowered to when the mileage was corrected). So it seems it has gotten stuck and for some reason it doesn't overwrite/update it with the current KM from FEM.
Interestingly when I check KM with Nyo4, it displays the higher KM number what I also see in car after it updates the display in a few seconds. Do these chips store KM value in two places or where does Nyo4 get the number that is not in the first two rows?


Should I be able to erase 160D0WT with CodiProg? It doesn't have a option for 160D0WT, it has a option for 160D0WQ.

[M11]

Just to update. I tried to erase the 160D0WT with codiprog. It erased about 50% of the first two rows. I calculated the remaining km value and it's ~2000km now. From my understanding the car should write it's mileage in kombi if the kombi has lower mileage and the VIN's match, correct?
I put the kombi in car and now it shows that 2k for a few seconds and then reverts to 180k (this happens every time after the car goes to sleep). It is also still giving me the "Service Indicator Not Available" error.
When I read the 160D0WT chip again after it had been in car, the same bytes that I couldn't erase are still the same values. The ones that I could erase have new values. To me this looks like a problem with eeprom.

I also ordered a few 160d0wq eeproms from ali, but I can't write to these at all. When I read them, they are all 0000. I did read in another forum that this means they are remakes and not new chips? It was written there that new chips should have only first two rows as 0000 and all other lines as FFFF. Is that correct?

[doni]

Have you tried erasing the VIN from the chip and recoding the cluster using esys? post the eeprom dump and let me have a look

[CEBEP]

Have you coded kombi? Does it show red dot when ignition is on?

[M11]

Have you coded kombi? Does it show red dot when ignition is on?

I have not coded this kombi as I didn't see a point. According to the owner, the mileage was manipulated before he bought the car a few years ago and everything worked correctly until now. Problem started without anyone doing anything to the car. 
It does not show the red dot. It just doesn't write mileage to the chip and because of that it displays "Service Indicator Not Available" error after every time you let the car go to sleep. Everything else works as expected. 

I have seen the same symptoms once before, in that case the kombi had the same chip type and the mileage had also been reset, so I'm assuming this chip gets corrupted somehow when it's mileage is manipulated. I flashed that kombi and coded it, but it did not fix the issue.

[SweetBMW]

Per my knowledge the 160D0WT chip does not have ID, but the 35160WT has. I have had many issues myself with the latter chip.

If you can, try a dump from a good kombi and make sure both chips (if it has both 160 and 95320) are soldered good to the board.

[M11]

Per my knowledge the 160D0WT chip does not have ID, but the 35160WT has. I have had many issues myself with the latter chip.

If you can, try a dump from a good kombi and make sure both chips (if it has both 160 and 95320) are soldered good to the board.

Thanks for the suggestions. Already tried taking it off and resoldered, it didn't change anything.

I have access to a 2012 F31 6WA kombi. Have to check if it has the same chip model.

How big is 160D0WT dump? I ask because I noticed that if i read it as 160D0WQ, I get 2 lines less than when I read it as 35160WT. CodiProg doesn't have 160D0WT option.

EDIT: Found in another forum the following information:
"160 WT has OTP memory in Block 800-81F /* can't be modded anyway*/ ... will give red dot.... eeprom error"
That explains what I got when reading it as 35160WT, so it seems changing the chip will give a read dot. So assuming that the chip is broken, only option is to buy a used kombi from ebay?