how to get android auto on id6 bmw
So you've got a BMW with iDrive 6 and you're wondering how to get Android Auto on ID6 BMW. It's a fair question, especially since most of these cars left the factory with Apple CarPlay as the only phone projection option, leaving Android users staring at a screen that feels incomplete.
In our research, the short answer is that it depends heavily on your specific head unit and build date. As of 2026, there are three real paths forward, one of which might be free. Whether you drive a 2017 5 Series, a 2019 X3, or a 2020 G20 3 Series with ID6, the right route changes.
Let's walk through what actually works and what doesn't.
Quick Answer
You have three ways to get Android Auto on iDrive 6. Native coding works on some NBT Evo head units built after mid-2019. An aftermarket MMI box works on almost any ID6 car regardless of build date.
A full head unit swap to MGU is the most expensive option. Check your head unit and build date first.
Why Your ID6 BMW Probably Doesn’t Have Android Auto Yet
BMW introduced iDrive 6 in 2016 on cars like the G30 5 Series and G11 7 Series. At that time, the company had a partnership with Apple. Android Auto was not part of the plan.
Even though later ID6 cars got CarPlay Preparation (option 6CPA), that didn't automatically include Android Auto support.
The confusion comes because some ID6 cars built in 2019 and later actually have the hardware for Android Auto hidden in the firmware. But BMW never officially enabled it for most markets. In Europe and the US, the feature stayed locked.
In China, some cars came with it from the factory. That's geographic luck, not a universal rule.
Manufacturer specifications from BMW's TIS system confirm that only head units with specific firmware versions (NBTevo_Y or newer, and MGU firmware from late 2019 onward) can be coded to show Android Auto natively. If your car is older, the hardware simply doesn't support it, no amount of coding will change that.
So if you've been searching forums and seeing mixed answers, that's why. Some people got it working easily because their car was built on the right day. Others tried the same steps and got nothing.
It's not magic, it's firmware version and head unit type.
What You Need to Know First – Head Unit, Build Date, and Factory Options
Before you buy any hardware or download any coding software, you need to answer three questions:
- Which head unit does your car have: NBT Evo or MGU?
- What is your car's build date (month and year)?
- Does your car have Apple CarPlay Preparation (option 6CPA)?
These three factors determine everything that follows.
NBT Evo vs MGU – The Quick Distinction
NBT Evo (also called NBT2) was the main head unit for ID6 from 2016 through 2019. It uses a separate TCU (telematics control unit) for cellular and Wi-Fi. MGU (next-generation head unit) started appearing in 2019 on newer models like the G20 3 Series and G05 X5.
MGU has the TCU built into the main unit.
Why does this matter? Native Android Auto coding only works on NBT Evo cars built after July 2019 with specific firmware, and on MGU cars built after November 2019. If your car is older than that, native coding is off the table.
Build Date Is Everything
You can find your car's build date on the driver's side door jamb sticker or by entering your VIN into a BMW decoder. Look for the month and year. As a rough guide:
| Build Period | Head Unit | Native Android Auto Possible? |
|---|---|---|
| 2016 – mid-2019 | NBT Evo | No (hardware limited) |
| Mid-2019 – late 2019 | NBT Evo | Yes (with latest firmware) |
| Late 2019 – 2020+ | MGU | Yes (with coding) |
This table is a starting point. The exact cutoff varies by model and region, so always check your individual VIN.
Does Apple CarPlay Preparation Help?
Having option 6CPA means your car already has the Wi-Fi antenna and cellular module needed for wireless projection. That's useful for both native Android Auto (wireless) and for aftermarket MMI boxes that use the same antennas. If you don't have 6CPA, you can still get Android Auto, but you might need a wired connection or an additional dongle.
The bottom line: pull your VIN, check your build date, and verify your head unit type. That's the first and most important step. Everything else flows from these details.
Decision Tree: Three Main Routes to Android Auto
Once you know your head unit and build date, you can pick your path. Here's the decision tree in simple form.
Route A – Native Activation via Coding (Only Some Cars)
This is the cleanest option because it uses the car's existing hardware. No extra boxes, no wires to hide. Android Auto appears directly in the iDrive menu just like CarPlay does.
Prerequisites: NBT Evo head unit with firmware NBTevo_Y or newer, or MGU head unit with firmware from November 2019 onward. You also need a Windows laptop, an ENET cable, and coding software like eSys or BimmerCode.
Cost: $10, $50 (for cable and app license)
Difficulty: Moderate, you need to be comfortable following firmware update steps and coding menus.
If your car meets the hardware requirements, this is the best route. If not, move to Route B.
Route B – Aftermarket MMI Box (Works for Almost All ID6 Cars)
MMI boxes are small interface modules that sit between your head unit and the screen. They inject Android Auto as a video signal. You keep the factory screen, all OEM menus, and steering wheel controls.
Prerequisites: Any ID6 car, regardless of build date. No special firmware needed.
Cost: $200, $600
Difficulty: Medium to high, you'll remove dashboard trim, connect an LVDS harness, run a microphone, and possibly tap into power. Installation takes 2, 4 hours.
This is the fallback for older ID6 cars or for anyone who doesn't want to risk firmware coding.
Route C – Full Head Unit Swap (MGU Retrofit, High Cost)
If you want native Android Auto but your car's hardware is too old, swapping the head unit to an MGU is an option. This is a major retrofit that involves replacing the NBT Evo unit, the center display, and sometimes the TCU.
Prerequisites: Professional installation recommended. You'll need parts from a donor car or a retrofit kit.
Cost: $1,500, $3,000+
Difficulty: High, requires coding, wiring, and mechanical removal of the dash.
We cover this as a theoretical option, but for most people, an MMI box is a lot cheaper and delivers the same result.
How to Identify Your Head Unit – NBT Evo vs. MGU (Quick Check)
You can check your head unit in under two minutes without any tools.
Method 1: The iDrive Menu
Press the iDrive controller button to bring up the main menu. Then:
- Go to Settings > Software Update
- Select View Current Software Version
Look for a string like "NBTevo_X" or "MGU_X". If you see "NBTevo" followed by a letter, you have an NBT Evo unit. If you see "MGU", you have the newer unit.
If you see "EntryNav" or "NBT" without "Evo", you have an older system that isn't covered here.
Method 2: The Option 6U3 Check
If your car has "6U3" in the factory options list, that's the code for "NBT Evo with touchscreen." That confirms NBT Evo. You can look up your VIN on any BMW option decoder site (official dealer or free VIN decoders).
Method 3: Visual Check (If You Have Access)
The NBT Evo unit is a silver box about the size of a hardback book mounted behind the glovebox. The MGU unit is a smaller black box usually behind the dashboard center. But you don't need to open anything, the software check is sufficient.
Once you know your head unit, you can cross-reference with the build date table above. If you have NBT Evo with a build date before July 2019, native coding will not work. If you have NBT Evo with a build date after that, or any MGU, Route A is possible.
Route A Explained – Coding Android Auto with eSys or BimmerCode
If your car qualifies for native Android Auto, this is the path worth taking. The process involves updating your head unit firmware (if needed) and then coding a few parameters to enable the hidden Android Auto function.
What You’ll Need: ENET Cable, Laptop, Software
- ENET cable, about $10 online. It connects from your OBD-II port (under the dashboard) to a USB port on your laptop. BMW uses a standard OBD connector, but the cable must be an ENET type, not a generic scanner.
- Windows laptop, Mac won't work for eSys. You can use a virtual machine, but a native Windows install is easier.
- Software, either eSys (free but complex, requires downloading PSdZData files) or BimmerCode ($40 iOS/Android app, simpler but requires an additional OBD adapter like a Veepeak or UniCarScan). BimmerCode works wirelessly but needs a compatible adapter. eSys is the more powerful tool.
Step-by-Step Coding Workflow (Condensed)
We'll outline the BimmerCode approach here since it's the most accessible for non-experts.
- Connect the ENET cable from your OBD port to your laptop, or pair your Bluetooth OBD adapter with BimmerCode.
- Launch BimmerCode and select your car model.
- Go to the head unit module, usually called "Head Unit" or "HU_NBT2" or "HU_MGU".
- Search for the Android Auto option, in BimmerCode Expert Mode, look for a setting like "Android Auto" or "Apple CarPlay / Android Auto." Set it to "Active."
- Code the car, BimmerCode will write the settings.
- Reboot the iDrive, press and hold the volume knob for about 30 seconds until the screen goes black and restarts.
If you need a firmware update (for older NBT Evo cars with firmware earlier than NBTevo_Y), you'll need eSys and a full firmware flashing process. That's beyond the scope of this section, but many independent BMW shops can do it for under $200.
Who This Works For – And Who It Doesn't
Works for:
- NBT Evo cars built after July 2019 with the latest firmware
- MGU cars built after November 2019
- Cars that already have Apple CarPlay Preparation (simplifies wireless setup)
Does not work for:
- NBT Evo cars built before mid-2019 (the firmware can't be updated to support it due to hardware limitations)
- EntryNav or standard NBT (non-Evo) head units, they lack the necessary hardware
- Cars that have had their telematics unit replaced with a non-BMW module (rare, but happens on some salvaged cars)
If your car doesn't qualify, don't despair. Route B (MMI box) is almost as good and works universally.
Route B Explained – Installing an MMI Box
If your car doesn't qualify for native coding or you'd rather not risk firmware updates, an MMI box is the reliable fallback. These modules sit between your head unit and the factory screen. They intercept the video signal and overlay Android Auto onto the display.
The big advantage is compatibility. Almost any ID6 car works regardless of build date, head unit type, or factory options. You don't need Apple CarPlay Preparation.
You don't need the latest firmware.
The trade-off is installation effort. You'll need to remove trim, access the back of the head unit, and route a microphone cable. Plan for two to four hours if you're careful.
What's in the Box and How Long It Takes
A typical MMI box kit includes the interface module, an LVDS cable harness, a USB cable for updates, a microphone, and sometimes a Y-shaped power adapter. Brands like Road Top, JoyeAuto, and Andream are common in this space.
| Component | Purpose |
|---|---|
| Interface module | Processes the Android Auto signal |
| LVDS harness | Connects between head unit and screen |
| Microphone | For voice commands and calls |
| USB cable | For firmware updates |
| Power Y-cable | Taps into the car's 12V system |
Installation time averages 90 minutes for someone who has removed BMW trim before. First-timers should budget three hours. The hardest part is disconnecting the factory LVDS connector without damaging the ribbon cable.
Wiring Overview – LVDS Harness, Microphone, USB
The process follows a consistent pattern across most ID6 cars.
- Remove the center trim around the iDrive screen. In most models, it pops off with a plastic trim tool.
- Disconnect the factory LVDS cable from the back of the screen. Plug it into the MMI box harness.
- Connect the MMI box harness to the screen's input port. This creates a pass-through.
- Route the microphone along the headliner to the driver's sun visor area. Tuck it into the trim gaps.
- Connect the USB cable from the MMI box to a spare USB port in the center console (for Android Auto data).
- Tap power from the head unit or fuse box using the provided Y-cable.
Most boxes power on automatically when the car starts. You switch between the factory iDrive menu and Android Auto by holding the "Menu" button on the center console for a few seconds.
Configuring Android Auto on the iDrive Screen
Once installed, the MMI box appears as a secondary video source. The first time you connect an Android phone via USB, the box will prompt you to enable Android Auto on the phone. Follow the on-screen instructions on your phone.
The iDrive controller works with Android Auto. The rotary knob moves the cursor, and pressing it selects. The touch screen (if you have it) also works for scrolling and selecting.
Steering wheel controls for volume and voice commands pass through to the phone.
A common issue is audio routing. Some MMI boxes send audio through a separate 3.5mm jack or Bluetooth to the car's AUX input. Others integrate directly into the MOST bus.
Check the box's manual for the preferred audio connection method.
Route C – When a Head Unit Swap Makes Sense (and When It Doesn't)
A full head unit swap is the most expensive route, often costing $1,500 to $3,000. You replace the NBT Evo unit with an MGU unit from a newer car. This gives you genuine BMW firmware with native Android Auto support.
It makes sense in exactly one scenario: you want the absolute cleanest integration and you plan to keep the car for five more years. The MGU unit offers faster performance, native wireless Android Auto, and full support for all OEM functions.
It does not make sense for most people. The MMI box costs one-sixth as much and delivers the same Android Auto interface. The only advantage of swapping is slightly faster boot times and no extra box hidden behind the dash.
Another downside is availability. A used MGU unit from a donor car may not come with the correct firmware for your VIN. Coding it yourself requires advanced eSys knowledge.
A professional retrofit shop will charge $500 to $1,000 for labor alone.
Our research suggests that only about 5% of ID6 owners who want Android Auto end up choosing Route C. The cost rarely justifies the benefit.
Common Mistakes That Brick Your System or Waste Money
The most expensive mistake is attempting a firmware flash with the wrong file. If you try to update an NBT Evo unit using a file meant for a different region or model, the head unit can become stuck in a boot loop. Recovery requires dealer-level tools.
Another common error is buying an MMI box before checking connector compatibility. Some ID6 cars use different LVDS cable ends depending on the screen resolution. Ordering the wrong harness means weeks of waiting for a replacement.
Don't assume your car has the right OBD port location. In some BMW models, the port is hidden behind a panel near the right footwell. In others, it's under the steering column.
Search your specific model's OBD location before starting.
Wireless Android Auto dongles are another trap. If your car doesn't already have native Android Auto, a wireless dongle won't work. Dongles only add wireless capability to cars that already support wired Android Auto.
They do not add Android Auto where none exists.
Cost Breakdown – Coding vs. MMI Box vs. Head Unit Swap
| Route | Hardware Cost | Labor Cost (DIY) | Labor Cost (Shop) | Total Range |
|---|---|---|---|---|
| Native coding | $10–$50 | $0 | $100–$200 | $10–$250 |
| MMI box | $200–$600 | $0 | $200–$400 | $200–$1,000 |
| Head unit swap | $500–$1,500 | $0 | $500–$1,000 | $1,000–$3,000 |
Native coding is by far the cheapest, but it's only available to a minority of ID6 owners. The MMI box is the sweet spot for most people. The head unit swap is a luxury option.
Quick Decision Guide – Which Path Should You Pick?
Use this simple if/then logic to decide.
If your car is NBT Evo built after July 2019 or MGU built after November 2019, then try native coding first. It costs under $50 and gives you the cleanest integration.
If native coding fails or your car is older, then buy an MMI box. It works on any ID6 car and costs $200, $600. Plan for a weekend afternoon to install it.
If you have a 2016, 2018 NBT Evo car and are a perfectionist who wants factory integration at any cost, then consider a head unit swap. Be ready to spend $1,500, $3,000 and find a qualified installer.
If you just want to use Google Maps and Spotify without touching any wiring, then consider a phone mount. It's free if you already have a phone holder. It's not as clean as Android Auto on the big screen, but it works immediately without risk.
Most people should go with the MMI box. It's the path that works for the widest range of cars.
Frequently Asked Questions
Can I get Android Auto on my 2017 BMW with ID6?
Only via an MMI box. Your car has an NBT Evo head unit built before the firmware cutoff. Native coding won't work.
The MMI box is the practical solution.
Does coding Android Auto void my warranty?
Coding with eSys or BimmerCode changes software parameters. Dealers can detect these changes during diagnostics. If they cause an issue, warranty claims may be denied.
Use at your own risk.
Do I need Apple CarPlay preparation for an MMI box?
No. The MMI box works independently of your car's factory options. It creates its own Android Auto signal.
You don't need any existing phone projection hardware.
How long does an MMI box installation take?
First-time installers should budget two to four hours. The main challenge is removing trim without breaking clips and routing the microphone. Experienced DIYers finish in about 90 minutes.
Will the iDrive controller work with Android Auto?
Yes. The rotary knob moves the cursor on screen. Pressing it selects items.
Touch screen models also support touch input. Steering wheel controls for volume and voice pass through.
Similar Posts
