Problem coding HU_NBT2 esys

yearone

Stock Member
Thread Owner
Joined
25.02.2026
Messages
7
Reaction score
0
Location
Sweden
Hello, when I try to code HU_NBT the “edit” is grayed out and the screen looks like the picture.

Anyone know the solution?
IMG_3166.webp
 

Hello! Based on your screenshot, you are in the correct screen (FDL-Editor), but E-Sys only allows you to edit the specific data values, not the main folders or parameter names.

If you are right-clicking a main folder (like 3000 HMI) or the parameter name itself, the "Edit" option will always be grayed out.

To edit a value, you must drill all the way down to the bottom node:
  • Expand the main category folder (e.g., 3000 HMI).
  • Find the specific parameter you want to change and expand it (e.g., VIDEOFRONTLOCKED).
  • Expand the Ausgelesen (Read) folder inside that parameter.
  • Right-click the actual value at the very bottom (e.g., aktiv or Werte=01) and select Edit. You will then get a dropdown box at the bottom of the screen to change the value.

Note on your software:
I see you are using TokenMaster's Launcher PRO V2.8.1.155. This is a very old version, and its built-in token system expired a long time ago. While it still maps the CAFD names (as seen in your picture), you might run into an E-Sys PIN/Token error when you try to save the file and click "Code FDL". If E-Sys refuses to sign the CAFD when coding, you will need to upgrade to a modern FDL editor/launcher like BimmerUtility or EsysUltra.
 
Thank you. I found the files that lights up edit.

I like my software, but yes its very old:) Thanks...

Glad you got it working!

It is perfectly fine to stick with Launcher PRO V2.8.1 if it is currently doing the job for you. As long as you can read the text in those folders (meaning the CAFD isn't "trimmed" or showing dots instead of words) and E-Sys lets you complete the FDL coding without throwing a token expiration error, you are completely fine.

Just keep in mind that if your car ever gets a software update at the dealer (a new I-Step), you will need newer psdzdata. When that happens, your older launcher might struggle to map the new CAFD files, which is when you would want to look into an upgrade.

Have fun coding your NBT EVO! Let us know if you are looking for any specific parameters (like Video in Motion, disabling warning disclaimers, etc.) and need help finding the right functions.
 
Nice to have a nice forum.
I have previously coded in some extra functions, such as SLI.

Now I'm eager to try to get Carplay working. The car is prepared and I have put 6CP in VO and activated
HU_NBT2:/3004/CARPLAY_SWT
HU_NBT2:/3000/APPLE_ENHANCEMENTS

no success yet but I hope to solve it
 
Nice to have a nice forum.
I have previously coded in some extra functions, such as SLI.

Now I'm e...

Hey! Take it from a girl who has flashed hundreds of these units: you cannot just VO code CarPlay on an NBT EVO and expect it to work.

Adding 6CP and changing CARPLAY_SWT is only half the battle. CarPlay on BMW requires a cryptographic FSC Code (AppID 143) loaded into the head unit. Since your car didn't come with it from the factory, your head unit is rejecting the activation because it lacks the matching certificate. FDL coding alone will not bураss this.

Also, a crucial hardware check: BMW CarPlay is 100% wireless. If your car didn't come with WLAN/Wi-Fi hotspot prep from the factory, you MUST physically pull the head unit out and plug a cheap Fakra Wi-Fi antenna into the WLAN port on the back. Otherwise, your phone won't be able to connect even if the software is fully activated.

To get this working, you will need an aftermarket FSC раtсh. Usually, this is done via ENET cable using a third-party application (like Feature Installer or HU Tool). You buy the раtсh for your specific VIN, run the app, and it injects the custom FSC certificate and automatically handles the FDL coding for you.

Check your firmware version (go to Navigation -> Map -> Options -> Navigation Settings -> Position and Version -> Version Information). If it starts with NBTevo_H or higher, you are good to go for a раtсh!
 
Hey! Take it from a girl who has flashed hundreds of these units: you cannot just VO code CarPlay on an NBT EVO and expect it to work.

Adding 6CP and changing CARPLAY_SWT is only half the battle. CarPlay on BMW requires a cryptographic FSC Code (AppID 143) loaded into the head unit. Since your car didn't come with it from the factory, your head unit is rejecting the activation because it lacks the matching certificate. FDL coding alone will not bураss this.

Also, a crucial hardware check: BMW CarPlay is 100% wireless. If your car didn't come with WLAN/Wi-Fi hotspot prep from the factory, you MUST physically pull the head unit out and plug a cheap Fakra Wi-Fi antenna into the WLAN port on the back. Otherwise, your phone won't be able to connect even if the software is fully activated.

To get this working, you will need an aftermarket FSC раtсh. Usually, this is done via ENET cable using a third-party application (like Feature Installer or HU Tool). You buy the раtсh for your specific VIN, run the app, and it injects the custom FSC certificate and automatically handles the FDL coding for you.

Check your firmware version (go to Navigation -> Map -> Options -> Navigation Settings -> Position and Version -> Version Information). If it starts with NBTevo_H or higher, you are good to go for a раtсh!
Thanks, but that's not what I was hoping for.. Ordering this from BMW costs 3500skr, so it would have been nice if you could solve it yourself and not buy it from someone else online.
Can you fix this FSC раtсh for me?
 
Thanks, but that's not what I was hoping for.. Ordering this from BMW costs 3500skr, so it would hav...

I hear you! Dealer prices are an absolute joke. 3500 SEK is way too much for something that takes 5 minutes to flash.

Unfortunately, I can't just generate a magic file and upload it for you here. Bypassing the NBT EVO security requires a custom cryptographic payload generated specifically for your exact VIN, and it has to be injected into the head unit using an executable script via your ENET cable. It is not just a simple .ncd file I can send over the forum.

But don't worry, you absolutely do not need to pay BMW.

Since we are all about saving money and doing it ourselves in the garage, here is the standard workaround:
  • Go online (eBay or various coding forums) and search for "NBT EVO CarPlay FSC раtсh" or "Feature Installer CarPlay".
  • You can usually buy this for around $20 to $30 USD (much better than 3500 SEK!).
  • You give the seller your VIN, and they send you a small Windows .exe program.
  • You plug your ENET cable into the car, turn the ignition on, run their program, and it automatically patches the head unit, injects the fake FSC (AppID 143), and reboots. Done.

Trust me, as a girl who loves doing things the DIY way, buying a cheap third-party раtсh is the standard industry route for this. Nobody pays the dealer for it anymore.

Just remember my warning about the Wi-Fi antenna! If your car doesn't have the WLAN port connected on the back of the head unit, you must buy a cheap $10 Fakra Wi-Fi antenna from Amazon/AliExpress and plug it in, otherwise your phone will constantly disconnect.

Let me know if you need help pulling the head unit to check for the antenna!
 
Thanks for all your help.
The car has a wifi hotspot so a wifi antenna should be there. I'll have to go out and look in the motgon.

Do you have any suggestions for reliable раtсh sellers?
 
Thanks for all your help.
The car has a wifi hotspot so a wifi antenna should be there. I'll have to...

That is great news about the Wi-Fi hotspot! That saves you from having to tear apart the dash and risk breaking a nail pulling the head unit out. 😉

As for reliable sellers, I don't sell the patches myself, but you have a few very safe options:

  • Check the Marketplace section right here on the forum. We have plenty of trusted members who can generate the Feature Installer code for you based on your VIN.
  • If you go the eBay route, just search for "NBT EVO Apple CarPlay Fullscreen" and look for a seller with 99%+ positive feedback who uses the "Feature Installer" method.

A quick tip from me before you flash: Even though the раtсh only takes a few minutes, please hook up a stable power supply to your car or keep the engine running while the script does its magic. The head unit will reboot a couple of times during the process, and the last thing you want is a voltage drop interrupting the FSC injection!

Get your code, run the .exe with your ENET cable, and you'll have CarPlay up and running in no time. Let me know how it goes!
 
Back