BMW NBT EVO Boot Loop
The NBT EVO — the head unit behind iDrive 5 and 6 on 2016-era onwards BMWs — is the unit we see most often in boot loops. The failure combines two things: these units run software-heavy features that have been updated many times over the years, and they are now at the age where internal storage wear makes those repeated write cycles take their toll.
The result is the familiar pattern: an update that doesn't complete cleanly, or a unit that one morning cycles through start-up and never settles. Recovery is often possible — the route depends on whether the storage still holds what's written to it.
Common Symptoms
- NBT EVO cycling through start-up without reaching the menu
- Boot loop appearing after a failed or interrupted update
- Increasingly slow or unstable behaviour in the weeks beforehand
- Freezes on the BMW logo, or flickering between screens mid-boot
Possible Causes
- Corrupted software from interrupted or failed updates
- Ageing internal storage no longer reliably holding its software
- Failed programming attempts
- Power interruptions during update processes
How We Diagnose This Fault
We read the NBT EVO's software and boot state with genuine BMW ISTA to determine whether this is recoverable software corruption or worn-out storage.
- Boot and update status analysis on the unit
- Fault memory review for storage and data errors
- Guided test plan execution for the boot fault
- Storage health assessment from the fault pattern
- Power supply verification before any recovery attempt
How We Repair This Fault
Recovery routes in order of invasiveness — software recovery, then unit repair or exchange, then replacement — with the quote following the test result.
- Controlled recovery re-flash with genuine software where storage is healthy
- Head unit repair or reconditioned exchange where storage has failed
- Replacement with the correct NBT EVO variant for your VIN, coded and protection-released
- Restoration of options and functions — including CarPlay activations — after any unit change
- Verification across restart cycles before hand-back
Can I Continue Driving?
Generally driveable — book diagnosis soon
Driveability is unaffected; the infotainment is unavailable until the unit is recovered. As ever with boot loops, retrying repeatedly on a weak battery makes matters worse, not better.
Frequently Asked Questions
Why does the NBT EVO boot loop after updates?
Updates rewrite large portions of the unit's software. If one is interrupted — power loss especially — the unit is left with software it can't complete booting from. Separately, storage wear can produce the same symptom without any update involved.
Can the boot loop be fixed without a new unit?
Frequently, yes — where the storage is healthy, a controlled recovery re-flash resolves it. Where storage has failed, repair or exchange is the route. The ISTA assessment tells us which before you spend anything on parts.
My CarPlay stopped working before the boot loop started — connected?
It can be. CarPlay and other functions often misbehave first as software corruption or storage wear develops, with the boot loop arriving later. Either way, the unit's condition is the thing to assess.
If the unit is replaced, will my CarPlay still work?
A replacement unit needs its functions activating for your vehicle's specification as part of the coding work — we restore the car's options, including CarPlay where it applies, and verify them before hand-back.
Related Faults & Services
Experiencing this fault on your BMW or MINI?
Jono's Vehicle Solutions specialises in advanced diagnostics, electrical fault finding, coding, programming and vehicle repairs. We find the actual cause with genuine BMW equipment before recommending any fix.
Request a Quote
Send your details and registration or VIN and we'll come back to you with the next step.