SYNC3 3.0.23219 - NAV NA 2 23, "Installation in Progress" error message

Ford SYNC 3 Support
, , , , ,
1

I recently updated my 2017 Fusion Sport (SYNC3 Factory) to the 23219 official release. No issues with the update. I decided to buy the NA 2 23 Nav update (to update from my NA 1 15 NAV file), and ran the update. It took about 45 minutes. I checked on the car about 35 minutes into the install and it was still Updating Software. But at 45 minutes I went down and saw the screens were all black. I turned on the car and it said it was done, I could pull out the USB and let it perform 1 key cycle or something to that effect. But afterwards I’d get the “Installation In Progress some features will continue to be disabled until this process is complete. Please keep the update USB in the system and the engine running so that it can complete.” error message every single time I start the vehicle.

It turns out it never installed the 14G422 voice package, and somehow Gracenotes would not show a version in the ABOUT SYNC menu. I manually installed the 14G422 voice package, re-installed Grace Notes (1.1.1139 NA-0010 seems to be the latest for my SYNC 3.0), and can confirm the Navigation Voice commands actually work, and I see the Gracenotes version number. However, I still see this error message.

I’ve tried a SYNC Master Reset without any impact.

I’ve used FORScan to reset the APIM, no impact.

I’ve deleted Gracenotes using CYANlabs’ tool, and re-installed, no impact.

I’ve downgraded to 202xx (whatever version that was most recent before this one, Ford Part # suffix is -AX). and upgraded back to 23219 (-AY) and no impact.

As far as I can tell, everything installed correctly but its just flagged as an incomplete install.

Does anyone have any ideas on this? Seems silly that there’s no way to manually remove this incomplete install flag, or have it reset after a re-install. The SYN3 Updater doesn’t have any packages for 3.0 only for 3.2/3.3/3.4 which I don’t think I’d want to use on my 2017 APIM.

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.23219 / NA 1 15 NAV

New SYNC Version: 3.0.23219 / NA 2 23 NAV

Do you have a error message, if so what is it?
Installation In Progress some features will continue to be disabled until this process is complete. Please keep the update USB in the system and the engine running so that it can complete.

Update Method: Official Ford

2

If you really want to stay on 3.0, create and run an interrogator log against the unit and share the produced XML file with us.

Also, provide the autoinstall.lst file that you tried running on the unit for upgrading all those packages that you mentioned. I guess Ford provided that for you.

Finally, map upgrades usually take a long time and later Sync3 must “process” them in the background, we had some reports of that before and eventually it fixes itself.

But lets not assume, lets see what’s on the unit.

1 Like
3

I used several different autoinstall.lst files to do the manual installs. Basically for the Options I’d use AutoInstall, Delay

I have the Interrogator Log but its on my computer at home, all the packages checked out with the NA 2 23 NAV Update, as well as the 23219 -AY package.

I did take a photo of the IVSU screen in my SYNC so I have that right now if that helps:

JR3T-14G381-AY 3.0.23219 no hash

JR3T-14G391-CE 3.2.19056 14768…

JR3T-14G423-CB 3.0.17024b3bf9…

JR3T-14G421-CJ 3.2.24003 a01fa…

JR3T-14G422-CM 3.2.24003 fc8088…

That’s all the packages in the IVSU menu, and from what I recall in the Interrogator log as well. I’ll post the XML contents once I am able to do so.

I’d be open to upgrading to a 3.2 or higher as long as it doesn’t brick my APIM and is easy to do. While it is a 2017 Fusion Sport I believe most of the hardware is from 2016 and its all original.

4

When the install routine runs on 3.0.x NA2.23, it looks for the license file which is ESN/VIN locked just like the 3.4.x NA2.23 so it will fail without a reformat.

If you don’t have a valid license subscription the highest you’ll be able to go is NA2.20 as that version did not require a license file, unless you jailbreak the unit and use the FMods map remover/update tool…

1 Like
5

Since I purchased it from Ford, it did come with the license file for my VIN and ESN, and it was installed prior to the map file according to the autoinstall.lst file. I followed the instructions Ford provided for inserting that file (14G424) into the SyncMyRide folder.

It seems there are 2 parts to the NA.2.23 install. The first part loads some tools as well as the license and then a message pops up on the SYNC screen to basically cycle the ignition. I believe that is when it starts to upload the main map package (10GB or so) followed by the Voice and Gracenote packages (which is still 1.1.1.1139 NA 010 same as what I had for years).

I can use the Navigation and maps just fine. How would I know if the license file wasn’t accepted/installed correctly?

So far it has been the worst $109 I ever spent to see this error message pop up all the time. Had I just left it at NA 1 15 (which would be like 10 year old maps) it would have been fine.

7

If you have a licensed map update why are you screwing around with the autoinstall ?

The autoinstall just tells the APIM what to load and in what order, you have to look at the log to see what has actually been loaded. The fact that it is in the autoinstall doesn’t mean it actually happened.

When you use a Ford map update you extract the entire zip file to the root of the USB and you then copy the downloaded license file into the SyncMyRide directory. Did you check the directory to see if it was actually there with the same name?

Installation takes roughly 90 minutes from a good quality USB, the tools that are being loaded allow the install to delete each old file and extract the new file to the APIM from the tarball on the USB.

The 2016MY and the 2017MY Fusions are close but not quite the same, the 2016MY was MFT not Sync3 and is actually a one off year for a number of wiring harnesses. Its actually closer to the 2015MY than it is the 2017MY, while the 2013-2015 a Sync3 conversion was pretty straight forward some doing the conversion on the 2016MY had to replace the GWM with one from a 2017MY to get everything working correctly.

9

Yes I understand all of that. But if you look at the autoinstall for the Nav package it starts with all the tools and license, tells you to basically reboot the APIM, and then starts phase 2 which is the maps/voice/gracenote portion (about 13GB).

If I try to run the Nav package now it gives me BGMAP_ERR01, what I haven’t tried to do is do an Options = AutoInstall for the map package. I did that for the voice package and gracenotes package and was able to fix those issues.

So what part of the Interrogator log tells me what packages are loaded? Just the packages section? If so, I already posted it above. I took photos of the IVSU packages list and it matches what I saw in the Syn3 updater interrogator log. I’ll have to post the log later tonight.

JR3T-14G381-AY 3.0.23219 no hash

JR3T-14G391-CE 3.2.19056 14768…

JR3T-14G423-CB 3.0.17024b3bf9…

JR3T-14G421-CJ 3.2.24003 a01fa…

JR3T-14G422-CM 3.2.24003 fc8088…

A lot of the 2017 Fusions were made in 2016, which is why I made the comment about the 2016 hardware. They switched to 2018 sometime around mid 2017.

Mine has the Sync Connect / FordPass capability which was the first year if I recall. My 2014 Taurus SHO had MFT so I know the difference. But 2017 doesn’t show tire pressures on Ford Connect’s app, I recall only 2018 and newer shows that.

10

Here’s the Interrogator Log with NA.2.23 installed. Note that I also have the log that Ford’s 3.0.23219 created and looked at it. Other than a few updated packages (14G421, 14G424, 14G422) they are identical.

NA.2.23
VIN:
Version JR3T-14G381-AY
APIM Model: HP5T-14G371-CCA
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 7.7G
5/27/2024 12:18:58 +00:00

Partition Type = Free / Total
/fs/usb0/ = 16G / 30G
/fs/tmpfs/ = 127M / 128M
/fs/sd/MAP/ = 14M / 10G
/fs/Nuance/ = 15M / 5.3G
/fs/Nuance/ = 2.5M / 482M
/fs/Nuance/grace = 5.1M / 1.0G
/fs/rwdata/ = 644M / 1024M
/fs/mp/ = 40M / 1024M
/fs/images/ = 7.7G / 26G

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

APIM AsBuilt
DE00: AA2A01030E028B00168A
DE01: 55530101C002409000000005
DE02: 0000000200
DE03: 01000200030001
DE04: 1AC21AA42BD0
DE05: 80
DE06: 07003300000000171C000056566D006A

13

You can’t just install the map files, the installer blocks it.

Last time I had this using a factory set was NA2.20 on my 2018 Fusion and it was because I pulled the USB early.

So…

  1. use a good quality USB drive (Sandisk, Lexar, PNY) wuth a high read speed
  2. unplug anything else plugged into the other USB port, even a charging cable
  3. Run the official update again from scratch. If you’re going to let the car idle turn off the 30 minute idle timer. If you’re going to drive it, DON"T TOUCH THE CONTROLS FOR ANYTHING AFTER IT STARTS, this means the screen, HVAC, volume or station so get everything set before you plug it in. When you touch the controls it will cause the “Updating System Software” banner to go away for a period of time, I’ve seen it disappear for as long as 15 minutes even though the map update is still running.
  4. When it tells you to unplug the USB and cycle the ignition at your next convenience WAIT 5-10 minutes to give the install time to close files and finish any writes. If it restarts on it’s own the install routine is still running and has moved to the next stage, don’t cycle the ignition.
14

It won’t run the official update, I get a BGMAP_ERR01 like I mentioned above. I can absolutely install the other individual packages using AutoInstall but I haven’t tried the Map package itself (10GB).

I am using a Samsung 32GB USB 3.0 flash drive. Has worked fine for all of my updates so far (3.0.23219 etc)

I’ve tried other high quality flash drives in the past and the car is finnicky. SanDisk 64GB USB3.0 won’t run at all. I once had to buy a brand new SanDisk USB 2.0 to make it work with the car even though USB2.0 drives were hard to find.

15

Here’s the AutoInstall file for the NAV package
[SYNCGen3.0_2.0.16074_PROD]
Item1 = LU5T-14G386-BB
Open1 = SyncMyRide\LU5T-14G386-BB.tar.gz
Item2 = HB5T-14G386-TAC
Open2 = SyncMyRide\HB5T-14G386-TAC.tar.gz
Item3 = HB5T-14G386-TKC
Open3 = SyncMyRide\HB5T-14G386-TKC.tar.gz
Item4 = JR3T-14G424-CJ
Open4 = SyncMyRide\JR3T-14G424-CJ.tar.gz
Item5 = GB5T-14G386-ZA
Open5 = SyncMyRide\GB5T-14G386-ZA.tar.gz
Options = AutoInstall

[SYNCGen3.0_2.0.16074]
Item1 = JR3T-14G421-CJ
Open1 = SyncMyRide\JR3T-14G421-CJ.tar.gz
Options = AutoInstall, Include, Transaction

[SYNCGen3.0_ALL]
Item1 = JR3T-14G421-CJ
Open1 = SyncMyRide\JR3T-14G421-CJ.tar.gz
Item2 = JR3T-14G422-CM
Open2 = SyncMyRide\JR3T-14G422-CM.tar.gz
Item3 = JR3T-14G423-CB
Open3 = SyncMyRide\JR3T-14G423-CB.tar.gz
Options = Delay, Include, Transaction

Here’s the autoinstall for 3.0.23219
; SYNC3 Consumer Assembly Upgrade - Release 3.0.25 - Only for Nav/NA assemblies.

[SYNCGen3.0_3.0.20204_PRODUCT]
Item1 = HB5T-14G386-THB
Open1 = SyncMyRide\HB5T-14G386-THB.tar.gz
Item2 = HB5T-14G386-TCC
Open2 = SyncMyRide\HB5T-14G386-TCC.tar.gz
Item3 = JR3T-14G381-AY
Open3 = SyncMyRide\JR3T-14G381-AY.tar.gz
Item4 = GB5T-14G386-AE
Open4 = SyncMyRide\GB5T-14G386-AE.tar.gz
Options = AutoInstall,Delay

The 14G391-CE package that’s loaded is from the -AY SYNC update (2019 DEC) - no other packages include an update for this file.

; SYNC3 Consumer Assembly Upgrade - Release 3.0.21 - Only for Nav/NA assemblies.

[SYNCGen3.0_3.0.19205_PRODUCT]
Item1 = HB5T-14G386-THA
Open1 = SyncMyRide\HB5T-14G386-THA.tar.gz
Item2 = HB5T-14G386-TCB
Open2 = SyncMyRide\HB5T-14G386-TCB.tar.gz
Item3 = JR3T-14G391-CE
Open3 = SyncMyRide\JR3T-14G391-CE.tar.gz
Item4 = JR3T-14G381-AS
Open4 = SyncMyRide\JR3T-14G381-AS.tar.gz
Item5 = HB5T-14G387-AAB
Open5 = SyncMyRide\HB5T-14G387-AAB.tar.gz
Item6 = GB5T-14G386-AB
Open6 = SyncMyRide\GB5T-14G386-AB.tar.gz
Options = AutoInstall,Delay

16

If you go to syncmyride.com what build of Sync3 does it think your VIN is currently on?
Which of the above is the actual untouched official autoinstall included in the map package?

  1. Reformat the USB as exFAT, follow the prep instructions and reload the drive.
  2. Do a master reset on the APIM
  3. Do a hard reset of the APIM twice (you can do this via the button method, Forscan or by pulling the battery cable for 15 minutes)
17

Ford says I am running 3.0.23219 (Which I am).
The very first autoinstall is part of the Super Official Ford NAV package (as I mentioned) which is NA.2.23

I had already reformatted the USB as exFat. It’s read by the car just fine. This samsung 32GB USB3.0 works just fine.

I know when a USB drive doesn’t work with the car because it just won’t work, or I used to get a low-power error message. The error messages must have been fixed with a SYNC update sometime in 2018-2020 because I haven’t seen it since - it just doesn’t work with some flash drives like the SanDisk 64GB USB3.0 (zero LED light/activity).

18

So I just followed the instructions in that video and still got the same BGMAP_ERR01 message.

19

OK, let’s try this.
Option 1, take it to Sync 3.0.2.16074 with a custom install, try installing the maps then bring it back up to current. HB5T-14G381-AJ - SYNC 3 APIM Software (IVSU) Database - CyanLabs

Option2, Change the header on the 1st group to [SYNCGen3.0_ALL] and remove the second group

It’s strange that the install is trying to install the map (14G421-CJ) twice, I’ve also never seen a NAV update that includes a GraceNotes update (14G423) as that is normally part of the APP update. I’ve also never seen LU5T-14G386- in Sync 3.0.x package, only Sync 3.4.x

Here’s what I have in the Ford official package for .23219, Ford “thinks” my 2018 Fusion Platinum is on 2.3.17109.

; SYNC3 Consumer Assembly Upgrade - Release 3.0.25 - Only for Nav/NA assemblies.

[SYNCGen3.0_3.0.20204_PRODUCT]
Item1 = HB5T-14G386-THB
Open1 = SyncMyRide\HB5T-14G386-THB.tar.gz
Item2 = HB5T-14G386-TCC
Open2 = SyncMyRide\HB5T-14G386-TCC.tar.gz
Item3 = JR3T-14G391-CE
Open3 = SyncMyRide\JR3T-14G391-CE.tar.gz
Item4 = JR3T-14G381-AY
Open4 = SyncMyRide\JR3T-14G381-AY.tar.gz
Item5 = JR3T-14G423-CB
Open5 = SyncMyRide\JR3T-14G423-CB.tar.gz
Item6 = GB5T-14G386-AE
Open6 = SyncMyRide\GB5T-14G386-AE.tar.gz
Options = AutoInstall,Delay

20

I posted my official 23219 package contents, but the one you posted adds 14G391-CE which is from -AS (DEC 2019?) release and yours also has 14G423-CB which is from the JUL 2019 release (-AM). My guess is whomever posted that “official package” was missing those earlier updates??

I can see 3.0.23219 in my About SYNC screen as well as on Ford. You’re supposed to upload the Interrogator log that is automatically generated, once that happens Ford’s website will show your correct version.

I already downgraded to 3.0.20xx (the one before 23219) and tried installing Maps buit get the BGMAP_ERR01 message.

I’ve tried changing the headers as well but that didn’t do anything. If I leave the headers as is, it will still perform those updates which reboots the SYNC system automatically.

The Gracenotes update isn’t really an update. It’s part of an old SYNC package (JUL 2019). I also know this because it is the same version as before 1.1.1.1139 NA010.

Is the LU5T-14G386-BB supposed to be a reformat tool? It’s only 40 kB in my NAV upgrade package. I see the ones on CyanLabs being 8MB or so.

I paid $109 from Ford and that’s the NAV file package I received/downloaded. It’s possible they screwed up somewhere.

That being said… I can confirm there’s a new part of the freeway in my area that was completed in 2017 (the highway exits on the right instead of the left) and the NA.2.23 shows this.

I cannot confirm if the voice commands works, but when 14G422 didn’t show up in the Interrogator Log or IVSU, telling SYNC “Navigation” and trying to do anything just crashed it. Now with 14G422 loaded, it will allow me to search for place/address but works like garbage. I ask for Gas or Hospitals and it tells me there’s nothing nearby. But if I manually click through to find stuff, the POIs will show up.

21

The autoinstall I posted is from what I had just downloaded from Ford.
https://ivsu.binaries.ford.com/owner-package/7143052462/JR3T-14G381-AY.zip

Funny little fact here, the zip file is named the same whether its NA/NAV, Non-EU/non-NAV, etc what matters is the package download location, the contents for each package location is different.

LU5T-14G386 is a Sync 3.3 specific tool which queries the APIM to see if it is a model that Sync 3.2+ shipped on, if that is present in the package its doing a pass/fail check. An official 3.2.x install on a 3.0.x APIM will throw an incompatible hardware warning, if this is in the map update I would imagine it’s doing the same thing as the map files are named differently for 3.0.x vs 3.2.x+.

22

I bet the file you downloaded from Ford was intended to be a block upgrade to take a much older version of SYNC3.0 to 3.0.23219 because I see it is 1.5GB

My official 23219 package from Ford direct download was only like 480MB. I believe something happens on Ford’s backend where you are expected to enter your VIN and they pick the package/files to send you. I’ve always uploaded my interrogator logs so they were tracking the latest version for my 2017 Fusion.

Here’s the autoinstall for 3.0.23219 (official -AY release that Ford lets me download after I log into SYNC My Ride)

; SYNC3 Consumer Assembly Upgrade - Release 3.0.25 - Only for Nav/NA assemblies.

[SYNCGen3.0_3.0.20204_PRODUCT]
Item1 = HB5T-14G386-THB
Open1 = SyncMyRide\HB5T-14G386-THB.tar.gz
Item2 = HB5T-14G386-TCC
Open2 = SyncMyRide\HB5T-14G386-TCC.tar.gz
Item3 = JR3T-14G381-AY
Open3 = SyncMyRide\JR3T-14G381-AY.tar.gz
Item4 = GB5T-14G386-AE
Open4 = SyncMyRide\GB5T-14G386-AE.tar.gz
Options = AutoInstall,Delay

I just did a drive using SYNC3 NAV and it was saying all the names of the streets/roads, so I imagine the voice pack was loaded correct. And I mentioned it shows a new section of freeway that was finished in 2017. I doubt NA.1.15 would have this section of the freeway.

So does this mean my Nav package files are “right” and I don’t need to change anything?

And just have to live with a janky “Installation in Progress” error message every time I start the car?

23

I would check the loaded IVSU’s using bezel diagnostics to see if everything matches up.

Have you made any mods to the APIM as built using ForScan?

25

I posted the IVSU bezel diagnostics package list as a reply to one of your posts above

JR3T-14G381-AY 3.0.23219 no hash

JR3T-14G391-CE 3.2.19056 14768…

JR3T-14G423-CB 3.0.17024b3bf9…

JR3T-14G421-CJ 3.2.24003 a01fa…

JR3T-14G422-CM 3.2.24003 fc8088…

No Forscan mods to APIM As-Built. Nothing to really change.