Interesting, I returned my truck back to stock and re-flashed my OZ tune with zero issues at all after I installed the PCM update via FDRS.
Using HP Tuners, I reflashed my custom tune after the update messed up my tune. No issues thus far.
Awesome, so it's not just me.
I’ll definitely be disabling mine also.
I just had my SCT X4 updated and unmarried free of charge in about 5 min thanks to the people at SCT. Ken is now building me a new tune for my current software. For how quick and easy it is to just unmarry and update the device and get a new tune built (which is what he recommends) I’d rather be safe than sorry. That’s just my personal opinion tho. Glad yours is working now. My OTA updates are now shut off for good LOL.
I just received an email from OZ about this subject and it states “DO NOT” try to re-flash your tune.
Ford says you're responsible for their OTA breaking your OOW vehicle. Then the local dealer's incompetence will have them replacing a module that other modules say it can't talk to after the GWM acts up post OTA. Then when asked for proof they're actually connected to the truck, they make excuses while sitting at the desk playing with PTS, even after the 'service manager', in very specific terms, is told what to do. If excuses were results, I'd advocate for hella bonuses for them.
That’s the shitty part that I don’t like. You won’t get them. You basically have to look in the notes after they roll out to see exactly what that update did. If it doesn’t mention upgrading PCM software or anything in that general area you should be good to download. I’ve always had mine on and the truck seemed to improve with each update. But since there’s the risk of whipping your tune out my OTA updates will be off from now on.
That’s the kicker for most people… OTA is the only way for a good majority of the folks on this forum.
Unfortunately, the ability to go to OTA updates has become kind of an addictive drug for e.g. the car companies. “Let’s release this feature/uodate/bug fix to production before it’s really wrung out and we can fix it with an OTA update later.”
Even worse, the layman’s description of each update is insultingly dumb, “Great news! We’re making your truck run better!”
It’s just speculation on my part, but it would not surprise me if it turns out that this method, which worked fine this time, leads to all kinds of trouble with some future OTA update. Just because it worked fine this time is no guarantee it will next time. Remember, there are often many many paths through a software load based on a host of variables any one of which could lead to bad juju if things go sideways for any reason.
