E46 Fanatics Forum banner

MS4X Flasher update from MS430066 to 0069 failed, momentarily bricked DME - SOLVED

395 views 6 replies 2 participants last post by  DigitalRelay  
#1 · (Edited)
After a full read and saving my original DME bin file for my 325i and realizing I was on the 0066 bin, I decided to update. I've been learning and researching how to use MS4X Flasher for my upcoming M54B25 to B30 swap and felt like I understood what I was doing, but on the first attempt to flash the MS430069 bin file for US that I downloaded from MS4X.net, I got an error code toward the end of the flash telling me it failed. I then noticed that I had actually used the MS430069 bin for the B30, so I was going to re-flash anyway, but when I tried to flash again, I got a safety check error that I'm pretty sure was due to the failed flash.

After a slight panic hit me, I reset the computer, turned the car off, checked my battery charger status and tried to start the car - crank, no start. Not surprising.

Instead of forging ahead with trying to flash the 0069 bin again, I decided to write my original bin file back to the DME, which required me to turn off the Safety Check in MS4X Flasher and was a nervous few minutes waiting for it to complete, but I'm back up and running again.

Before I take another stab at this, I just wanted to double check with someone who knows this better than me that I'm doing this correctly.

In MS4X Flasher, load Siemens_MS43_MS430069_E46_M54B25_US.bin and do a full write. Once completed, turn the car off for 10 seconds.

If successful, then do a full read, save that bin, then I can make changes in TunerPro and save as noting what I changed.

Do I have this right? TIA
 
#4 ·
Update in case this stuff is useful to someone in the future: I decided to try flashing my spare DME to MS0069 for the M54B25 that's currently in the car. I also used TunerPro to SAP delete, rev limit to 7k, and exhaust flap delete. After saving as that bin, I did a full write to the DME, then opened INPA, cleared error codes and cleared adaptations.

I installed it in the car and it fired up after a slightly longer than normal cranking period, but I had the EML light and Traction Control lights on. The engine was hunting for a stable idle, which it eventually found, but I could not rev past about 1500 rpm. So, I shut it down, swapped DMEs back, made sure the car was back to normal, it was.

I reopened the latest bin in TunerPro to check my work and although Immobilizer Bypass, and Immobilizer Bypass DTC Fix both showed as Patched, Clear Immobilizer Data did not, which I'm almost sure I did patch previously. I Patched Clear Immobilizer Data and resaved the bin. I'll flash it to the spare DME again and try it later or tomorrow.
 
#5 ·
I posted this on the BMW Tuning Discord, but want to include any information here:

I’m in the middle of rebuilding a stock M54B30 that I intend to swap into my 2002 325i. Being aware that I’ll need to flash my MS43 DME for the larger engine, I bought a spare DME and assembled an OBD2 bench setup to better understand and learn tuning and coding with MS4X Flasher and TunerPro.

The spare DME was from a 2001 X5 with 3L. I wanted to update firmware from 0066 to 0069, and disable the immobilizer so I could use it in my car, and eventually learn SAP delete, and change rev limits.

Here’s what I did:
  • MS4X Flasher full read - save bin.
  • MS4X Flasher write Siemens_MS43_MS430069_E46_M54B25_US.bin
  • MS4X Flasher full read - save as bin “FlashedTo0069”
  • TunerPro - open new bin, select 0069 XDF, select Community Patch 0069 2.9.2
  • TunerPro - Immobilizer Bypass apply patch, Immobilizer Bypass DTC Fix apply patch, Clear Immobilizer Data apply patch - save as bin “FlashedTo0069-immoDel”
  • MS4X Flasher - load bin “FlashedTo0069-immoDel”, Full Write
  • Power down DME for 10 seconds
  • MS4X Flasher - Adaptations - select all - Clear Adaptations
Once installed in the car, EML and TCS lights are on, rough idle, will not rev past 1500 rpm. I’ve tried this a couple times, and also opened the spare DME to inspect for any physical damage, which it does not appear to have.

Am I doing something wrong?
 
#6 ·
Well, that was fast. A Discord member suggested that it was a problem related to DTC codes. It was recommended to clear DTCs, and adaptations, in that order. I had already cleared adaptations earlier, so I decided to install the spare DME again, turn the ignition on, and use my OBD2 bluetooth scanner and OBD Fusion to read codes, which there were a couple, which I cleared. I then started the car, no CEL, idled normally, revs normally.