Ok, so based off the autoinstall the last utility to run is in the first section, after that its all file copy.
I’d try to see if it cleans it up.
[SYNCGen3.0_ALL]
Item1 = GB5T-14G386-ZA
Open1 = SyncMyRide\GB5T-14G386-ZA.tar.gz
Options = AutoInstall
Personally at this point I’d go the reformat route and get into 3.4/NA223, yes it stops you from buying map updates from Ford. Personally when I do this on older APIMs I use PNY Attache 3 32GB drives.
Which utility file is that from? I don’t see that in either of the packages I received from Ford.
Also would my APIM handle a 3.4 update since it is so old?
The 2017 Fusion has an H series APIM, the interrogator log you posted shows that you have a HP5T-14G371-CCA which is not a MY2020 unit so you should be able to do a straight reformat to get to 3.4.x/NA223 Follow the instructions for using the updater, the whole process from start to finish once the files are downloaded and the USB is prepped takes like 30 minutes.
Ok got it. I can give that a try first
What are the chances of me bricking with a 3.4 update?
Odds are 50/50 even on a new MY2020+ APIM, all you can do is reduce the risk.
The G series in the 2016MY (eg the Escape) were more prone to bricking.
I personally haven’t had a case where an H series bricked, I always check the USB ports first, use PNYs for my USBs, do a master reset before I start and take the car for a drive while the process is running.
Ones that I have seen bricked where I put in new APIMs for people I usually find they either: 1) used a cheap USB drive; 2) had screwed up USB ports or something plugged in the 2nd port; 3) tried to do the reformat with the car idling or powered up with a battery charger.
So I’ve tried the last tool in the autoinstall and it didn’t work.
I did notice that I get the message only once in a day, like the morning. I think its because I don’t lock the doors while parked at home. The rest of the day, I have to start the car maybe 2-4 times but each time I lock the doors when I leave the car/unlock to enter the car.
A 50/50 chance of bricking is going to be a hard pass for me with the upgrade to 3.4 and who knows when Ford will provide another update for my 3.0 - the current 23219 just came out and the one before that was December 2020.
I truly doubt we’ll see another update for 3.0.x or 3.4.x (and some will disagree) other than maps.
A Fusion APIM in a 2017+ only takes about 20 minutes to change out, so if you ever go looking for one from a Fusion a KS7T-14G370-BCH is a 2019 NAV unit.
You can pretty much use any model’s APIM, if you buy one with the screen one from a Fusion/MKZ/pre MY2020 Escape or MKC/F150 will work. For whatever reason units from the 2018-2019 Escape tend to be $30-$50 cheaper than units from a Fusion/MKZ
Since I have a license for NA.2.23 NAV, how do I use that license file with the SYNC3.4 update with NA 2.23 map package in Syn3 updater?
If you have a license, there is no reason to use Syn3 Updater.
Syn3 Updater does not have this functionality.
So can I still install 3.4.23188 and NA.2.23 using Syn3 updater on my 3.0.23219 and just not use the license?
Not sure why you would buy a license and than use a free program to reformat and install it.
I recommend following Ford’s instructions for when you buy the maps and get a license.
If you read the thread from the start, I’m the OP asking about how to get rid of the error message after the Ford Nav update package messed up while following their instructions. I didn’t realize Cyan Labs had the Nav packages for free, otherwise I wouldn’t have paid the $109 for the license. I had no intention of updating to SYNC 3.4 although I have heard of it in the past. So this is me now asking if I needed to use my license to get NA.2.23 NAV with the Cyan 3.4 update, and apparently the Reformat install method negates the need for the license unless I am mistaken.
Anyway, to answer the license file question.
To go from 3.0 to 3.4 you have to reformat and you want to install the maps as part of it otherwise you’re going to boot back up with a NAV fault because the maps won’t be there.
No license file is used or required when you reformat, you’re basically repeating the process used when the APIM was made at the factory and the software loaded.
In a “normal” map update the installer reads the license file (which is actually a certificate with the VIN & ESN in it), installs it on the APIM and the subsystem allows the new maps to be used. Its the only time the license file is read or used in normal use.
So I bit the bullet and took your advice, went with the 3.4.23188 reformat package and NA 2.23 maps. It took only 29 minutes from start to finish (32 minutes total to include the initial reboot from the installation package). Gracenote is now updated.
Nav works fine, and I can confirm some of the major roads were updated. Voice commands for Nav even works, and it shows nearby gas stations, POIs, etc…
Still a tad sluggish, probably because my APIM model is a bit older than the ones I see on YouTube videos showing how much smoother/faster it is.
It now even syncs my GPS clock/time with Daylight Saving time. It bothered me for 7 years that it would sync the clock but not account for DST.
Only 1 bug I noticed w/ SYNC 3.4 is that my WiFi password keeps getting rejected. I tried it a dozen times and it wouldn’t accept it. I think it is either too long or a combination of special characters causes it to not work. But it worked fine with SYNC 3.0.23219 and all the years prior to that, and in fact same WPA2/2.4GHz settings that it worked fine just prior to updating to 3.4 right now. I’m 110% sure it is something to do with the update.
I did see a new message pop up each time saying my vehicle location is being shared, and to pair a device to avoid seeing this message. It’s already connected to Ford Pass, my phone via Bluetooth, etc… I am going to see if it just needs a drive cycle or something to reset that message. But it goes away by itself without user intervention at the moment, just seems to pop up during each startup.
And yes I followed the Cyan Labs instructions to a “T”. Did the Master Reset and everything.
Losing Bluetooth or wireless credentials is normal after a reformat and expected, delete the version on your phone then re-add after re-starting your phone…
Yes I did both before I even attempted to use the WiFi. It just won’t accept the password.
Regarding the new message, I had cycled the ignition a few times already but still got that weird message. I understand why I got it the first time during the fresh start, but not after connecting Bluetooth and Ford Pass. I’ll keep an eye on it.
In the meantime I just turned WiFi off in the car as I don’t see a need for it. It never ever updated SYNC properly via WiFi and I’m sure with the 3.4.23188 update I don’t think Ford would recognize this is an official install.
FYI this was the solution if this type of question ever comes up in the future! The Syn3 updater package was far more seamless than the official Ford packages.
The message started showing up after GM got hit with the suit for selling OnStar vehicle data, at some point in Ford Pass you should have seen a lengthy terms and conditions popup that you had to agree to.
If you go into settings and turn off Sync diagnostic data, etc where the system sends anonymized data up to Ford it usually goes away.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.