[sigmabody]

Originally Posted by LDT

I find it hard to believe that a software update could brick the car.

See my thread on the topic, for example: this update bricked my X5 (had to tow to dealership, and they had to flash 03/2024.25 onto it to fix it.

See also (importantly) that the CA at the dealership told me that if my vehicle wasn't under warranty, and I accepted an OTA update which bricked it, BMW would not cover the repair costs. So under no circumstances should you ever take an OTA update from BMW when not under warranty.

[Ibiza]

Originally Posted by sigmabody

See my thread on the topic, for example: this update bricked my X5 (had to tow to dealership, and they had to flash 03/2024.25 onto it to fix it.

See also (importantly) that the CA at the dealership told me that if my vehicle wasn't under warranty, and I accepted an OTA update which bricked it, BMW would not cover the repair costs. So under no circumstances should you ever take an OTA update from BMW when not under warranty.

An other reason to lease for 3 yrs to stay under warranty.

[Dochere2]

Originally Posted by sigmabody

...that the CA at the dealership told me that if my vehicle wasn't under warranty, and I accepted an OTA update which bricked it, BMW would not cover the repair costs...

This is unexpected, good to know. I guess I'm not surprised. I'd expect BMW to own up to issues resulting from OTA's. It's their hardware and their software after all, they should ultimately be responsible for proper function of their product. I'm pretty sure our involvement entails hitting "yes" once or twice during install. If you can't guarantee it works, don't release it. I know that's not how it goes but it seems like it should. Regardless, this is disappointing.

On a side note, they reflashed ours this afternoon. They wanted to keep it overnight. We should know more tomorrow, possibly pick it up if all's well.

They mentioned that the data showed the car was running while parked for 131 minutes at some point. We never walked up to the car running and I can't fathom where/when this might have occurred. I'm interested to find out more on this. There was one episode where I walked into the garage a few hours after the car was parked and the led's front/back were on, but it did not appear that the car was on... Though on doesn't mean what it used to mean so maybe that was the time? The car turns off as soon as the door opens. I know it will come back on for a few minutes if a door is opened again and not started. I'm dumbfounded that it could sit in an "on" state, on its own.

Final thought, I do not have the light animation package. After describing the light behavior while following the tow truck to the dealer, the tech said that the animation I observed was one of the animations that is included in the package. How could that be? Again, hoping for more answers tomorrow.

[rmorin1249]

Originally Posted by sigmabody

See my thread on the topic, for example: this update bricked my X5 (had to tow to dealership, and they had to flash 03/2024.25 onto it to fix it.

See also (importantly) that the CA at the dealership told me that if my vehicle wasn't under warranty, and I accepted an OTA update which bricked it, BMW would not cover the repair costs. So under no circumstances should you ever take an OTA update from BMW when not under warranty.

If true, I call FOUL! This is ridiculous. So glad my X5 is refusing to install OTA updates. It runs fine with no issues and hasn't updated since 2022.

[eluded]

This is also true with iPhones, Samsung TVs, and probably everything that gets a SW/HW update outside of warranty. In times like this I miss carburetors.

Originally Posted by Dochere2

This is unexpected, good to know. I guess I'm not surprised. I'd expect BMW to own up to issues resulting from OTA's...

[Dochere2]

Well, car's back in the garage. They updated the software to the 03/2024.42. 60 miles of driving after we picked it up with some stop and go and a few power downs. Nothing to note, seems fine. Though it seemed fine the first 1900 miles too, lol.

The only thing I noticed, and my evidence is anecdotal at best, is the start stop seems smoother. Turning off pretty much seems the same but turning back on was different. It doesn't seem to be as rough and seems more consistent. It also seemed to turn off faster at a stop, more frequently in bumper to bumper and smoother at those times where it turned off when it really shouldn't have and turned right back on. Anticipation turn on seemed the same.

I'll revive this thread if there's a change, repeat, etc.