This is not strictly IT but then again it is so I am posting it here. I recently purchased a 2016 Ford and found I needed to update the Sync3 software to use “CarPlay” with my phone. It sounds easy but turned out not to be.
Ford provides install instructions and the ‘tar’ files for the upgrade via a download on their web site. You need to create an account and register your vehicle to get the software. Then their instructions are basically to:
- Put the extracted files on a exFAT formatted USB
- Start your vehicle and with the vehicle running plug the USB
The install should start automatically. When it is complete you remove the USB, shut the vehicle off, wait 5 minutes and restart it. Simple process but my upgrade failed with the error:
The installation has run out of space or does not work with this version.
Also, when it restarted, the version still showed as 1.0 and the “Gracenote” version was now blank.
I tried it multiple times with multiple USB drives and could not get around the error. Sometimes the install would not generate the error but just hang with the “Updating” message on the screen and never end. Sometimes I got the error after giving up and restarting the vehicle. The install should take 30 minutes max but I waited as long as 2 hours before I gave up. After burning a quarter tank of gas, I called Ford Support but they had no clue.
Looking on the Internet I did see references to running the install in two stages. This was for v2.2, not v3.0 but I decided to try it anyway. In the installation download is an ‘.lst’ file with the install instructions and a folder “SyncMyRide” with seven ‘tar’ files. The ‘lst’ file for my v3.0 upgrade was:
; SYNC3 Consumer Assembly Upgrade - Release 3.0.21 - Only for My16 NonNav/NonEU assemblies. [SYNCGen3.0_3.0.19205_PRODUCT] Item1 = HB5T-14G386-THA Open1 = SyncMyRide\HB5T-14G386-THA.tar.gz Item2 = HB5T-14G386-TBB Open2 = SyncMyRide\HB5T-14G386-TBB.tar.gz Item3 = GB5T-14G386-SC Open3 = SyncMyRide\GB5T-14G386-SC.tar.gz Item4 = JR3T-14G391-BF Open4 = SyncMyRide\JR3T-14G391-BF.tar.gz Options = AutoInstall [SYNCGen3.0_ALL] Item1 = JR3T-14G381-AS Open1 = SyncMyRide\JR3T-14G381-AS.tar.gz Item2 = JR3T-14G423-BB Open2 = SyncMyRide\JR3T-14G423-BB.tar.gz Item3 = GB5T-14G386-AB Open3 = SyncMyRide\GB5T-14G386-AB.tar.gz Options = Delay,Include,Transaction
As you can see it is already divided into two separate installs — [SYNCGen3.0_3.0.19205_PRODUCT] and [SYNCGen3.0_ALL]. When I rem’d out the second install the first ran correctly, prompted me to remove the USB and restart the vehicle. When it restarted, the version still showed as 1.0 and the ‘Gracenote” version was still blank. But I was not getting an error. Here is the first half ‘lst’ file:
; SYNC3 Consumer Assembly Upgrade - Release 3.0.21 - Only for My16 NonNav/NonEU assemblies. [SYNCGen3.0_3.0.19205_PRODUCT] Item1 = HB5T-14G386-THA Open1 = SyncMyRide\HB5T-14G386-THA.tar.gz Item2 = HB5T-14G386-TBB Open2 = SyncMyRide\HB5T-14G386-TBB.tar.gz Item3 = GB5T-14G386-SC Open3 = SyncMyRide\GB5T-14G386-SC.tar.gz Item4 = JR3T-14G391-BF Open4 = SyncMyRide\JR3T-14G391-BF.tar.gz Options = AutoInstall ;[SYNCGen3.0_ALL] ;Item1 = JR3T-14G381-AS ;Open1 = SyncMyRide\JR3T-14G381-AS.tar.gz ;Item2 = JR3T-14G423-BB ;Open2 = SyncMyRide\JR3T-14G423-BB.tar.gz ;Item3 = GB5T-14G386-AB ;Open3 = SyncMyRide\GB5T-14G386-AB.tar.gz ;Options = Delay,Include,Transaction
I then ran the second half by reversing the rem’d out lines. This failed with the same error as the entire install. The error was in the second half! So I changed the file to divide the second half install into 3 separate parts.
; SYNC3 Consumer Assembly Upgrade - Release 3.0.21 - Only for My16 NonNav/NonEU assemblies. ;[SYNCGen3.0_3.0.19205_PRODUCT] ;Item1 = HB5T-14G386-THA ;Open1 = SyncMyRide\HB5T-14G386-THA.tar.gz ;Item2 = HB5T-14G386-TBB ;Open2 = SyncMyRide\HB5T-14G386-TBB.tar.gz ;Item3 = GB5T-14G386-SC ;Open3 = SyncMyRide\GB5T-14G386-SC.tar.gz ;Item4 = JR3T-14G391-BF ;Open4 = SyncMyRide\JR3T-14G391-BF.tar.gz ;Options = AutoInstall ;[SYNCGen3.0_ALL] ;Item1 = JR3T-14G381-AS ;Open1 = SyncMyRide\JR3T-14G381-AS.tar.gz ;Options = AutoInstall ;[SYNCGen3.0_ALL] ;Item1 = JR3T-14G423-BB ;Open1 = SyncMyRide\JR3T-14G423-BB.tar.gz ;Options = AutoInstall ;[SYNCGen3.0_ALL] ;Item1 = GB5T-14G386-AB ;Open1 = SyncMyRide\GB5T-14G386-AB.tar.gz ;Options = Delay,Include,Transaction
Note: I had to add a header to each part, an ‘options = AutoInstall’ line to the first two, and change the ‘Item’ and ‘Open’ lines for each to ‘1’ to reflect the first, and only, item in each.
I then un-rem’d each part to do the JR3T-14G381-AS and JR3T-14G423-BB installs one at a time. My goal was to determine which part was failing. But that is not what happened.
The AS install worked and prompted me to restart the vehicle. I waited 5 minutes (this may be folklore but I did it anyway) and when I restarted it showed version 3.0! But, the “Gracenote” version was still blank. A partial victory. After the BB install it did not request a restart but I did it anyway. The “Gracenote” version now showed as 188.8.131.520 (GL-0011.) At this point I had an upgraded system.
I then ran the GB5T-14G386-AB install and it generated the ‘.xml’ file in the “SyncMyRide” folder that you upload to Ford to verify the installation. I uploaded the file and Ford accepted it.
Why did I need to do this? I am not sure. It was apparently running out of space trying to do the AS and BB installations at one time. An artifact left behind by a previous install? Restricted space due to compromised hardware? Differences in actual physical memory size from different suppliers of the APIM module? The only other thing I can think of is that because I also have Sirius Radio and that used a little space in the Sync3 system. A non-Sirius, non-Nav system would work? Maybe, but I have no way to test the theory.
Whatever it was, if you have this issue on a 2016-1018 Ford Sync3 system upgrade, this approach may work for you. More detailed information on this can be found in another of my posts ”Fixing Sync3 Upgrade ‘Out Of Space’ Errors”.
If you are doing this on a MAC, you may also want to read the comment by ‘Themi Mintzas’ about extracting the download and file name changes on the ”Fixing Sync3 Upgrade ‘Out Of Space’ Errors” post referenced above.