Search results

From where did you grab the signal to feed the amp for the sub? Did your truck come with the 7 or 12 speaker system?

Unfortunately, due to some recent changes Ford made in their cybersecurity, anyone who runs a VIN through FDRS without being plugged directly into the vehicle runs the risk of getting their account banned. AFAIK, checking for pending updates in PTS is still safe from the ban-stick, but in my...

Did you order the kit from Infotainment? If so, they have top notch support and I would try contacting them.

The fact that you show an IPC update is a good thing. That module is directly related to the Sync modules. It is possible that updating the IPC with FDRS will release more updates for the APIM, GWM and/or TCU that will allow you to get further along the process. These modules have to be updated...

For FDRS, many people got around not being able to use it by using a VPN in the past, but not sure if that will work any more with the newer FDRS and the new cybersecurity systems. For the modem itself, I'm not sure if there is an easy way to trick it into getting cellular data working. I've...

No; only a few updates ever sent out require wifi. If the vehicle is exported to another country, the TCU would need to be provisioned for that country for connectivity to work. That is, if that country is supported by Ford for OTAs and connectivity to work.

You would need FDRS. I am pretty sure that FDRS is supported in Italy. You need a Ford-specfic Mongoose J2534 cable, a 20amp or bigger battery power supply, a USB drive and a windows-based laptop. A guide explaining what FDRS and basic tutorial on how to use it is below...

@vdob I have your VIN. OTA history is only recorded for 180 days at a time, and it shows no OTAs have been sent to you in 180+ days. Connectivity is working fine on your truck and it is not reporting any codes that would indicate any issues other than some low battery voltage codes since it...

I have other suspicions, but we've hijacked this thread as it is.

The AI will recognize the sign in from a different IP/MAC address and may ban the account. You may be able to get away with it for a bit, but it will catch it. I can tell you for sure it has happened to a few techs already that did this. Below is a message I got from someone who works in TAC...

The way it works now, if you buy the 2 day subscription for FDRS, it will also include access to IDS. It will be $120 regardless of whether you use only one or the other or both. https://www.motorcraftservice.com/Diagnostic/Support?channelId=51&categoryId=304

Yea, that's more or less when they started with this crap. The new system is garbage. The new AI cybersecurity system is banning people's accounts left and right for the slightest infraction. In some cases, accounts are getting banned for no reason at all.

This will not work anymore. Click the links and go through the motions as if you wanted to buy a license and you will see what I mean. That is the old link from when you used to be able to buy a license key. Now, it is subscription based and governed by the new cybersecurity methods they...

I think he means spending $120 on the FDRS license only for it to get banned again if the VPN doesn't work.

Do not use the same email you use for Fordpass for FDRS or it can mess up both if they ban you.. Always use a burner address for FDRS. I would recommend any FDRS DIY user do this whether you are in the USA or not.

Ford made some changes to their cybersecurity systems recently. The new system is believed to be AI based and bans accounts for the slightest infractions. I don't think the VPN trick will work anymore.

You can download the ab data from any vehicle with the VIN here: https://www.motorcraftservice.com/AsBuilt

Some people on the Bronco Sport forum posted they had appts made to address this already, so maybe I was wrong on terms of how long the fix was going to take.

Assuming you are talking about the recall below: No, this OTA will not address that. For now, Ford has just filed the recall with the NHTSA as of a few weeks ago, so I highly doubt the firmware to address this is ready. I doubt this will be ready for a few months. Also, I mentioned earlier...

Correct. That is a GWM update. But, this is a prerequisite to the APIM update that may address your concerns. From what I have been seeing on other forums, you may get it in a days followed by a third update for the TCU. Edit: The APIM update mentioned above is not meant to correct the issue...