The Ford website gives me files to update to 3.0.20204. The process fails with a mem_error03 on my 2017 Ford Escape (no maps), so I thought I’d try Syn3Updater. It lists several potential versions for me to install, but none of them are 3.0.20204. Should I try a version less than 20204 (3.0.20196) or go straight to the latest version offered?
Additionally, will using Syn3Updater likely get me around the mem error I get when I try to install using the Ford website download?
Ford offers updates that they will support thru their dealerships and other channels. 3.0.20204 is the latest ‘supported by Ford’ version for your production platform, Sync 3.0. Although Ford does not support 3.4 on your vintage Sync 3.0 unit, it will work fine. Since you have a Non-Navigation APIM, you might not be able to reinstall Gracenotes due to insufficient memory, if that is important to you.
Thank you.
I created an “Interrogator Log” USB, plugged it in, and my sync unit says “Updating System Software” for almost a half-hour now. I expected a few minutes. Do I let it keep going?
You are on a very old version of Sync3 v2.0.16074 14.03.2016. Try doing a Master Reset and then run the tool. If it does not work, try -AC version. There are reported issues using the tool on the very old versions like this.
You might have to update to Sync3 version 2.2 first if you want to update to 3.0.20204. Or just go to 3.4 direct using reformat.
You are a patient person, and I’m grateful for your help. How would I update to version 2.2? I can’t do that with Syn3Updater, right? That leaves me with a couple of questions:
Where would I get the 2.2 files that go in SyncMyRide?
What would be the proper settings in the autoinstall.lst?
If I create a logger using your tool, it produces an autoinstall that contains the word "Tool - " on the item line, and “Options = AutoInstall” at the end. The example shown on the document you pointed me to a couple of paragraphs up doesn’t have the "Tool - " bit, and the end is “Options = Delay, Include, Transaction”. What is the difference?
Both -AB & -AC versions of the logger worked - sort of - after doing a master reset. They both produced identical xml files. However, the Syn3Updater tool gets an error trying to read the resulting XML:
The contents of the xml file file, with the VIN obfuscated:
You have an overlay installed on you Sync system as indicated in the XML file 8060 data line.
HB5T-14G386-AHA 861Kb overlay (ifs с /apps/APP_SUM)
Your present Sync version is HB5T-14G381-AJ 555Mb Sync3 v2.0.16074 14.03.2016
Your voice file is JR3T-14G391-BF 1Gb Sync3 v3.2.19137-Pre18.5
Gracenotes is not present.
The voice file and Sync app file are way out of sync as the voice file is the latest for Sync 3.0, but the Sync App file is outdated. This is the result of the failure of the Ford packaged update to complete, as the Ford packaged update deletes Gracenotes, loads the voice file first, reboots, then adds the Sync App and Gracenotes files. If you pulled the usb stick on the first reboot then the install would have failed like this. This is why the Interrogator log is having an issue.
This is the autoinstall.lst for the FORD package:
; SYNC3 Consumer Assembly Upgrade — Release 3.0.25 — Only for NonNav/NonEU assemblies.
Have you tried to just place the USB back in the vehicle, engine running, and see if it will just complete the installation?
The update from Sync Sync3 v2.0.16074 will take some time.
To fix the overlay, use: HB5T-14G387-AAA 5Kb “# This utility uninstall overlay1.img which has the IVSU fix on MY17.x Versions” (HB5T-14G386-AH[A-H]). Earlier FORD packaged updates have this file present. The file can be found in the Software Database - CyanLabs
If that is successful, you could update to Sync 3.0.20204 directly. If that fails, you need to upgrade to Sync 3 version 2.2 manually to correct this issue first, then upgrade to Sync 3.0.20204.
My autoinstall.lst file received from Ford differs slightly in the first section from the one you show:
; SYNC3 Consumer Assembly Upgrade - Release 3.0.25 - Only for NonNav/NonEU assemblies.
Before contacting you I tried a few things - I tried doing the regular update straight up from Ford. After 90 minutes I gave up & did a master reset. After that I got Error_mem03 errors which is when I tried carving it up a little by grouping the files differently in three sets (darn vague youtube videos). The first two seemed to complete, but the third errored out again with the memory error. That’s when I found your web site & starting trying things with you.
So what would you suggest?
should I fix the overlay issue before anything else, and is that done by configuring just that one file you referenced in a setup like the logger - that single file alone?
I already know that a full install of the Ford package provided to me didn’t work - should I try it with the 3.0.20204 you specified (include your changes - eliminate my extra AHK file)?
If these don’t work, how can I do the manual 2.2 upgrade as a stepping stone to 3.0.20204?
More info - I ran the HB5T-14G387-AAA overlay fix, then re-ran the logger. The log produced was identical to the one produced before running the overlay fix. Is that expected?
I can take another shot at just trying to update to 3.0.20204 directly, but would like to know if I should use the file list you provided or the original I got from Ford?
In the event the direct to 3.0.20204 fails (as it did when I first tried it), could you send me the files & autoInstall.lst file to install 2.2? It sounds like going from 2.2 to 3.0.20204 would have a greater chance of success?
Does the didType=“Embedded Consumer Applications Part Numbers 1”, didValue=“8060” string read the same as the previous xml file? Specifically the value ‘484235542d3134473338362d414841’. did you reboot the unit and master reset after that?
See your PM…
Try loading Sync 2.2 then run the Interrogator tool…
or…
Upgrade thru reformat to Sync 3.3.19052. This version has the look of Sync 3.0 and the functionality is much better.
I had not done a master reset after applying the overlay cleanup before re-running the logger. As you said, the second string in didValue=“8060” was zeroed out.
I applied the 2.2 update successfully, then did a master reset before running the logger again. The resulting log still won’t load using the syn3Updater utility. Here are the contents:
<?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-28" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
<p:VIN>1FXXXXXXXXXXXXXXX</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>HN1T-14G381-SA</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>4a5233542d3134473339312d424600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</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>c696d772</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
<d2p1:Response>9e23d1ec</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
<d2p1:Response>ab2845038000aa150000</d2p1:Response>
<d2p1:IsConfig>true</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
<d2p1:Response>555301044002401000000005</d2p1:Response>
<d2p1:IsConfig>true</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE02" didValue="DE02">
<d2p1:Response>0000010200</d2p1:Response>
<d2p1:IsConfig>true</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE03" didValue="DE03">
<d2p1:Response>01000601080001</d2p1:Response>
<d2p1:IsConfig>true</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
<d2p1:Response>18061810295f</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>1604330000000000fa00000430700057</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-CB</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="ASCII" didType="ECU Core Assembly Number" didValue="F111" responseLength="24">
<d2p1:Response>HB5T-14G380-AA</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="ASCII" didType="ECU Delivery Assembly Number" didValue="F113" responseLength="24">
<d2p1:Response>HB5T-14G371-BAG</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-BA</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>WV5V02YL</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>Blank</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="State Encoded" didType="Diagnostic Specification Version" didValue="F163" responseLength="1">
<d2p1:Response>03</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-CB</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>88:c2:55:79:ba:1b</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
<d2p1:Response>88:c2:55:79:ba:1c</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-28T07:59:31+00:00" RAM="1401401344" vmcuVersion="Vector_VMCU_02.02.20">
<d2p1:PartitionHealth type="/dev/hd0t180" total="1738631168" available="8908768"/>
<d2p1:PartitionHealth type="/dev/hd0t181" total="669047808" available="2097120"/>
<d2p1:PartitionHealth type="/dev/hd0t178" total="136764416" available="2097152"/>
<d2p1:InstallationLog/>
<d2p1:SyncData>MIIE1AYJKoZIhvcNAQcDoIIExTCCBMECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBAC7PeJH9xK4ipPbzc84rTk9eDt3KaUn9d855mZkm03vuGCqbXWi1QmhFWwZ50BUVXtNEcgvOvwVzjTYvF9FsX/PqxYxNYrjiiGh6jrtY+eCohbPcO02jDtA3SQg91aCJgCKunlFU1A0wp8+Zx24DvwAkGQpd2AUFRDO6rMkXu5YgESHcxl7mR0do+kSqclXIjyGLb5p15oxvXFQudjFHAkYqgbXASYmcrXp5H4QNrkfDebvc6EgCUAaJMInn0mvXyCYsg61n8/MJyVZ17XbrlDBHQnFvd7xRQGSlqYTGUIDZtcuGs7Svpi6YMHMv5/Uik2RE2rvrrNsINzqp5dzaKu8wggL+BgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBDl6lHcQCnsuhsjz/bsVT8bgIIC0JCXfi8njxpBpfr+Upfii5n+N3bOM6c6FEAPvgPJtbRfkZmCvKV7B7Kku9zaQuJKUtSuvhc3ioYP4SiDJmnKpoNu0n8h7gkdp0XT1WpjgQb1Fq2pmQpTk5KV2fPGGVUNlve7SwtA4Voj8G3y7psSkMB+n/UxO7kyGw51TyyZq4Qb8NZSfXknMmAETEhwlPm2A4Fw/d4FoMlzYSoBalfa8/LWu1Ba3q9M2uXFn4tkFM8znhnr/jdGvvcbQyzLcLRGtIPyJtZPejMwLmYse0b0DXWw+gDSB3zHCFdr58iWGOhFoKFQ1KgtDaxFIUQ+688hT4/YujFYnxGZysQLWyU7AP5ppckc2wi2y4sSYVV1zX3uYJAn26OPEXIeMtzStjVqAbUoO7Zvn0ePoeaLB5zGoYOHszw9q06jNhncV/hPT2Zwx92gam232rNEmWdSb4h3/v1e/wz26mwN6AP07ByMxF1qWYerXvEND/6uCUnu14XZBYS42Uzd9bsxN/sObQKLK5nPlnTzjT6/q6Z1ZXx3ylWWjH2wBmUjQTjeMj4S0hIAFCItD+yOxCPflWFd5bG/64G3q1tT4GjcpPESlWNlCnK4Ib7QJGRrHTYDkjvPCegeZTcB6P7vvhD92xXI84Nw87DAN9AGyqUuvvPXeuMZbJp3ktFDrKWpQv7on1G9JaFbC3dYFQf/RN+zYiO55ac8pCWzNJK5KHT1sg6v48gQsSWoAv9FpbMmJDNp7UNGA/fV+4bFlDe8PqKNzojGCuKbXWg/Y6CTkpYuYQ+8iNYnuEnQhvY0TcNprHcDQRDtEsrYuvd4RDNfxCqcU7VBUFpznrGK0LorGN5bEgpRhAs+1g84GB2qu5Vm6CtCLowGwAhkwDWjO/I21cN60Lhgnre1cDEQKh37bAx7Ywmh382/6oUNla5M/8PvCchS3MwqAU/VjPr4ULxwwXS7hpAIJ9GFxQ==</d2p1:SyncData>
</d2p1:AdditionalAttributes>
</p:Node>
</p:OTAModuleSnapShot>
I'm going to try updating to 3.3.19052. When I initially ran Syn3Updater it asked for my current version, which was 2.0.16074. Now that I've upgraded to 2.2, I don't see a way to update the info in Syn3Updater. Is that important before creating the 3.3.19052 installer, or is the previous version just informational?
Sorry for the late reply, had something else going on…
From the Interrogator utility output, the XML shows the overlay is gone once you updated to Sync 3 2.2.17011. This is good the version cleared the overlay as it should. You can see the result in the storage (memory) usage report at the bottom.
