Update to Sync 3.4 and no Android Auto

Ford SYNC 3 Support CyanLabs Update Support
, , , , , ,
1

Recently updated my Sync to 3.4.23188, no navigation. It is not showing android auto and on random starts, I get “USB Hubs Are Not Supported. Please Remove”. Tried my phone and cord on the other car, works fine.

SYNC Region: NA

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4.23188

New SYNC Version: 3.0.23219

Do you have a error message, if so what is it?
Occasionally recieve “USB Hubs Are Not Supported. Please Remove”

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: Syn3 Updater 2.142.0 (Stable)

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

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

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

DESTINATION DETAILS
Mode: Drive
Model: PNY USB 2.0 FD USB Device
Size: 14.9GB
FileSystem: exFAT
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.14.2.0 Stable - Autoinstall Mode - Sync 3.4.23188 NA

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1= SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = VOICE - 5U5T-14G391-CS_1660783942000.TAR.GZ
Open2 = SyncMyRide\5U5T-14G391-CS_1660783942000.TAR.GZ
Item3 = GRACENOTES - 4U5T-14G423-CC_1615429225000.TAR.GZ
Open3 = SyncMyRide\4U5T-14G423-CC_1615429225000.TAR.GZ
Item4 = APPS - NU5T-14G381-AD_1689364279000.TAR.GZ
Open4 = SyncMyRide\NU5T-14G381-AD_1689364279000.TAR.GZ
Options = AutoInstall


FILES (4)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
5U5T-14G391-CS_1660783942000.TAR.GZ (385.5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)

LOG
[10/19/2025 6:46:02 PM] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: Non Nav APIM 
[10/19/2025 6:46:02 PM] Install Mode: Auto-Detect (autoinstall) Forced: False 
[10/19/2025 6:46:02 PM] MY20 Protection: Auto-Detect 
[10/19/2025 6:46:02 PM] Formatting USB drive
[10/19/2025 6:46:02 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[10/19/2025 6:47:27 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[10/19/2025 6:47:27 PM] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[10/19/2025 6:47:27 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[10/19/2025 6:47:27 PM] Validated: 5U5T-14G391-CS_1660783942000.TAR.GZ (Skipping Download) 
[10/19/2025 6:47:27 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[10/19/2025 6:47:29 PM] Validated: 4U5T-14G423-CC_1615429225000.TAR.GZ (Skipping Download) 
[10/19/2025 6:47:29 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[10/19/2025 6:47:31 PM] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
[10/19/2025 6:47:31 PM] Preparing USB drive
[10/19/2025 6:47:31 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[10/19/2025 6:47:31 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[10/19/2025 6:47:31 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[10/19/2025 6:47:31 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[10/19/2025 6:47:31 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[10/19/2025 6:47:31 PM] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[10/19/2025 6:47:59 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[10/19/2025 6:48:00 PM] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[10/19/2025 6:48:00 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[10/19/2025 6:48:00 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[10/19/2025 6:48:45 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[10/19/2025 6:48:47 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[10/19/2025 6:48:47 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[10/19/2025 6:48:47 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[10/19/2025 6:49:54 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[10/19/2025 6:49:58 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[10/19/2025 6:49:58 PM] Generating Autoinstall.lst
[10/19/2025 6:49:58 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!
2

If you plan to use Carplay you will need to replace the hub. Also if you get tired of the message you will also need to change the USB hub. Android Auto should work fine either way.

In the end you will want to replace the hub. Ford made this very clear for 2016 owners when they released the newer versions.

3

Have you master reset?. If you have, replace the HUB for a compatible CP one and that might solve the issue.

As Bill said it’s mandatory for CP, not for AA… but I remember reading a few comments about AA not working either… Maybe your car is one of that minority that requires a HUB upgrade for AA as well…

4

No Plans on Carplay. It did work previously but randomly stopped. Just want to get Android Auto working with my Samsung Android.

1 Like
5

I did do a master reset as well. Would the USB hub just stop working through software upgrades?

It wouldn’t surprise me if I have a minority truck that requires this. I have an old ipod that is hooked into the USB that still transfers music since I can’t use the AA now. I mainly want it for the google maps since I do a lot of driving to places.

6

It’s not that it does not work, you will be able to listen to music from a pendrive for instance… 3.4 is not compatbile with older hubs, your car from 2016 is an example…

Assuming there’s nothing wrong with your current hub and cabling, swapping the HUB for a CP compatible one should solve your issue.

You can take this post as a reference for part numbers → Media Hub, CarPlay Compatible - 2015-2020 Ford/Lincoln - SYNC 3

7

I appreciate the responses. I tried to do my best researching before the upgrade. Is it possible to go back to a previous Sync version before getting a new USB hub?

8

No, you can’t go back to 3.0 as stated in the documentation.
But you could go back to 3.3 to see if the message goes away (I’m unsure about it though), but from the functional point of view it will change nothing.