10-27-2020, 12:47 AM
I have a Mini F60 and my goal is to get to NBTevo version V. Flashing using psdzdata 4.25.40 (latest as of now) gives me only version U (NBTevo_U19384I). I know version V on Minis is a thing because that's the one that supports fullscreen Carplay unlock over cable.
I poked around in the binary data files for the HU_NBT module and there are definitely bin files in the distribution with "V" version numbers:
Since I know next to nothing about how all this works, can someone help me understand how the flash/calculation process selects one data file version over another? Is that stored in the car or in the psdzdata distribution? And, more importantly, is there a way to encourage esys to select a newer version for my car?
Thanks!
I poked around in the binary data files for the HU_NBT module and there are definitely bin files in the distribution with "V" version numbers:
- "NBTevo_V20153J" from btld_00001ffd.bin.007_008_010
- "NBTevo_V20153I" from btld_00001ffd.bin.007_020_010
Since I know next to nothing about how all this works, can someone help me understand how the flash/calculation process selects one data file version over another? Is that stored in the car or in the psdzdata distribution? And, more importantly, is there a way to encourage esys to select a newer version for my car?
Thanks!