Audi A5 Forum & Audi S5 Forum banner
1,361 - 1,380 of 1,462 Posts
Hello everyone, I have Audi a4 b8 BNav_EU_P0257_D1 4G0919884n ECE 5.17.2 Which software /firmware will work for my car? Thank you in advance.
You can use the latest BNav Europe map version 2023 (5.36.1, part number 4G0060884AN, what you cant find here) and the latest firmware K0260.
 
I registered on this forum after running into the same issue with navigation blocked on Checking medium - AND SOLVED IT. See below.
I have a A6 C6 facelift, MMI 3G basic. I was till yesterday on k0257, then upgraded to k0260 and tried to use the 5.35.2 maps.
The firmware upgrade went well, the older maps (2016) were still recognized. After inserting the new maps on SD, the trouble started.
Update went well, used the navdb_unblocker script, still locked. Used the latest activator, and in the end I got the famous error with Checking medium please wait...

From then all, hell broke loose. Tried the scripts from DrGer here ( Hut ab! ), none worked. _MMI3GB_ACT_REMOVE.7z -> didn't work. Tried the mmi3g_info no file created, not running, nada. Tried reapplying the maps, with both standard and user mode (activated in green menu -> SWDL), the update doesn't start (clicking the Start button does nothing). Original navi CD not recognized, same error. Time to panic.
Went to Green menu, tried to check or remove the database from the navi section, no go (Script not found error).
This is when I've started to consider reflashing the MMI. Perhaps some components went messed up because of the many scripts I've ran on it.
(end of part 1)
 
Part 2 What I've done here is not for the fainthearted:
1. Entered green menu, went to system, forced a emergency update with 0260. Have VCDS at hand to reactivate the green menu after. Still no go to install maps, clicking the Start button on the maps update did nothing, Check medium error still there. Maybe this step is optional, but I am mentioning it. Then...
2. Found on a Russian forum a link to a 0257 version, hoping that the old maps will work with that. Enabled in SWDL the two radio buttons for user defined mode and ignore region and variant. Then went to red menu (update one) and forced a downgrade to 0257. Got a few warnings and integrity errors, had to manually reboot with the 3 button sequence to start install, got other errors and then aborted the update. Magically, the Check medium error was not there anymore, and also the old factory CD was recognized. Yay, that's one off!
Russian-sourced 0257 here 33.55 GB folder on MEGA -> would be nice to have some here too.
3. Tried the normal update to 0260 back, didn't work (the Start button grayed out). Used VCDS (module 5f, block 6 change to 1), reactivated green menu, used the two SWDL radio buttons above, still can't go back to 0260. Then went back to green menu, emergency update, flashed the 0260 through that and now I got rid of the Check medium error, have 0260 but I am still on old maps.
Trying to update the maps with 5.35 or 5.36 is still no-go, clicking the start button doesn't work. But hey, I can use the old maps...
Maybe this is helpful for the ones here who are stuck in the Checking medium error... at least to unbrick your car if you ever intend to sell it at a good price.
If anyone discovers how to make the bloody map update work, please update here.. What worries me is the Script not found error when I try to Re-Check or Delete Database from the nav section of the green menu... I assume that some scripts from the original OS are now missing and I may be hitting a dead end with my attempts.
 
@DerPutzmeister -- MMI3G Basic is not fitted with a HDD, so you have no navdb to check/remove from the Green Engineering Menu (GEM); I haven't extracted the BNav_EU firmware filesystems (yet), but expect that they do not include scripts that are not relevant to the BNav configuration (while the GEM definitions are likely shared with the HNav system).

My understanding of the BNav navdb update process is that the system should recognize when a new(er) navdb media is inserted in the DVD or one of the SD card slots. The update method described in Post #1 of this thread has been used successfully by many people already. --g
 
@DerPutzmeister -- MMI3G Basic is not fitted with a HDD, so you have no navdb to check/remove from the Green Engineering Menu (GEM); I haven't extracted the BNav_EU firmware filesystems (yet), but expect that they do not include scripts that are not relevant to the BNav configuration (while the GEM definitions are likely shared with the HNav system).

My understanding of the BNav navdb update process is that the system should recognize when a new(er) navdb media is inserted in the DVD or one of the SD card slots. The update method described in Post #1 of this thread has been used successfully by many people already. --g
My understanding of the BNav navdb update process is that the system should recognize when a new(er) navdb media is inserted in the DVD or one of the SD card slots.

I share the same opinion, yet practice kills theory on a daily basis. It goes through all the steps, except when I have to press Start. This is when it does absolutely nothing, even with user defined mode on and ignore region and variant on. Weird.

The update method described in Post #1 of this thread has been used successfully by many people already. --g

I have no intention of denying this. Fact is, for me it doesn't work and I am looking for an explanation or way out of it :) Additionally, the last 6 pages show an increasing number of users running into the "Checking medium" issue and not reporting a solution.
 
@DerPutzmeister -- Yes, something like this:
Code:
mount -uw /mnt/efs-persist
rm -v /HBpersistence/SWDL/AudiInfoFile/DBACTIVATION/AudiUpdate.txt
rm -v /HBpersistence/SWDL/AudiInfoFile/NaviDatabase_ECE/AudiUpdate.txt
rm -v /HBpersistence/SWDL/AudiInfoFile/NaviPersistence/AudiUpdate.txt
--g
 
Thanks for the tip. I've finally managed to get my moody MMI3G to run your info collector and found the following files containing "AudiUpdate.txt". Should I remove just the ones indicated by you, or these ones as well ? Many thanks again.

Code:
/mnt/efs-persist/SWDL/AudiInfoFile:
total 16
drwxr-xr-x  2 root            172 Jan 01 00:00 DBACTIVATION
drwxr-xr-x  2 root            172 Jan 01 00:00 MapStyles
drwxr-xr-x  2 root            172 Jan 01 00:00 NaviDatabase_ECE
drwxr-xr-x  2 root            172 Jan 01 00:00 NaviPersistence
-rw-rw-rw-  1 root            645 Jan 01 00:00 AUDI_MMI3G_ECEAudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 AUDI_MMI3G_ECEAudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             12 Jan 01 00:00 AUDI_MMI3G_ECEAudiUpdate.txt.SWDL.version.txt
-rw-rw-rw-  1 root            645 Jan 01 00:00 DBActivationAudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 DBActivationAudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             12 Jan 01 00:00 DBActivationAudiUpdate.txt.SWDL.version.txt
-rw-rw-rw-  1 root            645 Jan 01 00:00 NaviPersistenceAudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 NaviPersistenceAudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             12 Jan 01 00:00 NaviPersistenceAudiUpdate.txt.SWDL.version.txt

/mnt/efs-persist/SWDL/AudiInfoFile/DBACTIVATION:
total 4
-rw-rw-rw-  1 root            735 Jan 01 00:00 AudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 AudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             15 Jan 01 00:00 AudiUpdate.txt.SWDL.version.txt

/mnt/efs-persist/SWDL/AudiInfoFile/MapStyles:
total 4
-rw-rw-rw-  1 root            735 Jan 01 00:00 AudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 AudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             15 Jan 01 00:00 AudiUpdate.txt.SWDL.version.txt

/mnt/efs-persist/SWDL/AudiInfoFile/NaviDatabase_ECE:
total 4
-rw-rw-rw-  1 root            735 Jan 01 00:00 AudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 AudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             15 Jan 01 00:00 AudiUpdate.txt.SWDL.version.txt

/mnt/efs-persist/SWDL/AudiInfoFile/NaviPersistence:
total 4
-rw-rw-rw-  1 root            735 Jan 01 00:00 AudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 AudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             15 Jan 01 00:00 AudiUpdate.txt.SWDL.version.txt

/mnt/efs-extended/map/styles:
total 5
drwxrwxrwx  2 root            216 Apr 08  2009 01
-rw-rw-rw-  1 root            645 Jan 01 00:00 AudiUpdate.txt
-rw-rw-rw-  1 root              5 Jan 01 00:00 AudiUpdate.txt.SWDL.compatibility.txt
-rw-rw-rw-  1 root             12 Jan 01 00:00 AudiUpdate.txt.SWDL.version.txt
 
So... solved it. I got again in the Check medium loop. Tried firmware downgrades and upgrades - did not help. No need to be done.
But - I did fiddle with GEM: NAV->Engineering->Set database and remove calibration commands.
Rebooted MMI -> factory DVD is now being recognized. This step above got me off the Check medium loop.

Inserted 5.36.1 card, still no success to upgrade. Went home, formatted card, recopied data on it, booted MMI without DVD, inserted card, everything went smooth. No need to run the rm commands above, it simply worked.
I cannot find an explanation for all this. Perhaps I did something wrong when building the cards. Hopefully I do not get activation prompt.
 
Can anyone possibly help me with my MMI issue? Bought my S5 used and first Audi and still learning but seems I did messed up big time. Anybody I have spoke to asks what version i have and dont even know to say since my screen in red. I do believe it ended in 9024? Also recall seeing "Nar 5.555.5 or similar to that. One of my buddies said that if I can get the software I have installed now on a sd card and formatted correctly when the green screen comes on it would install the software and might solve my problem? Is that true at all? Im on day 3 of no car with it draining and killing battery and no idea where to even begin
 
Can anyone possibly help me with my MMI issue? Bought my S5 used and first Audi and still learning but seems I did messed up big time. Anybody I have spoke to asks what version i have and dont even know to say since my screen in red. I do believe it ended in 9024? Also recall seeing "Nar 5.555.5 or similar to that. One of my buddies said that if I can get the software I have installed now on a sd card and formatted correctly when the green screen comes on it would install the software and might solve my problem? Is that true at all? Im on day 3 of no car with it draining and killing battery and no idea where to even begin
I assume we are talking about MMI 3G Basic here.
1. Download BNav_EU_K0260_1_D1 from first page.
2. Unzip in Windows (no MacOS).
3. Copy the files as they are in the zip root on the root of a FAT32 formatted SD card.
4. Remove all SDcards, DVDs etc and insert the generated SD card.
5. Press Setup-Knob-upper right key to reset the MMI. (read the guide PDF for this sequence or google Reboot MMI 3G)
6. Update starts.
Did it 4 times today.
 
I assume we are talking about MMI 3G Basic here.
1. Download BNav_EU_K0260_1_D1 from first page.
2. Unzip in Windows (no MacOS).
3. Copy the files as they are in the zip root on the root of a FAT32 formatted SD card.
4. Remove all SDcards, DVDs etc and insert the generated SD card.
5. Press Setup-Knob-upper right key to reset the MMI. (read the guide PDF for this sequence or google Reboot MMI 3G)
6. Update starts.
Did it 4 times today.
i believe i have the 3g+ HN. Would I still download that same file or different? Thank you so much for replying
 
1,361 - 1,380 of 1,462 Posts