Intermittent Black Screen

I upgraded to 3.4 22251 back in Jan no issues a couple of weeks later I upgrade the firmware to the ACM, the APIM was up to current firmware. Then randomly I get a black screen, no radio no rear camera nothing, the volume FF forward reset has only worked 3 times usually nothing happens. I can go out start the truck everything is fine, I shut the truck off to get fuel go to start it and it’s a black screen. It never goes black while the truck is running, only when I go to start it and it has no rhyme nor reason, just the roll of the dice as if it feels like working or not. the APIM and ACM are not original to the truck which is a 2017 F350 diesel the APIM is a JS7T-14G371-JED, ACM is HC3T-19C107-CK.
Any ideas why?
Thanks

Can you create and run an interrogator log against the unit and post back the results?.

VIN: 1FT8W3BT7HEB
Version NU5T-14G381-AB
APIM Model: JS7T-14G371-JED
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 4.3G
5/20/2023 9:03:16 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/ = 730M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 84M / 1.4G
/fs/images/ = 4.3G / 25G

Installed Packages
4U5T-14G423-CC
4U5T-14G421-CJD
4U5T-14G421-CHD
4U5T-14G421-CGD
4U5T-14G421-CFD
4U5T-14G421-CED
4U5T-14G421-CDD
4U5T-14G421-CCD
4U5T-14G421-CBD
4U5T-14G421-CAD
5U5T-14G391-CS
4U5T-14G422-CCH
4U5T-14G422-CBH
4U5T-14G422-CAH

APIM AsBuilt
DE00: 222A020724028942048A
DE01: 55530103C002018700000405
DE02: 0100010300
DE03: 01003201100000
DE04: 1AAE1A403E80
DE05: 80
DE06: 34003A0000000003BE00005656AA00CF

Thanks.

So you do not have the issue of this partition being full on 22251.
I asked for that information since you are the 2nd user that’s reporting “black screen” issues while using that build, which I find odd.

Other than recommending reformatting the unit (since it seems it’s not MY20/+ hardware), I’m not sure how to proceed. Besides, I would recommend not staying on 22251 either way, so this could be a good idea to do so.

You mentioned reprograming the ACM just before the issue started, so of course this seems to be related. Have you tried a master reset when the screen come back to life?. Does the unit have any DTC?.

1 Like

I’ll have to check for any DTC, there’s none that I remember and I have done a reset thru FORScan for the APIM and the ACM as well as disconnect both batteries for 10 min. So should I reformat back to 22200, I could also change my ACM as I have 2 others they are all HC3T-19C107- one A, B, and the C installed now I like HD radio, lol

Yes, you could go back to 22200 or even try the new 23088 from which we didn’t receive negative feedback. But yeah, whichever version you choose, I would not stay on 22251. Even if it may not be related to your issue, it’s best to stay away from it since we have not yet determined if the rwdata partition becoming full is related to the build, to vehicle’s specifics, or both.

I’ll do the 23088 tomorrow and I’ll check for DTC on the APIM ACM AND FCIM, I will reply if I have any DTC and of course if I continue to get black screens, I want to actually change my APIM and ACM to a early 2020 or late 2019 before HS4 and the new harness to get all the metadata from Sirius and the extended channels.
Thanks for you help MUCH appreciated

Just a note to add, I also noticed that after the build it takes much longer for the screen to load the maps and logos, it is slower than before on 22200. I’ll make note if it becomes faster after 23088

Try 3.4.21265, which is the most stable version of the last few revisions. Also look in FORScan and show the DTC’s if any after the version change and master reset.

Be aware that the 2017 F350 is the older CGEA 1.2 platform, and that the newer APIM/ACM combo is really meant for the CGEA 1.3 platform. There will be additional wiring and programming to accomplish this upgrade. I am not sure if it will work on a CGEA 1.2 vehicle.

@bill32399 can you add your experience here with Explorers?

@Killer_Volt HS4 has nothing to do with anything you mentioned so far. HS4 was a new network that put the TCU on its own network with the APIM and GWM for Security purposes.

If you go to a 2020 APIM you can’t do any of what you mentioned so I am not sure why that was even brought up. Also, you don’t need a new Harness to get Sirius 360L all you need to do is add 2 wires from the APIM to the ACM.

@bill32399 C240A pin 4 & 5 to C2383A pins 27 & 28 are those the two wires you’re talking about. Are those the ones that will get me 360L?

Hi F150 Chief,
As far as I can see everything on FORScan for my truck is CGEA 1.3 My original Sync was the 4" screen and the first place I saw the CGEA 1.3 was in the SWCM because the first ACM I changed out I had programed it all wrong and my phone and control buttons on the SW wouldn’t work. The APIM and ACM I have in the truck right now worked fine no issues, till I updated the firmware on the ACM I was going to do the APIM but it had the latest firmware.

@SaNdMaN
I updated to 23088 build, had an issue getting the screen to come back on after updating, three tries and on the third reset with FORScan it came on and said finishing update, I shut the truck off and 5 min later started it again the screen came to life and said again update complete, shut it off and have started it 3 times since and it comes on every time so far. I ran the interrogator again. Also it seems a little faster loading, one more thing I noticed when I get a black screen, when I turn on the key my compass goes spinning N NE S N NE N NE like it can make up its mind.
VIN: 1FT8W3BT7HEB

Version NU5T-14G381-AC
APIM Model: JS7T-14G371-JED
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 4.3G
5/21/2023 6:59:53 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/ = 720M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 84M / 1.4G
/fs/images/ = 4.3G / 25G

Installed Packages
4U5T-14G423-CC
4U5T-14G421-CJD
4U5T-14G421-CHD
4U5T-14G421-CGD
4U5T-14G421-CFD
4U5T-14G421-CED
4U5T-14G421-CDD
4U5T-14G421-CCD
4U5T-14G421-CBD
4U5T-14G421-CAD
5U5T-14G391-CS
4U5T-14G422-CCH
4U5T-14G422-CBH
4U5T-14G422-CAH

APIM AsBuilt
DE00: 222A020724028942048A
DE01: 55530103C002018700000405
DE02: 0100010300
DE03: 01003201100000
DE04: 1AAE1A403E80
DE05: 80
DE06: 34003A0000000003BE00005656AA00CF

and NO DTC

Was the upgrade performed via reformat?
Make sure to perform a master reset.

I did the module reset on FORScan, I will do the master reset from the settings. I’ll post the results and how the Sync is working.
Thanks

I’m not sure if the upgrade was via reformat. I still have the intermittent issue, tho it loads a lot faster, and today on one of its black screen episodes, I shut the truck off but remained inside talking on my phone and about 5 min after I shut the truck off the screen came to life and booted up and connected to my phone (I had done the master reset and reprogrammed my phone this morning) it has never done that before and the power & FF button don’t work to reset either.
I am going to downgrade to 3.4.21265 with reformat and I will master reset as soon as its done. The interrogator log I posted last, the only thing I’ve done is master reset. I will also run interrogator again after I downgrade and master reset so I have it.

Thank you for the update.
Your case is quite strange.
Syn3updater saves all the logs in a folder, maybe you should check there to see which installation method it was used last time. If you installed maps, almost certainly it was a reformat.
I’m starting to think your issue is hardware based:

  • the APIM is not well
  • there’s a cable not seated correctly
  • some weird and unrelated electrical issue that’s affecting the APIM’s power source

But, I’m fishing…

I’ll keep trying and I’ll check the connections as I am a Master Electrician over 40 yrs. I will check the last upgrade to see if it was reformat I am going to downgrade today/tonight when I get the Sync to boot up. If I have issues yet again I will disassemble and check all connections and I do have a spare APIM but it is a GB5T-14G371-FF not the one I want to use.
I will keep posting! Thanks :grinning:

Just checked is was not a reformat so there’s hope

Update: Downgraded to 21265 black screen when it completed, went for a ride and just kept pressing power and FF somewhere around 20 tries it rebooted and came to life, checked the about Sync and it had the build 21265 (btw have not updated maps ever) everything looked good, did a master reset and went black and stayed black even tho I reset it at least 50 times as I drove around, I did notice that my USB ports are dark. When I hit power and FF about 10 seconds they light up and stay lit for about a min or so then go out, and my compass would work correctly sometimes and then just so spastic on the instrument cluster (upgraded that too). Tomorrow is another day and its gonna be demo day lol nah but I will disassemble all components look for the obvious and check the upgrade harness that came with the kit 4"to 8", I’ll check the pins and continuity, make sure nothing got bent or broke when I installed it originally, and of course I will post my findings.

So far today Sync has worked like its suppose to no issues, I will take it apart this weekend and check all connections and harness just to rule them out or see if there is a problem. I may add the 2 wires between the APIM and ACM as bill32399 talked about I’m guessing he is referring to the Satellite Digital Radio Data Link (+) (-) and see if I get Sirius 360L.

Hey there, thank you for the updates. So changing builds and even reformatting the unit did not produce any change. So this does not seem related to software.
We will wait for your findings.

FYI after the last master reset that took a couple of tries when I down graded to 21265 3 days ago it has not gone black and works like a charm and it loads much faster. I am still going to disassemble and check all connection this weekend as well as add the 2 wires from APIM TO ACM. As it stands now I’d say this is a fix, of course any new information I will post here.
Thanks SaNdMaN @F150Chief, @bill32399 Thanks for you help and knowledge I appreciate it