Ford Puma Sync3 audio reinstall

Hello all,

my European Ford Puma 2022 with Sync 3 got upgraded to 3.4.22251_PRODUCT and F11 maps. The upgrade itself did not error out, and seemed to be ok. I found out later on that the audio commands no longer work. A rough translation from the Sync3 is that one must reinstall the maps update to finalize the audio upgrade.

If I reinsert the USB media I used for the upgrade, it will eventually end up with MEM_ERR1 and reinstallation fails. The autoinstall.lst file is split into SYNCGen3.0_ALL, 3.4.22251_PRODUCT and 3.4.22251 which I was wondering if same files are going to get installed more than once thus the MEM_ERR1 shows. Ford customer service has not been able to come up with any usefull recovery methods, other than performing the master reset on the unit and retrying the upgrade, which does not resolve the issue.

Any tips on trying to get just the audio part reinstalled on the unit?


SYNC Region: EU

Navigation Variant: Non Nav

Manufacturer Year: MY20

Install Type: OEM

Old SYNC Version: 3.4.19200

New SYNC Version: 3.4.22251

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

Update Method: Official Ford

Run the Interrogator Utility in Syn3 Updater and post the results here.

Hi,

here are the gathered logs.

Sync_NYC901L1_WF02XXERK2LB44736.xml (11.1 KB)

Your installation did not go quite right or did not finish. The maps are not complete and the Sync version did not upgrade to Sync 3.4.22251. You are presently on 3.4.22110 with the associated voice file. The GN and DAB file are from previous but are fine. This is what is installed:

1U5T-14G421-BAJ
1U5T-14G421-BBE This is an old map file from previous installation.
1U5T-14G421-BCJ
1U5T-14G421-BDJ
1U5T-14G421-BEJ
1U5T-14G421-BFJ
1U5T-14G421-BGJ
1U5T-14G421-BHJ
1U5T-14G421-BJE
1U5T-14G424-BL
4U5T-14G422-BBG Missing 3 of the 4 voice files.

5U5T-14G381-EZ
5U5T-14G391-AS
4U5T-14G423-AC
1U5T-14G658-AH

This is the storage space. There is 18GB free, so no issue there.

<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ1.1G” available=β€œ1.0M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ1.1G” available=β€œ20M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ2.8G” available=β€œ14M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ2.3G” available=β€œ14M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ1.5G” available=β€œ7.8M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ2.2G” available=β€œ17M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ3.8G” available=β€œ21M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ38M” available=β€œ336K”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ31M” available=β€œ708K”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ3.2G” available=β€œ5.6M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ3.2G” available=β€œ25M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ4.6G” available=β€œ27M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ4.8G” available=β€œ29M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ1.9G” available=β€œ8.4M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/grace” total=β€œ1003M” available=β€œ21M”/>
<d2p1:PartitionHealth type=β€œ/fs/rwdata/” total=β€œ1.2G” available=β€œ933M”/>
<d2p1:PartitionHealth type=β€œ/fs/rwdata/quip/” total=β€œ35M” available=β€œ35M”/>
<d2p1:PartitionHealth type=β€œ/fs/rwdata/quip/” total=β€œ90M” available=β€œ90M”/>
<d2p1:PartitionHealth type=β€œ/fs/mp/” total=β€œ1.4G” available=β€œ84M”/>
<d2p1:PartitionHealth type=β€œ/fs/mp/resources” total=β€œ72M” available=β€œ332K”/>
<d2p1:PartitionHealth type=β€œ/fs/images/” total=β€œ54G” available=β€œ18G”/>

Fix this in 2 stages:
First upgrade the Sync app to 3.4.22251 with the right voice file for Sync. Do this with the Syn3 Updater. DO NOT install any maps at this time.
Once that is completed and the APIM is rebooted and everything checks out, Master Reset the unit.
Once the Master Reset is completed and the unit reboots, you can install the entire EU map set with voice files. This is the maps and nav voice only.
This will be autoinstall, so will take about 90 minutes or so.
Use this autoinstall.lst file:
autoinstall.lst (1.6 KB)

This procedure will reboot the APIM and continue with the installation. DO NOT remove the USB until the end of the installation.
Once this is completed, reboot the unit and wait for all the maps to load and the unit to stabilize. You will likely get a nav not available message until this is done. It should take about 10 minutes sometimes. Once this appears to be complete, reboot the unit.
Once rebooted if you still get the nav not available message, wait until it completes as above. You can also shut off the vehicle and leave it for an hour or so. The system will work in the background for a while completing this.
Now test the system and see if everything works. The most prevalent issue that causes these issues like this is that people are not patient with the installation.

Thank you for the tips. I created a new usb with Syn3 Updater, with options:

Region: Europe
Version: Sync 3.4.22251
Map version: Keep existing maps

The upgrade ended without errors and after a device restart I did the master reset.

I created a new Syn3 UPdater USB with the following settings:

Region: Europe
Version: Sync 3.4.22251
Map version: F11 (2021) - EU (05 2022)

after the USB got created I replaced the autoinstall.lst on the root of the usb, which you provided in the post.

When the USB is inserted, Installation failed: MEM_ERR01 is presented. I gathered new set of logs of the status, which I’m attaching here.

Sync_NYC901L1_WF02XXERK2LB44736.xml (11.0 KB)

1 Like

MEM_ERR01 – Error is MEM_NOSPACE_TO_COPY

This is what is installed on the unit:
1U5T-14G421-BAJ
1U5T-14G421-BBE - This is an old map file from previous installation.
1U5T-14G421-BCJ
1U5T-14G421-BDJ
1U5T-14G421-BEJ
1U5T-14G421-BFJ
1U5T-14G421-BGJ
1U5T-14G421-BHJ
1U5T-14G421-BJE- This is an old map file from previous installation.
4U5T-14G422-BBG - Missing 3 of the 4 voice files.
1U5T-14G424-BL

NU5T-14G381-AB
5U5T-14G391-AT
4U5T-14G423-AC
1U5T-14G658-AH

The Sync apps look fine. The maps still need work.
The storage is nearly the same:
<d2p1:PartitionHealth type=β€œ/fs/images/” total=β€œ54G” available=β€œ19G”/>
with 19GB free.

There is definitely an issue with the installation of the maps. There is plenty of free space to process the autoinstall, but the process fails with a NOSPACE failure. We can try a cut down installation to fix the -BBE file first. Use the same USB with files but use this autoinstall file. This will only install 3 files, which should be well under the 19GB of free storage.
autoinstall.lst (454 Bytes)

If this works and completes, run the Interrogator again and post the results.

You are in Finland according to the APIM asbuilt coding. Is this correct?

I used the same USB NAV update, with the autoinstall file you provide. Again succesfull installation, restarted unit and still the same problem where an audio message says that you should complete the NAV update to get the audio files installed.

I’m located in Finland, which is correct from the data you provided. New set of logs attached after latest attempt
Sync_NYC901L1_WF02XXERK2LB44736.xml (11.0 KB)
.

OK, at this point all of the proper map files are installed except one, which we can do along with the voice files. The storage is still the same, so that is good. The reason the installation was failing before is that the installation file list file size was greater than the amount of free storage remaining. By slicing up the installation to smaller chunks, it seems to be working. Based on that we can continue with the installation.
This is what is now installed:
1U5T-14G421-BAJ
1U5T-14G421-BBJ - Fixed
1U5T-14G421-BCJ
1U5T-14G421-BDJ
1U5T-14G421-BEJ
1U5T-14G421-BFJ
1U5T-14G421-BGJ
1U5T-14G421-BHJ
1U5T-14G421-BJE - This is an old map file from previous installation.
4U5T-14G422-BBG - Missing 3 of the 4 voice files.
1U5T-14G424-BL

NU5T-14G381-AB
5U5T-14G391-AT
4U5T-14G423-AC
1U5T-14G658-AH

Since you can just use the existing USB and the files needed for the rest of the installation, I’ll write out the necessary autoinstall files below.

Step 1: Fix the -BJE file. This is similar to what was done for the -BBE file.
You will need the proper file in the SyncMyRide folder on the USB:
1U5T-14G421-BJJ
Use this autoinstall file:
autoinstall .lst (250 Bytes)
This is one file, so should be only a few minutes to complete. Reboot the APIM after installation.

Step 2: Fix the nav voice files.
You will need the proper files in the SyncMyRide folder on the USB:
4U5T-14G422-BAG
4U5T-14G422-BBG
4U5T-14G422-BCG
4U5T-14G422-BDG
Use this autoinstall file:
autoinstall.lst (626 Bytes)
This is 4 files, so this will take a while to complete. The script will reboot the unit once and continue the installation. Do not remove the USB till it is done. Ignore any key cycle messages. Reboot the APIM after installation.

Step 3: After this is all done, perform a master reset on the unit.

Run the Interrogator Utility and post the results…

It seems that the problem is finally resolved! Audio file installation took nearly 90min to complete, after which I did the master reset. Voice controls are available again, thank you very much!

Is the content of the autoinstall.lst files explained anywhere or does the Sync3 actually read what is the headline for the files to be opened, such as:

[SYNCGen3.0_3.2.22012_PRODUCT]
or
[SYNCGen3.0_3.2.22012]

or does one actually need to know to which revision the files are actually related? I recall I did try installing only the audio files in the past, but obviously did not know that I had some older files still in the system.

Here’s the log.
Sync_NYC901L1_WF02XXERK2LB44736.xml (12.1 KB)

Good job! Enjoy.

This is what is installed on the unit. Everything is installed and all looks fine.
1U5T-14G421-BAJ
1U5T-14G421-BBJ
1U5T-14G421-BCJ
1U5T-14G421-BDJ
1U5T-14G421-BEJ
1U5T-14G421-BFJ
1U5T-14G421-BGJ
1U5T-14G421-BHJ
1U5T-14G421-BJJ
1U5T-14G424-BL

4U5T-14G422-BAG
4U5T-14G422-BBG
4U5T-14G422-BCG
4U5T-14G422-BDG

NU5T-14G381-AB
5U5T-14G391-AT
4U5T-14G423-AC
1U5T-14G658-AH

The storage is correct, no issues.
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ1.1G” available=β€œ1.0M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ2.8G” available=β€œ14M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ2.3G” available=β€œ14M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ1.5G” available=β€œ7.8M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ2.2G” available=β€œ17M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ3.8G” available=β€œ21M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ38M” available=β€œ336K”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ3.2G” available=β€œ5.6M”/>
<d2p1:PartitionHealth type=β€œ/fs/sd/MAP/” total=β€œ3.2G” available=β€œ25M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ4.6G” available=β€œ27M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ4.8G” available=β€œ29M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ4.3G” available=β€œ25M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ3.6G” available=β€œ35M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/” total=β€œ1.9G” available=β€œ8.4M”/>
<d2p1:PartitionHealth type=β€œ/fs/Nuance/grace” total=β€œ1003M” available=β€œ21M”/>
<d2p1:PartitionHealth type=β€œ/fs/rwdata/” total=β€œ1.2G” available=β€œ938M”/>
<d2p1:PartitionHealth type=β€œ/fs/rwdata/quip/” total=β€œ35M” available=β€œ35M”/>
<d2p1:PartitionHealth type=β€œ/fs/rwdata/quip/” total=β€œ90M” available=β€œ90M”/>
<d2p1:PartitionHealth type=β€œ/fs/mp/” total=β€œ1.4G” available=β€œ84M”/>
<d2p1:PartitionHealth type=β€œ/fs/mp/resources” total=β€œ72M” available=β€œ332K”/>
<d2p1:PartitionHealth type=β€œ/fs/images/” total=β€œ54G” available=β€œ11G”/>

This information is contained in the license files contained in the packages. I always place it in the autoinstall files to keep track of what is what, since I work with these all the time. If you look at the Ford packaged updates, this is also done. The installation will read the license file for this information, this is here for us humans.

The IVSU database here on the site is probably the easiest way to determine the file versions.
SYNC 3 APIM Software (IVSU) Database - CyanLabs

1 Like

Does the logfile display information on the features enabled/available on the vehicle to be controlled? I was thinking of the initial problem that might have caused the update to leave old files on the system. The user guide for the car mentions that Settings β†’ Vehicle β†’ 30min Max idle should be possible to set either disabled and enabled, and I did not locate the setting from this car (I have it on my Kuga PHEV) - thus I was wondering if the car had switched off the engine after the idle timer had run out and seemed to be complete.

I don’t know if hybrids have that setting. But they will switch off after 30 minutes unless you interact with the vehicle.

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