Search results

@broncobase1 Not that it will help the cause at this point, but I can check what codes the truck reported to the cloud when whatever happened happened with the VIN.

If it is what I think it is, it can be fixed in minutes with FORScan.

VIN?

Same thing applies. If you get stuck at sync 23159 and show no more updates, let me know.

Well, damn.....I feel kinda bad now because I boosted you up into firing up FDRS. Turns out, the new APIM update has only been released by Ford for the 2023 Broncos. I know Ford does weird stuff like this, but since I don't follow these vehicles as closely as I do the F150's, Lightnings and Mach...

Yup. You going to reach out to him or do I?

I don't think the few updates you are missing are going to give you anything new, but if you have OCD like I do, I would want to be on the latest and greatest either way.

The only one you're showing is the GWM you need. Once you do that, it'll should release the APIM. If it doesn't, message me while your FDRS license is active and we can fix it.

No, I totally forgot. I don't spend a lot of time on this forum. Shoot me a PM tonight after 6pm eastern when I'm home and I'll gladly check.

PTS does not, but for the modules that update with USB, PTS rarely ever shows pending updates. I would have to check in FDRS when I get home in a bit to see if that OTA did release the next update you would need. However, we've learned a lot since then. He can most likely make the update for...

Correct....it is a back-end issue. Many vehicles (not just Broncos) hit a wall at Sync 23159. Do you still have FDRS access?

You can try an IPMA calibration procedure with FORScan. It will cost you next to nothing if it doesn't work.

I'm everywhere and nowhere at the same time. It is believed that this update is to fix an issue where vehicles on Sync 23159 stop getting certain update(s) they need to progress through the OTA process.

Auto-updates only apply to updates that require the vehicle to be inhibited while it installs. This is not one of those updates, so it will go through regardless of your auto-updates schedule. Once the OTA trigger is created, starting the vehicle is what will allow the OTA process to go through...

Gladly. Post or PM it to me

Most likely the same issue as the OP. Post or send me the VIN and I can confirm.

@Dfinch218 Post or send me the VIN. I have access to Ford's PTS and FDRS systems. If your Fordpass is activated, I can see the codes it is reporting to the cloud and any TSB's or recalls associated with them.

Does anyone that is experiencing this issue have FORScan? Is so, plug your truck in and go to line 754-10-01 in the TCU. If you anything on that line other than "5553 14" then that is the problem. Or post or message me the VIN and I can take a look to see if I can figure out the problem.

Post or send me your VIN and I'll poke around to see if I see anything.

Do any of your connected services work? If you have FORScan or know how to pull the as-built data on your truck, go to this line in the TCU. If in the 754-10-01 location you see anything other than 5553 14, then your TCU is registered to another country and that's your problem. Or send me your...