Update from 1.0 to 3.4.23188 - Factory Backup Camera Issues

Ford SYNC 3 Support CyanLabs Update Support
, , , , ,
1

I went from Sync 3 1.0 on my 2016 F150 to the lastest 3.4.23188 today. Everything with the update went well. Having an issue with the backup camera now. It is going blue screen, then black screen, then camera not avalaible. Is there a fix for this or a way to revert bac k to the 1.0?

SYNC Region: NA

Navigation Variant: Non Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 1.0

New SYNC Version: 3.4.23188

Do you have a error message, if so what is it?
Camera unavaliable error message when in reverse.

Update Method: CyanLabs Syn3 Updater

Syn3 Updater Version: Most recent, downloaded yesterday

Syn3 Updater Documentation Read: yes

Syn3 Updater Log File

..
2

Did it work before the update? and is it an aftermarket camera or a true Ford OEM one?

As the instruction indicate, you cannot revert back to any 1.0 or 2.0 version once you go past 3.3

3

Yes, it worked perfectly before the update. It is the factory camera built into the tailgate.

1 Like
4

Use the updater to go back to 3.3.19052 and see what happens.

5

I attempted this already today. I went to the oldest version that the program would allow me to go back to. Taking a look at the ForScan readings, it said there was an electrical issue. I am assuming it is something with the APIM hex codes…

6

Have you master reset?

7

Yes, I have tried master reset as well.

8

Are you the first owner of the car?.

It’s unlikely it’s an asbuilt setting, have you done any modification to it?.
Is that DTC new?. A Sync3 update does not trigger an electrical DTC.

9

I am unsure if it is new as I have never had to hook the truck up to ForScan. It would have to be a massive coincidence that it has an electrical issue as the truck hasn’t moved or done anything except for a couple of flash drive tasks. I did go down the jailbreak route using FMods but all of this was also reset after having to flash back to the oldest software offered. Could jailbreaking it cause something like this? After going down everything on the list that I could think of or find, as a last resort ended up writing the APIM coding using what was sent over VIN specific by Ford Website today. Even that resulted in no luck.

10

For the 2nd time, are you the first owner of the car?

11

No, I am not but have had the vehicle for about 4.5 years with no issue on 1.0.

12

I didn’t think you were, you are “too involved” to have a 2016 vehicle without ever upgrading it to the latest 3.0 builds.

So that opens another front, another honest question: if you are not the first owner of the car, how can you assure the camera is OEM/factory?.

13

When looking up the vin, it is pulling it as having parking sensors and backup camera. The camera is built into tailgate handle and sensors in bumper. Judging by that, it is almost certain it is factory correct? All harnesses behind radio are from factory.

14

These little details are important, we do not know the car.
There were some models (specially in South Africa) that had issues with cameras, but they didn’t really were OEM/factory, they were added by dealers over there. That was solved by reverting to an older 3.4, which is not your case.

So, assuming everything is OEM, installing 3.4 would not kill your camera.
I know we do not like coincidences, but they do happen.

About the DTC, which is exactly?. Which module is telling you that?.

Also, it’s a good idea for you to create and share the interrogator log file, which will contain your current ASBUILT for the APIM. From your previous update, I got you already re-applied the OEM asbuilt and reset the module for it to pick it up, right?. This also goes towards that something else may be at play here.

15

Yes, I reapplied the OEM asbuilt and have attached that here. The DTC is coming from APIM code C1001 - Vision System Camera (additional Fault symptom: General Electrical Failure).

73fd43c6-6a72-4497-8c32-5c34a8ddba3d
73fd43c6-6a72-4497-8c32-5c34a8ddba3d638Ă—295 4.77 KB

F150.ab (28.3 KB)