Should I update 2019 Lincoln Navigator with the Syn3 updater?

scb71 · 4 December 2022 01:47

I have read through enough of the information here to be very interested however without starting on this I am still unclear whether this will work for a Lincoln as most people are talking about slightly older Ford models.I just purchased this 2019 Navigator and the system will not update via the Lincoln wifi and the Lincoln webpage says I am up to date but the car is still on 3.0.17302! If it is an improvement to move up to the newer versions, and to get the newest maps, which version is the best for a Navigator? thank you in advance for responding to my clearly a newbie inquiry.

SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.0.17302

New SYNC Version: 3.0.17302

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

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: I have the auto updater 2.11.8.0

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

nothing done yet

SaNdMaN · 4 December 2022 03:14

If it’s worth updating it’s up to you, really.
We can’t answer that question for you.

F150Chief · 4 December 2022 04:49

Yes, 2019 Lincoln Navigators came with Sync 3.0 from the factory. While the rest of Ford was transitioning to Sync 3.2 and later. This version of Sync 3 was released in 2017.
(JL7T-14G381-BK 405Mb Sync3 v3.0.17302 29.10.2017)

Your vehicle is probably equipped with a 10" screen. This will be an issue if you upgrade to Sync 3.2+ without adjusting the theme (screen display) properly. This is a simple process but does require the use of an OBD adapter and programming tool like FORScan. If you are in doubt that the upgrade would work, run the Syn3 Updater Interrogator Utility in the tools tab and post the results here. Redact your VIN if you care…

scb71 · 4 December 2022 18:47

Thanks in advance - and super glad I did not just do this. Here is what I extracted. Is this what you need in order to advise?

<?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-12-03” xsi:schemaLocation=“urn:ford/Vehicle/Module/Information/v3.0 ModuleSnapshot.xsd”>
<p:VIN>XXXXXXXXXXXXXXXXXXXX</p:VIN>
<p:ModuleName>ECU</p:ModuleName>
<p:RequestRole>
d2p1:RoleCONSUMER</d2p1:Role>
d2p1:RoleSourceOTA</d2p1:RoleSource>
d2p1:RoleDescSYNC</d2p1:RoleDesc>
d2p1:RoleIDOTA</d2p1:RoleID>
</p:RequestRole>
<p:Node isFlashed=“false” specificationCategory=“GGDS”>
d2p1:Address7D0</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:ResponseJL7T-14G381-BK</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“Packeted” didType=“Embedded Consumer Applications Part Numbers 1” didValue=“8060” responseLength=“384”>
d2p1:Response4a5233542d3134473432312d4342000000000000000000004a5233542d3134473339312d4344000000000000000000004a5233542d3134473432322d4343000000000000000000004a5233542d3134473432332d434100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“Packeted” didType=“Embedded Consumer Applications Part Numbers 1” didValue=“8061” responseLength=“384”>
d2p1:Response000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU Checksum 1” didValue=“D704” responseLength=“4”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU Checksum 2” didValue=“D705” responseLength=“4”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE00” didValue=“DE00”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE01” didValue=“DE01”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE02” didValue=“DE02”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE03” didValue=“DE03”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE04” didValue=“DE04”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE05” didValue=“DE05”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didType=“Direct Configuraation DID DE06” didValue=“DE06”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigtrue</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“On-line Diagnostic Database Reference Number” didValue=“F110” responseLength=“24”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Core Assembly Number” didValue=“F111” responseLength=“24”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Delivery Assembly Number” didValue=“F113” responseLength=“24”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Calibration Data #1 Number” didValue=“F124” responseLength=“24”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“Private Sub Node #1 Serial Number” didValue=“F141” responseLength=“16”>
d2p1:ResponseWY2F3KG5</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“State Encoded” didType=“Software Download Specification Version” didValue=“F162” responseLength=“1”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“State Encoded” didType=“Diagnostic Specification Version” didValue=“F163” responseLength=“1”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“Vehicle Manufacturer ECU Software Number” didValue=“F188” responseLength=“24”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“ASCII” didType=“ECU Serial Number” didValue=“F18C” responseLength=“16”>
d2p1:ResponseBlank</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU MAC Address 1” didValue=“F1D0” responseLength=“6”>
d2p1:Responsef8:36:9b:a3:a1:dd</d2p1:Response>
d2p1:IsConfigfalse</d2p1:IsConfig>
</d2p1:DID>
<d2p1:DID didFormat=“HEX” didType=“ECU MAC Address 2” didValue=“F1D1” responseLength=“6”>
d2p1:Responsef8:36:9b:a3:a1:de</d2p1:Response>
d2p1:IsConfigfalse</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=“2022-12-03T20:29:19+00:00” RAM=“993783808” vmcuVersion=“Vector_VMCU_02.02.20”>
<d2p1:PartitionHealth type=“/fs/usb0/” total=“115G” available=“115G”/>
<d2p1:PartitionHealth type=“/fs/tmpfs/” total=“128M” available=“124M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“1.5G” available=“41M”/>
<d2p1:PartitionHealth type=“/fs/sd/MAP/” total=“9.1G” available=“57M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“4.7G” available=“243M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“475M” available=“13M”/>
<d2p1:PartitionHealth type=“/fs/Nuance/grace” total=“1.0G” available=“5.1M”/>
<d2p1:PartitionHealth type=“/fs/rwdata/” total=“1024M” available=“641M”/>
<d2p1:PartitionHealth type=“/fs/mp/” total=“1024M” available=“221M”/>
<d2p1:PartitionHealth type=“/fs/images/” total=“26G” available=“8.1G”/>
d2p1:InstallationLog/
d2p1:SyncDataMIIEZAYJKoZIhvcNAQcDoIIEVTCCBFECAQAxggG4MIIBtAIBADCBmzCBhjEbMBkGA1UEChMSRm9yZCBNb3RvciBDb21wYW55MQswCQYDVQQGEwJVUzERMA8GA1UEBxMIRGVhcmJvcm4xHjAcBgkqhkiG9w0BCQEWD21nbXNlY0Bmb3JkLmNvbTEnMCUGA1UEAxMeU3luYyBNb2R1bGUgRW5jcnlwdGlvbiBHZW4zIEEyAhDfwyMpAoa+v0vYmqleqJR7MA0GCSqGSIb3DQEBAQUABIIBAH46g/TReGiQbxjit7YNdfhj7O9llgbBkKYUMxoCrOYlCKoRDbFY06grb3eWipwwIUuB7p3xvQyIV26JBTmfaoZlwKs+A4I/9HlcbRP2t6ejtENtpE715/6GkM6Nm4Dzecrtwl4yJddZQf1oX53aBglmSb1KTvAh0Cfrqx/QfCDWJtw+CLMDl9i4VJydXRezxgdHfpTN7T7bltZ42C661LNE+k4Ga+ZHmNBbBcqGmBtZ1vqaeTDsi61Wzfo/ha+uWYx9dfJTxiSrRLvnQqrTeYcFn2hQP31FxGHbCwa05+MWQvnaEI+uDLW2Vyj32W1scHcGI9nV76sM3O1qLZKkIeIwggKOBgkqhkiG9w0BBwEwHQYJYIZIAWUDBAEqBBA186FY9U7Pd6TgZIkLUjv7gIICYPC3MO5J7qeNawQXKzdJ5pQnNEFxhl6fWfrWbWaDo0RGzMbVEppeEFps/X6p3Rka5dg0M5KIKpeYKxAiz75WH17N2cy8MTjJSWrF/BlGA5r96q3793QlKUhZ32nARJ31SItPn2TEb9EGSOVyCjYfuap7qOHH/Y+C4+RBkGmE5m90Jbk3oDlAAtxqr1qpuBvquh9cu8KcajN4qewdp0m9iHhWJVXRbsEK971hBNZv7N6ISvUJMy1gyE4RenUOxWKyGSGUEcdsV+KU357pMq8yVddyGAHJgiRKBT8V1U68aimYJs7lqjIT6igSu2boWAObCwCOD4+oER1HBIRD+gjr5vXrjMmBChtqqITEsfI97+TiDQ8dgjjL/KMK+X7mrZ3ivvGGk70rFqL/yVjpvezYm/st9Xf7O4Gx7wxQ7COS9R157wWgA0e9iQlCMOSpGMSzITFhwXyGD6DwyZpLht7ym2GWMAxW0ccofWc097x8qoODo7ZetPfwO74rmyvgglsg3OXq1NaTFJ4dMRmP67OWUNLMzRi8rm2IwChw0AU5YrZLpVciQIxtlnF0WtGKPjH42srC9syzrDoXDkOycHLpHUzXo+7u1knZI5k25D4foPoAK+lsTjUkVxFIxEuMF7AuloguNyrMsoU0ZAEAEWEKtXfx3LLFn090h8W0MCfz/N8VDUraZjira5aEpDWUoljyHSJme2chrIvNN9k1PC3l2CkeGoIjqjIv2azu1E8ZG+iQxevuZDPRmBoiSV1fIFeqbELQu9s/q5toRREzaASZmrfMlhJWSop0BVxIlRVHMKdq</d2p1:SyncData>
</d2p1:AdditionalAttributes>
</p:Node>
</p:OTAModuleSnapShot>

F150Chief · 4 December 2022 19:12

The APIM is original and is a NA NAV version with 32GB of storage. All good there.
The installed files are:
JL7T-14G381-BK
JR3T-14G391-CD
JR3T-14G423-CA
JR3T-14G421-CB
JR3T-14G422-CC

You have 2 options for update/upgrade:
Update the APIM (Sync) to Sync 3.0.20204 with the associated system voice and Gracenote files, NA 2.20 maps and Nav Voice.
JR3T-14G424-CF NA 2.20 (No ESN lock.)
This does not require reformatting the APIM and should not need FORScan to make APIM asbuilt setting changes.
Since you will not be reformatting the APIM, this requires a rather lengthy map installation. Nothing complicated, just takes time for the installation.
The actual installation time is about 20 minutes for the Sync files and another 60 minutes for the maps.
or…
Upgrade to Sync 3.4.22251 with the associated system voice and Gracenote files, NA 2.21 maps and Nav Voice.
This requires reformatting the APIM and will need FORScan to make APIM asbuilt setting changes.
The actual installation time is about 30 minutes for all of the files. You will then need to make the FORScan asbuilt changes, which should only be 10-15 minutes to complete.
Keep in mind that if you upgrade to Sync 3.4 you cannot go back to Sync 3.0. Also, there are risks, so read the Syn3 Updater documentation.

scb71 · 5 December 2022 01:03

Thank you for the detail. So can I use the automated updater and just keep it at 3.0 as it is and add new maps? Or I guess the closest would be to update to 3.0.20204 and then add the maps you reference?

I clearly am not picking up yet on what the various files are that you linked or what I would gain by updating to 3.0.20204 but I am very surprised that there has not been a factory posted update in years to what is still a recent build car (2019 Navigator). This is all new to me and I look forward to learning but for starters I just do not want to break something that is not broken. My maps are dated but other than that I don;t know what I am missing.

F150Chief · 5 December 2022 04:49

The Syn3 Updater is for Sync 3.2+ only. It will not do Sync 3.0 versions, so that will be a manual installation. Updating to Sync 3.0.20204 is simple, then adding the NA 2.20 maps is a separate installation that is also simple but just takes time.

From posts on the Lincoln forums, every other 2019 Navigator owner is also surprised. Your maps are from 2016.
JR3T-14G421-CB Sync3 v3.0.17128 NA.1.16 (13.10.2016)

F150Chief · 19 December 2022 04:49

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