HOWTO Downgrade Sync3 v3.0 back to Ford Official v2.2 (build 17011)
#31
My 2016 has Sync 3 v3.0 build 17276. I keep getting the wi-fi prompts and my Grace notes doesn't show a version. I have tried to go back to 2.2 using the OP's instructions, and it will tell me that the software is downloaded, and it very briefly tells me I need a key cycle. When I turn it off, and then back on, I am still stuck with 3.0 that keeps prompting me for wi-fi. Any suggestions on what to try?
#32
Senior Member
Thread Starter
Also, even after a key-cycle, sometimes the installation is still performing tasks in the background, so changes/versions may not manifest until 30 min or so.
Some people may say to perform a master reset, but I have found this to be unnecessary in every installation (and downgrade) instance. However, if all else fails, it's worth a try as a last resort -- after you have run both installation phases.
HTH.
The following users liked this post:
oldcrashtestdummy (11-10-2017)
#34
Just Another Member
It works fine from 17194 or 17276.
#35
Have you performed both phases of the installation?
Also, even after a key-cycle, sometimes the installation is still performing tasks in the background, so changes/versions may not manifest until 30 min or so.
Some people may say to perform a master reset, but I have found this to be unnecessary in every installation (and downgrade) instance. However, if all else fails, it's worth a try as a last resort -- after you have run both installation phases.
HTH.
Also, even after a key-cycle, sometimes the installation is still performing tasks in the background, so changes/versions may not manifest until 30 min or so.
Some people may say to perform a master reset, but I have found this to be unnecessary in every installation (and downgrade) instance. However, if all else fails, it's worth a try as a last resort -- after you have run both installation phases.
HTH.
#36
Senior Member
Thread Starter
I tried it again. I did a master reset, then I pulled the fuses (passenger inside box, 32 and 33) and I let it sit for 30 minutes. I put step 1 on a USB stick and step 2 on a separate USB stick. This time when I did the key cycle after step 2 with the USB still in, it started to do more installing. I let it sit while it installed, when out and restarted it. It says new software installed. I did not get 2.2, I still have 3.0 build 17276, but I also have Gracenote with a version number and I don't seem to get the wi-fi prompt. I will give it a try and if everything works, I will quit screwing around with it.
The phases are split because of internal memory imitations, which were causing out-of-memory errors (and failed installations).
You’re welcome for the tips and help attempts provided thus far.
The following users liked this post:
oldcrashtestdummy (11-11-2017)
#37
Well I put 70 miles on the truck today and Sync 3 v3.0 build 17276 worked great. It looks like Gracenote is also working. I'm sure that the second USB stick was what got Gracenote working, I'm unsure why my many attempts at installing 2.2 failed though.
#38
@Cuch can you impart me with some of your wisdom for the a downgrade of the Nav version... I'm coming across a "your system is already up to date error." Since there is not the same memory limitation of the non-Nav units, I think we can do this in one pass, but I am having trouble modding the autoinstall file to force the update. I made the change from:
[SYNCGen3.0_2.0.16074_PRODUCT] to [SYNCGen3.0_ALL], and added AutoInstall
...but I must be missing something. Here is the original code:
[SYNCGen3.0_2.0.16074_PRODUCT] to [SYNCGen3.0_ALL], and added AutoInstall
...but I must be missing something. Here is the original code:
Code:
; SYNC3 Consumer Assembly Upgrade - Release 2.3.10 - Only for MY 17 Nav/NA assemblies. [SYNCGen3.0_2.0.16074_PRODUCT] Item1 = HB5T-14G386-TCB Open1 = SyncMyRide\HB5T-14G386-TCB.tar.gz Item2 = HB5T-14G386-AHH Open2 = SyncMyRide\HB5T-14G386-AHH.tar.gz Item3 = JL7T-14G391-CA Open3 = SyncMyRide\JL7T-14G391-CA.tar.gz Item4 = JL1T-14G381-AJ Open4 = SyncMyRide\JL1T-14G381-AJ.tar.gz Item5 = JL7T-14G423-CA Open5 = SyncMyRide\JL7T-14G423-CA.tar.gz Item6 = HB5T-14G387-AAB Open6 = SyncMyRide\HB5T-14G387-AAB.tar.gz Item7 = GB5T-14G386-AA Open7 = SyncMyRide\GB5T-14G386-AA.tar.gz Options = Delay,Include,Transaction
#39
Senior Member
Thread Starter
@Cuch can you impart me with some of your wisdom for the a downgrade of the Nav version... I'm coming across a "your system is already up to date error."
[...]
Here is the original code:
[CODE]
; SYNC3 Consumer Assembly Upgrade - Release 2.3.10 - Only for MY 17 Nav/NA assemblies.
[...]
Here is the original code:
[CODE]
; SYNC3 Consumer Assembly Upgrade - Release 2.3.10 - Only for MY 17 Nav/NA assemblies.
I'll try not to derail this thread too much (the howto and thread is for 3.0 -> 2.2 non-Nav users), but...
If you want v2.3 (Nav), you need to downgrade to v2.2 Nav *first*, then upgrade to 2.3 Nav.
Reason being, is that in *only* v2.3, there is an internal (and digitally-signed) version checker, which checks the version of the currently installed Sync3 application layer. If the currently installed version of Sync3 is > 2.3, the 2.3 internal installer routine will bail and display "already up to date". This is not something that can be manipulated via the installer script. Downgrading to 2.2 first, should do the trick...
I would suggest you get the official 2.2 Nav package from Ford*, downgrade to that, then use the official Ford channels to then upgrade to 2.3 Nav (owner.ford.com). Fortunately, you can just run the 2.2 upgrade without manipulating anything.
* Here is the official Ford OTA/CDN link for their official 2.2 Nav package:
Code:
http://ivsu.binaries.ford.com/owner-package/2795246548234394720/HN1T-14G381-SA.zip
The following 2 users liked this post by Cuch:
RustedRoot (01-02-2018),
swamplynx (11-11-2017)
#40
It *looks* as if you're attempting to go from v3.0 Nav to v2.3 Nav. If that's the case, the downgrade won't the way this howto describes, nor the way you're attempting...
I'll try not to derail this thread too much (the howto and thread is for 3.0 -> 2.2 non-Nav users), but...
If you want v2.3 (Nav), you need to downgrade to v2.2 Nav *first*, then upgrade to 2.3 Nav.
Reason being, is that in *only* v2.3, there is an internal (and digitally-signed) version checker, which checks the version of the currently installed Sync3 application layer. If the currently installed version of Sync3 is > 2.3, the 2.3 internal installer routine will bail and display "already up to date". This is not something that can be manipulated via the installer script. Downgrading to 2.2 first, should do the trick...
I would suggest you get the official 2.2 Nav package from Ford*, downgrade to that, then use the official Ford channels to then upgrade to 2.3 Nav (owner.ford.com). Fortunately, you can just run the 2.2 upgrade without manipulating anything.
* Here is the official Ford OTA/CDN link for their official 2.2 Nav package:
(not-hotlinked intentionally, due this forum's bad habit of truncating linked long URL's)
I'll try not to derail this thread too much (the howto and thread is for 3.0 -> 2.2 non-Nav users), but...
If you want v2.3 (Nav), you need to downgrade to v2.2 Nav *first*, then upgrade to 2.3 Nav.
Reason being, is that in *only* v2.3, there is an internal (and digitally-signed) version checker, which checks the version of the currently installed Sync3 application layer. If the currently installed version of Sync3 is > 2.3, the 2.3 internal installer routine will bail and display "already up to date". This is not something that can be manipulated via the installer script. Downgrading to 2.2 first, should do the trick...
I would suggest you get the official 2.2 Nav package from Ford*, downgrade to that, then use the official Ford channels to then upgrade to 2.3 Nav (owner.ford.com). Fortunately, you can just run the 2.2 upgrade without manipulating anything.
* Here is the official Ford OTA/CDN link for their official 2.2 Nav package:
Code:
http://ivsu.binaries.ford.com/owner-package/2795246548234394720/HN1T-14G381-SA.zip