First, sorry about swapping "Ak" and "ar" in your name Akarpet. Thanks for this feedback. I'm going to do a Cyanlabs build and give it a go.

 

OK, I understand now.

 

I meant that the warranty outline you described is standard practice across many companies offering products that run software. Computers, smartphones, etc.

I'd love to hear of a company that has warrantied software updates in the context you're looking for. You don't get to call Microsoft, Apple, Google, etc. when they push a bad update to your computer or smartphone and demand a fix "today". Apple is not going to replace my iPhone for free because of a bad update. You report the issue and hope they release an update to make it right in an acceptable timeframe. I can demand fixes from all of these companies all day long, but at the end of the day I'm at their mercy if they push an update in 3 days, 3 months, or 3 years. As a consumer, it's up to me to decide how long I'll put up with waiting before I switch products. To my knowledge, Ford has not told anyone that's contacted them that they will not be issuing an update or TSB to address the issue, but that it will come at an unknown date in the future. This isn't just a simple task of "change the bit that is causing this issue" and push the new update. Due to how the issue affects being able to install updates, Ford needs to develop and test a repeatable process that dealer techs can use to free up space and install an updated/fixed version of Sync.

Again, this practice happens all day long with your computer, your smartphone, etc. I get what you're saying, but I'll still argue that we aren't talking about a major system that's critical to your truck running here. This isn't brakes, airbags, or wheel bearings. It's a radio, and the "safety" of that system, if you're that worried about it, can be accomplished by simply pulling a fuse or disconnecting it. You don't need a radio to drive your truck.

I get it's frustrating and Ford does need to address it, but IMO you're putting the cart before the horse a bit. If your major complaint is the coverage under warranty, then make sure the issue is documented with your local dealer while in warranty, so that you can plead your case for reimbursement or a free fix when a fix is released. This is no different than other components on these trucks that people have paid out of pocket to replace, only to later find out Ford issued a recall or TSB to have the component replaced for free.

 

I am a new member. I joined the forum because I was having this issue with my MY19 F-150. Local Ford dealer said I need a new APIM. But thanks to all the members on this forum I did not waste $1000 on a new APIM. Hesse, your 6 easy to understand steps along with other members instructions allowed a non-tech guy to fix the issue! I did not have or know how to use Forscan but the good folks over at “fmod” had a download to a usb that would accomplish the Jailbreak. So I could follow your outline and fix the issue. Thanks for your help!!!!!

 

Obviously our rationale is different on this subject. So I propose we agree to disagree and move on with the important matters at hand.

 

Also wanna know!!!

 

All good

 

I have been fighting this thing for 2 months and been unable to get the jailbreak to work on my 2020. It is less than 3 years old, but because I drive a lot I have exceeded the 36k b2b warranty. I have never been so aggravated with a vehicle in my life. I got a new phone today and now it will not stay paired.

My first car was a 1966 Mustang and I had been a Ford man ever since. But I will NEVER buy another Ford again. THEY ****ed up MY vehicle and now I have to pay to fix it. I have no words.

Where is the best/most reliable place to purchase a new APIM?

Thanks

 

Had this same issue on my 2019 F-150 Lariat with the pop-ups at startup and losing settings or going to default randomly (ex. radio goes from Satellite to FM or SID), backup camera delay setting wiped out, WiFi settings reset, etc. for about a month.
All the research pointed to what appears to be an issue with the log files filling up the APIM memory in build version 3.4.22251.

Found the following to solve my problem (likely in the short term only until there's a permanent updated/fix from Ford with a new build) without having to downgrade/upgrade my SYNC software. The whole process took around 10-15 minutes doing it the first time after watching the tutorial video a couple of times to feel confident in the timing of the steps.

Follow Step 1 (you do need FORScan but it's) and first part of Step 2 (Daemon Installer only) and then as Step 3 add the rwdata Cleaner mod from the following instructions.
Step 1 - Jailbreak (Step 1 in the following link)
https://www.fmods.net/community/viewtopic.php?t=190
Step 2 - Daemon Install (First of 2 install packages mentioned, you don't need the Mods Tools step)
https://www.fmods.net/community/app....r_%28daemon%29
Step 3 - rwdata Cleaner
https://www.fmods.net/community/app....wdata_cleaner/

Expect that my log folder will gradually fill up again over time (possibly faster if using CarPlay as there's potentially a 2nd bug associated with that which is impacting the size of the log files) so I'm keeping the USB with Step 3 in my vehicle so that if the issues come up again I can simply plug that last USB drive in and let it clear the log folder again to buy more time until a permanent fix is out.
My SYNC system doesn't show access to the latest build version 3.4.23088 which is believed to have solved the log file compression issue (but potentially not the CarPlay issue) so while this is not perfect solution it's still a relatively easy workaround that is sustainable.

 

Nice!