MSS6x Flasher - Now released!

[terra]

interesting, being able to flash the boot section without BDM would be nice.

So I did try just straight up changing the hardware reference and flashing (and also changing security access keys to the MSS65 ones). While it does accept the flash and respond to some INPA commands, it doesn't seem to boot completely as a lot of commands just don't work. Flashing back to MSS65 code from there worked fine, it wasn't bricked or anything.

That boot section does have a number of differences so I'm not sure replacing it is avoidable, though would have to study the differences closer.

I'm sure mpower32 would have the means to overwrite the boot sector given the other things his software can do (i.e clear censorship mode and restore the flash). I'm not skilled enough to write code to do that reliably myself.

[hobbit382]

interesting, being able to flash the boot section without BDM would be nice.

[terra]

So while I doubt most people will run into this (seems like no one else reported anything similar in the last 6 years) - for future reference if you have an RSA bypass'd DME and later on use WinKFPs expert mode to do some flashing and accidentally pick the wrong DME (i.e MSS60 file on MSS65 or vice versa), the DME will happily overwrite its bootloader with the new one. And this breaks a bunch of things... the DME doesn't actually want to run due to the hardware string not matching, and the RSA keys will no longer match what they should be, so security access is broken and the correct binaries will no longer have a valid signature as far as the DME is concerned. I was able to ultimately recover without BDM with a bunch of hacky changes to my app, but something to keep in mind. Unfortunately I don't think there's a fantastic way for me to protect against that sort of issues. From what I recall, other BMW DMEs would normally not copy the new bootloader if the hardware string doesn't match rather than complaining after the fact.

Good news is that might mean it's possible to crossflash MSS60 code to the MSS65 without BDM using a similar trick to what we do to get the CSL flash to work on non-CSL DMEs. I'll have to dig into the non-writeable code a little deeper to see if there's any major compatibility issues there.

[terra]

So for whatever it's worth, this application seems to work fine on Windows for ARM, except you need to change the port from FTDI0 to COM1 (or whatever COM port you have the cable assigned to). It appears the ARM version of the FTDI driver doesn't support D2XX mode.

From what I recall, I had used D2XX mode in the first place because I found it to be more stable, but so far it seems stable enough here.

For completeness, this is using an M1 Macbook Pro with Windows 11 for ARM running in VMWare

[BigRussia]

I suspect you have an issue with the tach, rather than an issue with the DME software. Personally, if you're happy with the tune, then I'd leave it alone.

Perhaps try a tach/kombi cluster test with INPA and see if it behaves.

Cool thanks for that insight, I have INPA so I'll try to see if it can do a KOMBI test of the warmup dial, I didnt even think of doing that so worth a shot!

Yeah no issues with the AA tune, car is a daily with just the AA Signature xpipe and mufflers. The two features of the MSS60 Binary Modification Tool I wanted to use were Engine Temp Rev Limit (and hoping as extra benefit it might also resolve that weird warmup dial issue) and tuning the throttle mappings, since I find Comfort too soggy and dead down low and Sport to be too touchy and stabby in that same initial pedal tip-in, so was looking to tune those closer together like I did on the E46 using the MSS54 Tool (and has been fantastic btw!). Was thinking to make Comfort fully linear if possible.

BTW if anyone is interested I made a thread on M3post about the warmup dial issue, and here's a couple of the most extreme instances lol (usually it gets stuck around 6.5-7.2k RPM ranges when it does mess up, but then will usually sorts itself next drive or overnight):

[Martyn]

I suspect you have an issue with the tach, rather than an issue with the DME software. Personally, if you're happy with the tune, then I'd leave it alone.

Perhaps try a tach/kombi cluster test with INPA and see if it behaves.

[BigRussia]

060E is very old software, which is why my tool is advising you to upgrade, clearly if you do this you'll lose your AA tune, however it will allow you to perform an RSA bypass aftwards as it'll be back to stock.

Oh interesting that Active didn't update the software when doing their tune, the previous owner had it done only like a year or so ago at Active's HQ here in Miami (same time he had them do the full exhaust install, it was a package).
Slightly unrelated but I wonder if my software being so out of date and with their likely ancient tune is causing another issue I'm having with the tach warmup dial going on the firtz and getting stuck at random rpms even with the car fully warmed up (doesnt force a rev limiter though). Also I am not familiar with the software updating process, did some google searching and read a few threads but didn't seem to be a definitive guide to the process, could you point me to one if you know of?

Do you mind sharing the 060E full read here?

Yes of course, I attached the Full Read 5120kb file here thanks!

[terra]

Do you mind sharing the 060E full read here?

[Martyn]

060E is very old software, which is why my tool is advising you to upgrade, clearly if you do this you'll lose your AA tune, however it will allow you to perform an RSA bypass aftwards as it'll be back to stock.

[BigRussia]

Hi terra

I attempted this on my 2008 E90 M3 6mt, that came with Active Autowerke tune from previous owner, and ran into a few oddities/issues:

- After the Read Full Flash completed, I went to 'Read ISN / Secret Key’ as recommended and I got the message: "Could not find secret key".
- I then attempted the RSA Bypass; clicked Load File using my same full file dump, chose Slow option and got message: "The file you loaded is not a stock binary. The RSA bypass requires a stock binary be used."

I'm guessing both of the above could be cause of the AA tune? I don't have the stock tune file for my car since it came with the AA tune from the previous owner, who had it installed with full AA exhaust with HFC.

- Lastly, I booted up the MSS60_Binary_Modification_Tool_V1.9.5 to see my full dump file settings, and got message: "Out of date / unsupported software version detected! Please upgrade your DME to 240/241E."

Thanks in advance!

[Tbonem3]

Did you try compatibility mode (win 7) - administrative start?

Make sure your obd2 cable is set up properly. Needs to be flashed with ediabas firmware, and then set your device settings so that it's listed as COM1 with latency @ 1ms.

[Bissell63]

I installed on my Dell Laptop with Windows 11 Pro. Is application compatible with my setup. Are there any special settings I need to address in order to run on my system?

This is frustrating because I was running the software on my old laptop with no problem.

[Bissell63]

Yes, Ediabaslib.dll is in same folder as the executable MSS6X Flasher.exe which are in:
D:\BMW Diagnostic Software\MSS6x Flasher\
I have both MSS6X Flasher and Ediabas installed on an expansion hard drive formatted as D: drive.
I changed the ecupatch in the config file MSS6X Flasher.exe.config to reflect this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.2"/>
</startup>
<appSettings>
<add key="Port" value="FTDI0"/>
<add key="ecuPath" value="D:\Ediabas\Ecu"/>
<add key="defaultSGBD" value="MS_S65.PRG"/>
<add key="defaultProgrammingSGBD" value="10flash.prg"/>
<add key="ClientSettingsProvider.ServiceUri" value=""/>
</appSettings>
<system.web>
<membership defaultProvider="ClientAuthenticationMembershipPro vider">
<providers>
<add name="ClientAuthenticationMembershipProvider" type="System.Web.ClientServices.Providers.ClientFo rmsAuthenticationMembershipProvider, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" serviceUri=""/>
</providers>
</membership>
<roleManager defaultProvider="ClientRoleProvider" enabled="true">
<providers>
<add name="ClientRoleProvider" type="System.Web.ClientServices.Providers.ClientRo leProvider, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" serviceUri="" cacheTimeout="86400"/>
</providers>
</roleManager>
</system.web>
</configuration>

[Martyn]

Double check you have the required files in place, ediabaslib.dll is in the same folder as the exe and that the config points to the correct location to the ECU/PRG files.

[Bissell63]

I downloaded and ran MSS6X Flasher application. When I run I get this screen:



It looks to be disabled for some reason. Has anyone seen this before who may offer up some things to remedy it?

I am looking to use it on my 2006 BMW E60 M5. Thank you.

Henry