JEB
Well-known member
- Joined
- Aug 15, 2021
- Threads
- 0
- Messages
- 576
- Reaction score
- 393
- Location
- Northern Illinois
- Vehicles
- 2021 F-150 Lariat Powerboost
I’m not sure about this. I saw reading and indexing activity during the update but no indication that the truck was ever writing directly to the drive. But it’s possible. It’s also possible that files are written during post-install validation by the computer.I would negate this statement. The truck writes back data to the USB drive once update completes. This is what I have observed: When FDRS copied files to my USD drive, it contained all the update files in a folder called FordSoftwareUpdates and a manifest file called 1FTFW1ED2NFAxxxxx_FordSoftwareManifest.der. Once the installation completed and removed the drive from the truck, it contained an extra file 1FTFW1ED2NFAxxxxx_vil. I am not sure what is the purpose of this "vil" file as FDRS never asked me to plug the USB drive back in to my laptop. It did its own validation over CAN without USB drive inserted.
I am also questioning the need of leaving the USB drive connected when it asks for system restart on the Sync screen. The only reason it would be, is to copy this "vil" file back, which is not used anyway. At least not by FDRS tool. Perhaps the older IDS/FJDS tool needs it ?
As for the prompt to return the USB to the computer, that prompt does not come from FRDS. It comes from the Sync screen following reboot after the truck is restarted. If you’ll recall, when you start the update procedure after inserting the drive into the truck’s USB reader, the sync screen has a pop up that cautions you to not remove the USB drive until prompted to do so. That removal prompt comes after restart and reboot, from Sync not FDRS, along with an instruction to transfer the drive back to the computer. Once that’s done, FDRS again takes over to continue the validation after you click “ok” on the computer that the update was successful. Whether this happens every time or not I don’t know. But it definitely happened with the TCU and APIM updates I did last month and the GWM update I did two days ago.
Sponsored