Sync 3 Technical Discussion
5 Year Member
Joined: Jan 2017
Posts: 73
Likes: 14
From: On the New Madrid Fault
BUT the file I downloaded (again, from Ford by the VIN of the vehicle) is JL1T-14G381-AJ, doesnt match with any of the part numbers. Did they sent me the wrong file?
Thread Starter
Senior Member
Joined: Nov 2017
Posts: 204
Likes: 98
You want the screen you had originally, that shows the IVSU versions, and expand the column so you can see the actual versions
Junior Member
Joined: Feb 2018
Posts: 5
Likes: 1
How about breaking it into two more steps, i.e., removing GN, rebooting and making sure GN was gone, then installing voice? Without GN, there should be enough room to install voice.
Another issue can be install files were not deleted in the copy and extract folders. There's a different script for that. Easier than trial and error could be to install 2.2 without voice/gn (but with the package deleting gn), then install 2.3 without gn, and if complete, install gn manually
Another issue can be install files were not deleted in the copy and extract folders. There's a different script for that. Easier than trial and error could be to install 2.2 without voice/gn (but with the package deleting gn), then install 2.3 without gn, and if complete, install gn manually
IIUC, when installing 2.2 without voice and gn, there will still be voice present on the system. This is because system was previously updated to 2.2 and there is nothing in the install process/scripts to remove voice. Verified that voice was present and gn was not after the modified 2.2 install.
That 'should have' cleaned up all temp files made more space available by not installing gn. But, still the MEM_ERR03 persists.
Thread Starter
Senior Member
Joined: Nov 2017
Posts: 204
Likes: 98
Ok, I tried both of these. No success. Still getting MEM_ERR03.
IIUC, when installing 2.2 without voice and gn, there will still be voice present on the system. This is because system was previously updated to 2.2 and there is nothing in the install process/scripts to remove voice. Verified that voice was present and gn was not after the modified 2.2 install.
That 'should have' cleaned up all temp files made more space available by not installing gn. But, still the MEM_ERR03 persists.
IIUC, when installing 2.2 without voice and gn, there will still be voice present on the system. This is because system was previously updated to 2.2 and there is nothing in the install process/scripts to remove voice. Verified that voice was present and gn was not after the modified 2.2 install.
That 'should have' cleaned up all temp files made more space available by not installing gn. But, still the MEM_ERR03 persists.
So you tried to install 2.3 without GN correct? Or did you try to install the whole 2.3 package?
I need to make one of my modules have this error and then hammer the steps out for everyone. It's going to be doable, just have to get the steps down exact
Junior Member
Joined: Feb 2018
Posts: 5
Likes: 1
; SYNC3 2.3.10 NonNav install Voice
[SYNCGen3.0_ALL]
Item1 = JL7T-14G391-BB
Open1 = SyncMyRide\JL7T-14G391-BB.tar.gz
Options = AutoInstall,Delay,Include
Trying to keep it as simple as possible.
Thread Starter
Senior Member
Joined: Nov 2017
Posts: 204
Likes: 98
Ok I've recreated the MEM_ERR on one device, now I'll look for the solution.
So you can see what's happening, here's a 2.2 system with GN removed prior to trying to install 2.3
And here it is right before MEM_ERR03 after it has copied VOICE but before it's unpacked
Look at the size of voice.img and pay attention to /dev/hd0t180 ....
I have an idea of hopefully a simple fix. Going to try it now
So you can see what's happening, here's a 2.2 system with GN removed prior to trying to install 2.3
Code:
/dev/blk/ram-0-allo 128M 1.0M 127M 1% /fs/tmpfs/ /fs/images/map.img 139M 137M 1.9M 99% /fs/sd/MAP/ /fs/images/voice.im 1.4G 1.3G 70M 96% /fs/Nuance/ /dev/hd0t181 1024M 351M 673M 35% /fs/rwdata/ /dev/hd0t178 1024M 894M 130M 88% /fs/mp/ /dev/hd0t180 4.2G 1.7G 2.5G 41% /fs/images/ /dev/hd0 1.9M 1.9M 0 100% /dev/hd0t182 /dev/hd0 1.0G 1.0G 0 100% /dev/hd0t177 /dev/hd0 32M 32M 0 100% /dev/hd0t6 /dev/hd0 7.2G 7.2G 0 100%
Code:
/dev/umass0t7 30G 18G 12G 61% /fs/usb0/ /dev/blk/ram-0-allo 128M 1.0M 127M 1% /fs/tmpfs/ /fs/images/map.img 139M 137M 1.9M 99% /fs/sd/MAP/ /fs/images/voice.im 1.4G 1.3G 70M 96% /fs/Nuance/ /dev/hd0t181 1024M 147M 877M 15% /fs/rwdata/ /dev/hd0t178 1024M 894M 130M 88% /fs/mp/ /dev/hd0t180 4.2G 2.8G 1.3G 68% /fs/images/ /dev/umass0 30G 30G 0 100% /dev/hd0 1.9M 1.9M 0 100% /dev/hd0t182 /dev/hd0 1.0G 1.0G 0 100% /dev/hd0t177 /dev/hd0 32M 32M 0 100% /dev/hd0t6 /dev/hd0 7.2G 7.2G 0 100%
I have an idea of hopefully a simple fix. Going to try it now
Thread Starter
Senior Member
Joined: Nov 2017
Posts: 204
Likes: 98
Ok the trick looks promising .... now look at /dev/hd0t180
EDIT: for some reason I can't reformat the code below to look like above,but the take home msg is there's now 3.4GB free where before there was 1.3GB .... and Voice needs 1.5GB
EDIT: for some reason I can't reformat the code below to look like above,but the take home msg is there's now 3.4GB free where before there was 1.3GB .... and Voice needs 1.5GB
Code:
/dev/umass0t7 30G 18G 12G 61% /fs/usb0/ /dev/blk/ram-0-allo 128M 1.0M 127M 1% /fs/tmpfs/ /fs/images/map.img 139M 137M 1.9M 99% /fs/sd/MAP/ /fs/images/voice.im 475M 462M 13M 98% /fs/Nuance/ /dev/hd0t181 1024M 150M 874M 15% /fs/rwdata/ /fs/images/overlay1 3.9M 1.2M 2.7M 32% /fs/mp/ /dev/hd0t178 1024M 894M 130M 88% /fs/mp/ /dev/hd0t180 4.2G 787M 3.4G 19% /fs/images/ /dev/umass0 30G 30G 0 100% /dev/hd0 1.9M 1.9M 0 100% /dev/hd0t182 /dev/hd0 1.0G 1.0G 0 100% /dev/hd0t177 /dev/hd0 32M 32M 0 100% /dev/hd0t6 /dev/hd0 7.2G 7.2G 0 100%
Last edited by Acool; Feb 7, 2018 at 09:08 PM.
Thread Starter
Senior Member
Joined: Nov 2017
Posts: 204
Likes: 98
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:
It's crucial you reboot after doing this or you'll have way too much space used up
@Cuch you can use this method too to get the right voice package on your system. Just remember to delete GN first
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
@Cuch you can use this method too to get the right voice package on your system. Just remember to delete GN first
Mustang Owner
Joined: Nov 2017
Posts: 43
Likes: 4
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:
It's crucial you reboot after doing this or you'll have way too much space used up
@Cuch you can use this method too to get the right voice package on your system. Just remember to delete GN first
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
@Cuch you can use this method too to get the right voice package on your system. Just remember to delete GN first
Junior Member
Joined: Feb 2018
Posts: 5
Likes: 1
I modified the process slightly in an attempt to avoid those potential other issues encountered during the 2.3 update. So, being paranoid and overly cautious I did:
From complete v2.2, installed Nav 2.2 version of Voice as per the instructions
My extra step was to then to do a modified v2.2 install without GN or Voice. The thought is that this would clean up any left over temporary files or state and leave the maximum amount of free space. Although, just getting rid of 2.2 non-nav voice as in step 1 should be sufficient.
I then installed the complete v2.3 update. It worked without issue, and ran to the update complete screen.
I verified all SW versions and everything looks good.
Thanks again!