Sync 3 Technical Discussion
Junior Member
Joined: Mar 2018
Posts: 7
Likes: 0
In my opinion you really want to install the full 3.0. It has several utilities that clean up certain things it did in previous installs, so downgrading is the best path. Someone posted a list of all available files to download directly from Ford's servers. I believe it was a PDF floating around. What I would do is download ONLY the apps install, which is 381. That's how the unofficial 3.0 was anyway. You really only installed the apps plus whatever someone else might have packaged together with it. Put that line only in the autoinstall.lst, then downgrade. Then install the full official 3.0. And if your APIM is non-nav, go ahead and add the lines a few posts above before the 381 install to get the APIM ready to avoid a MEM_ERR03 issue.
Thread Starter
Senior Member
Joined: Nov 2017
Posts: 204
Likes: 98
you only need the 381 package to switch Sync versions. Pick your poison ... Plenty to choose from in that PDF. But watch out for the smaller JL7T, those I believe according to AuRon are 4" versions
Last edited by Acool; Mar 19, 2018 at 09:12 PM.
Junior Member
Joined: Nov 2017
Posts: 23
Likes: 5
There no point to return to 2.3 and install again 3.0. The 3.0.18025 package is exactly the same.
Junior Member
Joined: Mar 2018
Posts: 7
Likes: 0
Someone over at the Mustang forums said the unofficial and the official file sizes are exactly the same. I’m assuming this means nothing has changed between the official 18025 build and the 17276? If so, I’ll just keep what I have. It’s been working flawlessly.
5 Year Member
Joined: May 2016
Posts: 145
Likes: 20
Senior Member
Joined: Aug 2015
Posts: 226
Likes: 21
It's just one unzip of the downloaded package. What you are experiencing is a known issue, especially if installing on 2.3. Use the reset buttons (I think hold power and eject), let it boot, and keep trying until you see flashing light. If you don't see flashing lights, reboot, put the USB in and wait ~30 min to see if it starts updating. I did a few today and each one had different behavior. You can also try changing the options in the Autoinstall.lst and remove "delay" to see if it has any effect. But on one module I just had to keep trying and trying..
I don't know that I use GN anyways, since I always use Car Play. Reported my upgrade, and Ford "took it".
All seems to be awesome!
Junior Member
Joined: Nov 2017
Posts: 23
Likes: 5
What doesn't change is the package between the build 18025 that we have from sometime and new newly officially released 18025. In that case the package is exactly the same.. even the links used to create the big package downloadable from ford is the same as you can see from the pic below.
Last edited by Au{R}oN; Mar 20, 2018 at 03:04 AM.
Thread Starter
Senior Member
Joined: Nov 2017
Posts: 204
Likes: 98
The mem error fix using the Nav/Nav file, and editing the auto install worked like a charm. Ran that first, rebooted a few times to be safe, and plugged in 3.0 Non Nav. Unit now states it has 3.0, although GN does not show a version number anymore, perhaps it will be there when I wake up? Or is part of enabling wifi auto updates?
I don't know that I use GN anyways, since I always use Car Play. Reported my upgrade, and Ford "took it".
All seems to be awesome!
I don't know that I use GN anyways, since I always use Car Play. Reported my upgrade, and Ford "took it".
All seems to be awesome!