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
10-26-2017, 09:10 AM
#4321
This...
I did try that (thanks for your help) and it didn't work. I got repeated out of memory errors. I used both an existing 32GB USB 2.0 flash drive and a new 64GB USB 3.0 flash drive. I tried installing it in two parts, and then file by file (tedious - editing the autoinstall.lst for each step) - still got the memory error.
I suspect it's because my 2016 came with Sync 3 version 1.0 and the version 2.2 was the engineered update path - a direct upgrade to 1.0. The system never had 2.0 on it. But I bet if I could get my hands on the factory 1.0 files it would work: 1.0 > 2.2 > 3.0.
At this point, the last thing I might try is resetting the APIM with Forscan and then trying the 17276 update. If that doesn't work then I'm going to wait and hopefully the OEM files will be released or someone talented will find a fix. I think the issues we are experiencing are pretty common among the non-nav updates to 17276. I haven't heard of a successful update yet.
I suspect it's because my 2016 came with Sync 3 version 1.0 and the version 2.2 was the engineered update path - a direct upgrade to 1.0. The system never had 2.0 on it. But I bet if I could get my hands on the factory 1.0 files it would work: 1.0 > 2.2 > 3.0.
At this point, the last thing I might try is resetting the APIM with Forscan and then trying the 17276 update. If that doesn't work then I'm going to wait and hopefully the OEM files will be released or someone talented will find a fix. I think the issues we are experiencing are pretty common among the non-nav updates to 17276. I haven't heard of a successful update yet.
I have been trying everything in my power to get my '16, formerly v1.0 APIM, back to v2.2 17011 (since that was the most stable), but to no avail. Tried spitting it up in steps; no go: MEM_ERR03 every time.
Oddly, I was able to get 3.0, 17194 downgraded from 17276; but this is where I'm stuck.
I will report back if I get this figured out.
10-26-2017, 09:41 AM
#4322
Just Another Member
Version 3.0 Build 17194 fixed Gracenote and probably some other small issues. It's also faster, but as you can see from the last couple of pages, there are some issues with going from Build 17194 to the newer 17276 for some (most?) non-nav systems. Version 2.2 is an official release too - you can download the files from Ford.
Last edited by Theocoog; 10-26-2017 at 09:22 PM.
10-26-2017, 11:07 AM
#4323
Senior Member
Version 3.0 Build 17194 fixed Gracenote and probably some other small issues. It's also faster, but as you can see from the last couple of pages, there are some issues with going from Build 17194 to the newer 17276 for some (most?) non-nav systems. Version 2.2 is an official release too - you can download the files from Ford, whereas 3.0 is not official yet.
10-26-2017, 01:33 PM
#4325
Another Successful Navigation version update. I installed 3.0 via USB 8gb formatted in exFAT. Update took about 20 minutes and after I finished it says I have version 17276. Prior to update I was still running 2.0 16074.
Last edited by SpeckTracker; 10-27-2017 at 09:09 AM.
10-26-2017, 02:14 PM
#4326
OK ladies and germs, I have figured out how to successfully downgrade from 3.0 Non-Nav (both builds: 17276 and 17194) back to official Ford IVSU 2.2 build 17011, with Gracenotes working again and no annoying pop-ups.
It's a very involved process and I had to reverse engineer some stuff to get it figured out.
Ergo, I will be posting a brand new thread with a consummate HOWTO, and hopefully we can make it a sticky post. Stay tuned for my post/HOWTO this afternoon.
I have a theory as to why the downgrade back to 2.2 (from 3.0) has failed for so many Non-Nav users, and the process I got working, reinforced my hypothesis.
Lesson learned for me: I'll from now on stick with official Ford builds from their owner.ford.com site. </facepalm>
It's a very involved process and I had to reverse engineer some stuff to get it figured out.
Ergo, I will be posting a brand new thread with a consummate HOWTO, and hopefully we can make it a sticky post. Stay tuned for my post/HOWTO this afternoon.
I have a theory as to why the downgrade back to 2.2 (from 3.0) has failed for so many Non-Nav users, and the process I got working, reinforced my hypothesis.
Lesson learned for me: I'll from now on stick with official Ford builds from their owner.ford.com site. </facepalm>
10-26-2017, 02:31 PM
#4327
Just Another Member
OK ladies and germs, I have figured out how to successfully downgrade from 3.0 Non-Nav (both builds: 17276 and 17194) back to official Ford IVSU 2.2 build 17011, with Gracenotes working again and no annoying pop-ups.
It's a very involved process and I had to reverse engineer some stuff to get it figured out.
Ergo, I will be posting a brand new thread with a consummate HOWTO, and hopefully we can make it a sticky post. Stay tuned for my post/HOWTO this afternoon.
I have a theory as to why the downgrade back to 2.2 (from 3.0) has failed for so many Non-Nav users, and the process I got working, reinforced my hypothesis.
Lesson learned for me: I'll from now on stick with official Ford builds from their owner.ford.com site. </facepalm>
It's a very involved process and I had to reverse engineer some stuff to get it figured out.
Ergo, I will be posting a brand new thread with a consummate HOWTO, and hopefully we can make it a sticky post. Stay tuned for my post/HOWTO this afternoon.
I have a theory as to why the downgrade back to 2.2 (from 3.0) has failed for so many Non-Nav users, and the process I got working, reinforced my hypothesis.
Lesson learned for me: I'll from now on stick with official Ford builds from their owner.ford.com site. </facepalm>
10-26-2017, 04:01 PM
#4329
My forthcoming downgrade HOWTO will include the official Ford link to the 2.2 files as well as detailed instructions.
The following users liked this post:
Theocoog (10-26-2017)