Search results

You're also on Sync 21091 like the OP. You have an APIM update pending for you, so the update you need to progress is there. Modem is working fine and the truck is talking to the cloud. Just like the OP, I see no reason why you aren't getting updates. Last APIM update you got was in July 0f...

VIN? PM is fine.

https://github.com/agronick/aa-torque?tab=readme-ov-file This has been out for months. It's not in the playstore, so you'd need to side-load it with Kingstaller. It can be tedious to set up all the PID's, but it works and it works well.

Unfortunately, something like this is virtually impossible to diagnose remotely. I will tell you this: Before I pay $670 to swap out some O2 sensors, you best believe I am crawling under my truck and doing it myself.

"Not completed" means the update failed, expired or got canceled by the server. I can check which of these it is with the VIN, but it is moot point now. Nothing you can do but wait for it to be resent.

Post or send me your VIN and I can check.

As mentioned, the VCX Nano is not recommended due to possible issues. I know multiple people on the F150 forums who started updating with the Nano and ended up having to order a Mongoose to finish what the Nano broke. If you do go the FDRS route, I would compromise elsewhere. Or, get on the list...

No, what I showed is what Ford's PTS website shows your truck has right now. The .pdf says the latest is 24ddd. The Ford rep you spoke to said they can't see your software version because you haven't gotten an update. That is straight BS. You can not only see the sync version, but you see the...

The people that answer the phone there are trained for customer service and usually don't know a damn thing when it comes to the vehicles they represent They have access to the same things I do, but do not know where to click to see things or know how to interpret what they see. While there are...

You're only showing door module updates. FDRS just for updates would be wasteful. These modules will be updated with OTA DDM 24.11.5 which is being talked about here and is getting mixed reviews...

Post or send me your VIN and I can see what you have pending. Keep in mind that the OTA process is hot garbage and older vehicles are going to have more pending than you and will get updates yours will never see since it was already built with them.

The $1,500 VCM is the one dealers use. It writes faster reducing the amount of time you spend installing updates. Worth it for a dealer, but not for an individual. Being a 2024 owner, I don't think there would be enough updates pending for you to invest in it. If you have the disposable income...

Agreed on all point but this one. FDRS is full of guided routines that do all the work for you. If a module bricks, guided routine to recover it is there. it's pretty dummy proof, IMO. Like you said, the initial investment to get the tools needed are more than many are willing to spend. Whether...

Exactly right.

According to Ford, it should 24ddd for the 2024 Bronco. This does not make much sense to me in terms of how you decode the Sync version, but that's what it says. 23237 would be software approved for release on the 237th day of 2023, so I don't know what ddd means.

Don't bother with the FORScan codes. It's like I mentioned yesterday: This would be very difficult to diagnose remotely. The only thing we can think of, is send me the link to or the instructions to the plug & play kit you used so we can see what it requires in terms of install to see if that...

Ok, so when you said "no communication with module A", what were you trying to do when you got that message? Also, the codes your truck is reporting to the cloud may not be all of the codes it is reporting. If you can, plug it up to FORScan again and send me all the codes it is recording via...

Yea, I don't think this has anything to do with the FORScan changes. Your truck is spitting out all kinds of lost comms codes between different modules. This may be impossible to diagnose remotely, but maybe I can give you an idea where to start. I'll get back to you tomorrow. So you're saying...

Strange. The FORScan changes you made were to the ACM, I assume? That module has nothing to do with the symptoms you're describing. Send me your VIN.

Module A?