Downgrading Sync 3.4 to 3.3 issues, APIM version blank

Hello,

I’ve recently purchased a used Ford Transit Connect XL 2022 that came with Sync 3 with the 8" touchscreen.

I want to downgrade its Sync version from 3.4 to 3.3 because I cannot stand the safety features that prevent browsing music folders.

Upon running the USB interrogator tool, I get the following for my APIM version:
APIM AsBuilt
DE00: BLANK
DE01: BLANK
DE02: BLANK
DE03: BLANK
DE04: BLANK
DE05: BLANK
DE06: BLANK

I tried taking the dashboard apart with mitigated success. I can’t locate the physical module (not in the glove box, not behind the screen either), and something prevents me from taking everything apart. I don’t want to force it and I can’t find a proper tutorial online.

I’m left with the Forscan option, but I can’t find anywhere how to check my APIM version with the tool. I will figure it out, but it leaves me with this question:

Can I downgrade a unit that shows blank on the APIM version?


SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: MY20

Install Type: Unknown

Old SYNC Version: 3.4.21194

New SYNC Version: 3.4.21194

Do you have a error message, if so what is it?
APIM AsBuilt
DE00: BLANK
DE01: BLANK
DE02: BLANK
DE03: BLANK
DE04: BLANK
DE05: BLANK
DE06: BLANK

Update Method: CyanLabs Manual Method

Additional info after working on it:

Forscan tells me I have a NU5T-12G371-CAA unit, which is a MY20 according to Sync3 updater.

Now, when checking all the options, and going through the update method (not downgrade), I get the USB with 3.4 to 3.3 configuration, run it by the car, get the “update successful, restart the car” message, but when I read back the XML file it tells me:

“The XML file you have selected does not contain a valid ECU delivery asssembly number, do not continue without getting help from an expert”.

May I ask for some help from an expert please?

Hello.

Have you master reset?.

That’s fine, but you do not need Forscan nor Syn3update to reach that conclusion: your vehicle is “Ford Transit Connect XL 2022”, of course it’s MY20…

Since the APIM is MY20 you can’t reformat it, but you can run whatever autoinstall you like on it. So, you can move among 3.3 and 3.4 versions without issues, just make sure the installation method is autoinstall. Keep MY20 protection enabled at all times so that Syn3updater won’t generate a reformat or downgrade USB.

It’s worth mentioning that in the realm of Syn3updater, downgrade means “go to 3.3 and then reformat”, so a downgrade turns into a reformat… YOU CAN’T DO THIS.

But, as I said before, you can install 3.3 which is an autoinstall.
It does not matter if the asbuilt is shown or not.

Please post the full interrogator log…

Thank you for your help.

I have not master reset. Should I?

I have “upgraded” to 3.3, but the system remains the 3.4 interface after restarting the car. However, when I go to the “about” section, Sync does not display the version anymore (which should say 3.4).

I am going to run it again to get the latest interrogation log, and will report back.

Always…

1 Like

Voice commands work much faster here.

1 Like

I don’t understand how. I have 300+ artists by folder, so I’d have to come up with a specific name in mind instead of scrolling briefly to pick. Same for documentaries for long trips; instead of browsing, I’d have to remember the exact folder, name and episode when I don’t really have something in mind.

And with 3.4 as is, I’m stuck with one folder, whichever was picked when I started driving. Impossible to listen to anything else. VERY frustrating.

Alright, so, I have master reset Sync, no dice. Still stuck with 3.4. after updating to 3.3.

Looking into uploading the interrogation file now :frowning:

VIN: NM0GS9E26N1534576
Version 5U5T-14G381-ET
APIM Model: Unknown
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 9.5G
4/21/2024 1:33:06 PM +00:00

Partition Type = Free / Total
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 13M / 1.4G
/fs/sd/MAP/ = 10M / 1.4G
/fs/sd/MAP/ = 2.8M / 937M
/fs/sd/MAP/ = 8.5M / 1.3G
/fs/sd/MAP/ = 14M / 1.7G
/fs/sd/MAP/ = 17M / 1.7G
/fs/sd/MAP/ = 7.2M / 1.4G
/fs/Nuance/ = 23M / 480M
/fs/Nuance/grace = 57M / 1.0G
/fs/rwdata/ = 573M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 132M / 1.4G
/fs/images/ = 9.5G / 25G

Installed Packages
4U5T-14G421-CAD
4U5T-14G421-CBD
4U5T-14G391-CJ
4U5T-14G421-CDD
4U5T-14G421-CCD
4U5T-14G421-CFD
4U5T-14G421-CGD
4U5T-14G421-CHD
4U5T-14G421-CJD
4U5T-14G421-CED
4U5T-14G423-CA
4U5T-14G424-CD

APIM AsBuilt
DE00: BLANK
DE01: BLANK
DE02: BLANK
DE03: BLANK
DE04: BLANK
DE05: BLANK
DE06: BLANK

That’s 3.4.21194 …

Well… yes… you never installed 3.3… the unit is running 3.4.21194…

What am I missing here?

I used the tool on the car, selected the 3.3 package for my USB stick to update it, plugged it in the car, car said “updating” for about 15 mins, then screen went off, I removed the key, open/closed the door, locked the car, opened back up, started Sync, still 3.4. I then did a master reset, and still 3.4.

Am I missing a step?

Lets do this:

  • create an “upgrade” USB, set 3.3 as target, keep maps, let APPS be the only package installed.
  • once the USB is created, share its log with us.
  • connect it to the car and let it run.
  • once it ends and you see installation complete, let it reboot and unplug the USB before it does.

Here is the log after creating the USB stick with your instructions.

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

PREVIOUS CONFIGURATION
Version: 3.4.21194
Region:
Navigation: True
Install Mode: Auto-Detect (autoinstall)
Install Mode Overridden: False
My20 Protection Enabled: Enabled

DESTINATION DETAILS
Mode: Drive
Model: Kingston DataTraveler 3.0 USB Device
Size: 57.8GB
FileSystem: exFAT
Partition Type: MBR

AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.12.5.0 Stable - Autoinstall Mode - Sync 3.3.19052 NA

[SYNCGen3.0_ALL_PRODUCT]
Item1 = RWDataCleaner TOOL - PU5T-14G386-BB_1690840002000.TAR.GZ
Open1= SyncMyRide\PU5T-14G386-BB_1690840002000.TAR.GZ
Item2 = APPS - 4U5T-14G381-AN_1552583626000.TAR.GZ
Open2 = SyncMyRide\4U5T-14G381-AN_1552583626000.TAR.GZ
Options = AutoInstall

FILES (2)
PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
4U5T-14G381-AN_1552583626000.TAR.GZ (479.7MB)

LOG
[4/21/2024 1:48:39 PM] Selected Region: NA - Release: Sync 3.3.19052 - Map Version: Keep Existing Maps
[4/21/2024 1:48:39 PM] Install Mode: Auto-Detect (autoinstall) Forced: False
[4/21/2024 1:48:39 PM] MY20 Protection: Enabled
[4/21/2024 1:48:39 PM] Formatting USB drive
[4/21/2024 1:48:39 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[4/21/2024 1:48:47 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ
[4/21/2024 1:48:47 PM] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download)
[4/21/2024 1:48:47 PM] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ
[4/21/2024 1:48:48 PM] Validated: 4U5T-14G381-AN_1552583626000.TAR.GZ (Skipping Download)
[4/21/2024 1:48:48 PM] Preparing USB drive
[4/21/2024 1:48:49 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ
[4/21/2024 1:48:49 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ
[4/21/2024 1:48:49 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ
[4/21/2024 1:48:49 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ
[4/21/2024 1:48:49 PM] Checking Existing File: 4U5T-14G381-AN_1552583626000.TAR.GZ
[4/21/2024 1:48:49 PM] Copying: 4U5T-14G381-AN_1552583626000.TAR.GZ
[4/21/2024 1:49:13 PM] Validating: 4U5T-14G381-AN_1552583626000.TAR.GZ
[4/21/2024 1:49:14 PM] Copied: 4U5T-14G381-AN_1552583626000.TAR.GZ
[4/21/2024 1:49:14 PM] Generating Autoinstall.lst
[4/21/2024 1:49:14 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

Will report back

That looks good, try it.

From your previous post:

That tells me the installation never completed, you never saw a message saying so… you need to make sure the installation complete message is shown, if the vehicle is in an open and well ventilated environment, run the upgrade with the engine running…

1 Like

Bingo!

So my mistake was to remove the USB stick too early and not let it complete. I assumed I should remove it when it said “system will now restart”, and it seems to be the problem. This time I let it run with the vehicle engine on, and waited until I saw the familiar light blue screen from the 3.3.

Thanks again for all the help.

1 Like

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