[MIB-Wiki]

Success! The update took about 23 minutes, completed normally, and after rebooting itself the Maps and Nav work as expected. The the new map even has my little private street shown, so it doesn't look like I'm off-roading the last few hundred feet to my home!

Next I'll try to use these same maps to update my 2016 Audi A3...

Nice!
Still strange, what you have seen 1st...

View attachment 42298

This is MHIG --> MIB1 Harman High.
Maps are actually the same, but unit also has to be patched.
There is no ready to use solution I'm aware of.
I could help you for the manual way.
D-Link, PC, time and some nerves needed

The maps I finally got installed in my Cayman claim to be from 2022. Whatever they are, they are definitely newer and more complete than the 2018 maps that shipped with the car.

Maps on your unit have been from 2016. Here from your units backup:
NavDB: P60_N60S5MIBH3_NAR_NT_Q3.16

BTW, so is that also work for Audi? I have a 2013 Audi S5 which never have the navi map update and also don't have carplay or AA (not even an option back in time). So is there any luck to have AA enable on an old Audi? or will that tricks able to update the navi map?

That will be a MIB1 unit, maybe also Harman High (MHIG, like shown above). In that case, maps will be same, but you also would need a patch made and installed manually.

 

[MIB-Wiki]

@MIB-Wiki The version number is correct but sure how to verify that all of NAR is actually there?

Try to install again the normal way.
NORMALLY you will see which parts are already on unit.

 

[Arne]

This is MHIG --> MIB1 Harman High.
Maps are actually the same, but unit also has to be patched.
There is no ready to use solution I'm aware of.
I could help you for the manual way.
D-Link, PC, time and some nerves needed

I'd need to buy a pair of the D-Link adapters, since neither of my MacBook Pros have an ethernet port. Or maybe a long Cat5 cable from the car to the iMac on my garage workbench. Don't need Putty or similar, I'm adept at using the Mac Terminal to SSH into Linux boxes. But in the end, it's not worth it. I can't recall the last time I opened the navigation in the Audi.

 

[danchee]

Looks like if you have had Sima enable AA on your PCM, the AIO patch would not apply anymore. I wonder if what he did was essentially do the GEM update

First perform the basic MIB install. After the PCM reboots (3 times), go back and install the correct AIO patch for your PCM model. (Find the version numbers in SWDL.) Then go back in and apply the SVM error fix.

I think at this point AA was activated. My car already had CarPlay. Activating Nav took two or three attempts, first was the basic activation, and then there was a second step listed. I may have had to go back and apply the SVM fix again before it finally worked when I pressed the NAV button.

Also note that my car already had the factory GPS antenna installed because it was ordered with Porsche Connect (w/o Nav). Obviously Nav won't work without an antenna.

What is the "SVM fix"? My PCM was previously activated by Sima so I can't use the AIO patch. I wonder if I can just patch Nav and have it work. In the screen on checking antenna, I have the result as "Antenna OK -> GPS Antenna is connected" and "Antenna Open ->no GPS Antenna connected". Does this match what you had before activating? I do have Porsche Connect w/o Nav.

 

[Arne]

I found this in the M.I.B. readme file:

- SVM error has to be cleared via M.I.B. function in GEM after installation

Apparently this is an a fault code that pops up during the patching process. Once M.I.B. is installed, there is a menu item to 'fix' or clear the SVM code. I installed M.I.B, ran the SVM fix, installed the AIO patch, and then ran the fix again, just to make certain. In fact, I may have run it a third time after the Nav enabling, as it didn't seem to work immediately. I can't recall for certain, but that may have been when the Nav started working, I can't recall for certain.

As for the GPS antenna, I never did see the "Antenna OK" message. Mine said something like "Antenna status" and the next line was all the GPS coordinates including altitude.

 

[Westcoaster]

Looks like if you have had Sima enable AA on your PCM, the AIO patch would not apply anymore. I wonder if what he did was essentially do the GEM update

What is the "SVM fix"? My PCM was previously activated by Sima so I can't use the AIO patch. I wonder if I can just patch Nav and have it work. In the screen on checking antenna, I have the result as "Antenna OK -> GPS Antenna is connected" and "Antenna Open ->no GPS Antenna connected". Does this match what you had before activating? I do have Porsche Connect w/o Nav.

I too had Sima enable AA, It is my understanding that the patch file needs to be run in order to enable NAV and the other things, as it is a package deal like you I tried to run the patch file but could not.

Because I optioned factory NAV when the car was built, so of course I have a GPS antenna module, this is what the status screen looks like for it in GEM, a working antenna that can see satellites will show this kind of display.

 

[danchee]

I figured it out this evening. Thanks for the information. Essentially what I had to manually do is add the FEC to the current setup. Sima essentially did the whole GEM thing remotely. Did not even need to run the SVM clear function. Once I enabled NAR maps, FEC and voila, everything just works. Was even able to enable the Android Auto icon! Now if only I can make it so when you long press the "Voice assistant" button on the stalk, it would trigger Google Assistant without the error about not having a CarPlay device attached. It still works but just the aesthetics of having that message pop up is not ideal.

 

[MIB-Wiki]

I found this in the M.I.B. readme file:

- SVM error has to be cleared via M.I.B. function in GEM after installation

Apparently this is an a fault code that pops up during the patching process. Once M.I.B. is installed, there is a menu item to 'fix' or clear the SVM code. I installed M.I.B, ran the SVM fix, installed the AIO patch, and then ran the fix again, just to make certain. In fact, I may have run it a third time after the Nav enabling, as it didn't seem to work immediately. I can't recall for certain, but that may have been when the Nav started working, I can't recall for certain.

As for the GPS antenna, I never did see the "Antenna OK" message. Mine said something like "Antenna status" and the next line was all the GPS coordinates including altitude.

SVM (Software Version Management) error only pops up after running a FW update.
It has nothing to do with M.I.B itself.

M.I.B only makes it easy to clear, otherwise it has to be done via OBD and some XOR calculation.

 

[danchee]

Is there a way to update the FW on the PCM without going to dealer? Also is it safe to update after the patches or do we need to revert to stock first?

 

[danchee]

Updating map now. Just did it using Nav->Opt->Set Nav-> Update map. Slooooow though reading from SD card 😂 map was from 2017/2018 when the car was made.

 

[MIB-Wiki]

Is there a way to update the FW on the PCM without going to dealer? Also is it safe to update after the patches or do we need to revert to stock first?

Yes, FW updates can be installed.
However, only a POG24 FW update is available for US version publicly.

To be honest, newer FW does not bring new stuff and it is anyway not documented what was changed.

Best is to patch stock FW on unit.

 

[Westcoaster]

Updating map now. Just did it using Nav->Opt->Set Nav-> Update map. Slooooow though reading from SD card 😂 map was from 2017/2018 when the car was made.

Yes, very slow, I found it took nearly 30 minutes to load the map update! Interesting the path you took, it seems mine is a bit longer! Starting with the PCM buttons: Home, Car, Set (on screen), System, Software Update, Load Update, then select the SD slot where you put the extracted Navigation DB and follow the prompts. The system will begin the updates and give percentages until completion.

 

[ians]

Yes, it is debugged now and and working POG11.

Known issues:

• button color is slightly off
• no button select animation

So is it ready to move out from beta version now?

 

[MIB-Wiki]

Yes, can be used.

 

[Westcoaster]

So is it ready to move out from beta version now?

If I may suggest, clean quick format SD card, extract AA_button_beta.7z to the root, insert in PCM, enter GEM and navigate to POG11, enable AA button.

 

[fontana302]

I have Factory Sat Nav - ROW & are attempting to upload the latest 2022/23 maps downloaded from mib.mibsolution.one.

I have an issue where it aborts half way through utilising the Nav->Opt->Set Nav-> Update map option & asks for a second SD card to be installed about 57% of the way through, though all of the files are installed on a 64GB SD card fromatted to exFAT as the total file size is greater than 32GB)

I have added the FEC 063D0099 to addFecs.txt & created a FecContainer.fec using the "Edit FecContainer.fec based on addFEC.txt in patch folder" script which I have confirmed updated based on the PCM backup similar file.

Do I need to run #2 below as well to enable in the PCM?

I had AA previously installed by a third party prior to realising this thread existed & I installed the AA button successfully using the AA_button_beta.7z extract.

I would have thought the upload wouldn't have started at all if I didn't have the FEC installed correctly.

All help appreciated.

 

[Westcoaster]

I have Factory Sat Nav - ROW & are attempting to upload the latest 2022/23 maps downloaded from mib.mibsolution.one.

I have an issue where it aborts half way through utilising the Nav->Opt->Set Nav-> Update map option & asks for a second SD card to be installed about 57% of the way through, though all of the files are installed on a 64GB SD card fromatted to exFAT as the total file size is greater than 32GB)

I have added the FEC 063D0099 to addFecs.txt & created a FecContainer.fec using the "Edit FecContainer.fec based on addFEC.txt in patch folder" script which I have confirmed updated based on the PCM backup similar file.

Do I need to run #2 below as well to enable in the PCM?
View attachment 42698

I had AA previously installed by a third party prior to realising this thread existed & I installed the AA button successfully using the AA_button_beta.7z extract.

I would have thought the upload wouldn't have started at all if I didn't have the FEC installed correctly.

All help appreciated.

Should not be "exFAT", should be FAT32... perhaps find a smaller SD card, 32GB is more than large enough for the NAV DB.

Also if you simply patched the FW with the file matching your firmware version on the PCM you should not have had to alter the FEC container at all as it adds all of the needed FEC's during the process, from your wording did you manually add FEC 063D0099?. You simply needed to enable NAV through GEM then use the PCM user menu to update the maps.

 

[fontana302]

Thanks Westcoast.

I have factory NAV & factrory installed Apple Carplay like yourself which was ordered from new, but I am in Australia. I didn't patch anything to do with NAV or car, but as I'm an Android phone user, I had AA installed by the same third party as you had done, so my config as a starting point is exactly as yours was except a different part of the world.

I downloaded ROW NAV files (from the same location as you downloaded the US Nav Files). The ROW NAV Map files downloaded are larger than 32GB, hence the the need for the 64GB card.

First thing I did was a "clean" install just as you did - but mine failed as described.

I then tried different cards, reformatted, multiple downloads from the site & installs through the PCM using different approaches & the same error every time.

That FEC I mentioned is NOT in any of the default addFecs.txt files, so it wouldn't have been uploaded unless manually edited (whichj is what I did).

As a potential solution after all that I ran "Edit FecContainer.fec based on addFEC.txt in patch folder" script/option just to see if it made any difference re map upload - No it didn't. I am unsure if that simply creates FecContainer.fec & writes it to the PCM or if you need to install it as well (it may already be there for all I know placed by the third party who installed AA).

I have NOT installed personnaly any PATCHES as AA & everything work & always has. I did install the AA button image aftyer the above just for kicks & it worked perfectly

All I want to achieve is to get the current maps uploaded & wondering why they won't. It's either FEC or SD Card related.

To get the files down to less than 32GB I have to delete some - happy to do that, but which ones? ROW map upload has NO option to select any. The error occurs at any stage from as low as 4% to as high as 86% install before the error occurs asking for 2nd SD card. I remove the same card & reinstall, hit continue - keeps asking so I have to cancel.

 

[MIB-Wiki]

If you edit addFEC.txt, make sure that you use something like notepad++.
Normal Windows notepad will change line end format, blocking M.I.B from using the file.

Get a fresh addFEC.txt and edit with notepad++.
This should work fine.

If your unit was previously patched by sima you also have to apply the M.I.B patch.
(He is replacing the public key for FecContainer signing on unit with his own. Enabling him to sign his own FecContainer, however this is only working with his private key, which we do not have)
So keys added by M.I.B will be invalid. After patching they will be accepted.

 

[Westcoaster]

Thanks Westcoast.

I have factory NAV & factrory installed Apple Carplay like yourself which was ordered from new, but I am in Australia. I didn't patch anything to do with NAV or car, but as I'm an Android phone user, I had AA installed by the same third party as you had done, so my config as a starting point is exactly as yours was except a different part of the world.

I downloaded ROW NAV files (from the same location as you downloaded the US Nav Files). The ROW NAV Map files downloaded are larger than 32GB, hence the the need for the 64GB card.

First thing I did was a "clean" install just as you did - but mine failed as described.

I then tried different cards, reformatted, multiple downloads from the site & installs through the PCM using different approaches & the same error every time.

That FEC I mentioned is NOT in any of the default addFecs.txt files, so it wouldn't have been uploaded unless manually edited (whichj is what I did).

As a potential solution after all that I ran "Edit FecContainer.fec based on addFEC.txt in patch folder" script/option just to see if it made any difference re map upload - No it didn't. I am unsure if that simply creates FecContainer.fec & writes it to the PCM or if you need to install it as well (it may already be there for all I know placed by the third party who installed AA).

I have NOT installed personnaly any PATCHES as AA & everything work & always has. I did install the AA button image aftyer the above just for kicks & it worked perfectly

All I want to achieve is to get the current maps uploaded & wondering why they won't. It's either FEC or SD Card related.

To get the files down to less than 32GB I have to delete some - happy to do that, but which ones? ROW map upload has NO option to select any. The error occurs at any stage from as low as 4% to as high as 86% install before the error occurs asking for 2nd SD card. I remove the same card & reinstall, hit continue - keeps asking so I have to cancel.

I had a similar experience the first time I tried to upgrade the NAV DB on my car, it turned out to be bad connections between the microSD card and the adapter I was using, failure to load at different point each time. I used a different adapter and the load progress faster/smoother without error to completion.