NA 2024 (Released 2025) Maps add to Syn3 Updater

NA 2024 (2.24) Maps for NA has been found online and added to Syn3 Updater! thanks once again to @AuRoN

This release only updates the Nav, Voice Nav package no new application etc.

It IS ESN locked as per other NA map packs
(it actually might not be but we don’t have the license file so can’t confirm)

Rules

  • Do not reply to this thread with general issues that are not specific to 2.24 Maps
  • If you notice a bug or change specific to this feature report it below

Failure to follow the above rules will result in your post either being moved (if moderators or myself are feeling generous) or deleted without prompt

To clarify, MEM_ERR’s, Missing Logos, LST_ERRS etc should not be posted here, make a new thread using this Support Link

Install Methods

Syn3 Updater

You can update using Syn3 Updater

Manual Method

It’s also added to the manual method available at the below link

Cutdown Maps

It’s also added to the cut down maps at the below link

Package URLs

License:
Missing (probably ESN locked anyway)

Nav Voices:
4U5T-14G422-CAP
4U5T-14G422-CBP
4U5T-14G422-CCP

Maps:
4U5T-14G421-CAH
4U5T-14G421-CBH
4U5T-14G421-CCH
4U5T-14G421-CDH
4U5T-14G421-CEH
4U5T-14G421-CFH
4U5T-14G421-CGH
4U5T-14G421-CHH
4U5T-14G421-CJH

SYNC 3 Common Issues and FAQ’s

Technical Information from FMods

— New 2024 US Maps Released —
Release date: 7 Mar 2025
Packages Date: 13 Feb 2025
Maps Date: Feb 2024

3 Likes

Do not reply to this thread with general issues that are not specific to 2.24 Maps

I’ve noticed a slight performance bump vs the previous map version on my wifes 2019 Fusion than the 23 maps, Have they ever optimized the Nav section before for more performance?

The NA224 maps are just map data and updated voices, the NAV app is part of whatever version of 3.4.x you’re running.
You’re probably seeing the result of all of the history being cleared out as well as the RW data cleaner running as part of the update package that the updater builds.

Wait a few weeks to see how it goes, because you have just reformatted the unit, so a little improvement is expected but not due to the map update…

My Sync system (23188) seems to be running better too. Finally this map update found the road I travel to and from work every day, so now it doesn’t look I’m driving through an empty field.

Hello, maybe some infoemation, when Europe have new update .
Thank you
Regarda Bostjan

As we are not ford, we do not know.

1 Like

2016 Fiesta ST
I’m trying to create a Map Update Only USB for this release and it is locked out due to the My20 Lock. I have this disabled and have tried restarting the program - still getting the same results.

This requires a reformat.
You can’t just do a map update.

After upgrading from Sync 3.0 to 3.4.23188 using CyanLabs, I recently swapped radios to get HD Radio, this changed my Sirius XM ID. Could anyone advise if my ESN changed with the radio swap? thus causing issues with the map update??

That would not affect the maps, just the SDARS.

if maps are esn locked reformat or jailbreak is the only way, that wording could probably be made a bit clearer though

Okay, so it is locked for everyone, even those of us rolling in a pre-My20 system. Have a 2016 F150 with 3.4.23188. Guess I will sit tight until it gets unlocked

Thanks for all the work and effort you all do for us

Or you just can reformat the unit and install them like any other ESN locked map in the past…

2 Likes

NA maps need to be licensed unless you install them via reformat. There is no other ‘practical’ way.

1 Like

Not gonna happen

1 Like

up until about three years ago I had subscribed to the maps. Then started using Cyan to update from 3.0 to 3.4 and used it for maps as well.

i did notice on the ford site that it says there is a 3.0 update. i think 3.0.23160 or something. I’ll stay with 3.4.

I do have one more year left on my map subscription with ford but it seems they haven’t released it yet as when i try to download it from them it brings up last years packets

If your car came with Sync 3.0.x and you’ve updated to the 3.4.x, you’re stuck on 3.4.x (or 3.3.x) there’s no going back even if you wanted to without replacing the APIM.