NBT EVO HU error when inject CAFD VO

[snex]

Please help add CAFD to HU_NBT2.
My car has a factory configuration and nothing has changed/added in it and NBT EVO if factory from this car.

I coded different blocks (KOMBI/KAFAS2/PMA2/HU_NBT2/....)

The car has American settings and I wanted to change the settings to European. I add all sorts of conveniences such as automatically close mirrors / display road signs / FM radio / display 360 cameras while driving and other things.

After I changed the

HU_NBT2 -> country us->ece

My screen turned black and the CAFD file disappeared.
Also short VIN number is displayed as HU_NBT2 [63] [яяяяяяя]




I've already tried:

Connect => Read FA (VO) => Activate FA (VO) => Read (ECU) => Click on HU_NBT2 => Click on "Detect CAF for SWE" => Select the CAFD from shown => Select OK => Right-Click on HU_NBT2 (the ECU itself not the underlying CAFD) => Select CODE.

FSC-extended -> WriteDataByIdentifier

and always the same error:
Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession
Service WDBI_PLAIN returned a negative response with response code requestOutOfRange

As far as I understand NBT EVO is not a locked. (Because the fsc code AppID 368(0x170) FSCStatus not available)

About this device:
Model: NBT EVO HU
Model No: HB B211 EC:308 HW:3.2
Version: US
Date 42/16
All FSC codes are standard from the factory. and status says all is well.
No patches or modifications were made.
carplay/mirroring works without using FSC codes
i-step/i-level actual F025-18-03-530
TELEPHONE: TB-006.018.050
MEDIA: MB-006.018.050
HMI: 006.026.050
Software version on map NBTevo_N (fsc code 121 disappeared after coding)

How do i get a cafd file back?
Maybe I need to look for a problem in the settings of other ECU? Possibly KOMBI/Kafas2/....?

I think that my VO is completely original, I don't understand whether it makes sense to change something there.

Please tell me where to look for a solution?

Similar topics:
https://www.bimmerfest.com/threads/h...signal.979009/
https://f30.bimmerpost.com/forums/sh....php?t=1451103
https://www.cartechnology.co.uk/show....php?tid=40450
https://cartechnology.co.uk/showthre...d=67649&page=2
https://cartechnology.co.uk/showthre...=40782&page=19
https://cartechnology.co.uk/showthread.php?tid=52223
https://www.bimmerfest.com/threads/n...yyyyyy.1260730

[RED_Y_]

Did you make a back up of CAFD/NCD files before you started coding?

[snex]

Yes. I restored it from esys logs which worked successfully before the change

country us->ece

. So i have all the logs and there are all these CAFD files.

[RED_Y_]

I might be wrong but I thought that you need some VO coding in order to get the region changed. Looks like similar problem described here: https://mhhauto.com/Thread-EVO-id6-r...ange-US-to-ECE
I am not that experienced with coding, you might need help from someone like shawnsheridan or kubax86

[snex]

I'm wondering if this problem can be caused by changing the CAFD files of other ECU (KOMBI/KAFAS2/....)?

I will try to experiment as it is written in this answer.
https://www.bimmerfest.com/threads/n...#post-12469838

It seems to me that the solution is not to replace the firmware or any manipulations with tool32 / hutools 2.6.

I think that esys / ista-d should deal with this problem, but I still can't figure out how.

[shawnsheridan]

Originally Posted by snex

...After I changed the

My screen turned black and the CAFD file disappeared.
Also short VIN number is displayed as HU_NBT2 [63] [яяяяяяя]

As far as I understand NBT EVO is not a locked. (Because the fsc code AppID 368(0x170) FSCStatus not available)

EVO is not Component Protection Locked, it it is VO Code Locked. PM sent.

[snex]

Wrote PM, waiting for an answer.
How to understand "VO Code Locked" it is something that needs to be repaired on NBT using a patch / tool32 / hutool 2.6 (my nbt evo has 18-3 firmware)

or it is a problem that I need to configure something correctly in SVT and then
when i see the correct display VIN numbers in HU_NBT2 [63] [correct]
then the CAFD should probably be accepted.

Where to look for this error? Inside in NBTEVO firmware or maybe some eeprom or hard drive?
Is the error completely hidden in the correct ESYS -> SVT settings?

[kubax86]

Originally Posted by snex

Wrote PM, waiting for an answer.
How to understand "VO Code Locked" it is something that needs to be repaired on NBT using a patch / tool32 / hutool 2.6 (my nbt evo has 18-3 firmware)

or it is a problem that I need to configure something correctly in SVT and then
when i see the correct display VIN numbers in HU_NBT2 [63] [correct]
then the CAFD should probably be accepted.

Where to look for this error? Inside in NBTEVO firmware or maybe some eeprom or hard drive?
Is the error completely hidden in the correct ESYS -> SVT settings?

Best way is to get a patch then playing around. E-Sys settings won't help you in this case.

[snex]

Сan i generate this patch with Hutools 2.6?
What should my current steps be?
Please help me find a solution on how to bring it all back to life.
My HU_NBT2 have i-step/i-level 18-3.
Can the patch damage the options supported by the head unit?

AppID 111(0x6F) FSCStatus accepted
AppID 160(0xA0) FSCStatus accepted
AppID 366(0x16E) FSCStatus accepted
AppID 367(0x16F) FSCStatus accepted

609 Navigation System Professional
645 Radio Control Us
655 Satellite Radio
610 Head Up Display
688 Harman/kardon Surround Sound
6AC Intelligent Emergency Call
6AE Teleservices
6AK Connecteddrive Services
6AM Real Time Traffic Information
6AP Remote Services
6CP Apple Carplay Preparation
6NW Telephony With Wireless Charging
6WD Wifi Hotspot

[shawnsheridan]

Originally Posted by snex

Сan i generate this patch with Hutools 2.6?

No.

[snex]

Thanks to everyone who tried to help. The problem was solved by a paid solution using remote unlocking "VO coding" and then I was able to insert my CAFD file.

Three people offered me this service, I chose the one who was the first.
Thank you shawnsheridan for recommending me Gerry

Also, if someone knows how to do it on their own then I will be interested in how close I was to the solution)

[shawnsheridan]

Originally Posted by snex

Thanks to everyone who tried to help. The problem was solved by a paid solution using remote unlocking "VO coding" and then I was able to insert my CAFD file.