Bummer!! As I said -it was a guess.
Yes, I'm aware of GITHUB and "More Incredible Bash" albeit I've not used the software to convert a Japanese MIB. I guess you could try - but be aware that this type of exercise is a one-way-street meaning that once you go down this route there is no way to reset to the original set-up.
Of course in this case, the original set-up is of little value - so the lost option ain't worth much!!
If the "More Incredible Bash" method bricks the Japanese MIB, and you pursue a MIB replacement - you should know that you will encounter a mechanism called "Component Protection" (CP). This is a special protocol that VW uses in the Golf mk7 supposedly to combat the black-market trade in stolen parts - but in reality, I suspect that the real purpose of CP is to enhance the role of dealers!!.
Anyway, CP works like this: every time that you turn-ON the ignition, a CP software routine is run which requires that the primary modules in the car disclose their identity. The Address 19: CAN Gateway (J533) module in your VCDS scan report then compares each of the reported module identities against an encrypted master-list of modules that has been authorized by VW for this car's VIN. Alas, the MIB is a member module of the CP "constellation" - not all of the car's modules are in this category .
If any of the responding module identities in the CP interrogation process differ from those in the authorized list, a CP error is generated in the fault memory of the offending module. Ironically, the normal consequence of a CP error on the
MIB is no audio - yes, the same symptom as currently exists on the Japanese MIB!
So- the ONLY formal way to delete a CP error is to have a dealer insert the new module's identity into the car's encrypted master-list of authorized modules. That said, it is possible to hack the MIB software to deal with the loss of audio caused by a CP error - but this normally involves the very unofficial services of a third party
Don
Yes, I'm aware of GITHUB and "More Incredible Bash" albeit I've not used the software to convert a Japanese MIB. I guess you could try - but be aware that this type of exercise is a one-way-street meaning that once you go down this route there is no way to reset to the original set-up.
Of course in this case, the original set-up is of little value - so the lost option ain't worth much!!
If the "More Incredible Bash" method bricks the Japanese MIB, and you pursue a MIB replacement - you should know that you will encounter a mechanism called "Component Protection" (CP). This is a special protocol that VW uses in the Golf mk7 supposedly to combat the black-market trade in stolen parts - but in reality, I suspect that the real purpose of CP is to enhance the role of dealers!!.
Anyway, CP works like this: every time that you turn-ON the ignition, a CP software routine is run which requires that the primary modules in the car disclose their identity. The Address 19: CAN Gateway (J533) module in your VCDS scan report then compares each of the reported module identities against an encrypted master-list of modules that has been authorized by VW for this car's VIN. Alas, the MIB is a member module of the CP "constellation" - not all of the car's modules are in this category .
If any of the responding module identities in the CP interrogation process differ from those in the authorized list, a CP error is generated in the fault memory of the offending module. Ironically, the normal consequence of a CP error on the
MIB is no audio - yes, the same symptom as currently exists on the Japanese MIB!
So- the ONLY formal way to delete a CP error is to have a dealer insert the new module's identity into the car's encrypted master-list of authorized modules. That said, it is possible to hack the MIB software to deal with the loss of audio caused by a CP error - but this normally involves the very unofficial services of a third party
Don
Last edited: