When installing the SYNC 3 update, the following error is reported: INSTL_ERR12

[jguarin (Jonathan Guarin)]

My 2018 Ford currently has SYNC 3.0 software, but Apple CarPlay and other features have stopped working. I performed the update process using the Syn3 app and downloaded it to a USB drive. When I connected the drive to the car and updated, the following error appears: INSTL_ERR12

---

SYNC Region: ANZ

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.17276

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
INSTL_ERR12

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.13.1.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

YANLABS - SYN3 UPDATER - V2.13.1.0
Branch: Stable
Operating System: Microsoft Windows 11 Home Single Language (2009)

PREVIOUS CONFIGURATION
Version: 3.0.17276
Region: ANZ
Navigation: False
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: General UDisk USB Device
Size: 14.6GB
FileSystem: exFAT
Partition Type: MBR

REFORMAT.LST
VOICE=5U5T-14G391-BS_1660772122000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.13.1.0 Stable - reformat  Mode - Sync 3.4.23188 ANZ

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1 = SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = REFORMAT TOOL  - 1u5t-14g386-cb.tar.gz
Open2 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

FILES (4)
1u5t-14g386-cb.tar.gz (8.5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
5U5T-14G391-BS_1660772122000.TAR.GZ (1.4GB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)

LOG
[18/03/2025 04:33:35 p. m.] Selected Region: ANZ - Release: Sync 3.4.23188 - Map Version: APIM sin Navegación 
[18/03/2025 04:33:35 p. m.] Install Mode: Auto-Detect (reformat) Forced: False 
[18/03/2025 04:33:35 p. m.] MY20 Protection: Auto-Detect 
[18/03/2025 04:33:35 p. m.] Formatting USB drive
[18/03/2025 04:33:35 p. m.] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[18/03/2025 04:33:43 p. m.] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[18/03/2025 04:33:43 p. m.] Downloading: 1u5t-14g386-cb.tar.gz
[18/03/2025 04:33:47 p. m.] Validating: 1u5t-14g386-cb.tar.gz 
[18/03/2025 04:33:47 p. m.] Downloaded: 1u5t-14g386-cb.tar.gz 
[18/03/2025 04:33:47 p. m.] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18/03/2025 04:33:47 p. m.] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ
[18/03/2025 04:33:47 p. m.] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18/03/2025 04:33:47 p. m.] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18/03/2025 04:33:47 p. m.] Checking Existing File: 5U5T-14G391-BS_1660772122000.TAR.GZ 
[18/03/2025 04:33:47 p. m.] Downloading: 5U5T-14G391-BS_1660772122000.TAR.GZ
[18/03/2025 04:42:30 p. m.] Validating: 5U5T-14G391-BS_1660772122000.TAR.GZ 
[18/03/2025 04:42:34 p. m.] Downloaded: 5U5T-14G391-BS_1660772122000.TAR.GZ 
[18/03/2025 04:42:34 p. m.] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18/03/2025 04:42:34 p. m.] Downloading: NU5T-14G381-AD_1689364279000.TAR.GZ
[18/03/2025 04:45:29 p. m.] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18/03/2025 04:45:31 p. m.] Downloaded: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18/03/2025 04:45:31 p. m.] Preparing USB drive
[18/03/2025 04:45:31 p. m.] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[18/03/2025 04:45:31 p. m.] Copying: 1u5t-14g386-cb.tar.gz 
[18/03/2025 04:45:31 p. m.] Validating: 1u5t-14g386-cb.tar.gz 
[18/03/2025 04:45:32 p. m.] Copied: 1u5t-14g386-cb.tar.gz 
[18/03/2025 04:45:32 p. m.] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18/03/2025 04:45:32 p. m.] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18/03/2025 04:45:32 p. m.] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18/03/2025 04:45:32 p. m.] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[18/03/2025 04:45:32 p. m.] Checking Existing File: 5U5T-14G391-BS_1660772122000.TAR.GZ 
[18/03/2025 04:45:32 p. m.] Copying: 5U5T-14G391-BS_1660772122000.TAR.GZ 
[18/03/2025 04:46:46 p. m.] Validating: 5U5T-14G391-BS_1660772122000.TAR.GZ 
[18/03/2025 04:47:21 p. m.] Copied: 5U5T-14G391-BS_1660772122000.TAR.GZ 
[18/03/2025 04:47:21 p. m.] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18/03/2025 04:47:21 p. m.] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18/03/2025 04:48:08 p. m.] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18/03/2025 04:48:31 p. m.] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[18/03/2025 04:48:31 p. m.] Generating reformat.lst
[18/03/2025 04:48:31 p. m.] Generating autoinstall.lst
[18/03/2025 04:48:31 p. m.] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY! 

[warlock12118]

Are you sure that you had 3.0.17276?
CP wasn’t supported completely until 3.0.22x
If it was working and then stopped I would be looking at the USB cable and/or the USB media hub since if either of those has issues CP is not going to work correctly.

[F150Chief]

This error is usually due to a hardware failure but try this…

There is a reset procedure for Sync of performing 2 reboots in a row, one right after the other, that can clear errors and free memory being used by temporary files. This is effective for the BGMAP and other errors also. Using the Soft Reset option will free up some storage/memory for the short term in perform a reformat and/or upgrades/downgrades. This procedure does not normally clear any user settings, stored phones, nav destinations, etc.

1. If possible, perform a Master Reset under Settings > General > Reset. This may not be possible, and the unit will hang. If the unit hangs while trying to perform a Master Reset, try performing a key cycle first to see if that helps completing the Master Reset. Continue with the steps below.
2. Once the unit has fully rebooted, perform two soft reboots in a row.
3. Hold the power button and next track (seek >) button on the center console interface at the same time for about 5 seconds or until the screen goes black. The APIM will reboot, and the system will restart.
4. Once the first soft reboot is done, perform the second soft reboot as above.
5. Once the system is back up after the second soft reboot, try to run the update, etc.

There is another method of this using FORScan to reset the APIM a couple of times. This is effectively the same as above. Be aware that this procedure will not completely clear the /fs/rwdata logs but will usually make enough free space to be able to run the reformat tool or upgrades. The upgrade (or downgrade) process will not clear the /fs/rwdata partition. It is recommended that you perform a reformat or run the scripting to clear the left-over logs and data from the rwdata partition.