Audi A5 Forum & Audi S5 Forum banner
2,201 - 2,220 of 2,925 Posts
@Krism95 -- You referred to my unblocker script in your post #2,188, above. Generally, you don't want to kill vdev-logvolmgr before it is allowed to create the new acios_db.ini file for the navdb updated from production (otherwise, this situation is likely). You should also confirm that this is indeed the problem by reviewing the various /nav screens in the Green Engineering Menu, for example:
View attachment 187243
and
View attachment 187244
The Console output will report an error message when the script cannot file /HBpersistence/navi/db/acios_db.ini --g
Hi again!

no valid acios_db found in /database

How do I go about adding a file into the car with the script? Attached both screens below
 

Attachments

@Krism95 -- Pro tip: Save MMI3G screenshots as PNG files to a FAT32 SD card in slot SD1 using [TEL]+[MEDIA] (press & hold). Take proper screenshots of the Green Engineering Menu screens you have above plus /nav/diagvalues and post as attachments (so they can be downloaded properly). Fixing your acios_db issue is not too difficult. --g
 
@Krism95 -- Pro tip: Save MMI3G screenshots as PNG files to a FAT32 SD card in slot SD1 using [TEL]+[MEDIA] (press & hold). Take proper screenshots of the Green Engineering Menu screens you have above plus /nav/diagvalues and post as attachments (so they can be downloaded properly). Fixing your acios_db issue is not too difficult. --g
Hi @DrGER

I knew about the screenshots just posted for speed as was easier posting off phone camera but here are the 3 below screenshots and the text file. Looking forward to getting this working!

kris M
 

Attachments

@Krism95 -- Thanks for the PNG images.

We saw a spate of broken navdb updates due to this problem back in April/May, so I took a closer look at the contents of acios_db.ini and found that it can be regenerated from the navdb configuration files installed already on the HDD in /mnt/nav. Take a look at my SD card script here: GitHub - DrGER2/Make-MMI3G-acios_db.ini: H-B MMI3G SD script to create acios_db.ini from the installed PKG file info
Extract the ZIP directly to a blank FAT32 SD card; start your MMI system (ignition OFF), wait for all functions to start fully (at least 3 minutes), insert the SD into an empty SD1/2 slot, and folllow the on-screen prompts. Restart the MMI manually. Check the SD card for copy of the new acios_db.ini in the var folder. Confirm with the GEM /nav/databaseupdate [List HDD Database info] script. --g
 
@Krism95 -- Thanks for the PNG images.

We saw a spate of broken navdb updates due to this problem back in April/May, so I took a closer look at the contents of acios_db.ini and found that it can be regenerated from the navdb configuration files installed already on the HDD in /mnt/nav. Take a look at my SD card script here: GitHub - DrGER2/Make-MMI3G-acios_db.ini: H-B MMI3G SD script to create acios_db.ini from the installed PKG file info
Extract the ZIP directly to a blank FAT32 SD card; start your MMI system (ignition OFF), wait for all functions to start fully (at least 3 minutes), insert the SD into an empty SD1/2 slot, and folllow the on-screen prompts. Restart the MMI manually. Check the SD card for copy of the new acios_db.ini in the var folder. Confirm with the GEM /nav/databaseupdate [List HDD Database info] script. --g
@DrGER i can hardly believe it - that’s it working!!
Checked the txt file and not seeing any errors and green screen confirms new file been generated and that’s the navs working. I believe I need to go a drive to calibrate the position as it’s showing me about 5 miles away but I am chuffed!!! Thanks for all your help, got my Dads car to do now it’s the same system in an A5 so will be at that tomorrow :)
 
@Krism95 -- That's good news.

When you do your Dad's MMI3GP, don't run the nav unblocker script SD until after the navdb update and you get the "nav data is unavailable" message on the MMI screen. Evidence suggests that disabling the normal Harman-Becker navdb activation process before running the first update affects the creation of acios_db.ini properly. --g
 
@DrGER "again for further updates [although it looks like the 6.36 map update is the last anyway]. Oh maaaan - I thought it seemed late for a new map version release - is this the last one? Do you think there is a way of'grafting' in other vehicle maker's map DBs as with MMI 2G DVD and replacing 2020 Audi mapping with current Mercedes mapping?
 
@Krism95 -- That's good news.

When you do your Dad's MMI3GP, don't run the nav unblocker script SD until after the navdb update and you get the "nav data is unavailable" message on the MMI screen. Evidence suggests that disabling the normal Harman-Becker navdb activation process before running the first update affects the creation of acios_db.ini properly. --g
@DrGER updated firmware first then maps on, failed on a few modules but retried both and it took it then the maps seemed to be working then came up with error message after about 2 minutes. Ran script and 3 button restart and off it went 😊 thanks so much for your help again!
 
@tzoboy -- OK, I see now -- C7 A6 IC map display can be enabled in some markets. Definitely not a standard configuration for C7 MMI3GP. Thanks for the reminder. And, yeah, I'm curious about having a closer look at this K1510 firmware. --g
 
Hi everyone,

I have a 2013 Q5 (MMI 3G+) imported from Canada and would like to update my software and change the region from US to EU. The current software version is HN+_US_AU3G_P0566. What is the procedure for changing the region as well as updating the software? I see that @congo has posted 2 several manuals for software update and region change. Does the region automatically change along with the software update to version HN+_EU_AU3G_K_0942?

Thank you all for your help.
 
@matinis -- MMI3GP NAR to EUR conversion is discussed in this thread often; for example, see this post: https://www.a5oc.com/threads/mmi-3g...avigation-6-36-0-and-firmware-updates-currently-2023-europe.176144/post-1640359
Two main issues to consider: EU language spec in the main unit EEPROM needs to be updated (needs special diagnostic tool like OBDeleven or VCP); and size of ECE 6.36.0 navdb requires HDD nav partition to be reformatted using the Green Engineering Menu. In rare case, firmware needs to reflashed using the IPL (this seems to happen more often with JP > EU conversions, also discussed in the thread). In any case, start here: AudiEnthusiasts Master and AudiEnthusiasts EEPROM --g
 
Discussion starter · #2,220 · (Edited)
2,201 - 2,220 of 2,925 Posts