Haha! Awesome!
Synch 3 Wifi update
- Thread starter XMan
- Start date
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.
Haha! Awesome!
Thanks. I'm up near Fairfax (in the part of VA Richmond doesn't recognize). I'll try your recommendations tomorrow, and let you know what happened. Cheers!
NoVA, yeah, we only claim ya’ll when it is convenient... [emoji23]
GeezingInVA
Well-Known Member
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".
Cheers!
17LimitedExpy
Full Access Members
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".
Cheers!
Just to confirm...you’ve tried updating via wi-fi and that gives you the same error message?
17LimitedExpy
Full Access Members
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
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
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
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.
