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?
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.
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.
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.
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.
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.
Got the first two stages to install successfully today (at 27 and 51 minutes) but I lost power before stage 3 completed. (I was only running the engine periodically to save gas and overestimated how long I had before the battery would conk out.). Ah well, third time’s the charm.