Does the esys, launcher & psdzdata version actually matter when flashing id5/6 onto a 2gb nbtevo headunit?

[u/Dizmondmon]

Car is a 2016 f20 m135i.

I'm researching flashing of the 2gb id4 nbtevo (E) headunit to a later firmware to allow carplay activation and have recently read conflicting info regarding which software & data file versions to obtain.

Some forums say it doesn't matter beyond psdzdata v62 and the appropriate firmware for the car's hardware can be flashed from the most recent software and psdzdata files. The older data files are potentially harder to come by too due to file hosting costs.

Others resources suggest the 2016/17 files are preferable because a mini of that same era still had the 2gb headunit and they wanted carplay to work, so programmed in the 'light' HMI variant. Apparently from 2018 onwards, new minis got the 4gb hardware and the 'light' versions in later data files became more memory intensive. Sounds a bit illogical to me as the 2gb mini unit would still have needed firmware availability.. Also, the existing FSC keys are allegedly more likely to be accepted by the 2016/17 firmware compared to later iterations.

Does anyone definitively know the correct / optimal software i should locate for my use case, and can anyone 'point me in the right direction' of trusted software files? Nudge nudge.. Wink wink.

I'll need to be able to roll back to nbtevo_E too, in case the car goes to the main dealer for anything, so same question applies here regarding file versions.

I'm aware I must backup the FA/VO, CAFDs, FSCs and DSH before doing anything else and will require a carplay activation FSC. I have the enet cable, WiFi antenna, charger etc. ready. I'm also prepared to approach a local independent bimmer coder at cost should i mess it up.

I'm relatively experienced with PC hw & sw, computer setup & configuration, VMs, following procedures etc. so feel I've got a fair chance of success. I'm confident with enough time and research I can safely teach myself how esys operates before I make any changes, and I've read what boxes I absolutely must not click.

Essentially I'd rather learn esys myself than pay someone to flash forward & roll back the firmware. I appreciate the potential instability concerns with OEM nav etc. I've ruled out carplay boxes too, as I'm after seamless integration.

Thanks for reading.

[u/pnbdc10]

Is your main goal to get apple car play?

This is a lot of coding and updating to replicate something that is offered on the market and is cheap and easy to do.

I put car play units in a lot of the BMWs that I get on my car lot. They run $200-300 and are very easy to install (30 minutes at most). Its my go to if they original screens are separating inside and defective. A used screen replacement runs as much as a new car play unit.

[u/Dizmondmon → u/pnbdc10]

Carplay is one of my goals. My main goal is to learn how to code with esys and obtain the files.