I'll let you know when my APIM update appears as we seem to be on a similar timeline.Yeah several times. No luck here.
If anyone is curious for a benchmark, it took only 10 minutes to copy the 6GB of files for this APIM update to this drive.I use the 64GB version and haven't had one problem. Love that drive.
Took just under 3 minutes copying manually with windows explorer.If anyone is curious for a benchmark, it took only 10 minutes to copy the 6GB of files for this APIM update to this drive.
Its a CA thing....EV Emissions....Is this a new setting in the new UI? What does it mean?![]()
I didn't want the extra variable of needing to make sure I copied over only the correct files doing it manuallyTook just under 3 minutes copying manually with windows explorer.
![]()
It slowed down some, but still faster than letting FDRS do it.
Do you download the file to your hard drive then transfer it to the flash card?Took just under 3 minutes copying manually with windows explorer.
![]()
It slowed down some, but still faster than letting FDRS do it.
How did you reset the PCM?So now that we're all getting the ball rolling....It was a naughty PCM update that was keeping the GWM from showing up. I'm told that in addition to whatever dependency issue was created by doing the PCM update (at the time I did it there was no GWM in my list) the PCM was not completely 'reporting' as well, which could have compounded the problem.
I asked somebody on another forum to check something out for me and the result was a 'reset' of my PCM reported version to a previous iteration.
Which made the GWM....and the PCM (again) show up as updates in my list.
![]()
I was advised to do an offline download of the GWM software (no network scan), and then only plug it in afterward...and to do a PMI (and answer "No" to the question about if the original module is installed).
That worked like a charm and after the completion of the GWM update (GWM "-LAD" revision) and the network scan I was bestowed with the precious Sync 640 APIM update, and the naughty PCM update had disappeared from the list (because it was actually already installed).
![]()
Afterward, another GWM showed up and all the packages in that update still showed as "-LAD" except the F188 which flipped over to "-LAE".
All good...another Sync crisis put to rest.
I’m with you Tony.I'll let you know when my APIM update appears as we seem to be on a similar timeline.
I didn't. I asked a forum member on the F-150 forum to assist and that's what he came up with. He's a certified module whisperer.How did you reset the PCM?
When the USB drive is created by FDRS there is one file that is the .cer file. That is the certificate that the car recognizes and allows the files to be updated. The other file is written to the USB drive when the update is complete. That second file is the reason we used to have to put the USB drive back into the computer so FDRS could read and validate that the update completed sucessfully. Now FDRS just does it using the Mongoose cable instead.Looking on the data on my USB stick for the GWM, i noticed that there are 2 files that are matched to my VIN number. I was wondering if these files stay the same in a newer update ?
The manifest and json file are both encrypted so nu luck in figuring it out manually.