Crap ... back to dealer for Sync problem after update.
Thread Starter
5th Gear Member
Joined: Aug 2006
Posts: 2,460
From: Cumming, GA
Crap ... back to dealer for Sync problem after update.
I updated my Sync from 2.0 to 3.1. I think I messed it up. It is upgraded to 3.1 as per the verification file.
Problem I have is:
SERVICES COMMAND DOES NOT WORK .. NOT EVEN A MENU ITEM FOR SERVICES.
IF I SELECT THE APPLICATION MENU SYNC CRASHES AND REBOOTS.
Other functions work OK ... I basically have no voice NAV support.
Problem I have is:
SERVICES COMMAND DOES NOT WORK .. NOT EVEN A MENU ITEM FOR SERVICES.
IF I SELECT THE APPLICATION MENU SYNC CRASHES AND REBOOTS.
Other functions work OK ... I basically have no voice NAV support.
5th Gear Member
Joined: Aug 2006
Posts: 2,127
From: Los Angeles Ca
I updated my Sync from 2.0 to 3.1. I think I messed it up. It is upgraded to 3.1 as per the verification file.
Problem I have is:
SERVICES COMMAND DOES NOT WORK .. NOT EVEN A MENU ITEM FOR SERVICES.
IF I SELECT THE APPLICATION MENU SYNC CRASHES AND REBOOTS.
Other functions work OK ... I basically have no voice NAV support.
Problem I have is:
SERVICES COMMAND DOES NOT WORK .. NOT EVEN A MENU ITEM FOR SERVICES.
IF I SELECT THE APPLICATION MENU SYNC CRASHES AND REBOOTS.
Other functions work OK ... I basically have no voice NAV support.
. Good luck getting it resolved 
1st Gear Member
Joined: Nov 2009
Posts: 71
From: CA
not true; Sync software option to self-upgrade is on the syncmyride site.
did you download both downloads available? im about to flash sync and noticed there are 2 downloads, one of which determines what upgrades you need....
did you download both downloads available? im about to flash sync and noticed there are 2 downloads, one of which determines what upgrades you need....
1st Gear Member
Joined: Nov 2009
Posts: 71
From: CA
.....don't bring the vehicle to the dealership for 3.1 If you are getting the error message like the original poster (which I am also getting) Microsoft/Ford are aware of the issue and supposedly they are going to release an update (to the update) that will resolve this problem. I was told via an email this morning that the fix should be released on February 22nd, 2010. Hope this info helps and also saves some people some time and money
Thread
Thread Starter
Forum
Replies
Last Post