Upgrade sync 3.4 usa to eu pl

Im bought ford fusion se 2018 from usa. Im polish in eu.
I have sync 3.4 19200 without maps with polish lang, and radio fm working ue. I want upgrade sync to latest with cyanlabs updater but:

  1. I dont know what version of region i have now in my car, how to check this?
  2. If region of actual soft is not important, can i just install latest sync for eu to have polish lang and others working?
  3. If i cant install eu soft how can i patch usa soft with polish lang voices and etc?
  4. Whats happen when install eu over usa region?
    5 I dont need nav if android auto will work.
1 Like

Read this:
Tutorial: Current EU Maps Installation on US Imported Vehicles - Ford / Guides & Info - CyanLabs Official Community

Yea, i read this before but its tutorial for maps, i dont have maps and i dont need them as long as android auto will work.

If i dont need maps i still need reformat my apim asbuils and etc?

Is not posible to install only sync3 for eu region? Or install sync3 for usa region with voices from eu package?

Eu install package is about 5,5gb
Us install package is almost 2gb
Storage apim is 8gb so should install easy,
I dont wanna try because i dont wanna brick hardware so i asking, cause it look easy in theory, but too many things may goes wrong :wink:

Hello.

  1. you can create an interrogator log and run it against the unit, it will have some information about that.

  2. if your current installed SW is for NA and you have polish, you should be fine. Point 1 will also show which packages you have installed on the unit.

  3. I think so, but i do not think it would be necessary

  4. I do not think it really matters if you do not have navigation. But it’s always recommended to have matching sw region with how the APIM is configured, even if it’s a no-nav APIM, to have matching configuration. Changing regions is not recommended without changing APIM’s settings.

  5. it’s not a matter if you need or do not need nav. If the unit is no-nav, you can’t install maps.

So, run the interrogator and post the results. Make sure to redact your vin from the file’s name and content, if you care about it being publicly shown.

1 Like

Ok, i found tutorial Tutorial: APIM Interrogator Utility. give me few days and i post results

Hello, do you need further assistance with something?.

Im a little bit of scare to do this, dont wanna brick my sync :frowning: i dont have odb to use forscan too if it will be needed after upgrade
Must more read about this upgrade

Ok, that’s up to you.
I’m setting a 7 days auto closure after the last reply, I think that will give you time to decide what to do.

Also, running the interrogator log does not modify anything, and will give more information of what’s on the unit.

ok @SaNdMaN i make log and post below. btw probably something wrong with xml cause sync3 updater cant read it :frowning:

<?xml version="1.0" encoding="UTF-8"?>
<p:OTAModuleSnapShot xmlns:d2p1="urn:ford/Vehicle/Module/Information/v3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="urn:ford/com/productdesign/ipp/ModuleSnapshot/v2.0" version="2022-02-16" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
  <p:VIN>3FA6P0HD0JR213XXX</p:VIN>
  <p:ModuleName>ECU</p:ModuleName>
  <p:RequestRole>
    <d2p1:Role>CONSUMER</d2p1:Role>
    <d2p1:RoleSource>OTA</d2p1:RoleSource>
    <d2p1:RoleDesc>SYNCGEN3</d2p1:RoleDesc>
    <d2p1:RoleID>OTA</d2p1:RoleID>
  </p:RequestRole>
  <p:BroadcastDTCType>
    <d2p1:DTC DTCValue="c1620008"/>
  </p:BroadcastDTCType>
  <p:Node isFlashed="false" specificationCategory="GGDS">
    <d2p1:Address>7D0</d2p1:Address>
    <d2p1:ECUAcronym name="APIM">
      <d2p1:State>
        <d2p1:Gateway gatewayType="NONE">
          <d2p1:DID didFormat="ASCII" didType="Embedded Consumer Operating System Part Number" didValue="8033" responseLength="24">
            <d2p1:Response>5U5T-14G381-CD</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8060" responseLength="384">
            <d2p1:Response>355535542d3134473339312d414500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="Packeted" didType="Embedded Consumer Applications Part Numbers 1" didValue="8061" responseLength="384">
            <d2p1:Response>000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 1" didValue="D704" responseLength="4">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE02" didValue="DE02">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE03" didValue="DE03">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE05" didValue="DE05">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE06" didValue="DE06">
            <d2p1:Response>Blank</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="On-line Diagnostic Database Reference Number" didValue="F110" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Core Assembly Number" didValue="F111" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Delivery Assembly Number" didValue="F113" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Calibration Data #1 Number" didValue="F124" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="Private Sub Node #1 Serial Number" didValue="F141" responseLength="16">
            <d2p1:Response>VX2F0045</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="State Encoded" didType="Software Download Specification Version" didValue="F162" responseLength="1">
            <d2p1:Response>00</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="State Encoded" didType="Diagnostic Specification Version" didValue="F163" responseLength="1">
            <d2p1:Response>00</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="Vehicle Manufacturer ECU Software Number" didValue="F188" responseLength="24">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Serial Number" didValue="F18C" responseLength="16">
            <d2p1:Response>
</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 1" didValue="F1D0" responseLength="6">
            <d2p1:Response>58:7a:62:6f:d0:48</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
            <d2p1:Response>58:7a:62:6f:d0:49</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
        </d2p1:Gateway>
      </d2p1:State>
    </d2p1:ECUAcronym>
    <d2p1:ODLNetwork d2p1:NetworkDataRate="500" d2p1:NetworkName="HS-CAN" d2p1:NetworkProtocol="CAN" d2p1:DLCName="SAE J1962" d2p1:Pins="6,14"/>
    <d2p1:DTC DTCValue="c1620008"/>
    <d2p1:AdditionalAttributes logGeneratedDateTime="2022-02-16T11:38:17+00:00" RAM="444141568" vmcuVersion="Vector_VMCU_02.02.20">
      <d2p1:PartitionHealth type="/fs/Nuance/" total="1.9G" available="72M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/" total="1.2G" available="998M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/quip/" total="35M" available="35M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/quip/" total="90M" available="89M"/>
      <d2p1:PartitionHealth type="/fs/mp/" total="1.4G" available="144M"/>
      <d2p1:PartitionHealth type="/fs/images/" total="3.0G" available="956M"/>
      <d2p1:InstallationLog/>
      <d2p1:SyncData>MIIEdAYJKoZIhvcNAQcDoIIEZTCCBGECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBAHu+MenEyCa0WquOp9+PRXzcckK66FLnUcTbm2KnkRNCL/AbritObu/zPh2ElwJhWk23tO4D5Zw8kmAUS78P0xVy7pEH5f+dhBRNJwSZ4t5jN6MXIe42HIPtVu6mOzp+R8GQKSRSKIvZaktCsMQ1LYtN0tbujwTTg2mQqMB6k+HE7waqQ5UwTvX1BC25LhQYezm9irTphcZOcTQW+72M0H2m17JkUjduIR6d0eIstg12oEJx6Lmzq2QzCtybNIOo3X9EQDdNEogupJ1ypBvU1yNNO59CJqu8eigeM5q11RIf7YBykau/Lr+d10QlW0I3Rhqf1/+BPLYkZiWxc51p+eAwggKeBgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBATY4gbOPJT/0gmHNO+t167gIICcK595aDgdq2KIrU05zBefSyuFWbQtrzKtTD6hQ9LJ6Jcg6jnUtBJX/J4ulcdN4XOCrSsrXKz1Wy2ZICbLdZwEzRvI+tEBiv+XvX0uDXVVAWt871MOc3Rml8UYmySkgr8q2Kiqc2D5LR8dALCyUReyFUhfjniUvHt2doOvhFbdA3nMjhbRjRuPpxB39002wcj+emiGeWMc8UZOWF4JI9ZgKj0P/YBaGNNOkN+TSAX+FgC78ohHEL3zN+xG07jaM8s7Vzc9egG7AiNz6XuMYKaJPxnCwgUDsLIne8A5NPbNEyibuswG6wttkXyQg/YQZeGTTO8AWrUclkhD+gyR3drvIYli8Vixx7zhtP4/SLxmGQ9i2Dxqx9+AaIGtUNsYCX4eM3wT8u5YkrP/W1VvlbIurcsZq1QQ2YKb5C2UyiUfMneqWwocx6Oez/lAvAu7+YTEJfizbGfOPytX2y9wQOMSCtiLqNd+X7abBWAZQkUjOMfiQQm5P+pGsRzPOyoJwFWx+y/9P0wh6JNAPzMvMbdEnoZffPf2SiyEEeG6SRFSMr+U0mjps0/CQQ6WZLD4I2Ok7B2rJqk79J3EED0sFbZ/p+0724NjdB+ftGdMrgWmC9J5NugfDWdSk9elO4cebxqvvcwuJ0nJP8y3164tH3s76PEiYtMxDvnUT5QJGhCgiWCP1IkNchz2wwA2ev0jvdpuR1V2cE1EXpu7XTtGPd41mXsdDuL/c0UbtpGSo2a8RGRJwAOoMsUfCjHdXO2Y8fYrOYojcPn7uGr+p97GH/lx0mQMCpvjmADue7oIo1l/ubVqwY6m7ZArhHrk7ZZlJs6iQ==</d2p1:SyncData>
    </d2p1:AdditionalAttributes>
  </p:Node>
</p:OTAModuleSnapShot>

Your unit is NON-NAV with 3.0GB free, and equipped with:
5U5T-14G381-CD - Sync app file.
5U5T-14G391-AE - voice file.

You should not have any issue updating the software for these 2 files to the latest versions available in the Syn3 Updater.

So should i change region in updater?
For region eu i have 4 files to download, apps, grace, voices and something else, i dont remember now.
Should i make usb only with apps and voices from EU region or download NA apps and voices from EU?

You should be using EU as the region if you are located in EU. Since you have a NON-NAV APIM, only install the Sync app and Voice (EU). Installing Gracenotes with EU software may not fit. See this tutorial for reference about this issue.

Tutorial: Sync 3.4 NON-NAV APIM: Failure to Update to Newer Version Sync 3.4 - Ford / Guides & Info - CyanLabs Official Community

Ok, readed tutorial and have last question before i start upgrade.

Its mandatory to have at least 1.5gb free memory?
Whats for it need this memory ? This is for buffering when installs new package, or installer first copy ex. full package with voices and after restart sync it replace old by new, and then delete old?

Im asking because i dont know do i need before upgrade remove grace and voice (you said i have only apps and voices, so probably already dont have grace so dont get free memory, if i free more memory by remove voices i dont know how many free memory i get, if not enough i still cant do upgrade, and will be without voices at all :frowning: )

Ps. Sorry for my english, but i hope you understand what i mean
Thank you for your time and support

If you read the tutorial then I’m sure you read this fragment:

That’s the answer to your question. And if I may add: that comment is made for a reason. You are free to try it with less than that amount, if you ran into issues then you will know why. I’m not sure why we are talking about this, since it was also stated before that your unit has 3GB of free space…

About why is that free space needed is for package processing, remember your upgrade USB device has compressed files only.

Hmm, sorry i thought i have 3gb unit and only 956M available free memory so need to delete something to get available 1,5gb free of 3gb total

<d2p1:PartitionHealth type="/fs/images/" total=“3.0G” available=“956M”/>

So i need to delete something to get at least 1,5gb available free memo ory on my unit or no?

I apologize, I didn’t read the previous log myself, just got hung up on what it was said by f150chief.

You are correct, you do not have enough free space.
I’ve personally reviewed your log, and there’s something strange with it.
According to that log, you only have 2 packages installed, so the only thing you would be able to reduce is the voice file, nothing else.

Which version of the interrogator log did you use?
Check the USB, does it end in -AB, -AC or -AD?

on usb i have one file GB5T-14G386-AC_1587495565000.TAR
in my log i dont see tag with [5U5T-14G391-AE] like posted @F150chief

so i dont know whats happen when i use “small voice package replacement usb” if it will remove my voices how much memory i get, if will too low i cant do upgrade and dont have voices at all :slight_smile: so i hope you understand why im so inquisitive before i start upgrade :slight_smile:

btw, there is a bug in sync3updater with formating usb, it show will format but dont do that, ex, when i make usb for log i have 1 file in syncmyride folder, later when i make usb for upgrade with 4 files after “format” i have 5 files in syncmyride folder (4 files to upgrade and 1 file for log)

I see…
Please, create an interrogator log with the -AB package and see how it goes.
You can find information about how manually doing this in this link Tutorial: APIM Interrogator Utility that you previously found.

Can you attach the xml file that you already have?.

If I’m understanding correctly, that’s expected. There’s always a +1 file for the log of the USB creation. Post a screenshot if you have one.

Sync_VX2F0045_3FA6P0HD0JR213XXX.xml (9,9 KB)

and i make usb for upgrade Syn3 Updater Log - CyanLabs and i have 3 files

Item1 = ENH_DAB - 1U5T-14G658-AG_1626915602000.TAR.GZ (59MB)
Item2 = APPS - 5U5T-14G381-EU_1634769242000.TAR.GZ (867MB)
Item3 = VOICE - 5U5T-14G391-AR_1633363332000.TAR.GZ (1.6GB)

so if the biggest file is 1.6GB i should have at least 1.6GB free memory to upgrade without issues?

new log i will try to do at weekend, today car is in service to change oil and tires

Thank you for the file.
It does not say what APIM you have, which is strange. Question: prior the current 3.4 version you have, what version did the unit had? 3.0?
And if so, did you upgrade it on the past?