[pebe292]

@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

I can't choose User Defined.

 

[JulianHicks]

To enable 'User Defined' you can add the following two lines to the [Common] section of the metainfo2.txt in the root folder of the SD. [It only needs to be modified in the root folder file].

skipMetaCRC = "true"
EnableUserDefinedSWDLMode = "true"

J

 

[DrGER]

I can't choose User Defined.

User defined software update mode is set generally in the Green Engineering Menu:

The selection stays set until the system restarts. Or you can edit the metainfo2.txt file, as noted above. --g

 

[pebe292]

In which file should I edit metainfo? Map or 257-6?
I can't install engineering mode. I will try again.

Got Green engineering working.

 

[pebe292]

Ok, finally got User defined to be clickable.

But then what, can't do anything. Yes, the photo shows ifs-emg, it doesn't matter. I tried every where.

I think I have to give up and start all over again.
1. Reset
2. Install 257_6 D1
3. Install map 636
4. Install Unblocker

Is that correct?

DrGer said before "the MU9038 device ", but I could only find MU9037 in the folders.

 

[DrGER]

@pebe292 -- That's strange -- you should be able to select the Application component of the ifs-root & efs-system parts of the MU device to re-install these, only.

In any case, the nav database is stored on the HDD, so you shouldn't need to re-install that part. Re-installing K0257_6_D1 is sufficient. --g

 

[pebe292]

@pebe292 -- That's strange -- you should be able to select the Application component of the ifs-root & efs-system parts of the MU device to re-install these, only.

In any case, the nav database is stored on the HDD, so you shouldn't need to re-install that part. Re-installing K0257_6_D1 is sufficient. --g

Ok, how do I delete K0257_6_D1?

 

[DrGER]

@pebe292 -- I think you need to be in IPL mode with a serial console device to do that. But what about ticking both "user defined mode" and "ignore region and variant" boxes before trying to select the Application boxes under ifs-root & efs-system for K0257 ? --g

 

[pebe292]

@pebe292 -- I think you need to be in IPL mode with a serial console device to do that. But what about ticking both "user defined mode" and "ignore region and variant" boxes before trying to select the Application boxes under ifs-root & efs-system for K0257 ? --g

I ticked thoose boxes in Green meny. But I still can't tick the boxes in ifs or efs when in User defined.

 

[jmagui1.36]

Hello, I just bought an A4, it comes with Hnav_EU_k0206_3_D1 and 5.12.5, I am not very clear about the firmware and maps that I have to put.

Thanks

 

[DrGER]

@jmagui1.36 -- Start with HNav_EU_K0257_6_D1: 33.55 GB folder on MEGA
When you finish this and your MMI3G High system is updated, you can prepare to update the nav database. --g

 

[jmagui1.36]

@jmagui1.36 -- Start with HNav_EU_K0257_6_D1: 33.55 GB folder on MEGA
When you finish this and your MMI3G High system is updated, you can prepare to update the nav database. --g

Great, I have already downloaded HNav_EU_K0257_6_D1, what are the current maps.
Thank you.

 

[DrGER]

@jmagui1.36 -- Latest/current EU nav database update is 6.36.0, posted to the MMI3GP thread in this forum. Pay close attention to which packages are required for MMI3G, since ALL packages in the pkgdb directory/folder will not fit on a FAT32 32GB SD card. When you complete the navdb update & you get the "nav data is blocked" message on the MMI screen, you need to disable the Harman-Becker navdb activation process with a small software patch; I have one here: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database. --g

 

[jmagui1.36]

@jmagui1.36 -- Latest/current EU nav database update is 6.36.0, posted to the MMI3GP thread in this forum. Pay close attention to which packages are required for MMI3G, since ALL packages in the pkgdb directory/folder will not fit on a FAT32 32GB SD card. When you complete the navdb update & you get the "nav data is blocked" message on the MMI screen, you need to disable the Harman-Becker navdb activation process with a small software patch; I have one here: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database. --g

Thanks

 

[Keith-i]

@DrGER just a quick question about your unblocker script please. I updated my maps last year and used one of the generic activator scripts before I came across your improved method. I would like to 'clean up' my HNav filesystem and wonder if I were to now run your unblocker whether it would remove the previous changes to files like mme-becker.sh or I would have to manually clean up the files first. Thanks

 

[DrGER]

@Keith-i -- Thanks for asking. Short answer is "yes, it does that". You can inspect the file "run.sh" in a plain-text editor and see that my unblocker script first checks for evidence of the changes attributed to Vlasoff from early 2016 and if found, removes these changes to the original state. --g

 

[Keith-i]

@DrGER thanks for the reply, I thought as much having looked at run.sh with my limited knowledge but just wanted to double check.

 

[Keith-i]

@DrGER I've run your latest unblocker and also mmi3ginfo3. From the logs it looks to me as though it hasn't removed the old mme-becker.sh file which still seems to exist in the sbin folder. Is this correct or have I misinterpreted something. Has it undone the previous activator changes?

Unblocker log

[INFO] Start: Thu Jan 01 00:01:26 UTC 1970; Timestamp: 20240211_185822; MU: MMI3G

[INFO] MMI3G Nav Database Unblocker: navunblocker-v221225

[ACTI] Appending patch to /usr/bin/manage_cd.sh ...
mv: Moving /mnt/efs-system/usr/bin/manage_cd.sh to /mnt/efs-system/usr/bin/manage_cd.sh-ORIG
cp: Copying /mnt/efs-system/usr/bin/manage_cd.sh-ORIG to /mnt/efs-system/usr/bin/manage_cd.sh

[ACTI] Copy FSC and acios_db.ini files to /mnt/sdcard10t12/var
cp: Copying /mnt/efs-persist/FSC/00040004.fsc to /mnt/sdcard10t12/var/00040004.fsc
cp: Copying /mnt/efs-persist/navi/db/acios_db.ini to /mnt/sdcard10t12/var/acios_db.ini

[INFO] End: Thu Jan 01 00:01:30 UTC 1970; Timestamp: 20240211_185826

mmi3ginfo3 excerpt below

[INFO] Start: Thu Jan 01 00:01:49 UTC 1970; Timestamp: 20240213_155705
[INFO] MMI3G Info Dump: mmi3ginfo3-v231230

[INFO] MU train name: HNav_EU_K0257_6_D1
[INFO] MU software version: 0187
[INFO] MU variant: 9308
[INFO] MU hwSample: n/a

[INFO] Installed HDD: TOSHIBA MK4050GAC sn Z18ATINMT fw TG104A
[INFO] HDD reported cylinders: 38154
[INFO] HDD capacity (512 byte sectors): 78139392
[INFO] HDD partition table:

   _____OS_____     Start      End     ______Number______   Size    Boot 
   name    type    Cylinder  Cylinder  Cylinders   Blocks                 

1. QNX       77          0      23555     23556  48243132  23556 MB   *
2. QNY       78      23556      34372     10817  22153635  10817 MB
3. QNZ       79      34373      35203       831   1702890    831 MB
4. Extd'd     5      35204      38153      2950   6040440   2949 MB


[INFO] Installed navigation database info: 8R0060884KB ECE 6.35.1 2022/2023
[INFO] Nav database region code: 1
[INFO] Nav database release activation file: 00040024.fsc
[INFO] Nav database release FSC file not found !
[INFO] H-B navdb activation: enabled !
[INFO] Found LVM patch in /usr/bin/manage_cd.sh.

[INFO] Gracenote CD-Database part number: 8R0060961C
[INFO] Gracenote CD-Database version: 3638

[INFO] uname -a
QNX localhost 6.3.2 2009/10/30-15:33:18EDT HB_SH7785 shle



/mnt/efs-system/sbin:
total 252
-rwxrwxrwx  1 root           8236 Jun 06  2013 dloader
-rwxrwxrwx  1 root         119450 Jun 06  2013 fdisk
-rwxrwxrwx  1 root            104 Dec 14  2022 mme-becker.sh

 

[DrGER]

@Keith-i -- You should be using the unblocker version posted at my GitHub repository dated 20230308: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database.
Re your info log excerpt, we see that you ran this at about 110 seconds after start-up, which is too early; vdev-logvolmgr is likely just started and hasn't been terminated yet by the system patch. The mme-becker.sh script came from the old "activator" patch; my updated unblocker script looks for "mmelauncher.cfg.pre-navdb.bak", which came from the original Vlasoff script in early 2016 (and that all the variants have used since, that I can tell). If /mnt/efs-system/etc/mmelauncher.cfg is original, the mme-becker.sh is ignored, so it is harmless. But all of this is moot, anyway: look over here: https://www.a5oc.com/threads/upgrading-mmi-3g-high-multimedia.180005/ --g

 

[Keith-i]

@DrGER

You should be using the unblocker version posted at my GitHub repository dated 20230308: GitHub - DrGER2/MMI3G-Navdb-Unblocker: Patch MMI3G/3GP systems to unblock access to an updated navigation database.

Thanks, I did indeed use the version from your GitHub.

If /mnt/efs-system/etc/mmelauncher.cfg is original, the mme-becker.sh is ignored, so it is harmless. But all of this is moot, anyway: look over here: https://www.a5oc.com/threads/upgrading-mmi-3g-high-multimedia.180005/ --g

Hmmm, looking into the mmi3ginfo3 log a bit further it looks to me like the patched mmelauncher is still in use. Is it perhaps because it was renamed mmelauncher.cfg-ORIG rather than mmelauncher.cfg.pre-navdb.bak that your unblocker didn't spot it?

/mnt/efs-system/etc:
total 5641
drwxrwxrwx  5 root            488 Jun 06  2013 browser
drwxrwxrwx  2 root             48 Jun 06  2013 imageInfo
drwxrwxrwx  2 root            312 Jun 06  2013 splashscreens
drwxrwxrwx  2 root            104 Jun 06  2013 version
-rw-------  1 root          25240 Jun 06  2013 166x76audi.ipod
-rw-------  1 root          12284 Jun 06  2013 DefaultScope.hbtc
-rw-------  1 root           4689 Jun 06  2013 DefaultScopeJ9.hbtc
-rw-------  1 root           1450 Jun 06  2013 DefaultSwdlScope.hbtc
-rw-------  1 root           9972 Jun 06  2013 IRCConfig.cfg
-rw-------  1 root        2795545 Jun 06  2013 NvDspCodecs.elf
-rw-------  1 root            584 Jun 06  2013 components.cfg
-rw-------  1 root            839 Jun 06  2013 componentsSWDL.cfg
-rw-------  1 root            190 Jun 06  2013 group
-rw-------  1 root             98 Jun 06  2013 hosts
-rw-------  1 root           1576 Jun 06  2013 iom.cfg
-rw-------  1 root           1335 Jun 06  2013 lastmode.properties
-rw-------  1 root          19969 Jun 06  2013 mme.conf
-rwxrwxrwx  1 root           1980 Dec 14  2022 mmelauncher.cfg
-rw-------  1 root           1946 Jun 06  2013 mmelauncher.cfg-ORIG
-rw-------  1 root            296 Jun 06  2013 passwd
-rw-------  1 root           1191 Jun 06  2013 qdb-noHDD.cfg
-rw-------  1 root           1451 Jun 06  2013 qdb.cfg
-rw-------  1 root             27 Jun 06  2013 shadow

But all of this is moot, anyway: look over here: https://www.a5oc.com/threads/upgrading-mmi-3g-high-multimedia.180005/ --g

Yes, I've seen that thread. All very interesting but I'm not brave enough just yet...