Free Windows installer for NBT-AAD: native wireless Android Auto on NBT Evo / iDrive 6 head units (BMW, Toyota GR Supra J29). Not affiliated with BMW or Toyota. https://gitlab.com/octagram-labs-group/NBT-AAD-Easy-Installer
  • C# 85.6%
  • Shell 13%
  • PowerShell 1.4%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-11-12 18:41:16 -05:00
docs/screenshots Installer: taller window so no page scrolls; fix step 3 status overlap 2026-11-11 19:02:15 -05:00
installer Installer: taller window so no page scrolls; fix step 3 status overlap 2026-11-11 19:02:15 -05:00
.gitattributes Installer: backup before every run, undo, auto start, run logs, tests and CI 2026-11-09 00:23:26 -05:00
.gitignore Installer: taller window so no page scrolls; fix step 3 status overlap 2026-11-11 19:02:15 -05:00
.gitlab-ci.yml CI: one pipeline per push instead of a branch and an MR pipeline 2026-11-11 19:03:18 -05:00
LICENSE.md Add PolyForm Noncommercial License 1.0.0 2026-10-23 09:13:22 -04:00
README.md README: remove donation button and support message 2026-11-12 18:41:16 -05:00

NBT-AAD Easy Installer

A free Windows installer for NBT-AAD, which runs native wireless Android Auto on NBT Evo (iDrive 6) head units in BMW cars and SUVs and the Toyota GR Supra (J29). Made by Octagram Labs-group.

Step 1: choose install, update or undo

⬇ Download: NBT-AAD-Easy-Installer.zip Downloads. Unzip it and run NbtAadInstaller.exe.

Note

Antivirus and "Windows protected your PC" warnings. NbtAadInstaller.exe is not code-signed (signing certificates cost money), so Windows SmartScreen and some antivirus programs may warn about it or flag it on heuristics. These are false positives: I can assure you nothing in it is malicious. If Windows says "Windows protected your PC", click More info, then Run anyway. All of the source code is right here in this repo, so if that would make you feel more comfortable, you're always welcome to build it yourself. Thanks for giving it a try!

Free for everyone. Selling it, or bundling it with anything sold, is not permitted. If you paid for it, you were scammed.

Why this exists

NBT-AAD by nanaisu / Sq00ky puts Android Auto on the car's own screen, with no aftermarket box. Installing it by hand means downloading the right release files, copying them to a USB stick, turning on SSH, logging in as root and typing a list of shell commands on the head unit. One wrong command can leave the install half done.

This installer does all of that for you, one page at a time:

  • You pick the NBT-AAD version: the latest official release is chosen for you, and any older one is a click away. Every file is checked.
  • It finds the head unit on the ENET cable and checks that it really is an NBT Evo / iDrive 6 before anything changes.
  • It backs up everything it is about to change, every run. If the backup can't be saved, nothing is changed.
  • It runs the exact steps from NBT-AAD's own install and update guides, and stops at the first problem.
  • It can undo the last update.

NBT-AAD itself is not part of this repo or the installer. The installer downloads the version you pick from its official GitHub releases every time.

What you need

  • Windows 10 or 11 with the built-in OpenSSH Client (Settings → System → Optional features). The installer checks for it.
  • An OBD-to-ENET cable. A Wi-Fi or Bluetooth OBD dongle does not work.
  • A USB stick formatted FAT32 or exFAT.
  • An NBT Evo / iDrive 6 head unit. In the car, Navigation → Settings → Position and software version must start with NBTevo_.
    • iDrive 7 (MGU) and iDrive 4/5 are not supported.
    • NBTevo_T22181I is known not to work.
    • Confirmed versions are in NBT-AAD's requirements.md.
  • Factory CarPlay coded, and the Wi-Fi antenna fitted.

How it works

1. Install, update or undo

Pick what you want to do:

  • First-time install: Android Auto is not on the car yet.
  • Update: Android Auto is already installed.
  • Undo the last update: puts the previous version back.

The latest NBT-AAD release starts downloading in the background as soon as the installer opens.

2. Prepare the USB stick

Step 2: prepare the USB stick

Pick the NBT-AAD version and the USB stick, then click Download this version to USB.

  • The version list shows every NBT-AAD release on GitHub, newest first, with its date. The latest stable release is picked and marked recommended. Test builds are marked pre-release.

  • Pick an older version if the newest has a problem on your car, or to go back to one that worked.

  • Some newer releases don't include pf_aa (the firewall tool). The installer then takes it from the nearest stable release that has it.

  • Every file is checked against GitHub's SHA-256, or its size when GitHub doesn't list one.

  • Downloads are cached, so a file isn't downloaded twice.

  • Old plugin files on the stick are removed, the new ones are copied, and every size on the stick is checked.

  • A stick that already has the chosen version is left as it is.

No USB stick (experimental): tick send the files over the ENET cable and the files go straight to the head unit over SSH.

3. Connect and turn on SSH

Step 3: connect and turn on SSH

  1. Turn the ignition on and plug the USB stick into the car.
  2. Plug the OBD-to-ENET cable into the car's OBD port and the laptop.
  3. Turn on SSH with the free Bavarian SSH client.

The installer downloads the Bavarian SSH client from its official site (ssh.bavarian-aa.uk) and verifies it against the site's SHA256SUMS. If it is already on the computer, the installer opens it for you.

The page checks the cable every 2 seconds and notices by itself when SSH is on. It then looks (read-only) at the car:

  • Is it an NBT Evo / iDrive 6 head unit?
  • Is Android Auto installed, and which build is running?
  • Are the installed files the version you picked?

It warns you when the action you picked can't work, for example an update on a car that has no install yet. With Start by itself ticked, the install or update starts as soon as SSH is on.

4. Run the install or update

Step 4: run the install

Click Run install over SSH. A command window opens, logs in and runs everything. The root password is entered for you.

  • Backup first, every time. Before anything changes, /opt/aa, the iDrive plugin folder and the car's pf.conf are copied to aa-backup\<date-time>\ on the stick (on the head unit for cable runs). Every copy is size-checked. If the backup can't be saved, the run stops and nothing is changed. The installer also keeps a copy in %LOCALAPPDATA%\NbtAadInstaller\backups, with a RESTORE.txt that explains how to put one back.
  • Install copies the Android Auto program to /opt/aa, installs the iDrive plugin (all 5 files checked) and adds the firewall rule with pf_aa. If an earlier install stopped halfway, Install finishes it.
  • Update moves the old version aside as .old copies, which is what Undo puts back. It never overwrites files in use.
  • Every file's size is checked against the release before anything changes. The run stops at the first problem.
  • Everything the window shows is saved to %LOCALAPPDATA%\NbtAadInstaller\logs.
The same page when updating

Step 4: run the update

When the window shows DONE, click Next. If it shows FAILED, don't reboot. Read the message first.

5. Reboot and connect

Step 5: reboot and connect

  1. Reboot the head unit: hold the volume knob for about 30 seconds until the screen restarts.
  2. In iDrive, open Media/Radio → Android Auto → Start. The first start after a reboot can take a minute.
The same page after an update

Step 5 after an update

Something not working? Click Save car logs before you reboot. It copies Android Auto's own logs to the laptop, because a reboot wipes them.

Safety

Use at your own risk. As the NBT-AAD author notes, only BMW/Toyota can reflash a broken head unit. Never do this while driving.

The backup covers the files the installer changes. It is not a firmware image: it can undo the installer's changes while the head unit still starts, but it can't repair a head unit that no longer starts.

Tested: working

Car Toyota GR Supra (J29)
Head unit software NBTevo_T20454I
NBT-AAD build v1.9.36-combo (Nov 8 2026), installed with this installer, then updated over the earlier v1.9.35-wifisel
Tested November 8, 2026
Result Android Auto works natively. Start with the car (autostart) works: Android Auto launches by itself at boot and comes on screen when the phone connects, with the iDrive knob and touch controlling it.

Excerpts from the NBT-AAD logs (Log to USB). Personal details such as location and phone name are removed:

Build: v1.9.36-combo (Nov  8 2026 11:54:09)
HU software / nav version: NBTevo_T20454I
[Car] vehicle Toyota (carplay.ini logo; Manufacturer=Toyota, logo OEM_TOYOTA.png), screen 1280x480 (carplay.ini)
[TcpServer] Bi-directional Android Auto engine active on port 5277 (Listener + Auto-Connector)
[NbtAadApp] start with the car: launching nbt-aad (/var/opt/aa/autostart)
[NbtAadApp] start row text -> 14 (connected)
[NbtAadApp] hold: event 52 -> state 13 (Android Auto came on screen, try 1)
[NbtAadApp] hold: state 13 visible -> 1
[NbtAadApp] hold: state 13 focus -> 1

Tips from testing:

  • The first start after a head unit reboot can take a minute while the phone reconnects.
  • Turn off any aftermarket Android Auto/CarPlay box (e.g. MMI Prime) so it doesn't take the phone first.

For developers

Build steps, the head unit scripts and the tests are described in installer/README.md.

Credits

License

PolyForm Noncommercial License 1.0.0 (SPDX-License-Identifier: PolyForm-Noncommercial-1.0.0), the same as NBT-AAD. See LICENSE.md or https://polyformproject.org/licenses/noncommercial/1.0.0

Required Notice: Copyright (c) 2026 nanaisu - NBT-AAD (https://github.com/Sq00ky/Supra-iDrive6-Android-Auto) Required Notice: Copyright (c) 2026 Octagram Labs-group - NBT-AAD Easy Installer

BMW, iDrive, Toyota, Supra and Android Auto are trademarks of their respective owners. This project is not affiliated with or endorsed by them.