Issue updating to 3.4

Ford SYNC 3 Support
,
1

2016 Ford Edge Titanium (non-Nav)

I successfully updated from my stock SYNC 3 v1.0 to 3.3.19052 using the SYN3 Updater. I’m trying now to update to 3.4 (any version) and I’m following the same SYN3 process for creating the USB but when I turn on the vehicle, put the USB in, the only thing that happens is I get the ‘Update Detected’ screen. When I select ‘Yes’ nothing else happens.

SYNC Region: North America & Canada

Navigation Variant: No

Old SYNC Version: 3.3.19052

New SYNC Version: 3.4.21265

Do you have a error message, if so what is it?

CYANLABS - SYN3 UPDATER - V2.10.8.0
Branch: Stable
Operating System: Microsoft Windows 10 Home (2009)

PREVIOUS CONFIGURATION
Version: 3.3.19052
Region: NA
Navigation: False
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: USB DISK 3.0 USB Device
FileSystem: exFAT
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.10.8.0 Stable - Autoinstall Mode - Sync 3.4.21194 NA

[SYNCGen3.0_ALL_PRODUCT]
Item1 = GRACENOTES - 4U5T-14G423-CC_1615429225000.TAR.GZ
Open1 = SyncMyRide\4U5T-14G423-CC_1615429225000.TAR.GZ
Item2 = APPS - 5U5T-14G381-ET_1627475308000.TAR.GZ
Open2 = SyncMyRide\5U5T-14G381-ET_1627475308000.TAR.GZ
Item3 = VOICE - 5U5T-14G391-CP_1626959995000.TAR.GZ
Open3 = SyncMyRide\5U5T-14G391-CP_1626959995000.TAR.GZ
Options = AutoInstall

FILES (3)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
5U5T-14G381-ET_1627475308000.TAR.GZ (847.2MB)
5U5T-14G391-CP_1626959995000.TAR.GZ (385.4MB)

LOG
[2/10/2022 10:52:00 PM] Selected Region: NA - Release: Sync 3.4.21194 - Map Version: Non Nav APIM
[2/10/2022 10:52:00 PM] Install Mode: Auto-Detect (autoinstall) Forced: False
[2/10/2022 10:52:00 PM] MY20 Protection: Auto-Detect
[2/10/2022 10:52:00 PM] Formatting USB drive
[2/10/2022 10:52:00 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[2/10/2022 10:52:08 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:52:08 PM] Downloading: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:52:56 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:52:58 PM] Downloaded: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:52:58 PM] Checking Existing File: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:52:58 PM] Downloading: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:54:29 PM] Validating: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:54:32 PM] Downloaded: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:54:32 PM] Checking Existing File: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:54:32 PM] Downloading: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:55:04 PM] Validating: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:55:05 PM] Downloaded: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:55:05 PM] Preparing USB drive
[2/10/2022 10:55:05 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:55:05 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:55:48 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:55:56 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ
[2/10/2022 10:55:56 PM] Checking Existing File: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:55:56 PM] Copying: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:57:21 PM] Validating: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:57:33 PM] Copied: 5U5T-14G381-ET_1627475308000.TAR.GZ
[2/10/2022 10:57:33 PM] Checking Existing File: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:57:33 PM] Copying: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:58:12 PM] Validating: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:58:16 PM] Copied: 5U5T-14G391-CP_1626959995000.TAR.GZ
[2/10/2022 10:58:16 PM] Generating Autoinstall.lst
[2/10/2022 10:58:16 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

2

Based on what you are telling us, maybe it’s not moving forward because of storage issues. Try performing a master reset first, but I do not think that will help.

If that does not help, check this thread → Tutorial: Sync 3.4 NON-NAV APIM: Failure to Update to Newer Version Sync 3.4
Even though it’s for 3.4, overall is the same for troubleshooting low storage on APIM for your current situation.

Finally, since you already reformatted the unit, another easy, clean and fast method would be to force a reformat installation of 3.4.

3

Is there a tutorial for the forced reformat installation of 3.4?

4

Yes, you can read information in the documentation. Check these pages:

There is enough information there, if you want to force the install method you need to go to the advanced options tab. So you would need to just recreate the USB by forcing reformat as installation method.

But run the interrogator log against the unit, to see how much free space it has.

5

@Hawkeye One last thing that I overlooked before.

DO NOT USE AN EXTERNAL DISK

Use a simple quality branded USB pendrive…
Using a DISK may prevent things from flowing as they should…

6

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.