RomRaider

So i'm looking through some roms and thought maybe it would be worth adding to the definitions how to virginise a DME on software 430056. I realise most of us would just use EWS delete, but for those that wish to keep EWS, this would help with re-syncing new DMEs.

From what i can tell, in order to virginise a DME you need to FF the range:
x3ED4 to x3ED9

I'm not certain on the next segment, but it looks like the range x3EE6 to x3EF1 also needs to be FF.

Can anyone confirm this is all that is required to clear the ISN?

x3ED4 to x3ED9 is the ISN - confirmed

setting that to FF should be enough

Yes writing FF to ISN is enough. In both ms42 and ms43. Remember make the full flash in boot mode. Otherwise the ISN is not overwritten.

After virginizing just do ews sync with inpa and everything works fine.

Caution.
I've had instances where I virginized it and did EWS sync, only to have the car start once, then it doesn't start. Sync EWS and it starts again.
When I re-read the fullflash, EWS remained at FF FF FF FF FF FF. It never updated the ISN. Not all DMEs did it, but some did, so it's better if you just write the ISN in yourself.

you're talking about the VIN number. ISN is overwritten.

Didn't check the address that ba114 provided. So I don't know if it is ISN or VIN. But I personally have written FF to ISN to virginize roms. It's easy to find just by searching "regensbu" ISN is always close to that.

Or are you talking about boot mode flash? I didn't have succes virginizing the roms without boot mode. The ISN was not overwritten to FF without. I used mss5x flash tool.

I always use boot mode for it. and thats exactly how I find the ISN as well. Works for many other DMEs/DDEs.

It's just a few that gave me troubles, so I just made it a habit of writing the ISN if it's available. Who knows if it was a DME problem or something else.


And correct, the MSS5x tool cannot write to the bootloader section where this ISN is stored.

MS43 Fullread ISN in 3ED4 - 3ED9
MS43 Fullread VIN in 3C40 - 3C4C

Mxx-Flasher dont write at fullflash isn ... need bootmode.

Good info guys thanks! Now if i can just get this flasher working.

for example
image 1 - correctly virginized ms43

image 2 - stock ms43

it is not enough to FF only isn on ms43...
everything should be FF up to "REGENSBU"

if you FF only 03ed4-03ed9, DME wouldn't remember ISN

Hey guys,

Thank you for the info. in this thread, it was a huge help. I was able to resync my DME that could not be synced via INPA with the error -

"Startwert verstanden, EWS und DME passen nicht zusammen"

Basically that the EWS and DME were not matched, even though they were the original stock parts. My DME had been bricked and I have been working to recover it.

Quick follow up question if any of you are still around after a year... would I be able to use the same 'virginizing' process to match any exact part DME to the car? Or did it only work because they were a matched pair already?

Thanks again!

Yes any dme is fine to virginize and sync ews.

Hello, I hope someone out there can help me.

I found this helpful thread from a google search while trying to virginize a used MS43 to replace the car's original MS43 DME. I understand that in order to erase the ISN, I will need to "FF" from 3ED4 - REGENSBU.

If I do the same for the VIN, and "FF" from 3C40 - 3C4C, will the VIN be erased and obtained when connected to the car?

Or is my best option to obtain the VIN from a fullread of the original ECU, and copy it into the donor ECU, while erasing its ISN?

I am using JMGarageFlasher, with a K+DCan cable, on a bench in bootmode.

Thanks!