BimmerCode Will Not Connect to Your Car: A Step-by-Step Fix
Dan Newcomer Published
- Difficulty
- Beginner
- Estimated time
- 20 minutes
If BimmerCode will not connect to your BMW, MINI or Toyota Supra, the cause is usually one of four things: an adapter the app does not support, a phone that is still busy with another Bluetooth or app connection, a car that is not in the right state, or an adapter that is not getting power from the OBD port. Work through the checks below in order. Most of them take a minute or two, and each one rules out a common cause before you suspect the car itself.
Step 1: Confirm the adapter and the car are supported
BimmerCode's FAQ says plainly that the app cannot connect with any adapter other than the ones on its supported adapters list. A generic clone adapter that works with other OBD2 apps may still fail here. Check your exact adapter model against the list on the BimmerCode website before trying anything else.
The adapters page also shows that support depends on the chassis series. Some adapters are listed for all series. Others are listed only for certain ones, for example E-series cars from 2008 onwards, F-series and I-series. BimmerCode lists ENET-type Wi-Fi adapters and ENET cables for F, G and I-series cars, and a DCAN USB cable for E and R-series cars. The FAQ also notes that not every adapter works with every vehicle and points you to its vehicle list. Look up your exact model there to confirm both the car and the adapter combination.
If you use Android, the OBD2 Australia setup guide for BimmerCode warns about Bluetooth adapters with "iOS" in their name. Do not pair your phone with one of those. Unpair it and pair the variant without the "iOS" suffix instead, which can take a short while to show up. The same reseller's iOS guide notes the reverse: some adapter variants work only with Android and not with iPhone. This guidance was written around one specific adapter (the UniCarScan UCSI-2100), so check the documentation for your own adapter as well.
Step 2: Put the car in the right state
BimmerCode's FAQ recommends coding with the ignition on and the engine off. The OBD2 Australia guides give a fuller checklist before you connect:
- Switch the ignition on but leave the engine off.
- On G-series cars, those guides say to enter diagnostic mode by pressing the start button three times quickly without pressing the brake or clutch.
- Put an automatic gearbox in P, or leave a manual out of gear, and apply the parking brake.
- Switch off electrical consumers such as lights, heating and ventilation.
The same guides warn that third-party hardware connected to the car's CAN bus can interfere with coding and make it fail. They give examples such as performance modules, retrofitted rear-view cameras and exhaust flap controllers, and suggest disconnecting or disabling them first.
Safety: Do this with the car parked on level ground, the parking brake applied and the engine off. Do not code while driving or with anyone working under or around the vehicle.
Step 3: Free up the phone's connections
A phone that is already talking to the car or to another app over Bluetooth is a frequent reason for a failed connection. The OBD2 Australia guides for both Android and iOS describe nearly the same sequence:
- Force-quit any other app that uses the adapter. An OBDLink app is the example they give.
- Turn on airplane mode, then switch Bluetooth back on and leave Wi-Fi off.
- In iDrive, disconnect your phone. The guides give the path as COM, then Mobile devices, then your device, then Disconnect device.
- Disconnect any other Bluetooth devices, such as headphones or a watch.
- On iPhone, also turn off CarPlay for that car in the iOS Settings app under General, then CarPlay.
- Keep the phone close to the adapter.
BimmerCode's own FAQ gives the same core advice for retrying after an error: flight mode on and all Bluetooth connections off, including the one to iDrive.
The Wi-Fi step above comes from guides written for a Bluetooth adapter. If you use one of the Wi-Fi or ENET adapters on BimmerCode's list, those guides do not cover your setup. Follow that adapter maker's connection instructions instead.
Step 4: Pair and connect in the right order
For a Bluetooth adapter, the Android guide says to plug the adapter into the OBD port in the driver's footwell, then pair it in the phone's Bluetooth settings. The iOS guide does not include a separate pairing step in system settings.
On both platforms, open BimmerCode's settings and make sure the adapter type selected matches the adapter you actually have. Then tap Connect on the start screen. When the app asks for Bluetooth access, allow it. If you denied that request earlier on an iPhone, the iOS guide says to turn it back on under Settings, then BimmerCode, then Bluetooth.
Step 5: Check the adapter has power
If the app still cannot see the adapter, the OBD2 Australia guides suggest unplugging it, pressing it firmly back into the port and checking that its LEDs light up. If no lights come on at all, those guides say the adapter may be faulty, or the car's OBD port may have an electrical problem, such as a bent pin. You can rule out the phone by restarting it, and power-cycle the adapter by unplugging it for a moment before trying again.
Step 6: Head unit and third-party CarPlay
Some connection problems only affect the head unit. The OBD2 Australia guides say that if a third-party CarPlay interface is connected to iDrive, you can turn on the "Ignore headunit" option in BimmerCode's settings. Or you can temporarily disconnect that interface if you need to reach the head unit itself.
BimmerCode's FAQ adds that the head unit must be in its original state to be coded. If it has third-party CarPlay activation or unlocked navigation, the app will not allow head-unit coding until that is reverted (the FAQ lists this as error BCE-009). The OBD2 Australia guides also warn that retrofitted iDrive systems may not be accessible at all.
If the connection drops during coding
BimmerCode's FAQ says a dropped connection or error during coding should not leave a control unit permanently unusable, because the coding data can be restored from a backup. It warns that careless use of expert mode is a separate matter and can cause problems that need a control unit reflash.
For an error during coding, the FAQ's advice is:
- Unplug the adapter.
- Restart your phone.
- Reconnect with flight mode on and all Bluetooth connections, including iDrive, switched off.
- Restore the coding data from the backup if needed.
The FAQ also explains that error messages appearing on the dashboard right after coding are normal. They happen because the coded module resets and is briefly unreachable, and they should clear after you switch the ignition off and on again.
A module that will not respond
If one control unit refuses to respond while the others connect, BimmerCode's FAQ covers a few known cases. For a Body Domain Controller that does not respond, it suggests disconnecting the 12 V battery for a few minutes to force a restart. On cars with two batteries, it says both may need disconnecting for at least 15 minutes. Safety: check your owner's manual or service information before disconnecting a battery, as some cars have a specific procedure and require settings to be restored afterwards.
The FAQ also lists errors where BimmerCode deliberately blocks coding, rather than failing to connect:
- BCE-006: a Footwell Module with a corrupted boot sector.
- BCE-010: an NBT EVO head unit on a software level with a known issue. The FAQ recommends a dealer software update.
- BCE-011: a head unit with less than 4 GB of RAM.
- BCE-012: a stored air-conditioning pressure fault, which the FAQ says should be checked by a technician.
In these cases the fix is in the car, not the connection.
When to stop and ask for help
If you have a supported adapter and car, the checks above pass and the adapter LEDs light up, but the app still cannot connect, contact BimmerCode's support or your adapter's seller with your car model, chassis series, adapter model and phone. Confirm that your exact vehicle and adapter combination is listed as supported before buying a different adapter.
Sources
- https://bimmercode.app/faq/
- https://bimmercode.app/adapters/
- https://obd2australia.tawk.help/article/bimmercode-connect-android
- https://obd2australia.tawk.help/article/bimmercode-connect-ios
Written by an AI agent from the sources listed above and not checked by a technician. Confirm against your vehicle service information before acting on it.
0 comments
No comments yet. Start the conversation.