NEW SYNC 3.0 Build 20204 Nav Android Auto/Apple Carplay

[TexasRebel]

No. I got a legit package.
I did the nav-voice install trick and it worked just fine.

Although owner.ford.com now says my car is up-to-date, but has no mention of the -AM update.

My car does say 18093_PRODUCT

Sponsored

 

[Danman]

Downloaded the file and updated last night. Took about 20-25 minutes.

 

[HizliBullet]

this is so unfair, the british ford gets this all in one page convenience and we dont

https://www.ford.co.uk/owner/resources-and-support/sync-bluetooth/update#/

https://www.ford.co.uk/content/dam/...support/docs/SYNC_3_USB_MAPS-Update-Guide.pdf

 

[2016 GT/CS Laila]

For those that are having an issue with Build 18093, I tried to update using the dash USB port and it failed multiple times with MEMERR_03. Before hacking up the autoinstall.lst file, I decided to try the USB in the center console. It worked on the first try . I did shut everything down (lights, AC, radio, etc.) and made sure nothing was plugged in even my cable for my phone. If you haven't tried this, it is something to consider before going through the long process of multi installs.

 

[EcoBoomer]

Updating 18093 FOR MAC USERS

If you are having trouble getting your Mac-formatted update to 18093 to work, there are a couple of things to watch out for:

1. The native Archive Utility.app that is the default in my MacBook unpacks JR3T-14G381-AM.zip in a rather funky way:
   
   SYNC will not recognize it and throw an error screen. I tried a second party app - The Unarchiver.app and it unpacked the zip file normally and worked fine:
   
   Curiously, the Ford site’s step by step instructions assumes you use a non-native app (Stuffit) in it’s graphic and makes no warning about the default app problem:
   

2. The install will work fine with either a FAT 32 or exFAT formatted drive by OS X, BUT you must make sure that you set it to the proper type. Mine defaulted to GUID Partition Map and, giving it no thought, used it.

The result was that SYNC never recognized the drive. It MUST be set to Master Boot Record.

Once you've watched out for these quirks, the drive should work no differently than a Windows formatted drive.

And, if you have a non-nav Sync like I do, it should take you to the next step- battling the MEM_ERR03 problem. (Which BTW, has NOTHING to do with the drive you are using.)

 

[RawisTheGameHhH]

first time i have seen the auto update work. however after 20 minutes the progress bar didnt move

 

[2016 GT/CS Laila]

first time i have seen the auto update work. however after 20 minutes the progress bar didnt move

They only time that the auto download has worked for me was a previous version on my 16 F150. Just did the download for the new software, with nav it was only about 441 MB. All the others were 1.1 GB (Mustang, Edge, and Focus).

 

[jefffrot]

Trying to update to 3.0 from 2.2 on my non nav 2016 GT but also getting the mem_err003 error. First tried 3.0 18025 and then tried 3.0 18093 but no had no luck with either. Had no issues upgrading to 2.2 a little over a year ago. Using same USB drive as before. What is my next option?

 

[RawisTheGameHhH]

They only time that the auto download has worked for me was a previous version on my 16 F150. Just did the download for the new software, with nav it was only about 441 MB. All the others were 1.1 GB (Mustang, Edge, and Focus).

and it finished on its own while the car was off apparently, gracenotes version is blank however

 

[catchthecarp]

Non-Nav Sync 3 owner here who was at Build 18025. Downloaded the 18093 update from Ford today and received MEM_ERROR03 during the install. Downloaded the MEM-ERR03 fix and it installed successfully. Ran the 18093 update again which installed with no errors. The About screen now reads Build 18093 but the Gracenote version remained unchanged at .1130. The updated pic posted on page 1 of this thread shows Gracenote at .1139. So what version should Gracenote be at after applying this update? I haven't notice any changes with Sync 3 after installing the update but it sure wasn't worth the effort.

 

[jefffrot]

Non-Nav Sync 3 owner here who was at Build 18025. Downloaded the 18093 update from Ford today and received MEM_ERROR03 during the install. Downloaded the MEM-ERR03 fix and it installed successfully. Ran the 18093 update again which installed with no errors. The About screen now reads Build 18093 but the Gracenote version remained unchanged at .1130. The updated pic posted on page 1 of this thread shows Gracenote at .1139. So what version should Gracenote be at after applying this update? I haven't notice any changes with Sync 3 after installing the update but it sure wasn't worth the effort.

Where did you get this MEM-ERR03 fix you talk about?

 

[catchthecarp]

There is a link in the 1st post of this thread back on page 1, it is updated each time a new release comes out. I believe the update installed correctly, it created the .XML file that is used to send back to Ford.

 

[HizliBullet]

Where did you get this MEM-ERR03 fix you talk about?

its on first page, many non nav users ran into that issue so I added the link

 

[EcoBoomer]

Trying to update to 3.0 from 2.2 on my non nav 2016 GT but also getting the mem_err003 error. First tried 3.0 18025 and then tried 3.0 18093 but no had no luck with either. Had no issues upgrading to 2.2 a little over a year ago. Using same USB drive as before. What is my next option?

I was updating from 18025 to 18093 and continued to get the same error message regardless of what I tried (disconnect battery cable to dump anything resident in memory, turning off blutooth etc). I read on other Ford sites and the problem has to do with the limited memory available in the non-nav apim. (As is often stated - it has nothing to do with your flash drive). Some had success rearranging the order of the file installations but I found that their order solution was the same order as the present download for the Mustang. It didn't work for me. Some did re-installs back to earlier versions (your 2.2 for example) but you are there and it isn't working for you. It's been determined that the install gets hung up on the 451.3MB and/or 772.1MB files; there isn't enough memory to unpack them both. Their workaround was to delete some of the files, do the install, then delete the other files, while restoring the first deleted files, and do the install again. None of the directions I found were done on 18093, this most recent one, and there are a different number of files with different names across the models, so really nothing to go by.

SO.... Fools rush in where angels fear to tread.

Here's what I did, I started with removing only one file at a time and it seems to have worked flawlessly.

1. Unpack the JR3T-14G381-AM.zip to your desktop and copy the contents of the JR3T-14G381-AM folder to your flash drive. Work only from your flash drive from this point on.
2. Delete the JR3T-14G423-BA.tar.gz file (772.1mb) from the SyncMyRide folder on your flash drive.
3. Open the autoinstall.lst with a text editor (TextEdit on a Mac or Notepad in Windows) on your flash and delete lines - Item3 and Open3.
4. Remove the spaces where Item3 andOpen3 resided and rename Item4 and Open4 to Item3 andOpen3. EVERYTHING ELSE SHOULD STAY AS IT IS.
5. Save the file with the same name - autoinstall.lst.

6. Take the flash to your car and do the install. It should update successfully and basically tell you that you are finished. But you are not. (I checked the Sync screen and it still showed 18025).
7. Take your flash back to your computer and do the same thing except you will copy the "BA" file from the SyncMyRide folder on your desktop to the same folder on the flash drive.
8. Now, delete the "AM" file - JR3T-14G381-AM.tar.gz (451.3mb) on your flash drive.
9. For simplicity sake, I copied the original autoinstall.lst from the desktop and overwrote the modified one on the flash drive and did steps 3,4, and 5 again, this time deleting Item2 and Open2 lines, removing spaces, and renaming Item3 and Open3 to 2, and Item/Open 4 to 3
10. Repeat step 6 and it SHOULD work for you (caveat emptor). I checked the Sync screen and it shows version 18093. I tested all the functions and everything seems to work fine. It even seems to be quicker - but that could be me wanting it to be so!

Godspeed!

 

[TexasRebel]

I was updating from 18025 to 18093 and continued to get the same error message regardless of what I tried (disconnect battery cable to dump anything resident in memory, turning off blutooth etc). I read on other Ford sites and the problem has to do with the limited memory available in the non-nav apim. (As is often stated - it has nothing to do with your flash drive). Some had success rearranging the order of the file installations but I found that their order solution was the same order as the present download for the Mustang. It didn't work for me. Some did re-installs back to earlier versions (your 2.2 for example) but you are there and it isn't working for you. It's been determined that the install gets hung up on the 451.3MB and/or 772.1MB files; there isn't enough memory to unpack them both. Their workaround was to delete some of the files, do the install, then delete the other files, while restoring the first deleted files, and do the install again. None of the directions I found were done on 18093, this most recent one, and there are a different number of files with different names across the models, so really nothing to go by.

SO.... Fools rush in where angels fear to tread.

Here's what I did, I started with removing only one file at a time and it seems to have worked flawlessly.

1. Unpack the JR3T-14G381-AM.zip to your desktop and copy the contents of the JR3T-14G381-AM folder to your flash drive. Work only from your flash drive from this point on.
2. Delete the JR3T-14G423-BA.tar.gz file (772.1mb) from the SyncMyRide folder on your flash drive.
3. Open the autoinstall.lst with a text editor (TextEdit on a Mac or Notepad in Windows) on your flash and delete lines - Item3 and Open3.
4. Remove the spaces where Item3 andOpen3 resided and rename Item4 and Open4 to Item3 andOpen3. EVERYTHING ELSE SHOULD STAY AS IT IS.
5. Save the file with the same name - autoinstall.lst.

6. Take the flash to your car and do the install. It should update successfully and basically tell you that you are finished. But you are not. (I checked the Sync screen and it still showed 18025).
7. Take your flash back to your computer and do the same thing except you will copy the "BA" file from the SyncMyRide folder on your desktop to the same folder on the flash drive.
8. Now, delete the "AM" file - JR3T-14G381-AM.tar.gz (451.3mb) on your flash drive.
9. For simplicity sake, I copied the original autoinstall.lst from the desktop and overwrote the modified one on the flash drive and did steps 3,4, and 5 again, this time deleting Item2 and Open2 lines, removing spaces, and renaming Item3 and Open3 to 2, and Item/Open 4 to 3
10. Repeat step 6 and it SHOULD work for you (caveat emptor). I checked the Sync screen and it shows version 18093. I tested all the functions and everything seems to work fine. It even seems to be quicker - but that could be me wanting it to be so!

Godspeed!

The workaround that is floating around is to install the voice file for a nav APIM onto a non-nav APIM to free up memory while all of the expected files remain present.
It just happens that the voice package on the nav units is smaller and this frees up enough room to run the update as-is from Ford. You lose voice functionality for a minute, but the update ultimately installs the correct version.

Sponsored