Completely locked out 😭

[Gungrave223]

Yes, engineers are working on getting the fix out soon as usual.

Here's a workaround until then: Anti-Lockout Solution for 2023s

The fact that, that's a thing is hilarious to me ?

Sponsored

 

[Mike G]

Surprised there isn't a poll on this by now.

Have you been locked out of your 23 or 24 model while the 12V battery was still good?

After your car was 'repaired' by the dealer did the lockout happen again?

I'm planning to do the string setup, but it occurred to me that maybe I ought to just go out to the car this morning and simply disconnect my negative battery terminal for 10 minutes and then reattach it as a preemptive measure to reset all the modules. If this glitch doesn't reoccur after a 12V battery disconnect and reconnect then maybe that's all we need to do?

 

[garyd9]

I'm planning to do the string setup, but it occurred to me that maybe I ought to just go out to the car this morning and simply disconnect my negative battery terminal for 10 minutes and then reattach it as a preemptive measure to reset all the modules. If this glitch doesn't reoccur after a 12V battery disconnect and reconnect then maybe that's all we need to do?

My opinion is that it's unlikely to prevent the issue, though it may reduce the chances of it happening.

I kind of look at this issue like an old laptop computer running Windows that BSOD's every now and then. Power cycling the machine once in a while might make the BSOD's less frequent, but it's not actually fixing the cause of the blue screens. It's just resetting the odds.

I'm starting to think it might be better to run the string, but also leave an OBDII dongle plugged in. Then if/when it happen, try to query the various buses/modules. Figure out which, if any, buses are working. Which modules, if any, respond, and so on. This information might be useful to the community (or Ford) to find a better workaround and/or a root cause. (Some module resets can be done with Forscan and don't require FDRS.)

Finally, when all the tests are done, yank the string to unlock and eventually "reboot" the car by unplugging it and plugging it back in.

No, it doesn't immediately help. In fact, it's unlikely that my idea would have any benefit whatsoever and just waste time. On the other hand, there's a small chance that some discovery could be made that would help some owners, and help Ford (if they are paying attention) pinpoint the issue.

 

[Mike G]

My opinion is that it's unlikely to prevent the issue, though it may reduce the chances of it happening.

I kind of look at this issue like an old laptop computer running Windows that BSOD's every now and then. Power cycling the machine once in a while might make the BSOD's less frequent, but it's not actually fixing the cause of the blue screens. It's just resetting the odds.

I'm starting to think it might be better to run the string, but also leave an OBDII dongle plugged in. Then if/when it happen, try to query the various buses/modules. Figure out which, if any, buses are working. Which modules, if any, respond, and so on. This information might be useful to the community (or Ford) to find a better workaround and/or a root cause. (Some module resets can be done with Forscan and don't require FDRS.)

Finally, when all the tests are done, yank the string to unlock and eventually "reboot" the car by unplugging it and plugging it back in.

No, it doesn't immediately help. In fact, it's unlikely that my idea would have any benefit whatsoever and just waste time. On the other hand, there's a small chance that some discovery could be made that would help some owners, and help Ford (if they are paying attention) pinpoint the issue.

But once again...has anybody that has gotten locked out reported that they got locked out again after the car was repaired?

 

[garyd9]

But once again...has anybody that has gotten locked out reported that they got locked out again after the car was repaired?

Not that I'm aware of. (I've been trying to pay attention to the reports.)

 

[Space_Pony]

It would also be interesting to know why the 23-24 models are affected and not 21-22 models. Could there be different hardware with the newer cars and compatibility issues?

 

[Mike G]

It would also be interesting to know why the 23-24 models are affected and not 21-22 models. Could there be different hardware with the newer cars and compatibility issues?

Or different software...which is more likely.

 

[Jerrytball]

Oh look, wonder when they'll look at the logs and remove BC1.3+ again. I'm sorry for anyone in '23 right now.

I think I got the same blue cruise in my car that it came with originally 1.2. My car has been fine. Knock on wood pull on string lol

 

[zvez]

Not that I'm aware of. (I've been trying to pay attention to the reports.)

has anyone figured out which OTA is causing it? I think the speculation is that it's the one to ease access to the car but haven't seen anything definitive

 

[azerik]

If it is the door zone one it's funny/not funny that the 21's got it fine.

 

[ReverendPete]

Didn't at least one of the reported lock-out victims actually have this happen out in a parking lot when he was running errands? Does that mean that it might have been a non-inhibit OTA? I was under the impression that when you set a schedule for OTA updates, it is only applying to the ones that inhibit vehicle use, and that other OTA updates might happen at other times during the day. Or am I wrong in that? I suppose it's also possible that the person might not have set up and OTA schedule...

My '23.0 is parked in my garage every night, and I have just been leaving the window down, so that if I get the lockout problem, I will be able to get into my frunk and disconnect the LVB to reset it. (And I have been getting the flurry of updates that others have reported, but don't believe that I've gotten the 24-PU0301-BLM-PE update yet, which I believe others have pinpointed as the potential culprit.)

But should I be worried about this potentially happening when I'm out and about, instead of in my garage, where I keep the window rolled down?

 

[garyd9]

Didn't at least one of the reported lock-out victims actually have this happen out in a parking lot when he was running errands? Does that mean that it might have been a non-inhibit OTA?

For some reason, people keep thinking it only happens during the process of getting an OTA. That does not appear to be the case.

At this point, I'm tired to trying to correct each and every person who assumes it's happening during an inhibiting OTA or other OTA.

 

[ReverendPete]

For some reason, people keep thinking it only happens during the process of getting an OTA. That does not appear to be the case.

Thanks. All the discussion I had seen seemed to be pointing toward it being related to an OTA update, which made sense to me. If it isn't part of receiving an OTA, then what else could it be? Or are you saying that it maybe happens sometimes after an OTA, but not as part of the OTA installation itself?

 

[garyd9]

Thanks. All the discussion I had seen seemed to be pointing toward it being related to an OTA update, which made sense to me. If it isn't part of receiving an OTA, then what else could it be? Or are you saying that it maybe happens sometimes after an OTA, but not as part of the OTA installation itself?

This is the "best guess" right now:

https://www.macheforum.com/site/threads/completely-locked-out-😭.37460/post-826910

It may be that a module is causing the problem, but it doesn't seem to be the update process...

 

[Mach-Lee]

I'm planning to do the string setup, but it occurred to me that maybe I ought to just go out to the car this morning and simply disconnect my negative battery terminal for 10 minutes and then reattach it as a preemptive measure to reset all the modules. If this glitch doesn't reoccur after a 12V battery disconnect and reconnect then maybe that's all we need to do?

That's what I recommend as a preemptive fix Mike. Hopefully that prevents the issue but I have no data.

Sponsored