Hello all! Having a strange problem with Errors after installing 3.4. Have done about everything

Ford SYNC 3 Support CyanLabs Update Support
, , , , , ,
1

Hey all. My first post here so I want to let everyone know how much I appreciate the help this board has offered. Now to get into things let me give you the backstory

I bought a Used 2019 F250 about 2 years ago. It had Sync 3.0 and it was dog laggy. I found this place back then and was able to use the updater to install 3.4 23088

It seemed to work perfect on day one, but then after a few months it started losing bluetooth connection to my phone. I ignored it and just used my usb cable after that to get Apple carplay working.

Shortly after that occasionally I would get a popup to update sync OTA and to connect to wifi in order to do so. I would go through the motions of connecting to wifi and checking for updates, but it never did a thing.

Eventually this became the issue every time I started the truck. I jumped back on here (about a year has elapsed by then) with hopes of finding a fix. It appeared there was a newer version of 3.4 so I got my USB stick out and attempted to install it. I got the “INSTL_ERR12” error code.

I messed with it on and off for a few days and put it on the back burner. Now (Another year later) I am determined to get this thing fixed but am running into a wall no matter what I do. Let me outline what I have done so far.

Disconnected the battery for 5 mins. Attempted a “Master Reset” which doesnt work. The screen freezes up so i have to do a soft reset.
Tried the official FORD update via USB from their website after I entered my VIN. INSTL_ERROR12.
I attempted the Interrogater log USB but was met with the INSTL_ERROR12 again.
I attempted the RW Data Cleaner USB and got the same error code
I attempted to remove Gracenotes and get the same error code.
I attempted the Downgrade option and got the same error code.
I tried 4 different USB sticks and made sure they were formatted and had MBR. 3 of these USB sticks were new in the package.
Finally, I tried to Jailbreak it. I never get to the “PKG ERROR5” when attempting it, just the same INSTL_ERROR 12.

I really dont want to purchase a new APIM if I dont have to. Has anyone run into this before?

As a side note, All of my Sync services work perfectly. GPS, WIFI, radio, backup cam, seats, etc.

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.20204

New SYNC Version: 3.4.23088

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.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 Home (2009)

PREVIOUS CONFIGURATION
Version: 3.4.23088
Region: NA
Navigation: True
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Disabled / Not MY20

DESTINATION DETAILS
Mode: Drive
Model: PNY USB 3.2.1 FD USB Device
Size: 115.5GB
FileSystem: exFAT
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.13.0.0 Stable - Autoinstall Mode - RWData Cleaner 

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1= SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Options = AutoInstall


FILES (1)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)

LOG
[1/17/2025 2:14:49 PM] Selected Region:  - Release: RWData Cleaner - Map Version:  
[1/17/2025 2:14:49 PM] Install Mode: Auto-Detect (autoinstall) Forced: False 
[1/17/2025 2:14:49 PM] MY20 Protection: Disabled / Not MY20 
[1/17/2025 2:14:49 PM] Formatting USB drive
[1/17/2025 2:14:49 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[1/17/2025 2:14:55 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/17/2025 2:14:55 PM] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[1/17/2025 2:14:55 PM] Preparing USB drive
[1/17/2025 2:14:55 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/17/2025 2:14:55 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/17/2025 2:14:55 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/17/2025 2:14:55 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[1/17/2025 2:14:55 PM] Generating Autoinstall.lst
[1/17/2025 2:14:55 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!
2

Hello.

Well, that’s your issue… that’s one of the builds that have a bug where the rwdata partition gets full, causing all those issues you are having…

All known methods for recovering from that are located here → APIM Sync Settings Not Saving, VER_ERR08 Errors, Cannot Perform Master Reset or Upgrades/Updates (Solved) .

If none of those work, not even the legacy ones, sadly we do not have anything else to recommend at the moment.

3

Thanks for the quick reply SandMan. Ill keep chugging along and try some of the legacy methods

4

I remember back in the day that the multiple SR → SR → MR combo worked for some users, and that for some it took maaaaany consecutive attempts to work…

I hope some of those work for you…

I’ll now mark this thread as resolved, but it will be kept open for 7 days, which I believe is plenty of time for you to try stuff and come back to us with the results.

5

Due to the fourth paragraph in your initial comment I suggest that you disable automatic updates and wifi as once you go down the Cyanlabs track you are no longer under the Ford ‘fold’ and their updates no longer work or apply to you.
That is why you were getting ‘pop ups’ from Ford with subsequent unsuccessful updates.

Also the ‘technology’ could possibly get confused due to Ford trying to update a 3.0 version through wifi as you already had version 3.4.23088.
As you are probably aware Cyanlabs do not do OTA updates.

From now on only Cyanlabs updates for your 3.4 version apply.

However there probably will not be a later version than the last 3.4.23188 for your car (and mine) but updated maps should still apply.

Hopefully you will resolve your issues with suggestions from @SaNdMan.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.