[csarp]

@csarp -- Your MMI3G Basic/BNav system does not have an internal HDD, so the GEM script, which is part of the HNav firmware, is meaningless on your system. With a FAT32 SD card in slot SD1, does your MMI3G Basic system save screenshots as PNG files when you press and hold the [<<]+[>>] keys for about 3-4 seconds ? Can you try this for the Setup > Version information and Red Engineering Menu screens ? --g

Here are the screenshots. Originally my map vas on disc 4G09199884F_ECE 5.10.5 but now at 35% stopped loading.

 

[DrGER]

@csarp -- Thank you for the PNG images, they are perfect.

MMI3G Basic systems were only fitted to European market cars, so our experience with them is limited, which make diagnosing nav issues difficult. We know much more about High and Plus system, but Basic systems should, theoretically, operate similarly. If you have the time and interest, can you run my MMI3G Info Report script on your BNav system with the 4G09199884F_ECE disc in the DVD drive ? The SD script is posted at my GitHub page: GitHub - DrGER2/MMI3G-Info: MMI3G Information Report Script
You can post the report log file here or to a shared cloud storage space (like Google Drive or OneDrive). The report script can tell us the state and condition of the system configuration. My guess here is that the navbd acios_db.ini file is either missing or not correct. --g

 

[csarp]

@csarp -- Thank you for the PNG images, they are perfect.

MMI3G Basic systems were only fitted to European market cars, so our experience with them is limited, which make diagnosing nav issues difficult. We know much more about High and Plus system, but Basic systems should, theoretically, operate similarly. If you have the time and interest, can you run my MMI3G Info Report script on your BNav system with the 4G09199884F_ECE disc in the DVD drive ? The SD script is posted at my GitHub page: GitHub - DrGER2/MMI3G-Info: MMI3G Information Report Script
You can post the report log file here or to a shared cloud storage space (like Google Drive or OneDrive). The report script can tell us the state and condition of the system configuration. My guess here is that the navbd acios_db.ini file is either missing or not correct. --g

Thank you for the script. I have uploaded the log file to google drive

 

[DrGER]

@csarp -- Thank you for the log file. A few observations from my first quick pass of the file:
1. No acios_db.ini file found in /mnt/efs-persist/navi/db (we expect to find it here).
2. Looks like a double layer (?) DVD is mounted on /fs/cd0, but we don't know what is stored on the DVD. On systems with HDDs, the navdb is always in /mnt/nav/db -- on BNav systems, the navdb could be in one of three places: DVD (/fs/cd0) or either of the SD card slots.
I can update my report script to look at the DVD drive (/fs/cd0) if it is found, and report its contents.
Unfortunately, we don't have an example yet of a WORKING BNav system with the navdb on the DVD drive or in slot SD2 for comparison. Let's see if we can fix that here. --g

 

[DrGER]

@csarp -- I updated the SD card script ZIP file -- can you try running the -231230 version and post the log file to your Google Drive ? Run this version with the 5.10.5 DVD inserted and the "initializing" message displayed on the screen. You should also try to get a PNG screen shot of the Green Engineering Menu /nav/databaseupdate [List HDD Database info] script output. --g

 

[csarp]

@csarp -- I updated the SD card script ZIP file -- can you try running the -231230 version and post the log file to your Google Drive ? Run this version with the 5.10.5 DVD inserted and the "initializing" message displayed on the screen. You should also try to get a PNG screen shot of the Green Engineering Menu /nav/databaseupdate [List HDD Database info] script output. --g

I downloaded the new script, started but there was an error in the script. The log file:
[INFO] Start: Thu Jan 01 00:07:11 UTC 1970; Timestamp: 20231231_084531
[INFO] MMI3G Info Dump: mmi3ginfo3-v231230

[INFO] MU train name: BNav_EU_K0260_1_D1
[INFO] MU software version: 0191
[INFO] MU variant: 9304
[INFO] MU hwSample: n/a

[INFO] No HDD reported by eide_display_devices.
./run.sh[110]: syntax error: `fi' unexpected

I have examined your script and put an extra line with "echo" in it:
else
echo "test"
fi ;;
With this modification the script finished well, but I don't know whether the result is good or not. I have uploaded the new .log to drive.

 

[DrGER]

@csarp -- Thanks again for sharing this information. Looks like I got distracted yesterday and didn't finish that part of the script; I just reworked it so that the script first looks for the navdb in SD1 then SD2 and if it is not found on an SD card, assumes it will be in the DVD drive; the updated ZIP is posted.

Now, back to your problem -- I think this is related to missing file acios_db.ini in /HBpersistence/navi/db (/mnt/efs-persist/navi/db). On MMI3G High/Plus systems, this is caused generally by running the vdev-logvolmgr termination patch prior to updating the production nav database (and allowing vdev-logvolmgr & MMI3GApplication to create the new acios_db.ini file). To solve this on High & Plus systems, I wrote an SD card script that (re)creates a working acios_db.ini file from the PKG file for the new navdb installed on the HDD.

In the case of MMI3G Basic systems, however, the file naming scheme of the update SD card does not follow your original DVD from 2010; that shouldn't be a problem assuming the metaifo2.txt files are correct. So, what is the best way forward here ? I think having the navdb on a DVD is the best configuration -- but not everyone has the ability to prepare the correct DVD media from the SD card downloads. Next best is to use slot SD2 for the navdb (so that SD1 can be used to capture screenshot PNGs and run shell scripts). With the updated navdb SD in slot SD2, we can run a SD script from SD1 that creates a new acios_db.ini file for the "installed" nav database. But the Basic navdb is relatively simple -- for example, I would expect the acios_db.ini file for your ECE DVD to look like this:

# Audi-MMI3G_ECE_B_E_5_10_5
ANY: /fs/cd0/pkgdb/GDB/8434_v37b.gdb
ANY: /fs/cd0/pkgdb/LABEL/Label.DB
ANY: /fs/cd0/pkgdb/LIT/8435_L1.DB
ANY: /fs/cd0/pkgdb/LIT2/8435_L2.DB
#SDS: /fs/cd0/pkgdb/SDS/SDS_Data.iso
#MNT(SDS): /fs/cd0/pkgdb/SDS/SDS_Data.iso   
ANY: /fs/cd0/pkgdb/TMC3GP/TMC_Trafficmaster.DB   
ANY: /fs/cd0/pkgdb/XAC/KN084EUx30_0.DB
ANY: /fs/cd0/pkgdb/XAC2/KN084EUx30_1.DB

I downloaded the EUW database from the thread, and the acios_db.ini for this navdb running from SD2 might look like this:

# Basic_EUW_Ba_R_5_35_2
ANY: /fs/sd1/pkgdb/GDB/EIW131_v37a.gdb
ANY: /fs/sd1/pkgdb/LABEL/Label.DB
ANY: /fs/sd1/pkgdb/LIT/EIW131a_L1.db
ANY: /fs/sd1/pkgdb/LIT2/EIW131a_L2.db
#SDS: /fs/sd1/pkgdb/SDS/SDS_Data.iso
#MNT(SDS): /fs/sd1/pkgdb/SDS/SDS_Data.iso
ANY: /fs/sd1/pkgdb/TMC/kN213EUx03t01.db
ANY: /fs/sd1/pkgdb/XAC/kN213EUx03.db

The MMI3G Basic system might even accept the acios_db.ini file stored DIRECTLY on the SD card (in the root dir/folder) -- though I have no way of testing or confirming that idea.

So, where to next on this ?

My script also reports that the Keldo/Vlasoff vdev-logvolmgr termination patch was applied to your BNav system, which disables normal navdb activation using stored FSC files. --g

 

[DrGER]

@csarp -- Take a look at my mkacios_db.ini SD card script updated for MMI3G Basic navdbs: 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 download to a blank FAT32 SD card; remove all SD cards; insert your newer 5.35.2 navdb SD into slot SD2; start the MMI system and wait for all functions to start fully; insert the SD script card into slot SD1 and follow the MMI screen prompts; eject the card from slot SD1 and review the run-time log for errors. Restart the MMI system. Use the GEM to check for the acios_db.ini file in persistent /HBpersistence/navi/db.

Happy New Year. --g

 

[csarp]

@csarp -- Take a look at my mkacios_db.ini SD card script updated for MMI3G Basic navdbs: 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 download to a blank FAT32 SD card; remove all SD cards; insert your newer 5.35.2 navdb SD into slot SD2; start the MMI system and wait for all functions to start fully; insert the SD script card into slot SD1 and follow the MMI screen prompts; eject the card from slot SD1 and review the run-time log for errors. Restart the MMI system. Use the GEM to check for the acios_db.ini file in persistent /HBpersistence/navi/db.

Happy New Year. --g

Happy New Year for U!

I have downloaded "makeacios" script, inserted navdb into slot SD2, restart MMI and after insert SD1 the card with script. Seemingly nothing happened, something wrong with the script, nothing on the screen, but it ran. Unfortunately I forgot to save the log file from SD card, but it fixed missing acios.db.
I checked in green menu.
The new map from SD2 tried to update database, but sent a message "No update device found."
At this moment when I start MMI must be inserted both DVD with 5.10.5 and the SD card with newer maps.

 

[DrGER]

@csarp -- Thank you for the feedback. I mixed up the names of the low & high resolution screen files in the ZIP file, which broke the screen prompt messages. This should be fixed now.

How the MMI3G system registers the "active" nav database is not understood completely (at least by me). On HDD systems, we assume this to be based on the DBInfo.txt file found in /mnt/nav/db/. But on MMI3G Basic systems, inspection of the metainfo2.txt file suggests that two files from the DVD/SD are updated in flash memory:

/HBpersistence/SWDL/AudiInfoFile/DBACTIVATION/AudiUpdate.txt
/HBpersistence/SWDL/AudiInfoFile/MapStyles/AudiUpdate.txt

Both files reference the navdb version (for example, "EUR 2022/2023"); it may be useful to inspect the contents of file
/HBpersistence/SWDL/AudiInfoFile/DBACTIVATION/AudiUpdate.txt in my Info reporting script.

So, now I'm curious: you show that /HBpersistence/navi/db/acios_db.ini references the navdb files on the SD card in slot SD2 (that is, /fs/sd1/pkgdb/...) but Setup > Version information still reports the DVD navdb version. If you have a map display, can you tell if it shows any map features (for example, roads or POIs) that were added since 2010 ? --g

 

[csarp]

DrGER Well I have tested it. The navigation uses the old map.
When i removed the SD card, the map is gone. I put it back and in the next step I removed DVD. The MMI displayed usual message "New database found ..Install Database etc" but it is not possible. When inserted DVD back, navigation continued with old map.

 

[DrGER]

@csarp -- That is confusing. Are you using Mac OSX to create your nav update SD card -- see this post in the thread from 2016: https://www.a5oc.com/threads/mmi-3g...-navigation-5-35-2-and-firmware-updates-currently-2022-2023.113473/post-1284186
We also see reports of people burning the update onto double-layer DVDs from an ISO image: https://www.a5oc.com/threads/mmi-3g...-navigation-5-35-2-and-firmware-updates-currently-2022-2023.113473/post-1272866 -- I think if we had a BNav system in the US, I would use this approach to keep the SD slots open for screenshots/GEM scripts (SD1) and audio/media (SD2). As an experiment, I managed to create a double layer DVD+R disc with the 8R0060884AM_EUW files on my Linux desktop in about an hour. --g

 

[csarp]

@csarp -- That is confusing. Are you using Mac OSX to create your nav update SD card -- see this post in the thread from 2016: https://www.a5oc.com/threads/mmi-3g...-navigation-5-35-2-and-firmware-updates-currently-2022-2023.113473/post-1284186
We also see reports of people burning the update onto double-layer DVDs from an ISO image: https://www.a5oc.com/threads/mmi-3g...-navigation-5-35-2-and-firmware-updates-currently-2022-2023.113473/post-1272866 -- I think if we had a BNav system in the US, I would use this approach to keep the SD slots open for screenshots/GEM scripts (SD1) and audio/media (SD2). As an experiment, I managed to create a double layer DVD+R disc with the 8R0060884AM_EUW files on my Linux desktop in about an hour. --g

DrGER - I used MacOS and Win10 too, but the result was the same, I am thinking .. As you analyzed I have no HDD ... MMI after detecting inserted SD card with new map after reading card displays "No update device found!".
Is it not possible that searching the non-existing HDD to write ?
By the way when MMI found new map and asking "Install database?" in my case the default answer set to NO, at the others is YES.

I found in first post MMI 3G Basic 5.34.2 Europe 2022 DVD image, I will try it.

 

[DrGER]

@csarp -- The BNav system is designed to operate without an integrated HDD, so we know for certain that is not the problem here. The "metainfo2.txt" file in the Basic folder of the SD card (or DVD) shows that the following files are updated in flash memory (/mnt/efs-persist) during the "update" process:

/HBpersistence/SWDL/AudiInfoFile/DBACTIVATION/AudiUpdate.txt
/HBpersistence/SWDL/AudiInfoFile/NaviDatabase_ECE/AudiUpdate.txt
/HBpersistence/navi/db/clearLastCityHistory.sh
/HBpersistence/navi/db/clearLastCityHistory.xml
/HBpersistence/SWDL/AudiInfoFile/NaviPersistence/AudiUpdate.txt

and that the "AudiUpdate.txt" file is the same in all cases. In your case, we don't find this information stored in persistent flash memory /mnt/efs-persist, so how the BNav system "knows" that a new navdb is found in, say, SD2 when the DVD is removed and the system restarted, is a mystery to me.
If you do manage to update using a double-layer DVD+R disc, can you share the MMI3G Info report log of your working nav system ? Cheers --g

 

[csarp]

@csarp -- The BNav system is designed to operate without an integrated HDD, so we know for certain that is not the problem here. The "metainfo2.txt" file in the Basic folder of the SD card (or DVD) shows that the following files are updated in flash memory (/mnt/efs-persist) during the "update" process:

/HBpersistence/SWDL/AudiInfoFile/DBACTIVATION/AudiUpdate.txt
/HBpersistence/SWDL/AudiInfoFile/NaviDatabase_ECE/AudiUpdate.txt
/HBpersistence/navi/db/clearLastCityHistory.sh
/HBpersistence/navi/db/clearLastCityHistory.xml
/HBpersistence/SWDL/AudiInfoFile/NaviPersistence/AudiUpdate.txt

and that the "AudiUpdate.txt" file is the same in all cases. In your case, we don't find this information stored in persistent flash memory /mnt/efs-persist, so how the BNav system "knows" that a new navdb is found in, say, SD2 when the DVD is removed and the system restarted, is a mystery to me.
If you do manage to update using a double-layer DVD+R disc, can you share the MMI3G Info report log of your working nav system ? Cheers --g

DrGER -- It works finally!
I did not make a DVD yet, but I thought about how I did the update yesterday. Probably I made a mistake, I forgot to remove nav DVD,
So I repeated the process. I started with your MMI3G-Info script, examined log file and deleted all existence of AudiUpdate.txt from /HBpersistence/SWDL/AudiInfoFile/ subdirectories
Rebooted MMI with new nav db in slot SD2

After restart I could start updating.

Here is the final log




Thank you very much for your help!!

 

[DrGER]

Thank you for sharing your successful result (both PNGs and log file). I am curious now about the navdb activation file in /mnt/efs-persist/FSC -- I assume you installed this as directed in the instructions. But your BNav system also has the Keldo/Vlasoff vdev-logvolmgr patch installed, which disables the normal process used by Harman-Becker to activate a navigation database, so the FSC file should not be needed. But, no matter -- you got the updated navdb working, and that's the important part. Bravo ! Maybe you will get to revisit this when 4G0060884AN (2023) is shared. Cheers. --g

 

[csarp]

Thank you for sharing your successful result (both PNGs and log file). I am curious now about the navdb activation file in /mnt/efs-persist/FSC -- I assume you installed this as directed in the instructions. But your BNav system also has the Keldo/Vlasoff vdev-logvolmgr patch installed, which disables the normal process used by Harman-Becker to activate a navigation database, so the FSC file should not be needed. But, no matter -- you got the updated navdb working, and that's the important part. Bravo ! Maybe you will get to revisit this when 4G0060884AN (2023) is shared. Cheers. --g

DrGER - Meanwhile I found the newer map, I tried and managed to update again.

Thanks once more.

 

[DrGER]

there is no solution for that problem yet, since I've been looking for the same one for a couple of months.

Do you have the original nav database DVD in the DVD player ? You should examine the current state of the MMI3G system with my MMI3G Info reporting script: GitHub - DrGER2/MMI3G-Info: MMI3G Information Report Script
Download the ZIP archive from the GitHub repository and extract directly to an empty FAT32 SD card.
If you have the original navdb DVD, start the MMI system with the DVD in the DVD drive. When all the NAV, TEL, CAR, MEDIA, and RADIO functions are started, insert the script SD into either open SD slot & follow the prompts on the MMI display. When the script is finished, save the plain-text log file to a shared cloud storage (like Google Drive or OneDrive) for our review and comment. After we know something about how the system is configured, we can offer some suggestions for moving forward. --g

 

[Lquirke]

Hi all,
I recently tried to update my mmi on my 2010 a6 and now it is stuck in the emergency update loop. Ive downloaded countless amounts of firmware updates and they all say no medium and go into a red screen and it retries it again. I have had a minor amount of luck with the HN+R_US_AU_K0942_3_(Q3-A6-A7-A8) (1) FW from here. When I insert this update into the MMI it stays in the green screen and says:

MMI3G EmApp 21.26.1642
MU9411
0/8 -> V0
Erase
Please Wait...

Is my system broken or would it be worth trying to hard reset it with a UART cable (Ive seen this on one or 2 forums I dont know if this works) or am I best off buying another MMI and removing component protection.

Thanks

 

[DrGER]

@Lquirke -- You should start a new topic/thread for this problem, as it is NOT related specifically to any of the posted navigation database updates.

That said, it is not likely that your 2010 A6 has MMI3G Plus (HN+R); more likely to be either Basic (BNav_EU) or High (HNav_EU) for that model year. Applying the WRONG software update to your system generally has a bad outcome (like your present case). You need to identify which main unit you have (MU9404, MU9408, MU9411, or MU9498) before you proceed -- knowing the production software version or the part number of the main unit will help here. --g