Jump to content

Sync3 v2.0 -> v3.0 USB Difficulties (solved)


Recommended Posts

I upgraded my 2017 Explorer from Sync3 v2.0 to Sync3 v3.0 this weekend via the USB mechanism with some difficulty. I figured I could document it on the off-chance that someone else runs into the same problems I did. This could be because I'm using a Mac.

 

WiFi recognized that an update was available, but the download status bar never got above 50% so I moved to USB.

 

1) I downloaded the "JR3T-14G381-AL.zip" file from https://owner.ford.com/tools/account/how-tos/keep-your-sync-up-to-date/sync-software-update.html#/prepare and uncompressed it.

 

2) I noticed that it uncompressed into

 

JR3T-14G381-AL

├── DONTINDX.MSA

├── SyncMyRide\GB5T-14G386-AA.tar.gz

├── SyncMyRide\HB5T-14G386-AHH.tar.gz

├── SyncMyRide\HB5T-14G386-TCB.tar.gz

├── SyncMyRide\HB5T-14G386-THA.tar.gz

├── SyncMyRide\HB5T-14G387-AAB.tar.gz

├── SyncMyRide\JR3T-14G381-AL.tar.gz

├── SyncMyRide\JR3T-14G391-CD.tar.gz

├── SyncMyRide\JR3T-14G423-CA.tar.gz

└── autoinstall.lst

 

0 directories, 10 files


That is I had files named "SyncMyRide\GB5T-14G386-AA.tar.gz" with the "\" and all that.

 

Attempting to upgrade with these files resulted in no activity on the USB drive when it was plugged into the Sync USB port

 

3) Step #2 in the install process made reference to a "SyncMyRide" folder so I changed the folder structure to

 

JR3T-14G381-AL

├── DONTINDX.MSA

├── SyncMyRide

│ ├── GB5T-14G386-AA.tar.gz

│ ├── HB5T-14G386-AHH.tar.gz

│ ├── HB5T-14G386-TCB.tar.gz

│ ├── HB5T-14G386-THA.tar.gz

│ ├── HB5T-14G387-AAB.tar.gz

│ ├── JR3T-14G381-AL.tar.gz

│ ├── JR3T-14G391-CD.tar.gz

│ └── JR3T-14G423-CA.tar.gz

└── autoinstall.lst

1 directory, 10 files

 

 

That is I created a "SyncMyRide" folder and moved the .tar.gz files into it (along with a rename).

 

The upgrade proceeded correctly after this.

 

After upgrading, I noticed the new logos for Ford and Sirius. No Waze yet (Waze app needs an update), and the version number of Sync3 is now v3.0 (and I got the .xml file generated for the last step in the upgrade process) so it appears to have worked.

 

I'm not sure if anyone from Ford is monitoring this site, but having to create the "SyncMyRide" folder and move/rename the files was pretty subtle, and probably a bug. Anyone know how to report this to Ford?

 

Link to comment
Share on other sites

  • 3 weeks later...

On my first try, something went wrong. Reloaded everything on usb drive and tried again. This time it said it succeeded and told me it had updated. But when I put the thumb drive in the computer to transfer the last file, it wasn't on the thumb drive. Any ideas or suggestions??

You probably rushed the process. Just because Sync3 says it has updated, it's just beginning the process. If you didn't sit in the car waiting for at least 30 minutes, it wasn't done. Mine rebooted twice during the process and it took more like 40 minutes (I know, a royal pain). My suggestion is to start all over again. Sorry.

Link to comment
Share on other sites

I was able to update my '16 Mustang GT (non-NAV) to version 2.2 (has the new USB hub installed) and the '17 Explorer (with NAV) came with 2.2 installed.

 

Tried version 3.0 from the Ford Owner site for the '16 Mustang using an ex Fat formatted 32 GB USB 3.0 drive, the update runs for about 3 minutes then I get a 0003 Error Code. According to Ford Sync tech support that means the drive was removed during the update, which it wasn't. Beyond that, Tech Support suggested a new flash drive and was pretty clueless.

 

I've tried the update about 6 times, re-downloaded, reformatted the drive, etc, etc., tried another flash drive - a brand new Sandisk 64 GB USB 3.0, formatted same as above - couldn't even get the update to start!

 

To schnee's point about the file structure: interesting.....I noted all the file names in the SyncMyRide folder end with .tar - but not .tar.gz as you indicate. I'm using 7zip to extract the files and in Windows it shows the file type is a gz Archive. Do you think I need to have the .gz extension after .tar in the file name?

 

 

Considering what schnee has found - and that I had zero issues updating from 1.0 to 2.2, it seems like there is something wrong with version 3.0.

 

Is anyone else experiencing issues like this?

Link to comment
Share on other sites

My first try updating to 2.2 was with the same 32GB drive I tried the 3.0 update with.

 

Funny though - the Ford owner site instructs you to format with exFAT.

 

When I updated Sync from 1.0 to 2.2 I used NTFS formatting and it worked on the first try.

Link to comment
Share on other sites

First, it's a known fact that 32GB drives that are Version 3.0 don't work. I made sure the 32GB I recently bought was Version 2.0. Didn't matter.

 

I've always used exFat, per the instructions. Try using a 16GB drive, I tell ya.

 

I didnt know that and Ive been using 16GB exfat all along

Link to comment
Share on other sites

Drive capacity should have no bearing on the ability to install an update - besides, I used the same 32 gig drive to update from 1.0 to 2.2 and had no issues.

 

This update seems buggy compared to the first few released updates.

 

The extent of assistance from Ford Sync support has been:

 

- try another flash drive

- try going to a dealer

- perform a master reset.

 

  • Perform a master reset? Great - I lose all my audio settings, all my radio presets and all my functional settings - and have no idea if it will work.

- Sync should to designed to retain all of that, similar to the way cell phone operating systems are designed.

 

- More concerning is the lack of customer support from Ford which seems to be getting worse. Frankly I'm a little surprised and disappointed.

Edited by harrry
Link to comment
Share on other sites

I was able to update my '16 Mustang GT (non-NAV) to version 2.2 (has the new USB hub installed) and the '17 Explorer (with NAV) came with 2.2 installed.

 

Tried version 3.0 from the Ford Owner site for the '16 Mustang using an ex Fat formatted 32 GB USB 3.0 drive, the update runs for about 3 minutes then I get a 0003 Error Code. According to Ford Sync tech support that means the drive was removed during the update, which it wasn't. Beyond that, Tech Support suggested a new flash drive and was pretty clueless.

 

I've tried the update about 6 times, re-downloaded, reformatted the drive, etc, etc., tried another flash drive - a brand new Sandisk 64 GB USB 3.0, formatted same as above - couldn't even get the update to start!

 

To schnee's point about the file structure: interesting.....I noted all the file names in the SyncMyRide folder end with .tar - but not .tar.gz as you indicate. I'm using 7zip to extract the files and in Windows it shows the file type is a gz Archive. Do you think I need to have the .gz extension after .tar in the file name?

 

 

Considering what schnee has found - and that I had zero issues updating from 1.0 to 2.2, it seems like there is something wrong with version 3.0.

 

Is anyone else experiencing issues like this?

 

Oh my gosh that is exactly my issue on my 2016 Expedition. I did the hub swap and did the unofficial 2.2 update as well and was able to get Apple CarPlay working. But now I can't get 3.0 no matter what I do. Tried Ex-Fat and Fat32, tried doing it from a Mac and Windows, tried doing it on 8gb flash and even bought a brand new 32gb flash. Still same error like you get. Then I take the same flash drive and go out to my 2018 Fusion and it worked first time. I've probably spent 4 hours trying to get Waze on my Expedition. Now I'm beginning to think the update we did for 2.2 is the problem. I downloaded it from a forum where some guy posted a link (before Ford posted on owner.ford.com) I wonder if I can find an official 2.2 or 2.3 version somewhere and try installing that overtop of the 2.2 I currently have if that will allow 3.0 to correctly install.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...