It does say it’s updating. but trying it twice again, after about an hour it says “installation failed the installation has run out of space or does not work with this version” and i did try both ports. also it went from gracenote version 1.1.1.615 (NA-0010) before i messed with it to the version being blank after it tried to update.
; SYNC3 Consumer Assembly Upgrade - Release 3.0.25 - Only for My16 NonNav/NonEU assemblies.
The USB should be exFAT, although I’m not sure that’s your issue since it seems the USB is being recognized, but try with exFAT instead.
Also, what Ford is pushing your way is basically a Gracenotes, Voice and Sync3 update.
Since it’s a NO NAV unit, maybe there’s enough free space on the unit to process all those updates at once.
We could try a different approach by installing them individually.
The files you need installed are:
Voice: JR3T-14G391-BF
Apps: JR3T-14G381-AX
Gracenotes: JR3T-14G423-BB
If you go to those links, you can download the autoinstall.lst file required for installing them individually, run one at a time.
But, before moving forward, I see an .xml file on the USB’s root, that’s an interrogator output.
Please share it, redact the VIN from the title and content first (open it as text).
I would like to review it before you moving forward, but I think you already know where this is going to: installing packages individually, and installing 2.2.17011 ( HN1T-14G381-SA ) before installing 3.0…
thank you! i accidentally deleted the interrogator but i will try to run the update again in exfat and get back to you with it if it still doesnt work.
Ok, you can do that as well. But you could recreate the .xml file with Syn3updater, it uses the same package. All I’m interested in is in seeing the apim’s free space, which may cause your issue. If it’s an 8GB APIM, there’s not a lot of room to play with…
i got a new flash drive and ran the interrogator with syn3updater like you said. it wont let me paste the whole text of the .xml since it says it’s more than two links. here is a ss from syn3
That’s an incomplete log. The APIM is not presenting itself, so we do not know what unit it is.
It says “non-navigation”, so based on the fact you also mentioned it’s a no-nav, I would say it’s an 8GB APIM, it’s only a guesstimation.
I see you have Gracenotes installed as well, GB5T-14G423-BH.
So, at this point I would try installing the packages individually.
If this fails, there’s something else we could try.
But, the only thing important for that package is the autoinstall.lst file, the file you already have from Ford’s update. Here’s the autoinstall.lst file you need:
everything finished installing successfully. the gracenotes version is still blank when i go to about sync but everything seems to be working. i do not yet have the carplay module. however, i did order one part # HC3Z-19A387-F is this correct?
can i tell if cp and aa installed properly before the module arrives? i do not see any options for them in settings.
also if i ever wanted to upgrade to 3.4 with syn3, would i need to buy a new module (part # HC3Z-19A387-B-G) or will this one still work?
The option will not appear until a compatible phone is connected. You should not need to replace the HUB while on 3.0. I’m still running 3.0 and both CP and AA work. Have you tried connecting it?.
Take a look at the previous link for part numbers, but most likely yes, you would need to change the HUB for 3.4. Android Auto might work, but Car Play may not.
i did try connecting my iphone for carplay but it’s not working. i can still play music from my phone through the usb. the hub is in the mail. hopefully that’s all that’s left. if not i should downgrade to 2.2 then upgrade back to this version?
Just remove the 2 lines from the autoinstall file. Make sure the numbering is correct. You can leave the file on the USB, it won’t matter.
You will need to remove the Gracenote file from the APIM first by running the Gracenote Removal in the Syn3 Updater. This will free up more space on the APIM for the update. You can add the Gracenote file back to the APIM after the update.
I’ve marked this as resolved since the original concern was addressed and you got Android Auto working.
There’s no reason for CP not working from the Sync3 side of things.
