Update fail, Black screen

Hey I’m sorry to bother you, my name is Luke. I just got a 2019 f250 with sync 3. I watched videos on upgrading to newer version and I think I may have messed up. I thought it was said to plug the USB drive in the truck then turn on the truck. I did that and then my screen went black and doesn’t turn back on. I tried a soft reset with the power and right seek button but didn’t work. Then pulled the fuses for 5 min and put them back in. Pulled the battery cables for 15 min and fuses again, still nothing. Any ideas? Thank you

I did a search on here and found someone who had the same problem but was able to get his warranty at the dealer. My truck has 96000 miles on it and I don’t have any warranty to fall back on. I have reached out to Naviupgrade and he can program me a used APIM if that is what I need to do. But I want to see if someone can help me see if it can be fixed first.

Here is my log from creating the USB.

Branch: Stable
Operating System: Microsoft Windows 10 Home (2009)

Version: 3.0.20204
Region: NA
Navigation: False
Install Mode: Auto-Detect (reformat)
Install Mode Overridden: False
My20 Protection Enabled: Auto-Detect

Mode: Drive
Model: General USB Flash Disk USB Device
Size: 28.9GB
FileSystem: FAT32
Partition Type: MBR


; CyanLabs Syn3Updater Stable - reformat Mode - Sync 3.4.22110 NA

Item1 = REFORMAT TOOL - 1u5t-14g386-cb.tar.gz
Open1 = SyncMyRide\1u5t-14g386-cb.tar.gz
Options = AutoInstall

1u5t-14g386-cb.tar.gz (8.5MB)
4U5T-14G423-CC_1615429225000.TAR.GZ (564.2MB)
5U5T-14G381-EZ_1652218180000.TAR.GZ (869.8MB)
5U5T-14G391-CR_1644007976000.TAR.GZ (385.5MB)

[7/28/2022 12:46:48 PM] Selected Region: NA - Release: Sync 3.4.22110 - Map Version: Non Nav APIM
[7/28/2022 12:46:48 PM] Install Mode: Auto-Detect (reformat) Forced: False
[7/28/2022 12:46:48 PM] MY20 Protection: Auto-Detect
[7/28/2022 12:46:48 PM] Formatting USB drive
[7/28/2022 12:46:48 PM] Re-creating partition table as MBR and formatting as ExFat on selected USB drive
[7/28/2022 12:46:56 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz
[7/28/2022 12:46:56 PM] Downloading: 1u5t-14g386-cb.tar.gz
[7/28/2022 12:47:06 PM] Validating: 1u5t-14g386-cb.tar.gz
[7/28/2022 12:47:06 PM] Downloaded: 1u5t-14g386-cb.tar.gz
[7/28/2022 12:47:06 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 12:47:06 PM] Downloading: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 12:53:06 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 12:53:08 PM] Downloaded: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 12:53:08 PM] Checking Existing File: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 12:53:08 PM] Downloading: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 1:01:00 PM] Validating: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 1:01:03 PM] Downloaded: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 1:01:03 PM] Checking Existing File: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:01:03 PM] Downloading: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:05:51 PM] Validating: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:05:53 PM] Downloaded: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:05:53 PM] Preparing USB drive
[7/28/2022 1:05:53 PM] Checking Existing File: 1u5t-14g386-cb.tar.gz
[7/28/2022 1:05:53 PM] Copying: 1u5t-14g386-cb.tar.gz
[7/28/2022 1:05:53 PM] Validating: 1u5t-14g386-cb.tar.gz
[7/28/2022 1:05:54 PM] Copied: 1u5t-14g386-cb.tar.gz
[7/28/2022 1:05:54 PM] Checking Existing File: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 1:05:54 PM] Copying: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 1:06:39 PM] Validating: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 1:06:54 PM] Copied: 4U5T-14G423-CC_1615429225000.TAR.GZ
[7/28/2022 1:06:54 PM] Checking Existing File: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 1:06:54 PM] Copying: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 1:08:11 PM] Validating: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 1:08:32 PM] Copied: 5U5T-14G381-EZ_1652218180000.TAR.GZ
[7/28/2022 1:08:32 PM] Checking Existing File: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:08:32 PM] Copying: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:09:05 PM] Validating: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:09:08 PM] Copied: 5U5T-14G391-CR_1644007976000.TAR.GZ
[7/28/2022 1:09:08 PM] Generating reformat.lst
[7/28/2022 1:09:08 PM] Generating autoinstall.lst

I wasn’t sure how to link or tag this post, but this seems like the same thing that happened to me.

Please do not post many messages one after the other, there’s an edit button to add information.

About your vehicle, can you gain physical access to the unit?.

Sorry about the multiple messages, i didn’t know. I could take my dash apart to get at the radio if that’s what you mean.

1 Like

Yes, that’s exactly what I meant.
There are 2 stickers on then unit, one on the APIM and one on the screen. Please take a photo of them and post them here.

It should not matter you connected the USB before time.
What I want to check if you have a MY20 component…

Ok, it will take me a few minutes to open it up but I’ll get it asap. Do you think this problem may be able to get fixed?

Something else that may be relevant is that my phone’s bluetooth was on and was trying to connect

It depends.
As far as you are saying, the unit is unresponsive.
This should not be happened due to a USB stick being connected before time.
What I suspect is they maybe your unit has MY20 components. If so, the USB would kill the unit.

Ok, the download i did had the safety for that in it right?

Here is a pictures.

Not quite, since it’s auto detect, not enabled.
Didn’t you see a warning while creating the USB?

I saw a warning, i just didn’t understand what it was asking i guess. My truck is a 2019. I didn’t think it would have a newer radio in it.

Do i need to take the apim off of the screen to get the other picture?

Bad news Luke.

Even though your vehicle is from 2019 somehow it has a 2021 APIM.
So it’s been serviced, it’s not stock.

So the APIM is dead, you can’t reformat MY20+.
Only question is if they changed both components (APIM+Screen) or it’s only the APIM.

So what are my options to get a radio again?

Can you explain what my 20 is for me please.

Screen seems ok, it’s from early 2019.
So the culprit would be the APIM from 2021.
I think you will have to replace the APIM, and you should be good to go.
Do not get L ones, since those are from 2020.
J or K series are the newest before 2020 (2018, 2019), make sure to check the manufacture date.
Yours is a J series but this must be a replacement unit from Ford, so the original part number J does not reflect the real year, lets say.
So before buying a new one, make sure the check the sticker.

Sorry, I overlooked this question.
MY20 is Model Year 2020, basically.
This does not refer to the car itself, but to the Screen and APIM.
Starting with MY20 APIMs and Screens, Ford decided to introduce a change in their architecture (different type of memory). The tool we use (the reformat tool) is a leaked tool from Ford that enables reformating the partitions on the APIM in order to get 3.3+ builds, you can’t go from 3.0 to 3.3 or above without reformat.

The issue is that the reformat tool that’s been leaked can’t handle MY20 components.
If the APIM is MY20, it bricks it. If the Screen is My20 but the APIM is not it will “soft brick” the unit, since the reformat tool does not have the proper drivers for a MY20 screen, thus failing the upgrade. This can be solved by temporarily connecting a non-MY20 screen to complete the process. Once the process is complete, you can connect a MY20 screen again.

Thank you for explaining, I guess the dealer has the abilty to put the newer unit in because they have the software that works with it.

What needs to be done programming wise to put a different unit in? If i get one from the used market can i just install it?

Not sure if the average dealer has the proper equipment to reprogram it, depends on the dealer I would say. Some thing tells me most dealers don’t do that kind of jobs.

They are plug and play, you just replace the APIM and “that’s it”.
From the previous log you showed your car does not have NAV, so assuming you are NA based you could get a similar NA 16GB NON-NAV APIM, and it would be basically plug-and-play if it’s not a modified unit.

So depending on that, you may need to perform some changes to the asbuilt (configuration) of the unit to match your vehicle. That’s done with a proper odb2 interface and forscan, not hard to do.

Of course, if the donor vehicle is like yours, then you may not need to do anything than connecting the new unit.

Thank you again for your time. One more question, does the ford pass have anything to do with the apim?

Ford pass as the app?.
I’m not really sure, but as far as I know (and do not quote me on this one) there’s another module that handles the communication with Ford’s servers, that’s not the APIM.
I believe it’s the TCU, not the APIM.

Ok thank you, what about Android auto and Apple car play. Do I need something specific for that?

Nope, those are part of Sync3.
If you get a running 3.x system, it would be fine.