Updating the NAR MMI 3G/3GP: Software & Navigation Database

Compiled by DrGER 17 Mar 2021; 31 Oct 2023 v1.10

 2

Table of Contents

1.0 Introduction 4
1.1 VW RNS-850 Systems 5
1.2 MMI 3G High Systems 5
1.3 Software Update Conditions 5
2.0 Update to NAR 6.16.2 2017/2018 Navigation Data 6
2.1 MMI 3G+ Software Update to NAR K0942_6 7
2.2 NAR 2017/2018 Navigation Database Update 12
2.3 Unblocking Navigation Data 13
2.4 Clearing Known DTCs Due to Updates 15
3.0 Update to NAR 6.24.0 and Later Navigation Data 17
3.1 Notes regarding navigation database updates 17
3.2 Update Procedure 18
3.4 Clearing Known DTCs Due to Updates 24
3.5 Troubleshooting Update Error(s) 24
3.6 MMI 3G High Navigation Data Updates 25
3.9 VW RNS-850 Update Notes 28
4.0 References 30
5.0 Acknowledgements 30
APPENDIX A 31
A.1 Reference - MMI3GP US9426 Software Update Device Summary (Table A.1) 31
APPENDIX B 34
B1. Enable Green Engineering Menu (GEM) 34
B.2 - Enable User Defined Software Update Mode 34
B.3 Software Update Logging 35
APPENDIX C 39
C.1 - DTC 03276 - Please Check Software Version Management 39
C.2 - DTC 03623 - Invalid Security/Release Code 40
C.3 - DTC 03677 - Missing FSC File 41
APPENDIX D 43
D.1 Preparing Navigation Data Update Media from Internet Downloads 43
D.2 Confirm Quality of Downloaded RAR Parts 43
D.3 Extract the Multi-Part RAR Archive 43
D.4 Prepare Release for User Defined Software Update 44
D.5 Validating Release Media 45
APPENDIX E 49
E.1 8R0906961FE HN+_US_AU3G_K0942_6 Manifest Summary 49

31 Oct 2023
 3

APPENDIX F 51
F.1 User Defined Navigation Database Update Device Selection Screens 51
APPENDIX G 54
G.1 Reference - MMI 3GP NAR 6.24.0 /mnt/nav/db File Size List 54
G.2 Reference - /efs-persist/navi/db/acios_db.ini File 56
APPENDIX H 57
H.1 Notes on VAG Module Adaptation Using Xtool VAG401 Diagnostic Tool 57
APPENDIX J 61
J.1 Updated Navigation Database Unblocker Patch Script 61
INSTALLATION CHECKLIST: NAR Navigation Database Update 3GP/3G+ 65

31 Oct 2023
 4

1.0 Introduction

This document is a record of observations and research by the author with regard to updating the
MMI3GP system software and navigation database on a 2014 Audi A4 with MMI 3G+ system. It
is comprised of several sections and appendices:

Section 2: (1) Updating the MMI 3G+ (HN+) software from production version P0715 to current
K0942_6, (2) updating the navigation data using purchased database and “activator pack” SD
cards, and (3) clearing DTCs due to the MMI update process.

Section 3: Updating later versions of the navigation data using SD cards created from installation
archives downloaded from internet sites, including NAR MMI 3G High (HNav) and VW RNS850
(HN+) systems.

The various appendices offer reference information and additional details for planning and
executing these updates.

DISCLAIMER: Use this guide at your own risk. The author is not responsible for any
mis-application of the procedures described herein resulting in loss of MMI functionality.
When we purchased our A4 used as third owners in July 2017, the MMI system had the original
production software (HN+_US_AU3G_P0715) and navigation database (8R0060884BD NAR
6.8.2 2012/2013) installed (build date Oct 2013), as reported on the [MENU] >> [MMI Setup] >>
Version information screen (Fig. 1.1).

Fig. 1.1 Production MMI version information.

The build code for this configuration is PR-7T6 (Navigation system (MID)), noted on the vehicle
information sticker affixed to the body under the luggage compartment floor. The VAG hardware
part number of the MMI main unit is 8R1035746D (for mmi 3g +), as reported by VCDS and the
Green Engineering Menu.

31 Oct 2023
 5

We note here that navigation databases released for MMI3GP (3G Plus) systems apply also to
systems with software version HN+R_US_AU3G (includes Q3, A6, A7, and A8 models) and can
be adapted for use in VW RNS-850 systems.

1.1 VW RNS-850 Systems

RNS-850 systems installed in VW Touareg models are made by Harman-Becker using the
MMI3GP main unit. As a result, the procedures described here can be applied directly, with a
few exceptions due to differences in the user interface. The current NAR version is
HN+_US_VW_K0711 (released in 2013). The current EUR/RoW version is
HN+_EU_VW_K0821.

1.2 MMI 3G High Systems

Earlier NAR MMI 3G High systems (e.g., used in the MY2009-2012 B8 platform) can use the
same original (unmodified) NAR navigation update media as MMI 3GP/3G+ systems. The
current software version of NAR MMI 3G High systems is HNav_US_K0133_3_D1. We assume
that NAR MMI 3G High systems will be updated to HNav_US_K0133_3_D1 prior to any
navigation data updates. Specific procedures for updating the software of MMI 3G High systems
are beyond the scope of this document. Refer to section 3.8 for brief remarks regarding the minor
differences between MMI 3G High and 3GP/3G+ navigation data updates.

1.3 Software Update Conditions

1. Ignition OFF;
2. Battery maintainer attached (we use a CTEK MUS 5.0).

31 Oct 2023
 6

2.0 Update to NAR 6.16.2 2017/2018 Navigation Data

In September 2018, the author obtained a set of media (SD cards) from an eBay vendor in the
UK to update the navigation database to NAR 6.16.2 (NAR 2017/2018). This SD media set
included:

1. 8R0906961FE Updatemedium SVM: US9426 (K0942_6), assembled Oct 2016:

2. 8R0051884EN NAR Version 2017/2018 Pack No. US/6.16.2, assembled Nov 2017:

3. 8R0060884EN Activation Pack NAR 6.16.2:

We know now that the first two SD cards are not genuine OE parts, given that the bar codes on
their labels are fake and that the contents of these SD cards matches known MMI3G software and
navigation database archives. We also know with certainty that the third SD card is not original
equipment, as the so-called “activation” script does not, in fact, provide a proper activation

31 Oct 2023
 7

license for the updated navigation database as described in Audi Technical Service Bulletins. We
discuss this later in section 2.3.

The navigation database update requires that the MMI software be updated first; we proceed with
that task in the next section.

2.1 MMI 3G+ Software Update to NAR K0942_6

All recent navigation database versions after 2016 or so require MMI software version K0900,
minimum. This section describes updating the NAR MMI 3GP system to K0942_6 using SD
8R0906961FE or equivalent SD card prepared with the update release files.

1. Prepare as noted in 1.3, above.

2. MMI turned ON using the console power/volume control.

3. Wait for all functions (Car, Media, Navigation, Radio, Telephone) to start fully.

4. Confirm that the MMI system time source is set to GPS (Fig. 2.1). This setting ensures
that software update logging information has correct date/time stamps.

Fig. 2.1 MMI [Time] setting for Time source set to GPS.

5. Enter the Red Engineering Menu (REM) with [CAR]+[BACK].

n.b.: Screenshots in this section were obtained after the original update was performed in
Oct 2018, and with the update SD card in MMI SD Slot 2, to allow for screenshots to be
captured on the SD card in SD Slot 1. In general, the source of MMI software updates
can be either SD1 or SD2. The images presented here are intended for general reference.

31 Oct 2023
 8

Fig. 2.2 REM start screen with [Settings], [System], and [Update] softkeys.

6. Insert write-protected SD card 8R0906961FE (US9426) or equivalent in MMI SD Slot 1

or 2.

7. Select REM softkey [Update] (Fig 2.2).

8. Scroll to SD 1 or SD 2 and select (Software update: Select source) (Fig. 2.3).

Fig. 2.3 REM Update source selection screen.

9. Select release HN+_US_AU3G_K0942_6 (Software update: SD 2) (Fig. 2.4).

31 Oct 2023
 9

Fig. 2.4 REM Update release selection screen.

10. Select Standard (Software update: SD 2 - HN+_US_AU3G_K0942_6) (Fig. 2.5).

Fig. 2.5 REM Update type selection (Standard) screen.

11. Scroll to end of Device selection list and select Start update (Fig. 2.6).

31 Oct 2023
 10

Fig. 2.6 Device Selection: Start update.

n.b.: Applications with external Bose or B&O audio amplifiers may use the User defined
update method so that the Bose or B&O software is not updated by the end-user. In our
case, our B&O amplifier and DSP audio (AMPLCPKO) was not selected by the Standard
update.

In the unlikely case that the Bose or B&O audio component is selected here, (1) exit the
REM with [CAR]+[BACK], (2) enable User Defined Update in the GEM (see Appendix B),
(3) restart this section, (4) select User defined at Step 9, above, and (5) remove the Bose
or B&O audio component from the selected devices before continuing with the software
update.

We note here that B&O devices AMP_LC_P and AMPLCPKO have not been updated by
the manufacturer since the original production releases in 2008.

12. Confirm on next screen by selecting Start. MMI will restart and update will continue.

Document update progress with pictures of update screens.

13. After all selected device updates are complete, the MMI will restart and return to the REM
with a Device summary list. Review the Device summary, as needed. In general, we’re
looking for OK on component selections that were installed successfully. Component
selections with NOK should be investigated before continuing. This information is also
visible from the REM [Logging] function, as described in Appendix B.3.

14. Scroll to the end of the Device summary list and select Continue to continue to the last
step (Fig. 2.6).

31 Oct 2023
 11

Fig. 2.6 Device summary - Continue.

15. Scroll to Abort documentation and select (Fig. 2.7). MMI will restart into normal
operation.

Fig. 2.7 REM final software update screen.

16. Remove write-protected SD card 8R0906961FE (US9426) from the MMI SD slot. Insert
writable SD card in SD Slot 1 (for screenshots documentation):

[MENU] >> [MMI Setup] >> Version information

Software version:
HN+_US_AU3G_K0942_6 (updated version)

Navigation database version:

8R0060884BD NAR 6.8.2 (NAR 2012/2013)

17. Confirm all MMI functions work properly.

31 Oct 2023
 12

2.2 NAR 2017/2018 Navigation Database Update

Remarks in this section apply generally to initial navigation database updates from the
production release. In these cases, the production database release is activated properly with a
valid FSC file and the MMI operating system is otherwise modified or patched.

Regarding instructions to delete the current navigation data and disk partition (by reformatting)
prior to updating/installing new navigation data, at the time we performed the update in Oct
2018, various installation documents compiled by third-parties offered differing views on
whether it was necessary to delete current navigation data (database or partition) using the Green
Engineering Menu. Recent guidance notes that the navigation database should be deleted prior
to a database update only when data for a new region is to be installed (e.g., NAR to ECE).
Reformatting the navigation partition, however, is expected only when the partition is known to
be corrupted; note that since the GEMMI package is stored on the nav database partition,
/mnt/nav, the GEMMI package must be reinstalled from the US09426 (8R0906961FE) SD card as
described in the previous section. Certain early MMI3G (HNav) systems may benefit from
formatting the nav HDD partition; this is discussed in a later section.

If a newer version of the navigation database is currently installed in place of the production
version, refer to section 3.0. The section applies only for the initial navigation database update.

1. Prep as noted in 1.3, above.

2. MMI turned ON using the console power/volume control.

3. Wait for all functions (Car, Media, Nav, Radio, Tel) to start fully.

4. Ensure time setting (Fig. 2.1) for correct software update logging.

5. Enter the Red Engineering Menu (REM) with [CAR]+[BACK].

6. Insert write-protected SD card 8R0051884EN (NAR 2017/2018) or later version in MMI

SD Slot 1 or 2.

7. Select REM softkey [Update].

8. Scroll to SD 1 or SD 2 and select (Software update: Select source)

31 Oct 2023
 13

9. Select NAR 6.16.2 (MMI3GP) (Software update: SD 2)

10. Select Standard (Software update: SD 2 - NAR 6.16.2 (MMI3GP))

11. Scroll to end of Device selection list and select Start update.

12. Confirm on next screen by selecting Start. MMI will restart and update will continue.

Document update progress with pictures of update screens.

13. After all selected device updates are complete, the MMI will restart and return to the
REM with a Device summary list. Review the Device summary, as needed. In general,
we expect to find OK on component selections that were installed successfully (Fig. 2.8).
This information is also visible from the REM [Logging] function, as described in
Appendix B.3.

Fig. 2.8 Package AUDI_MMI3G_NAR updated successfully.

Scroll to the end of the list and select Continue to continue to the last step.

14. Scroll to Abort documentation and select (Fig. 2.5). MMI will restart into normal
operation.

15. Remove SD card 8R0051884EN (NAR 2017/2018) from the MMI SD slot.

2.3 Unblocking Navigation Data

After a (brief) period, an attempt to access [NAV] will return a notice on MMI3GP systems that
“the navigation data is unavailable” (Fig. 2.9):

31 Oct 2023
 14

Fig. 2.9 Note: The navigation data is not available (MMI3GP).

This indicates that the updated navigation database is not available for use, as the new nav
database release was not activated properly using the ODIS SVM - Activation process, which
generates a new FSC (FreiSchaltung Code) file for the specific installation (VIN and navigation
database release), as defined in the release PKG file. When a valid FSC file is not available for
the navigation database update, end-users can apply a software patch to the MMI system that
disables the normal activation process used by the Harman-Becker MMI3G system.

The SD card supplied here with VAG part number 8R0060884EN has been determined to be
based on the method described by Keldo in early 2016 (and attributed to Vlasoff) to disable the
normal navigation database activation process.

This activation process is disabled when system process vdev-logvolmgr is terminated shortly
after regular file acios_db.ini is created in the /mnt/lvm filesystem. An established approach to
disabling the activation process is to add the following shell commands as a background
sub-shell to an existing shell script that is called during the system boot/startup process:

waitfor /mnt/lvm/acios_db.ini 180 && sleep 10 && slay vdev-logvolmgr

A common approach since early 2016 has been to add this code to a new shell script that starts
the mme-becker system process (by way of the mmelauncher process and its configuration file
mmelauncher.cfg), as found here on the so-called “activator” SD card.

The solution proposed here is to patch system file /mnt/efs-system/usr/bin/manage_cd.sh,

which is common to MMI3G, MMI3GP, and RNS-850 systems, by appending the patch text to the
script as:

(waitfor /mnt/lvm/acios_db.ini 180 && sleep 10 && slay vdev-logvolmgr)&

31 Oct 2023
 15

The navigation database unblocker patch installer shell script is presented here in Appendix J.1.

With the navigation database activation process disabled, document the finished update:

Insert writable SD card in SD Slot 1 (for screenshot documentation):

1. [MENU] >> [MMI Setup] >> Version information (Fig 2.10).

Fig. 2.10 Updated MMI Version Information.

2. [GEM] >> dtc >> qualified_dtcs (Fig. 2.10).

Fig. 2.12 GEM Qualified DTCs.

2.4 Clearing Known DTCs Due to Updates

Scanning module 5F - Information Electr. with a VAG scan tool will return fault codes typically:

31 Oct 2023
 16

03276 - Please Check Software Version Management

03623 - Invalid Security/Release Code

Procedures for clearing DTC 03276 are presented in Appendix C.1.

Procedures for clearing DTC 03623 are presented in Appendix C.2.

31 Oct 2023
 17

3.0 Update to NAR 6.24.0 and Later Navigation Data

Recent available media for NAR navigation database updates include:

8R0051884JE NAR 6.24.0 (NAR 2021/2022), assembled Aug 2020 (Fig. 3.1).

Fig. 3.1 NAR 6.24.0 Navigation Database.

3.1 Notes regarding navigation database updates

1. All recent NAR navigation data require MMI 3GP (HN+) software version K0900, at
least. Refer to the procedure in section 2.1, above, before proceeding with the navigation
database update and be prepared to patch the system with the navigation database
unblocker script following the navigation database update.

2. MMI3G (both High and Plus) systems that were patched with the navigation database
unblocker script after updating the MMI 3GP software to version K0942_6 will not
require patching following later navigation database updates.

3. Navigation data can be updated directly from any release in the same region, including
from the factory installed version; deleting the current navigation database or
reformatting the disk partition using the GEM in this case is not necessary nor is it
recommended, in general.

4. High quality, high speed SDHC cards should be used to install the navigation database
update. Sandisk 32 GB Ultra 80 MB/s and faster SDHC cards are recommended. Avoid
the use of microSD cards with full size adapters.

31 Oct 2023
 18

3.2 Update Procedure

This section describes a process for updating the navigation database as a user-defined software
update given a properly formatted (FAT32) 32 GB SDHC card populated with the correct NAR
navigation data update (refer to Appendix D for remarks on preparing the update SD card from
downloaded archives). An abbreviated check-list of this procedure can be found on the last page
of this document.

1. Prep as noted in 1.3, above.

2. Enable User defined mode for software updates in the GEM (Appendix B.2).

3. Enter the Red Engineering Menu (REM) with [CAR]+[BACK].

4. Insert write-protected NAR navigation update SD card in MMI SD Slot 1 or 2.

5. Select REM softkey [Update] (Fig 3.2).

Fig. 3.2 REM start screen with [Settings], [System], and [Update] softkeys.

6. Scroll to SD n and select (Software update: Select source) (Fig 3.3).

31 Oct 2023
 19

Fig. 3.3 Source selection.

7. Select software release NAR 6.x.y (MMI3GP) (Software update: SD n) (Fig. 3.4).

Fig. 3.4 Update software release selection.

8. Select User defined (Software update: SD n - NAR 6.x.y (MMI3GP)) (Fig. 3.5).

31 Oct 2023
 20

Fig. 3.5 User defined mode selection.

9. Select navigation database components to be updated manually:

a. Scroll to the entry for AUDI_MMI3G_NAR and note the selection status indicator:
Y, N, S, ?, or N/A. An indicator of ? requires manual selection of installation
packages (Fig. 3.5). Select AUDI_MMI3G_NAR to continue.

Fig. 3.6 User defined update required here.

b. For each sub-entry under AUDI_MMI3G_NAR, select the sub-entry, select the
Application component, as required, and return (Fig. 3.6).

Do not select the Bootloader component for any sub-entries. Note also that
update is not required when the Application version number does not change (as
shown in Fig. 3.6); in this case, package LABEL_NAR can be omitted safely from
the current navigation database update.

31 Oct 2023
 21

Fig. 3.7 Application component of package LABEL_NAR selected.

c. After all appropriate Application components are selected, return to the top-level
device selection list.

d. In some cases, entries NaviPersistence and MapStyles may also require updating,
depending on their versions in the new release (cf. Appendix A). Select each to
view their respective sub-entry lists. As in (b), above, review each of the
Application versions to determine whether a component should be selected for
updating. In general, version numbers that are the same (e.g., as in Fig. 3.7) may
be omitted from the update.

e. After all sub-entry Application components are selected for updating, return to the
top-level device selection list. Appendix F offers screenshots of the NAR device
selection screens for additional reference.

10. Scroll to end of Device selection list and select Start update (Fig 3.4)

31 Oct 2023
 22

Fig. 3.8 Start update selection.

11. Confirm on next screen by selecting Start (Fig. 3.5). MMI will restart and the update will
continue.

Fig. 3.9 Software update confirmation screen.

Document progress with pictures of MMI display for each update step.

12. After all selected device updates are complete, the MMI will restart and return to the REM
with a Device summary list. Review Device summary, as needed. In general, we’re
looking for OK on component selections that were installed successfully (Fig. 3.10).

31 Oct 2023
 23

Fig. 3.10 Device summary OK.

Component selections with NOK indicate problems with the installation (Fig. 3.4); refer
to section 3.6, below, for further discussion. This information is also visible from the
REM [Logging] function, as described in Appendix B.3.

Scroll to the end of the list. Select Continue to continue to the last step (Fig. 3.9).

Fig. 3.11 Device summary - continue.

13. Scroll to Abort documentation (Fig. 2.5) and select. MMI will restart into normal
operation.

14. Confirm all MMI functions work properly.

15. Remove update card from its SD slot 1 or 2 and insert write-enabled SD card in Slot 1 for
screenshot documentation:

31 Oct 2023
 24

a. [MENU] >> [MMI Setup] >> Version information

b. [GEM] >> dtc >> qualified_dtcs

Refer to section 2.4, above, and Appendix C for remarks regarding DTC fault codes in module
5F as a result of the navigation database update.

3.4 Clearing Known DTCs Due to Updates

Refer to section 2.4, above, to clear DTCs 03276 and 03623 in Address 5F, Information Electr.,
due to the navigation database update. Refer to Appendix C.3 to clear DTC 03677 - Missing FSC
File following the second and subsequent navigation database updates.

3.5 Troubleshooting Update Error(s)

Package components that report update errors are due often to faulty or low quality SD cards
(Error code 150), but may be due to no space left on the HDD partition (Error code 140) or
missing source files (Error code 160).

Fig. 3.12 Device error: Error code 160 (credit Theiceman)

When Error code 150 is reported during the REM Update process, entry Retry should be applied
until the device is updated successfully. Error codes 140 (no space on device) and 160 (no source
file to copy) must be investigated separately.

In cases where a navigation database update ends with a result of NOK on the Device summary
list (Fig. 3.4), (1) the update should be concluded normally, (2) a new 32 GB SDHC card
formatted as FAT32 should be prepared as described in Appendix D, and (3) the update repeated
from 3.1, above, until all devices report OK in the final Device summary list (Fig. 2.6).

31 Oct 2023
 25

Fig. 3.13 Device summary: AUDI_MMI3G_NAR: NOK (credit Theiceman)

Note that log information for software updates initiated by the REM [Update] function can be
reviewed at any time with the REM [Logging] function, as described in Appendix B.3.

3.6 MMI 3G High Navigation Data Updates

The OE navigation data update SD media always includes releases for both NAR MMI 3G High
(HNav) and 3GP/3G+ (HN+) systems. Differences in the installation procedure described in
sections 2.2 and 3.2, above, are minor. The first difference is the release name to select after
inserting the nav data update SDHC card in Slot 1 or 2. For NAR MMI 3G High, this is: NAR
6.x.y (MMI3G)

The second difference noted affects a subset of components of the AUDI_MMI3G_NAR device
selection (Fig. 3.2). These are summarized in Table 3.1.

Table 3.1 NAR MMI3G / MMI3GP Device Selection Components.

NAR 6.x.y (MMI3G) NAR 6.x.y (MMI3GP)

CTY_NAR CTYS3TC_NAR

TMC_NAR TMC3GP_NAR

LIT_NAR LIT3GP_NAR

LIT2_NAR LIT3GP2_NAR

LIT3_NAR LIT3GP3_NAR

LIT4_NAR LIT3GP4_NAR

31 Oct 2023
 26

n/a PSD_NAR

n/a PSD2_NAR

SDS_NAR SDS3GP_NAR

The last difference to note here is that device selection MapStyles version number for the MMI3G
release is not the same as the MMI3GP release, hence, it should be checked during package
selection, as noted in 3.2.9.d, above.

In any case, the pkgdb directory/folder should be inspected to ensure that the downloaded
archive includes the correct packages for the release to be installed (Table 3.2).

Table 3.2 NAR MMI3G / MMI3GP Required Packages

NAR MMI3G pkgdb Listing NAR MMI3GP pkgdb Listing

CTY_NAR CTYS3TC_NAR

GDB_NAR GDB_NAR

GDB2_NAR GDB2_NAR

LABEL_NAR LABEL_NAR

LIT_NAR LIT3GP_NAR

LIT2_NAR LIT3GP2_NAR

LIT3_NAR LIT3GP3_NAR

LIT4_NAR LIT3GP4_NAR

MMI3G_NAR_Hi_R_6_x_y.pkg MMI3GP_NAR_Hi_R_6_x_y.pkg

MMI3G_NAR_Hi_R_6_x_y.pkg.sig MMI3GP_NAR_Hi_R_6_x_y.pkg.sig

NaviPersistence_NAR_3 NaviPersistence_NAR_3

PIT_NAR PIT_NAR

(n/a) PSD_NAR

(n/a) PSD2_NAR

SDS_NAR SDS3GP_NAR

StyleDBMMI3G_NAR_9x StyleDBMMI3GP_NAR_9xxx

TER_NAR TER_NAR

TER2_NAR TER2_NAR

31 Oct 2023
 27

TER3_NAR TER3_NAR

TMC_NAR TMC3GP_NAR

XAC_NAR XAC_NAR

XAC2_NAR XAC2_NAR

When the production MMI3G navigation database is updated without proper activation by the
ODIS - Activation function, accessing the [NAV] function will display the Note “the navigation
data is blocked.” (Fig. 3.14).

Fig. 3.14 The navigation data is blocked (MMI3G) (credit NucMed)

Refer to section 2.3 for remarks on unblocking the new navigation data by patching the MMI3G
QNX operating system with an SD card shell script to disable the normal Harman-Becker
navigation database activation process.

We conclude our remarks about updating the MMI3G navigation database by noting that the
/mnt/nav HDD partition as delivered from the factory may require reformatting in the Green
Engineering Menu (with [Delete Nav HDD partition]) to ensure that future navigation database
updates have sufficient space on the HDD (Fig 3.15).

31 Oct 2023
 28

Fig. 3.15 HNav Green Engineering Menu /nav/databaseupdate (credit NucMed)

3.9 VW RNS-850 Update Notes

As noted earlier, the RNS-850 system installed in VW Touareg models uses main unit variant
9478 (MU9478) of the Harman-Becker MMI3GP series.

The production software version is confirmed by accessing the Engineering screen with
[SETUP]+[PHONE] (Fig. 3.16).

Fig. 3.16 RNS-850 Production Engineering Menu Screen (credit ahmed.t.braimah)

MU software versions prior to 0706 should be updated to the current version before any
navigation database updates (Fig. 3.17).

31 Oct 2023
 29

Fig. 3.17 NAR RNS-860 Updated to HN+_US_VW_K0711 (credit ahmed.t.braimah)

The K0711 software update also adds the System > Software information menu item and screen,
which also reports the navigation database version and VAG part number (Fig. 3.8).

Fig. 3.18 RNS-850 Software version information screen (credit ahmed.t.brainmah)

31 Oct 2023
 30

4.0 References

https://www.a5oc.com/threads/mmi-3g-3gp-navigation-6-31-1-and-firmware-updates-
currently-2020-2021.113737/

https://www.docdroid.net/mqjDVM2/update-instructions-for-mmi-3g-v17-pdf

Decimal to Hex Converter:

https://www.rapidtables.com/convert/number/decimal-to-hex.html

MMI copie_scr.sh Script Decrypter:

https://github.com/megusta1337/Copie_scr_Decoder

5.0 Acknowledgements

A few acknowledgements here for their contributions (however unwitting) to this work:

ahmed.t.braimah@clubtouareg.com (RNS-850 PNG screenshots)

audimib@audizine.com (SD script ideas)
BlueStar@audizine.com (reminder that GEMMI lives on the nav partition)
dhuddleson@a5oc.com (7-zip, don’t do multiple downloads from Google Drive)
Hiwasss@a5oc.com (nav data unavailable screenshot PNG).
Jimingle10@audizine.com (source of MMI3GP NAR 6.24.0 update media)
JulianHicks@a5oc.com (REM logging, HN+R QNX information, many others)
Lysy@clubtouareg.com (RNS-850 info, release PKG file userflags parameter)
My_name_is_rob@a5oc.com (feedback on document)
NucMed@ozaudi.com (HNav screenshots, information on ROW navdb release)
rydah@audizine.com (source of MMI3GP NAR 6.22.1 update)
spijun@audiworld.com (source of MMI3GP NAR 6.19.1 and 6.20.1 update archives)
stayfunny@audizine.com (thoughts on MMI3G High updates)
Theiceman@audizine.com (images of errors and a NOK update)

31 Oct 2023
 31

APPENDIX A

A.1 Reference - MMI3GP US9426 Software Update Device Summary (Table A.1)

Table A.1 HN+_US_AU3GP_K0942_6 Software Update Device Summary

Device Name Selected Updated Description

AMPLCPKO N - B&O amplifier, DSP applications

ARU9471 S OK RU, Radio Unit

DVD N - FJ-TEN DV-05 FEAT2

AH6 N - Cinterion AH6 NAR modem; to v 300100

KBD_FB8 N - unknown

MuIOC Y OK MainUnit IO controller; to v 1341

MuINIC Y OK MainUnit MOST controller; to v 17892131

DUA130 N - DU7 High, Display Unit; v 104

MU9498 S OK MainUnit ImageLayout (9498) to v 1040

MuGPS N - GPS Chip & Firmware

CombiStyles N - CombiStyles NAR (v12); v 12

GEMMI Y OK Google Earth MMI; to v 8025

sss S OK Speech - Tts

AudiSupportedFscs Y OK Supported FCSs ? to v 7

MapStyles Y OK MapStyles NAR (v06); to v 9120

MuTnrRef Y OK Spare Part Number List; to v 528

TMCConfig Y OK TMCConfig; to v 16

MUConsistency Y OK MU Consistency; to v 1041

31 Oct 2023
 32

A.2 Reference - NAR MMI3GP Release Information

Information in Table A.1 includes NavTeq release information extracted from the LIT3GP
database file using strings(1).

Table A.1 NAR MMI3GP Release Information

VAG Part Number Version 1 Version 2 NavTeq Release String

8R0051884EN NAR 6.16.2 NAR 2017/2018 North America NavTeq Q3/2016 MMI3GP

8R0051884GB NAR 6.19.1 NAR 2019 North America NavTeq Q1/2018 MMI3GP

8R0051884GJ NAR 6.20.1 NAR 2019/2020 North America NavTeq Q3/2018 MMI3GP

8R0051884HG NAR 6.22.1 NAR 2020/2021 North America NavTeq Q3/2019 MMI3GP

8R0051884JE NAR 6.24.0 NAR 2021/2022 North America NavTeq Q3/2020 MMI3GP

A.3 Reference - AUDI_MMI3G_NAR Component Version Numbers (Decimal/Hex) - 3GP

Component NAR 6.16.2 NAR 6.20.1 NAR 6.22.1 NAR 6.24.0

LABEL_NAR 366850 / 0x59902 366850 / 0x59902 366850 / 0x59902 366850 / 0x59902

CTYS3TC_NAR 398849 / 0x61601 401408 / 0x62000 401920 / 0x62200 402432 / 0x62400

TER_NAR 329474 / 0x50702 329474 / 0x50702 329474 / 0x50702 329474 / 0x50702

TER2_NAR 329474 / 0x50702 329474 / 0x50702 329474 / 0x50702 329474 / 0x50702

TER3_NAR 329474 / 0x50702 329474 / 0x50702 329474 / 0x50702 329474 / 0x50702

GDB_NAR 398849 / 0x61601 401408 / 0x62000 401921 / 0x62201 402432 / 0x62400

GDB2_NAR 398849 / 0x61601 401408 / 0x62000 401921 / 0x62201 402432 / 0x62400

TMC3GP_NAR 398848 / 0x61600 401408 / 0x62000 401921 / 0x62201 402432 / 0x62400

PIT_NAR 398849 / 0x61601 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

XAC_NAR 398848 / 0x61600 401408 / 0x62000 401921 / 0x62201 402432 / 0x62400

XAC2_NAR 398848 / 0x61600 401408 / 0x62000 401921 / 0x62201 402432 / 0x62400

PSD_NAR 398850 / 0x61602 401408 / 0x62000 401921 / 0x62201 402432 / 0x62400

PSD2_NAR 398850 / 0x61602 401408 / 0x62000 401921 / 0x62201 402432 / 0x62400

31 Oct 2023
 33

LIT3GP_NAR 398849 / 0x61601 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

LIT3GP2_NAR 398849 / 0x61601 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

LIT3GP3_NAR 398849 / 0x61601 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

LIT3GP4_NAR 398849 / 0x61601 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

SDS3GP_NAR 398850 / 0x61602 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

config.nfm 366848 / 0x61600 366848 / 0x61600 366848 / 0x61600 366848 / 0x61600

DBInfo.txt 398850 / 0x61602 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

PKG 398850 / 0x61602 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

SIG 398850 / 0x61602 401409 / 0x62001 401921 / 0x62201 402432 / 0x62400

A.4 Reference - NaviPersistence Component Version Numbers (Decimal)

Both package components script and xml have version “3” since the NAR 6.16.2 release.

A.5 Reference - MapStyles Component Version Numbers (Decimal) - 3GP

Package component NAR was version “9129” for the NAR 6.16.2 release. Since NAR 6.19.1,
the version is “9131”.

A.6 Reference - MapStyles Component Version Numbers (Decimal) - 3G High

Package component NAR has version “94” since the NAR 6.16.2 release.

31 Oct 2023
 34

APPENDIX B

B1. Enable Green Engineering Menu (GEM)

When the GEM is not enabled (i.e., holding [CAR]+[MENU] has no effect), the GEM can be
enabled by setting the value of Adaptation channel 6 to ‘1’ for Control Module Address 5F -
Information Electr.:

1. Using a VAG diagnostic scan tool (VCDS, VAG401, Foxwell NT510, etc.):
a. Open Control Module Address 5F.
b. Open function for Adaptations.
c. Open Adaptation Channel 6.
d. Set the Adaptation Value to 1 and Save.

An example using VCDS is presented here:

https://www.car-auto-repair.com/how-to-enable-audi-mmi-green-menu-hidden-menu-
by-vcds-script/

An example using VAG401 is presented here in Appendix H.

2. OBDII Bluetooth applications that are VAG-aware (e.g.., Carista, OBDeleven) have
special functions to enable the Green Engineering Menu with a single selection.

Once set, the GEM can be accessed directly without restarting the MMI.

B.2 - Enable User Defined Software Update Mode

With the MMI turned ON and at the main menu:

1. Start the Green Engineering Menu (GEM) with [CAR]+[MENU].

n.b.: If the GEM is not already enabled, refer to section B.1, above.

2. Scroll to swdl and select (Fig. B.1).

31 Oct 2023
 35

Fig. B.1 Green Engineering Menu entry for swdl.

3. Scroll to user defined mode and select (Fig. B.2).

Fig. B.2 User defined mode selected.

4. Exit Green Engineering Menu with [MENU].

User defined mode is enabled until the next MMI power cycle or system restart; it is not a
persistent configuration setting.

B.3 Software Update Logging

Information about software updates initiated using the REM [Update] function are saved in the
/mnt/efs-persist/SWDL/Log directory of the MMI hard disk as encoded and zlib compressed
files. The [Logging] function of [REM] >> [Update] can be used to display this log information
at any time (Fig. B.3).

31 Oct 2023
 36

Fig. B.3 Available Software Update Logging Information.

Selecting a listed software update returns a menu of log information that can be displayed (Fig
B.4).

Fig. B.4 Logging information menu selections.

Selecting General information returns (1) update mode (standard, user-defined); (2) start
date/time of the update; (3) end date/time of the update; (4) whether the update was the result of
a retry; (5) update release name; etc. (Fig. B.5).

31 Oct 2023
 37

Fig. B.5 Software Update Logging: General information.

Of particular interest here is the Device summary selection (Fig B.6).

Fig. B.6 Software Update Logging: Device summary.

Review of this section reports devices that were affected by the update. As noted in previous
sections, software for devices listed as OK was updated successfully. Selecting an item in the
Device summary list returns detailed status of the component that was updated (Fig. B.7).

31 Oct 2023
 38

Fig. B.7 Detail component update status.

Return to the normal MMI system menus from the REM Software Update Logging viewer with
[CAR]+[BACK].

31 Oct 2023
 39

APPENDIX C

C.1 - DTC 03276 - Please Check Software Version Management

According to ross-tech.com, DTC 03276 is issued when “a Control Module Software Update has
been performed, but the required Feedback/Specification Documentation via Software Version
Management (SVM) was not” (URL:http://wiki.ross-tech.com/wiki/index.php/03276). DTC
03276 is cleared by either (1) performing Feedback/Specification Documentation via Software
Version Management (SVM) or (2) submitting a calculated check value to Adaptation Channel
15 of Module 5F using an appropriate VAG diagnostic tool. End-user VAG diagnostic tools that
can perform this adaptation include Foxwell NT-510 (and similar) and Ross-Tech VCDS tools.

A method for clearing DTC 03276 using VCDS is presented here:

https://www.audienthusiasts.com/Application_SVMError.html

Alternate methods for clearing DTC 03276 using the Foxwell NT-510 and VAG401 tools follow:

With the appropriate tool attached to the OBDII port and ignition ON (engine OFF):

Foxwell NT-510

1. Select: V/A (VAG) >> 2 Audi >> 1 Systems >> 4 Control Unit >> 6 Electronics 2 >>
5F-Information Electr.
2. Function Menu: select: 1 Read Codes
3. Function Menu: select: 9 Adaptation
4. Adaptation: select: 1 Input the channel number
5. Adaptation: select: [Keyboard] 015 [Finish]
6. Input Dialog Box: select [Yes]
7. CH NO. 15: Record value from “No text” field (e.g., 22657)
8. Calculate: X [XOR] 51666 (see n.b., below)
9. CH NO. 15: select: [Set new val]
10. Set new Value: select: [Keyboard] <value from 7, above> [Finish]
11. Input Dialog Box: select: [Yes]
12. HERE? - select [OK]
13. Confirm DTC 03276 is cleared: 3 Erase Codes >> 1 Read Codes

Xtool VAG401

1. Diagnosis systems >> Electric System 2 >> 5f - Message options >> [ENTER]
2. 5f - Message options: 02-Read fault codes >> [ENTER] >> [ENTER] >> [ENTER]
3. 5f - Message options: 10-Adaptations >> 015 [ENTER]

31 Oct 2023
 40

4. Channel Number:015: Record value below “Matched data” line (e.g., 22657.0)
5. Calculate: X [XOR] 51666 (see n.b., below)
6. Press [ENTER] for the “Input matched data screen”, enter <value from 5, above>, press
[ENTER] when complete
7. Press [ENTER] display new “Match data” value; press [ENTER] to continue.
8. Press [ENTER] to save matched data; success: Adaption_success!
9. Press [ESCAPE] to return to function menu, then clear and reread fault codes:
05-Clear fault codes >> 02-Read fault codes

Additional remarks on the use of VAG401 for module adaptation are presented in Appendix G.

n.b.: On-line tool to calculate DTC 03276 adaptation check value: http://xor.pw/

1. I. Input: decimal (base 10): value from Channel 15, above (e.g., 22657).
2. II. Input: decimal (base 10): 51666
3. III. Ouput: decimal (base 10)
4. Select: [Calculate XOR]
5. Record result from Output field (e.g., 37203)

Fig. C.1 Input and Outfields of xor.pw XOR calculator tool

C.2 - DTC 03623 - Invalid Security/Release Code

DTC 03623 is due to the presence of an invalid FSC file stored in /HBpersistence/FSC. An SD
script must be applied to remove FSC files when the MMI system is patched to disable the normal
navigation database activation process based on FSC files.

The following SD script may be used to clear DTC 03623 by removing all FSC files from the MMI
system:

echo; echo "[ACTI] Copy FSC files to SD card"

31 Oct 2023
 41

cp -v /mnt/efs-persist/FSC/*.fsc ${SDPATH}/FSC/
cp -v /mnt/efs-extended/FSCBackup/*.fsc ${SDPATH}/FSCBackup/
echo; echo "[ACTI] Remove FSC files from flash"
mount -uw /mnt/efs-persist
rm -f -v /mnt/efs-persist/FSC/*.fsc
rm -f -v /mnt/efs-persist/FSC/cache/*.fsc

After the SD script is complete, restart the MMI system and rescan for remaining fault codes.
FSC files copied to the SD card should be saved off-line in case they are needed later.

C.3 - DTC 03677 - Missing FSC File

Removal of FSC files from the MMI system to clear DTC 03623 as described in the previous
section will likely trigger DTC 03677 after the next navigation database update. DTC 03677 can
be cleared from the GEM /dtc/control screen. Here, the internal qualified DTC number is 84
(Fig. C.2).

Fig. C.2 DTC 03677 - Missing FSC File

Applying value “84” in /dtc/control is expected to clear this DTC (Fig. C.3).

31 Oct 2023
 42

Fig. C.3 Clearing DTC “84” from the GEM.

31 Oct 2023
 43

APPENDIX D

D.1 Preparing Navigation Data Update Media from Internet Downloads

The navigation data update is distributed typically as a collection of multi-part RAR files that are
downloaded from Internet archives to a local computer or storage device. For example, NAR
6.20.1 might have this collection of eight (8) multi-part RAR files downloaded individually to a
single directory/folder:

8R0051884GJ.part01.rar
…
8R0051884GJ.part08.rar

D.2 Confirm Quality of Downloaded RAR Parts

After each file is downloaded individually, the MD5 hash/checksum should be computed and
checked against the known MD5 checksum, which can be found in the accompanying md5sum
file. On Win10 systems, the MD5 hash can be computed from a command window prompt with
certutil:

>certutil -hashfile 8R0051884GJ.part01.rar md5

MD5 hash of 8R0051884GJ.part01.rar:
c7385a315f033d711406b84f5fcb08e2 (computed)
CertUtil: -hashfile command completed successfully.
>type 8R0051884GJ.part01.rar.md5sum
c7385a315f033d711406b84f5fcb08e2 (known)

On Linux systems, md5sum(1) can be used to compute the MD5 checksum of the downloaded
file.

When the computed md5sum is the same as the known md5sum, the integrity of the downloaded
file is assured. When the md5sums are different, assume that the downloaded RAR file did not
download and save correctly and retry until the md5sums match correctly.

D.3 Extract the Multi-Part RAR Archive

On Windows systems, third-party applications 7-Zip (URL: https://7-zip.org/) and WinRAR

(URL: https://www.win-rar.com/) can be used to extract the multi-part RAR collection to a new
directory/folder on the current computer or to a blank 32 GB SDHC card directly. On Linux
systems, rar(1) or unrar(1) can be used from a command-line prompt to extract the
multi-part archive to the current working directory of a mounted SD card (e.g.
/media/user/8R0051884GJ). The Gnome Shell Archive Manager utility is also known to work

31 Oct 2023
 44

here. In all cases, selection of the first part of the multi-part archive is sufficient to extract the
entire archive. Avoid the use of the Linux Gnome Shell with the mounted SD card directly as it
can introduce hidden directories/folders that can cause updates to fail.

Ensure that the high speed 32 GB SDHC card is formatted as “FAT32” before files are extracted
or copied to the card. Windows 7 and 10/11 systems and Linux GParted are known to format
these cards successfully for MMI system updates.

Once extracted (and/or copied) to the SDHC card, the top level directory/folder will have four (4)
files and three (3) directories (using ls(1) on a Linux/Ubuntu desktop):

-rwxr-xr-x 1 user 29 Nov 12 2018 build1

-rwxr-xr-x 1 user 233 Nov 12 2018 config.nfm
-rwxr-xr-x 1 user 206 Nov 12 2018 DBInfo.txt
-rwxr-xr-x 1 user 1434 Nov 12 2018 metainfo2.txt
drwxr-xr-x 2 user 0 Nov 12 2018 MMI3G ## MMI 3G High release info
drwxr-xr-x 2 user 0 Nov 12 2018 MMI3GP ## MMI 3G+ release info
drwxr-xr-x 2 user 0 Nov 12 2018 pkgdb

Original NAR navigation update media that is suitable for both MMI3G and MMI3GP releases
will contain 32 directories/folders and 64 files. If the extracted archive contains fewer than
these, the archive was modified for a specific release (i.e., either MMI3G or MMI3GP), and
should be applied accordingly.

At this point, the SDHC card is prepared properly for the navigation data update using the Red
Engineering Menu (section 3.0).

D.4 Prepare Release for User Defined Software Update

As distributed, the GEM is required to enable user-defined software update mode, as described in
Appendix B.2, above. User-defined software update mode can be enabled in the release directly
as follows:

1. In the top level (root) directory of the release, rename metainfo2.txt to metainfo2.orig.
2. Copy metainfo2.orig to metainfo2.txt.
3. Edit metainfo2.txt as an MS-DOS plain-text file and replace text line:

MetafileChecksum=XXXXXX

with two new text lines:

31 Oct 2023
 45

EnableUserDefinedSWDLMode = "true"
skipMetaCRC = "true"

4. Save the edited metainfo2.txt file as an MS-DOS plain-text file.

D.5 Validating Release Media

Validating the integrity of database components files can be tested before and after installation
using file size and checksum information included with the release.

The SD media can be validated prior to installation by inspecting the “.conf” files of database
components and comparing the published MD5 checksum with the computed MD5 checksum for
that database component file. Note that the list of packages used for a release is defined in the
MMI3GP_NAR_Hi_R_6_X_Y.pkg file. A prototype Unix shell script to check the validity of an SD
card prepared from an Internet archive download is presented below:

#!/bin/sh
# shell functions:
getpktname(){
sed -n 's/^PacketName = "//p' ${MMIVER}/metainfo2.txt | sed 's/"^M//'
}
getpkgfilelist(){
sed -n 's/^filedef=//p' $PKGFILE | sed 's/^M//' | sed 's/_ECE//'
}
getconffsect(){
sed -n '/\[file\]/,$p' pkgdb/${pfname}/${pfname}.conf
}
# Main:
case "$#" in
"0") MMIVER="MMI3GP" ;;
"1") MMIVER="$1"
case "$MMIVER" in
"MMI3G" | "MMI3GP") true ;;
*) echo "Usage: $(basename $0) [MMI3G | MMI3GP]"
exit 1 ;;
esac ;;
*) echo "Usage: $(basename $0) [MMI3G | MMI3GP]"
exit 1 ;;
esac
RELNAME="$(getpktname)"
echo "Checking release: $RELNAME"
PKGFILE=pkgdb/${RELNAME}.pkg
for pfname in $(getpkgfilelist); do
if [ -d pkgdb/${pfname} ]; then
dbfname=$(getconffsect | sed -n 's/^name=//p' | sed 's/^M//')
dbfsize=$(getconffsect | sed -n 's/^size=//p' | sed 's/^M//')
dbfmd5sum=$(getconffsect | sed -n 's/^MD5=//p' | sed 's/ ^M//')
dbfname2=pkgdb/${pfname}/${dbfname}
dbfsize2=$(stat -c '%s' $dbfname2)
if [ X"$dbfsize" = X"$dbfsize2" ]; then

31 Oct 2023
 46

dbfmd5sum2=$(md5sum $dbfname2 | cut -f1 -d' ')

if [ X"$dbfmd5sum" = X"$dbfmd5sum2" ]; then
echo "OK: $dbfname2"
else
echo "Failed MD5: $dbfname2 : $dbfmd5sum : $dbfmd5sum2"
fi
else
echo "Failed size: $dbfname2 : $dbfsize : $dbfsize2"
fi
else
echo "Missing $MMIVER component: $pfname"
fi
done
exit 0

The ‘^M’ characters in the script are literal control-M characters, as found in MS-DOS text files.

After installation, the validity of the installed database components can be confirmed by
comparing the size and checksum values of component files against a list of known size and
checksum data computed from the database release. For NAR MMI3GP 6.24.0, these values are
presented below:

# 20230209 drger; MMI3GP NAR 6.24.0 CRC32 data

844097341 2048 LABEL_NAR/Label.DB
3269732890 2141927424 XAC_NAR/kN203NAx01_0.db
2131959214 837376000 XAC2_NAR/kN203NAx01_1.db
339521353 3307 TMC3GP_NAR/info.xml
1880494384 10115072 TMC3GP_NAR/kN203NAx01t01.db
4082470216 2147358156 GDB_NAR/AJ031_v36a.gdb
4196103061 782338350 GDB2_NAR/AJ031_v36a.gd2
1740790186 11290519 PIT_NAR/AJ031a.PIT
3284589262 2147379200 LIT3GP_NAR/AJ031Pa_L1.db
2193624690 2147377152 LIT3GP2_NAR/AJ031Pa_L2.db
656658641 2147389440 LIT3GP3_NAR/AJ031Pa_L3.db
681316134 1128742912 LIT3GP4_NAR/AJ031Pa_L4.db
2101749683 625029120 SDS3GP_NAR/SDS_Data.iso
2313134060 567130288 CTYS3TC_NAR/3PN203NA20343P1597a.4_4.ATLAS
3152140788 2097143696 TER_NAR/86_DTM_3G_NT_NAR.4_4.0.ATLAS
1545938481 2097149808 TER2_NAR/86_DTM_3G_NT_NAR.4_4.1.ATLAS
3419416047 1202786576 TER3_NAR/86_DTM_3G_NT_NAR.4_4.2.ATLAS
1205326302 2097141456 PSD_NAR/APN203NA20343P1595a.5_1.0.ATLAS
1946246159 684799712 PSD2_NAR/APN203NA20343P1595a.5_1.1.ATLAS

A prototype Unix shell script to prepare this list of file size and checksum data from an existing
release SD card is presented below:

#!/bin/sh
# shell functions:
getpktname(){
sed -n 's/^PacketName = "//p' ${MMIVER}/metainfo2.txt | sed 's/"^M//'
}

31 Oct 2023
 47

getpkgfilelist(){
sed -n 's/^filedef=//p' ../$PKGFILE | sed 's/^M//' | sed 's/_ECE//'
}
getconffsect(){
sed -n '/\[file\]/,$p' ${pfname}/${pfname}.conf
}
# Main:
case "$#" in
"0") MMIVER="MMI3GP" ;;
"1") MMIVER="$1"
case "$MMIVER" in
"MMI3G" | "MMI3GP") true ;;
*) echo "Usage: $(basename $0) [MMI3G | MMI3GP]"
exit 1 ;;
esac ;;
*) echo "Usage: $(basename $0) [MMI3G | MMI3GP]"
exit 1 ;;
esac
RELNAME="$(getpktname)"
echo "# cksum data for release: $RELNAME"
PKGFILE=pkgdb/${RELNAME}.pkg
cd pkgdb
for pfname in $(getpkgfilelist); do
if [ -d ${pfname} ]; then
dbfname=$(getconffsect | sed -n 's/^name=//p' | sed 's/^M//')
cksum ${pfname}/$dbfname
fi
done

As above, the ‘^M’ characters in the script are literal control-M characters, as found in MS-DOS
text files. Output of the script is expected to be captured in a plain-text file by re-directing
standard out for use in the QNX shell script presented below:

#!/bin/ksh
PKGDATA=${SDLIB}/${MUVER}-nar6240-cksums.txt
getfield(){
sed -n 's/^\([^[:blank:]]*\)[[:blank:]]*\([^[:blank:]]*\)[[:blank:]]*\
\([^[:blank:]]*\)/\'$1'/p'
}
if [ -f "$PKGDATA" ]; then
cd /mnt/nav/db/pkgdb
sed '/^#/d' $PKGDATA | while read xrec; do
dbcname="$(echo $xrec | getfield 3)"
dbcsize="$(echo $xrec | getfield 2)"
dbccsum="$(echo $xrec | getfield 1)"
tvar1="$(cksum $dbcname)"
dbcsize2="$(echo $tvar1 | getfield 2)"
if [ "$dbcsize2" = "$dbcsize" ]; then
dbccsum2="$(echo $tvar1 | getfield 1)"
if [ "$dbccsum2" = "$dbccsum" ]; then
echo "OK: $dbcname"
else
echo "FAILED cksum: $dbcname : $dbccsum : $dbccsum2"

31 Oct 2023
 48

fi
else
echo "FAILED size: $dbcname : $dbcsize : $dbcsize2"
fi
done
else
echo "ERROR: Cannot find cksum datafile $PKGDATA on SD card."
fi

Given that the time to compute the CRC32 checksum value with cksum is not insignificant for
very large (2 GB) database component files, we suggest this method be used only when a
navigation database fails to initialize properly after a successful nav database update. Also, the
run time of the script presented above will likely exceed the normal power time-out of the MMI
system; hence, be prepared to run this SD script with the ignition ON (engine OFF).

Note also that MMI3G (HNav) systems do not have the QNX executable binary file for the sed
command installed in directory /mnt/ifs-root/usr/bin. The script may be used on MMI3G
(HNav) systems with the HN+ QNX sed binary copied to the bin directory of the SD card.

31 Oct 2023
 49

APPENDIX E

E.1 8R0906961FE HN+_US_AU3G_K0942_6 Manifest Summary

Device Name Vendor Version Description

AH6 NAR Harman/Becker AS 300100 Cinterion AH6A-US 3G modem

AMPLCPKO LEAR 30 B&O Amplifier, DSP Application

p/n 8T1035223A

AMP_LC_P LEAR various B&O Amplifier, DSP Application

p/n 8T0035223AL, -AN

ARU9438 Harman/Becker AS various RU (radio unit)

ARU9469 Harman/Becker AS various RU (radio unit)

ARU9471 Harman/Becker AS various RU (radio unit) ***

AudiSupportedFscs HarmanBecker 7 Support FCSs

BO_Q7 ASK Industries Gmbh 80/110 B&O Premium Sound

BoseG3_Q7 Bose Automotive GmbH various Bose Amplifier 6000NXTV2

CombiStyles HarmanBecker 12 CombiStyles NAR (v12)

DU9466 Harman/Becker AS 98 DU7 High (display unit)

DUA130 Harman/Becker AS 104 DU7 High (display unit)

DVD Harman/Becker AS various FJ-TEN DV-05 FEAT2

DVD Harman/Becker AS 1319680 FTEN-DV04FT1

GEMMI HarmanBecker 8025 Google Earth MMI

IDC_APN ALPINE 140 IDC_APN ?

IDC_UDF Panasonic 0490 MP3 CD-Changer

IT Harman/Becker AS 2300 Internal Telephone, NAD module

KBD_FB8 Preh GmbH 12/30 KBD_FB8 ?

MU9498 HarmanBecker various Main Unit (9498, HW61)

MapStyles HarmanBecker 9120 MapStyles NAR (v06)

MuGPS Harman/Becker AS various GPS Chip Firmware

MuINIC Harman/Becker AS 17892131 INIC MainUnit MOST

31 Oct 2023
 50

MuIOC HarmanBecker various MainUnit IO controller

MuIOC+ HarmanBecker n/a MainUnit IO controller

MuTnrRef Audi 528 Spare Part Number List

TMCConfig HarmanBecker 16 TMCConfig

TVHybrid Hirschmann various Hybrid TV-DVB p/n 4F0919129D

Telit Harman/Becker AS 802540002 Telit 3G UMTS NAR modem

sss HarmanBecker 9411-NAR-18 Speech - Tts

0-20140612

MUConsistency HarmanBecker 1041 MU Consistency

31 Oct 2023
 51

APPENDIX F

F.1 User Defined Navigation Database Update Device Selection Screens

31 Oct 2023
 52

31 Oct 2023
 53

31 Oct 2023
 54

APPENDIX G

G.1 Reference - MMI 3GP NAR 6.24.0 /mnt/nav/db File Size List

============================================
Size (b) File name
--------------------------------------------
206 DBInfo.txt
5 DBInfo.txt.SWDL.compatibility.txt
15 DBInfo.txt.SWDL.version.txt
233 config.nfm
5 config.nfm.SWDL.compatibility.txt
15 config.nfm.SWDL.version.txt

5 pkgdb/CTYS3TC_NAR.SWDL.compatibility.txt
15 pkgdb/CTYS3TC_NAR.SWDL.version.txt
5 pkgdb/GDB2_NAR.SWDL.compatibility.txt
15 pkgdb/GDB2_NAR.SWDL.version.txt
5 pkgdb/GDB_NAR.SWDL.compatibility.txt
15 pkgdb/GDB_NAR.SWDL.version.txt
5 pkgdb/LABEL_NAR.SWDL.compatibility.txt
15 pkgdb/LABEL_NAR.SWDL.version.txt
5 pkgdb/LIT3GP2_NAR.SWDL.compatibility.txt
15 pkgdb/LIT3GP2_NAR.SWDL.version.txt
5 pkgdb/LIT3GP3_NAR.SWDL.compatibility.txt
15 pkgdb/LIT3GP3_NAR.SWDL.version.txt
5 pkgdb/LIT3GP4_NAR.SWDL.compatibility.txt
15 pkgdb/LIT3GP4_NAR.SWDL.version.txt
5 pkgdb/LIT3GP5_NAR.SWDL.compatibility.txt
15 pkgdb/LIT3GP5_NAR.SWDL.version.txt
5 pkgdb/LIT3GP_NAR.SWDL.compatibility.txt
15 pkgdb/LIT3GP_NAR.SWDL.version.txt
2063 pkgdb/MMI3GP_NAR_Hi_R_6_24_0.pkg
5 pkgdb/MMI3GP_NAR_Hi_R_6_24_0.pkg.SWDL.compatibility.txt
15 pkgdb/MMI3GP_NAR_Hi_R_6_24_0.pkg.SWDL.version.txt
128 pkgdb/MMI3GP_NAR_Hi_R_6_24_0.pkg.sig
5 pkgdb/MMI3GP_NAR_Hi_R_6_24_0.pkg.sig.SWDL.compatibility.txt
15 pkgdb/MMI3GP_NAR_Hi_R_6_24_0.pkg.sig.SWDL.version.txt
5 pkgdb/PIT_NAR.SWDL.compatibility.txt
15 pkgdb/PIT_NAR.SWDL.version.txt
5 pkgdb/PSD2_NAR.SWDL.compatibility.txt
15 pkgdb/PSD2_NAR.SWDL.version.txt
5 pkgdb/PSD_NAR.SWDL.compatibility.txt
15 pkgdb/PSD_NAR.SWDL.version.txt
5 pkgdb/SDS3GP_NAR.SWDL.compatibility.txt
15 pkgdb/SDS3GP_NAR.SWDL.version.txt
5 pkgdb/TER2_NAR.SWDL.compatibility.txt
15 pkgdb/TER2_NAR.SWDL.version.txt
5 pkgdb/TER3_NAR.SWDL.compatibility.txt
15 pkgdb/TER3_NAR.SWDL.version.txt
5 pkgdb/TER_NAR.SWDL.compatibility.txt
15 pkgdb/TER_NAR.SWDL.version.txt

31 Oct 2023
 55

5 pkgdb/TMC3GP_NAR.SWDL.compatibility.txt
15 pkgdb/TMC3GP_NAR.SWDL.version.txt
5 pkgdb/TMC_NAR.SWDL.compatibility.txt
15 pkgdb/TMC_NAR.SWDL.version.txt
5 pkgdb/XAC2_NAR.SWDL.compatibility.txt
15 pkgdb/XAC2_NAR.SWDL.version.txt
5 pkgdb/XAC_NAR.SWDL.compatibility.txt
15 pkgdb/XAC_NAR.SWDL.version.txt

567130288 pkgdb/CTYS3TC_NAR/3PN203NA20343P1597a.4_4.ATLAS
503 pkgdb/CTYS3TC_NAR/CTYS3TC_NAR.conf

2147358156 pkgdb/GDB_NAR/AJ031_v36a.gdb
481 pkgdb/GDB_NAR/GDB_NAR.conf

782338350 pkgdb/GDB2_NAR/AJ031_v36a.gd2
481 pkgdb/GDB2_NAR/GDB2_NAR.conf

473 pkgdb/LABEL_NAR/LABEL_NAR.conf
2048 pkgdb/LABEL_NAR/Label.DB

2147379200 pkgdb/LIT3GP_NAR/AJ031Pa_L1.db
486 pkgdb/LIT3GP_NAR/LIT3GP_NAR.conf

2147377152 pkgdb/LIT3GP2_NAR/AJ031Pa_L2.db
487 pkgdb/LIT3GP2_NAR/LIT3GP2_NAR.conf

2147389440 pkgdb/LIT3GP3_NAR/AJ031Pa_L3.db
487 pkgdb/LIT3GP3_NAR/LIT3GP3_NAR.conf

1128742912 pkgdb/LIT3GP4_NAR/AJ031Pa_L4.db
487 pkgdb/LIT3GP4_NAR/LIT3GP4_NAR.conf

1783846912 pkgdb/LIT3GP5_NAR/AJ031Pa_L5.db
486 pkgdb/LIT3GP5_NAR/LIT3GP5_NAR.conf

11290519 pkgdb/PIT_NAR/AJ031a.PIT
475 pkgdb/PIT_NAR/PIT_NAR.conf

2097141456 pkgdb/PSD_NAR/APN203NA20343P1595a.5_1.0.ATLAS
498 pkgdb/PSD_NAR/PSD_NAR.conf

684799712 pkgdb/PSD2_NAR/APN203NA20343P1595a.5_1.1.ATLAS
498 pkgdb/PSD2_NAR/PSD2_NAR.conf

481 pkgdb/SDS3GP_NAR/SDS3GP_NAR.conf
625029120 pkgdb/SDS3GP_NAR/SDS_Data.iso

2097143696 pkgdb/TER_NAR/86_DTM_3G_NT_NAR.4_4.0.ATLAS
494 pkgdb/TER_NAR/TER_NAR.conf

2097149808 pkgdb/TER2_NAR/86_DTM_3G_NT_NAR.4_4.1.ATLAS
495 pkgdb/TER2_NAR/TER2_NAR.conf

31 Oct 2023
 56

1202786576 pkgdb/TER3_NAR/86_DTM_3G_NT_NAR.4_4.2.ATLAS
495 pkgdb/TER3_NAR/TER3_NAR.conf

487 pkgdb/TMC3GP_NAR/TMC3GP_NAR.conf
3307 pkgdb/TMC3GP_NAR/info.xml
10115072 pkgdb/TMC3GP_NAR/kN203NAx01t01.db

479 pkgdb/TMC_NAR/TMC_NAR.conf
6526976 pkgdb/TMC_NAR/kN123NAx08T01.db

482 pkgdb/XAC_NAR/XAC_NAR.conf
2141927424 pkgdb/XAC_NAR/kN203NAx01_0.db

482 pkgdb/XAC2_NAR/XAC2_NAR.conf
837376000 pkgdb/XAC2_NAR/kN203NAx01_1.db

G.2 Reference - /efs-persist/navi/db/acios_db.ini File

# This file has been generated by the LVM (epoche 46)

ANY: /mnt/nav/db/pkgdb/PSD_NAR/APN203NA20343P1595a.5_1.0.ATLAS
ANY: /mnt/nav/db/pkgdb/TER3_NAR/86_DTM_3G_NT_NAR.4_4.2.ATLAS
ANY: /mnt/nav/db/pkgdb/GDB2_NAR/AJ031_v36a.gd2
ANY: /mnt/nav/db/pkgdb/PIT_NAR/AJ031a.PIT
ANY: /mnt/nav/db/pkgdb/TER_NAR/86_DTM_3G_NT_NAR.4_4.0.ATLAS
ANY: /mnt/nav/db/pkgdb/GDB_NAR/AJ031_v36a.gdb
ANY: /mnt/nav/db/pkgdb/LIT3GP_NAR/AJ031Pa_L1.db
ANY: /mnt/nav/db/pkgdb/XAC2_NAR/kN203NAx01_1.db
ANY: /mnt/nav/db/pkgdb/TMC3GP_NAR/kN203NAx01t01.db
ANY: /mnt/nav/db/pkgdb/PSD2_NAR/APN203NA20343P1595a.5_1.1.ATLAS
ANY: /mnt/nav/db/pkgdb/LIT3GP2_NAR/AJ031Pa_L2.db
#SDS: /mnt/nav/db/pkgdb/SDS3GP_NAR/SDS_Data.iso
#MNT(SDS): /mnt/nav/db/pkgdb/SDS3GP_NAR/SDS_Data.iso
ANY: /mnt/nav/db/pkgdb/CTYS3TC_NAR/3PN203NA20343P1597a.4_4.ATLAS
ANY: /mnt/nav/db/pkgdb/LIT3GP4_NAR/AJ031Pa_L4.db
ANY: /mnt/nav/db/pkgdb/LIT3GP3_NAR/AJ031Pa_L3.db
ANY: /mnt/nav/db/pkgdb/XAC_NAR/kN203NAx01_0.db
ANY: /mnt/nav/db/pkgdb/LABEL_NAR/Label.DB
ANY: /mnt/nav/db/pkgdb/TER2_NAR/86_DTM_3G_NT_NAR.4_4.1.ATLAS

31 Oct 2023
 57

APPENDIX H

H.1 Notes on VAG Module Adaptation Using Xtool VAG401 Diagnostic Tool

With the VAG401 attached to the OBDII port and the ignition ON (engine OFF), open Module 5F:
Diagnosis systems >> Electrical system 2 >> 5f - Message options

After the module information is displayed, press [ENTER] to return to the function menu:

5f - Message options
===========================
>01-Control Unit Info
02-Read Fault Codes
05-Clear Fault Codes
08-Data block Measurement
03-Test actuator
04-Basic settings
10-Adaptation
07-Code Module
11-Code Module II
16-Access permission
15-Readiness

Use the arrow UP/DOWN keys to move the cursor (>) to “10-Adaptation” and press [ENTER] to
open the adaptation channel number input screen:

10-Adaptation
===========================

Input Channel Number (0~255):

----------------------------
000

Example 1 -- Enable Green Engineering Menu using Adaptation Channel 6:

Use the UP/DOWN arrow keys to change the number at the current cursor position [0-9] and the
LEFT/RIGHT arrow keys to move the cursor to another digit position:

10-Adaptation
===========================

Input Channel Number (0~255):

----------------------------

31 Oct 2023
 58

006

With the correct channel number displayed (e.g., 006), press [ENTER] key to read the adaptation
channel:

Channel Number:006
===========================
>Matched data 00000
00000.00

When adaptation channel 6 value is ‘0’, the Green Engineering Menu is disabled. Press
[ENTER] key to proceed to adaptation value input:

10-Adaptation
===========================

Input matched data:

----------------------------
00000

Use the UP/DOWN arrow keys to change the number at the current cursor position [0-9] and the
LEFT/RIGHT arrow keys to move the cursor to another digit position to set the right-most digit
to ‘1’:

10-Adaptation
===========================

Input matched data:

----------------------------
00001

With the correct adaptation value entered (1), press [ENTER] key to review the adaptation
channel information:

Channel Number:006
===========================
>Matched data 00001
00000.00

Press the [ENTER] key to proceed:

31 Oct 2023
 59

10-Adaptation
===========================

Save matched data?

Press the [ENTER] key to save the new adaptation value to the control module. VAG401 will
report success with the message:

10-Adaptation
===========================

Adaption_success!

Press the [ESCAPE] key to return to the module function menu. The GEM can be accessed
directly without restarting the MMI.

Example 2 -- Clearing DTC 03267 using Adaptation Channel 15:

Use the UP/DOWN arrow keys to change the number at the current cursor position [0-9] and the
LEFT/RIGHT arrow keys to move the cursor to another digit position:

10-Adaptation
===========================

Input Channel Number (0~255):

----------------------------
015

With the correct channel number displayed (e.g., 015), press [ENTER] key to read the adaptation
channel:

Channel Number:015
===========================
>Matched data 00000
22657.00

For clearing DTC 03267, record the highlighted value below the first “Matched data” line (e.g.,
22657) and use this value to determine the result of: <channel 15 value> XOR 51666. Press
[ENTER] key to proceed to adaptation value input:

31 Oct 2023
 60

10-Adaptation
===========================

Input matched data:

----------------------------
00000

Use the UP/DOWN arrow keys to change the number at the current cursor position [0-9] and the
LEFT/RIGHT arrow keys to move the cursor to another digit position:

10-Adaptation
===========================

Input matched data:

----------------------------
37203

With the correct adaptation value entered (e.g., 37203), press [ENTER] key to review the
adaptation channel information:

Channel Number:015
===========================
>Matched data 37203
22657.00

Press the [ENTER] key to proceed:

10-Adaptation
===========================

Save matched data?

Press the [ENTER] key to save the new adaptation value to the module. VAG401 will report
success with the message:

10-Adaptation
===========================

Adaption_success!

Press the [ESCAPE] key to return to the module function menu to clear and re-read fault codes.

31 Oct 2023
 61

APPENDIX J

J.1 Updated Navigation Database Unblocker Patch Script

#!/bin/ksh
# Exit the script if patch installed previously
if test -n "$(grep 'acios_db.ini' /usr/bin/manage_cd.sh)"
then
echo; echo "[INFO] Found MMI3G NavUnblocker patch installed. Done."
else
mes=/mnt/efs-system
mount -uw $mes
# NavUnblocker patch not installed; look for old mme-becker patch to remove
if test -a ${mes}/sbin/mme-becker.sh
then
if test -n "$(grep 'acios_db.ini' ${mes}/sbin/mme-becker.sh)"
then
if test -a ${mes}/etc/mmelauncher.cfg.pre-navdb.bak
then
echo; echo "[ACTI] Removing old mme-becker activator patch."
mv -v ${mes}/etc/mmelauncher.cfg ${mes}/etc/mmelauncher.cfg-TMP
mv -v ${mes}/etc/mmelauncher.cfg.pre-navdb.bak ${mes}/etc/mmelauncer.cfg
rm -v ${mes}/etc/mmelauncher.cfg-TMP
rm -v ${mes}/sbin/mme-becker.sh
fi
fi
fi
# Patch /usr/bin/manage_cd.sh
echo; echo "[ACTI] Appending patch to /usr/bin/manage_cd.sh ..."
mv -v ${mes}/usr/bin/manage_cd.sh ${mes}/usr/bin/manage_cd.sh-ORIG
cp -v ${mes}/usr/bin/manage_cd.sh-ORIG ${mes}/usr/bin/manage_cd.sh
echo '/usr/apps/bench/TimeLogger "Starting MMI3G NavUnblocker patch"' >> \
${mes}/usr/bin/manage_cd.sh
echo '(waitfor /mnt/lvm/acios_db.ini 180 && sleep 10 && slay vdev-logvolmgr) &' >> \
${mes}/usr/bin/manage_cd.sh
chmod 0777 ${mes}/usr/bin/manage_cd.sh
touch -r ${mes}/usr/bin/manage_cd.sh-ORIG ${mes}/usr/bin/manage_cd.sh

# Copy FSC and acios_db.ini files to SD card var dir:

echo; echo "[ACTI] Copy FSC and acios_db.ini files to $SDVAR"
cp -v /mnt/efs-persist/FSC/*.fsc ${SDVAR}/
cp -v /mnt/efs-persist/navi/db/acios_db.ini ${SDVAR}/
fi

Download URL: https://github.com/DrGER2/MMI3G-Navdb-Unblocker

J.2 FSC Activation File Reference

The specification for the navigation database activation FSC file is given in the navigation
database release PKG file as an option to the “userflags” parameter. For example, The PKG file
contained in 8R0051884EN (NAR 6.16.2) has User Flags parameter:

31 Oct 2023
 62

userflags=fsc@40014;region@2;model@1

In this case, the MMI3GP system expects to find FSC file /mnt/efs-persist/FSC/00040014.fsc
with correct encoding from the SVM - Activation process using activation data obtained from the
activation document associated with the 2017/2018 nav database release.

Table J.1 Harman-Becker FSC File to Release Mapping

FSC Spec Release VAG Part Numbers 8R0060884

40000 2010 J/ECE

40001 2010/2011 AC/NAR

40002 2011 AL/NAR; R/ECE+1

40003 2011/2012 AC/NAR; AD/NAR

40004 2012 AM/NAR

40005 2013 AR/ECE; AS/ROW

40006 2013/2014 BD/NAR^+2

40007 2014 BK/ECE; BL/NAR^; BN/APA

40008 2014/2015 BT/ECE; CA/NAR; CB/ROW

40009 2015 CH/ECE; CJ/NAR+3

40010 2015/2016 CR/ECE+4; CS/NAR; CT/ROW

40011 2016 DF/ECE

40012 2016/2017 DQ/NAR

40013 2017 ED/ECE

40014 2017/2018 EM/ECE; EN/NAR^

40015 2018 FC/ECE; FD/NAR

40016 2018/2019 FK/ECE; FL/NAR

40017 2019 GA/ECE+5; GB/NAR

40018 2019/2020 GJ/NAR^

40019 2020 GS/ECE

40020 2020/2021 HF/ECE+6; HG/NAR^; HJ/ROW

31 Oct 2023
 63

40021 2021 HQ/ECE; HS/APA

40022 2021/2022 JD/ECE^; JE/NAR^

40023 2022 JN/ECE

40024 2022/2023 KB/ECE^; KC/NAR; KE/ROW

40025 2023 KL/ECE^

Notes:
1. 2010 Q5 UK prod.
2. 2014 A4 US prod.
3. 2015 Q7 US prod.
4. 2015 A8 UK prod.
5. Update (UK).
6. Update (DK).

31 Oct 2023
 64

THIS PAGE LEFT BLANK INTENTIONALLY.

31 Oct 2023
 65

INSTALLATION CHECKLIST: NAR Navigation Database Update 3GP/3G+

[ ] NAR MMI 3GP/3G+ software updated to K0942_6.

[ ] Nav update SD prepared on 32 GB SDHC formatted as FAT32.
[ ] (optional) Navdb unblock patch script SD prepared on SD formatted as FAT32.
[ ] Battery charged, battery maintainer connected.
[ ] All media removed from MMI; MMI ON; all functions loaded; GPS time set.
[ ] Enable Green Engineering Menu with VAG diag tool (VCDS, VAG401, Carista, etc.).
[ ] Enable User defined software update in GEM: [CAR]+[MENU]
[ ] Start REM: [CAR]+[BACK]
[ ] Blank SD card in MMI SD Slot 1; Nav update SD card in MMI SD Slot 2.
[ ] REM: [Update] >> SD2 >> NAR 6.x.y (MMI3GP) >> User defined
[ ] Scroll and select: AUDI_MMI3G_NAR
[ ] Select Application for applicable sub-entries & return to top device list.
[ ] Select if status is ?: MapStyles >> Application >> [BACK]
[ ] Scroll and select: Start update >> Start (record start time):
[ ] Updated: Database - LABEL
[ ] Updated: Database - [ ] XAC; [ ] XAC2
[ ] Updated: Database - TMC3GP
[ ] Updated: Database - [ ] GDB; [ ] GDB2
[ ] Updated: Database - PIT
[ ] Updated: Database - [ ] LIT3GP; [ ] LIT3GP2; [ ] LIT3GP3; [ ] LIT3GP4
[ ] Updated: Database - SDS3GP
[ ] Updated: Database - CTYS3TC
[ ] Updated: Database - [ ] TER; [ ] TER2; [ ] TER3
[ ] Updated: Database - [ ] PSD; [ ] PSD2
[ ] Updated: Database - config.nfm
[ ] Updated: Database - DBInfo.txt
[ ] Updated: Database - PKG
[ ] Updated: Database - SIG
[ ] (optional) Updated: MapStyles (if selected above for install)
[ ] Device Summary: confirm all OK; if any NOK, check SD card & repeat update.
[ ] Scroll and select: Continue >> Abort documentation
[ ] Confirm all MMI functions start properly after last reboot.
[ ] Navigation data blocked/unavailable: Navdb unblock patch script applied.
[ ] DTC 03276 cleared with VAG diag tool; [ ] DTC 03623 cleared with GEM/script.
[ ] Update complete !

31 Oct 2023