Suggestions on Next Step after Black Screen

Like a few others I ran into issues recently where setting were not saving every time I started my truck. Screen would change from Dark to Auto and I would need to confirm Auto Updates settings every time I started Sync 3. I did some reach search and since I had gotten a new phone recently I tried doing a Master Reset. That seemed to hang so I did a Soft Reset before trying a Master Reset again. The Master Reset Started but never finished and now I just get a Black Screen. I didn’t even think it could have anything to do with the software I was running I just assumed it was my APIM going bad. Now after doing some research it seems like maybe my data dir was full? I’m looking for suggesting on next steps. Should I try and downgrade back to 3.3 before and see if that restores the screen? Before trying to move to the latest 3.4. It feels like the APIM is still working it just in bad state.

My plan was to build a 3.3.19052 and insert the USB stick and start a timer and hope it gets past the first part where you need to turn off the truck open the door and let it start the upgrade. Will that work? I read someone else had this issue and it worked for them. Will it work for me? My Asbuild seems weird that it’s blank. I was thinking maybe that because the master reset or maybe something else.

I installed 3.4.21194 over 2 years ago and it’s been great until the setting were not saving.


SYNC Region: NA

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 3.4.21194

New SYNC Version: 3.3.19052

Do you have a error message, if so what is it?
No error as of yet except the black screen after doing a master reset.

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: It was so long ago I don’t know going to use the latest

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

Version 5U5T-14G381-ET
APIM Model: Unknown
APIM Type: Navigation 
APIM Size: 32GB 
APIM Free Space: 4.3G 
12/10/2023 7:32:55 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/ = 822M / 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-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-CP
4U5T-14G422-CCH
4U5T-14G422-CBH
4U5T-14G422-CAH
4U5T-14G423-CC


APIM AsBuilt
DE00: BLANK
DE01: BLANK
DE02: BLANK
DE03: BLANK
DE04: BLANK
DE05: BLANK
DE06: BLANK

I had a similar issue with my system going dark after a Master Reset and this is what I did to fix it:

Ford Logo then backlit black screen after Master Reset

I hope that this information is at least somewhat helpful!

I fixed the black screen issue by downgrading to 3.3 but the quip is still full and I tried to use the RWdata cleaner and it doesn’t work. What is also weird is the APIM AsBuilt is still Blank. Now that I’m at 3.3 I’m going to create a reformat to 3.4 latest. Wish me luck. Hope the reformat will clear out the bad things and it will fix my

/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M

APIM AsBuilt
DE00: BLANK
DE01: BLANK
DE02: BLANK
DE03: BLANK
DE04: BLANK
DE05: BLANK
DE06: BLANK

I guess before I move forward will the reformat option clear the Rwdata?

Do not post consecutive messages, use the edit button instead.

Your rwdata parition is just fine:

So that’s not an issue.

Do you currently have any issues?.
I would upgrade to the latest 3.4 version.

Yes, still have some issues. The prompts keep coming up asking me if I want to auto update and other settings want me to confirm on each startup. I am building an 3.4.latest right now and since I"m at 3.3 I have the reformat option. I will give that a try and report.

PS I will edit my messages going forward. Sorry about that.

About the reformat, are you 100% sure it’s not MY20?.
I’m asking because of this:

The interrogator log can’t see what APIM the vehicle has.

If you are not 100% sure, this is what I would do: I would autoinstall the latest 3.4 and perform a master reset. Do not update maps, just Sync3. And then I would re-run the interrogator log to see if any more information is displayed.

I was able to update to 3.4 latest. My truck is a 2019 and things seem to be working and was able to do a master reset after I updated. I wonder if the master reset fixed things or the software did. Remember my Master Reset failed and caused my screen to go black. Either way I’m happy it’s fixed if you want me to send you anything I can for debugging.

I just restarted the truck and looks like the settings are holding now. I also ran a interrogator log and I can see the AsBuilt now.

Version 4U5T-14G381-AN
APIM Model: JR3T-14G371-CHA
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 3.9G
12/16/2023 12:38:17 PM +00:00

Partition Type = Free / Total
/fs/sd/MAP/ = 12M / 1.5G
/fs/sd/MAP/ = 12M / 1.5G
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 10M / 1.4G
/fs/sd/MAP/ = 2.9M / 951M
/fs/sd/MAP/ = 8.6M / 1.3G
/fs/sd/MAP/ = 14M / 1.8G
/fs/sd/MAP/ = 17M / 1.7G
/fs/sd/MAP/ = 6.7M / 1.4G
/fs/Nuance/ = 15M / 1.6G
/fs/Nuance/ = 10M / 1.1G
/fs/Nuance/ = 24M / 2.5G
/fs/Nuance/ = 23M / 480M
/fs/Nuance/grace = 57M / 1.0G
/fs/rwdata/ = 1.0G / 1.2G
/fs/mp/ = 505M / 1.4G
/fs/images/ = 3.9G / 25G

Installed Packages
4U5T-14G421-CAE
4U5T-14G421-CHE
4U5T-14G421-CGE
4U5T-14G421-CJE
4U5T-14G421-CFE
4U5T-14G421-CEE
4U5T-14G421-CDE
4U5T-14G421-CCE
4U5T-14G421-CBE
4U5T-14G391-CJ
4U5T-14G422-CCK
4U5T-14G422-CBK
4U5T-14G422-CAK
4U5T-14G423-CA

APIM AsBuilt
DE00: AA2A050326028940048A
DE01: 55530103F402009F00004005
DE02: 0100010300
DE03: 00001000100001
DE04: 1AAE1A403E80
DE05: 80
DE06: 34003A0000000003BE00005656AC00CF

I also sent over some $$ to help support becuase without you continuing to support us I would have a broken system. Thanks you for everything you do.

1 Like

The log you sent is saying the unit is running 3.3.19052, not 3.4.
Do you have a more current log?.

Now this is interesting:

Now you know what APIM the car has and the interrogator is full of data, as it should.

You case has been a bit odd since it’s not usual for users to have those kind of issues, but coincidently there was another use that also had a black screen “without reason” and was fixed by installing a different Sync3 version, which is really odd. One common factor is that both had “not so recent” builds, but nothing that others had to face either, so it’s really hard to say what’s wrong here…

But this is even more interesting:

Your rwdata, which was not full before, is ok now as well. Remember that before you had 822 MB of free space in that partition, which is A LOT of space… issues like settings not being saved and such things were seen on units with 0MB left, so a full partition condition, which was not your case.

Anyways, good thing you could recover the unit. Keep an eye on it from now on, since there’s a possibility that the reformat could actually has “fixed” (or hidden) an underlying eMMC storage issue… I’m only saying this because due to the unusual aspect of your case…

But, that’s something for the future… for the time being, enjoy the unit and that’s it.

Take care and happy holidays.

That was my fault. I was pointing at the wrong log file. I was wondering why Sync Updater was telling me the system did match what i told it. Here is the recent log file.

Version NU5T-14G381-AD
APIM Model: JR3T-14G371-CHA
APIM Type: Navigation
APIM Size: 32GB
APIM Free Space: 4.2G
12/16/2023 3:16:55 PM +00:00

Partition Type = Free / Total
/fs/sd/MAP/ = 12M / 1.5G
/fs/sd/MAP/ = 12M / 1.5G
/fs/sd/MAP/ = 12M / 1.4G
/fs/sd/MAP/ = 10M / 1.4G
/fs/sd/MAP/ = 2.9M / 951M
/fs/sd/MAP/ = 8.6M / 1.3G
/fs/sd/MAP/ = 14M / 1.8G
/fs/sd/MAP/ = 17M / 1.7G
/fs/sd/MAP/ = 6.7M / 1.4G
/fs/Nuance/ = 15M / 1.6G
/fs/Nuance/ = 10M / 1.1G
/fs/Nuance/ = 24M / 2.5G
/fs/Nuance/ = 3.2M / 465M
/fs/Nuance/grace = 5.8M / 775M
/fs/rwdata/ = 981M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 84M / 1.4G
/fs/images/ = 4.2G / 25G

Installed Packages
4U5T-14G421-CAE
4U5T-14G421-CHE
4U5T-14G421-CGE
4U5T-14G421-CJE
4U5T-14G421-CFE
4U5T-14G421-CEE
4U5T-14G421-CDE
4U5T-14G421-CCE
4U5T-14G421-CBE
5U5T-14G391-CS
4U5T-14G422-CCK
4U5T-14G422-CBK
4U5T-14G422-CAK
4U5T-14G423-CC

APIM AsBuilt
DE00: AA2A050326028940048A
DE01: 55530103F402009F00004005
DE02: 0100010300
DE03: 00001000100001
DE04: 1AAE1A403E80
DE05: 80
DE06: 34003A0000000003BE00005656AC00CF

Happy Holidays to you as well. Hope this thread helps others with the same issue. Happy to answer any questions.

Steps I took After issue of Black Screen

Did a lot of reading to get to this step to feel confident I was doing the right thing

Step 1 Downgraded to 3.3 with Maps upgrade (This fixed black Screen)
Step 2 Upgraded to 3.4.Latest with Map Upgrade (Format Triggered)
Step 3 Ran Logs and confirmed everything was working. (Did a happy dance and donated)

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.