Unveiling the Witchcraft Spell that Powers Android Auto

The use of technology has become an essential part of our daily lives, with various devices and applications designed to make tasks more efficient and convenient. One such innovation is Android Auto, an integrated software system that allows users to connect their smartphones to their vehicle's infotainment system. However, there has been a recurring concern about the potential witchcraft connection with Android Auto. While this may sound like an irrational belief, it is essential to understand the underlying reasons for such fears. The connection between witchcraft and technology can be traced back to historical contexts where witchcraft was associated with supernatural powers and black magic. In folklore and popular culture, witches are often depicted as possessing the ability to control and manipulate various aspects of nature, including technology.

There are two revisions of the MMI boxes that use slightly different firmware. Earlier units only use ISPBOOOT.BIN files while later units (henceforth called 'B version') use GEMINI_PACK.BIN. A and B versions are not compatible with each other.
The latest updates for B versions also include an ISPBOOOT.BIN file now (next to the existing GEMINI_PACK.BIN), which can be used to update to that specific version as well.
Very important: GEMINI_PACK.BIN files don't include all partitions and should be flashed subsequently (delta update), i.e. don't skip any versions between flashes. ISPBOOOT.BIN always includes all partitions, it should be safe to skip versions in this case. If your download includes both files, you do not need to flash both of them (just pick one; preferably the full ISPBOOOT.BIN to avoid potential problems with missing partitions).
Please also note, if you have a B version with an older firmware, it is not possible to flash ISPBOOOT.BIN files. That option was only introduced in later updates.

Furthermore, the software update menu now requires a vendor specific PIN code and a non-compatible update will show Invalid key and result in an unusable device. I Just thought i let you know as soon as possible that something in Pre 14 causes this and wanted to know if people with other phones also have this issue.

In folklore and popular culture, witches are often depicted as possessing the ability to control and manipulate various aspects of nature, including technology. In the case of Android Auto, the concern arises from the perceived notion that the system's connection and integration may allow external entities, including witches or evil spirits, to exert control over the vehicle or the driver. This fear is further fueled by instances of technological malfunctions or accidents that have occurred while using the software, leading some individuals to attribute these incidents to supernatural forces rather than technical issues or human error.

The witchcraft connection android auto

This thread is intended to consolidate all available information on the chinese 'Andream' MMI Box.

• FAQ & General information - down below
• Pictures - 2nd post
• Software updates - 3rd post
• Research (Manufacturer, PCB, . ) - 4th post

• Apple CarPlay (wired and wireless)
• Android Auto (wired and wireless)
• Apple AirPlay
• Screen Mirroring (wired) with Autolink
• Displaying 3rd party aftermarket camera video signals
• Basic USB playback from e.g. a thumb drive

In general for Chinese products you can buy from AliExpress. Unfortunately there is no one-fits-all link available as it seems to depend on the user's location. The official vendor is 'Andream Car Multimedia Store'.
Make sure the model number 'EW-BMCP-NBT01A' (. for NBT) matches.
Try https://www.aliexpress.com/item/4000192794400.html (UK) or https://www.aliexpress.com/item/4000174276908.html (GER).

Make sure to compare prices before you buy!

There is an identical unit from Korean company IndiWork here for 315$. Their model number is 'SCB-NBT' but the software is identical, so the units truly are the same.
The same unit with slightly different software (some graphics are changed) is sold by Carlinkit.

There is a similar but different unit from JoyeAuto here that also supports CIC for ~415$.
It has wireless CarPlay and wired Android Auto support but it is unknown if AA also works wireless.
Note that this unit cannot use the car's microphone and requires an external mic (might result in poor audio, depends on the mic).
Link to thread: https://f30.bimmerpost.com/forums/sh. php?t=1622013

BimmerTech is selling their MMI Prime box for 649$.
While the price tag is high-end, the unit is actually identical to the ones sold by Andream, IndiWork and Carlinkit. The software of all of them can be used interchangeably on all units with no difference in features, only a few main menu graphics/icons are changed (Update: No longer the case, refer to the Downloads post below).
Link to thread: https://f30.bimmerpost.com/forums/sh. php?t=1615794

Installation

1. Disconnect the big 'Quadlock'-cable from the original headunit
2. Connect the box's Y-harness to that cable. The new quadlock goes into the headunit, the small power cable into the MMI box itself
3. Disconnect the LVDS cable from your original display and plug it in the box's 'LVDS in' connector
4. Connect the 2nd LVDS cable to 'LVDS out' and plug that into the display instead

• No sound
• iDrive clock stops working
• No trip info / usage stats

Quadlock and 2-pin cable:

Video guides

From YT 'BMW DIY Guy' for BimmerTech's MMI v1: link

From YT 'Grind My Gears' for BimmerTech's MMI Prime: link

Official BimmerTech Prime installation video: link

Configuration

The main configuration is done on the box itself using 'dip switches':

The unit itself (main menu, settings, etc), CarPlay and Android Auto.

Apple CarPlay

Android Auto

Newer software versions have the AA widescreen enabled and look like this:

Screen Mirroring

For Android phones with an app called Autolink.

Software Updates

• Andream (EW-BMCP-NBT01A & EW-BMCP-NBT02B)
• IndiWork.co.kr (SCB-NBT)
• Carlinkit
• RoadTop
• Bimmertech's MMI Prime

1. Format a USB flash drive with FAT32
2. Unzip the archive, then copy the upgrade file 'ISPBOOOT.BIN' / 'GEMINI_PACK.BIN' (for Software) or 'upgrade.bin' (for MCU) into the root directory of the USB flash drive
3. Insert the USB flash drive into the MMI's USB port
4. Start the car and switch to the MMI
5. Navigate to 'Setup' -> 'Software Update' -> 'System Update' or 'MCU Update' (newer versions will require a PIN, see below)
6. Confirm the popup
7. The upgrade takes ~1-2min. Do not power off the unit (i.e. don't turn off the car)
8. The unit will automatically switch to iDrive. You can switch back to see the update progress

In case your unit does not boot up anymore or you have other issues updating there is a way to force flash an update.

1. Put the ISPBOOOT.BIN file on a usb flash drive (FAT32) and plug it into the box
2. The MMI box needs to be fully powered off (best to remove the power cable)
3. Press and hold the 'Back' button on your iDrive controller. Do not let go!
4. If you removed the power cable, plug it back in while still pressing the 'Back' button.
5. Turn on the ignition of your car. Keep pressing the 'Back' button.
6. The display should switch to a black screen and show the update screen shortly afterwards. You can let go of the 'Back' button now.

These are the official firmwares provided by the Chinese sellers.

Warning: Please read the info on cross compatibility below before downloading anything. Do not flash updates from other vendors that are marked as 'not cross compatible'!!
Warning 2: Do not flash versions for NBT on CIC or the other way around!
Warning 3: Do not flash directly to the latest version in case you still run on a very old firmware!
Warning 4: If your unit is asking for a GEMINI_PACK.BIN, do not skip updates. Those updates should be flashed subsequently. This is not the case for ISPBOOOT.BIN.

Cross compatibility of updates

Andream, Bimmertech, Carlinkit and RoadTop all offer the same product from the below mentioned company Sunplus.
Since Carlinkit v9.2.2.yl.b / Andream v2.1.0.3.gpe.b / Bimmertech v2.0.2.4.mmi.b cross flashing is no longer possible! Furthermore, the software update menu now requires a vendor specific PIN code and a non-compatible update will show 'Invalid key' and result in an unusable device. You will not be able to use Carplay or Android Auto anymore.
TL;DR: Do not flash updates from different vendors. If you are unsure which device you have, do not flash anything at all!!

ISPBOOOT.BIN vs GEMINI_PACK.BIN

There are two revisions of the MMI boxes that use slightly different firmware. Earlier units only use ISPBOOOT.BIN files while later units (henceforth called 'B version') use GEMINI_PACK.BIN. A and B versions are not compatible with each other.
The latest updates for B versions also include an ISPBOOOT.BIN file now (next to the existing GEMINI_PACK.BIN), which can be used to update to that specific version as well.
Very important: GEMINI_PACK.BIN files don't include all partitions and should be flashed subsequently (delta update), i.e. don't skip any versions between flashes. ISPBOOOT.BIN always includes all partitions, it should be safe to skip versions in this case. If your download includes both files, you do not need to flash both of them (just pick one; preferably the full ISPBOOOT.BIN to avoid potential problems with missing partitions).
Please also note, if you have a B version with an older firmware, it is not possible to flash ISPBOOOT.BIN files. That option was only introduced in later updates.

Available software and download links:

Andream [ NBT ] [ ISPBOOOT.BIN ] (should work with IndiWork as well)
Model: EW-BMCP-NBT01A
Note: Andream is shipping units with '.lc.b' versions that can be upgraded to '.gpe.b' versions (there is no difference between versions). Do not confuse this with '.lt.b' versions, these are RoadTop and not compatible!!

• v2.0.2.5.t0.gp.b
• v2.0.2.6.gpe.b
• v2.0.2.7.gpe.b
• v2.1.0.3.gpe.b (PIN: 2863) (Not cross compatible)
• v2.1.0.6. lc .b (PIN: 2863) (Not cross compatible)
• v2.1.0.6. gpe .b (PIN: 2863) (Not cross compatible)
• v2.1.0.7.gpe.b (PIN: 2863) (Not cross compatible)
• v2.1.0.8.multiusb.gpe.b (PIN: 2863) (Not cross compatible) -- AA widescreen fix (but wrong DPI)
• v2.1.0.9.gpe.b (PIN: 2863) (Not cross compatible) -- Correct AA resolution and DPI
• v2.1.1.2.gpe.b (PIN: 2863) (Not cross compatible)
• v2.1.1.5.gpe.b (PIN: 2863) (Not cross compatible)
• v2.2.0.5.gpe.b (PIN: 2863) (Not cross compatible)
• v3.5.0.9.gpe.b (PIN: 2863) (Not cross compatible)
• v3.6.0.2.gpe.b (PIN: 2863) (Not cross compatible)

• MCU 19.12.04
• MCU 19.12.12
• MCU 20.4.2.14 (Not cross compatible)
• MCU 20.5.9.10 (Not cross compatible)
• MCU 20.06.02 (Compatible with Carlinkit & RoadTop)

• B_V1.0.2 (PIN: 5025) (Not cross compatible)
• B_V1.0.4 (PIN: 5025) (Not cross compatible)
• B_V1.0.4-2 (PIN: 5025) (Not cross compatible) -- AA widescreen fix (Additional info)
• B_V1.1.2 (PIN: 5025) (Not cross compatible)
• B_V1.1.5 (PIN: 5025) (Not cross compatible)
• B_V1.2.1 (PIN: 5025) (Not cross compatible)
• B_V1.2.5 (PIN: 5025) (Not cross compatible)
• B_V1.5.5 (PIN: 5025) (Not cross compatible)
• B_V1.5.9 (PIN: 5025) (Not cross compatible)
• B_V1.6.2 (PIN: 5025) (Not cross compatible)

• MCU 20.10.22.16 (Cross compatibility unknown)

Note: There are two B2-Versions for 'NBT'. Their updates are not compatible with each other.

• B2_V1.1.5 (PIN: 5025) (Not cross compatible)
• B2_V1.2.0_t (PIN: 5025) (Not cross compatible)
• B2_V1.2.5 (PIN: 5025) (Not cross compatible)
• B2_V1.5.0 (PIN: 5025) (Not cross compatible)
• B2_V1.5.5 (PIN: 5025) (Not cross compatible)
• B2_V1.5.9 (PIN: 5025) (Not cross compatible)
• B2_V1.6.2 (PIN: 5025) (Not cross compatible)

• MCU 20.10.22.16 (Cross compatibility unknown)
• MCU 21.09.13.122 (Cross compatibility unknown)

Note: There are two B2-Versions for 'NBT'. Their updates are not compatible with each other.

• B2_V1.6.2_1_n (PIN: 5025) (Not cross compatible)
• B2_V1.6.5_n (PIN: 5025) (Not cross compatible)

• v2.2.0.2.gpe.e (PIN: 2863) (Not cross compatible)

• E_V1.1.5 (PIN: 5025) (Not cross compatible)
• E_V1.5.4 (PIN: 5025) (Not cross compatible)
• NEW E_V1.6.7_n (PIN: 5025) (Not cross compatible)

• v2.1.0.4.gpe.c (PIN: 2863) (Not cross compatible)
• v2.1.0.7.gpe.c (PIN: 2863) (Not cross compatible)
• v2.1.0.9.gpe.c (PIN: 2863) (Not cross compatible) -- AA widescreen fix

• MCU 20.4.22.12 (Not cross compatible)
• MCU 20.6.18 (Cross compatible with RoadTop CIC)
• MCU 20.9.29.13 (Cross compatibility unknown)

Note: There are two B-Versions for 'CICHL'. Their updates are not compatible with each other.

• CHL_V1.1.2 (PIN: 5025) (Not cross compatible)
• CHL_V1.1.4.cpbb_n (PIN: 5025) (Not cross compatible)
• CHL_V1.1.5 (PIN: 5025) (Not cross compatible)
• CHL_V1.2.5 (PIN: 5025) (Not cross compatible)
• CHL_V1.5.0 (PIN: 5025) (Not cross compatible)
• CHL_V1.5.5 (PIN: 5025) (Not cross compatible)
• CHL_V1.6.2 (PIN: 5025) (Not cross compatible)

• MCU 21.1.28.10 (Cross compatibility unknown)

Note: There are two B-Versions for 'CICHL'. Their updates are not compatible with each other.

• v3.1.0.2.gpe.c.hl (PIN: 2863) (Not cross compatible)
• v3.5.0.2.gpe.c.hl (PIN: 2863) (Not cross compatible)
  

• MCU 20.9.29.13 (Cross compatibility unknown)
• MCU 21.1.16.17 (Cross compatibility unknown)

• v2.1.0.6.lt.b (PIN: 8032) (Not cross compatible)

• MCU 20.06.02 (Compatible with Andream & Carlinkit)

• BR104 (PIN: 8032) (Not cross compatible)
• BR110 (PIN: 8032) (Not cross compatible)
• BR112 (PIN: 8032) (Not cross compatible)
• BR115 (PIN: 8032) (Not cross compatible)
• BR120.cpSDNRTY (PIN: 8032) (Not cross compatible)
• BR125 (PIN: 8032) (Not cross compatible)
• BR152.drvrst (PIN: 8032) (Not cross compatible)
• BR157 (PIN: 8032) (Not cross compatible)
• BR164t (PIN: 8032) (Not cross compatible)
  

• MCU 20.06.02 (Compatible with Andream & Carlinkit)
• MCU 20.10.22.16 (Cross compatibility unknown)

Note: There are two B2-Versions for 'NBT'. Their updates are not compatible with each other.

• B2R115 (PIN: 8032) (Not cross compatible)
• B2R116_10s (PIN: 8032) (Not cross compatible)
• B2R123 (PIN: 8032) (Not cross compatible)
• B2R125 (PIN: 8032) (Not cross compatible)
• B2R154 (PIN: 8032) (Not cross compatible)
• B2R157 (PIN: 8032) (Not cross compatible)
• B2R162 (PIN: 8032) (Not cross compatible)
• B2R164t (PIN: 8032) (Not cross compatible)
• NEW B2R168_a (PIN: 8032) (Not cross compatible)

Note: There are two B2-Versions for 'NBT'. Their updates are not compatible with each other.

• v3.6.0.2.lt.b2 (PIN: 8032 ?) (Not cross compatible)

• ER162 (PIN: Unknown) (Not cross compatible)

• MCU 21.6.12.117 (Not cross compatible)

• v2.1.0.6.lt.c (PIN: 8032) (Not cross compatible)
• v3.5.0.10.lt.c (PIN: 8032) (Not cross compatible) Note: Untested, flash at your own risk

• MCU 20.6.18 (Cross compatible with Andream CIC)

• CHLR157 (PIN: 8032) (Not cross compatible)
• CHLR162 (PIN: 8032) (Not cross compatible)
• NEW CHLR166 (PIN: 8032) (Not cross compatible)

• 9.1.8.yl.b
• 9.1.9.yl.b
• 9.2.2.yl.b (PIN: 4091) (Not cross compatible)
• 9.2.5.yl.b (PIN: 4091) (Not cross compatible)
• 9.2.7.t.yl.b (PIN: 4091) (Not cross compatible)
• 9.2.8.yl.b (PIN: 4091) (Not cross compatible)
• 9.2.9.yl.b (PIN: 4091) (Not cross compatible)
• 9.2.17.yl.b (PIN: 4091) (Not cross compatible)
• 9.2.20.yl.b (PIN: 4091) (Not cross compatible)
• 9.5.10.yl.b (PIN: 4091) (Not cross compatible)
• 9.6.3.yl.b (PIN: 4091) (Not cross compatible)

• MCU 20.1.4 (md5 hash is identical to Bimmertech's MCU '10.1.4.11')
• MCU 20.5.9.10 (Cross compatibility unknown)
• MCU 20.06.02 (Compatible with Andream & RoadTop)
• MCU 20.08.13 (Cross compatibility unknown)
• MCU 20.10.22.16 (Cross compatibility unknown)

• 9.2.20.yl.b2 (PIN: 4091 ?) (Not cross compatible)
• 9.5.4.yl.b2 (PIN: 4091 ?) (Not cross compatible)
• 9.5.10.yl.b2 (PIN: 4091 ?) (Not cross compatible)
• 9.6.2.yl.b2 (PIN: 4091 ?) (Not cross compatible)

• MCU 20.10.22.16 (Cross compatibility unknown)

• 9.5.4.yl.e (PIN: 4091 ?) (Not cross compatible)
• 9.5.10.yl.e (PIN: 4091 ?) (Not cross compatible)

• v2.0.2.3t6.mmi.b
• v2.0.2.3t7.mmi.b
• v2.0.2.4.mmi.b (Not cross compatible)
• v2.0.2.5t2.mmi.b (Not cross compatible)
• v2.0.2.5t5.mmi.b (Not cross compatible)
• v2.0.2.6.mmi.b (Not cross compatible) -- AA widescreen fix
• v2.0.2.6t0.mmi.b (Not cross compatible)
• v2.0.2.7t0.mmi.b (Not cross compatible)
• v2.0.2.8.mmi.b (Not cross compatible)
• v2.1.0.0.mmi.b (Not cross compatible)
• v2.1.1.0.mmi.b (Not cross compatible)
• v2.1.1.4.mmi.b (Not cross compatible)
• v2.1.1.4t.mmi.b (Not cross compatible)

• MCU 10.1.4.11
• MCU 10.2.18.15 (Not cross compatible)
• MCU 10.3.24.15 (Not cross compatible)
• MCU 10.6.13.9 (Not cross compatible)
• MCU 10.6.18.21 (Not cross compatible)
• MCU 10.10.20.15 (Not cross compatible)
• MCU 10.10.20.18 (Not cross compatible)

• v3.0.0.1.mmi.e (Not cross compatible)
• v3.1.0.1.mmi.e (Not cross compatible)
• v3.1.1.2.mmi.e (Not cross compatible)
• v3.1.1.4t1.mmi.e (Not cross compatible)
• v3.1.1.6s.mmi.b (Not cross compatible)

• MCU 10.10.24.15 (Not cross compatible)
• MCU 10.12.3.17 (Not cross compatible)
• MCU 11.5.2.12 (Not cross compatible)

• 2863
• 5140
• 6561
• 8032
• 3782
• 4091
• 2233
• 5920
• 9281
• 6376
• 1058
• 2916
• 5025

Custom Firmware

Note: As of 2021, I do not recommend flashing the custom firmware anymore. It is quite outdated and there is no real need for it anymore since the majority of features are available in the default firmware by now. Do not flash the custom firmware unless you know what you are doing.

Universal [ NBT ] [ ISPBOOOT.BIN ]
Note: This update will work on any A-Unit no matter the seller (does not work on B-version!)
Note2: A word regarding MCU updates: With this update you can only flash the MCU updates by Bimmertech. Flashing the default MCU from Andream/Carlinkit etc is only possible on their firmware. Currently there is no need to do anything (no new features etc), so you can leave everything as is. Also note that Bimmertech transforms the first digits of the MCU version from '20' to '10'.

• v2.0.B0.mod (for BMW) (no PIN) (Cross compatible) (based on: v2.0.2.7t0.mmi.b)
• v2.0.M0.mod (for MINI) (no PIN) (Cross compatible) (based on: v2.0.2.7t0.mmi.b)

• MCU 20.06.02 custom (only flashable on v2.0.x0.mod)

Note: You will not be able (yet) to flash any CIC MCU-Updates on this version. Make sure to flash them beforehand if you are not running the latest version and want to update.

• v2.0.B1.mod (for BMW) (no PIN) (Cross compatible) (based on: v2.0.2.7t0.mmi.b)

• v1.0.A0.mod (PIN: 2863) (Not cross compatible) (based on: v2.1.0.6.gpe.b)- Link removed -

• v1.0.C0.mod (PIN: 4091) (Not cross compatible) (based on: v9.2.5.yl.b)- Link removed -

• Android Auto Widescreen Fix
• Android Auto DPI Fix
• Autolink Mirroring Screen Size Fix
• Renamed MMI to BMW-MMI/MINI-MMI for Carplay and AA
• Replaced MMI icon with BMW/MINI icon
• Replaced car image on integrated PDC/camera screen
• Changed icons to Blue when highlighted
• Removed update / key checks
• BMW/MINI Boot Logo
• Custom Flash/update screen

• Android Auto Widescreen Fix
• Custom boot logo (BMW icon)
• Replaced Z4 car image on integrated PDC/camera screen
• Black flash/update screen

However, it is important to note that there is no scientific evidence to support the existence of witchcraft or its connection to Android Auto. The concerns and fears surrounding this topic can be attributed to superstitions and misconceptions rather than factual evidence. Android Auto, like any other technology, operates based on established engineering principles and software algorithms, with no room for supernatural interference. To alleviate these concerns, it is crucial to promote awareness and education regarding the functioning of Android Auto. By understanding the technical aspects and limitations of the system, users can navigate the software with confidence, knowing that their safety and control are not compromised by mythical forces. Additionally, manufacturers and developers should continue to improve and update the software to address any potential glitches or vulnerabilities, providing users with a reliable and secure experience. In conclusion, the idea of a witchcraft connection with Android Auto is rooted in superstition and misinformation. It is essential to rely on facts and scientific understanding when assessing the capabilities and limitations of technology. By dispelling these irrational beliefs, users can fully embrace the benefits of Android Auto without unnecessary fear or apprehension..

Reviews for "The Witchcraft Connection: Is Android Auto the Future of Automotive Technology?"

1. Sarah - 1 star - I was really disappointed with "The witchcraft connection android auto". The plot was all over the place and the characters were poorly developed. I couldn't connect with any of them and I found myself losing interest halfway through. The writing style was also cumbersome and confusing, making it hard for me to follow along. Overall, I would not recommend this book to anyone looking for a well-written and engaging read.

2. John - 2 stars - "The witchcraft connection android auto" had an interesting premise, but it failed to deliver on many levels. The pacing was extremely slow, and I found myself easily bored while reading. The dialogue between the characters felt forced and unnatural, making it difficult to believe in their relationships or invest in their stories. Additionally, the ending felt rushed and unresolved, leaving me feeling unsatisfied. Overall, I was disappointed with this book and would not recommend it to others.

3. Emily - 2 stars - I had high hopes for "The witchcraft connection android auto" based on the synopsis and positive reviews, but unfortunately, it fell flat for me. The writing style was overly descriptive and verbose, slowing down the narrative and making it hard to stay engaged. The characters lacked depth and development, and their actions often felt illogical and inconsistent. Additionally, the world-building was underwhelming and left many unanswered questions. Overall, this book was a letdown and not something I would recommend to others.

4. Mike - 1 star - "The witchcraft connection android auto" was a complete waste of my time. The story was convoluted, with too many subplots that added unnecessary confusion. The characters were shallow and uninteresting, and their motivations were poorly explained. The writing was also full of grammatical errors and awkward sentence structures, making it a chore to read. I strongly advise against picking up this book if you're looking for a well-written and engaging story.

5. Jessica - 2 stars - I struggled to get through "The witchcraft connection android auto". The plot was messy and disjointed, with no clear direction or purpose. The dialogue felt stilted and unnatural, making it hard to believe in the characters' interactions. Additionally, the pacing was slow, and the story failed to hold my attention. While the concept had potential, the execution fell short. Overall, I wouldn't recommend this book to others unless they have a lot of patience and a high tolerance for poorly written narratives.

Witchcraft Unleashed: How Android Auto Harnesses its Powers