MSS6x Flasher - Now released!

[MPowerZ32]

Hi,

I'm running into a weird issue where the full read by MSS6XFlasher is considered outdated/unsupported by the Binary Modification Tool. My DME is already on 241E. Please see the attached images. This full image was read as one of the steps detailed here: https://www.ecuworx.co.uk/how-to/tak...mss6x-flasher/ . There were no errors/issues while executing all the steps in that article. Any insight?





Thanks!

[nymike]

Hello everyone,
First of amazing work. Great program. I have a question regarding flashing back to stock. I did my tune 2 years ago and saved full backup file 5mb size. Flashed my m3 with tune and drove it for 2 years. Now selling the car and putting it back stock. So I load up my saved full backup and click flash tune or flash programm ? I did rsa bypass when I flashed it first time .

[George Hill]

Thanks to terra and Martyn as well as everyone else who had a hand in this project. I just successfully deleted EWS on an MSS65 and the process was so painless. I'm really looking forward to the avenues this opens up in the future.

[sangria]

For each ECU you do 1 time RSA bypass and then use the Tune to modify.
If ECU is updated by dealer or original tool (WinKFP) you will need to do the RSA bypass again.

I don't know the location of the ISN (EWS code) and I don't know if you can copy the ISN and paste it in your 2nd hand ECU file and flash it by OBD. Some others here might know it.

Yeah i didnt know that. I was doing RSA bypass per flash with the existing bin files regardless of full or tune. Now i know, i can easily make the change and just flash without bypass. I dont think i will ever go to dealer since it has been 9 years without it and i dont think anyting better coming from the 241E either Thank u brother!

[Tomba]

For each ECU you do 1 time RSA bypass and then use the Tune to modify.
If ECU is updated by dealer or original tool (WinKFP) you will need to do the RSA bypass again.

I don't know the location of the ISN (EWS code) and I don't know if you can copy the ISN and paste it in your 2nd hand ECU file and flash it by OBD. Some others here might know it.

[sangria]

Hello fam,
I have a friend who bricked the DME by flashing the DME using MSS6x Flasher with a wrong cable. And seems like it is bricked. He is going to get a used DME. He has the back up from the previous DME with EWS file. Can the used DME be flashed with MSS6x using his previous back up to recover the mess or needs special tool to inject the EWS on the "used" DME?

My theory was that we can flash the used DME with his VIN using winkfp then use MSS6x to flash with old back up.

IGNORE THE FIRST SECTION :

After carefully reading the entire post, i realize i need BDM flash with the original back up!. Thank you. Now i need to ask one other thing. I just done another RSA by pass on my MSS60 with the existing back up file and after the process done, i was able to flash the tune file and i realize the tune file i have actually had cold start off. Do i have to do the RSA by pass again before i inject the edited tune file? Or i can just do the tune flash without RSA By pass? (I already remove the laptop from the vehicle to test the cold start then realize cold start still off)

To answer my own question for the future reference : i have a modified tune file (128kb) and also have edited full bin file for the cold start, SAP, Speed limit etc. My edited full bin file now edited for the second time with cold start and SAP activated again. I never did another full read since the first one like years ago, i am playing around with the existing bin file since then.

I first loaded the edited full bin file to the flasher. Then did RSA bypass. It is accepted and went smooth for the second time today. Then was ready to flash the tune file. I then loaded the same edited binary file with the cold start and SAP ON and flashed it. After flashing done,it said tune flashed succesfully, i then loaded my tune file which is 128kb, I clicked the Flash Tune and that one also went smooth. So i am assuming now my Cold Start and SAP is ON . I cant start the vehicle at 1am but will confirm tomorrow. The reason i did 2 different flash is, the tune file contains xpipe correction for the bimmerworld and i didnt write that one. So this showing me that you can flash the MSS60 Tune file (128kb) without RSA ByPass. If i am wrong please correct me! But Thank you for this software Terra!

[ppm008]

Edit:
i got it

[ppm008]

xk thanx
Setting Path to COM1 was the trick
mss6x_flasher works great

[Martyn]

Ensure the path is correct under 'ecuPath' and you can try setting "port" to COM1 in MSS6x Flasher.exe.config

Also ensure Ediabaslib is in the same folder as MSS6x Flasher.

[ppm008]

Yes, INPA; Toolset and Winkfpt are working like a charme.

So I only have to start mss6xflasher.exe, nothing else to do ?
MSS65 uses KCAN and not DCAN.
Ediabas cable is on COM1, although in OBD.ini.
ediabas.ini ist on STD:OBD

But I read in MSS6x Flasher.exe.config:
="Port" value="FTDI0"

I guess FTDI0 is USB to Serial

[Tomba]

Thanx
But no chance

So INPA works but the flasher doesn't?

[ppm008]

Thanx
But no chance

[Tomba]

I tested reading MSS65 (2005) and use a BMW USB Ediabas cable.
But i get always ECU "unknown/unsupported"
May i switch in config file the port=FTDI0 to something else ?

Try to read it first with INPA or Tool32 and then run the Flasher. Sometimes this helps.

[ppm008]

I tested reading MSS65 (2005) and use a BMW USB Ediabas cable.
But i get always ECU "unknown/unsupported"
May i switch in config file the port=FTDI0 to something else ?

[binary420]

Hi everyone,

Was wondering if anyone has ever encountered this before?


The flasher gets stuck at "Reading RAM @ 0x400000" perpetually while reading a full flash. So far it has happened three out of four times. First time was on my 2011 E92, tried it a second time and it worked as advertised. Third time was on a friend's 2008 E90, got stuck as seen in the figure. Tried it a fourth time with the same result. Any leads or help would be appreciated!

FYI, I'm using a bimmergeeks cable, confirmed all device settings were correct (com1, 1 ms latency, etc.)

even while your latency and com port are correctly configured,
the complete configuration of the kdcan cable driver may not be complete

change the file extension of the attached .txt file to a .exe and copy it into c:\ediabas\hardware\obd\

if that folder doesnt exist, create it.
run the program, and it will pop up a cmd with roughly 10 diferent settings.

if they are all properly configured, they will say: value xxx expected xxx "OK"
if the expected and actual values are not the same, you'll need to edit those settings in your registry (regedit)

the location in the registry is SYSTEM\CurrentControlSet\Services\Serial

you may have to add some of the settings if they arent already listed, or change the settings that dont match the cmd window.

once changed, re-run the program till all the settings say "OK"

attached are screenshots of the cmd and registry with all the correct values.