Cannot update from 3.0.17276 to 3.0.23219

Hi guys, apologies if this has been answered but I’ve been trying for hours now and can’t seem to suss it. I’m currently on Sync version 3.0.17276 (Old I know) and I’m trying to update to Sync version 3.0.23219 (As per the ford websites instructions).

I’ve gone through the official process of downloading their update file onto a USB and plugging it into my car, only to be met with the error code VER_ERR08, which after looking through the forms I discovered was a lack of memory on the car to do an update. I created a special USB using CyanLab’s to clear the RWData, aswell as the Gracenotes and such but still no fix I’m unable to install the update.

So then I thought to try and update my car to the next chronological update thinking as it will be less of a jump it might work, but after downloading the update files to a USB and plugging them in I’m met with error code LST_ERR05 which I think is wrong/lack of files. So I’m not really sure where to go from here.

I did do an interrogator log to see if there was still room on my APIM and it shows there is 8GB still free.

I was looking to update the software to 3.0.23219 and not 3.4 as I’m needing to sell the car next month and just wanted the next owner to have the correct update but the SYNC system keeps resetting all of my settings everytime I start the car as if a master reset has been done, so I don’t know whether to just do it.

Am I making an obvious mistake?

Thanks


SYNC Region: EU

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.17276

New SYNC Version: 3.0.23219

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

Update Method: Official Ford

1 Like

You need to select 3.0.23219 as your intended update option to begin with.

Not sure what you mean?? Where are you referring too? On here or CyanLabs?

Can you share the XML file from the interrogator log?. Redact the VIN from it if you are about it.

He’s trying to do the Ford update at the moment.

1 Like

He may need to do a manual install of 3.0 2.2.17011 first, I’ve run into this a couple of times.

That’s extremely confusing, to the point it almost seems wrong.

I “know” you meant Sync3 2.2.17011, which is a downgrade from the users’s current build)… but why are you recommending that?.

wow everyone seems confused here lol

1 Like

sounds like a faulty apim since the memory issue doesnt apply to 3.0

Possibly a skipped pre-req on a previous update.

What?.
But would a 2018 come with any other than 3.x?

My 2018 Fusion which has a build date of 9/2017 came with 2.0.16025 and had never been updated when I bought it in 3/2021.

It comes down to what was in stock when the car came down the line, my wife’s and daughter’s Escapes are literally twins with the daughter’s being made 6 days later. The APIM in the daughter’s had a lower calibration in it than the wife’s and was loaded with the last public 3.3.x/NA2019 build while the wife’s had 3.4.19274.NA2019.

I see your point, but I think most users will use the year they purchased the car for the profile, not the actual MY…

Lets see what OP says…

Hey, here are the results from my interrogator log:

VIN: ***************
APIM Model: JK2T-14G371-ACC
APIM Type: Non-Navigation
APIM Size: 16GB
APIM Free Space: 9.3G
Version 3.0.17276 (JR3T-14G381-AJ)

02/01/2014 23:43:23 +00:00

Partition Type = Free / Total
/fs/usb0/ = 7.4G / 7.4G
/fs/tmpfs/ = 127M / 128M
/fs/Nuance/ = 93M / 1.8G
/fs/rwdata/ = 675M / 1024M
/fs/mp/ = 173M / 1024M
/fs/images/ = 9.3G / 12G

Installed Packages
JR3T-14G423-AA
JR3T-14G391-AD

APIM AsBuilt
DE00: 006A04CA1000BC0440C0
DE01: 554B0001C08A088028B80005
DE02: 0000010004
DE03: BLANK
DE04: 190819082653
DE05: BLANK
DE06: 0B0533000000006428000056565D0061

All of that goes above my head to be honest. I’m just unsure why I get two different error codes when I’m trying to do the two different updates I’ve tried.
VER_ERR08 When trying to bring it up to date with 3.0.23219.
But then LST_ERR05 when trying to do the next chronological update being 3.0.17307. I’m assuming that I didn’t format that one correctly on the usb or maybe I’m missing something.

Thanks in advance.

Thank you for the XML.

Do you still have the USB you are trying to use for upgrading?.
If so, provide:

  • A screenshot of the SyncMyRide folder’s content
  • The autoinstall.lst file you are using.

You mentioned that the APIM sometimes reset itself, like a master reset has been performed. This is not a good sign, not at all… Have you tried a Master Reset?.

Apologies for the late replies.

Here is what my USB looks like when trying to do both updates. (They will be on the root of the USB not inside the folders I’m showing right now)
Also apologies for pic quality I was just being lazy and taking pic of screen.

I have tried multiple master and soft resets, when I start my car up my screen takes about 2 minutes just to boot up from black screen (it used to be instant) the radio comes through slightly before the screen turns on, then once it’s all loaded up I have to re click all my settings again. I’m going to assume my APIM’s now faulty? But thought it would be best to check everything first as dishing out for a Ford service is not ideal.

Thanks




Just realised where I went wrong in terms of updating the older update (3.0.17307) and getting the LST error code, no longer getting that one at all, but I am still getting the VER_ERR08 error code regardless of which update I try, but I’m confused on this as my interrogator log shows I have memory on my APIM. Would it be worth me trying to plug in the Sync 3.4 update from the CyanLab installer to see if it fully reformats my system? Or do I run the risk of completely ruining everything.
Or is there a way of installing the update that I want and also reformatting it all?

Thanks.

If none other installation is possible while on 3.0, your only shot is to try reformatting the unit and installing the latest 3.4…

Will it work?, who knows… Your APIM is not behaving as it should right now…

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