Black Screen after update from Sync 3 v3.0 to v3.3 - Ford Mustang 2018





Manufacture date on the APIM is 6/24/2020. If replaced with the screen than it is prob a 2020 model. I’ll let the experts chime in though.

Well, no manufacturing date on the screen so… But I’ll be buying probably 2018 APIM no the less, because it’s the cheapest compatible unit I found.

Edit. Bought this one. Hope it will work fine. Sill able to return it though if You tell me I can recover the previous one :stuck_out_tongue:

Thanks for the pictures, i’ll do some research after work if i remember.

Thanks, will appreciate it greatly!

Both this and that thread have JR3T-14G371-BJD

Unfortunately i don’t believe there is a fix for this, however taking pictures of the inside of the unit would help me confirm my theorys, specifically the eMMC chip.

Either way, i have added JR3T-14G371-BJD to “My20 models” for Syn3 Updater to detect this model as My20 however, it won’t stop them seeing this message and still saying “No” and then bricking their APIM, a update for Syn3 Updater would need to be released to fix that, and i have no intention of releasing a new version of Syn3 Updater at this time.

Well to tell the truth, the car wasn’t manufactured in 2020, so the alert You posted may be misleading. I would suggest adding “or You suspect the APIM unit in the vehicle might be replaced”.

Like I said, I didn’t check the unit number before the instal, so no hard feelings, but such change may help others in the similar situation. You may also add, that it is recommended to check the number online for any photos.

So one last thing before ending this thread. Like I asked before, could you tell me if replacing the APIM unit and coding it in forscan to match my as build config will be enough? If there is some procedure to do it, I would be very grateful if You could share it with me and others that may read this thread.

If I understand correctly, with the screen I have, I won’t be able to use the installer even withe the new 2018 APIM?

At the time of creation of that error message, we were not aware of this unit so of course this message is misleading

But in all seriousness, no warranty is provided you do this at your own risk and things like this will happen.

For what it’s worth it does say in the documentation about retrofits, and it also says if unsure click YES

I have updated the documentation to also mention replacements now

Yes

I don’t believe the screen is the issue in this specific instance, but as previously mentioned we do not know, this is like the 3rd instance of this out of thousands, and i literally mean thousands of upgrades, we get about 800 a month if not more according to my logs

Replacing the unit and coding it like the old one is a simple procedure that I can help you with. First thing is to back up the old APIM asbuilt settings, firmware versions, and obtain the factory asbuilt file, which you have here.
1FA6P8TH9J5114739.ab (28.2 KB)
When the replacement unit arrives, install it into the vehicle and back up the asbuilt settings before you do anything else. Also, look at the firmware versions and post those. Once we have that info, we can program the replacement unit to work with your vehicle properly.

One thing I would like to point out, that this is absolutely a replacement part that was ordered by a service department to replace the original unit. This is evident by the service tag placed on the unit backside. The order number is shown at the top and ordered for your VIN.

apim

The screen is NOT MY20, this looks original.

screen

So, I would say the issue here is that the eMMC is the NEW version. You would need to access the eMMC directly to maybe rescue the unit if this is the case. This requires expertise, the proper hardware and software, and a bit of skill (luck).

Post back here or PM me when you get the replacement unit…

1 Like

I was planning downloading the factory as build directly via forscan, because i have a picture of my original as build settings and I can see if it checks up. But thank You for the file.

As the firmware version of the Sync 3 goes, I will update you on this. I guess it will be some build of v3.0 and I will have European language pack, because my new unit was produced in Hungary. So I guess, the purpose of the failed update will be archived non the less. I think I won’t be able to update via official ford website though, not to upload the US firmware again.

I believe it to be the case as well. When it comes to programming the eMMC, I’m aware of some Chinese tools (like so: https://pl.aliexpress.com/item/1005001484737834.html?_randl_currency=PLN&_randl_shipto=PL&src=google&src=google&albch=shopping&acnt=708-803-3821&slnk=&plac=&mtctp=&albbt=Google_7_shopping&albagn=888888&isSmbAutoCall=false&needSmbHouyi=false&albcp=9594049142&albag=100017018638&trgt=542650620136&crea=pl1005001484737834&netw=u&device=c&albpg=542650620136&albpd=pl1005001484737834&gclid=Cj0KCQiA8vSOBhCkARIsAGdp6RT0U5rMfoaUoWK7mS-kTqnxf_AfmGWRZiVHazTQ4tifA4pG_899W1gaAtAAEALw_wcB&gclsrc=aw.ds&aff_fcid=2dd5cf56a792455ab482849415cea73c-1641932759300-03455-UneMJZVf&aff_fsk=UneMJZVf&aff_platform=aaf&sk=UneMJZVf&aff_trace_key=2dd5cf56a792455ab482849415cea73c-1641932759300-03455-UneMJZVf&terminal_id=1222503e851e44549e2fc3b4a366b95f) that would let me access the eMMC memory directly, but I think I will pass on this :wink:

I’m just curious why the module was replaced and if I will have the similar problems with 2018 version I ordered, but seeing how much people have stable 2018 units with zero problems, I hope for the best.

If the one you ordered was manufactured in 2018 and has the older eMMC chip, you should be completely fine using the reformat.

Well, I can’t be sure if the screen isn’t from 2020, so I probably won’t risk bricking the unit for the second time

I would pass also. BTW - don’t buy that one, issues with newer MY20+ units.

The issues with the later Sync units are not all that common but it does happen. The G and H series are much more prone to issues, the J series are pretty good. As was mentioned above, we have only seen about 3 of these out of the hundreds that have used the software.

Should be fine, I agree.

I will have a 2020 unit 64 gb EU maps tomorrow. The 2018 unit I ordered had a different antena/gps connector, so I had to return it.

I’ll post here tomorrow if everything is working. Will uploading my original as build file have an impact on GPS functionality? I guess, i’ll have to change the country code from original as build 5553 (USA) to 504C (PL). Anything else?

Should be fine. Just don’t reformat it…! :grinning:

OK! Will keep in mind :smiley:

1 Like

It turns out, the APIM unit i bought has Sync3 v3.4 despite being originally Sync3 v3.2

Here is the photo of the unit:

And here photo ot the “About SYNC” screen:

Now, after installing the unit, I made a factory reset. Then I uploaded the factory as build data to the unit. Uploading the factory as build made the navigation options disappear, although, the map files are still in the about screen:

To have the access to the maps, I guess I would need European Mustang (preferably Polish) from 2020 as build data, to make it work. @F150Chief is it possible for you to download such file as you did with my car?

**Edit: I was able to find where I can download the as build data. I found VIN numbers of some 2020 Polish mustangs, so I will be digging into it and chcecking if it will make things work: **
https://www.motorcraftservice.com/AsBuilt

Here is the as build data that was originally on the unit I bought:

What is more, the 3.4 version of Sync is a little laggy comparing to the experience I had with v3.0. I guess, there isn’t a way I can go back to the 3.2 or 3.3 version?

You can downgrade to a 3.3 build if you like, Syn3updater can create the USB for you, keeping maps and all.

Just make sure to not reformat the unit.

You are the only one who will say this, SYNC 3.4 is noticeably faster,

1 Like

It also struck me as very strange. Perhaps these are my prejudices against the appearance of the new interface, but before that I went straight through the various options, and now it sometimes takes a second…