[YucA]

Casually looking for an nbt evo hu to upgrade my 2015 f31. I have factory reverse camera, 8.8” screen, touch idrive and the usb port in my glovebox.

Came across the hw 3.1 unit pictured below. I’m not worried about missing gps as we never use onboard nav (will be using CarPlay exclusively), but I don’t want to lose any other functionality (tpms/vehicle displays). Will missing the 2nd apix port or anny others affect me?

After acquiring the new hu, I will need the main harness adapter and WiFi antenna, and screen harness that that lowers voltage to 9v, correct?

Also as I understand it, nbt evo only supports wireless CarPlay, there is no way to enable wired CarPlay correct?

Back of hu in question:


Thanks!

[thatgarrett]

What’s the serial number on the unit? Should start with a B followed by a few numbers- that will tell you if it has the 2 or 4 GB RAM. When I did my retrofit, I used a HW 3.2 unit that was one of the earliest versions that had the required 4GB RAM, that’s the only thing I’d check before pulling the trigger.

I did the same as you- no GPS port and haven’t missed it at all to be honest, thought I might with the HUD not giving turn by turn directions but the ease of using CarPlay to put in addresses far outweighs that, plus free traffic info.

No need for the second APIX connector, you can’t use it on the F3X platform, that’s for like a 7 series or something that used that connection to power the 6WB digital cluster, not required on our platform though.

Do you have an APIX1 screen or APIX2? If a 2, you don’t need the 9V regulator harness, otherwise you will. You also don’t need a harness adapter, I think your pin out should be the same, even for reverse camera and mic, since you already have an NBT. Should be a pretty straightforward swap, just get the WLAN antenna and you’ll be set. Also get someone who can code it properly and inject FSC codes, unless you know how to do that yourself.

Also yes, CarPlay is wireless only

[YucA]

thatgarrett Thanks for the quick response, appreciate it.

I was wrong, actually seems to be a 3.2. Here’s a shot of the label:


What number does it have to be after the “hub b” to confirm its 4gb

[thatgarrett]

As long as it starts with “B2…” you’re good, that one should work( I think that’s the same serial number as mine, or close to it, so you should be good to go with that one!

[YucA]

thatgarrett Thanks again for all the info. Pulled the trigger on that one!

[fe7565]

Originally Posted by YucA

Casually looking for an nbt evo hu to upgrade my 2015 f31. I have factory reverse camera, 8.8” screen, touch idrive and the usb port in my glovebox.

Came across the hw 3.1 unit pictured below. I’m not worried about missing gps as we never use onboard nav (will be using CarPlay exclusively), but I don’t want to lose any other functionality (tpms/vehicle displays). Will missing the 2nd apix port or anny others affect me?

After acquiring the new hu, I will need the main harness adapter and WiFi antenna, and screen harness that that lowers voltage to 9v, correct?

Also as I understand it, nbt evo only supports wireless CarPlay, there is no way to enable wired CarPlay correct?

Back of hu in question:
Attachment 3933902

Thanks!

Some info here for later when you install it: https://f30.bimmerpost.com/forums/sh....php?t=2180790

[YucA]

Originally Posted by fe7565

Some info here for later when you install it: https://f30.bimmerpost.com/forums/sh....php?t=2180790

Thanks for that link. Hadn't seen that thread before, tons of useful info. Just got the HU, now I need to remove the screen to see if it's 12v or 9v, and if I need the wifi cable. Need the oabr cable too.

Definitely going to attempt it all myself.

[YucA]

Got the headunit and the wifi cable on hand. Waiting for the oabr connector, I will be making my own oabr to ethernet.
Using T568B RJ45 standard it seems like it should be (correct me if I'm wrong) :
Orange/White : OABR pin 17
Orange : OABR pin 19
Green/White : OABR pin 18
Green : OABR pin 20

If I need to adjust the voltage for the screen, I have the necessary hardware on hand to modify an existing screen cable, so that shouldn't pose an issue.

Most of the diy retrofits are using an atm emulator or proper ATM, but I am not going that route and just want to make sure I don't brick the evo. I've acquired HUtool 2.6 so I should be able to get the FSC codes required, but I'm still a bit unclear about jailbreaking/updating the vin and system and would appreciate any clarification possible.

[steve@codemybimmer]

Originally Posted by YucA

Got the headunit and the wifi cable on hand. Waiting for the oabr connector, I will be making my own oabr to ethernet.
Using T568B RJ45 standard it seems like it should be (correct me if I'm wrong) :
Orange/White : OABR pin 17
Orange : OABR pin 19
Green/White : OABR pin 18
Green : OABR pin 20

If I need to adjust the voltage for the screen, I have the necessary hardware on hand to modify an existing screen cable, so that shouldn't pose an issue.

Most of the diy retrofits are using an atm emulator or proper ATM, but I am not going that route and just want to make sure I don't brick the evo. I've acquired HUtool 2.6 so I should be able to get the FSC codes required, but I'm still a bit unclear about jailbreaking/updating the vin and system and would appreciate any clarification possible.

If this head unit is on firmware 18-11-5XX and up, HU Tool won't work and you'll need Feature Installer.

Show me what you see on the SVT on E-sys under HU_NBT2 or PM me the VIN of the donor and I'll be able to tell what's involved in having it FSC activated.

[YucA]

Originally Posted by steve@codemybimmer

If this head unit is on firmware 18-11-5XX and up, HU Tool won't work and you'll need Feature Installer.

Show me what you see on the SVT on E-sys under HU_NBT2 or PM me the VIN of the donor and I'll be able to tell what's involved in having it FSC activated.

This is something I wasn't aware of. Thanks for the heads up! I'll be shooting you a pm.

[YucA]

I finally got a chance to work some more on this. Installed the new head unit and plugged everything in. I made my own oabr cable and APIX cable to reuse my original 8.8" screen. Took a bit of messing around to figure out what I had to do but this is what worked out for me for the most part... Questions below.

1. I connected e-sys via obd and saved my FA and SVT for cya purposes.
2. Disconnected e-sys and hooked up to the OABR cable and connected to the evo using "Connection via Gateway URL" and 169.254.199.9.
3. Expert mode --> FSC Extended
4. Write 0x63 to choose NBT_evo
5. Click on Identify
6. Add WriteDataByIdentifierVIN to job list and write typed my cars VIN.
7. Click on Start
8. Expert mode --> Coding
9. Load FA & SVT that I previously saved.
10. Click on "Detect CAF for SWE", selected the last bolded CAFD file from the list and then click on "Code" to code it to the NBT_HU

Before coding, my display had the "No Signal" error which I understood as normal. I thought I would have to manually modify the coding options for it to fully support the APIX1 screen but that surprisingly was not the case! After the steps above, the screen just started working. It's still slightly off in the main menu area, but oddly it looks fine everywhere else? Also, CarPlay just works? I thought this would have to get coded!? I tested phone calls and music and it all just works? I stopped there and haven't tested much else other than that and the FM radio. I will not be using gps or connected apps, but would like to make sure the screen is 100% and I still have my car options like TPMS, reverse cam etc (which I didn't dig into the menu to look for)

Now that I've gotten this far, I still need to finalize the install and fix the odd screen bug. Pics below. Any advice or help would be greatly appreciated.

Also I did confirm these settings were set:
voltage set to ~8.4v
Apixmode = APIX1
Color Depth = 18
Com Mode = spi
Resolution and screen size too.

Screen bug and CarPlay:










APIX 2 to 1 mod: