New and improved: Updating your Lincoln/Ford Sync 3 to Sync 3.4 or above with latest F8 2019 maps (Europe, America, ETC.)

Introduction

This is a newer safer and more compatible guide for Ford / Lincoln Cars to upgrade your Sync 3 on any version to the latest Sync 3.4 version even though older hardware versions of the Sync 3 APIM are not officially compatible with newer versions of Sync.

Thanks to all the Russian guys over at https://ffclub.ru/topic/418797/ and a leaked ford flashing/formatting tool we have a solution.

If you car looks like the left side of this picture you are able to upgrade to Sync 3.4. If you car looks like the right side of this picture then you will require replacement hardware in order to have Sync 3.X

Here are some of the benefits of upgrading to Sync 3.4

  • Android Auto navigation on the small screen in the Dash Cluster / Speedo. (potentially car play aswell)
  • Much snappier and more responsive user interface
  • A nicer looking stock blue theme
  • Newest map data for SatNav
  • If you update your APIM firmware you can also get Radio logos and Calm Mode.
  • There are probably others, if you know of any let me know and i will add them here.

BY FOLLOWING THE BELOW GUIDE YOU TAKE FULL RESPONSIBILITY FOR ANY DAMAGES THAT MAY OCCUR, I AM NOT RESPONSIBLE FOR YOUR ACTIONS. THIS HAS BEEN EXTENSIVELY TESTED BY MANY PEOPLE WITH MANY DIFFERENT FORD AND LINCOLN CARS WITH NO ISSUES, I HAVE ALSO PERSONALLY TESTED THIS ON MY OWN FORD FOCUS MK3 2015 WITH A EU NAVIGATION MODEL APIM.

Guide Update History
Guide Update History

26/01/2020 – Fixed issue with autoinstall.lst for NA Navigation, NA Nav must use Sync_3.4.19101_NA_Base_WithNav_CYANLABS.zip see comments for more information.
26/01/2020
– Added a section explaining how to get your existing versions and to take note of them should something go wrong.
25/01/2020 – Initial Release of new updated method

Requirements

  • Although you can do it with just 1 USB, I recommend at least 2 with 3 being the preferred amount.
    1GB is fine for the first, 8GB is fine for the second, If you want map and voice data you will need a third which is atleast 16GB
  • A car with Ford / Lincoln Sync 3 installed, if you have the old 4 quadrant sync 2 system as shown above you are out of luck.
  • Please note the following variants of the APIM.
    • American, UAE, Turkey, ROW and China APIM’s with navigation has 32GB of storage.
    • European APIM with navigation has 64GB of storage.
    • European, American and ROW APIM’s without navigation have only 8GB or 16GB of storage.

0. Taking note of your current IVSU’s

In the unlikely event that something goes wrong it is highly recommend to take note of your current installed IVSU’s

  1. First we need to enter in to “Bezel Diagnostics”, this can change from car to car but it should be one of the following
    • Hold Skip Track on the stereo and Skip Track on the steering wheel for around 10 seconds. (Confirmed working on Ford Focus)
    • Hold Eject Skip for around 10 seconds.
    • Hold Eject Seek for around 10 seconds.
    • If none of the above work try googling “car name Sync diagnostic mode”.
  2. Once we are in Bezel Diagnostics touch “End Test”.
  3. Then touch “APIM Diagnostics”.
  4. Next touch “IVSU Versions”.
  5. Now you should be at a screen like below, if the page is mostly blank go back and touch “IVSU Versions” again, Take some photos of this information and make sure to scroll down if able to. The part numbers are the most important bit.

  6. Once you have all this information safely saved we can exit bezel diagnostics and continue with the rest of the guide.

1. Putting your Sync 3 in to “Factory Mode”

  1. Download the following file
  2. Make sure your USB is MBR not GPT – Click for instructions
  3. Format the smallest USB drive as exFAT in windows by right clicking the drive in This PC and pressing Format… and then make sure it’s set to exFAT and press Start.
    you may wish to format all drives that you will be using to save time later, all drives need to be MBR and exFAT.
  4. Extract Sync_Reformat_Tool_CYANLABS.zip to the root of the USB, it should look like this.
    Do not extract any TAR.GZ files only extract the .zip
  5. Safely remove the USB and unplug it from your computer and keep it to the side for now.

2. Downloading and copying the base system

Download one of the following files depending on your desired region.

  • European Base Package (for Nav and Non-Nav) with 19101, EU Logos, EU Grace notes, EU Voice
    Sync_3.4.19101_EU_Base_CYANLABS.zip
    MD5: A80CE697E62D9906D16972A3E3F3B8A3
    SHA-1: 18657169759E1C88BDC27943DC4B8E6C6EF5395C
  • American Non-Navigation Base Package (For Non-Nav) with 19101, NA Grace notes, NA Voice (NA logos are pre-included)
    Sync_3.4.19101_NA_Base_CYANLABS.zip
    MD5: 88570C69CCB23A0711786F8CF9C21404
    SHA-1: 142CAD54BCFE5FE0640A76035D7324BCB8C294C5
  • American Navigation Base Package (for Nav) with 19101, NA Grace notes, NA Voice (NA logos are pre-included), Navigation Map and Voice data.
    Languages supported: English American, Spanish Mexican, French Canadian
    Sync_3.4.19101_NA_Base_WithNav_CYANLABS.zip
    MD5: FB9C50F51500923A638631FB1005B84A
    SHA-1: 18764F047CF866E7AA91928F3E77D17C898807BA
  • Not sure what region you are or know that your region isn’t included, send me the IVSU Versions of your current system and i will see what i can do.
  1. Extract Sync_3.4.19101_**_Base**_CYANLABS.zip to the root of the USB again make sure it’s MBR (not GPT) and exFAT, it should look like this,
    The DONTINDX.MSA is not critical.
    Do not extract any TAR.GZ files only extract the .zip
  2. Safely remove the USB and unplug it from your computer and take this and the first USB to your car.

ONCE YOU HAVE INSERTED THE FIRST USB YOU WILL HAVE FORCED YOUR SYNC UNIT IN TO “FACTORY MODE” IT WILL NO LONGER BOOT NORMALLY UNTIL YOU REFLASH IT AT THIS POINT, DO NOT INSERT THE FIRST USB IF YOU HAVE NO INTENTION OF CONTINUING THE PROCESS!

3. Installing the 3.4 base system

  1. insert the first USB in to your car and make sure the ignition is on after ~2 minutes it should reboot and show “Please insert USB”.
  2. At this point we need to remove this USB and insert the second USB.
  3. Once the USB is detected it will start the reformat process and will progress through the following screens, it will take around 10 minutes.
    If you used the American with Nav package it will take significantly longer, 40-60 minutes if not longer.
  4. Once the install is complete you will see this screen, remove the USB and the system should start SYNC and the base system should be updated
  5. You should now be on 3.4.19101.
    • If you have a EU or NA non navigation model or a NA navigation model you are done.
    • If you have a EU navigation model please continue below to install navigation and voice and resolve the navigation fault.

4. Installing the EU navigation map data

This step is only required for EU Navigation, NA navigation should have used the Sync_3.4.19101_NA_Base_WithNav_CYANLABS.zip file and should already be up and running with navigation

Download the following map file

  1. Extract Sync_3.X_**_F8_Navigation_CYANLABS.zip to the root of the USB again make sure it’s MBR (not GPT) and exFAT, it should look like this,
    The DONTINDX.MSA is not critical.
    Do not extract any TAR.GZ files only extract the .zip
  2. Safely remove the USB and unplug it from your computer, switch on your car ignition and insert the USB you will see the following message at the top of the screen. It can take over 40 minutes, if you think your battery may die make sure to start your engine, you may wish to do this on your commute or a long journey so you aren’t sat in your car for a long time.
  3. Once the install is complete you will see this screen, restart your car and you should have navigation, however we still need to add the navigation voice, continue below.

5. Installing EU the navigation voice data

This step is only required for EU Navigation, NA navigation should have used the Sync_3.4.19101_NA_Base_WithNav_CYANLABS.zip file and should already be up and running with navigation

Download the following navigation voice file

  • European F8 Navigation Voice
    Sync_3.X_EU_F8_Nav_Voice_CYANLABS.zip
    Languages supported: English British, Dutch, French and German
    MD5: ED0E50BE254D90A79CD0C1042D3951E3
    SHA-1: 7C82476202308BDF07EE37ED576A3F266C3DC5BC
  1. Extract Sync_3.X_**_F8_Nav_Voice_CYANLABS.zip to the root of the USB again make sure it’s MBR (not GPT) and exFAT, it should look like this,
    The DONTINDX.MSA is not critical.
    Do not extract any TAR.GZ files only extract the .zip
  2. Safely remove the USB and unplug it from your computer, switch on your car ignition and insert the USB you will see the following message at the top of the screen. It won’t take as long as the map data but can still take over 20 minutes, if you think your battery may die make sure to start your engine, you may wish to do this on your commute or a long journey so you aren’t sat in your car for a long time.
  3. Once the install is complete you will see this screen, restart your car and you should now be fully up and running, continue below if you wish to upgrade to 19274.

6. Optional Extras

Section
Upgrading to Sync 3.4.19274
Downgrading to Sync 3.4.19101 or Sync 3.4.19200
Updating the firmware
Ford Sync file archive
Ford Sync 3 error code list
Sites that are discussing this guide
Upgrading to Sync 3.4.19274

Please note that the reformat tool has been BLACKLISTED in this version meaning you can’t use the reformat tool any more, you can however downgrade to an older version to be able to re-use the reformat tool (see section below)

  1. Download the following file.
  2. Extract the Sync_3.4.X_To_Sync_3.4.19274_CYANLABS.zip file to the root of the USB, it should look like this,
    Do not extract any TAR.GZ files only extract the .zip
    The DONTINDX.MSA is not critical.

  3. Safely remove the USB and unplug it from your computer, switch on your car ignition and insert the USB you will see the following message at the top.
  4. Once the install is complete you will see this screen and you should be on 19274 after a restart.
Downgrading to Sync 3.4.19101 or Sync 3.4.19200

This is only required if you have already upgraded to 19274 and wish to downgrade back to an older version. since 19274 blocks the reformat tool we will do a workaround and “update” to a lower version 19101 or 19200 in this case. This can also be used to switch from 19200 to 19101 and vice versa.

  1. Download one of the following files
  2. Extract the Sync_3.4.X_To_Sync_3.4.19***_CYANLABS.zip file to the root of the USB, it should look like this,
    Do not extract any TAR.GZ files only extract the .zip
    the DONTINDX.MSA is not critical.
  3. Safely remove the USB and unplug it from your computer, switch on your car ignition and insert the USB you will see the following message at the top.
  4. Once the install is complete you will see this screen and you should be on 19274 after a restart.
Updating the firmware

You may wish to upgrade your APIM firmware, to do this you will need either UCDS (recommended method) or a USB ELS27 or similar and the experimental ForScan build check the ForScan forums, more information can be found here https://ffclub.ru/topic/418797/jump_1470/

If you don’t update your firmware you may not get features like radio logos or “calm mode”.

To quote the Russian forum.

Calibration must be updated using Forscan or UCDS. In both case you have to follow a specific order. The order is the following:

GB5T-14G376-AA.vbf (Bootloader) //Mandatory
XXXX-14G374-XX.vbf (Diret Config Configuration) //Mandatory
XXXX-14G375-XX.vbf (ECU Calibration Data) //Mandatory
GB5T-14G379-AA.vbf (ECU Cal-Config #1 AKA Audio Profiles) //Facoltative
XXXX-14G379-XX.vbf (ECU Cal-Config #2 AKA Illumination) //Facoltative

Both 14G379 are not mandatory but i honestly don’t know which cars need it and which doesn’t.

Where you see XX it’s because it change based on revision (version), bootloader and audio profiles never changes (at least until now)

To determinate if a calibration is for a MY18.5 you have to read the first XXXX, they must have 1U5T or 5U5T (maybe 3U5T and 4U5T too but i’m not sure if they exist)

Also, it’s important to keep in mind that file 14G374 is different based on APIM region and Flash Size. here a summary:

XXXX-14G375-A*.vbf 8GB / 16GB EU without NAV
XXXX-14G375-B*.vbf 8GB / 16GB NA without NAV
XXXX-14G375-C*.vbf 8GB / 16GB ROW without NAV
XXXX-14G375-D*.vbf 32GB NA with NAV
XXXX-14G375-E*.vbf 32GB CHINA with NAV
XXXX-14G375-F*.vbf 32GB XX (i think it means ANY region) with NAV (Telenav)
XXXX-14G375-G*.vbf 32GB ROW With NAV (NNG)
XXXX-14G375-H*.vbf 64GB EU with NAV
XXXX-14G375-J*.vbf 32GB TURKEY with NAV
XXXX-14G375-K*.vbf 32GB UAE with NAV (NNG)

Where you can download the files?

From here:
https://www.ucdsys.ru/calibration/

If you are having issues where the APIM doesn’t turn off after the car ignition is off and door opened, you may need to use UCDS to set APIM > DEO5 > “illumination Gateway” > C1MCA,
i presume this can be done via ForScan however unfortunately i do not have the AsBuilt hex values.

Ford Sync file archive

Credit to https://ffclub.ru/topic/418797/ for most of these files / links.

You can use these files to create your own reformat.lst or autoinstall.lst files, a reformat.lst example can be found below.

APPS=5U5T-14G381-AP_1555085337000.TAR.GZ
VOICE=4U5T-14G391-AJ_1552513063000.TAR.GZ
VOICE_NAV=4U5T-14G422-BAC_1542814330000.TAR.GZ
GRACENOTES=4U5T-14G423-AA_123694.tar.gz
MAP=1U5T-14G421-BAE_1542902523000.TAR.GZ
MAP=1U5T-14G421-BCE_1542828353000.TAR.GZ
ENH_DAB=1U5T-14G658-AD_1544799507000.TAR.GZ
LICENSE=1U5T-14G424-BG_1547214450000.TAR.GZ

Application (Base)

Sync 3.2

1U5T-14G381-AE – 432Mb Sync3 v3.2.17182 30.06.2017
1U5T-14G381-AG – 432Mb Sync3 v3.2.17237 25.08.2017
1U5T-14G381-AJ – 440Mb Sync3 v3.2.17288 15.10.2017
1U5T-14G381-AK – 440Mb Sync3 v3.2.18004 04.01.2018
1U5T-14G381-BA – 420Mb Sync3 v3.2.18010 10.01.2018
1U5T-14G381-BC – 421Mb Sync3 v3.2.18072 13.03.2018
1U5T-14G381-BD – 421Mb Sync3 v3.2.18152 01.06.2018
1U5T-14G381-BE – 421Mb Sync3 v3.2.18275 02.10.2018
1U5T-14G381-CA – 440Mb Sync3 v3.2.18124 04.05.2018
2U5T-14G381-AG – 291Mb Sync3 v3.2.17263 20.09.2017
2U5T-14G381-AH – 300Mb Sync3 v3.2.17324 20.11.2017
2U5T-14G381-AJ – 300Mb Sync3 v3.2.18016 16.01.2018
2U5T-14G381-CA – 300Mb Sync3 v3.2.18066 07.03.2018

Sync 3.3

4U5T-14G381-AB – 458Mb Sync3 v3.3.17339 05.12.2017
4U5T-14G381-AD – 478Mb Sync3 v3.3.18037 06.02.2018
4U5T-14G381-AE – 484Mb Sync3 v3.3.18064 05.03.2018
4U5T-14G381-AF – 484Mb Sync3 v3.3.18096 06.04.2018
4U5T-14G381-AG – 485Mb Sync3 v3.3.18136 16.05.2018
4U5T-14G381-AH – 480Mb Sync3 v3.3.18190 09.07.2018
4U5T-14G381-AJ – 480Mb Sync3 v3.3.18201 20.07.2018
4U5T-14G381-AK – 480Mb Sync3 v3.3.18266 23.09.2018
4U5T-14G381-AL – 480Mb Sync3 v3.3.18295 22.10.2018
4U5T-14G381-AM – 480Mb Sync3 v3.3.18351 17.12.2018
4U5T-14G381-AN – 480Mb Sync3 v3.3.19052 21.02.2019
4U5T-14G381-BE – 342Mb Sync3 v3.3.18095 05.04.2018
4U5T-14G381-BH – 342Mb Sync3 v3.3.18183 02.07.2018
4U5T-14G381-BJ – 342Mb Sync3 v3.3.18201 20.07.2018

Sync 3.4

5U5T-14G381-AL – 891Mb Sync3 v3.4.18347 13.12.2018
5U5T-14G381-AM – 891Mb Sync3 v3.4.19050 19.02.2019
5U5T-14G381-AN – 891Mb Sync3 v3.4.19078 19.03.2019
5U5T-14G381-AP – 891Mb Sync3 v3.4.19101 11.04.2019
5U5T-14G381-BE – 399Mb Sync3 v3.202.18033 02.02.2018
5U5T-14G381-BH – 455Mb Sync3 v3.202.18249 06.09.2018
5U5T-14G381-BL – 463Mb Sync3 v3.4.18347 13.12.2018
5U5T-14G381-BM – 464Mb Sync3 v3.4.19050 19.02.2019
5U5T-14G381-BN – 464Mb Sync3 v3.4.19078 19.03.2019
5U5T-14G381-BP – 464Mb Sync3 v3.4.19101 11.04.2019
5U5T-14G381-CD – 828Mb Sync3 v3.4.19200 19.07.2019
5U5T-14G381-DD – 408Mb Sync3 v3.4.19200 19.07.2019
5U5T-14G381-DJ – 408Mb Sync3 v3.4.19274 02.10.2019
5U5T-14G381-CJ – 828Mb Sync3 v3.4.19274 02.10.2019 – This blocks the reformat tool

Voice

Language Info

(1) ARW,DUN,ENA,ENG,ENU,FRC,FRF,MNC,MNT,PTB,PTP,SPM
(2) ENU,FRC,SPM
(3) ARW,ENA,ENG,ENU,FRF,GED,PTB,RUR,SPM,TRT
(4) ENU,MNC,MNT
(5) ARW,CZC,DAD,DUN,ENG,ENU,FRF,GED,ITI,MNC,NON,PLP,PTP,RUR,SPE,SWS,TRT
(6) CZC,DAD,DUN,ENG,FRF,GED,ITI,NON,PLP,PTP,RUR,SPE,SWS,TRT
(7) ARW,ENA,ENG,FRF,GED,PTB,RUR,SPM,TRT
(8) ARW,DUN,ENA,ENG,ENU,FRC,FRF,KOK,MNC,MNT,PTB,SPM
(9) ENA,ENG,ENU,GED,MNT,PTB,RUR,SPM,TRT
(10) ARW,CZC,DAD,DUN,ENG,FIF,FRF,GED,ITI,NON,PLP,PTP,RUR,SPE,SWS,TRT
(11) ARW,DUN,ENA,ENG,ENI,ENU,FRC,FRF,KOK,MNC,MNT,PTB,PTP,SPE,SPM,THT
(12) ARW,DUN,ENG,ENI,ENU,FRC,FRF,MNC,PTP,SPE,SPM,THT
(13) ARW,DUN,ENG,ENU,FRC,FRF,MNC,PTP,SPE,SPM,THT

CZC – Czech
ARW – Arabic
CZC – Czech
DAD – Danish
DUN – Dutch
ENA – Australian English
ENG – British English
ENI – Indian English
ENU – American English
FRC – Canadian French
FRF – French
GED – German
ITI – Italian
KOK – Korean
MNC – Chinese Mandarin
MNT – Taiwanese Mandarin
NON – Norwegian
PLP – Polish
PTB – Brazilian Portuguese
PTP – Portuguese
RUR – Russian
SPE – Spanish
SPM – Mexican Spanish
SWS – Swedish
THT – Thai
TRT – Turkish

Sync 3.2

1U5T-14G391-AE – 1.5Gb Sync3 v3.2.17171 (10)
1U5T-14G391-BE – 1.4Gb Sync3 v3.2.17171 (11)
1U5T-14G391-CE – 380Mb Sync3 v3.2.17171 (2)
1U5T-14G391-DE – 1Gb Sync3 v3.2.17171 (9)
1U5T-14G391-EE – 185Mb Sync3 v3.2.17171 (4)
1U5T-14G391-FE – 1.3Gb Sync3 v3.2.17171 (12)
1U5T-14G391-AG – 1.5Gb Sync3 v3.2.17222 (10)
1U5T-14G391-BG – 1.4Gb Sync3 v3.2.17222 (11)
1U5T-14G391-CG – 385Mb Sync3 v3.2.17222 (2)
1U5T-14G391-DG – 1Gb Sync3 v3.2.17222 (9)
1U5T-14G391-EG – 188Mb Sync3 v3.2.17222 (4)
1U5T-14G391-FG – 1.3Gb Sync3 v3.2.17222 (12)
1U5T-14G391-AH – 1.5Gb Sync3 v3.2.17268 (10)
1U5T-14G391-BH – 1.4Gb Sync3 v3.2.17268 (11)
1U5T-14G391-CH – 383Mb Sync3 v3.2.17268 (2)
1U5T-14G391-DH – 1Gb Sync3 v3.2.17268 (9)
1U5T-14G391-EH – 188Mb Sync3 v3.2.17268 (4)
1U5T-14G391-FH – 1.3Gb Sync3 v3.2.17268 (12)
1U5T-14G391-BJ – 1.4Gb Sync3 v3.2.17321 (11)
1U5T-14G391-CJ – 382Mb Sync3 v3.2.17321 (2)
1U5T-14G391-DJ – 1Gb Sync3 v3.2.17321_DEVTEST (3)
1U5T-14G391-EJ – 188Mb Sync3 v3.2.17321 (4)
1U5T-14G391-FJ – 1.3Gb Sync3 v3.2.17321 (12)
1U5T-14G391-AK – 1.5Gb Sync3 v3.2.18002 (10)
1U5T-14G391-DK – 1Gb Sync3 v3.2.18002 (9)

4U5T-14G391-AJ – 1.5Gb Sync3 v3.2.19049
4U5T-14G391-BJ – 1.4Gb Sync3 v3.2.19049
4U5T-14G391-CJ – 381Mb Sync3 v3.2.19049
4U5T-14G391-DJ – 1Gb Sync3 v3.2.19049
4U5T-14G391-EJ – 187Mb Sync3 v3.2.19049
4U5T-14G391-FJ – 1.3Gb Sync3 v3.2.19049

5U5T-14G391-AA – 1.5Gb Sync3 v3.2.18018
5U5T-14G391-BA – 1.4Gb Sync3 v3.2.18018
5U5T-14G391-CA – 384Mb Sync3 v3.2.18018
5U5T-14G391-DA – 1Gb Sync3 v3.2.18018
5U5T-14G391-EA – 190Mb Sync3 v3.2.18018
5U5T-14G391-FA – 1.3Gb Sync3 v3.2.18018
5U5T-14G391-AB – 1.5Gb Sync3 v3.2.18241 (10)
5U5T-14G391-BB – 1.4Gb Sync3 v3.2.18241 (11)
5U5T-14G391-CB – 384Mb Sync3 v3.2.18241 (2)
5U5T-14G391-DB – 1Gb Sync3 v3.2.18241 (9)
5U5T-14G391-EB – 190Mb Sync3 v3.2.18241 (4)
5U5T-14G391-FB – 1.3Gb Sync3 v3.2.18241 (12)
5U5T-14G391-AH – 1.5Gb Sync3 v3.2.19164 (10)
5U5T-14G391-BH – 1.4Gb Sync3 v3.2.19164 (11)
5U5T-14G391-CH – 385Mb Sync3 v3.2.19164 (2)
5U5T-14G391-DH – 1Gb Sync3 v3.2.19164 (9)
5U5T-14G391-EH – 189Mb Sync3 v3.2.19164 (4)
5U5T-14G391-FH – 1.2Gb Sync3 v3.2.19164 (12)
5U5T-14G391-AK – 1.5Gb Sync3 v3.2.19258 (10)
5U5T-14G391-DK – 1Gb Sync3 v3.2.19258 (9)

Sync 3.3

4U5T-14G391-AE – 1.5Gb Sync3 v3.3.18057
4U5T-14G391-BE – 1.4Gb Sync3 v3.3.18057
4U5T-14G391-CE – 384Mb Sync3 v3.3.18057
4U5T-14G391-DE – 1Gb Sync3 v3.3.18057
4U5T-14G391-EE – 189Mb Sync3 v3.3.18057
4U5T-14G391-FE – 1.3Gb Sync3 v3.3.18057
4U5T-14G391-AG – 1.5Gb Sync3 v3.3.18088
4U5T-14G391-BG – 1.4Gb Sync3 v3.3.18088
4U5T-14G391-CG – 384Mb Sync3 v3.3.18088
4U5T-14G391-DG – 1Gb Sync3 v3.3.18088
4U5T-14G391-EG – 189Mb Sync3 v3.3.18088
4U5T-14G391-FG – 1.3Gb Sync3 v3.3.18088
4U5T-14G391-AH – 1.5Gb Sync3 v3.3.18114
4U5T-14G391-BH – 1.4Gb Sync3 v3.3.18114
4U5T-14G391-CH – 384Mb Sync3 v3.3.18114
4U5T-14G391-DH – 1Gb Sync3 v3.3.18114
4U5T-14G391-EH – 189Mb Sync3 v3.3.18114
4U5T-14G391-FH – 1.3Gb Sync3 v3.3.18114

Navigation Maps

Sync 3.2

1U5T-14G421-FAB – 3.4Gb Sync3 v3.2.17087 CAM Ver.675967 (16Q2), Caribbean Ver.671808 (1606), India Ver.671808 (16Q2), Israel Ver.677130 (1608), Mena Ver.675967 (16Q2), SAF Ver.675967 (16Q2), SEA Ver.671808 (1606)
1U5T-14G421-BAA – 1.7Gb Sync3 v3.2.17171 EU.1.17 (26.05.2017, F7 EU_Common)
1U5T-14G421-BBA – 434Mb Sync3 v3.2.17171 EU.1.17 (EU_Map_ext)
1U5T-14G421-BCA – 1.7Gb Sync3 v3.2.17171 EU.1.17 (EU_North_UK)
1U5T-14G421-BDA – 340Mb Sync3 v3.2.17171 EU.1.17 (EU_Iberia)
1U5T-14G421-BEA – 1.4Gb Sync3 v3.2.17171 EU.1.17 (EU_France)
1U5T-14G421-BFA – 2.4Gb Sync3 v3.2.17171 EU.1.17 (EU_Central)
1U5T-14G421-BGA – 1.9Gb Sync3 v3.2.17171 EU.1.17 (EU_South)
1U5T-14G421-BHA – 2.3Gb Sync3 v3.2.17171 EU.1.17 (EU_East)
1U5T-14G421-BJA – 19Mb Sync3 v3.2.17171 EU.1.17 (EU_Cyprus)
1U5T-14G421-CAA – 1.1Gb Sync3 v3.2.17193 NA.1.17 (21.06.2017)
1U5T-14G421-CBA – 820Mb Sync3 v3.2.17193 NA.1.17 (NA_Map_ext)
1U5T-14G421-CCA – 992Mb Sync3 v3.2.17193 NA.1.17 (NA_US_West)
1U5T-14G421-CDA – 1.1Gb Sync3 v3.2.17193 NA.1.17 (NA_US_Central)
1U5T-14G421-CEA – 1Gb Sync3 v3.2.17193 NA.1.17 (NA_US_NorthMid)
1U5T-14G421-CFA – 1Gb Sync3 v3.2.17193 NA.1.17 (NA_US_NorthEeast)
1U5T-14G421-CGA – 1Gb Sync3 v3.2.17193 NA.1.17 (NA_US_SouthEast)
1U5T-14G421-CHA – 963Mb Sync3 v3.2.17193 NA.1.17 (NA_Canada)
1U5T-14G421-CJA – 670Mb Sync3 v3.2.17193 NA.1.17 (NA_Mexico)
1U5T-14G421-AB – 6.1Gb Sync3 v3.2.17177 CN.1.16 (05.06.2017, SLG=0)
1U5T-14G421-DAD – 4.1Gb Sync3 v3.2.17177 EU.1.17 (19.04.2017, G7 Tur), ANZ.1.16 (21.10.2016), SA.1.17 (18.05.2017), TW.4.16 (15.02.2017, SLG=1)
1U5T-14G421-DAE – 4.2Gb Sync3 v3.2.17191 EU.1.17 (19.04.2017, G7 Tur), ANZ.1.17 (26.06.2017), SA.1.17 (18.05.2017), TW.4.16 (15.02.2017, SLG=1)
1U5T-14G421-FAC – 3.7Gb Sync3 v3.2.17191 CAM Ver.699603 (17Q1), Caribbean Ver.702939 (1612), India Ver.699603 (17Q1), Israel Ver.699603 (1703), Mena Ver.699603 (17Q1), SAF Ver.699603 (17Q1), SEA Ver.699603 (1703)
1U5T-14G421-AC – 5.8Gb Sync3 v3.2.17222 CN.1.16 (27.07.2017, SLG=0)
1U5T-14G421-BAB – 1.8Gb Sync3 v3.2.17222 EU.1.17 (EU_Common)
1U5T-14G421-BBB – 443Mb Sync3 v3.2.17222 EU.1.17 (EU_Map_ext)
1U5T-14G421-BCB – 1.5Gb Sync3 v3.2.17222 EU.1.17 (EU_North_UK)
1U5T-14G421-BDB – 936Mb Sync3 v3.2.17222 EU.1.17 (EU_Iberia)
1U5T-14G421-BEB – 1.4Gb Sync3 v3.2.17222 EU.1.17 (EU_France)
1U5T-14G421-BFB – 2.1Gb Sync3 v3.2.17222 EU.1.17 (EU_Central)
1U5T-14G421-BGB – 1.6Gb Sync3 v3.2.17222 EU.1.17 (EU_South)
1U5T-14G421-BHB – 1.9Gb Sync3 v3.2.17222 EU.1.17 (EU_East)
1U5T-14G421-BJB – 14Mb Sync3 v3.2.17222 EU.1.17 (F7 EU_Cyprus)
1U5T-14G421-CAB – 1.1Gb Sync3 v3.2.17222 NA.1.17 (13.08.2017)
1U5T-14G421-CBB – 820Mb Sync3 v3.2.17222 NA.1.17 (NA_Map_ext)
1U5T-14G421-CCB – 865Mb Sync3 v3.2.17222 NA.1.17 (NA_US_West)
1U5T-14G421-CDB – 994Mb Sync3 v3.2.17222 NA.1.17 (NA_US_Central)
1U5T-14G421-CEB – 918Mb Sync3 v3.2.17222 NA.1.17 (NA_US_NorthMid)
1U5T-14G421-CFB – 881Mb Sync3 v3.2.17222 NA.1.17 (NA_US_NorthEeast)
1U5T-14G421-CGB – 913Mb Sync3 v3.2.17222 NA.1.17 (NA_US_SouthEast)
1U5T-14G421-CHB – 897Mb Sync3 v3.2.17222 NA.1.17 (NA_Canada)
1U5T-14G421-CJB – 526Mb Sync3 v3.2.17222 NA.1.17 (NA_Mexico)
1U5T-14G421-AD – 5.9Gb Sync3 v3.2.17251 CN.1.16 (25.08.2017, SLG=0)
1U5T-14G421-BAC – 1.8Gb Sync3 v3.2.17254 EU.1.17 (27.08.2017, F7 EU_Common)
1U5T-14G421-BBC – 433Mb Sync3 v3.2.17254 EU.1.17 (EU_Map_ext)
1U5T-14G421-BCC – 1.5Gb Sync3 v3.2.17254 EU.1.17 (EU_North_UK)
1U5T-14G421-BDC – 937Mb Sync3 v3.2.17254 EU.1.17 (EU_Iberia)
1U5T-14G421-BEC – 1.4Gb Sync3 v3.2.17254 EU.1.17 (EU_France)
1U5T-14G421-BFC – 2.1Gb Sync3 v3.2.17254 EU.1.17 (EU_Central)
1U5T-14G421-BGC – 1.6Gb Sync3 v3.2.17254 EU.1.17 (EU_South)
1U5T-14G421-BHC – 1.9Gb Sync3 v3.2.17254 EU.1.17 (EU_East)
1U5T-14G421-BJC – 13Mb Sync3 v3.2.17254 EU.1.17 (EU_Cyprus)
1U5T-14G421-CAC – 1.1Gb Sync3 v3.2.17251 NA.1.17 (28.08.2017)
1U5T-14G421-CBC – 820Mb Sync3 v3.2.17251 NA.1.17 (NA_Map_ext)
1U5T-14G421-CCC – 865Mb Sync3 v3.2.17251 NA.1.17 (NA_US_West)
1U5T-14G421-CDC – 1Gb Sync3 v3.2.17251 NA.1.17 (NA_US_Central)
1U5T-14G421-CEC – 881Mb Sync3 v3.2.17251 NA.1.17 (NA_US_NorthMid)
1U5T-14G421-CFC – 881Mb Sync3 v3.2.17251 NA.1.17 (NA_US_NorthEeast)
1U5T-14G421-CGC – 931Mb Sync3 v3.2.17251 NA.1.17 (NA_US_SouthEast)
1U5T-14G421-CHC – 897Mb Sync3 v3.2.17251 NA.1.17 (NA_Canada)
1U5T-14G421-CJC – 526Mb Sync3 v3.2.17251 NA.1.17 (NA_Mexico)
1U5T-14G421-DAF – 3.7Gb Sync3 v3.2.17255 EU.1.17 (27.08.2017, G7 Tur), ANZ.1.17 (27.08.2017), SA.1.17 (15.08.2017), TW.4.16 (15.02.2017, SLG=1)
1U5T-14G421-AE – 5.9Gb Sync3 v3.2.17320 CN.1.16 (25.08.2017, SLG=0)
1U5T-14G421-BAD – 1.8Gb Sync3 v3.2.17320 EU.1.17 (27.08.2017, F7 EU_Common)
1U5T-14G421-BBD – 432Mb Sync3 v3.2.17320 EU.1.17 (EU_Map_ext)
1U5T-14G421-BCD – 1.5Gb Sync3 v3.2.17320 EU.1.17 (EU_North_UK)
1U5T-14G421-BDD – 935Mb Sync3 v3.2.17320 EU.1.17 (EU_Iberia)
1U5T-14G421-BED – 1.4Gb Sync3 v3.2.17320 EU.1.17 (EU_France)
1U5T-14G421-BFD – 2.1Gb Sync3 v3.2.17320 EU.1.17 (27.08.2017, F7 EU_Central)
1U5T-14G421-BGD – 1.6Gb Sync3 v3.2.17320 EU.1.17 (EU_South)
1U5T-14G421-BHD – 1.9Gb Sync3 v3.2.17320 EU.1.17 (27.08.2017, F7 EU_East)
1U5T-14G421-BJD – 14Mb Sync3 v3.2.17320 EU.1.17 (EU_Cyprus)
1U5T-14G421-CAD – 1.1Gb Sync3 v3.2.17320 NA.1.17 (28.08.2017)
1U5T-14G421-CBD – 825Mb Sync3 v3.2.17320 NA.1.17 (NA_Map_ext)
1U5T-14G421-CCD – 867Mb Sync3 v3.2.17320 NA.1.17 (NA_US_West)
1U5T-14G421-CDD – 1Gb Sync3 v3.2.17320 NA.1.17 (NA_US_Central)
1U5T-14G421-CED – 882Mb Sync3 v3.2.17320 NA.1.17 (NA_US_NorthMid)
1U5T-14G421-CFD – 882Mb Sync3 v3.2.17320 NA.1.17 (NA_US_NorthEeast)
1U5T-14G421-CGD – 914Mb Sync3 v3.2.17320 NA.1.17 (NA_US_SouthEast)
1U5T-14G421-CHD – 898Mb Sync3 v3.2.17320 NA.1.17 (NA_Canada)
1U5T-14G421-CJD – 527Mb Sync3 v3.2.17320 NA.1.17 (NA_Mexico)
1U5T-14G421-DAG – 3.7Gb Sync3 v3.2.17320 EU.1.17 (27.08.2017, G7 Tur), ANZ.1.17 (27.08.2017), SA.1.17 (15.08.2017), TW.4.16 (15.02.2017, SLG=1)
1U5T-14G421-BAE – 2.2Gb Sync3 v3.2.18305 EU.1.18 (16.09.2018, F8 EU_Common)
1U5T-14G421-BBE – 442Mb Sync3 v3.2.18305 EU.1.18 (EU_Map_ext)
1U5T-14G421-BCE – 1.6Gb Sync3 v3.2.18305 EU.1.18 (EU_North_UK)
1U5T-14G421-BDE – 1Gb Sync3 v3.2.18305 EU.1.18 (EU_Iberia)
1U5T-14G421-BEE – 1.5Gb Sync3 v3.2.18305 EU.1.18 (EU_France)
1U5T-14G421-BFE – 2.3Gb Sync3 v3.2.18305 EU.1.18 (EU_Central)
1U5T-14G421-BGE – 1.8Gb Sync3 v3.2.18305 EU.1.18 (EU_South)
1U5T-14G421-BHE – 2.3Gb Sync3 v3.2.18305 EU.1.18 (EU_East)
1U5T-14G421-BJE – 17Mb Sync3 v3.2.18305 EU.1.18 (EU_Cyprus)

Sync 3.3

Navigation Voice

Language Info

(1) NA (ENU,FRC,SPM)
(2) EU (CZC,DAD,DUN,ENG,FRF,GED,ITI,NON,PLP,PTP,RUR,SPE,SWS,TRT)
(3) DUN,ENG,FRF,GED
(4) DAD,FIF,NON,SWS
(5) ITI,PTP,SPE,TRT
(6) CN (ENU,MNC)
(7) ANZ (ENA,ENG), SA (ENU,PTB,SPM), TUR (ENG,GED,RUR,TRT)

CZC – Czech
ARW – Arabic
CZC – Czech
DAD – Danish
DUN – Dutch
ENA – Australian English
ENG – British English
ENI – Indian English
ENU – American English
FRC – Canadian French
FRF – French
GED – German
ITI – Italian
KOK – Korean
MNC – Chinese Mandarin
MNT – Taiwanese Mandarin
NON – Norwegian
PLP – Polish
PTB – Brazilian Portuguese
PTP – Portuguese
RUR – Russian
SPE – Spanish
SPM – Mexican Spanish
SWS – Swedish
THT – Thai
TRT – Turkish

1U5T-14G422-AC – 1.4Gb Sync3 v3.2.17103 CN, Nav Data version: 530. Packaged on: 20170202 (6)
1U5T-14G422-DC – 1.2Gb Sync3 v3.2.17103 ANZ 430/20170202, SA 440/20170317, TUR 510/20170202 (7)
1U5T-14G422-CD – 2.2Gb Sync3 v3.2.17129 NA, Nav Data version: 1050. Packaged on: 20170419 (1)

1U5T-14G422-BAB – 2Gb Sync3 v3.2.17195 EU, Nav Data version: 600. Packaged on: 20170623 (3)
1U5T-14G422-BDB – 1.8Gb Sync3 v3.2.17195 EU, Nav Data version: 600. Packaged on: 20170623 (4)
1U5T-14G422-BBB – 1.9Gb Sync3 v3.2.17195 EU, Nav Data version: 600. Packaged on: 20170623 (5)
1U5T-14G422-BAC – 2Gb Sync3 v3.2.17222 EU, Nav Data version: 600. Packaged on: 20170623 (3)
1U5T-14G422-BDC – 1.8Gb Sync3 v3.2.17222 EU, Nav Data version: 600. Packaged on: 20170623 (4)
1U5T-14G422-BBC – 1.9Gb Sync3 v3.2.17222 EU, Nav Data version: 600. Packaged on: 20170623 (5)
1U5T-14G422-BAD – 2Gb Sync3 v3.2.17268 EU, Nav Data version: 630. Packaged on: 20170929 (3)
1U5T-14G422-BCD – 1.4Gb Sync3 v3.2.17268 EU, Nav Data version: 630. Packaged on: 20170929
1U5T-14G422-BDD – 1.8Gb Sync3 v3.2.17268 EU, Nav Data version: 630. Packaged on: 20170929 (4)
1U5T-14G422-CAC – 1.3Gb Sync3 v3.2.17268 NA, Nav Data version: 1130. Packaged on: 20170928 (ENU)
1U5T-14G422-CBC – 802Mb Sync3 v3.2.17268 NA, Nav Data version: 1130. Packaged on: 20170928 (SPM)
1U5T-14G422-CCC – 553Mb Sync3 v3.2.17268 NA, Nav Data version: 1130. Packaged on: 20170928 (FRC)
1U5T-14G422-BBD – 1.9Gb Sync3 v3.2.17268 EU, Nav Data version: 630. Packaged on: 20170929 (5)
1U5T-14G422-DE – 1.8Gb Sync3 v3.2.17268 EU, Nav Data version: 520. Packaged on: 20170928 (7)
1U5T-14G422-AD – 1.4Gb Sync3 v3.2.17321 CN, Nav Data version: 530. Packaged on: 20170202 (6)
1U5T-14G422-BAE – 2Gb Sync3 v3.2.17321 EU, Nav Data version: 630. Packaged on: 20170929 (3)
1U5T-14G422-BBE – 1.9Gb Sync3 v3.2.17321 EU, Nav Data version: 630. Packaged on: 20170929 (5)
1U5T-14G422-BDE – 1.8Gb Sync3 v3.2.17321 EU, Nav Data version: 630. Packaged on: 20170929 (4)
1U5T-14G422-CAD – 1.3Gb Sync3 v3.2.17321 NA, Nav Data version: 1130. Packaged on: 20170928 (ENU)
1U5T-14G422-CBD – 800Mb Sync3 v3.2.17321 NA, Nav Data version: 1130. Packaged on: 20170928 (SPM)
1U5T-14G422-CCD – 552Mb Sync3 v3.2.17321 NA, Nav Data version: 1130. Packaged on: 20170928 (FRC)
1U5T-14G422-DF – 1.3Gb Sync3 v3.2.17321 ANZ 520/20170928, SA 520/20170928, TUR 630/20170929 (7)

4U5T-14G422-AA – 1.6Gb Sync3 v3.2.17324 CN, Nav Data version: 600. Packaged on: 20171102 (6)
4U5T-14G422-BCA – 1.4Gb Sync3 v3.2.18023 EU, Nav Data version: 640. Packaged on: 20180119 (CZC,PLP,RUR)
4U5T-14G422-CAA – 1.3Gb Sync3 v3.2.18023 NA, Nav Data version: 1140. Packaged on: 20180119 (ENU)
4U5T-14G422-CBA – 800Mb Sync3 v3.2.18023 NA, Nav Data version: 1140. Packaged on: 20180119 (SPM)
4U5T-14G422-CCA – 552Mb Sync3 v3.2.18023 NA, Nav Data version: 1140. Packaged on: 20180119 (FRC)
4U5T-14G422-DA – 1.3Gb Sync3 v3.2.18023 ANZ 520/20170928, SA 520/20170928, TUR 640/20180119 (7)
4U5T-14G422-AB – 1.7Gb Sync3 v3.2.18241 CN, Nav Data version: 600. Packaged on: 20171102 (6)
4U5T-14G422-BAB – 2Gb Sync3 v3.2.18241 EU, Nav Data version: 640. Packaged on: 20180119 (3)
4U5T-14G422-BBB – 1.9Gb Sync3 v3.2.18241 EU, Nav Data version: 640. Packaged on: 20180119 (4)
4U5T-14G422-BCB – 1.4Gb Sync3 v3.2.18241 EU, Nav Data version: 640. Packaged on: 20180119
4U5T-14G422-BDB – 1.8Gb Sync3 v3.2.18241 EU, Nav Data version: 640. Packaged on: 20180119 (5)
4U5T-14G422-CAB – 1.3Gb Sync3 v3.2.18241 NA, Nav Data version: 1140. Packaged on: 20180119 (ENU)
4U5T-14G422-CBB – 802Mb Sync3 v3.2.18241 NA, Nav Data version: 1140. Packaged on: 20180119 (SPM)
4U5T-14G422-CCB – 553Mb Sync3 v3.2.18241 NA, Nav Data version: 1140. Packaged on: 20180119 (FRC)
4U5T-14G422-DB – 1.3Gb Sync3 v3.2.18241 EU, Nav Data version: 640. Packaged on: 20180119
4U5T-14G422-BAC – 2.1Gb Sync3 v3.2.18305 EU, Nav Data version: 700. Packaged on: 20180604 (3)
4U5T-14G422-BBC – 2Gb Sync3 v3.2.18305 EU, Nav Data version: 700. Packaged on: 20180604 (4)
4U5T-14G422-BCC – 1.5Gb Sync3 v3.2.18305 EU, Nav Data version: 700. Packaged on: 20180604
4U5T-14G422-BDC – 1.8Gb Sync3 v3.2.18305 EU, Nav Data version: 700. Packaged on: 20180604 (5)
4U5T-14G422-CAC – 1.2Gb Sync3 v3.2.18305 NA, Nav Data version: 1210. Packaged on: 20181009 (ENU)
4U5T-14G422-CBC – 751Mb Sync3 v3.2.18305 NA, Nav Data version: 1210. Packaged on: 20181009 (SPM)
4U5T-14G422-CCC – 537Mb Sync3 v3.2.18305 NA, Nav Data version: 1210. Packaged on: 20181009 (FRC)
4U5T-14G422-DC – 1.3Gb Sync3 v3.2.18305 ANZ 600/20180611, SA 520/20170928, TUR 700/20180604 (7)

Gracenotes

Language Info

(1) DUN,ENG,FRF,GED,ITI,PTP,RUR,SPE,TRT
(2) DUN,ENA,ENG,ENI,ENU,FRC,FRF,KOK,MNC,PTB,PTP,SPE,SPM
(3) DUN,ENA,ENG,ENU,FRC,FRF,MNC,PTB,PTP,SPM
(4) DUN,ENG,ENI,ENU,FRC,FTF,GED,ITI,MNC,PTP,RUR,SPE,SPM,TRT
(5) DUN,ENG,ENU,FRF,GED,ITI,MNC,PTP,RUR,SPE,TRT
(6) DUN,ENG,FRF,GED,ITI,PTP,RUR,SPE,TRT
(7) ENA,ENG,ENU,FRF,GED,PTB,RUR,SPM,TRT
(8) ENA,ENG,ENU,GED,PTB,RUR,SPM,TRT
(9) ENU,FRC,SPM
(10) ENU,MNC

Sync 3.2

1U5T-14G423-AB – 710Mb Sync3 v3.2.17089 1.1.1.1319 (EU-0010) (17.02.2017) (1) RUR v1_3_3
1U5T-14G423-BB – 745Mb Sync3 v3.2.17089 1.1.1.1322 (GL-0011) (17.02.2017) (2)
1U5T-14G423-CB – 725Mb Sync3 v3.2.17089 1.1.1.1332 (NA-0010) (19.02.2017) (9)
1U5T-14G423-DB – 718Mb Sync3 v3.2.17089 1.1.1.1322 (GL-0011) (17.02.2017) (8)
1U5T-14G423-EB – 498Mb Sync3 v3.2.17089 1.1.1.1329 (CN-0010) (19.02.2017) (10)
1U5T-14G423-FB – 742Mb Sync3 v3.2.17089 1.1.1.1322 (GL-0011) (17.02.2017) (4)
1U5T-14G423-AC – 709Mb Sync3 v3.2.17320 1.1.1.1319 (EU-0010) (17.02.2017) (1) RUR v1_3_3
1U5T-14G423-BC – 743Mb Sync3 v3.2.17320 1.1.1.1322 (GL-0011) (17.02.2017) (2)
1U5T-14G423-CC – 724Mb Sync3 v3.2.17320 1.1.1.1332 (NA-0010) (19.02.2017) (9)
1U5T-14G423-DC – 717Mb Sync3 v3.2.17320 1.1.1.1322 (GL-0011) (17.02.2017) (8)
1U5T-14G423-EC – 497Mb Sync3 v3.2.17320 1.1.1.1329 (CN-0010) (19.02.2017) (10)
1U5T-14G423-FC – 741Mb Sync3 v3.2.17320 1.1.1.1322 (GL-0011) (17.02.2017) (4)

Sync 3.3

4U5T-14G423-AA – 709Mb Sync3 v3.3.18082 1.1.1.1319 (EU-0010) (17.02.2017)
4U5T-14G423-BA – 743Mb Sync3 v3.3.18082 1.1.1.1322 (GL-0011) (17.02.2017)
4U5T-14G423-CA – 724Mb Sync3 v3.3.18082 1.1.1.1332 (NA-0010) (19.02.2017)
4U5T-14G423-DA – 717Mb Sync3 v3.3.18082 1.1.1.1322 (GL-0011) (17.02.2017)
4U5T-14G423-EA – 497Mb Sync3 v3.3.18082 1.1.1.1329 (CN-0010) (19.02.2017)
4U5T-14G423-FA – 741Mb Sync3 v3.3.18082 1.1.1.1322 (GL-0011) (17.02.2017)

Note that according to the guys on the russian forum, siriusxm logo are embedded in the system. external logo packages is for europe only.
Ford Sync 3 error code list

Error Codes

NAVVOICE_ERR01 – Error is NAV_VOICE_ERROR
BGMAP_ERR01 – Error is BGMAP_ERROR

LIC_ERR01 – Error is MAP_LICENSE_MISMATCH_ERROR
LIC_ERR02 – Error is LICENSE_READING_ERROR

INSTL_ERR03 – Error is SCRIPT_PERMISSION_CHANGE_ERROR
INSTL_ERR04 – Error is SCRIPT_FILE_NOT_PRESENT_ERROR
INSTL_ERR05 – Error is POPUP_UTILITY_EXECUTION_ERROR
INSTL_ERR06 – Error is IMAGE_MOVING_ERROR
INSTL_ERR07 – Error is WRITING_NAV_LICENSE_TO_DPS_ERROR
INSTL_ERR08 – Error is APPS_TOGGLE_ERROR
INSTL_ERR09 – Error is IMAGE_TOGGLE_ERROR
INSTL_ERR10 – Error is APPS_UPDATE_BOOT_ERROR
INSTL_ERR11 – Error is APPS_UPDATE_PART_ERROR
INSTL_ERR12 – Error is DIR_CREATION_ERROR
INSTL_ERR13 – Error is UNMOUNT_ERROR
INSTL_ERR14 – Error is ACTIVATION_PENDING_ERROR
INSTL_ERR15 – Error is UNABLE_TO_FIND_PASSIVE_PARTITION_ERROR

LST_ERR03 – Error is LST_ERR_NO_APPROPRIATE_SECTION
LST_ERR04 – Error is LST_ERR_NO_SECTION
LST_ERR05 – Error is LST_PKG_FILE_NOT_FOUND
LST_ERR06 – Error is LST_ERR_MALICIOUS_CHAR  – Fix: Make sure there are no spaces in filenames or other strange characters in the autoinstall.lst file
LST_ERR07 – Error is LST_ERR_NO_OPEN1_PARAM
LST_ERR08 – Error is LST_ERR_OPEN_LIMIT_EXCEEDED – Fix: you can only have 10 items in the autoinstall.lst, remove extras.

VER_ERR01 – Error is VER_UNABLE_TO_FIND_VER_FILE
VER_ERR02 – Error is VER_FPN_EMPTY
VER_ERR03 – Error is VER_ERR_PARSE_VER_INF
VER_ERR04 – Error is VER_FILENAME_EMPTY
VER_ERR05 – Error is VER_VIN_MISMATCH
VER_ERR06 – Error is VER_ESN_MISMATCH
VER_ERR07 – Error is VER_TIME_LIMIT_EXCEED
VER_ERR08 – Error is VER_SETTING_VER_INFO_ERROR
VER_ERR09 – Error is VER_SAVE_LOCATION_EMPTY_INVALID_ERROR
VER_ERR10 – Error is VER_FPN_VERSION_MOVING_IN_TMP_ERROR
VER_ERR11 – Error is VER_FPN_IMAGE_FILE_NOT_PRESENT
VER_ERR12 – Error is VER_FILE_HASH_VALUE_NOT_PRESENT
VER_ERR13 – Error is VER_FILE_SIZE_NOT_PRESENT
VER_ERR14 – Error is VER_PKG_TYPE_NOT_PRESENT
VER_ERR15 – Error is VER_FILE_NOT_PRESENT_TO_CALC_HASH

MEM_ERR01 – Error is MEM_NOSPACE_TO_COPY
MEM_ERR03 – Error is MEM_NOSPACE_TO_EXTRACT

PKG_ERR02 – Error is PKG_DWNLD_PKG_NOT_FOUND
PKG_ERR03 – Error is PKG_UNTAR_FAILURE
PKG_ERR04 – Error is PKG_REVOKED

SIGN_ERR01 – Error is UNSIGN_ERROR
SIGN_ERR02 – Error is SIGN_HASH_VALUE_MISMATCH
SIGN_ERR03 – Error is SIGN_CERTS_NOT_PRESENT_ON_SYNC
SIGN_ERR04 – Error is INSTALL_ERROR
SIGN_ERR05 – Error is SCRIPT_INSTALL_ERROR

Contributions and Help

Hopefully you are all up and running with your newly upgraded Sync software however if you are not leave a comment below, send a Facebook message or join the discord server

When leaving a comment or message please include the following

  1. Region
  2. Sync Version
  3. Navigation or Non Navigation
  4. What type of computer you used (Windows, Mac, Linux etc)
  5. Any relevant information such as error message or screenshot

This will help me help you quicker.

If this guide has been helpful and you would like to support CyanLabs feel free to donate using one of the buttons below. This is greatly appreciated but of-course is not required at all.

Buy Me A Coffee

Still Struggling?

Due to the sheer amount of views and comments this guide has received i am unable to help everyone on a 1 by 1 basis however i will try my best to help in the comments, on discord and via Facebook. There are currently over 100k views on this page and over 500 comments.

However if you are still struggling with getting this sorted i am happy to help remotely via TeamViewer remote desktop software (Windows, Mac, Linux) or Chrome Remote Desktop (ChromeOS) for a small fee of $35 USD for 1 hour (not including download time) of 1 to 1 (Text Chat) support remotely paid via Paypal, Unfortunately multiple people have decided to go for this and not pay so i do require this Payment before hand to prevent people from getting the help and not paying. If this is something you are interested in please contact me via Email, Facebook or Discord.

101 Comments. Leave new

  • USA
    3.4 (19201)
    Navigation
    Windows 10
    everything works as it should besides Navigation. I go to load my 3rd USB and it pulls SIGN_ERR01 any idea what im doing wrong? other then that everything works as it should besides Navigation

    Reply
  • I just tried your newest NA with NAV method (1 file + Format tool) and it worked perfectly. Previously I could update to 3.4, but when I would load NA Nav, Sync would give me the error SIGN_ERR01 and wouldn’t go any further. I tried re-downloading and reformatting several times with no luck. Thanks for the new update!

    Reply
  • Have a 2016 Focus RS (RS2 trim level with Nav) in the United States and want to update to 3.4. Do you have a guide on how to update the APIM firmware using Forscan? I have an OBDLink MX Bluetooth OBD2 adapter and Forscan loaded on a laptop but can’t find a way to update it using Forscan.

    Reply
  • I upgraded right now on MacOS, 11/2018 pre-facelift Ford Mondeo HB, navigation, everything went as described. In last step I upgraded Czech nav voice. Many thanks to fma965 – I`ll buy you coffee.

    Without last step Sync3 was in Czech language, talking Czech, voice commands in Czech, but navi voice command were missing.
    Becourse of some maps upgrade problems reported I made one minor change in maps autoinstall file. I changed all files extension with small font. Some systems are case sensitive and files are .tar.gz but autoinstall file paths are .TAR.GZ.
    After restart system was bit lagy, but after several operations seems to be OK. I am pretty sure it is not faster nor smoother. Graphics is more modern, navi maps shows both ETA and KMs.

    EDIT: upgraded to 19274. Everything works perfect.

    Reply
    • Thanks, i’m not sure quite what you are saying with this part “Without last step Sync3 was in Czech language, talking Czech, voice commands in Czech, but navi voice command were missing.” are you saying the navigation voice wasn’t czech? did you fix this?

      Reply
      • No, everything was in Czech except navigation voice commands(czech language changed in setup). This was fixed after updating voice command file (described in last step) I only wanted to point it.

        Now I am going to upgrade to 19274. I’m confused about this sentence: Once you have downloaded the above package for your region… What region is in download?

        Reply
      • No, everything was in Czech except navigation voice commands(czech language changed in setup). This was fixed after updating voice command file (described in last step) I only wanted to point it.

        Now I am going to upgrade to 19274. I’m confused about this sentence: Once you have downloaded the above package for your region… What region is in download?

        Reply
  • Couple questions.

    First: anyone pull this off on a 2018 Ford Expedition Platinum? I am stuck on V3.0 19205 I believe. After it’s installed I can see Android Auto screens in the center instrument cluster (behind the steering wheel)? if so that is awesome 🙂

    Second: if I am using US Nav, then I don’t need the third USB stick? Just stick one for repartitioning then stick two with the US NAV version is enough right?

    Third: I don’t need to upgrade the APIM, right? No reason but I could reflash it to get the Calm Mode?

    Reply
    • 1. It will work on any sync 3 I’m sure someone has done it for a ford expedition.

      2. Correct due to the lack of licenses for na maps we do a workaround.

      3. Nope but if you can it’s good to do so to get extra features.

      Aa will show in the instrument cluster screen but it may need a Apim firmware update I’m not sure.

      Reply
      • Thanks a lot for doing this. I’m about to proceed.

        Just to be clear, both of the DONTINDX.MSA files are not necessary (for either usb 1 or 2). Because I can’t find that file in either of the archives I downloaded.. I suppose the screenshot show’s it in one of the steps but it says it’s not necessary which is good since I don’t have the file.

        Reply
  • Hi, first I want to thank you, the upgrade worked for me and now I’m on Sync 3.4 on a Ford Mondeo Vignale Hybrid from 2017, which was running sync 3.0.

    The F8 maps are not only for 3.2 and higher, I had the F8 maps installed on sync 3.0 (Europe)

    I do not really like the new theme compared to how 3.0 did look like, but I will get used too it. I think it looks like a pioneer aftermarket radio now but on the other hand, it is more fancy. The blue does just totally not match Fords black interiors I guess 🙂

    After the system restarted (after the first usb stick was put in) I worried, because the screen did go black and did no longer respond to anything (I saw some red error screen for a while). A few restarts of the car did help me, I was happy when the message ‘insert USB’ did show up. After this message, the update started succesfully. I like the images, but I cannot imagine that Ford has put them in? Who has created this update tool?

    The DONTINDX is not listed in the Google drive link (first USB). Do you know what this DONTINDX does? Because I did not had it on my USB, and the Ford sync system did show (for a short time) ‘indexing files’. j

    I think you should put your ‘DONTINDX’ is not critical warning also in step 1.

    A question: is it possible to downgrade to 3.0, now when 3.4 is installed?

    Another question: what are the differences between 19101, 19200 and 19274?

    I think it is a bit crazy that Ford just doesn’t publish these updates publicly..

    Again: many thanks, I really appreciate the work that you are putting into these guide.

    Edit: when I open my car door, the Vignale logo will still show. But when I shut the car down and open the door, a Ford logo will appear instead of a vignale logo. I guess that this is happening with every default theme, so maybe you can add it to the guide.

    Edit 2: I also cannot turn the heated seats on via the display, but I do not know if I was able to do this in 3.0 (although I vague remember that I could)

    Edit 3: I’m seeing video’s of sync 3.4 with the heated steering wheel/seats and cooled seats options available on the screen, even on the home screen (which is new). I do not understand why I do not see them, maybe this has something to do with the various versions of 3.4? Or maybe the firmware?

    Edit 4: Does the ‘scrolling’ through a song only works with USB music and not when a Bluetooth phone is connected?

    Edit 5: It looks like the day/night theme switching is a lot slower, compared to sync 3.0.

    Reply
    • hi, Thanks for the detail replied. maybe a bit too detailed 😉

      No this is a leaked ford official tool, the images are probably to stop any potential LCD burn in, although i’m not sure these displays are using a technology that is prone to this. the images are a bit odd though i have to admit, i guess since it’s a factory tool they probably just did something to show it wasn’t frozen.
      It has to be official as all packages are signed by ford’s cryptographic signature. strangely this tool does check if you have a compatible car but then continues anyway, could literally be a bug in the code or intentional, either way we can use it to get sync 3+ on our non 3+ compatible devices.

      the DONTINDX file is exactly what it sounds like “Dont Index” it tells SYNC to just not index the USB and instead only process the update.

      You can downgrade but the exact steps vary a lot, hopefully you took note of your IVSU’s as that will make it a lost easier.

      I can’t answer what the differences are, 19200 appears to be what is used on new cars in showrooms according to reports., 19101 is the only one with a auto dim option, all others force it on with no choice to change it.

      It is complicated for ford to update older units, the reformat tool, repartitions the system. they can’t release an update due to too small partition sizes on the older variants.

      Edit 1 : Yes this happens on default themes, not sure if it’s a bug by ford and they never fixed it or it’s intentional, personally i reckon the latter.

      Edit 2 / 3 : You will likely need to set some setting in Forscan or UCDS, i can’t advise with this as it’s different depending on many factors, google your car and apim asbuilt.

      Edit 4: honestly i don’t know i only really use AA mostly.

      Edit 5: i don’t seem to have this issue,.

      Reply
  • Following the steps of the “New and improved” tutorial i successfully installed the EU 3.4 base system, navigation and voice data.
    Focus ST year 2017
    Region: ITALY
    Sync Version: 3.0 Build 19205
    Navigation
    Windows 10.
    Installation: To activate factory mode took about 10 sec after inserting the 1 usb, at this point i was a little bit worried because a red screen appeared with “Error update package not found…” i just wait 1 minute to see if something happens, did nothing, at this point i remove the 1 usb and insert the second one, it immediately recognize it and start installing the base 3.4, after about 9 minutes the installation was completed and running.
    For the maps data took about 35 minutes. At this point i try the navigation before installing the voice data and it was running correctly in the language(ITI) i use with 3.0 sync version.
    For the voice data took about 8 minutes to install and nothing seems to change, everything its working fine till now.

    Update i running on:
    Sync version 3.4 Build 19101
    Gracenote: 1.1.1.1319 (EU-0010)

    Reply
  • well i used the old guide months ago and was getting the “Update in progress” block of text on almost every ignition on sequence. Then i saw this new and updated guide, downgraded from 19274 to 19200 i think, reformatted and followed the new guide and…no “update in progress” text anymore…WOOOO
    I do however want to update the APIM firmware and i will be using forscan however, the optional guide on updating APIM is confusing as f**k to me.
    I have the needed adapter cable and experimental build but its just i’m now at a loss of what i need to download, steps to take etc…
    Could someone with knowledge on this guide me through..I WILL NOT HOLD YOU RESPONSBLE FOR ANY DAMAGES OR LOSS OF FUNCTION TO MY SYSTEM.
    Thank you

    I have a 2017 Ford Focus Titanium X

    Reply
    • After some internet research I still do not have any idea about how to update the APIM. If you find something, please let me know because I would really like the calm mode and radio images.

      Reply
      • I’m also wanting to upgrade the apim software. I believe it requires hardware that you have to purchase. From what I can tell it requires a usb to odb connector and some software called forscan.

        Reply
        • yeah i can find that, I have buyd a cheap obd to usb connector and downloaded forscan. I’m waiting till the adapter arives.

          Reply
        • But to be fair, I do not think we will be able to update the firmware on short-term. There is a beta program running on Forscan and if you ask for the files they will send it, but it seems to be extremely unreliable. Furthermore it looks like people on Russian forum did manage to update the firmware.

          Reply
          • Russian forum use UCDS which is paid licensed software ahardware made in Russia. About 140eur . Due to the risks involved I don’t want to explain the Apim flashing progress via forscan. It’s bad enough when people cry saying there Apim software has broke because they fucked something up. I don’t want to be responsible (even though I’m not) for the low-level firmware on these devices (essentially a bios) being screwed up by using some pre release version of forscan, it also supposedly takes 30 minutes plus with forscan UCDS can do it in seconds. With that slow of a flash many things that are unexpected can happen.

            That said I will give a hint. There is discussion on flashing via forscan on the fordownersclub in the “sites discussing this guide” section.

          • richard brachwitz
            29th January 2020 12:09 pm

            Forscan is still in expermental stage and NOT stable .

    • I’m guessing you are the guy on the ford owners club forum?

      Reply
    • This is the information that comes with the experimental forscan build… No link provided. But it’s on the discord server.

      This function is in testing stage. There are problems, known ones and may be not known ones. Please note you use it “AS IS”. In no event shall FORScan team be liable for any direct or indirect damage, caused by use of this function. We strongly recommend to foresee an option to recover “bricked” module with another equipment (like IDS).

      Short instruction:

      The function is called “Module firmware update” and available in Configuration and Programming section. Content
      consists of 2 columns: current assembly/calibration and available for programming. All the firmware files that included into
      the assembly are displayed.

      There are 2 filter checkbox on the top (enabled by default):
      Only official branch – only firmware from official branch, this is what available in IDS. If this filter box is unchecked, all
      possible builds will be displayed, but only compatible with current hardware
      Only newer than current – this shows only builds that are newer than current. If you need older ones, uncheck this box.

      Every firmware file has status indicator on the right:
      – green – file is ready for programming and will be programmed
      – yellow – the file will not participate in programming
      – red – file is required but missing or damaged

      There 2 options at the bottom:

      – Force program unchanged firmware – if some file in the new calibration level is not changed, FORScan will not write it. This option changes the behaviour and all files will be rewritten.

      – Switch *ALL* modules to programming mode (silence on buses) – in this mode FORScan will switch all modules on both buses to programming mode, to make them “silent”. Unfortunately, this function properly works only on J2534 adapters with MS-CAN support. ELM327 kind of adapters and J2534 Passthru without MS-CAN can implement it partially (on current bus only) due to adapter limitations. This may cause serious panic in some modules. So it is recommended to use this option ONLY if there is no other way to program a module.

      There are 2 buttons on the bottom:
      – Download – download missing files from Internet ( Motorcraft site)
      – Program! – start the programming process

      It has to be counted that not all of firmware files are available on Motorcraft site (only those that allowed
      for dealership).

      Known problems:

      – It is not recommended to use china ELM327, as it is impossible to guarantee stable work in there. ELM327 Adapters that proved their ability to program firmware:
      — ELS27 – original (clone may hang after 30-40 minutes of work)
      — OBDLink SX (doesn’t support MS-CAN, so may need to be modified for it)
      — VINT-TT55502 USB (marked as Ford/Mazda/FORScan compatible, with HS/MS CAN switch)
      — VeePeak USB (marked as Ford/Mazda/FORScan compatible, with HS/MS CAN switch)

      – We do not recommend to program power steering modules yet. This requires special procedure. Current implemenation bricks Mondeo 4 PSCM

      – We do not recommend to program modules that have ECU Configuration * parts in their firmware, FORScan may not offer right file

      FORScan shows summarized firmware size and estimated programming time in the warning dialog before start
      programming. We recommend to pay attetion to these numbers, as programming time may be very significant (several hours).
      Time estimate for J2534 adapters may be very inexact yet.

      After the firmware update modules usually throw U2100 DTC. The following sequence of actions is enough to clear it:
      – Run Module configuration programmin (As Built format) and load *AB factory configuration in there. Please prepare it
      advance (download for Motorcraft site by VIN), as current version cannot download it in automated mode yet.
      – write All (all blocks!) to the module. If configuration isn’t changed change, FORScan will ask to confirm force write,
      please confirm it.

      After first successful connect to vehicle FORScan will create vehicle profile. We recommend to backup profiles, as they may be helpful in case of restoring.

      What we would like to get in case of problems:
      – short report about the problem
      – FORScan debug information (FORScan.log and dump.bin)
      – user logs (content of Log tab in the section Configuration and Programming).

      Regards,
      FORScan Team

      Reply
  • Was there some sort of method between the old method and new that no longer available where you had to load the USA maps and voice after loading 3.4? This is what i was following. 3.4 loaded easily, but having trouble getting the maps to load.

    Reply
    • yes, using the withnav file in step 2 will work fine though

      Due to a missing na maps license we can’t install Na maps the same as EU maps, therefore repeat the process from the start (downgrade if on 19274) and use the withnav file.

      Reply
  • Any clue where i can find 3.4 latest update for India location

    Reply
  • Omran Alabbadi
    27th January 2020 3:03 pm

    https://uploads.disquscdn.com/images/5f209a73aa9923f70e921b2c4e7a293335200b806ece767118cca9c09b9d3a88.jpg

    after upgrade to 3.4 19274, the screen became smaller and the touch is not working.

    i tried to re-use USB 1 to format the system again,, but it’s not working.

    any suggestion ??

    I used the below reformat.Ist for upgrading:

    APPS=5U5T-14G381-DJ_1571084015000.TAR.GZ
    VOICE=5U5T-14G391-CB_133518.tar.gz
    VOICE_NAV=4U5T-14G422-CAC_1542757383000.TAR.GZ
    GRACENOTES=4U5T-14G423-FA_123698.tar.gz
    MAP_LICENSE=4U5T-14G424-CA_1547147747000.TAR.GZ
    MAP=4U5T-14G421-FAF_1564054074000.TAR.GZ
    MAP=4U5T-14G421-FAB.tar.gz

    Thanks,

    Reply
  • Vardenis Pavardenis
    27th January 2020 8:21 pm

    Hi,

    Q: I have Ford Fusion 2017 from US but I am in EU – do I need to use American files or EU as I live in EU? What is the difference between them?

    Thanks

    Reply
    • Navigation or not navigation? if it’s not navigation then the only difference is supported languages, US = canada, american, mexican / EU = German, Dutch, British, French

      Reply
      • Vardenis Pavardenis
        27th January 2020 9:35 pm

        No navigation. Are there any differences in Radio i.e. no Sirius (or how it is called) and EU bands enabled in EU files? Or as you mentioned the only difference is in supported languages?

        Thanks 🙂

        Reply
  • can i just update maps on my sync 3 3.0 2013 ford taurus

    Reply
  • Successful did the Update from 3.0.19205 to 3.4.19101 with the new method from 25/01/2020 on my 2017 Ford Focus ST Turnier. Location: Germany

    Reply
  • Successful did the Update from 3.0.19205 to 3.4.19101 with the new method from 25/01/2020 on my 2017 Ford Focus ST Turnier. Location: Germany

    Reply
  • My Ford Explorer 2018 is a US model with NAV. I know the APIM has only 32Gb and the EU APIM 64Gb.
    Can I install complete EU NAV version with EU maps by leaving out the parts of Europe I won’t travel to by editing the autoinstall.lst file (and thus saving space)?

    Reply
  • I followed the guide on on how to make sure your USB is MBR and not GPT. When i deleted the volume it completely made my USB unusable and would not even recognize it. I had to google how to restore it and now it appears to be back to normal. I also googled how to check if my USB was MBR but when i did that it said to click on the volume tab which none of my USBs have? They are older 5+ year USB devices. Should they be MBR and not GPT? The 16gb is a ScanDisk and the 1GB is a PNY USB. Thanks!

    Reply

Leave a Reply

Menu