[Vlada33]

Don't know much about programing, but I just read text and as you say it looks like that if I backup missing files they will be removed again, so there is no need for extra work. As soon as I can I will try your unblocker and inform you about results.

 

[Vlada33]

well,this doesn't help,probably I have more problems that your unblocker can't fix...I try few things but doesn't go as planed

first I try with your unblocker,and script was done and navi still doesn't work,it stuck on "initializing navigation" and nothing happens...

then I check version ,and software was recognized (k0257),but navi version not (it should be 6.36.0),then I insert sd with maps,try update (not force update,red menu) and "navi persistant" was instaling again (as I can see is only thing that was instaling),no luck with this also

then I insert sd with firmware (k0257),there are few things that was aceppt update (again,red menu,not force update),and in this moment I get after "initializing navigation" I get Navigation Blocked message.try reset once again to see maps ,but that didn't worked,same as above,"initializing and then blocked,maps can be seen at all...

because I get massage that navi is blocked I decide to run your unblocker once again,script was executed and reset navi and once again "initializing navigation" on screen and I can't see maps and I don't get massage that navi is blocked...no luck...

I will present here logs from your unblocker (second run) and also log from mmiinfo script (run is made in the end when I give up and mmi stay like that for next try)

log unblock - Google Drive

drive.google.com

info - Google Drive

drive.google.com

 

[Stewart M]

Vlada33
I went through a similar process to you a while back. Used the incorrect unblocker. Unfortunatley I had to travel for work and never got round to fixing the issue. As far as I can tell, I have the maps installed (I have reinstalled them 4 times or something), but they are not showing correctly in the database.

I plan to use
DrGER
unblocker once I have the time to try it out. Hopefully this weekend I will be free. He was certainly very helpful when I was struggling last year, and so I hope this works this time.

 

[DrGER]

@Vlada33 : Can you run the current version of my MMI3G Info script: mmi3ginfo3-230401.zip
This version has code to get the train name & MU version on MMI3G (HNav) systems and some other parts of the MMI3G system.

Regarding sequencing of updates (software vs nav database), whenever you get a "nav blocked" message, that means system processes vdev-logvolmgr & MMI3GApplication cannot find a valid FSC file for the installed navdb release (based on its year as defined in the release PKG file). Terminating process vdev-logvolmgr before MMI3GApplication can complain about the missing or invalid FSC file disables the activation process (which is what all the so-called activator scripts do since 2014). Note that updating the K0257 software can over-write the activator disabler patch if package ifs-root.ifs is (re)installed.

When navigation hangs on initialization, we think this (may be) related to a missing or corrupt navdb package file. This is just a guess, but it would be useful to inspect the system syslog (as reported by sloginfo) to see whether process MMI3GApplication writes any error messages to the syslog when nav initialization gets stuck. --g

 

[Vlada33]

Ok, I will run current version of info script, probably tomorrow or Sunday, because car is in company use, and not always in my possession.

Also,first thing that I notice is that (read on forum here, probably your post, but not sure I understand it like it should) on startup navi create file acios.ini and from that point your patch stop vdev-logvolmgr and navi continue without asking for true fsc activator. In my case I don't have acios. ini at all, and I suppose that can be one of problems... This is how I see this problem (note, I'm not some programer, this is just my opinion), navi starts, loading is started, it comes somewhere about 27%,and loading stops, on screen then state "initializing navigation", loading maybe stops because acios. ini isn't created, your patch expect (not sure, just my opinion) that acios. ini being created to stop vdev-logvolmgr and continue with navi unblocking without confirming fsc.

Also, I was thinking and I'm asking for your opinion, if I decide to run again complete software update(if is possible at all) via green menu with same K0257, can I get a clean copy on my mmi, i mean, can that be a hard reset to back mmi in shape where I can see maps for 5 minutes?
From that point I will run again info script, and then decide is it necessary to delete navi partition and put same maps again or run your navi unblocker.
Note,when I first finished with software update old maps works without problems, then I put new maps and I can see maps for 5 minutes, also on mmi screen I can check navi version and that was ok 6.36.0,now I can't see navi version (blank line)

So, most important question here is if I try software update (green menu) with K0257 again (if is possible) can I get clean copy on mmi, will that restore all my mistakes with wrong scripts back to original state?

 

[DrGER]

@Vlada33 : I think your plan to restore MMI software to original state with K0257 SD card is a good idea. Use the Green Engineering Menu to set "user defined" update, then in Red Engineering Menu, select all the available Application parts of the MU9308 device (efs-system, fpga, fpga-emg, ifs-root, ifs-emg) to update. This restores main unit software to a known state. After the restore/update, nav should start and show blocked message after 5 minutes if the nav database is installed correctly. --g

 

[Vlada33]

Thanks for that information, also (probably not important) but I change line on metainfo (with notepad++) to start user defined update without green menu, I hope that this will save me from mistake in green menu (I made it to brick it in green menu already one time when I probably check some box that i didn't want,force update and another sd with K0257 save me) and I suppose that I will come to user defined update without entering green and red menu this way?

Line for metainfo are written on this topic few pages earlier, and is it ok to write them with notepad++?

 

[Stewart M]

So today I finally got around to trying some stuff.

A quick summary of what had happened previously (back in August last year). I first of all updated the firmware fully, then installed the latest, at the time, map. Then the activator that came with the map. Unfortunatley this was the incorrect activator. I then tried many different things to install the maps again, while doing so realising my battery was goosed as it would turn off midway through map update, replacing battery charger as my old one wasn't man enough to keep it charged, and eventually the battery itself. Which threw up it's own issues on my D3 A8. I had formatted the nav partition at some point, re-installed various maps versions, and eventually just left it. At this point it would say the Nav DB isn't compatible or similar. Despite at one point it working for around 5 mins. And so I left it like that for months. It's a third car mostly used for airport runs, so I didn't really need or use the Nav.

Firstly, I thought I would run the mmi3ginfo script to see what was going on with my system.
Here is the link to the file on my One Drive: mmi3ginfo-20230415_160437.log

Then I thought I'd run DrGER's new Nav Unblocker script, the log is here: run-20230415_160850.log

This resulted in the Nav database no longer looking incompatible. However, the Nav only seems to be partially working. I took the car for a decent drive, set a destination in the nav, and that all seemed to work well. Even giving turn directions in the cluster as well as to the side of the display screen. The only problem was there were no roads showing on the map. Any ideas? I am currently downloading the 2023 map, so if I have to reinstall the map database, at least I can get the latest one, hopefully.

 

[Vlada33]

Well, even that is some progress...

Mine situation is little different, I couldn't update K0257 again, even with user defined...
I this moment I'm in car and reinstalling maps and hopping for best, already was applyed unblocker now I waiting to finish maps reinstall.
If this doesn't work, I suppose that I have wrong mmelauncher (modified), don't have better idea...

 

[Stewart M]

Vlada33. Yes. Some progress. But not much. I went and found my last post in this thread, #259 from August 16th 2022. That's pretty much where I left it. And, to be honest, it seems to be where I am right now. I must have done something since then as the nav database has been incompatible since then, but at the point of that post, I could enter destinations, and get directions without roadsa visible too. So 9 months later and I'm in the same predicament, ha ha.

 

[Vlada33]

from my point of view it's not same...even your navi doesn't say it's blocked...maybe new maps will help.

i didn't reinstall maps,cars has to go on trip,stoped in half...who know what I can expect tommorow...for sure it will not be aworking navi...

still,I run a info script just in last seconds (didn't get conformation screen that script is finished,i don't know why)

info new - Google Drive

drive.google.com

 

[DrGER]

@Stewart M : A couple of observations re the MMI Info log:
1. Looks like you pulled the SD card out early ? Logging stopped during the INFO_FLASH2 section. The section that contains the Bordbook (User Manual) data is huge -- I'll look at reconfiguring the script to omit this as the default.
2. The Main Unit software version is reported as "0143" -- does that match what the Red Engineering Menu main screen reports ? I would expect this to be "0187" for K0257_D6. The date stamps in /mnt/ifs-root and /mnt/efs-system don't look right, either. I would expect them to be from Jun 2013. See the log output in @Vlada33 's post, above.
3. The log from my unblocker script looks correct.

Given (2), above, I suspect that your MMI software update to HNav_EU_K0257_6_D1 is NOT correct. This might explain why the nav map is not displaying the LIT part of the database correctly. The digital terrain model (DTM) parts of the database file (LIT) look OK, so there's that. You might consider re-running the K0257_D6 update as user-defined and select all the Application bits of the MU9308 device.

 

[Stewart M]

@Stewart M : A couple of observations re the MMI Info log:
1. Looks like you pulled the SD card out early ? Logging stopped during the INFO_FLASH2 section. The section that contains the Bordbook (User Manual) data is huge -- I'll look at reconfiguring the script to omit this as the default.
2. The Main Unit software version is reported as "0143" -- does that match what the Red Engineering Menu main screen reports ? I would expect this to be "0187" for K0257_D6. The date stamps in /mnt/ifs-root and /mnt/efs-system don't look right, either. I would expect them to be from Jun 2013. See the log output in @Vlada33 's post, above.
3. The log from my unblocker script looks correct.

Given (2), above, I suspect that your MMI software update to HNav_EU_K0257_6_D1 is NOT correct. This might explain why the nav map is not displaying the LIT part of the database correctly. The digital terrain model (DTM) parts of the database file (LIT) look OK, so there's that. You might consider re-running the K0257_D6 update as user-defined and select all the Application bits of the MU9308 device.

Thanks for that. I'll give that a go tomorrow hopefully.

There was no prompt on the script to say when it stopped. It said press any key to continue, I did, and it went to radio or something. I left it a minute or something and thought it was done. But obviously it wasn't. So what I'll do is try to re-run the K0257_D6 update as you say, then re-run the MMI Info script. Then post the results here.

I may get bored late tonight and do it then, but that would be after midnight, ha ha.

 

[Vlada33]

DrGER,if you grab a little free time,please look on my log from new info script,all I was noticed that I still can't get acios.ini. maybe that file have something with my problem even if your unblocker bypassing that...

122914 118822 mnt/ifs-root/bin/waitfor waitfor /mnt/lvm/acios_db.ini 180

from this point,acios_db.ini isn't showing anywhere on my log...

also,just checked,script not even close to be finished,I suppose that I have to do it again

 

[DrGER]

@Vlada33 : Thanks for posting your log results -- I found a stray single quote in the INFO_NAVDB section that caused the script to fail -- The script is updated and reposted to my Google Drive: mmi3ginfo3-230415.zip
Please use the updated version dated 230415 -- @Stewart M , too !

 

[DrGER]

DrGER,if you grab a little free time,please look on my log from new info script,all I was noticed that I still can't get acios.ini. maybe that file have something with my problem even if your unblocker bypassing that...

Your log dated 20230415_210905 was started too early -- process vdev-logvolmgr didn't start yet to create acios_db.ini -- the patch code is still running as PID 122914; you should wait at least 3 minutes before running the MMI Info script to allow system process to start fully.
And, as I noted above, the script had a small (but significant) typo -- now corrected. Now to come up with a (simple) way of skipping the bordbook mount in /mnt/efs-persist (if it's found). --g

 

[DrGER]

@Stewart M : One thing that confuses me about the HNav_EU_K0257_6_D1 update (downloaded from mega.nz) is that it contains more than one update for the MU9308 device. The first one in the archive appears to be what is installed on your system -- that is, it has trainname HNav_EU_K0257_6_D1 but version number is 0143; the third set in the archive has the correct MU version, 0187. When you try to redo the K0257 update, you should look for ifs-root version change from 956 to 1076 (as noted in their metainfo2.txt files). --g

 

[mpereyra24]

Hello there, im having a problem to upgrade the firmware before i try to install the navegation, i got MMI 3g High as my software version is Hnav_JP_P0213 so im trying to update to 0253 first but on red menu i get a error it say "A variant conflict ocurred! Mainunit variant:9309 Release info variant:9307 9308"

so im afraid to make a mistake, and i was doing a research in the forum also in google, but the only similar thread are peoble trying to update with the wrong software example trying to update mmi 3g high with 3g+ software

but i have download the one for 3g high so im confused

there is any problem trying to update japanise to EU firmware? anyone had same situation before thank you guys

 

[NoMyNaMe]

Gents, I need to pick your knowledge about activating the 6.36.0 in Audi A6 4F 2009's HNav with a K0257_6. Apologies if any as this forum is for A5, but I have been looking in the net for days without luck, and you seem to be my best hope atm.

My last update before this one was the 6.24.2 using the FSC Activator, my understanding was that the update will be flawless under this firmware and activator, but to my misfortune, not, I got a The Navigation Data Blocked message after the update. If I am correct, I can only activate the map using the FSC Activator due to the MMI age, as Keldo's Activator is for more recent MMI.

Do you know how to activate the map 6.36.0 in Audi A6 4F 2009's HNav with a K0257_6?

Thanks

 

[DrGER]

Hello there, im having a problem to upgrade the firmware before i try to install the navegation, i got MMI 3g High as my software version is Hnav_JP_P0213 so im trying to update to 0253 first but on red menu i get a error it say "A variant conflict ocurred! Mainunit variant:9309 Release info variant:9307 9308"
...

Your HNav system is for the JPN market and its configuration is NOT consistent with the HNav_EU updates. See, for example: https://cartechnology.co.uk/showthread.php?tid=68414

If you have VCDS, what part number is reported for Address 5F ?

You may be better off sourcing a salvaged HNav main unit from your region and retrofitting. --g