This is a supplement to my “Ford Sync3 v3.0 ‘The installation has run out of space’ Upgrade Failure or IT Guy Buys a Truck” post which discusses my experience getting around this problem. It covers my overall take on the cause of the failure and the syntax of these upgrades.
Understand, it is based solely on my observations and experience as an IT Engineer. I have no information that supports this from Ford. This information was originally posted on reddit.
The cause appears to be simply installing too many ‘tar’ files at the same time. Ford has apparently dealt with this partially by breaking the installation into two parts (groups) themselves. But, it is not enough to work on all vehicles in all situations.
The installation is controlled by the ‘autoinstall.lst’ file which will vary with each version and vehicle configuration. Here is the one I had for the v3.0 upgrade.
; 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
The syntax appears to be as follows:
- [name] entries identify install groups. [SYNCGen3.0_3.0.19205_PRODUCT] and [SYNCGen3.0_ALL] are individual installation groups/sections (as I said above Ford has already made this into two separate installations). Also, the actual name appears to be informational but does not appear to be important.
- ‘Items’ are individual installs. The name here does appear to be important and should be preserved.
- ‘Opens’ point to the ‘tar’ file for the ‘Items’.
- ‘Items’ and ‘Opens’ are identified and bound together with ordinal numbers.
- ‘Items’ ordinal entries must be in numeric order.
- ‘Options’ tell the installer what to do with the ‘Items’ in the group.
- Install groups begin with a ‘[name]’ entry and end with an ‘Options’ entry.
- Any line starting with a ‘;’ (semicolon) is a comment and ignored by the installer.
Knowing this we can manipulate this file to accomplish what we need to get around the error. In my case I needed to separate the ‘JR3T-14G381-AS’ and ‘JR3T-14G423-BB’ items into individual install groups and then it worked.
Here is the above file with the second group broken into individual ‘tar’ installs:
; 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 ;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
Each install starts with a [name] entry and ends with an Options = entry. All lines start with a semicolon and are comments. To use this start at the top and remove the semicolon’s for the first group. Save the file to the USB, start the vehicle, plug in the USB in and let it run till it is finished. Take the USB out, stop the engine, and wait 5 minutes. While you are waiting, replace the semicolons on the group you just did and remove them from the next group. Save the file. When the 5 minutes are up, start the vehicle ……. and so on till you have done all the groups to the end of the file. If the problem was really space, it may now have worked. It won’t take as long as you might think because each step will run quickly compared to the original install that does it all at once.
This is not a generic fix for all situations but the approach is generic. Figure out where the error is, separate those ‘tar’ installs, and do them individually. Preserve the installation order but allow each installation to complete and clean up to get the space back before you do the next one.
Note: specifics will only work if you have exactly the same situation; same version, same vehicle, same vehicle configuration, same Sync3 unit. But if you use the overall approach, it should work in situations where you are getting an “Out Of Space” error.
I hope this helps.