ERR04 in the car

Downloaded succesfully but the USB in the car gave the above error.


SYNC Region: ANZ

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4.23188

New SYNC Version: 3.4.23188

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.14.2.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File



  CYANLABS - SYN3 UPDATER - V2.14.2.0
  Branch: Stable
  Operating System: Microsoft Windows 11 Pro (2009)
  
  PREVIOUS CONFIGURATION
  Version: 3.0.20204
  Region: ANZ
  Navigation: True
  Install Mode: Auto-Detect (reformat)
  Install Mode Overridden: False
  My20 Protection Enabled: Auto-Detect
  
  DESTINATION DETAILS
  Mode: Drive
  Model: Verbatim STORE N GO USB Device
  Size: 28.9GB
  FileSystem: exFAT
  Partition Type: MBR
  
  REFORMAT.LST
  VOICE=5U5T-14G391-DS_1660784642000.TAR.GZ
  GRACENOTES=4U5T-14G423-DC_1615429585000.TAR.GZ
  APPS=NU5T-14G381-AD_1689364279000.TAR.GZ
  VOICE_NAV=4U5T-14G422-DM_1748465217000.TAR.GZ
  MAP=4U5T-14G421-DAK_1748463179000.TAR.GZ
  
  
  AUTOINSTALL.LST
  ; CyanLabs Syn3Updater 2.14.2.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 (7)
  1u5t-14g386-cb.tar.gz (8.5MB)
  PU5T-14G386-BB_1690840002000.TAR.GZ (3.2KB)
  5U5T-14G391-DS_1660784642000.TAR.GZ (1GB)
  4U5T-14G423-DC_1615429585000.TAR.GZ (896MB)
  NU5T-14G381-AD_1689364279000.TAR.GZ (869.8MB)
  4U5T-14G422-DM_1748465217000.TAR.GZ (1.6GB)
  4U5T-14G421-DAK_1748463179000.TAR.GZ (5.1GB)
  
  LOG
  [1/11/2025 7:30:19 PM] Selected Region: ANZ - Release: Sync 3.4.23188 - Map Version: 2.24 (2024) - ANZ, SA and TW 
  [1/11/2025 7:30:19 PM] Install Mode: Auto-Detect (reformat) Forced: False 
  [1/11/2025 7:30:19 PM] MY20 Protection: Auto-Detect 
  [1/11/2025 7:30:19 PM] Formatting USB drive
  [1/11/2025 7:30:19 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
  [1/11/2025 7:30:29 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
  [1/11/2025 7:30:29 PM] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download) 
  [1/11/2025 7:30:29 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [1/11/2025 7:30:29 PM] Downloading: PU5T-14G386-BB_1690840002000.TAR.GZ
  [1/11/2025 7:30:30 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [1/11/2025 7:30:30 PM] Downloaded: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [1/11/2025 7:30:30 PM] Checking Existing File: 5U5T-14G391-DS_1660784642000.TAR.GZ 
  [1/11/2025 7:30:34 PM] Validated: 5U5T-14G391-DS_1660784642000.TAR.GZ (Skipping Download) 
  [1/11/2025 7:30:34 PM] Checking Existing File: 4U5T-14G423-DC_1615429585000.TAR.GZ 
  [1/11/2025 7:30:37 PM] Validated: 4U5T-14G423-DC_1615429585000.TAR.GZ (Skipping Download) 
  [1/11/2025 7:30:37 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
  [1/11/2025 7:30:40 PM] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
  [1/11/2025 7:30:40 PM] Checking Existing File: 4U5T-14G422-DM_1748465217000.TAR.GZ 
  [1/11/2025 7:30:40 PM] Downloading: 4U5T-14G422-DM_1748465217000.TAR.GZ
  [1/11/2025 7:35:00 PM] Validating: 4U5T-14G422-DM_1748465217000.TAR.GZ 
  [1/11/2025 7:35:06 PM] Downloaded: 4U5T-14G422-DM_1748465217000.TAR.GZ 
  [1/11/2025 7:35:06 PM] Checking Existing File: 4U5T-14G421-DAK_1748463179000.TAR.GZ 
  [1/11/2025 7:35:06 PM] Downloading: 4U5T-14G421-DAK_1748463179000.TAR.GZ
  [1/11/2025 7:50:43 PM] Validating: 4U5T-14G421-DAK_1748463179000.TAR.GZ 
  [1/11/2025 7:51:18 PM] Downloaded: 4U5T-14G421-DAK_1748463179000.TAR.GZ 
  [1/11/2025 7:51:18 PM] Preparing USB drive
  [1/11/2025 7:51:18 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz 
  [1/11/2025 7:51:18 PM] Copying: 1u5t-14g386-cb.tar.gz 
  [1/11/2025 7:51:19 PM] Validating: 1u5t-14g386-cb.tar.gz 
  [1/11/2025 7:51:19 PM] Copied: 1u5t-14g386-cb.tar.gz 
  [1/11/2025 7:51:19 PM] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [1/11/2025 7:51:19 PM] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [1/11/2025 7:51:19 PM] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [1/11/2025 7:51:19 PM] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
  [1/11/2025 7:51:19 PM] Checking Existing File: 5U5T-14G391-DS_1660784642000.TAR.GZ 
  [1/11/2025 7:51:19 PM] Copying: 5U5T-14G391-DS_1660784642000.TAR.GZ 
  [1/11/2025 7:54:22 PM] Validating: 5U5T-14G391-DS_1660784642000.TAR.GZ 
  [1/11/2025 7:54:51 PM] Copied: 5U5T-14G391-DS_1660784642000.TAR.GZ 
  [1/11/2025 7:54:51 PM] Checking Existing File: 4U5T-14G423-DC_1615429585000.TAR.GZ 
  [1/11/2025 7:54:51 PM] Copying: 4U5T-14G423-DC_1615429585000.TAR.GZ 
  [1/11/2025 7:57:46 PM] Validating: 4U5T-14G423-DC_1615429585000.TAR.GZ 
  [1/11/2025 7:57:55 PM] Copied: 4U5T-14G423-DC_1615429585000.TAR.GZ 
  [1/11/2025 7:57:55 PM] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
  [1/11/2025 7:57:55 PM] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
  [1/11/2025 8:00:42 PM] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
  [1/11/2025 8:01:01 PM] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
  [1/11/2025 8:01:01 PM] Checking Existing File: 4U5T-14G422-DM_1748465217000.TAR.GZ 
  [1/11/2025 8:01:01 PM] Copying: 4U5T-14G422-DM_1748465217000.TAR.GZ 
  [1/11/2025 8:06:18 PM] Validating: 4U5T-14G422-DM_1748465217000.TAR.GZ 
  [1/11/2025 8:07:02 PM] Copied: 4U5T-14G422-DM_1748465217000.TAR.GZ 
  [1/11/2025 8:07:02 PM] Checking Existing File: 4U5T-14G421-DAK_1748463179000.TAR.GZ 
  [1/11/2025 8:07:02 PM] Copying: 4U5T-14G421-DAK_1748463179000.TAR.GZ 
  [1/11/2025 8:23:55 PM] Validating: 4U5T-14G421-DAK_1748463179000.TAR.GZ 
  [1/11/2025 8:26:29 PM] Copied: 4U5T-14G421-DAK_1748463179000.TAR.GZ 
  [1/11/2025 8:26:29 PM] Generating reformat.lst
  [1/11/2025 8:26:29 PM] Generating autoinstall.lst
  [1/11/2025 8:26:29 PM] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY! 
  

It’s a bit strange that (a) the car, post-running the USB, shows the software version the same as the one I downloaded, and yet I got an error, and (b) if it was successful, how come it only took a minute or so?

Those versions are wrong and contradicting. Configure the tool correctly and recreate the USB, read Basic Usage - CyanLabs for further details.

Sorry, but I don’t understand, from what you have said, what I did wrong. I followed the guide carefully. Please elaborate.

As per the log, your current build configured in Syn3Updater is 3.0.
As per your opening message, your current build is 3.4.

Which one is true?, they can’t be both true.
Configure Syn3Updater accordingly and recreate the USB.

When the help submission asked for ‘current build’, I went to the car, a post-installation attempt car - and read the build. I don’t know where the 3.0 came from, but if that was pre-installation in the car, then it appears the car has been updated to 3.4. Which is strange because of (a) the error and (b) the short time it took before the error appeared. I know of nothing that I would change in the configuration of the download, and as that process took quite a while, I am relucant to do it again unless it is really necessary. What is ERR04 in the list of error codes?

Thinking about it again, there was only one input where I had to guess the correct answer. I think it was the version to update to. I picked the top of the list. There was no advice to do otherwise. If that was wrong, how does one choose? (By the way, happy to give a donation if this is solved quickly and pleasantly.)

You need to name the previous configuration on the Updater as the same as the current build no. in the car but if it is showing 3.4.23188 in the car then it is already updated with the latest version.

So, what’s with the error message then? Is there not a list of error messages that we can consult? If it is known issue that that error means nothing, then perhaps you could update the notes? Plus, I don’t remember any instruction about the choice of version to pick for the update. (As I said earlier, I just selected the one at the top of the list.)

As I said earlier…you need to select the one that is showing as the latest build in the car as the previous configuration, not the one at the top of the list on the sync Updater but from what you are suggesting you already have the latest version 3.4.23188 so there is nothing to update.

Thanks Chief. 04 doesn’t mean much to me, but it doesn’t seem that the respondent gave me a solution that responded to that error. Anyway, let’s hope it’s updated despite the error. If it hasn’t, then I’ll be back.

There are 5 different ERR04 Ford gives us. Kinda hard to help when we dont know which one it is.

All it said on the screen was ‘Error code: PKG_ERR04’. If there is more than one, shouldn’t the solution be to cycle through them with the user until a solution is found?

Thats what I am looking for! thx

My apologies. I omitted that from my original post. So, you can now tell what I need to do?

I cant but I think others might have a better idea knowing exactly which code it is. If you search that error on here you will get an idea of how to fix it though.

Ta muchly. This (non-technical) owner will have a go.

1 Like

Hello.

Do not get this wrong way, but man you are over complicating things :slight_smile: :sweat_smile:

You as an user have just a few obligations, mainly to provide correct information to the tool. The tool is not sentient, it does not know what versions you want or the car is running. It’s your responsibility to do so.

So that’s why for the 3rd time I’m telling you the solution is to configure the tool correctly.
Please read the guide (which says the same thing) I sent a few days ago, check what the current version the car is running is (it does not matter if it’s pre or post update, current is current, current is now regardless what happened before) and configure it so in syn3updater… then select whatever version you want to go to (unless you want old stuff, go to the latest).

That means you are trying to run the reformat tool on a latest 3.4 which can’t be done since it’s blacklisted. And that is happening because you are creating the wrong USB because you fed incorrect information to the tool, possibly stating the car is running 3.0.

So, configure it correctly, recreate the USB and try again.

If that fails, then provide:

  • the log for the USB creation
  • a photo of the about sync3 screen that shows the build the car is running.

That is what I have been trying to get across but the poster insists on getting a build version from the Updater selection instead of the current build in the car.