Ahh I know what the issue is. I purposely created a new profile and left all the values (sync version & map) default and didn’t touch it. I thought doing that would have been better as it would be a clean start. I didn’t realize the integrator needed those values as well. Obviously for the actual upgrade I changed them. Oh well sorry about that. I’m going to re-try it tomorrow. Thanks!
I got the log not problems this time haha. I only have 6gb free space. So I’m guessing thats the issue. If I were to separate the updates (apim, then maps) do you think that would make any difference? Or is my only option to remove gracenotes?
Version 5U5T-14G381-ED
APIM Model: 5U5T-14G371-CMD
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 6.3G
2/23/2022 11:55:09 AM +00:00
Partition Type = Free / Total
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 13M / 1.4G
/fs/sd/MAP/ = 12M / 1.3G
/fs/sd/MAP/ = 3.0M / 922M
/fs/sd/MAP/ = 9.3M / 1.3G
/fs/sd/MAP/ = 16M / 1.7G
/fs/sd/MAP/ = 17M / 1.7G
/fs/sd/MAP/ = 13M / 2.0G
/fs/Nuance/ = 25M / 2.6G
/fs/Nuance/ = 3.1M / 465M
/fs/Nuance/grace = 57M / 1.0G
/fs/rwdata/ = 940M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 142M / 1.4G
/fs/images/ = 6.3G / 25G
Installed Packages
5U5T-14G391-CL
4U5T-14G423-CA
APIM AsBuilt
DE00: 2280001340020008008A
DE01: 555300000000000028000000
DE02: 0000000000
DE03: 01000000000000
DE04: 000000000000
DE05: 00
DE06: 0A000000000000000000000000000000
So just to confirm forall that you indeed have a MY20+ APIM, part number 5U5T-14G371-CMD.
You have plenty of storage space to process the updates, just do not reformat. As I posted above:
1 Like
I agree with the previous message, I was going to point out exactly that. It’s not a space issue, you have “plenty”.
Just follow the quoted tutorial to the letter and you should be good. But be aware it’s a lengthy process.
Thanks everyone, Im going to try separating the map update from the sync update. Its just odd why I got the MEM_ERR03 error last time if I had enough storage space to begin with. I updated a f150 from ver 2.2 with maps to the latest 3.4 & maps 2020 without any issue last week. Not sure why this one is giving me trouble. Ill post back my results later today. Thanks!
You could double check the order, which may be important.
As F150chief said, check there’s a specific order to update maps.
From that version to 3.4 it’s a reformat, so it’s quite an easy and fast process.
It’s always recommended to reformat, but since you can’t for having a MY20 unit, AUTOINSTALL is the only option. It’s slower, more time consuming and pickier.
But it should also work.
Good luck!
1 Like
So far so good! I updated to 3.4.21265. Working on the maps next
1 Like
Make sure to leave the USB in, do not remove it until you see the screen to specifically do so.
It will go thru about 3 reboots. Also, do not key cycle the ignition, just let the program do the reboots.
You just sit and watch for about 50 minutes. Open and close the door a few times to keep the truck awake.
Maps update was a success! I compared my integrator log to the tutorial log and both seem to match up pretty well. Only minor differences in size near the end. If you spot anything out of the ordinary please let me know. Everything seems to be functioning 100%. Thanks so much!
VIN:
Version 5U5T-14G381-EU
APIM Model: 5U5T-14G371-CMD
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 4.3G
2/23/2022 7:52:13 PM +00:00
Partition Type = Free / Total
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 13M / 1.4G
/fs/sd/MAP/ = 10M / 1.4G
/fs/sd/MAP/ = 2.8M / 937M
/fs/sd/MAP/ = 8.5M / 1.3G
/fs/sd/MAP/ = 14M / 1.7G
/fs/sd/MAP/ = 17M / 1.7G
/fs/sd/MAP/ = 7.2M / 1.4G
/fs/Nuance/ = 16M / 1.6G
/fs/Nuance/ = 10M / 1.1G
/fs/Nuance/ = 25M / 2.6G
/fs/Nuance/ = 3.2M / 465M
/fs/Nuance/grace = 5.8M / 775M
/fs/rwdata/ = 939M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 132M / 1.4G
/fs/images/ = 4.3G / 25G
Installed Packages
4U5T-14G423-CC
4U5T-14G421-CAD
4U5T-14G421-CBD
4U5T-14G421-CCD
4U5T-14G421-CDD
4U5T-14G421-CED
4U5T-14G421-CFD
4U5T-14G421-CGD
4U5T-14G421-CHD
4U5T-14G421-CJD
4U5T-14G422-CAJ
5U5T-14G391-CP
4U5T-14G424-CD
4U5T-14G422-CBJ
4U5T-14G422-CCJ
APIM AsBuilt
DE00: 2280001340020008008A
DE01: 555300000000000028000000
DE02: 0000000000
DE03: 01000000000000
DE04: 000000000000
DE05: 00
DE06: 0A000000000000000000000000000000
This is the correct free space for a NA Sync 3.4 installation with maps.
However, your APIM asbuilt cannot be correct for a 2015 F350 Sync 3 retrofit. Do you have FORScan?
Yes I do, I have forscan and IDS. I just completed the retrofit 2 weeks ago. Almost everything is working fine. I noticed there are some tweaks that still need to be done though. Such as the apim screen staying on only for 2020+ apims. I think I found the tweak for that. I dont have the link with me at the moment. If you see anything else please let me know. Im sure there are some other odd issues I just havent had time to go over all the features yet. I copied mostly from a 2017 F350 Lariat with similar options. Mine is a 2015 King Ranch. I still had to alter some settings. Thanks again!
Using the 2017 F-Series asbuilt will not be completely correct as your vehicle is CGEA 1.2, not CGEA 1.3, so there are fundamental differences in the subsystems like HVAC, etc. This is the reason the Sync screen may not shut down completely. the illumination gateway settings should fix this.
Most of the Sync 2 settings will be correct. You are missing the vehicle specific information in the asbuilt needed for the navigation and other functions. Also, most of the 7D0-08-xx and 7D0-09-xx will not apply to your vehicle as the hardware will not support the features.
If you would like help with the settings, PM me your VIN.
Thanks! I found that out the hard way last week when my hvac and steering controls didnt work. I believe I already changed everything to CGEA 1.2. I will send you a pm with the VIN. Im sure there are other things I missed. I tried reading up a lot but absolutely no expert haha. I appreciate all the help!
Oh and the line I was referring to yesterday that seems to fix the screen staying on is 7D0-06-01-8x5F. Where X is I had 0. It seems by changing to 1 it should fix the issue for 2020+ apims
This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.