MSS6x Flasher - Now released!

[angli]

Can you help me analyze why I can't read the DME information?

I read the DME info with winkfp, but I can't read the DME type with MSS 6X.

Thanks

[angli]

I dont know if you can to be honest, I just bought a cable that said that it was like this one

https://www.ecuworx.co.uk/product/ecuworx-flashing-cable-for-e60-m5-e65-m6-and-e92-m3/

but i dont know if having a non-updated cable would stop you being able to read the firmware... but Id always start with a correct one as the next thing you are going to do is want to write it anyway

Yes, I have this Flashing Cable. Do you have an instant messaging contact? It's easier to communicate that way.

[aaronmiles]

I dont know if you can to be honest, I just bought a cable that said that it was like this one

https://www.ecuworx.co.uk/product/ecuworx-flashing-cable-for-e60-m5-e65-m6-and-e92-m3/

but i dont know if having a non-updated cable would stop you being able to read the firmware... but Id always start with a correct one as the next thing you are going to do is want to write it anyway

[angli]

What COM Port are you using? Are you using the correct USB cable? (one of his for example with the updated ediabas firmware (not that this is supposed to limit your ability to read a DME))

COM port is com1 latency time set to 1
How do I verify that I have updated the ediabus firmware?

[aaronmiles]

What COM Port are you using? Are you using the correct USB cable? (one of his for example with the updated ediabas firmware (not that this is supposed to limit your ability to read a DME))

[angli]

I need your help, I tried a lot of things but I can't recognize the DME with MSS 6X.

My OS is windows 11, I installed Ediabus, INPA, NCS, imported MS_65.prg and 10flash.prg, INPA is working fine and I can read the AIF.

I read the DME with MSS 6X and it says UNKNOWN! / unsuppported.

I used inpa and winkpf to find out that my dme version is 241E.

[aaronmiles]

QQ. I did look through trying to find an answer to this but does would mss6xflasher work with an original BMW OPS orange head? (connected to OBD2, not MOST) via a proper ediabas install? Im not adverse to buying a pre-flashed obd cable, but thought I would just check if my bmw head would work also (it works with winkfp at the moment for example - I did the GTS flash tune on my e92 m3 without issue)

Cheers

[pyth0n]

Just to follow up on my Bricked MSS85 (M5) DME, and how I recovered it:

Bought KTAG clone off Ebay (You need KTAG, not KESS. Make sure it isn't coming with OBDII connectors.) Apparently a BDM100 off Aliexpress will work also (cheaper, longer to ship), or a Galletto 4 V54.

Opened, ECU, soldered pins on the BDM header connectors (pins came with KTAG).

Installed KTAG software, Make sure you install Visual C++ 2005 and reboot after install or you will get Checksum errors.

Read data from ECU to have a backup of what is there. If you get Checksum errors, STOP and fix them. The reads are worthless with these, and these reads could be important.

At least with KTAG it complained about the protocol being wrong for the right processor (instructions say 117, but it wanted 116). I just used the one it suggested and it worked fine. I believe this is a difference with the Siemens vs Continental DME builds (mine was an '08 and Continental).

Take you backup you made with MSS6X flasher (you did take one, right?), and use a hex editor to break it into 4 files. 0-0x7FFFF, 0x80000-0x27FFFF, 0x280000-0x2FFFFF, and 0x300000-0x4FFFFF. (512kb, 2048kb, 512, 2048)

The first block is the left MPC. The second is the Left External Flash. Third is right MPC, Fourth is right Ext Flash.
Flash these back to the DME. That should be it.

When I did this, I got a DME EWS error. My backup did not have the ISN in it. However, the ISN will be in your BDM backup that you took before you wrote. Open up the left micro backup file read by BDM. ISN is the 6 bytes at 0x7940. Move these to your your Flasher backup file and write back to the ECU.

Even better, make sure you read the ISN with MSS6X flasher before you even try to flash anything back. This will prove that the RSA bypass and everything is working.

You may want to just write to the Left Ext Flash first and the right MPC and flash, and see if you recover it. This will avoid overwriting the ISN if the left MPC is otherwise healthy.

I've now written back to the ECU many, many times with the MSS6X flasher program with no issues. I have no idea what failed, but it was a fluke based on my experience. I'm going to go see if I can find an obvious corruption between my BDM backup and what I was trying to write with the MSS6X flasher.

Thank you. This address is acceptable for MSS60?

Well, if BDM doesn't work either your only solution would be to get ISN from CAS and find another ECU.

Is there any way to get ISN from CAS without working key?

[Tbonem3]

Thanks I will. But I was able to connect, code, flash etc no problem last week, now no. I hate this shit lol.

[ZiMMie]

Check the config file and make sure the right path for edibas ECU folder is there.

[Tbonem3]

I too am having issues with "unkwon/unsupported"

My car works perfectly, I've been using the standard tools fine, I have a proper cable. I don't get it, it was just working fine last week. Now I can't communicate. Checked drivers, com1,latency, obd.ini in Ediabas folder. Anyone have an idea? I'm getting 2 black dots in INPA (cable/ignition).

Only new thing is a new battery, but I don't see how that would matter. I coded for it and registered it.

[Tomba]

I wrote before, no obd after rsa bypass

Well, if BDM doesn't work either your only solution would be to get ISN from CAS and find another ECU.

[Kinder]

I wrote before, no obd after rsa bypass

[Tomba]

Not sure, i needet dump for ews matching, before was connection by can, now not.

Can you try to flash stock file? Or flash ECU with WinKFP?

I believe MSS65 is short ISN and MSS60 long ISN. From all MSS65 I did RSA bypass on it couldn't find ISN. ISN in Terras program searches for long ISN, must be the reason.

[Kinder]

Not sure, i needet dump for ews matching, before was connection by can, now not.