I tried to update my Sync 3.4 system to 3.4.23188 and followed all steps.
Once I plugged in the USB, I got the message on the top left that it’s update system and it remains that way for a long time but no update starting.
I plug the USB out, it still says updating system on the top left. I need to switch off and switch on the car, so that the “updating system” status goes away.
I’m not sure what’s going wrong ? checked the USB on my computer, but doesnt look like there’s any change or update to logs.
Any help would be appreciated.
SYNC Region: NA
Navigation Variant: Nav
Manufacturer Year: Pre MY20
Install Type: OEM
Old SYNC Version: 3.4.19101
New SYNC Version: 3.4.19101
Do you have a error message, if so what is it?
None
Thanks a lot I will check this out, but im not 100% sure if my unit is non-nav or nav. My car is a USA import model into the Middle East. Initially, it did not come with Navigation but later a dealer added navigation of Middle East Maps to it. The dealer unfortunately is not willing to tell me how he added the maps to the sync unit. Currently I can use those maps for navigation but since Carplay is there I dont use it at all, so I dont mind if it goes away.
The reason im not sure if my unit is considered Maps or not is because under my Sync settings, I dont see the navigation maps version that i’ve seen in some SYNC update videos online.
Not sure if it’s imp., but my Grace Notes version shows “NA”.
Would you happen to tell if my unit is considered Nav or Non-Nav based on the above ?
I have followed certain steps of the guide you sent and done the following.
Created a RW data cleaner USB and used it
then Created a downgrade USB from the tools tab and used it but while trying to downgrade it gives me an error code: MEM_ERRO3.
I will try gracenotes, small voice, rw packages and then try to downgrade to remove the maps.
I wanted to clarify the best downgrade method, is it through the tools tab to create a downgrade USB directly OR is it through the home tab where you get to select region, versions and packages.
also, between executing gracenotes removal, small voice and rw packages, should I soft reset ?
“Downgrade” is this context ambiguous, so let me clarify that term:
Downgrading in the term of syn3updater is installing a 3.3.xxxx build to later reformat the unit. This is required because the reformat tool is blacklisted in later 3.4 builds, so you need to down-grade Sync3 to a version where running the reformat tool is allowed
In the context of the guide, downgrading is doing that: installing 3.3.xxxx because it’s smaller, hence releasing some storage on the unit. So you are down-grading from 3.4 to 3.3, but without a reformat (yet)
You can’t reformat MY20 APIMs, that’s why it’s imperative for you to confirm which APIM model you have.
You can’t remove MAPs without reformatting the unit.
So try making some space by removing Gracenotes and installing the small voice package, then maybe you can continue with Sync3 3.3.xxxx…
before plugging in any USB, I did the bezel diagnostics to try to find the APIM and it shows Assemby Part Number and H/W part number as empty. VMCU version as 5.2.8.0, CCPU as 3.4.19101_PRODUCT, Navigation Applicaltion Ver: 9.32.7.134897. Map Database Ver: 2020.Q4. Voice Control Application Ver: 68.10_RC1. POI Database Version: 2020.Q4.
Then I continued with USBs to remove, gracenotes, reduce voice, RW data and then finally I did the downgrade USB which I set up from the Tools tab using the Syn3 updater. It worked, it downgraded the Sync to 3.3.19052 and I did a master reset, everything works fine and it still has maps.
I then did an interrogator log, and weirdly it shows the APIM Model number now. Check it out below.
Reformat, yes, so that the installation mode is overwrote for this install.
Try a “full” install with all the packages installed… if for whatever reason that fails (based on the APIM being 8GB), remove Gracenotes from the installation and try again. (you do not need to redo the USB, just edit the reformat.lst file and remove the line that points to the gracenotes package.
Correct, that will install and run the reformat phase.
I am happy to report that it worked! The final interrogator log is below.
Thank you very much Sandman ! I even used one of the fixes found on these Forums to remove the navigation tab button from Sync using Forscan.
There’s only 1 small issue, the splash screen is now fixed on the standard Blue Ford Oval, even though in Forscan it shows that it’s the Ford GT one as I had previously set up. I tried to change it to default and then change it back to Ford GT but the Splash Screen still remained as the Standard Blue Ford Oval.
Glad we are almost there.
Can you share a photo or screenshot of the APIM’s asbuilt viewed through Forscan? (the section with the numbers, not the easy menu).
Also, when you changed the settings through Forscan, did you reset the module afterwards?.
This was my APIM AsBuilt before I changed 7D0-01-02-04XX-XXXX-XXXX to 7D0-01-02-00XX-XXXX-XXXX to remove the navigation button from the sync system.
Actually, i’ve never reset module’s after changing settings on Forscan ? is it necessary ? do you mind telling me how to do it ? I’ve done changes to other modules as well before, should I reset those modules too ?
I did a bit of read up and found that the Ford GT splash is not available in sync 3.4. So technically there’s no issue and I was able to go into the bezel diagnostics screen and change the splash to the mustang GT one. I think we’re all good now.
Please still do let me know about the resetting the module and if it’s required.
If you make changes to a module that affect the feature set or function, or especially change the software or firmware, you should always reset the module to clear the old cache files. If the module is working fine and not sluggish, you could leave it be.
