''Invalid or Unsigned File'' message when trying to update

LePtiQC413 · 4 September 2024 02:05

English is not my native language, if you don’t understand a sentences, please let me know

Hi, i have a 2012 Ford Focus SEL that come originally with Sync 2 with navigation. I bought a Sync 3 non-nav (software version 1.1 build 15349) from a wrecked 2018 Ford Focus that work good. I changed the USB hub and now im trying to update to 3.4 but i tried several software and method to update it and i always have a error message saying ‘‘Invalid or Unsigned File’’ 1 minute or so after pluging the USB drive in the car. I tried to update to 2.2 too from a file i found because i read on forums that sometimes you cannot update directly from 1.0 to 3.0 and same thing, tried to change my USB drive from exFAT to FAT32, tried to do split update cause i tought maybe my APIM run out of memory, Tried to master reset my APIM several time… Even tried to do the interogator mode and i always have the same message NO MATTER WHAT I DO ! My USB drive is a brand new SanDisk Extreme PRO 128gb that i bought just for this and it become a little bit hot when i plug it into the car just like when i plug it into my PC. (thats normal right ?)
I think maybe the USB hub i bought is not compatible? It supposed to fit for sync 3 and have USB 3.1 ? I don’t know what to do, I spent a whole day trying to find a solution and I couldn’t find anything. I just want CarPlay at this point i don’t mind having 3.4 or not

My APIM parts number: GJ5T-14G370-BL MFG DATE: 07/15/2015

SYNC Region: NA

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: Retrofit

Old SYNC Version: 1.1.15349

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
Invalid or Unsigned File
Your installation package may have corrupted, the package signature may have failed or the signature may have been revoked.

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.12.5.0

Syn3 Updater Documentation Read: no

Syn3 Updater Log File

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

PREVIOUS CONFIGURATION
Version: 1.1.15349
Region: NA
Navigation: False
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

DESTINATION DETAILS
Mode: Drive
Model: SanDisk 3.2 Gen 1 SCSI Disk Device
Size: 115,1GB
FileSystem: exFAT
Partition Type: MBR

REFORMAT.LST
VOICE=5U5T-14G391-CS_1660783942000.TAR.GZ
GRACENOTES=4U5T-14G423-CC_1615429225000.TAR.GZ
APPS=NU5T-14G381-AD_1689364279000.TAR.GZ


AUTOINSTALL.LST
; CyanLabs Syn3Updater 2.12.5.0 Stable - reformat  Mode - Sync 3.4.23188 NA

[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 (5)
1u5t-14g386-cb.tar.gz (8,5MB)
PU5T-14G386-BB_1690840002000.TAR.GZ (3,2KB)
5U5T-14G391-CS_1660783942000.TAR.GZ (385,5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564,2MB)
NU5T-14G381-AD_1689364279000.TAR.GZ (869,8MB)

LOG
[2024-09-03 21:54:20] Selected Region: NA - Release: Sync 3.4.23188 - Map Version: Non Nav APIM 
[2024-09-03 21:54:20] Install Mode: Auto-Detect (reformat) Forced: False 
[2024-09-03 21:54:20] MY20 Protection: Auto-Detect 
[2024-09-03 21:54:20] Formatting USB drive
[2024-09-03 21:54:20] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[2024-09-03 21:54:27] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[2024-09-03 21:54:27] Validated: 1u5t-14g386-cb.tar.gz (Skipping Download) 
[2024-09-03 21:54:27] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-09-03 21:54:27] Validated: PU5T-14G386-BB_1690840002000.TAR.GZ (Skipping Download) 
[2024-09-03 21:54:27] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-09-03 21:54:28] Validated: 5U5T-14G391-CS_1660783942000.TAR.GZ (Skipping Download) 
[2024-09-03 21:54:28] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2024-09-03 21:54:29] Validated: 4U5T-14G423-CC_1615429225000.TAR.GZ (Skipping Download) 
[2024-09-03 21:54:29] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-09-03 21:54:31] Validated: NU5T-14G381-AD_1689364279000.TAR.GZ (Skipping Download) 
[2024-09-03 21:54:31] Preparing USB drive
[2024-09-03 21:54:31] Checking Existing File: 1u5t-14g386-cb.tar.gz 
[2024-09-03 21:54:31] Copying: 1u5t-14g386-cb.tar.gz 
[2024-09-03 21:54:31] Validating: 1u5t-14g386-cb.tar.gz 
[2024-09-03 21:54:31] Copied: 1u5t-14g386-cb.tar.gz 
[2024-09-03 21:54:31] Checking Existing File: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-09-03 21:54:31] Copying: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-09-03 21:54:31] Validating: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-09-03 21:54:31] Copied: PU5T-14G386-BB_1690840002000.TAR.GZ 
[2024-09-03 21:54:31] Checking Existing File: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-09-03 21:54:31] Copying: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-09-03 21:54:33] Validating: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-09-03 21:54:34] Copied: 5U5T-14G391-CS_1660783942000.TAR.GZ 
[2024-09-03 21:54:34] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2024-09-03 21:54:34] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2024-09-03 21:54:38] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2024-09-03 21:54:39] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ 
[2024-09-03 21:54:39] Checking Existing File: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-09-03 21:54:39] Copying: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-09-03 21:54:44] Validating: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-09-03 21:54:46] Copied: NU5T-14G381-AD_1689364279000.TAR.GZ 
[2024-09-03 21:54:46] Generating reformat.lst
[2024-09-03 21:54:46] Generating autoinstall.lst
[2024-09-03 21:54:46] ALL FILES DOWNLOADED AND COPIED TO THE USB DRIVE SUCCESSFULLY!

SaNdMaN · 4 September 2024 08:35

Hello.

There are a few things that caught my attention:

That does not add up, unless the APIM was not native to that Focus, of course. But a Focus from 2018 should already have Sync3.

Also, that number is the assembly number, not the APIM’s model. So for the moment, the APIM’s model is unknown.

You can try going into bezel diagnostics, I think there’s a menu there where you can see the HW model, the 14G371 identification.

This is also strange, I’m not sure why it’s detecting it as an SCSI disk. Do you have any other USB pendrive to try with?, you can try running the interrogator alone…

LePtiQC413 · 4 September 2024 11:32

My bad, my new APIM come from a 2016 not 2018 Ford Focus and yes it have Sync 3 but 1.1 Version…

Heres a picture of the back of my APIM (sorry for the quality this is the only picture i have)

And ok, i will try a new USB Drive to see if its detected has SCSI

LePtiQC413 · 6 September 2024 01:59

Hi, i tried with two other USB Drive to run the interogator mode and same thing, about 1 minute after ‘‘Updating System Software’’ the message Invalid or unsigned file appears and no log on the USB when i check… oh and sometimes when i start the car, the message ‘‘USB hubs are not supported’’ appears on the screen… maybe my usb hub is not good and thats why i can’t do nothing ? It supposed to be compatible with sync 3 according to the amazon description and idk if its an oem one but it have the logo ‘‘FoMoCo’’ on the back

bill32399 · 6 September 2024 02:15

That APIM is SUPER old. Made in 2015 and for the most part Sync 3 was not until 2017 with a few models in 2016. No where close to being made for Sync 3.4

That hub is Chinese garbage. Ford never made a USB hub with type C with that size trim.

LePtiQC413 · 6 September 2024 02:31

Yeah i will return the chinese one and buy an OEM one… that was my next step to try to solve my problem lol… But for the APIM, yes its old but it have version 1.1 in it, and i see a lot of person on forums that have the 1.0 version that is even older and they update to 3.4 just fine so i guess it should work. I just don’t know why it always say Invalid or Unsigned File no matter what i try

LePtiQC413 · 6 September 2024 02:52

This ?

CyanLabs · 6 September 2024 12:40

Are you trying to go directly to 3.x from 1.x?

This won’t work, you may need to go to 2.2 first

LePtiQC413 · 6 September 2024 12:50

Yes, i tried to update to 2.2 too and i have the same error message Unsigned file…

CyanLabs · 6 September 2024 13:22

There were random DEV builds of 1.x floating around and on APIMs years ago, i wonder if you are using a build that has a dev certificate instead of a production certificate.

Also note that sometimes SYNC lies about the error message, if it displayed that error message 1 time, it may continue to display the same error until a hard power cycle of the APIM, many times i’ve thought something is not working but then hard reset and no longer get that error.

LePtiQC413 · 6 September 2024 13:35

I see… Do you know how i can do a hard reset ? Is that the ‘‘Master Reset’’ i tried that a couple time…

CyanLabs · 6 September 2024 13:36

A power cycle of some form, disconnect from battery for example, or shutoff the car and wait a bit of time for it to fully power off

LePtiQC413 · 7 September 2024 19:39

Little update… I tried to diconnect the battery for 30 seconds 2 time, tried another 2.2 upgrade even tried RW data cleaner and always the same Unsigned File message ! Interogator mode doesnt work either. And i tried to update with my sync 2 USB Hub too. At this point, i am really desperate seems like EVERYTHING i do leads to nothing … Is that possible to litteraly format my APIM and put a fresh file in it (like format a PC and download windows) i don’t know i am not really into this kind of stuff and this is just an idea from a desperate guy lol

and by the way is that normal that my USB Drive become really hot when i plug it into the car ?

LePtiQC413 · 10 September 2024 22:39

Hi, i purchased a brand new USB Hub at my dealer yesterday (HC3Z-19A387-F) Ive made another attempt updating to 2.2 with Syn3 updater and i got the same message

By the way, how do i know if i have a DEV build ? maybe my APIM is blocked to the 1.1.15349 version ? I don’t know what to do anymore…

CyanLabs · 11 September 2024 13:27

I don’t know, it might say in the version info, i’ve never seen one i just know they exist.

warlock12118 · 11 September 2024 13:39

2015 APIM could very well have an expired code signing certificate in it.
In 2014 you could generate a 10 yr cert, now the max accepted life for most OS even with a self signed code cert is 8 years.

The only way to verify if that is the case would be if someone had a way to change the internal clock date on the APIM back to say 2023.

LePtiQC413 · 11 September 2024 13:39

Ok thank you ! So I have no other option left to try to update ?

Do you know if that is possible ?

LePtiQC413 · 11 September 2024 13:43

Oh ! i haven’t thought about it, I’ll start my research thank you

warlock12118 · 11 September 2024 13:47

The updater method would be reformat, someone else might have to chime in to see if the Ford reformat tool will run on that low of a version of Sync3.

With the APIM being that old there’s a good chance that reformatting it will brick the unit.

LePtiQC413 · 22 September 2024 19:29

Quick update, I’m unable to update my APIM for some unknown reason and i lost hope, so I decided to going back to my SYNC 2 and selling everything I bought. So if anyone wants my APIM SYNC 3 and knows how to update it I can sell it AT YOUR OWN RISK I also have a brand new in-box HC3Z-19A387-F USB module that I purchased from my dealer (I have the receipt) if anyone is interested, send me a PM, im taking offers… Shipping from Quebec, Canada Anyway, thank you all for your help ! You are a great community i will close this topic now