Facelift MIB3 Map Update

alps26

Registered User
Joined
Mar 3, 2011
Messages
1,163
Reaction score
423
Points
83
Location
North West
I'm posting this map update process because I couldn't find this procedure for the Audi MIB3 system.

The Settings > Maintenance > Software Update option did nothing for me despite the MMI saying it found an update medium. You should try this first before proceeding with the steps below.

This needs to be done on a Windows computer, not a Mac. Make sure your car is connected to a battery charger. Do this at your own risk, I take no responsibility if you brick something. I'm only stating what worked for me as my maps were from 2022 and my Connect subscription has expired. My MMI software version is 3620.

  1. Log into your MyAudi account from your computer.
  2. Download the map - its around 29GB.
  3. Format your storage device to exFAT. It needs to be a minimum of 32GB, I used a 64GB SD Card
    1. There is a recommendation that you use a USB-C flash drive, but I got it to work with an SD Card and a USB-C SD Card adapter. I would recommend a USB-C flash drive as you dont need an adapter.
  4. Extract the Zip file to your storage device directly. This took 1.5hrs for me. You should only have 2 folders and 2 files on the root of the storage device once its done extracting.
  5. Plug the storage device into the USB-C port of the car.
  6. Switch ignition on and wait for the MMI to boot up. You should see it say 'Update medium found' after a few seconds. If it doesn't, then you need to check what was extracted to the storage.
  7. Hold 2 fingers at the very top right of the MMI screen. It will load into the red engineering menu.
  8. Choose the software update option.
  9. Follow the prompts on the screen. The MMI will do some checks then eventually ask you if you want to update.
  10. Leave it to update and don't touch anything. The update takes about an hour and I was able to lock the car and view progress from the window.
  11. Once complete, it will take you to a summary page, scroll to the bottom, tap Resume and the MMI will reboot. You may need to switch the ignition on if you locked the car.
  12. Check the map version (it can take a minute to populate so dont worry if its blank). Mine only went to 2023.12 but this could just be the last map I was eligible for.
I normally use the maps on Google or Apple Maps via CarPlay but the built in map gives a fallback option if those are not working for some reason.
 
Last edited:
If like me, the update only loads the first 4 stages and not the last, then call Jas at Midlands Vehicle Diagnostic (Derby), who will get it all done for you.
I didn't want the subscription of $140 pa, so I wasn't supposed to update the maps. I now have the latest 2025 maps.
 
  • Like
Reactions: alps26
Thanks, mine went through all 5 stages, but I tried this process on a friends RS4 last night and his came up with error 133 and only completed the first 4 stages like yours. I'll let him know about your contact.
 
Thanks, mine went through all 5 stages, but I tried this process on a friends RS4 last night and his came up with error 133 and only completed the first 4 stages like yours. I'll let him know about your contact.
That's the same code I got. What is needed is for the previous map files to be removed first (disc wipe). Jas, the fix guy, will also upload the latest firmware and map software and then clear all the faults. Mine is perfect and with the latest and greatest.
 
  • Like
Reactions: alps26
Thanks, mine went through all 5 stages, but I tried this process on a friends RS4 last night and his came up with error 133 and only completed the first 4 stages like yours. I'll let him know about your contact.
Updating this in case it helps someone as I fixed this on my friends 2020 RS4.

Error 133 is caused by the navigation database becoming corrupted, usually via an over the air update where there is an active Connect subscription. In the version information you will see this under navigation database:

IMG 2912

It can be resolved by wiping the nav database using VCDS:
5F > Basic Settings > Formatting Partitions of internal memory > Navigation Database (I forget the exact term but its obvious) > Go!

It takes a second and will say "not running" when complete. Reboot the MMI by holding down the power button. You can then load the map via USB once the MMI has settled and it should work.

As a side note, updating the map via the engineering menu will leave an SVM fault code on the 5F module.

You should be able to upload the maps without going into the engineering menu (won't leave SVM fault code). It can take 1-2mins for the update button to show after inserting the USB and the initial "update medium found" message is displayed.

IMG 2911

Once complete, clear the fault codes in the 5F module with VCDS and check they don't return.
 
Last edited:
Updating this in case it helps someone as I fixed this on my friends 2020 RS4.

Error 133 is caused by the navigation database becoming corrupted, usually via an over the air update where there is an active Connect subscription. In the version information you will see this under navigation database:

View attachment 282759

It can be resolved by wiping the nav database using VCDS:
5F > Basic Settings > Formatting Partitions of internal memory > Navigation Database (I forget the exact term but its obvious) > Go!

It takes a second and will say "not running" when complete. Reboot the MMI by holding down the power button. You can then load the map via USB once the MMI has settled and it should work.

As a side note, updating the map via the engineering menu will leave an SVM fault code on the 5F module.

You should be able to upload the maps without going into the engineering menu (won't leave SVM fault code). It can take 1-2mins for the update button to show after inserting the USB and the initial "update medium found" message is displayed.

View attachment 282761

Once complete, clear the fault codes in the 5F module with VCDS and check they don't return.
Hi, do you have the file or the link to download it?
 
Hi again, another question.
You wrote:

6. Switch ignition on and wait for the MMI to boot up. You should see it say 'Update medium found' after a few seconds. If it doesn't, then you need to check what was extracted to the storage.
7. Hold 2 fingers at the very top right of the MMI screen. It will load into the red engineering menu.

So, it seems that in order to upload the map, you should do it entering the engineering menu, but from the pictures you posted, it seems that you have done it from the standard menu.
Am I wrong?
Once I plugged the storage device into the USB port, I'm able to see the message "Update medium found", but nothing happens even if I try to click on the message.

Could you help me please?

Thanks a lot for your time, much appreciated.
 
There are 2 ways to update the maps. Through the engineering menu, or just through the MMI (standard menu).

It is better to update the map through the standard menu, if you do it through the engineering menu, it will leave an SVM error code.

You have to wait about 5 minutes for the update to show in the MMI AFTER you have plugged in the USB and the "update medium found" message shows. The MMI does checks and it takes time.
 
There are 2 ways to update the maps. Through the engineering menu, or just through the MMI (standard menu).

It is better to update the map through the standard menu, if you do it through the engineering menu, it will leave an SVM error code.

You have to wait about 5 minutes for the update to show in the MMI AFTER you have plugged in the USB and the "update medium found" message shows. The MMI does checks and it takes time.
That's great! Thanks a lot
 
  • Like
Reactions: alps26
Hi,
I was able to upload the maps successfully. Thanks to @alps26.
Just a note for other users: my first installation attempt failed. I formatted the Navigation System Database partition using OBDeleven (005F Electronic Information System -> 005 Basic Settings -> Formatting Internal Memory Partitions -> Navigation System Database), then ran the installation again. After that, everything worked perfectly.
:wink: :wink: :wink:
 
  • Like
Reactions: alps26