Synch 3 Wifi update

Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.

GeezingInVA

Well-Known Member
Joined
Jul 3, 2015
Posts
49
Reaction score
9
Location
Clifton, VA USA
I actually envy some of the problems/issues posted. I can't get past the "Installation Failed; Error Code: MEM_ERR03" when trying to update/upgrade from vers 2.2 on my non-nav 2016 Limited. I've tried the hardware and procedure alternatives/recommendations found in this thread and others, including trying with an assortment of (newly full-formatted exFAT) 32GB/64GB/128GB USB2.0 and USB3.1 thumb drives from SanDisk, PNY, and Corsair. Even though awhile back I was able to update to vers 2.2 from the original factory-installed vers 1.0, I was never able to update to vers 2.3 and now vers 3.0. Consider yourselves "lucky". Cheers!
 
Last edited:

chuck s

Full Access Members
Joined
Dec 20, 2006
Posts
1,990
Reaction score
753
Location
Chesterfield, VA (that's south of Richmond, y'all)
SYNC 3 v2.2 – APIM Programming Installation Failed Error – 2016-2017 Ford/Lincoln
oemdtc May 24, 2017 Diagnostic Tips


2016-2017 Ford/LincolnSYNC 3 v2.2 – APIM Programming Installation Failed Error

A ‘Installation Failed Error Code: MEM_ERR03’ error message may occur when programming the SYNC module to v2.2.



Programming tips:

The USB flash drive must be 32GB formatted to exFAT.

Do not remove the USB flash drive from the media hub until the final installation message is displayed (non-Nav vehicles have two installation complete messages).

Perform a complete ignition cycle by turning the key off for 5 minutes (open/close driver’s door) which is critical for a successful installation.

If these tips are ineffective, perform a SYNC master reset (Settings ⇒ General ⇒ Master Reset), ignition OFF for 5 minutes, ignition ON, and insert the USB drive again to complete programming.

If the message is still present, no additional repairs should be attempted.

Engineering is aware and is currently investigating. Monitor OASIS for future updates.

https://ford.oemdtc.com/2809/sync-3...stallation-failed-error-2016-2017-fordlincoln
 

GeezingInVA

Well-Known Member
Joined
Jul 3, 2015
Posts
49
Reaction score
9
Location
Clifton, VA USA
Thanks, chuck s. I'm ready to try anything short of having to take my Limited back to the dealer to have them try to update our SYNC3 to vers 3.0. Cheers!
 

GeezingInVA

Well-Known Member
Joined
Jul 3, 2015
Posts
49
Reaction score
9
Location
Clifton, VA USA
SYNC 3 v2.2 – APIM Programming Installation Failed Error – 2016-2017 Ford/Lincoln
oemdtc May 24, 2017 Diagnostic Tips

Thanks, again, chuck s. Tried that; same results. I even broke down and called the 800 help number on the displayed error message. I followed their "tap your head while you rub your belly, open/close the driver's door, skip around the vehicle clockwise twice and counter-clockwise once, and then sing all verses of Born In The USA"... and that didn't help either. :insane:

Just like I finally gave up with updating from vers 2.2 to vers 2.3 on my own, I'll just wait until the next regrettable need to have to break down (pun intended) to go to the dealer, then have them try to update to vers 3.0. (Maybe by then we'll have vers 4.0?)
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
I actually envy some of the problems/issues posted. I can't get past the "Installation Failed; Error Code: MEM_ERR03" when trying to update/upgrade from vers 2.2 on my non-nav 2016 Limited. I've tried the hardware and procedure alternatives/recommendations found in this thread and others, including trying with an assortment of (newly full-formatted exFAT) 32GB/64GB/128GB USB2.0 and USB3.1 thumb drives from SanDisk, PNY, and Corsair. Even though awhile back I was able to update to vers 2.2 from the original factory-installed vers 1.0, I was never able to update to vers 2.3 and now vers 3.0. Consider yourselves "lucky". Cheers!

You live anywhere near Richmond or Norfolk? If you do, let’s catch up and I should be able to get you straight. Send me a private Message.

The Non-Nav systems are WAY more of a pain than the Nav version and are more dependent on the Flash drive than the Nav version because of their limited storage memory.

I have done Nav updates using a 4GB Drive, but the Non-Nav I have not been successful with anything less than a 16GB, but you should have that covered with what you tried.

If you are willing to try it one more time follow these steps:

1) Turn off your antivirus if you are running one while you are downloading and installing to flash drive.
2) Download Update again.
3) Format flash drive to ExFat, Full not quick/fast
4) Remove flash drive
5) Reinsert flash drive and copy files to flash drive
6) Remove Drive, and turn AV back on
7) Start Car and wait for Sync to come all the way up
8) Turn off Audio and HVAC
9) Reboot unit 2 complete times(Holding Power and Next Track for 6+ Seconds), waiting between each reboot for Sync to boot all the way.
10) Insert Flash Drive with NOTHING else plugged in to the other USB ports if you have more than one.
11) Follow instructions on screen.

I have been using a Drive recently that has a flashing LED to indicate access. It helps me to know something is happening.

Yell back how it goes.
 

GeezingInVA

Well-Known Member
Joined
Jul 3, 2015
Posts
49
Reaction score
9
Location
Clifton, VA USA
You live anywhere near Richmond or Norfolk? If you do, let’s catch up and I should be able to get you straight. Send me a private Message.

Yell back how it goes.

Thanks. I'm up near Fairfax (in the part of VA Richmond doesn't recognize :sorrysign: ). I'll try your recommendations tomorrow, and let you know what happened. Cheers!
 

GeezingInVA

Well-Known Member
Joined
Jul 3, 2015
Posts
49
Reaction score
9
Location
Clifton, VA USA
I have been using a Drive recently that has a flashing LED to indicate access. It helps me to know something is happening.

Yell back how it goes.

Unfortunately, same results today. The most time it was (giving me false hope) in "Updating..." state was a little more than three minutes before it abended each time with the same ‘Installation Failed Error Code: MEM_ERR03’.

Tried 32GB/64GB USB2.0 flavor thumb drives, then a 128GB USB3.1 thumb drive. All were created exactly as you recommended. Made no difference. I double-cleared/reset the unit each time before trying the next thumb drive. I couldn't observe the flashing USB thumb drives' activity LEDs because my USB hub in my console orients the LED side of the drives downwards and out of my line-of-sight. I was too lazy to go look for a small mirror to put under the thumb drives to see in a reflection if the LEDs were flashing.

I guess as you suspected, updating my non-nav SYNC3 head unit is problematic.

I'll file this one, as I did trying to update vers 2.2 to 2.3,... "If it ain't broken, don't fix it". :banghead:

Cheers! :33:
 

East-TN

Full Access Members
Air Force
Joined
Jan 4, 2018
Posts
533
Reaction score
269
Location
TN
Unfortunately, same results today. The most time it was (giving me false hope) in "Updating..." state was a little more than three minutes before it abended each time with the same ‘Installation Failed Error Code: MEM_ERR03’.

Tried 32GB/64GB USB2.0 flavor thumb drives, then a 128GB USB3.1 thumb drive. All were created exactly as you recommended. Made no difference. I double-cleared/reset the unit each time before trying the next thumb drive. I couldn't observe the flashing USB thumb drives' activity LEDs because my USB hub in my console orients the LED side of the drives downwards and out of my line-of-sight. I was too lazy to go look for a small mirror to put under the thumb drives to see in a reflection if the LEDs were flashing.

I guess as you suspected, updating my non-nav SYNC3 head unit is problematic.

I'll file this one, as I did trying to update vers 2.2 to 2.3,... "If it ain't broken, don't fix it". :banghead:

Cheers! :33:

Just to confirm...you’ve tried updating via wi-fi and that gives you the same error message?
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
This may help...Mustang and F-150 non-Nav types are getting same ERR03 message. Let us know if this helps.

https://www.mustang6g.com/forums/showthread.php?t=100437

Here is Acool's write up from the F-150 forums:
"Ok so it worked ... I think this is the definitive way to overcome the wretched and notorious

MEM_ERR03 issue. I update the original post with more detailed instructions. But basically, if

you're on 2.2 for example, and can't install the whole 2.3 oem update without getting

MEM_ERR03, just install the voice.img file from the NAV 2.2 update. It's smaller for whatever

reason. Voice won't work, but, you'll free up enough space to install 2.3 without error and

then you'll have the proper 2.3 non nav voice package!!

Here's the install I used successfully while on 2.2, installing 2.2 Nav's voice file:
Code:

; Nav to the rescue of Non-Nav - Install this first to resolve MEM_ERR03

[SYNCGen3.0_ALL]
Item1 = HN1T-14G391-CC
Open1 = SyncMyRide\HN1T-14G391-CC.tar.gz
Options = Delay,AutoInstall

It's crucial you reboot after doing this or you'll have way too much space used up."

Here are the steps I took this afternoon.

1. Download NAV 2.2 software from #2547 (page 170 on my laptop screen) from "NEW SYNC 3 v3.0 Build 18025 Nav Android Auto/Apple Carplay" discussion thread on this forum.

2. Extract the software.

3. Delete all but HN1T-14G391-CC.tar.gz file in SyncMyRide folder

4. Edit and save the autoinstall.lst file using notepad or other text editor with below-

; Nav to the rescue of Non-Nav - Install this first to resolve MEM_ERR03

[SYNCGen3.0_ALL]
Item1 = HN1T-14G391-CC
Open1 = SyncMyRide\HN1T-14G391-CC.tar.gz
Options = Delay,AutoInstall

5. Copy the autoinstall.lst and SycMyRider folder into your USB stick. I used 16GB FAT32 formatted one, by the way.

6. Start your car and plug in your USB stick in your car.

7. Let it go through updating system process. It took about 5 minutes for me.

8. You'll get a message that it completed.

9. Turn off car and wait few minutes.

10. Restart car.

11. You'll get down arrow symbol on screen at top right that shows update completed when you click it.

12. Reboot Sync system pressing both Power button and >> fast forward button.

13. Sync will reboot.

14. After Sync is up and running again, run Master Reset in Settings (This may not be necessary, but I did it anyway).

15. After reboot completes. Turn off car

16. Reformat USB stick and copy Sync version 2.3 non-nav or 3.0 non-nav update software. (I used version 3.0 non-nav and skipped 2.3 non-nav entirely).

17. Turn on car.

18. I turned off WiFi Sync Settings screen (This may not be necessary, but I did it anyway).

19. Plug in USB stick.

20. Wait as it updates system (Mine took about 15 minutes).

21. It'll say update complete with a message popup. I pressed Close. Wait and Sync will reboot automatically. Do not unplug USB stick.

22. Sync will run like normal, but wait. It took another about 5 minutes after the Sync rebooted that the update system message came up again.

23. This time it took about 3-5 minutes to complete.

24. I got update completed message and it said that it won't take effect until restarting car.

25. Turn off car. Restart after at later time. I restarted my car 20 minutes later.

26. You'll get update completed arrow symbol again.

27. For some reason, Android Auto icon wasn't available after update to version 3.0, but once I connected my phone to USB port, it showed up.


Some notes and background info-
A. I updated with Ford official Sync version 1.0 to 2.2 April 2017. No error messages.
B. When I tried to update to official version 2.3 is when I started getting MEM_ERR03.
C. I tried to update to official version 3.0, but still had MEM_ERR03.
D. When I checked software version the other day on my version 2.2, my Grace Notes version number was missing. I know I had it after version 2.2 update because I posted completed screen shot in the discussions. I do not know when it went away. After this update, Grace Notes version number is back.




Sent from my iPad using Tapatalk
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
Here is Acool's write up from the F-150 forums:
"Ok so it worked ... I think this is the definitive way to overcome the wretched and notorious

MEM_ERR03 issue. I update the original post with more detailed instructions. But basically, if

you're on 2.2 for example, and can't install the whole 2.3 oem update without getting

MEM_ERR03, just install the voice.img file from the NAV 2.2 update. It's smaller for whatever

reason. Voice won't work, but, you'll free up enough space to install 2.3 without error and

then you'll have the proper 2.3 non nav voice package!!

Here's the install I used successfully while on 2.2, installing 2.2 Nav's voice file:
Code:

; Nav to the rescue of Non-Nav - Install this first to resolve MEM_ERR03

[SYNCGen3.0_ALL]
Item1 = HN1T-14G391-CC
Open1 = SyncMyRide\HN1T-14G391-CC.tar.gz
Options = Delay,AutoInstall

It's crucial you reboot after doing this or you'll have way too much space used up."

Here are the steps I took this afternoon.

1. Download NAV 2.2 software from #2547 (page 170 on my laptop screen) from "NEW SYNC 3 v3.0 Build 18025 Nav Android Auto/Apple Carplay" discussion thread on this forum.

2. Extract the software.

3. Delete all but HN1T-14G391-CC.tar.gz file in SyncMyRide folder

4. Edit and save the autoinstall.lst file using notepad or other text editor with below-

; Nav to the rescue of Non-Nav - Install this first to resolve MEM_ERR03

[SYNCGen3.0_ALL]
Item1 = HN1T-14G391-CC
Open1 = SyncMyRide\HN1T-14G391-CC.tar.gz
Options = Delay,AutoInstall

5. Copy the autoinstall.lst and SycMyRider folder into your USB stick. I used 16GB FAT32 formatted one, by the way.

6. Start your car and plug in your USB stick in your car.

7. Let it go through updating system process. It took about 5 minutes for me.

8. You'll get a message that it completed.

9. Turn off car and wait few minutes.

10. Restart car.

11. You'll get down arrow symbol on screen at top right that shows update completed when you click it.

12. Reboot Sync system pressing both Power button and >> fast forward button.

13. Sync will reboot.

14. After Sync is up and running again, run Master Reset in Settings (This may not be necessary, but I did it anyway).

15. After reboot completes. Turn off car

16. Reformat USB stick and copy Sync version 2.3 non-nav or 3.0 non-nav update software. (I used version 3.0 non-nav and skipped 2.3 non-nav entirely).

17. Turn on car.

18. I turned off WiFi Sync Settings screen (This may not be necessary, but I did it anyway).

19. Plug in USB stick.

20. Wait as it updates system (Mine took about 15 minutes).

21. It'll say update complete with a message popup. I pressed Close. Wait and Sync will reboot automatically. Do not unplug USB stick.

22. Sync will run like normal, but wait. It took another about 5 minutes after the Sync rebooted that the update system message came up again.

23. This time it took about 3-5 minutes to complete.

24. I got update completed message and it said that it won't take effect until restarting car.

25. Turn off car. Restart after at later time. I restarted my car 20 minutes later.

26. You'll get update completed arrow symbol again.

27. For some reason, Android Auto icon wasn't available after update to version 3.0, but once I connected my phone to USB port, it showed up.


Some notes and background info-
A. I updated with Ford official Sync version 1.0 to 2.2 April 2017. No error messages.
B. When I tried to update to official version 2.3 is when I started getting MEM_ERR03.
C. I tried to update to official version 3.0, but still had MEM_ERR03.
D. When I checked software version the other day on my version 2.2, my Grace Notes version number was missing. I know I had it after version 2.2 update because I posted completed screen shot in the discussions. I do not know when it went away. After this update, Grace Notes version number is back

Very interesting process, but confirms my suspicion that the error was caused by the limited memory the Non-Nav units have. Yell if you need the 2.2 Nav download mentioned, and I can post a link.


Sent from my iPad using Tapatalk
 

mossback

2017 Limited EL
Joined
Oct 9, 2017
Posts
359
Reaction score
176
Location
WA state
Interesting process for sure.

As far as v3.0 goes, I’m sure there are bug fixes and improvements under the hood but I haven’t noticed anything significantly different.
 

B-McD

Full Access Members
Joined
Jul 12, 2016
Posts
240
Reaction score
114
Location
Illinois
Did my update via USB today and it went well but I still have the same bugs when playing music from a USB stick. Drops the source a few times a day and reverts back to radio, about 30% of the time I try to advance to the next song there is a 20 second pause before it goes to the next song, stuff like that.
 

mossback

2017 Limited EL
Joined
Oct 9, 2017
Posts
359
Reaction score
176
Location
WA state
I've never done that. Do you just have a bunch of mp3's in a folder on the USB? Does it come up as a source when it's plugged in?
 
Top