Just FYI, If you need to flash firmware you must use a USB adapter…The BT vLinker will work for the asbuilt data.
Make sure you load the drivers for the pc…the procedure is similar to the USB setup.
Then read these tutorials…
FORScan Tutorial Links - Ford / Information - CyanLabs Official Community
GA8T-14G370-CL is an old but original unit for a 2016. It is NAV 32GB. The screen is also original to that vintage APIM.
When you upgraded to Sync 2.2.16280, you used the Ford script autoinstall file. Did it look like this?
[SYNCGen3.0_ALL]
Item1 = HB5T-14G386-TCB
Open1 = SyncMyRide\HB5T-14G386-TCB.tar.gz
Item2 = HN1T-14G391-CC
Open2 = SyncMyRide\HN1T-14G391-CC.tar.gz
Item3 = HN1T-14G423-CA
Open3 = SyncMyRide\HN1T-14G423-CA.tar.gz
Item4 = HN1T-14G381-LG
Open4 = SyncMyRide\HN1T-14G381-LG.tar.gz
Item5 = GB5T-14G386-AA
Open5 = SyncMyRide\GB5T-14G386-AA.tar.gz
Options = Delay’AutoInstall
I’m not 100% sure, but I believe this is the file I used https://onedrive.live.com/?authkey=!AHxq3PdupRiOQxU&cid=6301F3780584C35D&id=6301F3780584C35D!281201&parId=6301F3780584C35D!274323&action=defaultclick
After a lot of searching, I found some people saying that I needed to update to 2.2 before I could update to the latest firmware. So I found one of the help forums with a link to the 2.2 update and downloaded it from there.
Question: is the unit operative besides the black screen?.
Do you hear any audio?
The audio is working yes. The USB ports are lighting up, and the screen is turned on but it’s a black screen (the backlight is obviously working on the screen)
OK, that is similar enough and removes the overlay. Although, if you just use the reformat tool it does the same thing but will upgrade to Sync 3.4. Try updating to Sync 3.0.20204 to see if there is just an issue with the Sync 2.2.16280 installation. This is obviously an issue with the screen drivers.
The early Gxxx models are very temperamental.
Um… so the unit is operative with a black screen…
Do it seems it never got into the reformat phase…
Okay so just to clarify; I’m going to re-install the Syn3Updater files to a USB drive, using Sync 2.216280 as my current version, and 3.0.20204 as the target version, correct?
Also, I’m going to return this vlinker OBD scanner as it’s clearly not going to be any use to me to solve this issue. Is there any information that I should pull from the car before I return it?
No, you can’t update to 3.0 with the Syn3 Updater. Use Sync 2.2.16280 as the current version and Sync 3.4.21265 as the version to upgrade to. You do not need to include maps if you want, as we are just trying to get the unit fixed.
Also, do not just copy the files to the drive manually, use the Syn3 Updater app.
The adapter will not help with this issue since it is BT. Just return it and get the USB version if you want.
Okay I’ll return it and download that again.
Just to clarify, the system was working fine for a week AFTER it was updated to 2.2.16280.
It wasn’t until I tried updating to the newest version using Syn3 Updater that the screen turned black.
I should also mention that it turned black as SOON as I turned on the car with the USB inserted and the syn3 updater newest version files loaded onto the USB
UPDATE: I tried doing these steps as listed. I left my car on for 45 minutes with the USB (loaded with 3.4.21265 from the Syn3 Updater app) inserted. Nothing changed and the screen is still black.
It’s almost like the display cable is not plugged in or damaged. If not that than an Asbuilt setting. Its still working in the background right?
You could use the adapter to read the APIM asbuilt and post it here. Take a pic or post the asbuilt file.
I don’t think it’s anything to do with any cables. The screen blacked out the moment I turned the car on with the USB inserted and loaded with the syn3 updater files. Everything was working completely fine prior to that (other than being unable to update using conventional methods)
I’ve found that some things actually aren’t working.
I’m also going to order the recommended forscan OBD tool, but I’m in Canada so it’s going to take a while to get here.
Then read these tutorials…
FORScan Tutorial Links - Ford / Information - CyanLabs Official Community
Based on the VIN you sent me, that is the original asbuilt for the APIM for this vehicle:
7D0-01-01 A221 0503 2BCF
7D0-01-02 0283 0000 0A69
7D0-02-01 4341 0104 40A3
7D0-02-02 8200 0000 005D
7D0-02-03 0000 DC
7D0-03-01 0000 0002 00DD
7D0-04-01 0100 0000 00DD
7D0-04-02 0001 DE
7D0-05-01 198C 198C 2E55
7D0-05-02 0EEC
7D0-06-01 805E
7D0-07-01 0A00 3300 001C
7D0-07-02 0000 0EF9 00E7
7D0-07-03 0056 5684 0011
7D0-07-04 694B
The APIM is original to the vehicle:
F110>DSGB5T-14G371-AF
F111>GB5T-14G380-BC
F113>GB5T-14G371-CFC
F124>GB5T-14G375-CA
F141>WV28003T
F188>GB5T-14G374-AF
Most likely the issue is the Strategy (F188) file, GB5T-14G374-AF. This file has been identified as problematic with bad or incorrect addressing which can cause the failure of the APIM to boot. It is possible to re-flash this file with a newer corrected version with FORScan and the USB adapter.
Read the FORScan instructions for programming modules.
Updating Module Firmware with FORScan, Program Guide Revised 09/2021 - Ford / Information - CyanLabs Official Community
You will need to reprogram the Strategy file.
After you reprogram the Strategy file, you must reload the asbuilt for the APIM all at once. Use the “Load All” button at the bottom of the asbuilt configuration page. Force write the asbuilt.
This will hopefully recover the unit.
I re-programmed the Strategy file as instructed, but I got the “Programming Successful, but something went wrong” message.
I assumed that this was because the APIM was already bricked, so I proceeded to try to reload the APIM asbuilt. I can’t open the AS-BUILT service procedure anymore because it keeps saying “service procedure has been interrupted”
UPDATE: I’ve spent the past 8 hours trying to get SOMETHING working… The only thing that has been achieved here is that now more things don’t work in the car. The USB in the centre console no longer works, the audio no longer works, there are no longer any audible dings when changing climate control settings… Nothing seems to be working to remedy this issue.
I’m guessing that the only fix would be to remove the motherboard and force reprogram the eMMC with all firmware and software, which is not guaranteed to work if the eMMC has issues. This APIM seems to definitely have eMMC issues with storage. I know this may be frustrating, but you proved at least that the APIM is defective. These procedures should have brought it back, and the fact that the calibration files seem to successfully program but do not bear this out. Sorry, but I think the APIM has issues that can’t be fixed without replacing parts, which is not worth the cost over that of a replacement.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
