speedracercjr
Well-known member
No dice....same exact scenario.If it asks if original module is installed alwyas select no..
@antho told you updating the CMR was a bad idea LOL
Sponsored
No dice....same exact scenario.If it asks if original module is installed alwyas select no..
Must be a ford issue. I updated it a when it came out.
What cable / hardware are you using? Mongoose?
HP Laptop running Windows 11 and the mongoose. Same setup I've been using for a long time. As mentioned I even updated the TCU right before attempting the CMR. My truck has always fought me on updates, this really isn't a surprise either!What cable / hardware are you using? Mongoose?
Maybe disable antivirus temporarily?HP Laptop running Windows 11 and the mongoose. Same setup I've been using for a long time. As mentioned I even updated the TCU right before attempting the CMR. My truck has always fought me on updates, this really isn't a surprise either!
Now that you say it, a couple weeks ago Windows installed this new Microsoft Defender:Maybe disable antivirus temporarily?
Hey everyone. New 2021 F-150 owner here, and after reading this and other threads I decided to get a mongoose and FDRS to try and get my Truck updated. Its showing all the symptoms of being in OTA lockout, like the auto updates option being greyed out.
Last night I got the mongoose connected and FDRS going, but i'm unable to update the APIM. When I insert the USB it never installs the updates. I was prepared to perform the Module Repair TSB, but when I ran it, I got this message on my first attempt.
"Exception trying to obain diagnostic files from the backend server required to repair this vehicle. This could indicate the VIN has been locked out. Would you like to retry?"
I poked around in the VIN history and does seem like the APIM updates and module repair TSP has been attempted many times in the past. I've had the truck for a week, and i'm starting to see why the original owner may have traded it in. Any idea's how to fix it?
| 6/15/2022 | 1:48 PM | APIM Update attempted | Procedure Unsuccessful - low battery voltage |
| 6/15/2022 | 3:21 PM | APIM Update attempted | Procedure Unsuccessful - low battery voltage |
| 6/16/2022 | 10:51 AM | APIM Update attempted | Procedure Unsuccessful - Unable to program module |
| 6/16/2022 | 12:10 PM | Module Update Repair | Procedure Unsuccessful - Exception setting Ethernet adapter |
| 6/24/2022 | 1:44 PM | APIM Update attempted | Procedure Unsuccessful - low battery voltage |
| 6/27/2022 | 10:17 AM | Module Update Repair | Procedure Unsuccessful - Unable to perform Fastboot Image flash recovery |
| 6/27/2022 | 10:23 AM | Module Update Repair | Procedure Unsuccessful - Fastboot Process has timed out |
| 6/27/2022 | 12:50 PM | Module Update Repair | Procedure Unsuccessful - FlashDiagFileOverCan unknown error |
| 6/27/2022 | 12:53 PM | APIM Update attempted | Procedure Unsuccessful - BatteryCheck unknown error |
| 1/5/2023 | Vehicle Re-acquired by Ford | Reason provided by Ford - APIM needs replacing | |
| 1/30/2023 | 8:20 AM | APIM Update attempted | Procedure Unsuccessful - low battery voltage - no USB was inserted |
| 5/19/2023 | Vehicle Purchased by Me | Dealership informed me that the APIM was not replaced, and was reprogrammed instead. Clearly this didn't happen based on FDRS logs. There's one failed APIM update on 1/30 | |
| 5/24/2023 | 9:04 PM | APIM Update attempted | Procedure Unsuccessful - Unable to program module |
| 5/24/2023 | 9:39 PM | Module Update Repair | Procedure Unsuccessful - GetDiagFiles failure - VIN is locked out |
| 5/24/2023 | 10:22 PM | Module Update Repair | Procedure Unsuccessful - GetDiagFiles failure - VIN is locked out |
| 5/24/2023 | 10:35 PM | APIM Update attempted | Procedure Unsuccessful - Unable to program module |
| 5/25/2023 | 7:12 AM | Module Update Repair | Procedure Unsuccessful - GetDiagFiles failure - VIN is locked out |
Right? It's not like you are getting into a phone and need to protect the data.I'm still dumbfounded that they lock things out. Doesn't make sense to me why they would do that.