Signed-off-by: AnilShebin <anilshebin@gmail.com>

Signed-off-by: AnilShebin <anilshebin@gmail.com>

Signed-off-by: AnilShebin <anilshebin@gmail.com>

Needed for FBE decryption

Wasn't properly setting props which was causing some RUI1 roms to fail at flashing

RUI2 based ROMs currently use nicky codename while RUI1 based ROMs use RMX1971 codename. We want to support both.

Changes to kernel haven't been tested on other devices so it makes sense to rebrand to specific device to avoid confusion when sharing recovery images.

PLATFORM_VERSION := 127
does not work anymore and will lead to failing decryption on a13.

PLATFORM_VERSION := 16.1.0
will not affect a12 decryption and will also add support for a13

https://github.com/pjgowtham/android_kernel_oplus_sdm710

* TWRP build boots up on old fw, however device identifier nodes are broken. So, we differentiate devices based on fp sensor hardware and chipset
* Asserts are also done to support standalone custom roms and unified builds by me
* Asserts are also fixed to support stock realme ui 1 flash

* We have already defined it in twrp.flags and aren't in a hurry to mount them.

pjgowtham :

* This needs patching bootable/recovery
* This flag is necessary for flashing stock android 9(ColorOS) and android 10(RUI1)
* RUI2 doesnt do treble compatibiliy.zip check

* Hoping PRODUCT_ENFORCE_VINTF_MANIFEST will also be inherited from full treble build vars

* TW_NO_SCREEN_BLANK fixes the issue

* Blobs sourced from RUI2 early access builds
* Also enable twrp flags to support decryption

* References - https://github.com/bigbiff/android_device_oneplus_kebab/blob/android-11/recovery/root/system/bin/unified-script.sh

* Also remove props that are moved to init.recovery.usb.rc