[silent_tr]

Hi,
Firstly thanks for all these guides!

I've done all my firmware updates so I'm now on 0257_6.

I've formatted the SD card and tried to get the maps onto it but it's not big enough?
I'm 3G HDD MMI and the mega download shows version 6.32.1, total size is 27.6 GB and my SD card has 29.7 GB after formatting to FAT32.
Downloaded mega contents:
folder: MMI3G
folder: MMI3GP
folder: pkgdb
file: build1
file: config.nfm
file: DBInfo
file: metainfo2


No idea why it's showing not enough space, please could someone suggest a SD card to buy or if there is anything i can strip out of the pkgdb folder?
My current is a 32GB SDHC microsd in adapter.


Cheers

 

[DrGER]

@silent_tr -- If you've done any research on this, you would know that the pkgdb folder contains installation files for both HNav and HN+ systems; in your case, removing the LIT3GP... folders should be sufficient for the installation to fit properly on a 32GB SDHC card. BTW, micro SD cards are not recommended for navdb updates, given the size of the files you're copying to the MMI HDD -- use them at your risk. --g

 

[silent_tr]

@silent_tr -- If you've done any research on this, you would know that the pkgdb folder contains installation files for both HNav and HN+ systems; in your case, removing the LIT3GP... folders should be sufficient for the installation to fit properly on a 32GB SDHC card. BTW, micro SD cards are not recommended for navdb updates, given the size of the files you're copying to the MMI HDD -- use them at your risk. --g

Hi, yeah I've done research and knew you could remove some from here but I'm lost with the amount of tabs open so couldn't find the listing.
This is current list inside, i can't see a LIT3GP....Can i remove SDS3GP and TMC3GP ? anything else?

 

[DrGER]

@silent_tr -- You have the right idea -- the CTYS3TC folders are for the HN+ installation, so you can remove them, too. Take a look at the contents of the MMI3G/metainfo2.txt file -- this is what the Red Engineering Menu Updater process uses to determine what gets installed during the udpate.
BTW, when you're done with navdb update, you'll find that the NAV function is blocked after a while. To unblock, you need to disable the navdb activation process Harman-Becker uses on our MMI3G/3GP systems (it's the same on both). I have an SD card script that patches the MMI operating system following a method described by others back in 2015; you can find it here: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database. --g

 

[silent_tr]

@silent_tr -- You have the right idea -- the CTYS3TC folders are for the HN+ installation, so you can remove them, too. Take a look at the contents of the MMI3G/metainfo2.txt file -- this is what the Red Engineering Menu Updater process uses to determine what gets installed during the udpate.
BTW, when you're done with navdb update, you'll find that the NAV function is blocked after a while. To unblock, you need to disable the navdb activation process Harman-Becker uses on our MMI3G/3GP systems (it's the same on both). I have an SD card script that patches the MMI operating system following a method described by others back in 2015; you can find it here: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database. --g

Brilliant, appreciate this. Will go through the meta file if stripping those others aren't enough. Many thanks for the GitHub link! Is this script in addition to the activator?

 

[DrGER]

... Is this script in addition to the activator?

Read the description at my GitHub repository for my remarks on this -- short answer is that my SD script replaces earlier so-called "activators" (which aren't, really). --g

 

[silent_tr]

Read the description at my GitHub repository for my remarks on this -- short answer is that my SD script replaces earlier so-called "activators" (which aren't, really). --g

Just completed the install of maps, ran your unblocker and it seems to be working as expected. I currently can't search for postcode/zip codes but I believe this is normal until I take a bit of a drive to have it detect properly, satellite counts currently 8.

EDIT: 5 min drive about and it's all working! Time to go get the 6.36.0 2023 ones now

 

[DrGER]

...
EDIT: 5 min drive about and it's all working! Time to go get the 6.36.0 2023 ones now

And the navdb unblocker patch is (essentially) permanent (unless the MU software is re-installed), so no need to run the installer again after navdb updates. --g

 

[silent_tr]

I've taken the 6.36.0 2023 MMI 3G High/Plus Europe [Link on Mega (use 7z/7zip to open the files)] found in MMI 3G+/3GP navigation 6.36.0 and firmware updates - currently 2023 Europe

The install failed with error 140 on one of the files, so I've stopped the install. Navigation now doesn't work.

First question:
Do I need to do anything before re-installing the mmi-3g-nav maps from this post?

Second question:
What did I do wrong when installing from the other post, is there a way to only update the maps part? I just (wrongly) assumed that running the SD card via engineering menu that it would just update the maps part, should I have done user defined mode and only selected one part? I.e: StyleDBMMI3G_ECE_94?


Cheers

 

[DrGER]

...
The install failed with error 140 on one of the files, so I've stopped the install. Navigation now doesn't work.
...
What did I do wrong when installing from the other post, is there a way to only update the maps part? I just (wrongly) assumed that running the SD card via engineering menu that it would just update the maps part, should I have done user defined mode and only selected one part? I.e: StyleDBMMI3G_ECE_94?

Re the Error code 140: Most people get this to work by selecting "Retry" until the update component is successful.

When you did the first update (factory to ECE 6.32.1), Standard update worked because your factory navdb was activated properly (with the original FSC file). When you ran the next update (ECE 6.32.1 to 6.36.0), navdb activation was disabled due to the patch script you ran to unblock the updated 6.32.1 navdb, so you needed to run the update as User-defined. This will be the case for all subsequent navdb updates. To answer your second question, then, yes, you can use User-defined update to select only the parts you need (or wish) to update. Remember to select only the "Application" components (NEVER select the Bootloader in a User-defined software update). --g

 

[silent_tr]

thanks @DrGER - would my first step to be just try again with the 6.36.0 and keep trying the retry where possible?

RE the response to second question, how do i know from the list which are related to navdb updates if via user-defined way in future?

 

[DrGER]

@silent_tr -- Re the Error code 140, using "Retry" is advised generally. In your case, though, the size of the nav HDD partition can be an issue. All HNav systems were fitted with 40 GB HDDs, and the current MMI3G ECE 6.36.0 gets close to filling the partition. You might consider using the Green Engineering Menu to reformat your HDD nav partition for two reasons: (1) it can remove unnecessary MapStyle files installed by the MMI software update, and (2) it will reset the sector size of directories (the factory image has this set to 4096, standard is 1024). Find this in /nav/databaseupdate [Delete NAV HDD partition]:

Re what to select for a User-defined navdb update, if the entry is 'N/A' it's not part of the release; if it's 'N' or '?', you need to check whether the Application version of the release is later than the installed version & select -- generally, it is safe to just select all available components so the entry is 'Y'. --g

 

[silent_tr]

Getting 160 error now on database GDB:0.
Guess I'll reformat SD card and load back on to try again.

EDIT: just reviewed files and it looks like i forgot to add GDB and GDB2 to the SD card. So that makes sense why I was getting error code 160. Must of removed it mistakenly after reviewing the metainfo2.txt file thinking it wasn't needed.
I should be able to just do user defined mode and select GDB and GDB2 after this finishes installing?

Edit2:
I added the missing GDB and GDB2 to SD card and ran engineering menu update again, it realised only those two were required so no need for user defined mode, just did standard. All updated with no issues 😃

 

[DrGER]

Getting 160 error now on database GDB:0.
Guess I'll reformat SD card and load back on to try again.

EDIT: just reviewed files and it looks like i forgot to add GDB and GDB2 to the SD card. So that makes sense why I was getting error code 160. Must of removed it mistakenly after reviewing the metainfo2.txt file thinking it wasn't needed.
I should be able to just do user defined mode and select GDB and GDB2 after this finishes installing?

OK, that's good to know: Error code 160 for missing source files.
Yes, you should only need to update those two components with your next user-defined update. --g

 

[bogdan.tud]

Hello everyone. A friend of mine asked me to help him install Navigation on his Audi. He bought the car 1 year ago and the previous owner did not give him a navigation SD card. I've never owned an Audi, but after a quick research and having a look through its menu, I understood that the software should be an MMI 3G. I saw that this thread is for that, and started downloading the data. How do I install the latest maps - 2023? I saw that this thread is for 2020. Do i:
1. Download the torrent linked in the first message
2. Follow the instructions and update this package
3. Go to mmi-3g-3gp-navigation-6-36-0-and-firmware-updates-currently-2023-europe(link) and do another update with that one?
or just follow the instructions in the 2023 thread? I want to help him, but without ruining its operating software
Thanks in advance

 

[DrGER]

@bogdan.tud -- Looks like a Q7 with BNav software. This thread is for MMI3G High (Hnav). You should be asking in the BNav thread: MMI 3G Basic navigation 5.35.2 and firmware updates -... --g

 

[bogdan.tud]

@bogdan.tud -- Looks like a Q7 with BNav software. This thread is for MMI3G High (Hnav). You should be asking in the BNav thread: MMI 3G Basic navigation 5.35.2 and firmware updates -... --g

@DrGER Thanks for your quick reply. The car is an Audi A6, but I guess the thread that you mentioned still applies. I'll head over there

 

[JulianHicks]

If you're building a 32GB 3GHigh Nav SD, you don't need these folders:

\CTYS3TC
\CTYS3TC2
\LIT3GP
\LIT3GP2
\LIT3GP3
\LIT3GP4
\LIT3GP5
\PSD
\PSD2
\PSD3
\SDS3GP
\TMC3GP

 

[pebe292]

So I have updated my Hnav to 0257_6 and maps to 636 and I've tried different activators and sd-cards, but I'm still blocked.
I've read everywhere til my eyes started to bleed.
But I can not fix the blocked nav.

 

[DrGER]

@pebe292 -- Try running my MMI3G/3GP Unblocker script first: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database.
It may be that earlier scripts left your HNav system in an unknown state. If that is the case, my recommendation is to re-install the K0257_6 again for the MU9038 device, only, and for sub-components ifs-root and efs-system, which are changed by all of the legacy so-called "activator" scripts, and re-run my Unblocker patch script. You need to do that as a User Defined update and select the ifs-root & efs-system Application components manually. --g