FORScan Changes Made; 6.8 Update Fail - Coincidence?

[rugedraw]

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

When? No. If? Yes.

The update didn't fail because of anything you did. The update situation is a circus right now.

Sponsored

 

[FirstFord]

When? No. If? Yes.

The update didn't fail because of anything you did. The update situation is a circus right now.

Thanks. I guess I was ultimately figuring out if I should not do anything and just be patient (ha!), or if I would need to go the FDRS route. But it sounds like you are reasonably confident that despite the weird, inexplicable update failure, that OTA will ultimately prevail....

 

[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)"

@rugedraw , I was curious as to if you have learned any more about this newer(?) failed update attempt error message...

The 6.8 failed update attempt was on 1/10, and there have been no further attempts to update.

 

[rugedraw]

@rugedraw , I was curious as to if you have learned any more about this newer(?) failed update attempt error message...

The 6.8 failed update attempt was on 1/10, and there have been no further attempts to update.

I googled it and it seems like file mismatch or an interruption of the file verification process causes an error in the values of the files. I'm not a software programmer, so I can't really explain because I don't fully understand it myself. What I can tell you is that you did nothing wrong and there is nothing you could have done different. The problem lays somewhere in the deployment process of the OTA.

 

[FirstFord]

I googled it and it seems like file mismatch or an interruption of the file verification process causes an error in the values of the files. I'm not a software programmer, so I can't really explain because I don't fully understand it myself. What I can tell you is that you did nothing wrong and there is nothing you could have done different. The problem lays somewhere in the deployment process of the OTA.

Understood. Thanks.

So, does that mean Mongoose/FDRS is the next step, to resolve the issue? (I'm asking out of ignorance.)

 

[mrblonde]

6.8 claims to enhance center display. I got 6.8 couple days ago and see no change in the center display.

 

[rugedraw]

Understood. Thanks.

So, does that mean Mongoose/FDRS is the next step, to resolve the issue? (I'm asking out of ignorance.)

FDRS/Mongoose will free you from having to wait for the OTA process to get to you. Or you can continue to wait for the OTA. Up to you.

6.8 claims to enhance center display. I got 6.8 couple days ago and see no change in the center display.

It adds animations for the enhanced features of bluecruise that have not been released yet. Nothing will stand out otherwise.

 

[FirstFord]

6.8 claims to enhance center display. I got 6.8 couple days ago and see no change in the center display.

I am not obsessing over 6.8 per se, it is the larger picture that has my attention. My logic (albeit possibly faulty) is that if 6.8 needs to load before I get any other updates in the future, of which, some may be very useful/desirable.

 

[FirstFord]

FDRS/Mongoose will free you from having to wait for the OTA process to get to you. Or you can continue to wait for the OTA. Up to you.

Patience..... sometimes a challenge! But, I'll give it a try. Can you "ballpark" the length of time to wait before it becomes apparent that OTA is not going to work and I need to shift strategies to using FDRS?

 

[rugedraw]

You aren't so far behind where I think you need to be concerned. Maybe once the new version of Bluecruise comes out (if you have BC), it may be worth doing it. Right now, this IPC update doesn't give you anything tangible you can use. I would just wait for something to come out that would make a positive and impactful difference to your ownership experience before giving any of this update stuff any more thought. You aren't missing out on anything, so there is no need for FOMO.

 

[PatchManager]

I have glare free enable, which I did many months ago, but as others have mentioned, that may not be an issue. A week ago, I received a notice that my truck was going to install 6.8 the following day at my scheduled time. Since I was done using my truck for a few hours, I went ahead and requested that it install it now. When I went back out to check on it well after it would have completed, it said it failed. This was the first time I have ever seen an OTA fail with my truck. I drove home for about 30 minutes, so I assumed the batter would have been good and charged, and initiated the install of the OTA again. It failed again. I decided I was going to let it do what it had planned and let it install at the scheduled time the following morning. It successfully installed.

If I were you, and I made a change with Forscan that caused an error that wouldn't clear, and would undo that change. I would verify the error goes away or can be reset, and try again. I wouldn't leave a change in my truck that caused an error regardless of the OTA status. If others have noted that his error is common, maybe I would leave it, but still probably no.

 

[FirstFord]

You aren't so far behind where I think you need to be concerned. Maybe once the new version of Bluecruise comes out (if you have BC), it may be worth doing it. Right now, this IPC update doesn't give you anything tangible you can use. I would just wait for something to come out that would make a positive and impactful difference to your ownership experience before giving any of this update stuff any more thought. You aren't missing out on anything, so there is no need for FOMO.

Thanks again, Javier. I very much appreciate your counsel and guidance! I will put extra effort into be being patient. I do NOT have BC, so as you pointed out, there is nothing particularly noteworthy for me in 6.8. My larger concern was i didn't want this update failure to hinder future OTA updates still to come.

 

[FirstFord]

I have glare free enable, which I did many months ago, but as others have mentioned, that may not be an issue. A week ago, I received a notice that my truck was going to install 6.8 the following day at my scheduled time. Since I was done using my truck for a few hours, I went ahead and requested that it install it now. When I went back out to check on it well after it would have completed, it said it failed. This was the first time I have ever seen an OTA fail with my truck. I drove home for about 30 minutes, so I assumed the batter would have been good and charged, and initiated the install of the OTA again. It failed again.

That is almost a carbon copy of my experience - except that I saw no evidence of additional installation attempts, and except that you ultimately had success.

I went against advice (advice: don't change anything back; just be patient and let it try again), and went into FORScan and removed all of the changes I made and reinstalled the original ASBUILT values from my back up. No effect. Now, 2 two weeks later, still no success or signs of installation attempts, yesterday I returned to FORScan and put some of my changes back in - but only 3 - only the ones that addressed the behaviors that were REALLY bugging me, and left all the others out (including Glare-Free).

 

[shalabama]

I have Glare free enabled and didn’t have an issue installing 6.8 on Monday. Took a drive to get my morning coffee, came back and an hour later the alarm started going off.

Walked out to the truck and there was 6.8 installed. I always put the parking brake on in my driveway for what its worth.

Just curious…..are you saying your horn alarm sounded as a result of receiving 6.8 OTA? Not sure if I’ve ever heard of that happening.

 

[fordtruckman2003]

Updates will keep retrying over and over if they do fail. Nothing to worry about and what does not succeed now could work next time around. No features to be missing out on so nothing to worry about.

Sponsored