Trying to update Sync 3-ERR12

Hello. I just bought my son a 2018 Escape. We aren’t able to delete the old owner’s bluetooth information or make his the primary bluetooth. We’ve tried master reset, fuse pulling, battery disconnecting and nothing works. I couldn’t run an update via wifi or usb, so I tried the sync 3 updater. I put all the information in correctly, but I’m getting error code 12!

Is there anything else I can try?


SYNC Region: NA

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?
ERR12

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: V2.13.0.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

CYANLABS - SYN3 UPDATER - V2.13.0.0
Branch: Stable
Operating System: Microsoft Windows 11 Pro (2009)

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

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

REFORMAT.LST
VOICE=5U5T-14G391-CS_1660783942000.TAR.GZ
GRACENOTES=4U5T-14G423-CC_1615429225000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.13.0.0 Stable - reformat  Mode - Sync 3.4.23188 NA

[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 (5)
1u5t-14g386-cb.tar.gz (8.5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
5U5T-14G391-CS_1660783942000.TAR.GZ (385.5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)

LOG
[9/30/2024 1:24:58 PM] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: Non Nav APIM 
[9/30/2024 1:24:58 PM] Install Mode: Auto-Detect (reformat) Forced: False 
[9/30/2024 1:24:58 PM] MY20 Protection: Auto-Detect 
[9/30/2024 1:24:58 PM] Formatting USB drive
[9/30/2024 1:24:58 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[9/30/2024 1:25:07 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[9/30/2024 1:25:07 PM] Downloading: 1u5t-14g386-cb.tar.gz
[9/30/2024 1:25:09 PM] Validating: 1u5t-14g386-cb.tar.gz 
[9/30/2024 1:25:09 PM] Downloaded: 1u5t-14g386-cb.tar.gz 
[9/30/2024 1:25:09 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[9/30/2024 1:25:09 PM] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ
[9/30/2024 1:25:09 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[9/30/2024 1:25:09 PM] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ 
[9/30/2024 1:25:09 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[9/30/2024 1:25:09 PM] Downloading: 5U5T-14G391-CS_1660783942000.TAR.GZ
[9/30/2024 1:25:17 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[9/30/2024 1:25:18 PM] Downloaded: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[9/30/2024 1:25:18 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[9/30/2024 1:25:18 PM] Downloading: 4U5T-14G423-CC_1615429225000.TAR.GZ
[9/30/2024 1:25:30 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[9/30/2024 1:25:32 PM] Downloaded: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[9/30/2024 1:25:32 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[9/30/2024 1:25:32 PM] Downloading: NU5T-14G381-AD_1689364279000.TAR.GZ
[9/30/2024 1:25:52 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[9/30/2024 1:25:55 PM] Downloaded: NU5T-14G381-AD_1689364279000.TAR.GZ 
[9/30/2024 1:25:55 PM] Preparing USB drive
[9/30/2024 1:25:55 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[9/30/2024 1:25:55 PM] Copying: 1u5t-14g386-cb.tar.gz 
[9/30/2024 1:25:55 PM] Validating: 1u5t-14g386-cb.tar.gz 
[9/30/2024 1:25:56 PM] Copied: 1u5t-14g386-cb.tar.gz 
[9/30/2024 1:25:56 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[9/30/2024 1:25:56 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[9/30/2024 1:25:56 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[9/30/2024 1:25:56 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[9/30/2024 1:25:56 PM] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[9/30/2024 1:25:56 PM] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[9/30/2024 1:26:26 PM] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[9/30/2024 1:26:41 PM] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[9/30/2024 1:26:41 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[9/30/2024 1:26:41 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[9/30/2024 1:27:24 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[9/30/2024 1:27:46 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[9/30/2024 1:27:46 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[9/30/2024 1:27:46 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[9/30/2024 1:28:55 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[9/30/2024 1:29:28 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[9/30/2024 1:29:28 PM] Generating reformat.lst
[9/30/2024 1:29:28 PM] Generating autoinstall.lst
[9/30/2024 1:29:28 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY! 

Master reset should take everything in the APIM for BT back to factory.
If this isn’t working it sounds like a bad APIM.

For the reformat USB you really want to make sure you’re using a good quality unit (eg PNY, San Disk, Lexar, etc) and nothing should be plugged into the other USB port, not even a charge cable.

Hello.

If this is in fact the current version, most likely the unit has some kind of memory problem that won’t be solved since it’s a hardware damage. I mean, if it does not master reset and no information is erased, that’s quite a sign the unit is unhealthy.

There’s not much you can do, really… Even if the update to 3.4 works it may “hide” the issue for the moment (that memory not being used) or it can actually end up killing the unit…

I did 2 soft resets and a master reset before I put the USB in and no go. Still the ERR12 code. Ugh. The system actually works great, other than the bluetooth issue, which is very annoying. Now I’m trying to weigh whether or not it makes sense to replace the entire unit!

Have you tried another USB drive. Preferably a name brand like Sandisk, PNY, or the like. I found that my Ford is very particular about the USB drive I use and it does not matter if it is for updates or play music.

Just be prepared that the update may brick the unit if the unit has significant enough problems. If the internal drive has only a few bad spots, a reformat may fix things by mapping the format around the bad spots. If there are a lot of bad spots, then the reformat may not leave enough room for the operating system. If a drive is developing bad spots, it may not be long before more develop and you have more problems. In any case, if you are prepared to replace the unit, then you are ahead if it fixes it.

If you’re going to replace the APIM its pretty easy to do yourself on an Escape, the APIMs are pretty much vehicle agnostic as long as you stay in the same model year or higher. The Asbuilt for your vehicle will need to be loaded into the replacement unit.

With regard to sourcing one from a yard or eBay I would do so now before the flood damaged cars from Helene start hitting the yards.