[Krism95]

Hello - Q5 63 reg just installed update.
2 errors - PSD device failed (retried 3 times) now navigation telling me "The navigation data are invalid" and in version info in setup MMI - Nav. Database version: is blank.

Off to try another install on a different SD Card to see how I get on - reformatted in FAT32, extracting data now using 7zip and then off to give it another try! Fingers crossed

One last note - had to use a different activator as the one originally linked only has 2 files, whereas the instructions show a folder called FSC and metainfo2? I have read about 40 pages today but is there an updated activator to be used? I ended up using navunblocker-230308 from GitHub Nav Unblocker

Any help appreciated. If I can't get it to work the head unit will be getting changed!

 

[Krism95]

@Krism95
Firstly, the map update process copies over 20 database files from the SD card to the HDD in the head unit; most of these are 2GB in size. They all need to be copied correctly, so the failure of PSD will mean that the database is incomplete and it is likely this was the main reason that you got the "invalid" message. When the install process detects an error it shows an error code on the screen that may indicate what the problem was; typically these arise due to errors reading/writing the SD/HDD. You can't expect the Navigation to initialise until you successfully copy the PSD to the car's HDD!

Note that some users have indicated success by repeatedly using the Retry option ...



Secondly, there has always been some confusion regarding the 'activator'. Which 40 pages have you read? There are two docs by 'Congo' dated 2018 and 2021 and they show different activators. Some superb work by a US based contributor to this forum has deduced that both/all previous activators have made unnecessary [and sometimes confusing] changes and has developed the Unblocker, which supercedes all/any previous activators available [and it works on both 3GHigh & 3GPlus MMIs]. The unblocker updates only one MMI file and once installed is not required again for further updates [although it looks like the 6.36 map update is the last anyway].

J

Hi Julian

Thanks for getting back to me - I've now got it installed correctly but been sat on "initialising navigation" for about 15 mins.

Yes been looking through the forum to see if there was anyone else with same issue, I had an error with installing XAC2 but after retrying 3 times it took it.

Thanks for your feedback - I really appreciate it, this is a great forum and I will be pinging some cash over to Congo on the link. One last thing - can you point me in the direction of the unblocker if you wouldn't mind? Giving it a wash before it gets too dark here (UK) then plan to go a drive since it's been idling in the drive for ages reinstalling those updates.

Thanks again
KM

 

[Krism95]

@Krism95 -- The nav unblocker script is my work.

MMI3G nav startup hung on initializing usually means that the acios_db.ini is missing. This can happen when the vdev-logvolmgr process is killed BEFORE the production nav database is updated (which you may have done, based on your earlier comments). You can confirm this in the Green Engineering Menu under the /nav screens. Fixing is (relatively) simple: copy a known working acios_db.ini file for the installed nav database to the system manually using an SD script. The acios_db.ini file is NOT stored on the HDD -- it is saved in a persistent flash memory file system. --g

Hi DrGER

perfect - any chance of sending me the link for the unblocker. Where would I get a working acios_db.ini file and a script to add said file to system?

I followed every step of the instructions so not sure how I’ve managed to muck it up but I’ll give it a shot!

 

[Krism95]

@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 GrGer,

Ah got you! Thanks for that, worked in about 5 seconds flat.

I will go and have a look at the eng screen when I get a mo and get back to you.

 

[Krism95]

Hi Congo,

This is my first post on the forum, and I have just got myself a 2012 A5 3.0 TDi Quattro, Black Edition.
Pretty sure it has the 3G High Ami, (two SD slots on head unit, only the Ami port in the glove box) and I am looking to update it.
Have to admit to being bit confused by the various posts, on one hand this looks pretty straight forward, but then reading examples where folk have 'bricked' their attempt! I'm also on a MacBook Pro, so that seems to add another layer to the challenge!
If I understand the instructions correctly, once the files are downloaded onto the SD card it's simply a matter of popping it into the car and following the on-screen instructions?

Current version Info: BNav_EU_P0206_D1
Database Version: 4G0919884S EUW 5.22.3

Wondering if there are any kind members who might be able to download the necessary files onto an SD and send It to me? I have the required 32Gb SD Card ready to go and will also happily reimburse for your time!
I'm in Scotland, near Perth if that maybe makes it easier.

Any help, advice you might be able to provide would be greatly appreciated.

Hi Rob

where I’m at with mine is a few of the modules failed the first time - I retried a few times the following day but this then meant that some file didn’t generate so need to connect up VCDS to check the status of said file.

I think I would be able to get it sorted for you - I’m down in Edinburgh, up in the highlands for the festivities but can see about sending to you. I did the updates one at a time so the firmware update, then the nav update then the unblocker (to activate the NAV) now just need to check the status of the assumed missing file.

kris

 

[Krism95]

@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

 

[Krism95]

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

@DrGER forgot to tag you - apologies!

 

[Krism95]

Thanks, I'll have bit of a dig around!

Have a bit of reading and let me know what Files you’re needing and I’ll extract to a stick for you m8. 👍

 

[Krism95]

@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

 

[Krism95]

@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]

@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!