Hi, could anyone please help me with retrofitting, I did every step, from buying the MIB 2 unit and display, to flashing it with "mib-std2-pq-zr-toolbox" but when I turn the ignition on, the display turns on with standby clocks that I can scroll through (different faces ), but none of the buttons do anything (parking sensors normally show up),(by the blue dev screen on the photo below I know that they work even on this screen, they just don't do anything). But when I connect diagnostics, the screen flashes with standard interface for a moment and the turning back to clocks, then after choosing module 5F Multimedia, the screen comes alive, everything works, buttons, touch, with that I was able to change language from Russian, update the software and everything, but when I disconnect the diagnostics, it goes back to clocks.

The software is updated to version 480 (photo is before the update) but even then it is the same.

After disabling component protection from the toolbox, it still shows up as a fault in diagnostics

Would appreciate any help.

you should check with pab567, he is the MIB guru around here

@pab567 Would you please be able to help ? I've found out that you need ODIS coding to remove the CP, is it a necessity or Would I be able to do it through SD card (green menu) or OBD11 ?

In the future, I'm planning to compile every bit of information to sum it up and make a more straight forward guide, because when I did it, there were a lot of different guides and none of them were full. Each time I had to take some information from different sources, a bit of my knowledge and compile everything to make it to this point, so I would really appreciate the help.

I understand that pushing on/off button does not poer the unit up?

The unit is always on standby (the clocks), and no matter what I press, it doesn't react, but when I plug in an OBD11 and go to 5F, it comes alive and works like it should tomorrow I will check if it at least reacts to holding the power button in that state

and sorry for my late reply, I forgot to turn on push notifications

Edited 15 March15 Mar by vvojta

Are all cables fully connected? What is the part number of the display? Have you already completely reflashed the unit's firmware? I do many MIB1 conversions, but I've never encountered this problem before.

Where you buy the Unit?

You have a Firmware Train JUMP, this Update was correct done?

Edited 16 March16 Mar by Cairus

2 hours ago, Cairus said:

Are all cables fully connected? What is the part number of the display? Have you already completely reflashed the unit's firmware? I do many MIB1 conversions, but I've never encountered this problem before.

I think they are, because when I connect OBD 11 And open 5F, it works normally. I will try to film a video of it later this day.

The part number

Display: 5E0 919 605 H

Unit: 5Q0 035 840 B

Yes, I flashed it with toolbox master and this software MST2_EU_SK_ZR_P0480T

2 hours ago, Cairus said:

Where you buy the Unit?

You have a Firmware Train JUMP, this Update was correct done?

Second hand from a site similar to eBay (Czech form of eBay)

I think it was done correctly, but I don't know how to tell, everything works but only with the diagnostics tool

Edited 16 March16 Mar by vvojta

With mib1 all works fine

Which Model Year?

Edited 16 March16 Mar by Cairus

Just now, Cairus said:

With mib1 all works fine?

Before retrofitting, everything worked fine

When you Change Back? Everything fine?

Just now, Cairus said:

When you Change Back? Everything fine?

I will try when I get back home, but when I was changing the units back and forth during the flashing, everything worked

How you Install the ToolBox? The partnumber is MIB2 Bolero with one SD Card

I had to connect it to the back of the unit using jumpers and signal converters to connect it to the PC and flash it trough Putty. Then the update was done using an SD card

OK, 👍

1) Check im Service Menü "HMI Skin Change" what is there aktiv?

2) reflash Firmware without Main & CPU emergency and without ESD(ToolBox)in Swdl Menü

Edited 16 March16 Mar by Cairus

Just for clarification or more possible ideas for solution, it did the same thing when I bought it and plugged it in without any modifications, could it be because of CP ? When I scan the car, there is a fault for CP and incorrectly coded control module in 5F (multimedia) and CP in 19 (gateway)

In a bit I will go and have a look for the HMI skin

CP Error is Not the Problem, you have done CP Patch?

I have done it with the toolbox, but I've found out, that you need ODIS for full removal

The error for incorrect coding is U101400

Yes Odis online for remove CP

Incorrect Coding is Not the Problem for Touch

Which Mode have HMI Skin?

This is the skin selection

Tried all of them, none of them prevent the issue

Correct is 65skin

Show me Update History and Software overview

Your Screen have 6,5"?

Edited 16 March16 Mar by Cairus