No Android Auto on Sync 3 version3 build 19205

[ducka6969]

Good morning everyone. I’m new to the forum. I bought a 2016 f150 Lariat and Sync3 was never updated as far as I could tell. It was version 1. I tried to do the USB update through Ford’s website and it failed “The installation has run out of space or does not work with this version”. I turned on auto updates and connected to WiFi. That successfully updated my system to version 3 build 19205. However when I plug in my USB to my Samsung Galaxy S9+ it charges and I can play audio through the USB as a source, but I have no option to run Android Auto. After doing a bunch of reading I think I skipped the version 2 update that included Android Auto. I found a post on here that talked about how to install that version through CyanLabs, but I can’t seem to get USB updates to work properly. I always get the message “The installation has run out of space or does not work with this version”. If someone could help me out I would really appreciate it as this has been frustrating. For the record I don’t care about apple car play. I just want Android Auto.

Thank you!
-Kevin

---

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Unknown

Install Type: Unknown

Old SYNC Version: 1 1

New SYNC Version: 3 3 19205

Do you have a error message, if so what is it?
Installation failed
The installation has run out of space or does not work with this version

Update Method: Official Ford

This is the version 2.2 I attempted to install.

[derolk (7D0-01-01)]

Can you try to go to General settings and do a master reset? Then try to connect your android after the master reset?

[SaNdMaN]

+1 to the master reset recommendation.

Once it’s done, create, run and share the interrogator log 's xml file with us.

[ducka6969]

Master reset did not fix the issue. After running the interrogator I got a red error message. “The XML file you have selected does not contain the expected output. Syn3 Updater has determined you are on 3.0.19205 and may be using overlays. Syn3 Updater is unable to determine the configuration of your APIM. Request assistance on forum.” XML attached.

Sync_VV44KAVX_.xml (9.8 KB)

As Built:

VIN:
APIM Model: GJ5T-14G371-CFC
APIM Type: Non-Navigation
APIM Size: 0GB
APIM Free Space: Unknown
Version 3.0.19205 (JR3T-14G381-AS)

1/24/2006 9:22:56 PM +00:00

Partition Type = Free / Total
/fs/usb0/ = 977G / 977G

Installed Packages
GB5T-14G422-CJ
GB5T-14G421-CJ
GB5T-14G424-CH
JR3T-14G391-CE
JR3T-14G423-CB

APIM AsBuilt
DE00: 2A2A050220028B02048A
DE01: 55530103C402028000000000
DE02: 0000010300
DE03: 01000000000001
DE04: 1A681A683D54
DE05: 80
DE06: 47003300000000029A000056569400C8

[SaNdMaN]

Thanks, try following this post → 2016 Mustang Sync3 1.0 updated to 3.0 and no Apple Carplay! - #10 by SaNdMaN to install the intermediate 2.2.17xxx build and check if Android Auto works.

Also, you may need to swap the hub of the model is 2016 or earlier → Media Hub, CarPlay Compatible - 2015-2020 Ford/Lincoln - SYNC 3 , but do not do that yet.

[ducka6969]

That is the post I was following when I tried installing version 2.217xxx but got this message “The installation has run out of space or does not work with this version”. Pics of the USB that I set up, maybe you’ll see something that I did wrong.

[SaNdMaN]

Was this attempted after the master reset?.

The data from the interrogator log is wrong, there’s information missing so the APIM is questionable…

[ducka6969]

It was before the master reset that I did last night, but I had done several matter resets before then. Something is definitely funky. The date says it’s from 2006.

[warlock12118]

That’s a directory create date, you’ll see that if a directory is cleared and reused without being deleted.

The file dates are the important part and those show the correct date.

[SaNdMaN]

Ok, try again after the master reset…
If the unit can’t process these kind of packages, you will have to look into a replacement… It’s a very old unit…

[ducka6969]

Having to get a new unit would suck. Are you sure there’s nothing wrong with the update I was trying to install? I’m not very savvy when it comes to this sort of thing.

If it looks good. Ill run another master reset tonight and try again.

[SaNdMaN]

It’s not an USB issue, the APIM is not giving correct / complete information when the USB is ran against it.

Also, if you are creating the USBs via Syn3Updater, they are surely good as long as the pendrive is a good one.

[F150Chief]

Do not uncompress the .gz zip file.

[SaNdMaN]

Good catch, but I do not think he did… I think windows is just not showing the extension… But he should confirm this…