Why when make key CAS4+ we put isn from dme ? other interface make key without isn.
Can I put isn form dump cas4+ or must read everytime dme/dde ?

This is CAS4+, all sensitive data are encrypted (ISN, Key info,...etc)Autohex will need DME ISN to decrypt these data and then it can add the key.

Which means that we can't make key for MSD85, MSD87 based F10s?

Do we need isn for Cas4+ EWS Active even if we have working key???

Yes tibi 🙂

Which means that we can't make key for MSD85, MSD87 based F10s?

unfortunately looks like that

1 question > In the beginning procedure - how do we know to grab ISN if needed before downgrading ? <

Made copy key for 2007 Mini and after downgrading the dash did not turn on . So I elected to restore > grabbed the ISN > downgrade > key from file option 4 .... OK

Next Key copy was 2010 3 series > pulled ISN ( 20 MIN !! ) > downgrade firmware > add key through file > restore .... I did not need the ISN ,

Thanks

I create key for MSD85 many times, where your problem ?

Even when EWS5 is active?

xh...e im....ol:

1. FEM/BDC support emergency switch ON: FEM/BDC Key Learn->Emergency switch ON
2. Support read ISN from original key(even key was disabled): FEM/BDC Key Learn->Read ISN from original key
3. FEM/BDC support close/open transport mode: FEM/BDC Key Learn->Exchange FEM/BDC->Close/Open transport mode
4. !!!New Function: ECU/CAS ISN!!! (Menu->Key Learn->ECU/CAS ISN)
Support OBD exchange used or new ECU module, no need open PCB
Support OBD exchange used CAS3+/ISTAP module, no need open PCB
Support exchange used or new ECU module with "ECU dump file"
Support exchange used CAS3+/ISTAP, CAS4(1L15Y, 5M48H) with "CAS dump file"
(1). E-Series
(a). OBD read ECU ISN: MSV80, MSV801, MSD80, MSD81, MSD802, MSD812, MSD851
(b). OBD read/write ECU ISN: ME17N45(N45 Tricore), ME17N46(N46 Tricore)
©. OBD read/write ECU ISN: MEV17_2(N12 Tricore), MED17_2(N14 Tricore), MV1722(N16 Tricore), MVD1722(N18 Tricore), MEVD174K(N20, Tricore), MEVD176K(N55 Tricore), MVD1727(N18 Mini Tricore), MEVD17KW(Tricore)
(d). OBD Read/write CAS ISN: CAS3+(0L15Y, 0M23S), ISTAP version. Encrypt verison require working key support
(e). Support write new ISN to ECU flash dump file, fix checksum: MSV80, MSV801, MSD80, MSD81, MSD802, MSD812, MSD851
(f). Support write new ISN to ECU eeprom dump file, fix checksum: ME17N45(N45 Tricore), ME17N46(N46 Tricore)
(g). Support write new ISN to ECU eeprom dump file, fix checksum: MEV17_2(N12 Tricore), MED17_2(N14 Tricore), MV1722(N16 Tricore), MVD1722(N18 Tricore), MEVD174K(N20, Tricore), MEVD176K(N55 Tricore), MVD1727(N18 Mini Tricore), MEVD17KW(Tricore)
(h). Support write new ISN to CAS3 eeprom dump file, fix checksum: CAS3+(0L15Y, 0M23S), ISTAP version. Encrypt verison require working key support
(2). F-Series(some F-series ECU don't support read ISN from OBDII)
(a). OBD read/write ECU ISN: MEVD1724 (N20 Tricore), MEVD1725 (N13 Tricore), MEVD172Y(N55 Tricore), X63TU(S63TU, N63TU)
(b). Support write new ISN to CAS4(1L15Y) eeprom dump file, fix checksum: CAS4(1L15Y)
©. Support write new ISN to CAS4(5M48H) eeprom dump file, fix checksum: CAS4(5M48H). Encrypt verison require working key support
(3). Some function in ECU/CAS ISN require download VVDI2 configuration file: Online Update Tool(v4.9.0)->Menu->Software Update and Update Information->Configuration file Update
5. Support read CAS3+(ISTAP) EEPROM from OBDII(This is not full EEPROM, Support make dealer key, DON'T WRITE this file back to CAS)
without a functioning key - f series? I doubt

hi there. i am new and this is my first post.
i have vvdi2 and i tried to read isn from msd80...no success. can connect to ecu but cannot read. many features advertised but does not work.

This is Autohex forum for Autohex users...If you have it, use it, it's pretty straight forward for MSD8X.