Sync 3.3 will not work properly on that screen, but if you source a 6.5 or 8" screen you should be able to connect that and set the unit properly. You might have to perform an APIM RESET in FORScan with the smaller screen connected.
It should, yes. All it needs is the LVDS connection.
It is possible that the issue is tied to the JB, and you may want to restore the original Ford files.
Hook up the 8" screen, see if it just comes up right. It might take a reboot.
If not perform a reset with FORScan on the APIM. Reboot.
This will likely bring up the display, but it could be the wrong aspect. Make sure the theme is set to '00" Ford default.
Upgrade to Sync 3.4, make sure it all works.
Swap the 10" screen, see if it just comes up. Might take a reboot.
If not perform a reset with FORScan on the APIM. Reboot.
Received my screen and got back my touchscreen capabilities. I did my master reset and tried upgrading to the latest version and receive the same error.
OK, that’s progress. So you are still at Sync 3.3 but the screen is correct now?
VER_ERR08 – Error is VER_SETTING_VER_INFO_ERROR. I am doing some research on this to see what specifically could be the issue. The error means that your APIM cannot save the file for the setting.
I wonder if this is a cached error. You could hold the Radio Power button and Next Track, until screen goes black. Do that 2 times in a row, then try the update again. This reboots the unit and will clear the caches.
The last file you posted indicated Sync 3.3 with the Sync 3.4 voice file. This can cause performance issues, but I don’t know if it might do this.
4U5T-14G381-AN
5U5T-14G391-CS, should be 4U5T-14G391-CJ.
The storage has an issue:
<d2p1:PartitionHealth type=“/fs/Nuance/” total=“465M” available=“3.2M”/> <d2p1:PartitionHealth type=“/fs/rwdata/” total=“1.2G” available=“0”/>
<d2p1:PartitionHealth type=“/fs/mp/” total=“496K” available=“17K”/>
<d2p1:PartitionHealth type=“/fs/mp/” total=“1.4G” available=“505M”/>
<d2p1:PartitionHealth type=“/fs/images/” total=“25G” available=“24G”/>
This is the culprit, this partition needs to be fixed/emptied. There is no space to save data for the updates, etc. If the unit was not MY20, a reformat would do it. But that is not an option here.
This partition contains “fordlogs” and “slogs”, which are supposed to be temporary, but have run the partition full. Deleting these would free up space in the partition which should fix the VER008 issue.
Thanks again F150Chief. You were correct. My rwdata partition was full and just needed to clear all logs. This fixed my issue. Appreciate what you do for the community.
I’m going to do a writeup on this for the Guides section. This seems to be a rather common issue related to settings not saving, VER08 errors, etc. This will document the issue and provide a solution to users that are comfortable using it.
That’s just a decision that the user needs to make. JB the unit and run a script, or buy a new APIM. If the user still has a warranty, they should probably pursue that choice first.
Can you add that this could also cure the issue with sync not saving setting when vehicle restarts. If rwdata is full, things like setting, FordPass and even Sirius radio issues can be fixed by cleaning these three folders
That will be covered, yes. I had not thought of the SiriusXM radio issues with logos.
Symptoms include:
General settings not saving.
SiriusXM logos not populating.
FordPass not working properly, or at all.
VER_ERR08
Cannot perform updates or downgrades.
Master Reset will not work.
etc.
