Scoobmaster

Hi all - long time computer professional / IT guy here.

I just made an observation and wondered if any of you in the tech discussion of SYNC have noticed this. I own a 2016 F150 XLT and a 2016 Fiesta ST. I updated SYNC on the F150 last week (by downloading the JR3T-14G381-AL.zip file from the Ford owner website links for my truck) and using a USB stick - went without a hitch. I am getting ready to do the Fiesta, and for the heck of it i went into the Ford owner website, choose the Fiesta ST, then followed the link to download the SYNC 3.0 update. The file appeared to be the same one (JR3T-14G381-AL.zip) that I downloaded for the truck (no surprise there - both the F150 and the Fiesta have Nav and should be the same save for a slightly smaller touch screen on the Fiesta).

Here is where something looked odd... I still had the file I downloaded for the truck last week. I *thought* that they should be identical since the had the same filename, but the version I just downloaded for the Fiesta was slightly smaller in size. I was curious and opened them both up - The F150 file had 8 tarballs, while the Fiesta only had 7. The missing file from the Fiesta downloaded zip file is HB5T-14G386-AHH.tar.gz (8023 Kb). It isn't accidentally missing - the autoinstall.lst file does not include it in its list either in that package.

Anyone know what that 8 MB file (HB5T-14G386-AHH.tar.gz) contains? I wonder if it is something specific to the F150 but not in the Fiesta? Why would they have two identical filenames with the same version numbers that are clearly NOT identical?

** EDIT **
So I did some more back reading in this thread and discovered that in a post in another SYNC thread Airborne_Ape posted (and credited to an F150 owner by the name of Paul) that the file is a script that does some version checking and may prevent some owners that used a beta build from upgrading. he recommended removing the file if that was the case - well it appears that Ford removed it.

graym

Ok totally confused...downloaded the file from ford....now what....tried everything does the car have to be running? only AC mode?

bcb97

I'm still getting the MEM_ERR03 installation failed message even when I change my auto install file to what you first have. Do I only need to have the 2 folders the autoinstall file references in the SyncMyRide folder or is it ok to leave the 7 files there?

Acool

The file name is a container based on the OS version. So Nav and Non-Nav packages have the same file name, even though they are different packages. 14G381 is the main OS file. It's just inconvenient that they used that to name the package file too, which again, also contains the OS file 14G381 inside. Confused yet? To make matters worse, the package can be made on the fly depending on your vehicle VIN. For whatever reason Ford decided to include patches that are done based on your starting version, so there could be many different versions of the same package file name. The problem with this is Ford doesn't always know what version you're starting with. Many people do manual installs or don't report an install back to Ford. The AHH file has all (or maybe most) of the patches (8 total IIRC?). I haven't looked too in depth but I believe 3.0 removes the patches anyway. If you install a package with AHH, it is supposed to do a version check and then decide which if any of the 8? patches to install. If yours doesn't need the AHH file, installing with AHH in the package shouldn't make a difference bc it should skip it if it doesn't need it when it runs the version check script. The individual file in the AHH patches is a binary called APP_SUM that handles the software upgrade/installation process. The patch replaces the stock version of APP_SUM that is contained in 14G381 OS file. You can run a compare of the files to see what the differences are. In the 2.3 version, IIRC, one person found two different patches that looked identical save a spelling error in one. So what was the purpose? Dunno. Many people went to 3.0 before the official version was released, with no issues and without messing with patches. You can decide what route to go, but don't assume the Ford route is the correct one

Acool

It should be JR3T-14G391-CD (not BD) and you need to get that file from a nav package. BD is non-nav voice and what is causing the error. You need to install a NAV voice package to prep it.

You can use ANY Nav voice package from any install version, just get the xxxx-14G391-xx file from whatever version of a Nav package you have, and modify the autoinstall accordingly.

PSM 6.4

Heck yeah, thank you.

Got stuck on updating for 2+ hours and no activity with drive formatted exFAT.

Reformatted drive with the above recommendation (FAT32) and boom done in 15 mins.

17 NAV APIM.

Why does ford make everything so complicated lol.

bcb97

Thanks, I'll try that. I'm in the process of downloading the CD file. So to be clear, I just need to replace the BD with the CD file, change the autoinstall code to open the CD file, and it should work? Again thank you for helping with the MEM_ERR03 problem.

Scoobmaster

OK - I follow you. From a software patch perspective, it doesn't make sense to me to release package files with the same filename and version number and contain different content (bad practice). Heck - it totally violates the practice of using CRC checksum to be sure your download did not get corrupted. Anyway, I appreciate the post. I think I will use the original package I downloaded for my F150 (the one that does contain the AHH patch) to update my wife's Fiesta ST.

Ford4fun

Thank you very much to Acool and fordanator, I finally updated to 3.0 (18025) and avoided the 'MEM_ERR03'!!

Are we just waiting on an update from Waze now? Any date on that? Will Waze be usable in Carplay or just Applink?

Thanks all!

flyinghappy

You are waiting on an update from Waze. It will only be useable on Applink(or Android Auto ), not Carplay. I think Waze had thrown a mid April date out there, but can't remember for sure.