Tutorial: Sync 3.4 NON-NAV APIM: Failure to Update to Newer Version Sync 3.4

This tutorial covers the scenario where a NON-NAV APIM with Sync 3.2/3.3/3.4 installed and will not update to a newer version of Sync 3.4. This is not the same as upgrading from previous versions of Sync (3.0) to Sync 3.4.

NOTE:
Use the Syn3 Updater application for upgrading your Sync 3.0 system to Sync 3.2/3.3/3.4.

NOTE:
All the files needed can be found at Software Database - CyanLabs.

It is assumed that you have tried to upgrade your NON-NAV APIM with Sync 3.4 installed to a newer version using the SYN3 Updater application above and the procedure is failing. This can be due to several reasons, such as inadequate storage, defective USB, APIM issues (Check DTC’s), or other errors.

Read this document fully before starting any actions. It is your responsibility to follow the instructions as outlined below.

Determining the Issue
Determine if the APIM issue is due to storage limitations or other issues. Run the APIM Interrogator Utility to determine the specifics of your Sync unit installed in your vehicle. If there is less than 1.5 GB of free space, you will need to delete files in order to update your Sync unit. This utility will output an xml file that contains information about the APIM including the storage, asbuilt, serial number, part numbers, as well as strategy and calibration versions. The xml file also contains information on installed map and NAV_Voice files, if applicable to the APIM. The xml file can be opened in your browser or viewed thru the Syn3 Updater.

Once you have opened the xml file, scroll to the bottom of the file to see your storage. Below are examples of NON-NAV 8GB APIM units with Sync 3.4 installed. (These are NON NA or MNC/MNT units).

NON-NAV 8GB APIM with inadequate available storage for upgrade. Available storage is 938MB.
<d2p1:PartitionHealth type="/fs/Nuance/" total=β€œ1.9G” available=β€œ8.5M”/>
<d2p1:PartitionHealth type="/fs/rwdata/" total=β€œ1.2G” available=β€œ1009M”/>
<d2p1:PartitionHealth type="/fs/rwdata/quip/" total=β€œ35M” available=β€œ35M”/>
<d2p1:PartitionHealth type="/fs/rwdata/quip/" total=β€œ90M” available=β€œ90M”/>
<d2p1:PartitionHealth type="/fs/mp/" total=β€œ1.4G” available=β€œ146M”/>
<d2p1:PartitionHealth type="/fs/mp/resources" total=β€œ74M” available=β€œ380K”/>
<d2p1:PartitionHealth type="/fs/images/" total=β€œ3.0G” available=β€œ938M”/>

NON-NAV 8GB APIM with inadequate free storage available for upgrade with Gracenotes. Available storage is 403MB.
<d2p1:PartitionHealth type="/fs/Nuance/" total=β€œ1.3G” available=β€œ58M”/>
<d2p1:PartitionHealth type="/fs/Nuance/grace" total=β€œ1.1G” available=β€œ63M”/>
<d2p1:PartitionHealth type="/fs/rwdata/" total=β€œ1.2G” available=β€œ991M”/>
<d2p1:PartitionHealth type="/fs/rwdata/quip/" total=β€œ35M” available=β€œ25M”/>
<d2p1:PartitionHealth type="/fs/rwdata/quip/" total=β€œ90M” available=β€œ88M”/>
<d2p1:PartitionHealth type="/fs/mp/" total=β€œ1.4G” available=β€œ144M”/>
<d2p1:PartitionHealth type="/fs/images/" total=β€œ3.0G” available=β€œ403M”/>

NON-NAV 8GB APIM with inadequate free storage available for upgrade with MAP partition. You must downgrade and use the reformat tool to remove the MAP partition. Available storage is only 57MB.
<d2p1:PartitionHealth available=β€œ572K” total=β€œ1.0G” type="/fs/sd/MAP/"/>
<d2p1:PartitionHealth available=β€œ54M” total=β€œ1.7G” type="/fs/Nuance/"/>
<d2p1:PartitionHealth available=β€œ1006M” total=β€œ1.2G” type="/fs/rwdata/"/>
<d2p1:PartitionHealth available=β€œ35M” total=β€œ35M” type="/fs/rwdata/quip/"/>
<d2p1:PartitionHealth available=β€œ90M” total=β€œ90M” type="/fs/rwdata/quip/"/>
<d2p1:PartitionHealth available=β€œ142M” total=β€œ1.4G” type="/fs/mp/"/>
<d2p1:PartitionHealth available=β€œ380K” total=β€œ74M” type="/fs/mp/resources"/>
<d2p1:PartitionHealth available=β€œ57M” total=β€œ3.0G” type="/fs/images/"/>

In any case, the bottom line is the amount of storage free in β€œ/fs/images/”. As stated above, if there is less than 1.5 GB of free space, you will need to delete files to update your Sync unit.

Deleting Files
If it is determined above that the issue is inadequate storage available for the updates, there are several files that can be deleted to create free space. This is all about increasing the available storage in β€œ/fs/images/”.

The first set of files to delete are Gracenotes. These are stored in β€œ/fs/Nuance/grace”. Follow the procedure in the Removal of Gracenotes tutorial. Once Gracenotes are removed, run the APIM Interrogator Utility and check the available storage at β€œ/fs/images/”. If there is less than 1.5 GB of free space, you will need to free more storage space. If there is more than 1.5GB of free space available, you can proceed with the upgrade directly to the latest version of Sync 3.4.

NOTE:
Due to the increased storage use of Sync 3.4, it may not be possible to re-install Gracenotes in some situations because the combination of the Sync app and regional voice files may not leave enough available free storage. In these situations including Gracenotes in the Sync 3.4 update will cause the procedure to fail. NON-NAV units will generally not have the storage available to install Sync 3.4 app, voice, and Gracenotes, due to the increased size of the app over the Sync 3.2/3.3 versions.

EDIT: The newest version of Gracenotes (Late 2020) are now smaller in file size and will fit on a NON-NAV APIM with Sync versions 3.4 installed. Install Gracenotes last.

The second set of files to modify the application or system voice files. These are stored in β€œ/fs/Nuance/”. (If you have a NA or MNT APIM this step is not needed as a small voice file is already installed.)

The application voice files will be replaced temporarily with the NA (North American) version application voice files, which is a significantly smaller installation package and will free additional storage. Do not confuse this with the Navigation Voice files. The application voice files are the voice commands for the Sync system, not the Navigation system, which is also hosted on the Sync APIM platform. You can choose to keep the smaller voice file package or replace it with the proper regional version once you have enough free space to upgrade to the latest version of Sync 3.4.

NOTE:
The Syn3 Updater can be used to create a Small Voice Package Replacement USB in the Tools section.

To install the NA version of the application voice package, download 5U5T-14G391-CP_1626959995000.TAR.GZ. The file can be found in the APIM IVSU Database.

Follow the instructions below:

  1. Create a USB drive (format as EXFAT) with a SyncMyRide folder.
  2. Copy the file downloaded above into the SyncMyRide folder.
  3. In the root of the USB is the autoinstall.lst and DONTINDX.MSA files which you can obtain from any upgrade you previously performed.
  4. You will need to edit the autoinstall.lst file so it looks like the example below but replace β€˜filename’ with the actual file name you downloaded.

[SYNCGen3.0_ALL]
Item1 = 5U5T-14G391-CP_1626959995000.TAR.GZ
Open1 = SyncMyRide\5U5T-14G391-CP_1626959995000.TAR.GZ
Options = Autoinstall

  1. Insert USB in vehicle and wait for the installation to complete. You should see a message indicating completion.
  2. Remove the USB drive and reboot the APIM.

NOTE:
Rebooting the APIM after loading the new voice file is mandatory, or the system will not delete the old voice.img and install files and rename voice_new.img to voice.img.

Once the voice file is installed, run the APIM Interrogator Utility and check the available storage at β€œ/fs/images/”. There should be adequate storage space available as in the example below.

NON-NAV 8GB APIM with NA version 391 Application Voice file installed. Notice the size of the β€œ/fs/Nuance/” partition is smaller and storage has been allocated to available space in β€œ/fs/images/”.
<d2p1:PartitionHealth type="/fs/Nuance/" total=β€œ465M” available=β€œ3.1M”/>
<d2p1:PartitionHealth type="/fs/rwdata/" total=β€œ1.2G” available=β€œ1003M”/>
<d2p1:PartitionHealth type="/fs/rwdata/quip/" total=β€œ35M” available=β€œ35M”/>
<d2p1:PartitionHealth type="/fs/rwdata/quip/" total=β€œ90M” available=β€œ90M”/>
<d2p1:PartitionHealth type="/fs/mp/" total=β€œ1.4G” available=β€œ146M”/>
<d2p1:PartitionHealth type="/fs/mp/resources" total=β€œ74M” available=β€œ380K”/>
<d2p1:PartitionHealth type="/fs/images/" total=β€œ3.0G” available=β€œ2.3G”/>

At this point, if there is adequate storage space available you can upgrade the unit to the latest Sync 3.4 version using the Syn3 Updater. If for some reason the upgrade fails, or there is still inadequate storage space available to upgrade directly to Sync 3.4, you can downgrade the unit to Sync 3.3.19052, and then upgrade the unit to the latest Sync 3.4 version via reformat. Sync 3.3.19052 is about half the size of Sync 3.4.

Set your current Sync version and select downgrade in the Syn3 Updater and choose NON-NAV, or NO MAPS.

NOTE:
If you are unfortunate enough to have a MAP partition on the APIM, you must downgrade to 3.3.19052 and then use the reformat tool to install the latest Sync 3.4 version with voice. Choose downgrade in the Syn3 Updater and choose NON-NAV, or NO MAPS.

Manual Downgrade Option

NOTE:
You can use the Syn3 Updater application for downgrading your Sync 3 system.

To manually downgrade the unit to Sync 3.3.19052, download 4U5T-14G381-AN_1552583626000.TAR.GZ. The file can be found in the APIM IVSU Database.

Follow the instructions below:

  1. Create a USB drive (format as EXFAT) with a SyncMyRide folder.
  2. Copy the file downloaded above into the SyncMyRide folder.
  3. In the root of the USB is the autoinstall.lst and DONTINDX.MSA files which you can obtain from any upgrade you previously performed.
  4. You will need to edit the autoinstall.lst file so it looks like the example below:

[SYNCGen3.0_ALL]
Item1 = 4U5T-14G381-AN_1552583626000.TAR.GZ
Open1 = SyncMyRide\4U5T-14G381-AN_1552583626000.TAR.GZ
Options = AutoInstall

  1. Insert USB in vehicle and wait for the installation to complete. You should see a message indicating completion.
  2. Remove the USB drive and reboot the APIM.

This should force a downgrade to 3.3.19052. You will be able to upgrade using the Syn3 Updater application from 3.3.19052 to the latest version of Sync 3.4, choose NON-NAV, or NO MAPS.

NOTE:
Use the Syn3 Updater application for updating your Sync 3 system.

4 Likes
Sync 3.0 to sync 3.4
Sync 3 stuck at "Updating system software"
Sync 3.4.20282 - Feedback & Issues
Sync 3.4.20237 - Feedback & Issues
Sync 3.4.20351 Update Failing With MEM ERR 03
Installation Failed Error Code PKG_ERR04
Common Issues Documentation
Installation process dosent begin
Issue causing Not being able to update from 3.3 build 19052 to 3.4
Change 3.4 build to newer version
Downloading Sync 3 update with Nav in a car without Nav.
Problem updating from 19274 to a higher version
I can't update from 3.4.19274 to 3.4.20
Sync 3.4.20351 - Feedback & Issues
Red screen error while trying to upgrade
Issue with "Updating Software" and nothing happening
Sync3 v3.2 18275 update to v3.4 21098 issue
software update
Sync3 and wireless carplay
MEM size does not change after removal of GraceNote
MEM size does not change after removal of GraceNote
Need help, update 3.4.20021 to newer build
Issue with upgrade 3.4.19101 NO-NAV to latest 3.4.21194
2018 Ford Edge Titanium 3.4 issues
Common Issues Documentation
Ford Ka 2019 - Updated from 3.0 to 3.4 without Gracenotes
Ford Ka 2019 - Updated from 3.0 to 3.4 without Gracenotes
Hello good afternoon I have this problem with my update
Sync 3.4.20351 - Feedback & Issues
Sync 3.4.21194 - Feedback & Issues
Are my updates OK?
Updated sync 3.4 build 20021 to new build version fail
Strange error. Update/Downgrade not working
Common Issues Documentation
upgrade Sync 3.4
Upgrading SYNC 3.4.20196 to 3.4.21020 taking over 2 hours?
Sync 3.4 downgrade to 3.3 Error