MQB – Past, Present, and future. Key programming IMMO V

Many of the people I know appear to be entangled in negativity when discussing platforms, cross platforms and brand engineering on behalf of the OEMs. My opinion is that they are, at the very least, not as bad as people want to make them. I mean, MQB is always the first to be beaten on when talking about how everything is the same nowadays. The reality is that because you can use the drivetrain from an RS3 and put it in a T8 Transporter, this opens a huge door for tuners and the aftermarket in general. Many upgrades are readily available from scrap yards which makes it cheaper for people to upgrade their base model cars. Not just that, but all of the cars in the MQB platform manage to retain their individuality even though they are “the same” underneath. I am a proponent of platforms and am a particular fan of the MQB. The only thing is that a €35,000 Passat in 2016 now costs €80,000…

I. History.

MQB was conceived in the early 2000s when Ferdinand Piech wanted to “optimize costs”, the idea of a Modular Construction Platform (Modularer Querbaukasten) was first thrown around in engineering meetings back then. At the time VAG was obviously on some interesting substances as they were busy producing twin turbo V12 diesels, V10 turbo diesels, V10 twin turbo gasoline and W12, W16 monster engines at the same time. Piech was obsessed with that very Germanic, very Prussian “perfection” which as we all know requires a bunch of money to construct. We know where this spending eventually leads to and we know that VAG bought Porsche which in return bought them back and so on but the result is what is important to us. 2012 came and the engineering team was now ready to debut the MQB platform – an optimization strategy to build all cars on the same platform and have variations of it. The MQB came out with 15 vehicles of which there were variants. I am not going to list them all but the A3 8V and Golf 7 were the standouts together with the Octavia III. You can check them on Wikipedia if you would like. These cars may not have been as sexy as the firebreathers of the Piech era, but they are still very individual and an occasional monster is still available.

II. IMMO V MQB description.

IMMO 5 is a popular platform and it is split into BCM2, MQB, MLB and now there are new evolutions. The part of the platform I would like to focus on MQB. Here is what the variations are:

1. MQB IMMO 5A

First generation variation on the MQB, most typically defined by having a V850 Renesas processor in the IMMO (Dashboard) module. Remember, in this variation you have the IMMO in the dashboard and the two words are used interchangeably. The First generation is defined by 16 bytes CS in the immobilizer, 16 bytes in the transmission, 16 in the ECU and the same in the ELV (if present). The key here holds the well…key to key programming. If you have a working key (Megamos-AES ID88), it has all the needed information for you to program a spare one. If all keys are lost, you need to read the CS from all of the modules participating in the IMMO system. All of the security related to key programming ends up being 16 bytes Component security stored in the immobilizer and  32 bytes (known also as sync data) Component Security split between all the modules above.

2. MQB IMMO 5B

Pretty much the same as IMMO 5A, with the distinct difference of having RH850 processors instead of the V850 for IMMO 5A.

3. MQB IMMO 5C

Here we have a bit of difference. We have an RH850 but the dash has a crypto core which currently prevents the world from freely programming keys to this car type. Cars based on this platform are models such as Tiguan, Polo and T-Roc (Not sure what other models, maybe all the models released after 2020 where the immobilizer is in the dashboard). We are currently preparing a function to allow MQB spare key adding, this is a unique to Abrites functionality which will allow you to program keys of the Hitag-Pro (ID5C)  The best option for adding keys for your customers, unavailable anywhere else!
I will discuss the topic of the current form of MQB with GOLF 8 based cars where there is a completely new structure of the IMMO system present. IMMO is no longer retained to the above-mentioned modules (i.e. dashboard). We have another module, similar to BCM but as I said, I will get into it in due course.

III.   Overcoming IMMO V MQB key programming problems. Q&A

I can hear you already. There are many problems we need to address.

1. What about Sync Files, I heard you need those to program keys. Why doesn’t Abrites use those?

• The internet will have you believe that without the notorious SYNC FILES you cannot program a key to an MQB car. Sync files are basically VAG files containing all 32 bytes CS which come by VIN for a certain car, you load the file, you load also the CS of the immobilizer, and you are allowed to program keys. This is great if you have access to said files. Our approach is a bit different. We have set ourselves the goal of never needing anything from the manufacturer in order to allow you to do your work effectively. We prefer to work by extracting all the necessary information from the particular vehicle itself and not from anyone else. This allows us to guarantee that our customers are truly independent and not tied to manufacturers and their wishes. Of course if you have the infromation from someone else, you can use it.

2. How do you obtain this information?

• We have a selection of methods for extracting the 16 bites CS of the immobilizer. The main of them is the ability to read the processors from the IMMO 5A and IMMO 5B type using the RH850/ V850 ZN085 programmer using a specific attack. This method is related to removing the dashboard, soldering the ends of the cables in the ZN085 set and reading it on a bench. Our method, although not perfect, is the best solution for the moment because it only requires minimal removal of components from the dashboard and requires no cutting. Just to give you a perspective – for example in our last revision of the ZN085 we managed to reduce the number of components to be removed by 40%. Another feature of our procedure is that there is no trace cutting required. If you are careful, you can literally leave the dashboard completely restored after performing the key learning procedure which is the true testament to your professionalism and our attention to detail.
• For the extracting the 32 bytes (sync data - necessary only if all keys are lost) you need to read ELV, ECU (master and slave if present), TCU.

3. What obstacles will I face when performing key learning on MQB?

• It is no easy task. You will face a few problems. For example – there are two types of ELV. Ones that allow you to read the Component Security and those that don’t. Quorivva type is not supported whereas Renesas are supported. Here you need to try and then find out. We have Crypto core ECUs and Dashboards – we are still figuring those out. Apart from that you can rest assured that we will be able to help you both with all keys lost and adding key.

4. So what’s new, why are you writing all of this?

• There is a reason for that. I mentioned above, there is the IMMO 5C type – the Tiguan, Polo and T-Roc, there are probably other models I am missing here, come with a crypto core in the IMMO module. For the moment the world of diagnostic tools does not support any type of key adding. These cars use the  Hitag-Pro type of key, the so called ID5C. We now have a solution in the final stages of development which we hope to release in the next few weeks. The solution we will offer you is to permit the programming of spare keys for these models. Here is one thing which will allow you to offer a completely new service to your customers and win new customers which will be turned away by any other locksmith. Here is why you- the Abrites customers will once again have the competitive advantage.

I will be back with more information, and we will hopefully have a video on the topic soon. Until then – try to have fun at work.
Alek