E46 Fanatics Forum banner

Siemens MSS5x Flash Tool Discussion Thread

98K views 222 replies 53 participants last post by  Bali  
#1 · (Edited)
Hello fanatics,

I thought it would be helpful for people to exchange their experience with the Siemens MSS5x Flash Tool.

This way you can talk about operating system compatibility and functions, etc. and we keep the MS43 thread clean.

Please contribute some information about your tested hardware, that we can get it to work for everyone :)


Compatible Operating Systems:

Every x86 and x64 Windows should work. Make yure .NET 4.0 and the driver is installed

Requirements:
  • .NET Framework 4.0
  • USB K-Line Adapter with FTDI chipset



Registration process

Image



FAQ:

Q: Where can I get it?
A: Look for the download in the first section on www.ms43wiki.com

Q: It asks for a registration key?
A2: Yes, that's true, just create your licence here: https://www.ms4x.net/licence/


Q: The flasher crashes after activation.
A: Most propably you need this FTDI chipset driver

Q: Is the tool compatible with my ECU?
A: It is compatible with Siemens MS41, MS42, MS43, MSS50 and MSS54.

Q: Can it do full 256 KByte / 512 KByte flash?
A: Yes, it can read and write both, partial and full file.

Q: Is bootmode required for flashing full files?
A: On MS41 you have to supply +12V to ECU pin 60 or when it has full round OBD plug it's OBD pin 18. On other supported ECUs bootmode is NOT required, even for full flash.

Q: Can it to MS41.0 to MS41.(1/2) conversion?
A: No, you need MS41 Flash Tool V1.05d for that task.
 
#4 · (Edited)
Alright looks like I'm the first one with an issue. I copy pasted the key into the program and I keep on getting the error "Siemens Flash Tool has stopped working. A problem caused the program to stop working correctly. Please close the program."
The exe is still 200something kb so I think it didn't decrypt. I feel like the registration key may have caused an error because there were spaces at the top. Is there any way to delete the program history from my registry?

The machine is Windows 7 64 Bit. Alright, using regedit I found the entry for the tool. I used the search function in regedit and it came out as "SIEMENS FLASH TOOL." For me, it is located at Computer\HKEY_USERS\numbers\Software\SIEMENS FLASH TOOL


Okay so I reregistered it and I got this error:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: The path is not of a legal form.
at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.InternalGetDirectoryName(String path)
at FTD2XX_NET.FTDI..ctor()
at ​*‫‫‪**‬**​*‪*‬**‪​*‎**‪**​**..ctor(\]@A=j>KW2DT4\*kU\]bA4?greE! )
at \]@A=j>KW2DT4\*kU\]bA4?greE!..ctor()
at I-Y0A;R_8\&>CWj#@Oa\]lkK/O.‬**‬*‎‏*‏‫*‪‫**‫***‬‏​‏‏‬‬*​***(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
Siemens Flash Tool
Assembly Version: 1.1.2.2
Win32 Version: 1.1.2.2
CodeBase: file:///C:/Users/Official/Desktop/Siemens%20Flash%20Tool%20v1.1.2.2.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
FTD2XX_NET
Assembly Version: 1.0.14.0
Win32 Version: 1.1.2.2
CodeBase: file:///C:/Users/Official/Desktop/Siemens%20Flash%20Tool%20v1.1.2.2.exe
----------------------------------------
CxreeaJRvNDPTHoVGegLeGRaLbOaA
Assembly Version: 0.0.0.0
Win32 Version: 1.1.2.2
CodeBase: file:///C:/Users/Official/Desktop/Siemens%20Flash%20Tool%20v1.1.2.2.exe
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1099.0 built by: NETFXREL4STAGE
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1099.0 built by: NETFXREL4STAGE
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
#12 · (Edited)
Okay so I reregistered it and I got this error:
************** Exception Text **************
System.ArgumentException: The path is not of a legal form.
at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.InternalGetDirectoryName(String path)
at FTD2XX_NET.FTDI..ctor()
at ​*‫‫‪**‬**​*‪*‬**‪​*‎**‪**​**..ctor(\]@A=j>KW2DT4\*kU\]bA4?greE! )
at \]@A=j>KW2DT4\*kU\]bA4?greE!..ctor()
at I-Y0A;R_8\&>CWj#@Oa\]lkK/O.‬**‬*‎‏*‏‫*‪‫**‫***‬‏​‏‏‬‬*​***(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Try to install lastest FTDI chipset drivers and make sure the USB to K-Line adapter is plugged in and has received a COM port by windows.

This got it working at my computer where I had the same issue.
 
#11 · (Edited)
Well, to make the source better readable, we have to rename all the method and class names to the real ones.

The V1.1.1.4 was obfuscated by ObfuserEx v0.60, this version can be reversed very easily, but the newer version of the flashtool, v1.1.2.2, uses ObfuserEx v1.0.0, which doesn't keep those names.

If someone is skilled enough to do that, I will github the non-obfuscated sourcecode.
 
#21 ·
#24 ·
So as I already said in some other threads and on facebook, this software was obfuscated by Kim to protect it against the things we are doing now.

This type of obfuscating software is also often used to make malware executables undetectable against antivirus scan engines. Thats why your Sonicwall says "Win32.ObfuserEx3" because thats the type of scrambling software Kim used.

There is absolutely no trace of any malicious code inside the flasher.

Maybe you guys should just stop downloading files for your car at work ;)
 
#31 ·
In case anybody wondering why I do this, a few people including myself where discussing some ways to keep this software alive in an ethical way.

With the need of writing an email for a key, we were atleast aware of who got a key sent and could stop once anyone had problems with it.

But this is now obsolete at least from my side, feel free to do the deobfuscation and renaming in the v1.1.2.2 :) Or github it, or whatever.
 
#36 ·
You're right, I posted how to get rid off the registration feature, which is not needed anymore once we continue the development of this tool and make the unpacked sourcecode compilable.

But now people share the program and keygen without even knowing about the real author and this only is my concern. I could have released a keygen an hour after I got my hands on the flasher, but instead we discussed how we can create a better solution.

We came to a solution that is obviously not accepted, so it's okay for me, but don't expect any more help from my side.
 
#45 ·
This software is working great! A little scary with all the ant-virus popups I was getting, but it simplifies the whole tuning process by a lot! I'm hoping now that the keygen has been deleted and since so few people had access to it you all will continue development on it. It's a great piece of software.