I tried to update the sync 3 stereo in my 2017 Transit Connect Limited as it said there was an update available, downloaded the software from ford onto a usb and did the update, half way through the screen went blank and never came back on again, no sound from radio or nothing, not even showing up on bluetooth through my phone, the reverse camera only works just after you have started the van and will never show again until the van is turned off and back on again.

 

From what i can gather the APIM has stopped working, the part number for mine is HV1T-14G370-KFA, is there anyway this can be re flashed with the sync 3 software or can i buy a replacement module and does anybody know if any other similar modules will work or anybody that could fix this for me

 

many thanks

Steve

It's been awhile since this subject has come up. Yes the APIM of 2017 vehicles is prone to being bricked and Fords answer is always to replace it with a new one, at great cost !!

I would suggest you take a look at Cyan-Labs. They can possibly help get your APIM working again and even updated.

https://cyanlabs.net/

would this be done through OBD?

Read all of the information and carefully follow Cyan-Labs instructions exactly. You will need a USB pen drive. If in doubt contact their technical support.

3 minutes ago, unofix said:

Read all of the information and carefully follow Cyan-Labs instructions exactly. You will need a USB pen drive. If in doubt contact their technical support.

The stereo wont boot up, i get the ford logo on startup and thats all, black screen, nothing else

Yes, that is what happens when the APIM has been bricked. Cyan-Labs have the means to format and reload files to get it working in most cases. Just because the screen is blank and you can't see anything does not mean the APIM is not powered and awaiting further instructions.

Cyanlabs software can’t help you unbrick an APIM. It can only help you with updating or downgrading software. The system has to be able to read the usb and install the files off it. 
 

I would try Forscan and see if the firmware of the apim is still communicating on canbus. 

Agreed, Get the V-Linker or OBDLink-EX cable and a paid license and restore and update the firmware in the APIM and ACM, then update the Sync 3 software using CYAN Labs

If you're a paid license, FORScan support team will help you

I can resurrect dead sync 3 apims I have an eeprom writer and an image of a working apim to flash to it  the process takes about 4 hours 

@DaveT70 updating the firmware will have no bearing on this issue it’s the software that’s the fault and firmware and software are on 2 totally separate boards 

3 hours ago, alexp999 said:

Cyanlabs software can’t help you unbrick an APIM. It can only help you with updating or downgrading software. The system has to be able to read the usb and install the files off it. 
 

I would try Forscan and see if the firmware of the apim is still communicating on canbus. 

It will be communicating otherwise the camera wouldn’t work when he 1st turns it on and the ford logo would not show 

Just now, jimbojambojumbo said:

It will be communicating otherwise the camera wouldn’t work when he 1st turns it on and the ford logo would not show 

It shouldn't be possible to brick the APIM during a normal update, the system updates between two partitions, so even if it was interupted it should have the old system partition to boot from.

I wonder if the NAND has just died during writing.

57 minutes ago, alexp999 said:

It shouldn't be possible to brick the APIM during a normal update, the system updates between two partitions, so even if it was interupted it should have the old system partition to boot from.

I wonder if the NAND has just died during writing.

The nand dying is a known issue but the fact it is booting to some extent it’s more likely just an update gone bad for whatever reason and the new partition has been set active which is why it’s not booting to the previous version I recovered one recently that had this exact same issue 

On 9/22/2023 at 11:05 AM, jimbojambojumbo said:

The nand dying is a known issue but the fact it is booting to some extent it’s more likely just an update gone bad for whatever reason and the new partition has been set active which is why it’s not booting to the previous version I recovered one recently that had this exact same issue 

What would the cost be to try and fix this, no rush at the moment as i have bodged my old android head unit in for now, 

 

On 9/22/2023 at 6:13 AM, alexp999 said:

Cyanlabs software can’t help you unbrick an APIM. It can only help you with updating or downgrading software. The system has to be able to read the usb and install the files off it. 
 

I would try Forscan and see if the firmware of the apim is still communicating on canbus. 

I have forscan and the Vlinker cable, any instruction on what to try? (new to this forscan stuff)

See if Forscan can read the DTCs from the APIM. See if the unit is still communicating

Even if it is you’d need the software re written as someone mentioned above. If not it’s likely completely dead.