Mini R56 and R60 Bosch MEV17.2.2 Immo Off, Original File and CAS Alignment

Mini Cooper R56, 2011, N16 engine. The DME was swapped for a used one after the original suffered a coolant leak into the connector. Now the car cranks, catches for half a second and stalls. ISTA reports an ISN mismatch between DME and CAS. Label on the DME: 0261S07212, Bosch MEV17.2.2. Two ways out of that, and which one you pick depends on what you want the car to do afterwards.

Where MEV17.2.2 is fitted

Bosch MEV17.2.2 runs the naturally aspirated N16 1.6 in the 2010-2015 Mini Cooper and One (R56 hatch, R55 Clubman, R57 Convertible, R58 Coupe, R59 Roadster) and the R60 Countryman and R61 Paceman with the same engine. The turbocharged Cooper S with the N14 runs MED17.2 instead, and the N18 Cooper S runs MED17.2.2. Don’t order a file across those lines; they share nothing useful.

The two routes

CAS alignment (keep the immobiliser)

The DME holds an ISN, the CAS3+ holds the same ISN, and they compare at start. With a used DME you either write the car’s ISN into the used DME, or read the DME ISN and write it into the CAS. Tools that do this over OBD or on the bench for R56/R60: Autohex, AVDI and ACDP. The dealer way is ISTA-P with a new DME only. Alignment is the clean answer: the car stays factory, keys stay coded, no questions at inspection.

Immo off (skip the check)

An immo off file on the MEV17.2.2 removes the ISN comparison inside the DME. The CAS still has to accept the key to switch terminal 15 and release the starter, so the car isn’t running without a key; it’s running without the DME caring which CAS it’s bolted to. Handy when the CAS is an encrypted CAS3+ your tool can’t read, when the used DME’s ISN is unreadable, or when you’re chasing a no-start and want to rule the ISN out in ten minutes.

Original files

Original (stock) dumps for MEV17.2.2 are what you need after a failed remap write, a corrupt flash from a jump-start gone wrong, or a DME that reads with a checksum error. They’re listed by the Bosch 0261S number and the 1037 software number on the label. A few in stock:

• MINI COOPER R56 MEV17.2.2 0261S07212 1037525766 DUMP (and MINI COOPER R56 MEV17.2.2 0261S07212 1037525766 IMMO OFF DUMP)
• MINI COOPER R56 MEV17.2.2 0261S06125 1037505528 07612195 DUMP
• MINI COOPER R60 MEV17.2.2 0261S08678 1037525766 0089V10WJ20BRKES8 DUMP
• MINI COOPER R60 MEV17.2.2 0261S06663 1037512188 1037551989 DUMP
• MINI COOPER R60 MEV17.2.2 0261S06663 08656897 1037512188 1037551989 DUMP

Two different 1037 numbers on one label means the unit has been updated once already; send both. Writing a stock dump does not change the ISN on most versions, but read the DME EEPROM/ISN area before writing anything, so you have it if you need it later.

Reading the DME

MEV17.2.2 has TPROT. KESS V2, KESS3 and Autotuner read and write it over OBD on most software versions, which is enough for a stock file or a remap. For immo off and for anything involving the ISN, read it on the bench or in boot mode with KTAG, FoxFlash, New Trasdata or KT200, so we get the full flash and the EEPROM. The OBD, bench and boot guide shows which pads to hit.

Questions we get

I wrote immo off and it still won’t start.

Check the CAS first: does terminal 15 come on, does the starter engage? If not, the CAS isn’t accepting the key and no DME file fixes that. Then check the DME reads back correctly; a partial write is a common cause.

Can I align the CAS instead, after the fact?

Yes. Write the original file back, then do the ISN alignment. Nothing about immo off is permanent if you kept your reads.

Will ISTA complain about immo off?

It won’t flag the file, but it may log an ISN-related entry that keeps returning. Clear it and move on.

Order from the MEV17.2.2 page or the immo off and original file categories, or send the DME read plus the CAS label through the request form.