Interrogator Log - Error

17FlexLimited · 22 December 2024 22:17

I am planning to update a 2017MY Sync3 version 2.2 to the latest 3.4. I have no reason to believe the APIM is not the original factory unit, however I am the second owner. Since this is my wife’s DD and kid hauler, I do not want to brick the APIM. I ran the interrogator file to be safe before attempting to update and received the following error upon opening it in the updater:

"ERROR

The XML file you have selected does not contain the expected output

Syn3 Updater has determined you are on 2.2.16280 and may be using overlays

Syn3 Updater is unable to determine the configuration of your APIM"

I originally tried to update via USB with the most up to date file from Ford (version 3.0.23219) but kept receiving the error PKG_ERR03. I am using a 32GB USB formatted to exFAT. I completed a master reset with negative results. My objective is to update to a newer version, 3.4.23188 if safe to do so, or at a minimum 3.0.23219 if possible. Any assistance would be much appreciate!

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Unknown

Install Type: Unknown

Old SYNC Version: 2.2.16280

New SYNC Version: 2.2.16280

Do you have a error message, if so what is it?
The XML file you have selected does not contain the expected output

Syn3 Updater has determined you are on 2.2.16280 and may be using overlays

Syn3 Updater is unable to determine the configuration of your APIM

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: 2.13.0.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

<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="2024-12-22" xsi:schemaLocation="urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd">
<p:VIN>XXXXXXXXXXXXX</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-LG</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>484235542d3134473432312d434400000000000000000000484e31542d3134473339312d434300000000000000000000484e31542d3134473432322d434100000000000000000000484e31542d3134473432332d434100000000000000000000484235542d3134473338362d414845000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</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>01c3599d</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="HEX" didType="ECU Checksum 2" didValue="D705" responseLength="4">
<d2p1:Response>14c2100e</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE00" didValue="DE00">
<d2p1:Response>a22105030e028300000a</d2p1:Response>
<d2p1:IsConfig>true</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE01" didValue="DE01">
<d2p1:Response>434101044082000000000005</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>010011000a0004</d2p1:Response>
<d2p1:IsConfig>true</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType="Direct Configuraation DID DE04" didValue="DE04">
<d2p1:Response>198c198c2e0e</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>0a0033000000000ef900005656840069</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-BA</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-CCA</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>WW446YR6</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:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="HEX" didType="ECU MAC Address 1" didValue="F1D0" responseLength="6">
<d2p1:Response>98:5d:ad:55:da:c8</d2p1:Response>
<d2p1:IsConfig>false</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat="HEX" didType="ECU MAC Address 2" didValue="F1D1" responseLength="6">
<d2p1:Response>98:5d:ad:55:da:c9</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="2024-12-22T13:25:49+00:00" RAM="1036902400" vmcuVersion="Vector_VMCU_02.02.20">
<d2p1:PartitionHealth type="/dev/hd0t180" total="9392006144" available="54710240"/>
<d2p1:PartitionHealth type="/dev/hd0t181" total="637709312" available="2097120"/>
<d2p1:PartitionHealth type="/dev/hd0t177" total="136776704" available="2097152"/>
<d2p1:InstallationLog/>
<d2p1:SyncData>MIIE1AYJKoZIhvcNAQcDoIIExTCCBMECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBAAY3SRE51/he26xF/P/fue3cpfNda0mA8pACqn2Oz8d+a4EBIMVLZTghGiiW/e5p1Y1W+fYitR3nEc5Vk9ecYD1zHu/4Jp5shXB5PtaFprmp01IYddJUnlfXQCy/huOthKhq4OCDxiiQjKu9nqZI8EeS/eRURqSxhP+C/mBxv9/FVKMP66dt20LNqzLMjf/8226g0ajSF9BsH/ip258dGtpNjTNqAU76yx5Ia3VkPusS8YSv7GJDRGz6m7NsAMAUbs3r+d8IpcUtHVWCK7DvsLXuUpYA1sI43TWBSlyGaUx3F8utQ/gP0cK8VAhzS6sN9Ep46HibV9N9w8M+O65jfyYwggL+BgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBDSyYJvk2ciTjRkX5QAIrJvgIIC0GXywWxqgKZKYlRkMTP3e0ZnvrAIxqLJtTCEyzduIw4vA32zMgcbGhFCx8LUFnkIYL5Q94cfGti2+Ty8+NgIMYip0G+Q4kYp0y4xzVdhqEL63cIlg1vZIn5dXoRmh4BGRgLGLGPSB3rJ1zIX/J9ZH02Vp5FVz8tt8KoqNXGiYWdq018tPswLbmIvFQ+K/7JUhKo/w9FUFsz6VkKGXi8auF9HWszDoE653clSkke+EPChrZHZ9dOEi+u+xZStpShqPgBzRotzNoUfMpoSq2JF62Qhu8rdlzQ6Djo3259FD5rwq2iAzIAEXgpo3qE96FIrnRR8svgunOu6WwCi3OvRGsbaQ6JMipcD1CmByG32xjSEdh22TkMwS/PwSA+UiRSDpCYhXlrY7yWwk6MxKzUC9YsDKGKCYR93Q93hImg+iP72S6z/BgKx0yLpKZpG3BI9Qmlk26cFF/cSqOrkpwoKQK5dJqAJS5t61DPbcfqGlAnC2mWLeOZWs3MgRSIHNJTQ8q1sRF3pVLHBtF1OndtCnkX1MS3OhG855tVOoqpbi2cojhqRZsO0EFGF/fXLkhUBETIblCxBFOnvtisazFWLF5j4uZYsrRF3Ev0JvUjIZ6xfKR5+Ay+mfDnxOfpgGcm+ta2KWIVQzo61/4PUvkYYcunQgbhjhmM7ZI9rxNNpY5UFP7nOfRFnf+1ZttuLC0LR9Y0Tnw16fh4+b6Xel3qYMB1nXPxnvTmmx5FEI67Y4SwIF5hkOFu2sqvoXLVr5wrSdxa5cxLYUwvN8SQjx0WnhnFXD/he1K9z2VgnVJJEBZw1IuN0DugYMXQvXO4lAklOdmiVCD96mtErsKMyxnCP3IVsnee9MFiXwj3esBVEts5TmigTVfWuyve6stnM4MgVTGQtnqnJIvwCWPS8q2h/CCa4HaZes7x3TwOjrN9sEFxRdPAnnz4hP1w480pDLsT98w==</d2p1:SyncData>
</d2p1:AdditionalAttributes>
</p:Node>
</p:OTAModuleSnapShot>

SaNdMaN · 22 December 2024 22:36

Hello, thank you for the log.

Well, from what I’ve seen, your APIM is HB5T-14G371-CCA, which sounds about right for a MY17 model. And of course, as per the year and our hardware database, it’s not MY20.

Before moving forward, the recommendation is to ensure CarPlay and Android Auto work on 2.2 or 3.0… So for the time being, lets stick with this.

The error you are getting while trying to upgrade to 3.0 is because there’s an issue while processing the file. What kind of USB are you using?, which brand?.

Can you share the autoinstall.lst file that ford pushed your way?.

17FlexLimited · 22 December 2024 22:43

Hello and thank you for the quick response.

CarPlay and Android Auto both work via USB currently (though with the frustrating disconnect issue for seemingly no reason. Hopeful an update will correct the issue). For clarification, I have not updated to version 3.0, currently at 2.2. I have been unable to update using the Ford file.

I am using a SanDisk 32GB Ultra USB 3.0 Flash Drive (SDCZ48-032G-UAM46).

I think I have attached the autoinstall.lst file correctly. This is directly from the update from Ford.com

autoinstall.lst (613 Bytes)

SaNdMaN · 22 December 2024 22:49

Oh yes, I understood the 3.0 upgrade failed with the PKG_ERR03.
It’s a good thing that CP and AA works, one less thing to consider.

The .lst file you sent is for upgrading APPS, VOICE and GRACENOTES.
So, let’s try breaking a big update into smaller ones to see if that makes any difference.

Save the .lst file Ford sent your way for later, create a new one with this content:

[SYNCGen3.0_ALL_PRODUCT]
Item1 = APPS - JR3T-14G381-AY_1695755892000.TAR.GZ
Open1 = SyncMyRide\JR3T-14G381-AY_1695755892000.TAR.GZ
Options = AutoInstall

That will only install 3.0 without the other components, and will also tell us if the unit can process individual updates better than a big one. The tar.gz is already under the folder since that should be the file Ford sent your way, so you need to only change the autoinstall.lst file in the USB’s root.

17FlexLimited · 22 December 2024 23:03

Alright, just to confirm, the current .lst file has the following:

[SYNCGen3.0_3.0.20204_PRODUCT]
Item1 = HB5T-14G386-THB
Open1 = SyncMyRide\HB5T-14G386-THB.tar.gz
Item2 = HB5T-14G386-TCC
Open2 = SyncMyRide\HB5T-14G386-TCC.tar.gz
Item3 = HB5T-14G386-AHK
Open3 = SyncMyRide\HB5T-14G386-AHK.tar.gz
Item4 = JR3T-14G391-CE
Open4 = SyncMyRide\JR3T-14G391-CE.tar.gz
Item5 = JR3T-14G381-AY
Open5 = SyncMyRide\JR3T-14G381-AY.tar.gz
Item6 = JR3T-14G423-CB
Open6 = SyncMyRide\JR3T-14G423-CB.tar.gz
Item7 = GB5T-14G386-AE
Open7 = SyncMyRide\GB5T-14G386-AE.tar.gz
Options = AutoInstall,Delay

I should replace that with:

[SYNCGen3.0_ALL_PRODUCT]
Item1 = APPS - JR3T-14G381-AY_1695755892000.TAR.GZ
Open1 = SyncMyRide\JR3T-14G381-AY_1695755892000.TAR.GZ
Options = AutoInstall

Then replace the .lst file on the USB with the new .lst file, but keep all other tar.gz files in the SyncMyRide Folder?

SaNdMaN · 22 December 2024 23:09

Yes:

rename your current autoinstall.lst file to autoinstall.lst.ford.backup (or whatever name you want).
create a new text file named autoinstall.lst (make sure the extension is .lst and not .txt) with the content I sent before
yes, you can keep all the other files under the SyncMyRide folder because they will be used based on what the .lst file contains.

17FlexLimited · 22 December 2024 23:10

Thank you. I will report back once I am able to complete.

17FlexLimited · 23 December 2024 00:41

I attempted to update using the new .lst file I created and received a LST_ERR05 error.

I triple checked the .lst file I created and I believe it is accurate. I have attached it if you would like to review. Could the issue be that the file in the SyncMyRide folder is JR3T-14G381-AY.tar.gz and I am asking it to load JR3T-14G381-AY_1695755892000.TAR.GZ?

autoinstall.lst (241 Bytes)

SaNdMaN · 23 December 2024 01:17

Oh yes, my bad… the file named should exist under SyncMyRide folder…
It’s a good time for you to download this file JR3T-14G381-AY and save it there…
It’s the same file Ford sent you, but with a different name…

So, you would have a JR3T-14G381-AY that’s the one Ford sent you (which is called by the original autoinstall.lst file you renamed earlier) and a “new” JR3T-14G381-AY that’s referenced by the new autoinstall.lst file you created.

You could also just edit the new .lst file to call to your actual file, but I want to discard the file itself is the issue… If this works, your next partial installation could do that…

17FlexLimited · 23 December 2024 03:46

I am tracking, sounds good. I have downloaded the new file and will attempt an update again tomorrow. I will reply with the outcome. Thanks!

17FlexLimited · 23 December 2024 20:01

Success!

I was able to update the car using the downloaded tar.gz file you linked above and the new autoinstall.lst file. After upload I received the pop-up stating the installation was complete and that the USB drive could be removed. I restarted the car and everything appears and operates as expected. The About Sync menu shows version 3.0 Build 23219. Subtle visual changes from version 2.2 but noticeable improvement in performance.

So where do I go from here? Do I continue loading the rest of the tar.gz files for version 3.0? Do I run the interrogator again and see if the updater provides a different response? Attempt to load version 3.4?

SaNdMaN · 23 December 2024 22:00

Great that it worked, autoinstall by Ford has always been a little temperamental…

I believe the issue was the unit trying to process a lot of updates at the same time…
So you can continue installing packages one by one to ensure they install properly.
In fact, now that you know how the autoinstall.lst file works, you can try with the files Ford pushed your way.

The important files are:

JR3T-14G391-CE
JR3T-14G381-AY (already installed)
JR3T-14G423-CB

So, if you want you can try creating an autoinstall.lst file for each one of them, but using your current file under the SyncMyRide folder…

There’s no need for that, yet. The delta is you installing 3.0, that we know. Once you install the other 2 packages, then yes, you should run a new interrogator on the unit and upload that XML file to Ford, so that they know which packages are currently installed.

That’s a one way ticket, there’s no way to go back to 3.0 once you take that step… That’s up to you to decide… Personally, I’m still running 3.0 (the same version as you) simply because I hardly use Sync3 as an OS… I use wireless android auto for both navigation and music, I hardly see the Sync3 interface anymore…

So personally I do not see any real advantage in going to 3.4…

17FlexLimited · 24 December 2024 00:00

Thank you very much for the help. I am going to continue with the full upgrade to 3.0. I will then upload the XML file to Ford.

I’m not sure going to 3.4 is worth it as we use AA 99% of the time. I was really hoping for the most up to date maps, but I see that the NA2.23 maps will not work with version 3.0. From searching it looks like NA1.19 is the latest maps version compatible with 3.0. Do you know if that has changed? The post I found stating that info was from 2021. I am on version NA1.15 and there are some streets missing that have been built in my area since that pack was released. Nice to have as a backup if the AA starts acting up again. So far with the partial update (and possibly the previous master reset), I have not had the disconnect issue with AA after over an hour of driving. ::

SaNdMaN · 24 December 2024 00:12

There’s a guide for NA2.20 on 3.0, but it specifies the maps are ESN locked so you would need a license → Tutorial: Sync 3.0.20204 with 2020 NA2.20 Map Installation

My maps are from 2015/16 I think, I’ve used them a couple of times, mostly just for testing purposes… They will work, even in the case of an emergency…

But yes, that’s a decision you will have to make…

F150Chief · 7 January 2025 00:12

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