Community Mongoose (Reprogramming Vehicle Interface) Lending Thread

[rugedraw]

Hate for the cable to get too dusty! I’d be glad to borrow it if there’s still nobody on the waitlist.

I have 3 of them collecting dust in my garage. I will message you now.

Sponsored

 

[Cmatt]

I have 3 of them collecting dust in my garage. I will message you now.

I am also interested. I am very new to the F150 pickup world I come from BMW and GMC. Please message me I have a few questions about the process

 

[4 Fan Flyer]

Interested! Message sent!

 

[bgalakazam]

Put me on the list as well, please. Gotta get these updates going. Might do the Explorer, too.

 

[viper512]

Just curious, does using the mongoose cable permanently resolve the apim issue and enable auto updates?

 

[rugedraw]

Just curious, does using the mongoose cable permanently resolve the apim issue and enable auto updates?

Assuming you mean the bad Sync software that breaks the OTA process for 2021, then yes, it will fix the issue. The difficult part is getting out of where it is at now. That part alone can take 3-6 weeks. You need FDRS to make the USB update for the APIM and then you inset the USB into the truck and just have to wait for it to kick off and update the APIM.

 

[RyanRick]

Hi @rugedraw , I've pm'd you regarding the mongoose cable.

 

[rugedraw]

Hi @rugedraw , I've pm'd you regarding the mongoose cable.

Got your message, but right now may not be the time to do what you want to do. I am currently working with 4 other 2021 owners on the broken Sync that get stuck on Sync 22087 and not able to update it any more. I have reported the issue to Ford, but there is no solution in the immediate future.

I would recommend to you and anyone on Sync 20262, 20301 or 20312 to allow some time for us to figure out what is going on before climbing this mountain.

 

[RyanRick]

Oh bummer! So these trucks update until 22087 then get stuck? Yea I am stuck on 4.0.20262. I'll keep my eye's on the form to see if when there's a solution.

 

[viper512]

I'm about to update my truck, what seems to be the issue?

Newer updates aren't coming for 2021 trucks?

 

[rugedraw]

I'm about to update my truck, what seems to be the issue?

Newer updates aren't coming for 2021 trucks?

Trucks on very old Sync versions are getting stuck at a certain update. If your sync is newer than 22087, then it should be fine to update as much as you can based on what Ford has as available for your VIN.

 

[4 Fan Flyer]

I went through this just now with some help from rugedraw. I read the first few pages of the “ecu programming guide” forum thread from page 1 of this thread, and the last 5 pages. I definitely wasn’t reading all 1089 pages. The FDRS purchase and login has changed somewhat in the past few weeks. Make sure you download the .6.8 version, it’s a little bit lower on the download page (sorry don’t have a picture)

I had to go through 3 APIM updates over a several hour period this evening. I went from no version, to 22087, then to 22177, then 22293 (a 5gb update!) which gave me full screen car play. After the 22087 update rugedraw advised me to pull the negative battery terminal and let the truck sit for 20 min. I don’t know if this did the trick, or if something happened in the background that triggered FDRS to push several more updates.

I did not run the engine as FDRS advised for the updates, just left the truck hooked up to a power supply. Each APIM update took about an hour to complete, except 22293 which took almost 3hrs. 22293 took about 45 minutes just to download, another 15 to write to the memory card, then I let the usb stick sit in the car with the ignition on for about 2hrs. The update triggered as normal, but eventually the truck went to “sleep” except for a small banner on top of the main screen that said “update in progress”. I let the truck sit until this banner disappeared about 2hrs later.

When it was done I turned the truck on, the font for the sync screen looked significantly different and I had the option for full screen CarPlay.

 

[RyanRick]

I went through this just now with some help from rugedraw. I read the first few pages of the “ecu programming guide” forum thread from page 1 of this thread, and the last 5 pages. I definitely wasn’t reading all 1089 pages. The FDRS purchase and login has changed somewhat in the past few weeks. Make sure you download the .6.8 version, it’s a little bit lower on the download page (sorry don’t have a picture)

I had to go through 3 APIM updates over a several hour period this evening. I went from no version, to 22087, then to 22177, then 22293 (a 5gb update!) which gave me full screen car play. After the 22087 update rugedraw advised me to pull the negative battery terminal and let the truck sit for 20 min. I don’t know if this did the trick, or if something happened in the background that triggered FDRS to push several more updates.

I did not run the engine as FDRS advised for the updates, just left the truck hooked up to a power supply. Each APIM update took about an hour to complete, except 22293 which took almost 3hrs. 22293 took about 45 minutes just to download, another 15 to write to the memory card, then I let the usb stick sit in the car with the ignition on for about 2hrs. The update triggered as normal, but eventually the truck went to “sleep” except for a small banner on top of the main screen that said “update in progress”. I let the truck sit until this banner disappeared about 2hrs later.

When it was done I turned the truck on, the font for the sync screen looked significantly different and I had the option for full screen CarPlay.

This sounds promising... @rugedraw were the other folks able to get unstuck?

 

[rugedraw]

This sounds promising... @rugedraw were the other folks able to get unstuck?

Don't know yet. Some of them would need to borrow my Mongoose again to try. Even then, it will now cost $120 to try and hope it works. For all we know, you can spend that money and be stuck in the same place you were before.

 

[4 Fan Flyer]

Got my truck up to 22293, had a pending TCU update, updated the TCU this morning, that generated a gateway module update, finished the gateway update and after the update went through via the USB drive, FDRS needed to validate the installation and it appears the FDRS login servers went down. My FDRS lost connection and the gateway module update failed. I have been unable to get back into FDRS this morning. I ran the network test as well, I have a good internet connection but the FDRS login servers test said “failed”.

I think I might have been able to get another APIM update if the gateway test went through, but my license runs out in 90 minutes and I’m at least happy with how far I got.

Sponsored