[LMB335IS]

Originally Posted by Schmidty335i

my bad.... try this one:
https://mega.nz/#!ULBRhaqA!D-_QMQpct...rHKSnDTCbL-hG8

The stock bin looks okay. Is the last seven of your VIN E263279?

[Schmidty335i]

Originally Posted by LMB335IS

The stock bin looks okay. Is the last seven of your VIN E263279?

Yes... He said it was viginized when i bought it. i installed and coded it then got the error. this is the file i took off of it as a backup before i tried to revirginize it.

[LMB335IS]

Originally Posted by Schmidty335i

Yes... He said it was viginized when i bought it. i installed and coded it then got the error. this is the file i took off of it as a backup before i tried to revirginize it.

Okay, have you tried to write this back to the eeprom yet? If not, try that first. If it writes successfully, take this bin back into your hex editor and FF out the VIN as Sensible showed above starting at column 08. I have no idea what mileage it's showing and you said you couldn't get it to save the changes. I use a R270 and I usually just use the change mileage function and pick a random low number like 50km etc. It always writes that but won't take 00 across the first two lines.

And if that doesn't work I have plenty of virgin M3 cluster bins.

[Schmidty335i]

Originally Posted by LMB335IS

Okay, have you tried to write this back to the eeprom yet? If not, try that first. If it writes successfully, take this bin back into your hex editor and FF out the VIN as Sensible showed above starting at column 08. I have no idea what mileage it's showing and you said you couldn't get it to save the changes. I use a R270 and I usually just use the change mileage function and pick a random low number like 50km etc. It always writes that but won't take 00 across the first two lines.

i will give that a shot! i have only tried to write 00 across the first to lines to get it to go to 0 miles. i dont have the ability to just type in a milage and try that. do you know what i could type for the first two lines in hex to put it at 50km? i thanks again for the fast response it is very appreciated!

[LMB335IS]

Originally Posted by Schmidty335i

i will give that a shot! i have only tried to write 00 across the first to lines to get it to go to 0 miles. i dont have the ability to just type in a milage and try that. do you know what i could type for the first two lines in hex to put it at 50km? i thanks again for the fast response it is very appreciated!

50km would be 00 03 repeating across the first two lines.

[Schmidty335i]

Originally Posted by LMB335IS

50km would be 00 03 repeating across the first two lines.

just went and grabbed the cluster out of the car, going to tear it down and reprogram accordingly. thanks again for all of your help. hope this works i will be back to update!

[LMB335IS]

Originally Posted by Schmidty335i

just went and grabbed the cluster out of the car, going to tear it down and reprogram accordingly. thanks again for all of your help. hope this works i will be back to update!

[Schmidty335i]

Originally Posted by LMB335IS

ok i just did what sensible said... only cleared the red part of the 2E0 line. doing 00 03 for the first two lines did the same thing it would do with 00's. i just dont think my carprog can do it i guess. i am going to put the cluster back together and code it to the car. ill follow up soon with results.

[Schmidty335i]

Originally Posted by LMB335IS

well there is some good news i guess. when i turned only the selected part of 2EO to FF. i got the tamper dot back again so i know that my vin has been erased from the eeprom. but when attempting to code the cluster to the car it gives me an error:

https://scontent.fphx1-3.fna.fbcdn.n...9c&oe=5D1718B2

Maybe the EEPROM is finally virginized right now and i have been loading faulty coding to it the entire time and it just didnt give an error? hopefully someone can chime in and help me out.

[Schmidty335i]

translated the error from the error log. it said "Compare/verify errors in coding data SG already coded to other FG number, coding aborted". it mentions PABD/CABD A_PL2KMB.IPS also if that means anything to anyone.

[LMB335IS]

Originally Posted by Schmidty335i

translated the error from the error log. it said "Compare/verify errors in coding data SG already coded to other FG number, coding aborted". it mentions PABD/CABD A_PL2KMB.IPS also if that means anything to anyone.

I don't know what you have going on there to be honest. I take it you've used your coding setup and cable successfully before so there's no issue with that. It's a 080D0WQ eeprom right?

[Schmidty335i]

Originally Posted by LMB335IS

I don't know what you have going on there to be honest. I take it you've used your coding setup and cable successfully before so there's no issue with that. It's a 080D0WQ eeprom right?

i know it is crazy man... lol. i used it many times to code with the exact same setup i am using right now. it coded successfully last time when i coded the entire 2E0 line with FF's just a few days ago. tamper dot went away so i know it took the vin but i still got the original error that caused me to create this post. i am downloading the newest daten files i could find. my current ones are from 2015 and the new ones i got are from 2017. hopefully that works if now i have no idea. i do need to get it coded to at least the original gripe so at least all the gauges work. until i code to the car the rpm gauge will not work. anyone else have any ideas while i am installing the new daten files?

[Schmidty335i]

found out that with the carprog i can change the first two lines to FF and it takes. when i install it in my car now it shows a tamper dot and 999,999 miles. if i code it to my car will it put my car at that or at the proper milage 51000? i tried to write my original two lines back that showed the proper 51000 but it will not write. i can only change the first two lines to FF's.

[Sensible_]

Ok, let's start from beginning.

1. Write a good eeprom dump to the eeprom. An original backup of you have one.

2. Blank VIN with FF

3. ZERO mileage (if you need to) 00 bytes

5. Change byte 0x2D7 to 00 also.

6. Program KOMBI with winkfp

7. Default code with NCS.

[Sensible_]

Also, that error you posted basically means 'control unit (SG) already coded to other VIN number (FG)'

The VIN can't be blanked properly...

Do my steps above and everything should be ok.

[Schmidty335i]

Originally Posted by Sensible_

Ok, let's start from beginning.

1. Write a good eeprom dump to the eeprom. An original backup of you have one.

2. Blank VIN with FF

3. ZERO mileage (if you need to) 00 bytes

5. Change byte 0x2D7 to 00 also.

6. Program KOMBI with winkfp

7. Default code with NCS.

ok i am at work right now, i can do all that you mentioned except step 3. when i code my default backup to the cluster it wrote all the lines back except for the first two. since i changed them to FFs it will not let me change them to anything else. maybe i need to wait til my new eeprom chips get in cause my programmer says to use another progammer or a new chip to code erase the first two lines.

so with my current setup i have today i can do all the steps you mentioned but the first two lines will all be FF's. with FF's the cluster shows 999,999 miles with a tamper dot. is this safe to code? or will it mess up my milage? should i just wait and write my stock.bin file to the new eeprom? thanks for all of the help everyone! hopefully with all of the documentation here anyone trying to code there cluster will have a very detailed post about errors haha.

[Schmidty335i]

i should be home in about 4 hours so if its safe to code my current eeprom with the FF's in the first line i will give it a shot tonight.

[Sensible_]

Originally Posted by Schmidty335i

i should be home in about 4 hours so if its safe to code my current eeprom with the FF's in the first line i will give it a shot tonight.

No!

Don't. I have never seen anyone change the mileage to FF before. It should have been changed to 00.

Yes, the first 2 lines are protected.

Incase FF is ok, change the byte at 0x2D7 to 00 then check what the cluster displays.

If it still shows 999,999 don't code it! As soon as you code it all the modules in the car which store mileage will record 999,999!

[Schmidty335i]

Originally Posted by Sensible_

No!

Don't. I have never seen anyone change the mileage to FF before. It should have been changed to 00.

Yes, the first 2 lines are protected.

Incase FF is ok, change the byte at 0x2D7 to 00 then check what the cluster displays.

If it still shows 999,999 don't code it! As soon as you code it all the modules in the car which store mileage will record 999,999!

ok thank you for the heads up! to be clear the eeproms first two line of code are FF. it will not let me change it with the carprog. the carprog will write the first two lines if the chip is new which i have two coming soon. so i will wait til i get the new one then i will code the first two lines with 00s and my backup .bin file for the kombi with the two lines for the vin cleared and try reinstalling it again. thank you and i am happy you got back to me before i installed it showing 999,999 miles haha that would have sucked big time!

[Schmidty335i]

Originally Posted by Sensible_

No!

Don't. I have never seen anyone change the mileage to FF before. It should have been changed to 00.

Yes, the first 2 lines are protected.

Incase FF is ok, change the byte at 0x2D7 to 00 then check what the cluster displays.

If it still shows 999,999 don't code it! As soon as you code it all the modules in the car which store mileage will record 999,999!

i didnt see a line of code when i read the eeprom that said 0x2D7. strange?

[Schmidty335i]

ok so what i have gathered from all of this is. i need to wait for my new eeproms get here so i can code the first two lines properly and load my original .bin file with the selected areas of the 2E0 line FF. then put it in my car and code it with NCS expert? here is the .bin i am going to load on my new eeprom when it gets here:

https://mega.nz/#!JDgzyAzQ!p3DcsClR7...GYBINZoD0UbmoQ

does that look ok? thanks

[Sensible_]

Originally Posted by Schmidty335i

ok so what i have gathered from all of this is. i need to wait for my new eeproms get here so i can code the first two lines properly and load my original .bin file with the selected areas of the 2E0 line FF. then put it in my car and code it with NCS expert? here is the .bin i am going to load on my new eeprom when it gets here:

https://mega.nz/#!JDgzyAzQ!p3DcsClR7...GYBINZoD0UbmoQ

does that look ok? thanks

Why don't you just try changing the byte 2d7 to 00?

It's not a line. It's a byte...

Go down to line 2D0 and count 7 bytes along...