[marcel.buhna]

I am currently working on a recovery procedure for a bricked CAS3+ module on a BMW E90 320d (N47) that became unresponsive after a failed update attempt.
I have already performed a physical transfer (swap) of the MCU Flash and EEPROM from the original unit to an identical donor unit using VVDI Prog Xhorse 5.3.8. Both read and verify operations passed successfully. Despite the verified data transfer, the key fob is not detected by the unit. No communication possible via OBD (module unresponsive). I suspect a firmware/EEPROM incompatibility between the donor Flash and the original EEPROM data. I am looking for a known-good stock flash.bin file for this CAS variant to perform a full restore. I possess the necessary tools to perform the write process and complete the synchronization with the DDE and ELV once the module is responsive.
Hardware and Software Setup:

dїдgиo5тїc Tools: ALLSCANNER Vжdїдg Multi VCX-Plus ,VVDI Prog Xhorse 5.3.8

Power Supply: Stetsom Infinite Black 70A with AGM 100Ah battery (stable voltage at 13.8V-14.2V).

Environment: WinKFP v5.3.1.0, ёdїдbд5 v7.7.2.500, Tool32, i5тд-D, ñc5 ёxpёят.

Module Identification:

Original Unit: CAS3 BMW E90 | HW C4 | 61.35-9147226-01 | Siemens VDO 5WK49513YBR S/N: 2091870514 | Diag-Index 06A0 | Mask: 0L15Y

Donor Unit: CAS3 BMW E90 | HW C4 | 61.35-9147226-01 | Siemens VDO 5WK49513YBR S/N: 2091755954 | Diag-Index 06A0 | Mask: 0L15Y

I have attached the original CAS .bin files (Flash and EEPROM) for your analysis
Thank you for your technical support.

[ahmadarifai]

your eeprom looks ok, use this flash with your original eeprom and see if you get ignition.

[marcel.buhna]

your eeprom looks ok, use this flash with your original eeprom and see if you get ignition.

Here is an update. I wrote the file to two identical modules, both sharing the same рдят numbers and mask. I successfully flashed and verified both. However, the CAS3 is still not waking up, and there is no K-CAN communication. The slot just spits the key right out. The hazard lights work, but there is no clicking sound from the instrument cluster, though the position lights do turn on. I checked all the fuses in the glove box, and they are all good. I also tested pin 21 on the CAS connector with a multimeter, and it reads 12.66V. I tried to connect via OBD, but the module is completely dead. I have attached the INPA and Tool32 screenshots to show the communication errors.
--------------
Since the hardware is confirmed to be working on multiple boards, I suspect the issue might actually be a corruption or an active ELV lock in my original EEPROM.
Could you please review my original eeprom.bin file (which is attached to the first post of this thread), repair any corruption, and reset the ELV counter?

[ahmadarifai]

I tried your files on bench, turns out you have both a bad eeprom and flash.
you need a modified EEPROM file for your car it should start right up. change vin isn and make 0km then change vo code. you might need to program new key

[marcel.buhna]

I tried your files on bench, turns out you have both a bad eeprom and flash.
you need a modified EEPROM file for your car it should start right up. change vin isn and make 0km then change vo code. you might need to program new key

It makes perfect sense why the CAS and K-CAN are completely dead in the car.
I have one limitation, however: I only have a VVDI Prog to read and write the MCU, but I do not have any key programmer tool to generate a new transponder.
Is there any chance the key data can be recovered from my corrupted EEPROM and transferred to the modified donor EEPROM so I can still use my original keys? Also, were you able to extract the correct ISN from my dump?
Please let me know.

[ahmadarifai]

I made new file and added the existing 3 keys to the new eeprom the eeprom became corrupted, do you know which key number you have?

---

your Long isn 095CC88D4D6272EA4D52946305618DEC
short is 0000B459
power class 2

[marcel.buhna]

Those are exactly the ISN and Power Class values I see on my end.
Regarding the keys, I unfortunately do not have a key reader to check which exact key number I am holding. Since copying all 3 keys corrupted your new file, it makes sense that at least one of the key slots in my original dump got corrupted during the failure.
As a first attempt, I manually reset the ELV counter to FF in my original EEPROM dump. I am going to write this repaired EEPROM along with a healthy donor flash to the CAS and test all my physical keys in the car to see if at least one slot is still healthy and recognized.

I will report back with the results.

[marcel.buhna]

I made new file and added the existing 3 keys to the new eeprom the eeprom became corrupted, do you know which key number you have?

---

your Long isn 095CC88D4D6272EA4D52946305618DEC
short is 0000B459
power class 2

Hi, just a quick update: I tested the CAS in the car with my original EEPROM (with ELV manually reset to FF) and a donor flash. All my 3 physical keys work perfectly!

It seems the key slots were actually fine, so maybe your software just had a glitch when trying to copy them to the new file. The real issue was only the ELV fatal lock and the corrupted flash. Thanks anyway for confirming my ISN and Power Class, I really appreciate your help!