We have recieved 83% of our goal ..


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Help Needed: ECU & FEM from Donor Car – Cluster & NBT Not Working (VIN Mismatch)
#1
Hello everyone,

I’m working on a BMW X1 F48 and need advice from anyone experienced with module swaps and VIN/coding issues.

Here’s the situation:
  • I replaced the ECU (DME)FEM, and key fob with a matched set from a donor vehicle.
  • The car starts and drives fine, but there are problems:

    • The instrument cluster (KOMBI) shows errors and doesn’t function properly.
    • The NBT/iDrive system starts but navigation and other functions don’t work.
    • There is a clear VIN mismatch, likely causing communication and coding issues.
    • I also cannot use the key fob to lock/unlock, and the driver window doesn’t work.



What I’ve done:
  • Installed and working with E-Sys 3.40.2
  • Using PSdZData Lite
  • Tried Tool32 (only has FEM_20.prg)
  • Have original FA loaded
  • Can read SVT, but modules still show donor VIN





What I Need Help With:


  1. Is it possible to restore the original VIN to the ECU and FEM using Tool32 or BimmerUtility?
  2. After changing VIN, what modules (like HU_ENTRYNAV or KOMBI) also need to be coded?
  3. Will I need an FSC patch to get full NBT/iDrive functionality (like Navigation)?
  4. Would getting a virgin cluster or new NBT be a better solution — or is that unnecessary?
  5. Is there any risk if I VO-code now while VINs mismatch?


Any tips, tools, or guidance from someone who’s been through a similar retrofit or donor swap would be a huge help. Thank you!
Reply




Users browsing this thread: 1 Guest(s)