FORScan Changes Made; 6.8 Update Fail - Coincidence?

[FirstFord]

6.8 installation failed same day that I attempted FORScan changes for Glare-Free, which also didn't work (I got the "Check headlights / see manual" message). Coincidence??? This is the FIRST failed OTA that I have experienced (and the battery was on a charger, as usual). I know that the issues with Glare-Free are a separate matter, but I can't help but wonder if the changed FORScan values in the AS BUILT perhaps conflicted with 6.8???

- Should I just leave everything alone, and let 6.8 continually try to install? (I read one post where a member went through numerous failures before it finally loaded), or
- Should I restore the backed up original values prior to the Glare-Free FORScan change, and wait for the next 6.8 install attempt?

It seems to me that if I'm going to restore the AS BUILT files, then I need to do that right away. Suggestions / thoughts?

EDIT: I have learned in other threads/posts of some of the issues and resolutions that have occurred when enabling Glare-Free through FORScan, and consider the Glare-Free issue that I am experiencing a separate topic that can stand on its own. My much larger concern is getting the 6.8 OTA update, and to that end, should I remove Glare-Free, i.e., restore the original FORScan values? Or should I just wait it out?

Sponsored

 

[tbinmd]

I have glare free enabled and haven't had issue with the OTA updates.
If your changes for glare free gave you the error you might want to roll them back, you have something missing or incorrect.

 

[FirstFord]

If you changes for glare free gave you the error you might want to roll them back, you have something missing or incorrect.

Your reply prompted me to edit my original post. There are some known issues - with some trucks when Glare-Free in enabled through FORScan, as well as proposed resolutions . My focus is not so much on whether or not Glare-Free is operating correctly (to me, that's a different topic), but rather if the FORScan changes I made relative to Glare-Free contributed to the 6.8 update installation failure.

 

[rugedraw]

The reason the update failed is below. The VICM did not successfully put your truck into inhibit mode for the update install and it failed. I have never seen the "original hash mismatch" verbiage before and do not know what that means. I have seen updates fail many times due to VICM/API errors but not sure what the that term means.

Vehicle Inhibit Error

OTAM_E1010

January 10, 2024 3:15 PM

January 10, 2024 4:15 PM

"errorCode":"OriginalHashMismatch(22)""errorCategory":"VICM_API_ERROR_CATEGORY(11)"

 

[FirstFord]

Wow! Great information, but I'm not quite sure what to do with it.... Do you recommend I restore the original AS BUILT values?

 

[FirstFord]

And the fact that you have not seen that error before is really giving me concerns....

 

[FirstFord]

The reason the update failed is below. The VICM did not successfully put your truck into inhibit mode for the update install and it failed. I have never seen the "original hash mismatch" verbiage before and do not know what that means. I have seen updates fail many times due to VICM/API errors but not sure what the that term means.

I was in such a hurry to reply, I forgot to tag you on either post! Haste makes waste!

 

[rugedraw]

No, you don't need to do anything but wait for them to resend it. From my understanding, the worst that will happen is that the update will revert the IPC changes you made to enable glare-free and you'd have to go back and change it again. Eventually, the FORScan changes you made will become your as-built data when your truck syncs up with the server and future updates sent to you will have the changes you made built into the update already.

 

[FirstFord]

No, you don't need to do anything but wait for them to resend it. From my understanding, the worst that will happen is that the update will revert the IPC changes you made to enable glare-free and you'd have to go back and change it again. Eventually, the FORScan changes you made will become your as-built data when your truck syncs up with the server and future updates sent to you will have the changes you made built into the update already.

Thanks, Javier - you talked me down off the ledge....

 

[fordtruckman2003]

The reason the update failed is below. The VICM did not successfully put your truck into inhibit mode for the update install and it failed. I have never seen the "original hash mismatch" verbiage before and do not know what that means. I have seen updates fail many times due to VICM/API errors but not sure what the that term means.

Vehicle Inhibit Error

OTAM_E1010

January 10, 2024 3:15 PM

January 10, 2024 4:15 PM

"errorCode":"OriginalHashMismatch(22)""errorCategory":"VICM_API_ERROR_CATEGORY(11)"

Likely file hash, so just some speculation on what it is doing.
It downloaded files, generated hash and compared to what it is supposed to have, that failed to pass because somehow file was corrupted when it downloaded.
I would think it would do a check on files before inhibit process starts but perhaps not.

 

[FirstFord]

The reason the update failed is below. The VICM did not successfully put your truck into inhibit mode for the update install and it failed. I have never seen the "original hash mismatch" verbiage before and do not know what that means. I have seen updates fail many times due to VICM/API errors but not sure what the that term means.


Vehicle Inhibit ErrorOTAM_E1010January 10, 2024 3:15 PMJanuary 10, 2024 4:15 PM"errorCode":"OriginalHashMismatch(22)""errorCategory":"VICM_API_ERROR_CATEGORY(11)"

No, you don't need to do anything but wait for them to resend it. From my understanding, the worst that will happen is that the update will revert the IPC changes you made to enable glare-free and you'd have to go back and change it again. Eventually, the FORScan changes you made will become your as-built data when your truck syncs up with the server and future updates sent to you will have the changes you made built into the update already.

I did a number of FORScan changes at once, including the Glare Free. In retrospect, I've decided that probably wasn't the smartest thing to do. I let my new-found confidence overrun my intelligence. Since your post offering advice to me, I have learned that there are other issues with Glare Free and these are still being sorted out. That coupled with one or two of the other changes that I made I wasn't all that happy with, and I decided to reinstate the factory original AS BUILTs. My plan is after the 6.8 Update goes through, I will go back and perform those FORScan changes that I did like and saw value to.

You have stated many times that there is no way to know when anyone will get an OTA, or what the scheduling parameters are. That being said, I would think that after my 6.8 update failed, that it would try again the next night, or night after, or.... - trying to complete an installation attempt. But it has been a week, and no bueno. Does that mean that my failed update was thrown back in the general hopper of scheduling, and it could be another month, maybe two, before there is another attempt?

 

[rugedraw]

I did a number of FORScan changes at once, including the Glare Free. In retrospect, I've decided that probably wasn't the smartest thing to do. I let my new-found confidence overrun my intelligence. Since your post offering advice to me, I have learned that there are other issues with Glare Free and these are still being sorted out. That coupled with one or two of the other changes that I made I wasn't all that happy with, and I decided to reinstate the factory original AS BUILTs. My plan is after the 6.8 Update goes through, I will go back and perform those FORScan changes that I did like and saw value to.

You have stated many times that there is no way to know when anyone will get an OTA, or what the scheduling parameters are. That being said, I would think that after my 6.8 update failed, that it would try again the next night, or night after, or.... - trying to complete an installation attempt. But it has been a week, and no bueno. Does that mean that my failed update was thrown back in the general hopper of scheduling, and it could be another month, maybe two, before there is another attempt?

I would need to check the OTA dashboard of your truck, but PTS is down at this time.

 

[FirstFord]

I would need to check the OTA dashboard of your truck, but PTS is down at this time.

I'll be eager to learn of your findings.

 

[rugedraw]

I'll be eager to learn of your findings.

OTA failed to an error I only started seeing recently. Not sure what it means. Battery seems to be ok, but it failed to go into inhibit mode.

 

[FirstFord]

OTA failed to an error I only started seeing recently. Not sure what it means. Battery seems to be ok, but it failed to go into inhibit mode.

So there's no way of knowing when/if another attempt will be made to install 6.8?

Sponsored