INSTL_ERR12 When trying to update sync

Hi, I have a 2018 Mustang, and ever since I upgraded my phone, the apple carplay has stopped working. I called Ford, and they told me I have to update sync with a USB drive, but when I tried to plug in the drive, it gave me INSTL_ERR12. I called Ford back, and they’re saying I need to take the car to the dealership.

Has anyone experienced a similar issue? And is there any other way to update sync? Thanks!

This is usually due to a hardware issue with the Sync APIM. There is not a known solution other than replacing the module.

2 Likes

Lets start with what build of Sync are you on now? (on the screen, General, About Sync)
Is anything plugged into the other USB port, there shouldn’t be anything not even a charging cable?
Have you tried the other USB port?

1 Like

The current version is sync 3.0.17276 trying to update to 3.0.23219. I have tried both USB ports and nothing was plugged into any of the ports. When I connect my phone I get the Carplay Privacy & Terms of Use, but nothing happens after clicking agree.

Does master reset work?. If so, do that, then create and run an interrogator log and share the xml with us. If master reset does not work, try running the interrogator nevertheless.

master reset works. but when i plug in the interrogator usb drive im still getting the same error code 12.

Then it’s likely to be a hardware issue, as previously said.
You may want to start considering having it replaced.

1 Like

I know some folks will say its not needed, but try creating a USB to get you to 2.2.17011 first, then try going to 3.0.23219. v2.2 was the first version to fully supported CP with an updated USB hub.

What does CP have to do with an APIM that “rejects” package execution/manipulation with INSTL_ERR12 ?

Maybe you posted in the wrong thread ?

The OP is on 3.0.17276.
Personal experience here is that I’ve seen CP issues being on the 3.0.17xxx with iPhone 15/16. Its also not terribly unusual to see a fail trying to go from that build directly to 3.0.23219, dropping in 2.2.17011 as a midpoint in the process for whatever reason lets the APIM update to 3.0.23219 successfully.
Its something that takes all of 15 minutes to try which if it fixes the issue is way easier and cheaper than replacing an APIM

Ok so I tried to dropping in 2.2.17011 and now its giving me code LST_ERR05.

LST_ERR05 – Error is LST_PKG_FILE_NOT_FOUND

Your autoinstall file has errors.