View Poll Results: How many of you have utilized the SYNC3 update?
Upgraded
627
69.05%
Choosing to wait for Ford
281
30.95%
Voters: 908. You may not vote on this poll
Current SYNC 3 and CarPlay/Android Auto Information
Senior Member
Joined: Oct 2010
Posts: 304
Likes: 34
Updated to v3 17194 build a couple weeks ago with no issues, no loss of Gracenote. Install went well except I keep getting that annoying "connect to wifi" message unless I disable the automatic updates. Saw the link for 17276 that gets rid of that message and figured I would try it, did the update, Sync3 still says build 17194 and now there is no Gracenote version and I still get the pop-up messages for the wifi. Oh well, I guess that I can still live with it as long as my Sync3 didn't brick on me. Maybe I will try like others have to downgrade to v2.0 and then upgrade again.
Looking at the "autoinstall.lst" file for the 17276 afterwards, and it has "build 17194" listed, maybe someone linked the wrong one and labeled it as build 17294? Anyone out there that can check the autoinstall.lst file for 17276 build? Thanks.
Tom
Looking at the "autoinstall.lst" file for the 17276 afterwards, and it has "build 17194" listed, maybe someone linked the wrong one and labeled it as build 17294? Anyone out there that can check the autoinstall.lst file for 17276 build? Thanks.
Tom
I just did the 17276 build nav version update,
http://www.mustang6g.com/forums/showthread.php?t=41251
and had no issues.
8G thumb drive 3.0 FAT32. 4 minutes after I inserted the drive the display showed "updating" and was done in a total of 9 minutes. Everything checks out so far.
http://www.mustang6g.com/forums/showthread.php?t=41251
and had no issues.
8G thumb drive 3.0 FAT32. 4 minutes after I inserted the drive the display showed "updating" and was done in a total of 9 minutes. Everything checks out so far.
5 Year Member
Joined: Mar 2017
Posts: 1,534
Likes: 507
From: South St. Louis county, Mo.
From what I have read here guys have used all combinations of those.
Are you using a windows pc or Mac to copy to your sub drive? I'm guessing windows since you tried. FAT32. I ask because a few members that have Macs had to use a windows pc to copy files to the USB for it would work. Rather odd since osx can create, read and write exFAT.
Are you using a windows pc or Mac to copy to your sub drive? I'm guessing windows since you tried. FAT32. I ask because a few members that have Macs had to use a windows pc to copy files to the USB for it would work. Rather odd since osx can create, read and write exFAT.
Senior Member
Joined: Sep 2015
Posts: 384
Likes: 38
I got it! I used a different 64GB flash drive and for some reason it started working. About 5 mins after I plugged it in I got the prompt. It about gave me a heart attack though because after installed I shut the truck off and it showed the new update but navigation wasn't working at all and the maps were blank as well as the Navigation version number.... Nothing. I then shut down everything for a second time, waited a little bit longer and then restarted the truck and my navigation came back. Crazy. This update is a lot faster in response time. Everything is much snappier.
Just Another Member
Joined: Jun 2011
Posts: 7,111
Likes: 191
From: New England
The non-nav zip file that's over on the Mustang forum is Build 17194, not 17276, and that was the problem for me. I didn't check the autoinstall.lst file to see what the build number is, just assumed it was 17276 like the nav version.
The file is named fordsync3_3.0_na_non-nav.zip, but you have to look in the zip file, at the autoinstall.lst to see the build number.
My advice is that if you have non-nav SYNC, do not try the so-called 17276 update without verifying that it really is Build 17276. There's folks here and on the Mustang and Fusion forums that made the same mistake and messed up their systems. And please let me know if you actually find this mythical update!
The file is named fordsync3_3.0_na_non-nav.zip, but you have to look in the zip file, at the autoinstall.lst to see the build number.
My advice is that if you have non-nav SYNC, do not try the so-called 17276 update without verifying that it really is Build 17276. There's folks here and on the Mustang and Fusion forums that made the same mistake and messed up their systems. And please let me know if you actually find this mythical update!
Last edited by Theocoog; Oct 23, 2017 at 07:57 PM.
The Source
Joined: Jul 2016
Posts: 403
Likes: 247
From: New England, USA
The non-nav zip file that's over on the Mustang forum is Build 17194, not 17276, and that was the problem for me. I didn't check the autoinstall.lst file to see what the build number is, just assumed it was 17276 like the nav version.
The file is named fordsync3_3.0_na_non-nav.zip, but you have to look in the zip file, at the autoinstall.lst to see the build number.
My advice is that if you have non-nav SYNC, do not try the so-called 17276 update without verifying that it really is Build 17276. There's folks here and on the Mustang and Fusion forums that made the same mistake and messed up their systems. And please let me know if you actually find this mythical update!
The file is named fordsync3_3.0_na_non-nav.zip, but you have to look in the zip file, at the autoinstall.lst to see the build number.
My advice is that if you have non-nav SYNC, do not try the so-called 17276 update without verifying that it really is Build 17276. There's folks here and on the Mustang and Fusion forums that made the same mistake and messed up their systems. And please let me know if you actually find this mythical update!
Hash for Non-Nav 3.0 Build 17276-
SHA1: 171910BD65FFBE2AF789187A7840C9800082551F
MD5: 1D9860EE530AB966F3B4D0F9C13241D2
Just Another Member
Joined: Jun 2011
Posts: 7,111
Likes: 191
From: New England
EDIT: Looks like they posted the new file on the Mustang forum: http://www.mustang6g.com/forums/showthread.php?t=41251 The hashes check out.
Last edited by Theocoog; Oct 24, 2017 at 06:50 AM.