I have the adapter I have a DTC in the log page. Screenshot attached.
Below are what I hope you need
EDIT: I forgot to blur one spot for VINs. Oh well. Looking at https://www.motorcraftservice.com/AsBuilt/Details the ASBUILT information matches.
EDIT 2: I just noticed there is a lower half of the ASBUILT section. So here it is:
This is a 2020+ L series APIM. If you do manage to get this thing to work do not ever format it.
OK, I believe you. The Syn3.Installer states its a āMY20ā
I got my Fingers crossed Sandman will have a good solution for you that brings it back.
Me to! I know I havenāt been the best customer for him. I am a confusion grenade.
Hey, thank you for the data.
Yeah, you have a lot of DTCs, but none of the appear to be related to the screen at the moment. You should clear them and wait to see if they return.
About the ASBUILT for the APIM, Iām not seeing anything strange at the moment, boot screen and theme are set correctly. You could try changing this one:
to 01 and then 00 againā¦ But I would not say your current value is wrongā¦
Also, the last usb you tried was for installing 3.4.21020, so I think itās safe to assume the unit is running some kind of 3.4 buildā¦
Another thing you could try is, with syn3updater and MY20 protection active, creating an āupgradeā USB for just installing 3.3.19xxx. Just the APPS package, nothing else is required at the moment. It should take about 10 minutes to install (if so), then it should reboot.
And since we are talking about āinstalling thingsā, have you tried running an interrogator log as the unit is now?.
Sandman,
I have cleared them and the APIM one intermittently will come up again.
I was able to get all splash screens to run properly on the unit but afterwards I have a black screen.
You want an early build installed on to the car?
Yes I have tried the integrator tool and will load the data in a moment.
Ok, but splash screen we know it worksā¦ the visual design is the UI Sync will actually show after booting up (hence, past the boot screen).
So the unit is responding to autoinstall.lst files, which is goodā¦ Yes, share the XML if you have it, redact the VIN from the fileās title and content if you care about it.
Yes, my favorite is the Bronco one.
At this point no I donāt care, since I failed to cover it previously.
Here is the XML
Sync_V08P005A_1FMJK1MTXMEA65211.xml (10.9 KB)
Currently making a āupgrade usbā for apps only for 3.3.19052
EDIT:
I changed the value to ā01ā and no change, still a black screen after the logo.
I attempted to āupgradeā to 3.3. and have let the car sit for about 10 minutes until my USB data flash turned solid. No reboot of the system. I created an interrogator and here are the results below:
Sync_V08P005A_1FMJK1MTXMEA65211.xml (11.0 KB)
Looks like the āupgradeā didnāt take.
After two attempts to get this to upgrade to 3.3.19052 it will just not take.
Sandman!
Check it out.
This is using the different USB and trying to get it to do the 3.3.19052. But the one screenshot says its the newest
EDIT:
Here is the XML after this started working:
Sync_V08P005A_1FMJK1MTXMEA65211.xml (11.1 KB)
Ok, Iām not sure what happened, but hey, if itās working now I would not mess with it a lot moreā¦
I mean, normally I would recommend performing a master reset, but if you do not see any bug or issue preset at the moment, just let it beā¦
Thereās something thatās not quite right though:
/fs/rwdata/ = 531M / 1.2G
That usually indicates something is not working as expected and may become an issue in the near futureā¦ a master reset should clear thatā¦ or try running the official rwdata partition cleaner on itā¦ Are you a heavy car play user?.
Very heavy CarPlay. Thatās all we use.
Try to create just an RW cleaner USB and see if that helps
did it
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
