South African Map 2020 Q4 Paid feature

Hi CyanLabs. Hope you well.

I’m in South Africa and importer a USA 2018 Sync 3 - 3.0 17276 apim. I installed the apim and LCD myself in my Ford Everest 2016 Model that came with Sync 2. Everything is working perfect with android auto for maps. I found a Vin number of a 2017 model the same like my vehicle but came factory with sync3 without maps and uploaded that vin’s as build to the sync 3 apim

I used the sync 3 updated to create an interrogate tool to check how much memory my sync apim has. I believe it is the 32GB or even more if I calculate all the partitions space together. When I installed the apim, it did display USA maps but after I loaded South African asbuild it did not have maps afterwards. Obviously because its a USA apim. I can post the file the interrogate tool created from my apim for you to make sure I can update it with South African Maps 2020-Q4 or 2019Q4.

I want to use your sync 3 updater and I downloaded the ROW 2019 Q4 maps. Will this update work as is.

I know that you dont support region change but I believe a SA local vin as build same specs as my vehicle model just newer that came with navigation as build should change all required asbuild data that needs to be changed.

Secondly, I see there is a 2020 Q4 South African map update, but it is a paid feature. I’m interested to purchase this update to update my apim with. I would prefer this update

Will this paid feature update work with my apim storage space? I can send you the interrogated file of my sync3

Below is the botom of the sync 3 apim file
<d2p1:PartitionHealth type="/fs/usb0/" total=“29G” available=“29G”/>
<d2p1:PartitionHealth type="/fs/tmpfs/" total=“128M” available=“127M”/>
<d2p1:PartitionHealth type="/fs/sd/MAP/" total=“1.5G” available=“41M”/>
<d2p1:PartitionHealth type="/fs/sd/MAP/" total=“9.1G” available=“57M”/>
<d2p1:PartitionHealth type="/fs/Nuance/" total=“4.7G” available=“243M”/>
<d2p1:PartitionHealth type="/fs/Nuance/" total=“475M” available=“13M”/>
<d2p1:PartitionHealth type="/fs/Nuance/grace" total=“1.0G” available=“5.1M”/>
<d2p1:PartitionHealth type="/fs/rwdata/" total=“1024M” available=“604M”/>
<d2p1:PartitionHealth type="/fs/mp/" total=“1024M” available=“173M”/>
<d2p1:PartitionHealth type="/fs/images/" total=“26G” available=“8.3G”/>

Hope yo hear from you soon.


SYNC Region: North America & Canada

Navigation Variant: Yes

Install Type: OEM Replacement

Old SYNC Version: 3.0.17276

New SYNC Version: 3.0.17276

Do you have a error message, if so what is it?

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version:

Syn3 Updater Documentation Read: Yes

Syn3 Updater Log File

<?xml version="1.0" encoding="UTF-8"?>
<p:OTAModuleSnapShot xmlns:d2p1="urn:ford/Vehicle/Module/Information/v3.0" xmlns:xsi="" xmlns:p="urn:ford/com/productdesign/ipp/ModuleSnapshot/v2.0" version="2022-05-17" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
  <p:Node isFlashed="false" specificationCategory="GGDS">
    <d2p1:ECUAcronym name="APIM">
        <d2p1:Gateway gatewayType="NONE">
          <d2p1:DID didFormat="ASCII" didType="Embedded Consumer Operating System Part Number" didValue="8033" responseLength="24">
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8060" responseLength="384">
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8061" responseLength="384">
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 1" didValue="D704" responseLength="4">
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
          <d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
          <d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
          <d2p1:DID didType="Direct Configuraation DID DE02" didValue="DE02">
          <d2p1:DID didType="Direct Configuraation DID DE03" didValue="DE03">
          <d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
          <d2p1:DID didType="Direct Configuraation DID DE05" didValue="DE05">
          <d2p1:DID didType="Direct Configuraation DID DE06" didValue="DE06">
          <d2p1:DID didFormat="ASCII" didType="On-line Diagnostic Database Reference Number" didValue="F110" responseLength="24">
          <d2p1:DID didFormat="ASCII" didType="ECU Core Assembly Number" didValue="F111" responseLength="24">
          <d2p1:DID didFormat="ASCII" didType="ECU Delivery Assembly Number" didValue="F113" responseLength="24">
          <d2p1:DID didFormat="ASCII" didType="ECU Calibration Data #1 Number" didValue="F124" responseLength="24">
          <d2p1:DID didFormat="ASCII" didType="Private Sub Node #1 Serial Number" didValue="F141" responseLength="16">
          <d2p1:DID didFormat="State Encoded" didType="Software Download Specification Version" didValue="F162" responseLength="1">
          <d2p1:DID didFormat="State Encoded" didType="Diagnostic Specification Version" didValue="F163" responseLength="1">
          <d2p1:DID didFormat="ASCII" didType="Vehicle Manufacturer ECU Software Number" didValue="F188" responseLength="24">
          <d2p1:DID didFormat="ASCII" didType="ECU Serial Number" didValue="F18C" responseLength="16">
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 1" didValue="F1D0" responseLength="6">
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
    <d2p1:ODLNetwork d2p1:NetworkDataRate="500" d2p1:NetworkName="HS-CAN" d2p1:NetworkProtocol="CAN" d2p1:DLCName="SAE J1962" d2p1:Pins="6,14"/>
    <d2p1:AdditionalAttributes logGeneratedDateTime="2022-05-17T18:06:16+00:00" RAM="1479335936" vmcuVersion="Vector_VMCU_02.02.20">
      <d2p1:PartitionHealth type="/fs/usb0/" total="29G" available="29G"/>
      <d2p1:PartitionHealth type="/fs/tmpfs/" total="128M" available="127M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.5G" available="41M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="9.1G" available="57M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="4.7G" available="243M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="475M" available="13M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/grace" total="1.0G" available="5.1M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/" total="1024M" available="604M"/>
      <d2p1:PartitionHealth type="/fs/mp/" total="1024M" available="173M"/>
      <d2p1:PartitionHealth type="/fs/images/" total="26G" available="8.3G"/>


Yes you should be able to get ZA maps on here without issue, you will need to change the navigation mode in the as-built which you have mentioned already.

You have 32GB which is standard NA Nav size.

This would be the region, Navigation mode (Telenav/NNG)

If you would like to purchase the paid 2020 package please visit

Thank You for your swift response. I will go with the 2020Q4 South African Maps update paid feature.

After I install this update. Will I be able to update the maps using Ford NaviExtra Updater for future updates or do I need to use your tool again.

Will I also get tracks for Africa with this update as the local vehicles get.

Hope to hear from you soon.

Have a blessed life.


If you have a valid ZA 3.4+ VIN yes.

I have no idea what that is nor any idea if you will get that or not, i would assume yes but not sure.

Good day CyanLabs.

I purchased the paid feature map yesterday and received my order number yesterday. Normally how long does it take to receive license key?

Also I read that someone bricked his APIM with CyanLab updater and only after he removed his APim he saw that it was a replacement APIM dated 2020. He was the second owner of car and was not aware that apim was replaced.

I have a 2018 Ford Focus Apim USA. Cant rember model nr but I got this (JR3T-14G381-AJ) from the interrogator utility. Also I uploaded the xml file in previous post. Does the xml contain model or part number of apim.

Will the update work on my APIM? I dont want to brick it . I believe it will work because its an 2018, 32GB



As stated on the listing, it can take a few days, i have been working on some stuff on the website so haven’t been able to get the key till just now.

Email has been sent with your key.

I can’t guarantee you won’t brick, but JS7T-14G371-KED is a old unit so it should be fine
see this thread for the same APIM model

Thank you for your swift response. I received the key.

Below id my log for update. Is the following setting Ok for my 2018 APIM
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

Branch: Alpha
Operating System: Microsoft Windows 10 Home Single Language (2009)

Version: 3.0.17276
Region: ROW
Navigation: True
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

Mode: Drive
Model: SanDisk Cruzer Blade USB Device
Size: 29.2GB
FileSystem: exFAT
Partition Type: MBR


; CyanLabs Syn3Updater Alpha - reformat  Mode - Sync 3.4.21265 ROW

Item1 = REFORMAT TOOL  - 1u5t-14g386-cb.tar.gz
Open1 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

1u5t-14g386-cb.tar.gz (8.5MB)
4U5T-14G423-FC_1615431949000.TAR.GZ (923.8MB)
1U5T-14G658-AG_1626915602000.TAR.GZ (56.8MB)
5U5T-14G391-FR_1626960707000.TAR.GZ (1.4GB)
5U5T-14G381-EU_1634769242000.TAR.GZ (847.2MB)
4U5T-14G421-FFJ.tar.gz (1.1GB)
4U5T-14G424-FFJ.tar.gz (1.7KB)

[18/05/2022 22:54:16] Selected Region: ROW - Release: Sync 3.4.21265 - Map Version: 2020 Q4 - ROW (South Africa) 
[18/05/2022 22:54:16] Install Mode: Auto-Detect (reformat) Forced: False 
[18/05/2022 22:54:16] MY20 Protection: Auto-Detect 
[18/05/2022 22:54:16] Formatting USB drive
[18/05/2022 22:54:16] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[18/05/2022 22:54:24] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[18/05/2022 22:54:24] Downloading: 1u5t-14g386-cb.tar.gz
[18/05/2022 22:54:30] Validating: 1u5t-14g386-cb.tar.gz 
[18/05/2022 22:54:30] Downloaded: 1u5t-14g386-cb.tar.gz 
[18/05/2022 22:54:30] Checking Existing File: 4U5T-14G423-FC_1615431949000.TAR.GZ 
[18/05/2022 22:54:30] Downloading: 4U5T-14G423-FC_1615431949000.TAR.GZ
[18/05/2022 22:58:34] Validating: 4U5T-14G423-FC_1615431949000.TAR.GZ 
[18/05/2022 22:58:39] Downloaded: 4U5T-14G423-FC_1615431949000.TAR.GZ 
[18/05/2022 22:58:39] Checking Existing File: 1U5T-14G658-AG_1626915602000.TAR.GZ 
[18/05/2022 22:58:39] Downloading: 1U5T-14G658-AG_1626915602000.TAR.GZ
[18/05/2022 22:58:53] Validating: 1U5T-14G658-AG_1626915602000.TAR.GZ 
[18/05/2022 22:58:53] Downloaded: 1U5T-14G658-AG_1626915602000.TAR.GZ 
[18/05/2022 22:58:53] Checking Existing File: 5U5T-14G391-FR_1626960707000.TAR.GZ 
[18/05/2022 22:58:53] Downloading: 5U5T-14G391-FR_1626960707000.TAR.GZ
[18/05/2022 23:04:07] Validating: 5U5T-14G391-FR_1626960707000.TAR.GZ 
[18/05/2022 23:04:14] Downloaded: 5U5T-14G391-FR_1626960707000.TAR.GZ 
[18/05/2022 23:04:14] Checking Existing File: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[18/05/2022 23:04:14] Downloading: 5U5T-14G381-EU_1634769242000.TAR.GZ
[18/05/2022 23:07:18] Validating: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[18/05/2022 23:07:21] Downloaded: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[18/05/2022 23:07:21] Checking Existing File: Ford_South_Africa20Q4.tgz 
[18/05/2022 23:07:21] Downloading: Ford_South_Africa20Q4.tgz
[18/05/2022 23:11:33] Validating: Ford_South_Africa20Q4.tgz 
[18/05/2022 23:11:37] Downloaded: Ford_South_Africa20Q4.tgz 
[18/05/2022 23:11:55] Extracting: Ford_South_Africa20Q4.tgz (This may take some time!) 
[18/05/2022 23:11:55] Added MultiPackage files to Queue
[18/05/2022 23:11:55] Preparing USB drive
[18/05/2022 23:11:55] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[18/05/2022 23:11:55] Copying: 1u5t-14g386-cb.tar.gz 
[18/05/2022 23:11:56] Validating: 1u5t-14g386-cb.tar.gz 
[18/05/2022 23:11:56] Copied: 1u5t-14g386-cb.tar.gz 
[18/05/2022 23:11:56] Checking Existing File: 4U5T-14G423-FC_1615431949000.TAR.GZ 
[18/05/2022 23:11:56] Copying: 4U5T-14G423-FC_1615431949000.TAR.GZ 
[18/05/2022 23:15:44] Validating: 4U5T-14G423-FC_1615431949000.TAR.GZ 
[18/05/2022 23:16:21] Copied: 4U5T-14G423-FC_1615431949000.TAR.GZ 
[18/05/2022 23:16:21] Checking Existing File: 1U5T-14G658-AG_1626915602000.TAR.GZ 
[18/05/2022 23:16:21] Copying: 1U5T-14G658-AG_1626915602000.TAR.GZ 
[18/05/2022 23:16:35] Validating: 1U5T-14G658-AG_1626915602000.TAR.GZ 
[18/05/2022 23:16:37] Copied: 1U5T-14G658-AG_1626915602000.TAR.GZ 
[18/05/2022 23:16:37] Checking Existing File: 5U5T-14G391-FR_1626960707000.TAR.GZ 
[18/05/2022 23:16:37] Copying: 5U5T-14G391-FR_1626960707000.TAR.GZ 
[18/05/2022 23:22:24] Validating: 5U5T-14G391-FR_1626960707000.TAR.GZ 
[18/05/2022 23:23:21] Copied: 5U5T-14G391-FR_1626960707000.TAR.GZ 
[18/05/2022 23:23:21] Checking Existing File: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[18/05/2022 23:23:21] Copying: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[18/05/2022 23:26:50] Validating: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[18/05/2022 23:27:24] Copied: 5U5T-14G381-EU_1634769242000.TAR.GZ 
[18/05/2022 23:27:24] Checking Existing File: 4U5T-14G421-FFJ.tar.gz 
[18/05/2022 23:27:24] Copying: 4U5T-14G421-FFJ.tar.gz 
[18/05/2022 23:32:04] Validating: 4U5T-14G421-FFJ.tar.gz 
[18/05/2022 23:32:50] Copied: 4U5T-14G421-FFJ.tar.gz 
[18/05/2022 23:32:50] Checking Existing File: 4U5T-14G424-FFJ.tar.gz 
[18/05/2022 23:32:50] Copying: 4U5T-14G424-FFJ.tar.gz 
[18/05/2022 23:32:50] Validating: 4U5T-14G424-FFJ.tar.gz 
[18/05/2022 23:32:50] Copied: 4U5T-14G424-FFJ.tar.gz 
[18/05/2022 23:32:50] Generating reformat.lst
[18/05/2022 23:32:50] Generating autoinstall.lst

Yes it should do, although i’m not sure why you are using a Alpha build of Syn3 Updater. but the alpha redirects to Stable currently anyway

In updater settings, I configured the region as Middle East /Africa. The apim original region was USA but I updated it with a local ZA vin asbuild file so I believe that should have changed the region to South Africa.

In updater new version, I configured it to Middle East Africa (ROW Maps). Is this in order or,

Will this cause any errors during or after installation? Should I have set the region in settings to USA?

It doesn’t make any difference because that region select just checks in the app that it matches.

I was not sure regarding the release branch. Should I re creat the usb drive with the stable setting.

Also I choose ver 21265 because I read the later version has issues with radio logos. Im not sure if this is used in South Africa. Would you recommend I use latest version 22048. If, can I only update the version on the drive I just created and leave the maps file when and nor format usb drive agin

You should be on Stable unless you have a reason to be on Alpha but the USB you created will be the same regardless

I don’t know about radio logos for ZA sorry.

Should I then update to latest version 22048 instead of 21265(no radio logo issues). Is the newer one better

This is your choice, there are no changelogs provided by Ford so i can not comment on if the newer version is better unfortunately.

Good day Cyanlabs. Hope you well.

I have successfully upgraded my Sync 3 to Sync 3.4 21265 South African Maps 2020Q4 paid feature.

I also updated my apim asbuild to a Local SA 2019 identical model that came factory with sync 3 and navigation. After This my navigation tab was available and gps location is working.

I also Master reset the Apim.

Everything is working 100% except Navigation voice commands and when I check available voice command list, navigation voice commands is not in the list. Only radio, call, temperature and menus

I have put in a location with touchscreen and navigation is working. The basic voice guidance is working like for direction, turn left , turn right, and in so many meters turn. Also my location on map is following 100%.

The only thing that is not working / or not available is the navigation voice command to give destination by voice.

I have read of another forum of someone that had exactly same situation and according to them the navigation voice commands files was not copied to their apim during installation. They also said that the voice commands cant be set only to one geographic location as in maps, you have to install all the voice commands of that region it cant be separated only for certain section of a region. I dont know if this is correct.

I have installed the South African 2020Q4 ROW region only. If this is the case then you need to update my license so ROW ALL is available in the Sync 3 updater.

If there is a way that the South African only maps work with voice then I will prefer that solution for my APIM to have max free space in order to operate better. If not than Ill have to load the ROM ALL voice because this is an essential feature and one of the main reasons a purchase the maps.

My installation took about 12min without any errors usb size is about 5GB. Attached please find interrogation file of apim.

Please let me know if there is a solution for South African Maps only to work with Navigation voice command. If not and the only solution is to install ROW ALL then you’ll have to update my activation key in order for 2020Q4 ROW maps to be available in Sync updater. Currently only 2019ROW ALL and South Africa 2020Q4 is available for selection.

Hope to hear from you soon.

Have a Blessed LIfe…

Sync_VWBY05AA.xml (10.0 KB)

Investigating this, stay tuned…

this is wrong, there are 2 ways to get ROW maps

  1. a AIO package with 2 files All Maps and All Nav Voice
  2. Individual countries (bundles) with 2 files, country maps and country Nav Voice

I can confirm there is an issue here somewhere, trying to establish where the issue is, seems to be a bug with Syn3 Updater…

There does not seem to be an issue with this, my understanding is NaviExtra packages include the voice in the single map_new.img file contained in the package.

Please try this autoinstall.lst (you can keep the other files on the USB [delete the reformat.lst])

autoinstall.lst (248 Bytes)

Please provide this forum topic link

Please also provide me via Direct Message/Private Message or Email a genuine ZA Vin i can check some stuff with.

So I only need to replace the current autoinstall.lst on the flash drive I used to install with the one you attached and delete the reformat.lst on the flash drive.

Will this perform a new installation from scratch?


It will not install from scratch.