Sync 3 Technical Discussion
11-14-2017, 01:39 PM
#1
Sync 3 Technical Discussion
New thread to discuss all things technical/modding for Sync 3. Feel free to discuss anything, not just the MEM_ERR03 problem.
But if that's what you're here reading for, here's the solution!
There's a lot of misinformation out there, even coming from Ford. The problem is NOT your USB drive, it's NOT the format (exFAT vs FAT32), it's NOT the size of your USB drive (4GB is enough), It's because Ford's install process requires you to have enough space for 1) the packed voice package (~1gb) 2) the unpacked voice package (~1.5gb) 3) the original voice package ~(1.5gb) and 4) ridiculous, but it copies into the same directory but doesn't overwrite the original voice package, so add another 1.5GB. If ford had put some delete steps in there, no one would have an issue. But the way they have it, you need about 5.5Gb but you only have 4.2 .... so the solution is to free up some space. How do you do that? Easy. For whatever reason, NAV voice.img is ~400mb. Manually install it BEFORE trying to install whatever update you're getting the MEM_ERR03. Here's an example autoinstall.lst I used to install 2.2 Nav Voice.
; 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
Step 1) Manually Install Nav Voice
Step 2) Reboot - this is important bc it won't delete the old voice.img and install files and rename voice_new.img to voice.img if you don't
Step 3) Install whatever update you were having issues with
Issues you may encounter
*Sync Software doesn't fully install on first try because that's another Ford bug and sometimes you have to try twice
- Bummer because voice is the first package installed. You probably now have a 1.5gb voice file on your APIM, which means you may have to go back to step 1 if it doesn't complete. This happened to me where it rebooted and just stayed on "Updating System Software for 20+ minutes after the first reboot ... If it is stuck there for that long it is NOT installing anymore. I removed the 2.3 USB, rebooted, as soon as it booted put the 2.3 USB back in, and it resumed installing phase 2. I did not have to go back to step 1, I'm just writing this here as I imagine not every Ford install bug is the same, and you may have to go back to step 1 if a reboot doesn't resume the install and get you all squared away in about another 20 minutes.
*You are trying to install the same version of Sync
- You can't install 2.3 on 2.3. If you are on 2.3 but without the 2.3 voice, you can still do the above but you need to manually delete GN first, then install Nav voice, then install 2.3 voice, then install GN ... alternatively, you could install 2.2 and remove voice/GN from the install making sure to leave the GN delete utility in the autoinstall, then install Nav voice, then install the complete 2.3 package
Further clarifications:
You can use any version of voice from a nav package, and any version of an upgrade or downgrade as a starting point. 2.2 was my suggestion as most people already had a copy but seems like that's more difficult now. So you could use 2.3 nav voice, and install 3.0 for example, then install the complete 2.3.
To be able to install a complete Ford package without error and without modification, the point is you need to get a voice package installed from a nav package, and you need to be installing the ultimate complete oem package from a base sync version that isn't what you want installed (i.e., don't install 2.3 onto 2.3)
Reboot probably includes turn ignition off, open door, let sleep, turn ignition on. Button reset sequence will be for sure a reboot. Master reset isn't necessary. I did it on the bench so for me reboot means cut power off then on.
I have no association with Ford
EDIT 4/18/18: I ran across this post where a user by the name of Spart on the 6g Mustang forum took the above instructions and made an easy to install downloadable MEM_ERR03 fix package, with a nice disclaimer to boot. https://www.mustang6g.com/forums/showpost.php?p=2197698&postcount=18
But if that's what you're here reading for, here's the solution!
There's a lot of misinformation out there, even coming from Ford. The problem is NOT your USB drive, it's NOT the format (exFAT vs FAT32), it's NOT the size of your USB drive (4GB is enough), It's because Ford's install process requires you to have enough space for 1) the packed voice package (~1gb) 2) the unpacked voice package (~1.5gb) 3) the original voice package ~(1.5gb) and 4) ridiculous, but it copies into the same directory but doesn't overwrite the original voice package, so add another 1.5GB. If ford had put some delete steps in there, no one would have an issue. But the way they have it, you need about 5.5Gb but you only have 4.2 .... so the solution is to free up some space. How do you do that? Easy. For whatever reason, NAV voice.img is ~400mb. Manually install it BEFORE trying to install whatever update you're getting the MEM_ERR03. Here's an example autoinstall.lst I used to install 2.2 Nav Voice.
; 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
Step 1) Manually Install Nav Voice
Step 2) Reboot - this is important bc it won't delete the old voice.img and install files and rename voice_new.img to voice.img if you don't
Step 3) Install whatever update you were having issues with
Issues you may encounter
*Sync Software doesn't fully install on first try because that's another Ford bug and sometimes you have to try twice
- Bummer because voice is the first package installed. You probably now have a 1.5gb voice file on your APIM, which means you may have to go back to step 1 if it doesn't complete. This happened to me where it rebooted and just stayed on "Updating System Software for 20+ minutes after the first reboot ... If it is stuck there for that long it is NOT installing anymore. I removed the 2.3 USB, rebooted, as soon as it booted put the 2.3 USB back in, and it resumed installing phase 2. I did not have to go back to step 1, I'm just writing this here as I imagine not every Ford install bug is the same, and you may have to go back to step 1 if a reboot doesn't resume the install and get you all squared away in about another 20 minutes.
*You are trying to install the same version of Sync
- You can't install 2.3 on 2.3. If you are on 2.3 but without the 2.3 voice, you can still do the above but you need to manually delete GN first, then install Nav voice, then install 2.3 voice, then install GN ... alternatively, you could install 2.2 and remove voice/GN from the install making sure to leave the GN delete utility in the autoinstall, then install Nav voice, then install the complete 2.3 package
Further clarifications:
You can use any version of voice from a nav package, and any version of an upgrade or downgrade as a starting point. 2.2 was my suggestion as most people already had a copy but seems like that's more difficult now. So you could use 2.3 nav voice, and install 3.0 for example, then install the complete 2.3.
To be able to install a complete Ford package without error and without modification, the point is you need to get a voice package installed from a nav package, and you need to be installing the ultimate complete oem package from a base sync version that isn't what you want installed (i.e., don't install 2.3 onto 2.3)
Reboot probably includes turn ignition off, open door, let sleep, turn ignition on. Button reset sequence will be for sure a reboot. Master reset isn't necessary. I did it on the bench so for me reboot means cut power off then on.
I have no association with Ford
EDIT 4/18/18: I ran across this post where a user by the name of Spart on the 6g Mustang forum took the above instructions and made an easy to install downloadable MEM_ERR03 fix package, with a nice disclaimer to boot. https://www.mustang6g.com/forums/showpost.php?p=2197698&postcount=18
Last edited by Acool; 04-18-2018 at 12:04 PM.
The following 11 users liked this post by Acool:
Airborne_Ape (02-05-2018),
cfoxtrot (07-29-2018),
Cuch (11-14-2017),
DragonSSCC (02-07-2018),
JFM4 (03-22-2018),
and 6 others liked this post.
Popular Reply
10-21-2019, 04:26 PM
Anyone interested in being the guinea pig for the fix, PM me and I'll give you a link to the package! You must have the "Installation in Progress" message to successfully use this version of the fix. I'm working on a second version that is a bit bigger but works when you don't have that message.
11-14-2017, 01:58 PM
#2
I can't see the `mount` points or do a `df -h` since everything is crypto-signed and hollers at me when I try...but here's the XML log's ramdisk stats:
Since I went: 1.0 -> 2.2 -> 3.0_firstbuild > 3.0_secondbuild -> 2.2 -> 2.3, I surmise the Nuance images never got cleaned, like @Acool mentioned, because I likely botched something.
I'd really like to figure out how I can clean it up and get Nuance natively installed the way it's supposed to. My theory is that I am running Nuance from the last 3.0 build, since I can't downgrade/install that ONE frigging package.
The filesystems also seem to use QNX6FS, which makes matters more difficult. Could be wrong. I try mounting them using QNX6FS on my Linux boxes to no avail.
All of this effort and time and frustration I'm spending, yet I could likely purchase a MY 16 NAV APIM and be done with it ;-)
Code:
<d2p1:PartitionHealth type="/dev/hd0t180" total="1615713280" available="8908768"/> <d2p1:PartitionHealth type="/dev/hd0t181" total="706767872" available="2097120"/> <d2p1:PartitionHealth type="/dev/hd0t177" total="136764416" available="2097152"/>
I'd really like to figure out how I can clean it up and get Nuance natively installed the way it's supposed to. My theory is that I am running Nuance from the last 3.0 build, since I can't downgrade/install that ONE frigging package.
The filesystems also seem to use QNX6FS, which makes matters more difficult. Could be wrong. I try mounting them using QNX6FS on my Linux boxes to no avail.
All of this effort and time and frustration I'm spending, yet I could likely purchase a MY 16 NAV APIM and be done with it ;-)
11-14-2017, 02:45 PM
#3
If you just buy a new module that wouldn't be fun at all!
I'll throw this disclaimer out there up front that I'm a novice at linux/unix but I know enough (or how to google commands) to be dangerous.
It does use QNX6 as the main filesystem, however, my understanding is that the QNX boot/firmware/IFS partitions can be raw, and are written raw.
I believe 1 is raw despite showing FAT16, 4 is virtual, and 7 no clue. The remaining are QNX6
/dev/sdd1 * 32 65535 65504 32M 6 FAT16
/dev/sdd2 65536 2162687 2097152 1G b1 unknown
/dev/sdd3 2162688 4259839 2097152 1G b2 unknown
/dev/sdd4 4259840 15269887 11010048 5.3G 5 Extended
/dev/sdd5 4259872 13168639 8908768 4.3G b4 unknown
/dev/sdd6 13168672 15265791 2097120 1024M b5 unknown
/dev/sdd7 15265824 15269887 4064 2M b6 unknown
I'll throw this disclaimer out there up front that I'm a novice at linux/unix but I know enough (or how to google commands) to be dangerous.
It does use QNX6 as the main filesystem, however, my understanding is that the QNX boot/firmware/IFS partitions can be raw, and are written raw.
I believe 1 is raw despite showing FAT16, 4 is virtual, and 7 no clue. The remaining are QNX6
/dev/sdd1 * 32 65535 65504 32M 6 FAT16
/dev/sdd2 65536 2162687 2097152 1G b1 unknown
/dev/sdd3 2162688 4259839 2097152 1G b2 unknown
/dev/sdd4 4259840 15269887 11010048 5.3G 5 Extended
/dev/sdd5 4259872 13168639 8908768 4.3G b4 unknown
/dev/sdd6 13168672 15265791 2097120 1024M b5 unknown
/dev/sdd7 15265824 15269887 4064 2M b6 unknown
11-14-2017, 03:07 PM
#4
Just for Reference:
2016 Non-Nav File: JL1T-14G381-AJ.zip
md5: d6f629d18dbfb384bd9c7e5de13113cd
SHA1: aae7501cb572fab11a8be340148a79d58c91f836
SHA256: ebd9d39a871ad1ea7b50bcd7ce06f900722b8e4988956b4f89 7da9b0ee54beb6
@Cuch, How did you resolve the GN issue in v2.2_17011?
2016 Non-Nav File: JL1T-14G381-AJ.zip
md5: d6f629d18dbfb384bd9c7e5de13113cd
SHA1: aae7501cb572fab11a8be340148a79d58c91f836
SHA256: ebd9d39a871ad1ea7b50bcd7ce06f900722b8e4988956b4f89 7da9b0ee54beb6
@Cuch, How did you resolve the GN issue in v2.2_17011?
11-14-2017, 03:08 PM
#5
If you just buy a new module that wouldn't be fun at all!
I'll throw this disclaimer out there up front that I'm a novice at linux/unix but I know enough (or how to google commands) to be dangerous.
It does use QNX6 as the main filesystem, however, my understanding is that the QNX boot/firmware/IFS partitions can be raw, and are written raw.
I believe 1 is raw despite showing FAT16, 4 is virtual, and 7 no clue. The remaining are QNX6
/dev/sdd1 * 32 65535 65504 32M 6 FAT16
/dev/sdd2 65536 2162687 2097152 1G b1 unknown
/dev/sdd3 2162688 4259839 2097152 1G b2 unknown
/dev/sdd4 4259840 15269887 11010048 5.3G 5 Extended
/dev/sdd5 4259872 13168639 8908768 4.3G b4 unknown
/dev/sdd6 13168672 15265791 2097120 1024M b5 unknown
/dev/sdd7 15265824 15269887 4064 2M b6 unknown
I'll throw this disclaimer out there up front that I'm a novice at linux/unix but I know enough (or how to google commands) to be dangerous.
It does use QNX6 as the main filesystem, however, my understanding is that the QNX boot/firmware/IFS partitions can be raw, and are written raw.
I believe 1 is raw despite showing FAT16, 4 is virtual, and 7 no clue. The remaining are QNX6
/dev/sdd1 * 32 65535 65504 32M 6 FAT16
/dev/sdd2 65536 2162687 2097152 1G b1 unknown
/dev/sdd3 2162688 4259839 2097152 1G b2 unknown
/dev/sdd4 4259840 15269887 11010048 5.3G 5 Extended
/dev/sdd5 4259872 13168639 8908768 4.3G b4 unknown
/dev/sdd6 13168672 15265791 2097120 1024M b5 unknown
/dev/sdd7 15265824 15269887 4064 2M b6 unknown
11-14-2017, 03:13 PM
#6
follow this exact procedure I wrote:
https://www.f150forum.com/f118/howto...7011-a-398097/
worked for a whole bunch of us.
https://www.f150forum.com/f118/howto...7011-a-398097/
worked for a whole bunch of us.
The following users liked this post:
TexasRebel05 (11-14-2017)
11-14-2017, 03:29 PM
#7
I'm perusing she bash scripts in the tarballs and came across this...
My tarball from Ford is HB5T-14G386-AHH.tar.gz, so something seems amiss...
# AHG Software Versions
...
2.2.16280)
validateBaseVersion HN1T-14G381-LG
installOverlay HB5T-14G386-AHE
exit 0
;;
2.2.17011)
validateBaseVersion HN1T-14G381-SA
installOverlay HB5T-14G386-AHF
exit 0
;;
# AHH Software Versions
2.1.16173)
validateBaseVersion HB5T-14G381-CA
installOverlay HB5T-14G386-AJA
exit 0
;;
2.2.16223)
validateBaseVersion HN1T-14G381-LF
installOverlay HB5T-14G386-AKA
exit 0
;;
2.3.16350)
validateBaseVersion JL1T-14G381-AD
installOverlay HB5T-14G386-ALA
exit 0
;;
esac
fi
}
# MY 17
...
# MY 18
...
exit 1
...
2.2.16280)
validateBaseVersion HN1T-14G381-LG
installOverlay HB5T-14G386-AHE
exit 0
;;
2.2.17011)
validateBaseVersion HN1T-14G381-SA
installOverlay HB5T-14G386-AHF
exit 0
;;
# AHH Software Versions
2.1.16173)
validateBaseVersion HB5T-14G381-CA
installOverlay HB5T-14G386-AJA
exit 0
;;
2.2.16223)
validateBaseVersion HN1T-14G381-LF
installOverlay HB5T-14G386-AKA
exit 0
;;
2.3.16350)
validateBaseVersion JL1T-14G381-AD
installOverlay HB5T-14G386-ALA
exit 0
;;
esac
fi
}
# MY 17
...
# MY 18
...
exit 1
Trending Topics
11-14-2017, 03:31 PM
#8
Those are the CCPU versions I was referring to. It installs a patch depending on the base version. So I don't know what happens if your base version isn't listed or is experimental/3.0
11-14-2017, 03:35 PM
#10
follow this exact procedure I wrote:
https://www.f150forum.com/f118/howto...7011-a-398097/
worked for a whole bunch of us.
https://www.f150forum.com/f118/howto...7011-a-398097/
worked for a whole bunch of us.