[Levanime]

there is a way and you can flash it,

you would need MHD license,
then contact MHD support and they will provide special files that fixes this mess

[TheNine90]

You can use same authentication key as normal BMW bootloader from your svt soll. These are the file to modify sec_ncdkeys.xml and sec_auth_l3.xml
Solution is from bimmerscene

[pengshengshi]

You can use same authentication key as normal BMW bootloader from your svt soll. These are the file to modify sec_ncdkeys.xml and sec_auth_l3.xml
Solution is from bimmerscene

Can you explain in detail how to modify it, thank you

[TheNine90]

Here is the solution from another forum.

If you want to avoid the base variant mapping error(s), you will also want to add the following two entries:


1. C:\Data\psdzdata\mapping\blmap.xml

Again, add an entry by duplicating the most recent appropriate entry for your specific DME, and adjust it to suit. In this case I only needed to change the key= value

<entry smac="false" eeComponent="DME-MEVD172G" byteorder="MSB" key="00001a90">DME2</entry

2. C:\Data\psdzdata\mapping\cvnpos.xml
Same thing for this entry. Duplicate most recent, adjust it for your application. My entry looked like this:

<entry key="BTLD-00001A90">1</entry>


First, calculate an SVT target as normal, you'll need it to reference the correct target BTLD version. You can also get your current "custom" BTLD version this way, you will be using that value below.

You need to add entries to two files that are used to authorize bootloaders by esys:

1. C:\Data\psdzdata\security\sec_auth_l3.xml

In this XML file, use text editor to duplicate the AuthenticationKey entry from the target btld version. In my case, it was for BTLD-00001A83. Duplicate this entry, and modify it as follows to fit the bootmod3 customROM btld version currently installed on your DME. The actual long string for keyData doesn't matter, just copy it from the prior entry.

</AuthenticationKey>
-<AuthenticationKey plain="false">
<BL_ID>btld-00001A90-00.00.00</BL_ID>
<keyData signatureScheme="BMWSigVerify" digestAlg="md5" type="21">76079F1FC3E7D4.......LONG STRING HERE</keyData>
</AuthenticationKey>

2. C:\Data\psdzdata\security\sec_ncdkeys.xml

Do the same for NCodSigKey entries. Again, the actual keyData string can be copied from an existing entry. I duplicated the entry for btld-00001a83, and adjusted it as follows:

</NCodSigKey>
<NCodSigKey plain="false" testKey="false">
<BL_ID>btld-00001A90-00.00.00</BL_ID>
<keyData type="21" digestAlg="md5" signatureScheme="BMWSigVerify">AC7C51151162F.......LONG STRING HERE</keyData>


At this point, open esys and save an SVT_ist. Open the SVT_ist in the SVT editor, expand dme2-12 folder, expand StandardSVK, expand CAFD, BTLD, and both SWFLs. Edit the patch versions to be Patchversion=000. Do this for all four(CAFD, BTLD, and SWFLs). Save this modified SVT as SVT_ist_mod. Use this modified svt ist, along with a standard svt target file to create a TAL as normal.

You should be able to program the DME entirely in one shot at this point. Hope this helps somebody someday.