We do not work "on MIB units" in general: each platform has its own supplier, its own firmware and its own typical faults. These are the 14 families that come across our bench, with what we hold in the archive for each of them.
For these there is a page with typical faults, brands and available updates.
Audi, Porsche, SEAT, Škoda and Volkswagen
62 firmware files in the archive
SEAT, Škoda and Volkswagen
43 firmware files in the archive
Audi, Lamborghini, Porsche and Volkswagen
25 firmware files in the archive
Audi and Volkswagen
17 firmware files in the archive
Škoda and Volkswagen
15 firmware files in the archive
SEAT, Škoda and Volkswagen
12 firmware files in the archive
Audi and Volkswagen
12 firmware files in the archive
Audi
9 firmware files in the archive
Audi
7 firmware files in the archive
We repair them like the others. They do not have a page of their own because we would have little to write on it: when the archive grows, that arrives too.
SEAT, Škoda and Volkswagen
Volkswagen
Audi
Škoda
Audi
The typical fault is in the audio output stages: the unit works but stops playing sound, and it is repaired at hardware level. The boot loop also shows up, as on the MHI2 units.
It is not written on the screen. The platform comes from the unit part number: you will find it on the label applied to the body of the device, or you can read it with a diagnostic tool in the identification of the radio and navigation control unit.
Knowing the make, model and year is not enough, and this is the point that trips almost everyone up: the same car, depending on the year of manufacture, the trim level and the destination market, can be fitted with different families. Two Golfs from the same year can have two platforms inside them with nothing in common, either in the hardware or in the files. That is why we always ask for the part number before saying anything: without it, any answer would be a guess.
If you send it to us we will tell you which family it belongs to, what we usually see break on that family and whether your case is among those we repair or among those that get solved by replacing.
Supplier, generation, brands it is found on and how many files we hold in the archive. The numbers are the real ones, updated at every publication.
| Code | Supplier | Generation | Brands | Files |
|---|---|---|---|---|
| MHI2 | Harman | MIB2 | Audi, Porsche, SEAT, Škoda and Volkswagen | 62 |
| MST2 | TechniSat Preh | MIB2 | SEAT, Škoda and Volkswagen | 43 |
| MH2P | Alpine | MIB2 | Audi, Lamborghini, Porsche and Volkswagen | 25 |
| MST2 | Delphi | MIB2 | Audi and Volkswagen | 17 |
| MOI3 | Preh | MIB3 | Škoda and Volkswagen | 15 |
| MOI3 | LG | MIB3 | SEAT, Škoda and Volkswagen | 12 |
| MPR3 | Aptiv | MIB3 | Audi and Volkswagen | 12 |
| MHI3 | Aptiv | MIB3 | Audi | 9 |
| MHS2 | Delphi | MIB2 | Audi | 7 |
| MEN3 | LG | MIB3 | SEAT, Škoda and Volkswagen | 5 |
| MIB REGIO | VW Group | MIB | Volkswagen | 5 |
| MS2P | VW Group | MIB2 | Audi | 2 |
| MEN2 | LG | MIB2 | Škoda | 1 |
| MHIG | Harman | MIB | Audi | 1 |
It depends on the family and on the fault. On some, the recurring defects are down to the memories, or they show up as endless reboots, and those are repairs we do on the bench. On others — the MOI3 and the Aptiv units — what we see most often is damage to the CPU, and there no repair exists: it goes to replacement, with the spare part coded to the VIN. When it is the second case we tell you before the part leaves, not after it has reached us.
No, and the code on its own is misleading. MOI3 LG and MOI3 Preh are the same platform in the group's logic, but they remain two devices built by two different companies, with different hardware inside. The firmware is tied to the part number, not to the code: a file for one does not go on the other. That is exactly why the archive is organised by part number and not by trade name.
Because the archive grows with the work. The families that come across the bench most often are also the ones we have most versions of; for the others we have what we have, and we prefer to say so rather than give the impression it is complete. The number next to each code in the table above is the real one.
No. Most of the work comes from electronics labs and specialist workshops, and it is for them that remote coding and trade terms exist. But we also take on the private owner who has a faulty unit and wants to understand what to do, with no difference in the quality of the work.
Send us the part number printed on the label and the symptom: we will tell you what to expect and how much it costs. Free diagnosis, no obligation.