Apple CarPlay Activation in BMW NBT EVO and Entry Nav2 – Complete Guide

Apple CarPlay on BMW models with the NBT EVO or Entry Nav2 system is one of the most searched-for activations among F-series owners. In many cars, the manufacturer already installed all the necessary controllers and licenses at the factory – the feature simply stays dormant until it's unlocked with the right coding. This guide covers, in full technical detail, what this activation actually is, which features it unlocks, how the process works step by step, what it requires, how to check whether your car is compatible, and what to do if CarPlay doesn't appear immediately after the activation is complete.

This article draws on years of hands-on BMW coding and diagnostic experience – written for owners who want to understand the technical side of the process before deciding to activate.

What Apple CarPlay is and how the activation works

Apple CarPlay connects an iPhone to the car's infotainment screen. Once connected (wired or wireless), the iDrive display switches to the familiar phone interface – Apple Maps or Google Maps, Messages, Phone, Spotify, Apple Music, Podcasts, and voice control via Siri. In BMWs with NBT EVO, the required hardware (Bluetooth/Wi-Fi module, antenna, head-unit controller) is usually already present in the car – what's missing is simply an active FSC license (Feature and Service Code) and the corresponding coding of the head-unit controller.

Activating Apple CarPlay on BMW NBT EVO means writing the correct FSC code to the infotainment controller (the HU_NBT or HU_ENTRY module), plus – in some cases – additional parameter coding via E-Sys. The FSC is a unique activation code tied to the vehicle's VIN, generated from BMW's own servers. Without a valid FSC, CarPlay simply will not appear, no matter how modern your phone is or how up to date your navigation software happens to be.

The entire technical process is carried out remotely by a certified DiagsoCar technician. You don't need any BMW coding knowledge or need to understand controller architecture – you just need to have the hardware ready (laptop, ENET cable, internet) and grant remote access to your computer for the duration of the activation. That means the whole procedure happens without a visit to a dealership, workshop or coding shop.

Why the activation is possible in the first place

BMW has long followed a "feature on demand" approach – the car physically has the hardware needed for a given feature, but enabling it is licensed separately. This applies not only to Apple CarPlay, but also to features like Video In Motion, extended Bluetooth, or additional iDrive apps. This architecture lets the manufacturer differentiate trim levels without changing hardware components, while still allowing later activation if the car has the right module.

Which features the activation unlocks

Activating Apple CarPlay on NBT EVO usually focuses on CarPlay itself, but since it involves coding the infotainment controller, it's worth knowing the full set of related features that can be unlocked in the same system.

Apple CarPlay (Wireless and Wired)

The core feature – connecting an iPhone to iDrive. Newer NBT EVO software versions support both wired CarPlay (Lightning/USB-C cable into the console's USB port) and wireless CarPlay (over Wi-Fi, after initial Bluetooth pairing). Whether your car supports the wireless variant depends on the phone module's hardware – some cars need to stick with a wired connection.

VIM – Video In Motion

VIM (Video In Motion) removes the lock that, by default, disables video playback (movies, YouTube via third-party apps, the rear-view camera feed in service mode) while driving. By default, the screen blocks video playback above a certain speed for safety reasons. Activating VIM removes that restriction – keep in mind this feature is intended mainly for passengers and should be used responsibly.

Screen Mirroring

Screen Mirroring lets you display your phone's screen (Android or iOS) directly on the iDrive display, outside the standard CarPlay or Android Auto interface. This is useful for apps that CarPlay doesn't natively support.

BMW Apps

BMW Apps is BMW's native app platform within iDrive, allowing integration with certain online services directly from the infotainment system, without going through a phone connected via CarPlay.

Laptimer

The Laptimer feature records lap times, acceleration and basic track-driving metrics, displaying them on the iDrive screen. It's part of the BMW Sport/M package and is often activated alongside other infotainment features during the same coding session.

Extended Bluetooth

Extended (Advanced) Bluetooth allows two phones to be connected simultaneously, higher-quality audio streaming, and fuller synchronization of contacts and text messages. This is a feature that's often restricted at the factory in many cars, despite the corresponding hardware module being present.

iDrive 6 look

In some cars running iDrive 5, it's possible to switch the visual layer of the menu to the iDrive 6 style – newer, more legible tiles and a main-menu layout closer to what's found in later F-series model years and early G-series models.

Fullscreen Apple CarPlay and Split Screen

This is one of the most important distinctions BMW owners ask about – covered in detail in the next section, since Fullscreen availability depends directly on your navigation software version.

Fullscreen Apple CarPlay vs. Split Screen

On BMW NBT EVO, Apple CarPlay can run in one of two display modes.

Split Screen – CarPlay occupies part of the screen (usually the right or left column), while the rest still shows native BMW widgets – clock, temperature, media info. This is the older, more limited display method, found in lower software versions.

Fullscreen – CarPlay takes over the entire iDrive display, exactly like in newer BMW models with the MGU system. Maps, contact lists or the Spotify interface are shown at full size, without sharing space with native widgets.

What determines Fullscreen availability

Fullscreen mode is only available from a specific navigation software version upward (see the table below). If your car has an older version, only Split Screen can be activated – no amount of coding will "add" Fullscreen to a software version that doesn't support it. In that case, the only path to Fullscreen is updating the navigation software to a version that supports it first, then activating.

Advantages and limitations

• Full use of the screen's surface area, especially for navigation
• A look and feel closer to newer BMW models
• Better readability of lists, contacts and music playlists
• Not available on older software versions (below NBTevo_N)
• On some cars, a fully stable Fullscreen activation requires additional E-Sys coding

NBT EVO software versions – table

The NBT EVO navigation software version is marked with a letter at the end of the version string (e.g. NBTevo_N). This is what determines which Apple CarPlay display mode is available to you.

How to check your NBT EVO software version

Checking your version takes less than a minute and requires no diagnostic tools – just a few taps through the iDrive menu.

1. Open Navigation and go to the Map.
2. Press Options.
3. Select Navigation settings.
4. Scroll to the Position and version section.
5. Read the Version information – what matters is the letter at the end of the designation (e.g. "NBTevo_Q").

Write that letter down before purchasing an activation – it's the fastest way to know upfront whether your car will support Fullscreen or only Split Screen.

How to check if your BMW supports Apple CarPlay

Not every F-series BMW has the hardware required for CarPlay. Before deciding on an activation, it's worth verifying two things.

1. Infotainment system

This guide applies only to NBT EVO (ID5/ID6) and Entry Nav2 units. Older systems (CIC, standard NBT without EVO) do not support this activation due to a different infotainment controller architecture.

2. The 609 navigation package (Navigation Professional)

Many NBT EVO cars were factory-ordered with the 609 Navigation Professional package, which includes a phone module with the required hardware. Finding code 609 on the factory equipment list (visible e.g. in the VIN data or on the equipment sticker in the glovebox/trunk) is a good early sign that the car is compatible.

3. Verification with us

If you're not sure about your car's equipment or software version, the safest option is to contact us before purchasing – we'll verify compatibility based on your VIN before you commit to the service.

Supported BMW and MINI models

The activation applies to vehicles fitted with NBT EVO or Entry Nav2, mostly produced from 2015 onward.

Requirements for the activation

You only need three things to have Apple CarPlay activated:

• A Windows laptop – any machine capable enough to run the diagnostic software and hold a remote-access session
• An ENET cable – the interface connecting BMW's OBD diagnostic port to your laptop's Ethernet/USB port
• A stable internet connection – needed both to retrieve the FSC license and to run the remote session with the technician

Why ENET specifically, and not another interface

The ENET cable uses an Ethernet port, which gives significantly higher throughput than older USB/RS232-based interfaces like K+DCAN. For operations like writing an FSC or coding via E-Sys, that translates directly into more stability and speed for the whole process – and, in turn, into a safer operation on the vehicle's control module.

The activation process step by step

1. Purchase the service on sklep.diagsocar.com – choose the variant matching your system (NBT EVO / Entry Nav2)
2. Technician contact – after purchase, our certified technician reaches out to schedule a convenient time for the remote session
3. Hardware setup – connect the ENET cable to the car's OBD diagnostic port and to your laptop, then turn the ignition on
4. Remote access – grant the technician remote desktop access (e.g. via AnyDesk or TeamViewer) so they can perform the coding directly on your laptop, connected to the car
5. FSC generation and write – the technician generates the activation code tied to your VIN and writes it to the infotainment module
6. Write verification – checking that the coding was correctly accepted by the controller
7. System restart – once the write is complete, an iDrive restart is performed so the activation can fully load
8. Final test – checking that the Apple CarPlay option now appears in the Bluetooth/CarPlay connection settings

The whole procedure usually takes anywhere from a few minutes to under an hour, depending on internet connection stability and your car's software version.

What to do after activation – ISTA+ diagnostics

After the activation is complete, it's worth running a full vehicle diagnostic scan with ISTA+ (though it isn't mandatory) to confirm the coding didn't leave any incorrect entries in other modules.

What if ISTA+ shows errors

This is a common and usually harmless sight after any controller coding – including a CarPlay activation. In practice, these are most often:

• Historical entries – errors logged before the activation, unrelated to the procedure itself
• Transient communication messages – appearing during the module restart while the coding is being written

What to do with these errors

1. Clear all logged errors in ISTA+
2. Run the diagnostic test again on the whole vehicle
3. If the errors don't reappear – it doesn't indicate any damage to the car; they were historical or transient entries

If, after clearing and re-testing, the same errors keep showing up consistently in the same module, it's worth reaching out to our technical support for a review – though this situation is rare after a CarPlay activation.

E-Sys – when it's needed and what it's for

E-Sys is an advanced BMW controller coding tool, used by technicians in situations where writing the FSC alone isn't enough to get full functionality.

When E-Sys is used during a CarPlay activation

• Activating fullscreen Apple CarPlay – on some cars with a Fullscreen-capable software version (N and newer), writing the FSC alone turns on CarPlay, but in Split Screen mode. Switching to fullscreen requires additional parameter coding via E-Sys
• Non-standard factory configuration – if the car has an unusual set of option codes, the standard FSC procedure may need a correction in E-Sys so the system correctly recognizes the active feature
• Cars with prior, incomplete coding attempts – E-Sys allows restoring a consistent parameter state before the actual activation

Why additional coding is sometimes necessary

The NBT EVO infotainment controller stores hundreds of FDL (Fahrzeug Daten Liste) parameters describing the exact configuration of the vehicle. The FSC code unlocks the license for a feature, but exactly how that feature is displayed (e.g. in which screen mode) can depend on additional coding parameters. In most cases the standard procedure is enough, but the technician evaluates this individually based on your software version and your car's configuration.

Common questions about E-Sys

Do I always need E-Sys? No – in many cases a standard FSC activation is completely sufficient. E-Sys is only used selectively, when it's needed to enable Fullscreen mode or to handle a non-standard configuration.

Do I need to operate E-Sys myself? No. If your situation requires it, the additional coding is performed by the technician during the same remote session – it's not a separate, additionally-charged service outside the agreed scope.

Is E-Sys safe? Yes, provided the coding is done by someone who understands the FDL structure of the given controller. Incorrect parameters can cause module errors – which is why this step is always handled by a certified technician, never by an unsupervised automated script.

What if Apple CarPlay doesn't appear after activation

This is one of the most common concerns, and it's worth understanding well so you don't worry unnecessarily once the activation is done.

What to do in that situation

1. Wait about 30 minutes. The infotainment controller needs time to fully process the newly written FSC license
2. Perform a hard reset of iDrive (described below). This resolves it in most cases – after the restart, the feature appears automatically in the connection settings
3. If it still doesn't appear – in isolated cases, an additional manual activation via E-Sys is required. This doesn't mean the initial activation was done incorrectly – some cars simply need this extra coding step due to their individual controller configuration

If something's out of order after your purchase – e.g. CarPlay still doesn't appear even after a restart – reach out to our technical support, and any additional verification (including possible E-Sys coding) is covered as part of the service you purchased.

How to hard reset iDrive

A hard reset of the iDrive system is a basic service procedure worth knowing regardless of the CarPlay activation – it also helps with other minor infotainment freezes.

How to perform a hard reset

1. Turn off the ignition and wait until the iDrive screen goes completely dark
2. Hold the iDrive controller knob with the ignition on for about 10-15 seconds, until the screen restarts showing the BMW logo
3. Wait for the system to fully reboot – this can take anywhere from one to a few minutes
4. Check whether the changes (including Apple CarPlay) are now visible in the settings

When it's worth doing a hard reset

• Right after activation, if the new feature isn't visible yet
• After every navigation software update
• When the infotainment system responds more slowly than usual or "freezes" on one screen

Common issues and how to fix them

Apple CarPlay doesn't appear at all

Check, in order: whether at least 30 minutes have passed since activation, whether a hard reset of iDrive has been performed, and whether Bluetooth and Wi-Fi are enabled on your phone (needed even for wired CarPlay, for the initial pairing). If it still doesn't appear, an additional E-Sys activation may be required.

No Fullscreen mode despite activation

The most common cause is a navigation software version that's too old (below NBTevo_N) – in that case, only Split Screen is available. To get Fullscreen, the software needs to be updated to version N or newer first.

Errors in ISTA+ after diagnostics

As described in the ISTA+ section above – in the vast majority of cases, these are historical entries or transient messages from the module restart. Clear the errors and run the test again.

ENET connection issues

The most common causes are: a damaged or low-quality cable, missing network driver installation on Windows, or an incorrectly configured IP address on the laptop's network interface. The technician checks this while setting up the remote session.

Car not detected by the software

Usually caused by the ignition not being on (the car needs to be in ignition mode, not just have the battery connected) or the ENET cable not being properly plugged into the OBD port.

Certificate issues

The FSC code is generated using current data from BMW's servers – if the certificates used for generation are outdated, or the internet session is interrupted mid-process, the write can fail. In that case the technician simply retries the process.

Issues after an iDrive software update

Updating the map or navigation software can sometimes reset some display settings. A hard reset of iDrive is usually enough to fix this – the active FSC license stays written to the controller regardless of a map update.

Issues after an iOS update

Apple occasionally changes CarPlay protocol requirements in new iOS versions. If CarPlay stops connecting after a phone update, first try unpairing and re-pairing the phone with the car (remove and re-add the device in Bluetooth settings) before assuming the activation itself is at fault.

FAQ – Frequently asked questions

Safety and warranty

Technical requirements

After activation

Fullscreen and E-Sys

Purchase process and use

Activating Apple CarPlay on BMW NBT EVO and Entry Nav2 is a procedure that, with the right preparation (laptop, ENET cable, internet) and professional execution, runs smoothly and doesn't require a dealership visit. The key step is checking your navigation software version beforehand – it determines whether you'll get Split Screen or full Fullscreen mode. If the feature doesn't appear right after activation, the first thing to do is wait about 30 minutes and perform a hard reset of iDrive – that's standard system behavior, not a sign of an error.