PKG_ERR04 installation échouée

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

Hello,
I have a Fiesta MK7 de 2018 with SYNC3, version 3.4, Build 22251_PRODUCT, Gracenote Version 1.1.1.2316 (EU-0020), Navigation Maps Version : F11
I have prepared a USB flash drive MBR
Then downloaded the files in the latest possible versions : 3.4.23188, F13, package NU5T-14G381-AD
When I insert the USB drive into the car, the procedure starts, but stops almost immediately with the error PKFG_ERR04.

HELP

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4 22251

New SYNC Version: 3.4 23188

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

Update Method: CyanLabs Manual Method

2

You need to downgrade to 3.3 first, the reformat package is blacklisted in your current 3.4 build.

Once the unit is on 3.3, you can continue with the guide as normal.

1 Like
3

I choose release : 3.3.19052.

And when it start, ERROR code ; LST_ERR05

What’s wrong ?

(sorry for my English)

4

Don’t you have access to a Windows computer?, it will be easier…
LST_ERR05 means you are creating the USB wrong, either the .LST file is wrong or the packages are not located/named where they should.
But since you are not providing any other information than that, i’s hard to say.

So, post:

  • a screenshot of the USB’s root contents (file extensions visible)
  • a screenshot of the SyncMyRide folder’s content ( " " )
  • all the .lst files’ contents from the root.
5

Capture d’écran 2025-11-21 à 17.57.56
Capture d’écran 2025-11-21 à 17.57.56513×132 16.8 KB

At work, I have Windows computer, but only desk computer.

At home, it’s only Apple products. In France, it’s week-end now.

6

You are missing this:

7

Sorry, I don’t understand which root ?

8

Copy and paste each .lst file contents here, i need to see what they have inside.

1 Like
9

autoinstall.lst (149 Bytes)

reformat.lst (167 Bytes)

10

Thanks.

Your autoinstall.lst file is wrong, it points to some random package you don’t even have.

Download 4U5T-14G381-AN, that’s 3.3.19052. Autoinstall it, once the unit is on 3.3 you can proceed with the manual guide (reformat to whatever version you want, which I assume was your original goal).

11

Thank you. I’ll try tomorrow.

12

Should I unzip 4U5T-14G381-AN.tar file ?

13

No, you don’t. There’s no instruction anywhere to unzip them, that’s done during the process by the unit.

15

I found 4U5T-14G381-AN and autoinstall on this page 4U5T-14G381-AN - SYNC 3 APIM Software (IVSU) Database - CyanLabs

But same LST_ERR05

Capture d’écran 2025-11-22 à 10.10.08

autoinstall.lst (152 Bytes)

16

Packages need to be in the SyncMyRide folder, .lst files in the root (outside the folder).

Read the guide for reference, it tells you how to crate the USB structure. USB structure is always the same when it comes to Sync3.

18

I’m so stupid.

Sorry.

19

I tried with

Foder SyncMyRide/4U…..tar

file autoinstall

  • ERR05

I try with

Foder SyncMyRide/4U…..tar

file autoinstall

file reformat

  • ERR05

I don’t understand…

20

Double checking your previous image, it seems you uncompressed the file.
It needs to be .TAR.GZ, it only shows .TAR.

This is not hard, your current .lst file is

[SYNCGen3.0_ALL_PRODUCT]
Item1 = APPS - 4U5T-14G381-AN_1552583626000.TAR.GZ
Open1 = SyncMyRide\4U5T-14G381-AN_1552583626000.TAR.GZ
Options = AutoInstall

If the file “SyncMyRide\4U5T-14G381-AN_1552583626000.TAR.GZ” does not exist, it will fail.

21

Thank you very much for your patience.

Should the file reformat be on te USB, or only autoinstall ?

22

Was there ANY reference for reformat.lst when you downloaded the 3.3 package?

Also, have you read what I said?

Do not take this the wrong way, but you are making this harder than it should. That’s why I mentioned maybe you should wait a few days and use a Windows computer that will create the USB for you.

Reformat.lst is read by the reformat package/phase, autoinstall.lst is for normal installations without reformat. If reformat.lst is there but there’s no reformat package installed on the unit, it’s irrelevent if it’s there or not.

To avoid increasing your confusion it’s best not to mix them at the moment, functionally it’s irrelevant.