BMW X5 CAS 3

**paulsta** · 21st February, 2019, 10:36 AM

Could someone please double check the flash and eeprom to make sure it's not corrupted

Many thanksarchive.zip

Sent from my Pixel 2 XL using Tapatalk

**topclef** · 21st February, 2019, 10:43 AM

bad flash , post the screenshot for the CAS sticker

**droidwayne65** · 21st February, 2019, 03:06 PM

Flash, I can't tell without a part number but Eeprom is ok, except it's in programming mode.

**paulsta** · 21st February, 2019, 03:59 PM

Originally Posted by droidwayne65

Flash, I can't tell without a part number but Eeprom is ok, except it's in programming mode.

I just added a key to the eeprom and posted dump, here is the part number in the picture

Cheers

Sent from my Pixel 2 XL using Tapatalk

**droidwayne65** · 21st February, 2019, 04:40 PM

Originally Posted by paulsta

I just added a key to the eeprom and posted dump, here is the part number in the picture

Cheers

Sent from my Pixel 2 XL using Tapatalk

What tool did you use to add the key? It appears that it put the CAS in programming mode, added the data then wrote a Flash from a database. Anyway, here's a good Flash for your CAS.

**paulsta** · 21st February, 2019, 04:53 PM

Originally Posted by droidwayne65

What tool did you use to add the key? It appears that it put the CAS in programming mode, added the data then wrote a Flash from a database. Anyway, here's a good Flash for your CAS.

I used acdp but ive never had this issue before, thanks for the flash and i will try this out, how did you get the eeprom out of programming mode and is my added key still in there?

thanks again

**droidwayne65** · 24th February, 2019, 02:19 AM

Originally Posted by paulsta

I used acdp but ive never had this issue before, thanks for the flash and i will try this out, how did you get the eeprom out of programming mode and is my added key still in there?

thanks again

Didn't mess with key data, so it should be intact. There're three bytes, whose bit pattern determines whether it's in programming mode or not. Take a gander at both files. Reading several CAS eeproms after failed ISTA-P updates showed what it did to those bytes while it was updating the CAS.