VER_ERR08 While updating from "3.0.17276" to "3.0.23219" (South America)

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

Hello everyone,

I bought an used Ford Fiesta 2019 with stock media center in South America few months ago.
I recently had its APIM replaced by Ford (The previous one wasn’t saving anything due to degraded storage) - Under warranty!
This new one arrives with the System Version “3.0.17276” as described in my title.
I’ve been attempting to update with Ford official methods with no success to latest supported version “3.0.23219”. (Directly from Ford’s website)

So far I’ve:

  • Ran interrogator logs - Successful
  • Ran “RW Data cleaner” tool - Successful
  • Ran “Gracenotes removal” tool - Successful
  • Attempted to install the full package (2.3GB) - No luck - VER_ERR08
  • Attempted to install JUST the system update (JR3T-14G381-AY) - Just 427MB! - No luck - VER_ERR08

The logs from my last interrogator run:
“”"
Partition Type = Free / Total
/fs/tmpfs/ = 127M / 128M
/fs/Nuance/ = 129M / 1.4G
/fs/rwdata/ = 717M / 1024M
/fs/mp/ = 173M / 1024M
/fs/images/ = 2.6G / 4.2G
“”"
“”"
VIN: 9BFZD55P8KB627475
APIM Model: JR3T-14G371-BED
APIM Type: Non-Navigation
APIM Size: 8GB
APIM Free Space: 2.6G
Version 3.0.17276 (JR3T-14G381-AJ)
“”"

I don’t want to update to 3.4.* or newer since I don’t want to risk plus I just use CarPlay anyway. Just want to prevent the logs from clogging the system.

Any clues? Any scripts for reference for this unit?
Thanks!

Oh also, if I’m “stuck” with this version - if I run the “RW Data cleaner” every now and then - would I be safe from this thing clogging up?

SYNC Region: ANZ

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM Replacement

Old SYNC Version: 3.0.17276

New SYNC Version: 3.0.17276

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

Update Method: Official Ford

2

RWData issue affected Sync 3.4 builds higher than 3.4.21265 and lower than 3.4.23188.

To get your car play working while staying on 3.0, update first to 2.2.17011 HN1T-14G381-SA - SYNC 3 APIM Software (IVSU) Database - CyanLabs to get the back end car play support items in place and then use the install for your VIN from owner.ford.com to get you to 3.0.23219

3

Hello.

Is the replacement under warranty under warranty?. Ver08 is not a good error to have, specially on a ¿new? APIM. Let me doubt about it being new beucase it has a build from 2017…

Also, that build is known to be found on troubled APIMs, but to be fair it may be like that since it’s usually found on “ancient” hardware.

You won’t have issues with the logs, 3.0 is not affected by that.

4

Hi, thanks for the reply and your time! :slightly_smiling_face:

Curiously, the Apple CarPlay feature is working perfectly fine! - So I guess I’m cleared from this issue…
Thanks for explaining the whole RWData issue. Maybe I read a lot of non-sense regarding this old version I have here…

5

Hi, thanks for replying and your time! :grinning_face_with_smiling_eyes: - Real quick for weekday!

Well, it’s truly unknown to me what Ford did behind the scenes but the screen and the module look new enough (at least not worn or dusty) when I was at their repair center.

Thanks for clearing out the whole logs situation. I might have read a lot of non-sense when trying to figure out what was going on with the previously APIM that got replaced - That one had INSTL_ERR12 and was not saving anything. I am afraid the new one might suffer the same.

In fact, there’s a lot of people with problems under the same version I’m running at the moment, might be just a coincidence that this is the version that Ford shipped these devices with. Or that they physically fail often.

All in all, I guess my best bet is to hope this “new” module does not degrade so fast if ever since I basically can’t do anything update-wise.

Since you’re also a moderator - May you kindly close this “Support Ticket”?
Thanks again everyone!