You should be fine with Nano here as FDRS merely uses it to read the module state and certain configuration parameters to initiate the flashboot procedure. Then it will be used to create the USB update flash drive. You should be good to go here!
I can answer this question with quite of a certainty:
Cool. So that explains why the USB would still be in the truck. For the soul purpose of writing the json file to the USB, regardless of whether the file is critical.
Iceman, I did the TSB today. Used the following parts:
I think whether you need ethernet or not may be truck dependent. I did mine without it at first (because I only had a combined hub/ethernet which sync doesn't like) and it did not fix the issue. One I added the ethernet it deleted some sync databases and diagnostic files from the APIM, GWM, and TCU which is what finally un-greyed my updates and brought back my sync version.
Did the alignment procedure fix the right line hugging? My truck has done that since I got it off the lot. Still does it with BC active.
I think all the modules have self tests. But check two things before shelling out the cash. FIrst, have someone with an active FDRS license look in the APIM toolbox to verify. Second, FORScan has some diagnostic procedures, including self tests. If there’s an APIM self test in FORScan, you might be able to run it there without the cash outlay.
How long did the TSB take to do?Iceman, I did the TSB today. Used the following parts:
https://www.amazon.com/dp/B015ORX70S?psc=1&ref=ppx_yo2_dt_b_product_details
https://www.amazon.com/dp/B009GUXG92?psc=1&ref=ppx_yo2_dt_b_product_details
https://www.amazon.com/TRENDnet-Ethernet-Network-Compatible-TU2-ET100/dp/B00007IFED/ref=sr_1_4?crid=3IP8B0TWFG2Q0&keywords=trendnet+usb+to+ethernet&qid=1648443868&s=electronics&sprefix=trendnet+usb+to+etherne,electronics,137&sr=1-4
You need those and the mongoose. When you follow the TSB it says to remove the lower console panel but you need to remove the upper as well (see my picture). When you do this in FDRS, it will use the mongoose to reprogram some stuff first. Then it has you turn the truck off and download drivers. When you do this, the file you download installs the driver installer but not the driver itself. Navigate to C:\program files (x86)\sync drivers installer to find the actual installers. There should be an install.bat file somewhere in that folder. Run that before continuing in FDRS. Once you do that follow the prompts. For my truck I needed to use both the USB male-male AND ethernet adapters to recover the truck. Side note, you CAN'T use one of those combined USB hubs with ethernet- the APIM will reject it with an error. Once it is done it does some type of configuration on the APIM which I had to retry once or twice. Once the procedure finally finished I had a sync version and the update buttons were no longer greyed out. From there I ran the USB APIM updates and have since gotten myself to 21281. Let me know if you have questions, this should help those driving around with USB sticks in their truck hoping they will update at some point...
