Update maps manually (MN1 & MN2)

Officially, maps on Media Nav should be managed using the Media Nav Toolbox. Yet, there are many cases – like already having acquired the maps or simply wanting to use free crowd-sourced maps – where an alternative would be more viable. This can be achieved, although it needs a little more work.

The navigation software used in Media Nav is iGO Primo, so your files must be compatible.

Note: On first and second generation Media Nav units (MN1 & MN2), the space allocated for navigation is about 2.8 GB, out of which only about 2.5 GB are available for maps and additional files. When adding new maps, file sizes should be taken into account.

Guide

Note: This guide applies only to first and second generation Media Nav units (MN1 & MN2), firmware versions 4.0.0 through 9.1.3. For third generation Media Nav units (MN3), see Update maps manually (MN3).

Prerequisites:
– a tablet, laptop or desktop equipped with an USB port, containing the new maps
– USB flash drive, FAT32 formatted, min. 4 GB & max. 32 GB capacity
SyncTool Patch, if required

Optional step 1. Start the car engine, wait for the Media Nav to boot and access Windows CE from TEST MODE – see How to access Windows CE. Engine should be left running while working on the Media Nav, otherwise the Media Nav will shutdown automatically after about 20 minutes, interrupting the operations.

Optional step 2. Plug the flash drive in the USB port, go to My Device, and copy the contents of Storage Card 4 on the flash drive. This way, you will have a backup in case something goes wrong.

Note: If the flash drive doesn’t show up in My Device, go to Start > Programs and select USB PHY On. At this point, the flash drive should show up.

Optional step 3. After the files are copied, unplug the flash drive, shutdown the Media Nav from the Start menu and turn off the engine. Ideally, you can copy the backup from the flash drive on your device.

Step 1. Download and install SyncTool Patch – not required if the files you have are previously acquired iGO maps; required for other sources.

Step 2. Copy the maps and additional files on the flash drive, with respect to the following files and folders structure – this is how files are organized in the Media Nav storage:

/NNG
|
|---/content
|   |
|   |---/building
|   |   |---*.3dl - 3D buildings with textures
|   |   |---*.3dc - 3D buildings without textures
|   |
|   |---/cars
|   |   |---*.zip - skins for replacing the car's arrow
|   |
|   |---/dem
|   |   |---*.dem - 3D terrain
|   |
|   |---/global_cfg
|   |   |---global_cfg.zip - general info about countries
|   |
|   |---/histspeed
|   |   |---*.hsp - historical data about traffic patterns
|   |
|   |---/lang
|   |   |---*.dem - 3D terrain
|   |
|   |---/lang
|   |   |---*.zip - languages
|   |
|   |---/map
|   |   |---*.fbl - country map
|   |   |---*.fda - traffic signs
|   |   |---*.fds - dangerous road segments
|   |   |---*.fjv - junction view
|   |   |---*.fjw - junction view, vector format
|   |   |---*.fpa - point addressing (additional info for addresses); Primo only
|   |   |---*.fsp - traffic profiles
|   |   |---*.ftr - truck-oriented info, e.g.: closed roads for trucks
|   |
|   |---/phoneme
|   |   |---*.ph - correct pronunciations for street names
|   |
|   |---/poi
|   |   |---*.poi - points of interest
|   |
|   |---/raster
|   |   |---*.? - satellite imagery
|   |
|   |---/scheme
|   |   |---*.? - different colors for iGO
|   |
|   |---/skin
|   |   |---*.? - skins for iGO
|   |
|   |---/speedcam
|   |   |---*.spc/txt - fixed speedcams locations
|   |
|   |---/tmc
|   |   |---*.tmc - files for using Traffic Message Channel, where available
|   |
|   |---/userdata
|   |   |
|   |   |---/poi
|   |       |
|   |       |---/usericon
|   |       |   |
|   |       |   |---*.bmp - icons for user defined points of interest
|   |       |   
|   |       |---*.kml/kix/kst - user defined points of interest
|   |
|   |---/voice
|       |---*.zip - voices
|
|---/license
|   |---*.lyc - files used to update maps officially; may cause instability, unsupported map errors, other errors
|
|---data.zip - GUI elements, usually for certain resolutions
|---branding.zip - misc icons
|---sys.txt - config file

Note: The bare minimum in order for a country’s map to be usable is the *.fbl file. Depending on your map provider, the files may already be organized as above.

Step 3. Start the car engine and leave it running until all operations are complete. Access Windows CE from the test menu and plug the flash drive in the USB port.

Step 4. Go to My Device > Storage Card 4 > NNG > content and remove files for the countries whose maps you are going to replace, if any. Copy the new maps and additional files in the same location. If *.lyc files were provided, they will go to My Device > Storage Card 4 > NNG > license.

Step 5. After the files are copied, unplug the flash drive, shutdown the Media Nav from the Start menu and turn off the engine. Wait for about 30 seconds and turn on the Media Nav. At this point, if you go to Navigation, the new maps should be shown.

Troubleshooting

The Agree button is unavailable upon entering the navigation.
No maps are showing up in the navigation after the update.
Check to see if the files copied are placed in the correct folders. The absence or misplacement of the *.fbl files is commonly the cause. At the same time, there is also the chance of the files not being in a compatible format; your files must be compatible with the iGO navigation software.

The navigation is laggy/has a low FPS rate.
Usually, this is caused by 3D data files, *.3dl, *.3dc and *.dem, putting an additional strain on your hardware. This may happen in city centers and is more commonly a problem on first generation Media Nav units, due to having less RAM. Removing one or more of these files may increase the FPS rate considerably. For tweaking RAM allocation, see How to fix lag or low memory problems (MN1 & MN2).

If none of the above solutions worked or you encountered other problems, the simplest and safest fix would be to restore Storage Card 4 contents from the backup made before updating the maps, thus reverting the navigation to its previous state. This can be accomplished by following the same procedure as for copying the new maps.