BMW i5 software update issue (2024–2025)

BMW i5 · 2024–2025 · all trims

Reported symptoms

iDrive infotainment screen freezes, reboots unexpectedly, or becomes unresponsive during driving
DC fast charging session refuses to initiate, terminates early, or sustains charge rate well below specification
Driver-assist features inactive, intermittent, or behaving inconsistently
Cluster, head-up display, or driver-information display flickering, partially blank, or showing intermittent warnings
BMW Connected app reports vehicle errors, shows feature inconsistencies, or reports vehicle as offline
M60 variant: performance mode behavior inconsistent or fails to engage as expected

Questions to ask

Pose these to the service advisor at intake. Request answers in writing or via email.

How many open recall and software campaigns currently apply to VIN (Vehicle Identification Number) [VIN]?
What software versions are currently installed on the iDrive, BMS (Battery Management System), and other relevant modules, and which versions correspond to the closed remedies for each open campaign?
If VIN [VIN] is an M60 variant, are there any campaigns specific to the dual-motor configuration that should be addressed?
Has the BMW dealer confirmed in writing that any campaign applied to VIN [VIN] is i5-specific (G60 chassis), rather than an i4 (G26 chassis) campaign mistakenly extended?
Is each remedy delivered via OTA (Over-the-Air software update), dealer-side flash, or hardware adjustment?
Will all open campaigns be addressed in a single visit, or are sequential visits required?

Documents to request

Each item should be received in writing before authorizing repair work.

Diagnostic report listing all stored, pending, and historical fault codes from the affected modules
Repair order with technician notes, including a list of every campaign reference number addressed during the visit, with explicit chassis identification (G60)
Written confirmation of software versions installed before and after the visit on each affected module
Written confirmation of which campaigns are now closed for VIN [VIN] following the visit
Documentation of any M60-specific procedures applied, if applicable to the vehicle configuration

Pre-service evidence

Capture before drop-off. Once the vehicle leaves your possession, proving prior condition becomes significantly harder.

Screenshot or video-record any iDrive, display, charging, or driver-assist defects at the time they occur
Note specific incidents — system reboots, charging failures, driver-assist anomalies, ambient conditions — with dates
Save all BMW correspondence regarding software updates, recalls, or feature delivery timelines
Screenshot the BMW Connected app status pages over time, showing any reported errors
Save records from third-party charging network apps showing failed session details
Note odometer reading at drop-off and at pickup

Service advisor interaction

Operational notes specific to the conversation at the service desk.

Record the full name of the service advisor and the technician performing the work
The i5 (G60 chassis) is distinct from the i4 (G26 chassis) despite both being BMW EVs of similar generation. Service campaigns and software updates issued for one chassis do not automatically apply to the other. Verify in writing that any campaign reference is i5-specific.
Multi-campaign software situations are particularly susceptible to incomplete documentation. A general 'iDrive updated' note without enumerated campaign references creates ambiguity about which specific campaigns are closed.
If the advisor states verbally that an OTA update has been delivered for VIN [VIN] but the affected behavior remains unchanged, request written documentation of the diagnostic steps before any release

Repair authorization

Cautions before signing.

Recall and software campaign work is performed at no charge to the owner; do not authorize any charge for parts or labor associated with these campaigns
If a diagnostic fee is presented, request written confirmation of whether the fee is refundable if the issue is later determined to be recall- or campaign-covered
If high-voltage component replacement is quoted, request written warranty classification before signing the repair authorization
Repair authorization signatures often include language permitting additional related work — read the document and decline blanket additional work in advance

Post-service verification

Complete before leaving the service location. Issues that surface after departure are operationally harder to attribute to the visit.

Verify the iDrive system functions normally without unexpected freezes or reboots during a short test drive
Conduct a verified DC fast charging session at a CCS-compatible fast charger before traveling more than a short distance from the dealership
Test driver-assist features to confirm correct operation
If the vehicle is an M60 variant, test performance mode engagement and behavior
Confirm no warning messages or system errors on the cluster, head-up display, or BMW Connected app after a full ignition cycle
Confirm the repair order matches the work performed and references the correct campaigns

Email templates

Documentation-focused templates for service correspondence. Tap copy to use. Subject and body are kept verbatim — paste them as-is into your email client.

pre-service inquiry

to: dealer service

Service inquiry — BMW i5 software, request for written campaign list

Service Department, I am scheduling my [YEAR] BMW i5, VIN [VIN] (G60 chassis), for service. Symptoms observed: [LIST SYMPTOMS WITH DATES]. Before the visit, I am requesting written confirmation of the following: 1. A list of every open recall and service campaign currently applying to VIN [VIN], including the campaign reference number and a brief description of the function addressed by each. 2. Whether VIN [VIN] is an M60 variant, and if so, any campaigns specific to that configuration. 3. Whether all open campaigns can be addressed in a single visit, or whether sequential visits are required. 4. The fee structure, including any diagnostic charges and conditions under which they apply. Please reply to this email so the planned scope is on record. Thank you, [NAME]

documentation request

to: dealer service

Documentation request — BMW i5 service on [DATE], VIN [VIN]

Service Department, Following the service performed on [DATE] for VIN [VIN], I am requesting the following documents for my ownership records: 1. The full diagnostic report including all stored, pending, and historical fault codes. 2. The repair order listing every campaign reference number addressed during this visit, with explicit chassis identification (G60). 3. Written confirmation of the software versions installed on each affected module before and after the visit. 4. Written confirmation of which campaigns are now closed for this VIN and which remain open. These documents form part of the vehicle's service record and are operationally important. Please reply to this email at your convenience. Thank you, [NAME]

Warranty notes

BMW i5 components are covered under BMW's New Vehicle Limited Warranty and the high-voltage battery component warranty (8 years / 100,000 miles in most US markets). Coverage period and conditions for VIN [VIN] should be confirmed in writing.
Recall remedies, when issued, are performed at no charge to the owner regardless of vehicle age, mileage, or warranty status.
Software-only remedies do not consume warranty time; the standard warranty period continues independently of OTA or dealer-side software work.
Repairs performed under goodwill rather than warranty do not extend the warranty period. Confirm in writing which classification applies.

Observational patterns

The BMW i5 is on the G60 5-Series chassis, distinct from the i4's G26 4-Series Gran Coupe chassis. While both share elements of BMW's EV technology, service campaigns and software stacks can differ between chassis. Service interactions can conflate them, particularly because both are recent BMW EV sedans.

BMW's iDrive software has evolved significantly during this production window. The current software version, and which campaign closed which specific issue, is operationally important documentation.

Multi-campaign software situations are particularly susceptible to incomplete documentation if the repair order does not enumerate which specific campaigns were closed during a visit.

OTA delivery does not always produce a corresponding entry in the dealer-side service record. The closure of a recall delivered over the air requires explicit documentation through the dealer system.

All rated vehicles