NA 1 19 to NA 2 20 map upgrade issue

I have a 2016 Edge currently running Sync 3.3.19052 (I didn’t want to pay for the USB hub replacement required for 3.4.x) with NA 1 19 maps. I tried to use Cyan Labs’ tool to update to the latest, NA 2 20, using the “update maps only” option. So I downloaded the updates onto a 32GB USB stick.

Sync detected the update and spent 27 minutes updating. I was driving for most of this time, but stayed in the garage with the power on for the final 10 minutes to ensure the system didn’t shut off mid-update. I received the “update successful, restart required” notifications, so rebooted, and…the Sync 3 Version status still showed maps at NA 1 19. Rebooted again…same thing again.

Nav is working as expected and I can’t tell if I actually have NA 1 19 or NA 2 20 since I haven’t found any differences yet. But shouldn’t the reported version have changed? Should I try installing again, or instead go for the full install (overwriting 3.3.19052 with 3.3.19052 again)? Is it possible this is a licensing issue since NA 1 19 was purchased from Ford and NA 2 20 was through the tool?

This is the post you want and need to read → North America 2.20 Map Installation (Stand-Alone without Reformat)

Even though it’s a manual method, that’s what Syn3updater does, so the requirements and instructions are the same.

You will find all your answers about “maps only” update there.

If you ask me, having the chance of just reformatting, I would not perform a partial update since it take a lot of time.

Perfect, thank you! I did search the forums before posting but didn’t come up with that thread.

You may have updated successfully, as 3.3 has a bug that does not report the map update correctly. Run the APIM Interrogator Tool thru the Syn3 Updater and look at the installed files in the center window in the app once you open the XML. It will list the map files.

Interesting…I will have to try that first then. Thanks!

Is there any documentation available for the bug? Specifically, is it known if a master reset (or any other approach) would clear the error? I didn’t find much in site or Google searches.

Not documented by Ford, but it is acknowledged. It is fixed in 3.4.
Ford Releases Sync 3 v3.4.39 for some 2019 vehicles with v3.3 - Page 32 - Ford F150 Forum - Community of Ford Truck Fans

Hmm…unfortunately Interrogator did not report the map file names; it only reported partition sizes. Here’s the entire XML output (with VPN masked, but as mentioned it’s a 2016 Edge Titanium originally loaded with 3.0.x). Any help in confirming which map version I actually have would be appreciated!

If this XML isn’t sufficient to confirm version, if anyone knows of a definite change between NA 1 19 and NA 2 20, I’ll check for its presence in my map copy. Thanks.

<?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="2021-09-16" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
  <p:VIN>xxx</p:VIN>
  <p:ModuleName>ECU</p:ModuleName>
  <p:RequestRole>
    <d2p1:Role>CONSUMER</d2p1:Role>
    <d2p1:RoleSource>OTA</d2p1:RoleSource>
    <d2p1:RoleDesc>SYNC</d2p1:RoleDesc>
    <d2p1:RoleID>OTA</d2p1:RoleID>
  </p:RequestRole>
  <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>4U5T-14G381-AN</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>345535542d3134473432312d434143000000000000000000345535542d3134473432312d434243000000000000000000345535542d3134473432312d434344000000000000000000345535542d3134473432312d434443000000000000000000345535542d3134473432312d434543000000000000000000345535542d3134473432312d434643000000000000000000345535542d3134473432312d434743000000000000000000345535542d3134473432312d434844000000000000000000345535542d3134473432312d434a44000000000000000000345535542d3134473339312d434a00000000000000000000345535542d3134473432322d434148000000000000000000345535542d3134473432332d434100000000000000000000345535542d3134473432342d434400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</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>30d5d1c1</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
            <d2p1:Response>58b42674</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
            <d2p1:Response>aa2a050304028b00068a</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
            <d2p1:Response>55530104e403408000000000</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE02" didValue="DE02">
            <d2p1:Response>0000000200</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE03" didValue="DE03">
            <d2p1:Response>01000300000007</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
            <d2p1:Response>1ba31b9b2bc5</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE05" didValue="DE05">
            <d2p1:Response>80</d2p1:Response>
            <d2p1:IsConfig>true</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didType="Direct Configuraation DID DE06" didValue="DE06">
            <d2p1:Response>08003300000000186a00005656850070</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>DS-GB5T-14G371-AF</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Core Assembly Number" didValue="F111" responseLength="24">
            <d2p1:Response>GB5T-14G380-BC</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="ASCII" didType="ECU Delivery Assembly Number" didValue="F113" responseLength="24">
            <d2p1:Response>GB5T-14G371-CFC</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>GB5T-14G375-CA</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>WV1M01P1</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>GB5T-14G374-AF</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>68:c9:0b:ea:95:54</d2p1:Response>
            <d2p1:IsConfig>false</d2p1:IsConfig>
          </d2p1:DID>
          <d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
            <d2p1:Response>68:c9:0b:ea:95:55</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:AdditionalAttributes logGeneratedDateTime="2021-09-16T14:42:45+00:00" RAM="1057136640" vmcuVersion="Vector_VMCU_02.02.20">
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.4G" available="12M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.4G" available="36K"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.4G" available="148K"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.3G" available="12M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="937M" available="2.8M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.3G" available="8.5M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.7G" available="16M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="1.7G" available="16M"/>
      <d2p1:PartitionHealth type="/fs/sd/MAP/" total="2.0G" available="13M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="2.6G" available="25M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/" total="480M" available="23M"/>
      <d2p1:PartitionHealth type="/fs/Nuance/grace" total="1.0G" available="57M"/>
      <d2p1:PartitionHealth type="/fs/rwdata/" total="1.2G" available="708M"/>
      <d2p1:PartitionHealth type="/fs/mp/" total="1.4G" available="505M"/>
      <d2p1:PartitionHealth type="/fs/images/" total="25G" available="6.2G"/>
      <d2p1:InstallationLog/>
      <d2p1:SyncData>MIIEtAYJKoZIhvcNAQcDoIIEpTCCBKECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBAHQMsmmiuwYrIalO8HqcHTtxBm47BErQsadp6c7iUkqCoRnmbFEGylSsFdsQtyiTxNevrGryhtQkhBHMLJDmaDBBSkl2wgsL1Hph5eAlTTyMEQwC+TkcUq56xXj+YCIUrqdGJHMbcszxoTLZv3V8HmwHkOvg/+V2IL+ULZbKH9kaXVHupb9fZPReUJexWZSJjGPguaKFQTn18DPJxEEW/NDJNldOrsgJq7MBMJKDAzlVNM6Yp46uujtWkw5K4RVtUM0JnqG+3626OTKZkjwE5tNIDFox3crf4nz2bw9tsB9VPcov4ZyAjN2/JpuNzFh5pgr6+SlffZ3PNMADUSCwGEEwggLeBgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBAk3opY+pyytwuPMNzB2MQegIICsLY6xF27toluwcZm2qnbY0DVfx7SOHF0s1I+SjKGhs6dcNC/hL5uxxTUSNcLwG0AaLTnXt0vMfo9KlgTufgBcWG81xvYzNtMKI/v8JkTs8X+HwCH8P0FdFXorUDTJRoeyR8P41fw7ozlwYcgxkPZpiFGhZBrJQD/jkGffjceJR1yFND113SsZ1gHSCjZy8n5bC7cKmiForm3Og/XBs/20AygsWniGr13/JBmWtq8dcVUiAGvtgbvd3BvNaUow3LVE/9q/do4J8sFDk5B9Uvk2zbr+OYvyjImOEH3+kwCDzQ83ZwQ9peWLIX22C6Zm6lDDRZZYMyuZe3k71IsRXTsFry/lE+gG5uOxbY2T2qzS9KQJgM/6wTCblzWWVnt7W7mOf4Be8msWT3I8OsCkQMBrlqTc1N2O1GcrgFKaw58VtywWnFYSIgL6FVYFan3uihELSAIGC43XZXZ5u9b4V66N81BqfRHYPuO5Nl7QoyZI9mdSWWLBSsu2AQzp0FVz7Tq1oe4NATsmMjWyHwt5Hg2ukxSwgjC/YTvGBmGqviJltYHwZ8St++OFlBkUVvHrUuc9hBeK6ss9nC39+oOy9LYE1qC3xLok34CGfh7utj800BpRj3Rw1NvqngQpid7SU4WCkwh0LdNksdp0mezsAEXjz3HdjY9kk24j40LLOFqd5sLMGfbHy6bysP/4orCAxlgQgR79hSonji3XGLzIjQHABAN2O2l0gfuS8TEQDNit5t16izK0Ey+Ievq29V0HVkBuC+MSVtaBYk0wh/D9ywghovVwgvJG0fqZ+IcSK6I4dxlTFeh2c8UdSnggyEg3vAgszxUfYgRNZNBoI4Nlh2N2dkN+yQNvr8KwcjIqQBGxY4xjM4rP9VdtTzM338H2S0FkNAnKRKGox8kAqF50EGIm1s=</d2p1:SyncData>
    </d2p1:AdditionalAttributes>
  </p:Node>
</p:OTAModuleSnapShot>

this was alpha functionality, literally as of about 5 minutes ago is now in the latest release :slight_smile:

1 Like

4U5T-14G421-CAC
4U5T-14G421-CBC
4U5T-14G421-CCD
4U5T-14G421-CDC
4U5T-14G421-CEC
4U5T-14G421-CFC
4U5T-14G421-CGC
4U5T-14G421-CHD
4U5T-14G421-CJD
4U5T-14G391-CJ
4U5T-14G422-CAH
4U5T-14G423-CA
4U5T-14G424-CD

Your update did not complete according to the above data. Probably becauase you pulled the usb on the first of 3 reboots for the upgrade. Also, be advised that 3.3.19052 has a bug that it will not report the map upgrade properly. The fix is to upgrade to 3.4.

See this tutorial for reference…
North America 2.20 Map Installation (Stand-Alone without Reformat) - Ford / Guides & Info - CyanLabs Official Community

Thanks both. I wondered if I pulled it too early per the article. I didn’t expect to need to leave it in when I received the “update complete, you can remove the USB now” message, and hadn’t yet read the article when I tried to upgrade. I’ll give it another try.

I may also temporarily update to 3.4.x (despite the USB hub incompatibility) just to get the string to set correctly, then downgrade again. Not sure it’s worth that effort though. In a way I wish I’d left it on 3.0.x. Oh well, too late now - not possible to downgrade that far as far as I’m aware.

Upgrade to the latest 3.4.21194 and see how you like it. You can just downgrade to 3.3.19052 thru autoinstall if you don’t like it. You cannot downgrade back to 3.0, unfortunately. Make sure you downgrade the voice file also if you go back to 3.3.

As far as the maps, just run the install over again and let it reboot several times per the tutorial. It will take close to 90 minutes via autoinstall or 29 minutes via reformat.

By the way…
If you don’t use an iPhone, you don’t need to replace the hub. But you will get the nagging message on each start. The hub for your vehicle is about $55.00, and is part number HC3Z-19A387-E (BLUE BACKLIGHTING) Ford (Wide 2 USB-A Port) or -F.

Here is an example: OEM Genuine Ford APPLE CARPLAY Interface Module -Sync 3 Only- HC3Z-19A387-F Blue | eBay

Yeah, the nagging message is the main reason I don’t upgrade to 3.4.x. And I use a USB stick with a bunch of MP3s on road trips so I don’t want to disable the USB hub. I may spring for the $55; we’ll see. Thanks.

1 Like

Just don’t buy the hubs from Amazon (ALLWAY) or others who are not OEM, as these are not always the real thing…some are remanufactured.