Slappy McGee
Well-known member
- Joined
- Apr 19, 2021
- Threads
- 8
- Messages
- 151
- Reaction score
- 93
- Location
- South Caccalackey
- Vehicles
- 2021 F-150 Powerboost
- Thread starter
- #1
I figured I'd chronicle my attempt to get my '21 Platinum Powerboost working with the long-promised, often delayed BlueCruise feature.
I picked up a lot of nuggets from the massive FDRS thread, but wanted to provide a narrative/experience specific to trying to recover from a failed 1.7.1 OTA.
Like many others, my truck failed the 1.7.1 OTA update in Dec/Feb and gave up trying to update. I visited the dealer on 3/18 and they told me something to the effect that "Ford says not to do anything 'yet.'"
I'm a bit bummed to not have BC, and have little faith in Ford fixing this without a dealer visit or long delay, so decided to go the FDRS route.
DAY ONE:
Ordered my Mongoose from Amazon, which had clearly been used before and when prompted by the software to register was told that I was "already registered." Didn't seem to create any problems.
Paid my $50 for a 2-day FDRS license and got the software installed on a ~2 year old laptop running Windows 11.
Hooked the truck up and kept the battery around 12.5V with a NOCO Genius 10. Not the recommended solution but don't want to spend more on fixing Ford's problems.
Went through the updates. My basic flow was to pick the first module on the list, and hit update. Then let it install all the dependencies, reboot, and then leave the truck alone for a bit before doing the next one.
Several of the updates are SUPER frustrating in that there's no indication how long it will take or how many steps are involved. Lots of stages will say something like "Step 3/4" and then 10 minutes later you're somehow at "Step 1/6" so there are steps within steps.
Probably took me about 5-6 hours to get to the APIM update, some of the updates are huge (I'm looking at your IPMA and friends). The APIM USB preparation took FOREVER as well. My laptop is fairly modern, and I'm using what is supposed to be a USB 3 stick (unless it's an Amazon counterfeit) but it took a good 30+ minutes to copy 3.7GB to the stick.
I did NOT have a gateway module update in the list, but assume that's because I need to get everything else more current and then will get a batch of new goodies.
I put the stick in, the screen acknowledged it was there and did some "indexing" and then.... nothing. This seems to be common from reading the other thread.
I did the remaining updates (dash module, towing) and the consensus seems to be that the APIM USB update is like the Ghost of Christmas Yet to Come, who will arrive in his own good time.
I drove about 5 miles and didn't notice much difference on shifting, etc. other than the engine running more than usual on this route, presumably to charge up the hybrid battery after so many on/off cycles? I didn't clear the shift tables since FDRS said this was only if new hardware was installed. I may try that later if the consensus is that it's not going to break anything.
I did notice that the parking sensors, and reverse "lines" didn't work as I pulled out of the driveway, but they seem to calibrate after some driving and start working again automagically.
I also lost the power running boards functionality, which seems to be a problem others are encountering as well. Seems like Forscan will fix this although I'm hoping there's an FDRS solution so I don't have to buy/install/learn more software.
So at the end of Day One, I've spent ~5 hours giggling my mouse, watching painfully slow and inconsistent progress bars, and don't have much to show for it. I'll be away for a few days for work so hoping the drive to the airport triggers the USB update and there's some forward progress on getting the APIM updated.
I picked up a lot of nuggets from the massive FDRS thread, but wanted to provide a narrative/experience specific to trying to recover from a failed 1.7.1 OTA.
Like many others, my truck failed the 1.7.1 OTA update in Dec/Feb and gave up trying to update. I visited the dealer on 3/18 and they told me something to the effect that "Ford says not to do anything 'yet.'"
I'm a bit bummed to not have BC, and have little faith in Ford fixing this without a dealer visit or long delay, so decided to go the FDRS route.
DAY ONE:
Ordered my Mongoose from Amazon, which had clearly been used before and when prompted by the software to register was told that I was "already registered." Didn't seem to create any problems.
Paid my $50 for a 2-day FDRS license and got the software installed on a ~2 year old laptop running Windows 11.
Hooked the truck up and kept the battery around 12.5V with a NOCO Genius 10. Not the recommended solution but don't want to spend more on fixing Ford's problems.
Went through the updates. My basic flow was to pick the first module on the list, and hit update. Then let it install all the dependencies, reboot, and then leave the truck alone for a bit before doing the next one.
Several of the updates are SUPER frustrating in that there's no indication how long it will take or how many steps are involved. Lots of stages will say something like "Step 3/4" and then 10 minutes later you're somehow at "Step 1/6" so there are steps within steps.
Probably took me about 5-6 hours to get to the APIM update, some of the updates are huge (I'm looking at your IPMA and friends). The APIM USB preparation took FOREVER as well. My laptop is fairly modern, and I'm using what is supposed to be a USB 3 stick (unless it's an Amazon counterfeit) but it took a good 30+ minutes to copy 3.7GB to the stick.
I did NOT have a gateway module update in the list, but assume that's because I need to get everything else more current and then will get a batch of new goodies.
I put the stick in, the screen acknowledged it was there and did some "indexing" and then.... nothing. This seems to be common from reading the other thread.
I did the remaining updates (dash module, towing) and the consensus seems to be that the APIM USB update is like the Ghost of Christmas Yet to Come, who will arrive in his own good time.
I drove about 5 miles and didn't notice much difference on shifting, etc. other than the engine running more than usual on this route, presumably to charge up the hybrid battery after so many on/off cycles? I didn't clear the shift tables since FDRS said this was only if new hardware was installed. I may try that later if the consensus is that it's not going to break anything.
I did notice that the parking sensors, and reverse "lines" didn't work as I pulled out of the driveway, but they seem to calibrate after some driving and start working again automagically.
I also lost the power running boards functionality, which seems to be a problem others are encountering as well. Seems like Forscan will fix this although I'm hoping there's an FDRS solution so I don't have to buy/install/learn more software.
So at the end of Day One, I've spent ~5 hours giggling my mouse, watching painfully slow and inconsistent progress bars, and don't have much to show for it. I'll be away for a few days for work so hoping the drive to the airport triggers the USB update and there's some forward progress on getting the APIM updated.
Sponsored