Sponsored
Ldkburra
Well-known member
Guys I'm afraid I need done help. I'm working on the FDRS updates today for my first time. Things have been going well until I got to the APIM module. I followed the instructions and things were going well but at the end it showed that some of the files failed. I started the process over by re formatting the thumb drive and running fdrs to load the files onto the thumb drive. When instructed to move the thumb drive to the truck, the truck read the drive and stated that it had already been completed. And shows no signs of reading or progress. I'm not sure where to go from here. The computer is on the screen shown. Any input on what to do from here?
Ldkburra
Well-known member
I am thinking I made a mistake after placing the thumb drive in the truck and when prompted to turn the engine off but have the ignition on, I had the doors open and only pushed the ignition button once to turn the engine off, thinking it would leave the ignition on (as the screen remained on briefly). But I'm not positive.
The usb updates are simple
Insert usb
Wait for update detected
Restart required
TURN TRUCK OFF
Open door and leave usb in truck
Wait 10 min
Start truck and wait for update success message
Remove usb
Ldkburra
Well-known member
Yes, I already feel stupid, yes the directions are very plain and straight forward. But I got a "failed" message so tried following the prompts to "Re-try". I got the message then that the update has already been completed. However, I saw as the first attempt was finishing up that multiple files failed. That is why I tried again and didn't make any progress and am now stuck on the shown screen. I'm really sorry that I wasn't able to follow the simple process, yes I do feel stupid. Do you suggest I just click on "yes" it was installed correctly and try to move on with the remaining updates in fdrs? Is there a way to go back and re-do the APIM module later as I am sure there are files that failed? Sorry.....
Sponsored
iF THE VERIFICATION FAILED always REVERIFY.
The failure is typically from starting the verification too soon after turning on the ignition.
The failure is typically from starting the verification too soon after turning on the ignition.
Ldkburra
Well-known member
Thank you for reaching out rugedraw! I think I am making progress. I'm finding that each time there is an update that requires the USB drive, despite following the directions and waiting at least 15-20 minutes with the truck off and the key fob far away from the truck, when I turn the truck back on I never get the "update completed" message. But I have to click on either yes or no at the bottom of the page in order to move on. The first time I clicked "no" hoping it would Re-try the process, but after re-inserting the USB drive into the truck, I got the message "update has already been completed". On the subsequent updates that require the USB drive, even though I never receive an "update completed" message, I just click "yes" at the bottom of the page asking if the update was successful, and it appears to me that it completes the update and moves me on the the FDRS menu to proceed with other updates. I'm heading out now to see if I can get them all finished up. ?But I sure do appreciate you reaching out. Thank you!
rugedraw
Well-known member
@Ldkburra I was updating a Lightning last week and ran into a config error at the end of an APIM update. I reached out to Jesse because the APIM update was still showing in FDRS and if I tried to run it, it told me the update was already applied. I restarted FDRS and no change. I then restarted the laptop itself and when I did a network scan, the APIM update was gone from FDRS and a TCU update popped up in its place.
As Jesse mentioned: When prompted to turn on the ignition, give it a few second before you click "ok" in FDRS to ensure you allow enough time for everything to boot up before FDRS starts to check things.
As Jesse mentioned: When prompted to turn on the ignition, give it a few second before you click "ok" in FDRS to ensure you allow enough time for everything to boot up before FDRS starts to check things.
Sponsored
Ldkburra
Well-known member
Well I now have all modules cleared from the right hand of the screen, but on the left hand side, the SCCM is orange, and I have quite a few that are gray. It's there anything I need to be concerned with about that, or anything I need to do? Thanks!
rugedraw
Well-known member
Also, what Sync version does your touchscreen say it is on?
mau47
Well-known member
Anyone have any ideas on how I can get my SCCM updated?
I tried updating it on 2/2 through FDRS while I had complimentary access via a bug in 39.6.2 and it failed due to a manifest issue (all of the other modules I ran updated fine) at the time I didn't really have a chance to dive in any further and then it slipped off my radar.
Now I have gotten the update over the air and it is failing with the same or very similar error. Everything in the truck seems to be working fine, only thing I can think may play a part is I did replace the SCCM when I added the heated wheel. Everything seems to functional, but maybe theres a step I missed somewhere in the programming? I am happy to pay for a FDRS license if theres a procedure I can do to get it properly reset/updated.
I am not too worried about this particular update I don't want to cause issues down the line if we can't get this one installed.
I tried updating it on 2/2 through FDRS while I had complimentary access via a bug in 39.6.2 and it failed due to a manifest issue (all of the other modules I ran updated fine) at the time I didn't really have a chance to dive in any further and then it slipped off my radar.
Now I have gotten the update over the air and it is failing with the same or very similar error. Everything in the truck seems to be working fine, only thing I can think may play a part is I did replace the SCCM when I added the heated wheel. Everything seems to functional, but maybe theres a step I missed somewhere in the programming? I am happy to pay for a FDRS license if theres a procedure I can do to get it properly reset/updated.
I am not too worried about this particular update I don't want to cause issues down the line if we can't get this one installed.
Sponsored
