Sync3 official Ford update seems to have bricked the unit

Hello all, hopefully somebody can help with this as I’m getting pretty annoyed.
Basically, I updated the Sync3 in my 17-plate Kuga using the official files and directions from the Ford website (APIM from stock, as far as I know). I was on 2.2.16280 and the Ford update was 3.0.23219. Did everything the website said and eventually got the message to say that the update would be installed next time the engine is started. Went out yesterday morning in it and the screen is just black. It lights up (only a lighter shade of black) for around 10 seconds, and the 2x USB ports light up for around 10 seconds too, but then they both go off.
If I turn the engine off, open the door, close the door and turn the engine on again, it does the same thing, lights up for a few seconds then goes out.
The soft reset method of power and seek doesn’t do anything at all, neither did pulling the fuse and pulling the battery.
The APIM shows up on FORScan and APIM reboot works on FORScan, but all that does is the exact same light up for 10 seconds thing.
I don’t have any options on FORScan to flash the unit, I believe that’s because I don’t have a newer beta version of the software.
I tried the Syn3 Updater and created a reformat file with updates, but the USB ports just don’t seem to respond. I’ve also tried 3 separate USB sticks.
I’ve pulled the fuse again this evening and I’m leaving it overnight but I’m not feeling very optimistic.
Does anybody have any advice on where to go with it next please?


SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 2.2.16280

New SYNC Version: 3.0.23219

Do you have a error message, if so what is it?
There are no error messages, the screen is just black and lights up occasionally, but only a lighter black.

Update Method: Official Ford

Flashing firmware with ForScan isn’t going to do anything here.
Try pulling the battery cable for 35 minutes to force a full cold boot of all the modules.
After that if you don’t have any DTCs showing I’d go down the bad screen path first since the boot can hang up if the video board doesn’t fully initialize.
After that I’d be looking for a replacement APIM.

1 Like

Thanks for the reply. I’ll try the battery reboot first then. Any idea what might have actually happened?