[Samsung Galaxy Note 9 (Exynos) ROMs, Kernels, Reco] _alexndr:
Changelog

v7.4

(starting from N960NKSU3FUC1 DevBase):

- Fixed unzip issue which caused unexpected installation termination - applies to TWRP 3.5.0_9-1 and newer

v7.3

(starting from N960FXXU5DTCA DevBase):

- Fixed bootloop issue in case of Android Q and "noroot" scenario - thanks to @Zackptg5 for the up to date dm-verity disabler

v7.2

(starting from N960FXXS5DTB6 DevBase):

- Fixed bootloop issue in case of Android Q and encrypted devices (applies to dirty update)

v7.1

(starting from N960NKSU3DSLC DevBase):

- Potential fix for "make_ext4fs: not found" error in newer TWRP versions and in result "Failed! Not enough space..." message appears while applying CSC during install (applies to N960x devices)

v7.0

(starting from N960FXXU4DSLB DevBase):

- Initial support for Android Q / system-as-root devices

v6.0

(starting from N960FXXS2ARL3 DevBase):

- Introduced logging entire installation process (to devbase_install.log file, placed in /data or /cache in case of encrypted devices). These logs may significantly increase the possibility of my help in case of problems with/after installation

- Major imrovements/bugfixes/optimizations related to Android Pie support (e.g. takes care about special SELinux contexts for /odm content, introduced in Pie)

- Removed SuperSU support. Changed allowed "root" variable value in options.prop to true/false (backward compatible with old options.prop)

- Removed "skipblcp" option - baseband/modem will be always updated, bootloader need to be flashed separately (update is usually not mandatory)

v5.9

(starting from N960FXXS2ARH6 DevBase):

- Changed device detection method to bootloader's prefix (instead of ro.product.*)

- Improved support for applying custom mods automatically at each ROM's install/update, introduced in v5.6 (added support for etc, fonts, media & usr directories in {storage}/devbase/system)

- Added support for custom {storage}/devbase/post-installation.sh script

v5.8

(not released for N960F):

- Improved unzip_flash function in the installer to detect properly more flashing errors (e.g. EXT4 partition mismatch)

v5.7

(not released for N960F):

- Improved/expanded built-in RMM lock prevention (thanks to @jesec for idea of overriding properties via factory.prop)

- OEM unlock status will always be displayed correctly in Developer options (to avoid confusion) with stock kernel included in the DevBase ROM

v5.6

(not released for N960F):

- Added "App Lock" feature (Settings -> Advanced features)

- Added Xposed framework as installation option (it is NOT forced by default - you need to force it manually while installing with Xposed first time, e.g. by "xposed" string in ZIP's file name, but next ROM's updates will detect and apply Xposed profile automatically, unless you wipe /system - then auto detection is not possible)

- Added support for applying custom mods automatically at each ROM's install/update by placing modded apps in {storage}/devbase/system/(priv-)app or placing modded framework files in {storage}/devbase/system/framework (where {storage} may be: /sdcard, /external_sd or /usb-otg)

v5.5

(not released for N960F):

- Added support for flashing optional, CSC related partitions ($OMR, $PRELOAD)

- Added possibility to update recovery (optional, performs update if exists $NAME/images/recovery.img)

- Return to using only the original XML files in the CSC package (thanks to @fei-ke for omc-decoder)

- Partition(s) may be wiped only by writing new block's image

- Minor optimizations / improvements in the installer

v5.4

(not released for N960F):

- Big step forward in DevBase ROM customization ability - almost all current ROM features (hidden up to v5.3) have been moved to options.prop (you will be able to easy add new or remove current feature)

- Return to dm-verity-opt-encrypt boot patcher if necessary (wherever it works well, there are still devices which need "no_verity" function introduced in v5.1)

- Initial support for forcing (changing) CSC in case of devices with /odm as CSC location

- Minor optimizations / improvements in the installer

v5.3

(not released for N960F):

- Improved algorithm of search & change "ro.security.vaultkeeper.feature" property to 0 (/system & /vendor)

v5.2

(not released for N960F):

- Added support for devices with /odm as CSC location

- Added support for flashing $ODM, $VENDOR, $KEYSTORAGE, $DQMDBG images

- Added support for custom debloat list and custom CscFeature list in options.prop

- options.prop file format has been changed to CR/LF (Windows) - more noob-proof solution, user can edit a copy of options.prop file even in Windows Notepad (the installer still supports ANY text format of options.prop file - Win/Unix/MAC)

v5.1

(not released for N960F):

- Created new "no_verity" function in the installer, compatible with Samsung's Oreo, based on @Chainfire's patch tool (no-verity-opt-encrypt has been removed). In case of Oreo & Magisk as root solution - "no_verity" function will be used as additional support for patching fstab* (as long as Magisk does not do it correctly)

v5.0

(not released for N960F):

- SYSTEMLESS DevBase has been removed due to the fact, that in case of modern devices/firmwares we need to perform many changes physically in /system anyway, so it loses the sense of use here. If you liked it - you can still install it separately from HERE (it does not need to be re-installed after ROM update as it is installed in /data)

- Added "skipblcp" option to let users skip BL/CP update (additionally it disables auto-reboot when the installer finished work as it is just not necessary then)

- Added "phydebloat" option to let users choose beetween virtual and physical debloat (to get more space in /system)

- Other (minor) optimizations & improvements

v4.6

(not released for N960F):

- Initial support for devices with /system/omc as CSC location

- SYSTEMLESS DevBase updated to v2.0 (see changelog HERE)

- Added possibility to force CSC by renamig ZIP filename. Due to the fact that trere are many different CSC and it is possible that $ZIPNAME may contain a CSC accidentally - to force CSC you need to put CSC in $ZIPNAME at the beginning and CSC must be followed by "_". Example $ZIPNAME (to force CSC DBT): "DBT_N960FXXU3xxxx_DevBase.zip"

- Added auto efs-backup during install. Installer will create first backup (efs_backup.img.gz) and recent backup (efs_recent.img.gz). The installer will prefer external storage as default backup location (/external_sd or /usb-otg) due to encryption support. MD5 sum and restore command will be stored in efs_backup.txt or efs_recent.txt file

- Other (minor) optimizations & improvements, e.g. added more error messages in case of something went wrong during install

v4.5

(not released for N960F):

- Added new "rescue" option (readable only as string in ZIP file name due to the fact, that we will need this option rarely). It can be a potentially very helpful option in case of bootloop @ encrypted device, caused by a systemless mod/module/xposed stored on /data (without access to /data from TWRP) - more info in post #1

- SYSTEMLESS DevBase updated to v1.14 (see changelog HERE)

v4.4

(not released for N960F):

- Added new "encrypt" option (readable only as string in ZIP file name due to the fact, that we need to do it only once). Now you can easy encrypt all data in your device, just during the ROM upgrade (without data loss).

- SYSTEMLESS DevBase updated to v1.13 (see changelog HERE)

v4.3

(not released for N960F):

- "root.supersu" & "root.magisk" variables in the options.prop file have been replaced by one "root" variable (dropped possibility to install both - SuperSU & Magisk - due to the fact that Magisk v13+ does not support SuperSU as root solution)

- SYSTEMLESS DevBase updated to v1.9 v1.12 (see changelog HERE)

v4.2

(not released for N960F):

- Added possibility to add systemlessly NEW apps to /data/devbase/system/(priv-)app (up to 5 apps in "app" & 5 apps in "priv-app"). The only condition is that you need to rename its directories to CustomApp[1...5] (e.g. CustomApp1, CustomApp2, etc..). These apps will remain even if you flash a new DevBase as corresponding dummy directories will exist in future DevBase updates

- In case of DevBase update or re-installation - installer will not remove your custom entries in /data/devbase/system/build.prop and in *.xml files placed in /data/devbase/system/csc

- SYSTEMLESS DevBase updated to v1.6 v1.8 (see changelog HERE)

v4.1

(not released for N960F):

- Added full Magisk support - MagiskSU is now default root solution (ROM should pass SafetyNet with Magisk Hide enabled in settings)

- Since systemless Xposed does not need to be re-installed every new DevBase I will release (in case of using the same root solution) - it makes no sense to keep it anymore as installation option

- SYSTEMLESS DevBase updated to v1.5 (see changelog HERE)

v4.0

(not released for N960F):

- A huge step in the systemless direction! DevBase installer now installs pure odexed stock ROM (just slightly debloated), then systemless SuperSU, then systemless DevBase, then (optionally) systemless Xposed

- All Knox related applications are available again (except SecurityLogAgent, to prevent annoying security alerts)

- Fake KNOX 0x0 status (check it in PhoneINFO app) - most of Knox related apps should work again, like in case of untouched KNOX flag

- All mods known from previous DevBase versions (up to v3.x) now are applied systemlessly - all modified files (including modded apps) are placed in /data/devbase/system instead of physical /system partition. Mods section (#4) has been updated to install mods to /data/devbase/system/(priv-)app if systemless DevBase has been detected (otherwise will be installed as usual, to /system)

- Deodex on-the-fly feature has been removed. If you really need deodexed ROM - you can install someone else's deodexed ROM, then systemless DevBase as an overlay

- Init.d support has been removed as it is deprecated (use su.d instead)

v3.8

(not released for N960F):

- Added hexpatch to root_from function (support for SM-N930x, thanks to @Chainfire)

v3.7

(not released for N960F):

- Another major improvement/bugfix in deodex_from function (full support for 64 bit OS)

v3.6

(not released for N960F):

- Major improvement/bugfix in deodex_from function (added "-g" switch to zip command - finally no issues in case of deodexed Android 6.0.1)

v3.5

(not released for N960F):

- Improved root_from function (Android 5.1+) - added "setprop selinux.reload_policy 1" removal from init.rc (thanks to @Chainfire)

- Fixed bug in new alghoritm for checking whether stock recovery should be installed or not (introduced in v3.4)

- Added new functionality - installer will store a copy of patched stock kernel in /data for those who flashed custom kernel but for some reasons want to revert to the stock kernel (Android 5.1+)

v3.4

(not released for N960F):

- Completely changed alghoritm for checking whether stock recovery should be installed or not (it applies to FlashFire users). Now it depends on previously used recovery (instead of checking KNOX flag which was not 100% reliable across devices/recoveries)

v3.32

(not released for N960F):

- Updated set_csc, kcsc_backup, kcsc_restore functions to support more devices

- Updated partition detection algorithm to support more devices

- Fixed path to options.prop file placed in external sdcard in case of updating Marshmallow while using FlashFire

- Minor intaller's optimizations/bugfixes

v3.31

(not released for N960F):

- Potential fix for reported problems with root (rare cases)

v3.3

(not released for N960F):

- Improved method of reading options from ZIP file name (previous was directory/path sensitive also)

- Added support to mod_csc function for other than UNIX text format (it's a little ridiculous, but in case of some CSCs - original /system/csc/other.xml file has Windows or MAC text format!)

- Initial support for options.prop file in CRLF text format (DOS/Windows)

v3.21

(not released for N960F):

- Fixed installer's issue if there is a [space] present in ZIP filename or a directory containing DevBase (see #1728)

v3.2

(not released for N960F):

- Another improvements in add_initd function (details - see v1.3)

- Improvements in set_perm, set_perm_rec and root_from functions (recovery-independent structure)

- Improvements in deodex_from function related to Android MM

- New get_con function in the main sh script (useful for devs)

- BusyBox updated to 1.22.1 (bionic) [no, this is NOT a mistake!]

- Minor intaller's optimizations/bugfixes

v3.1

(not released for N960F):

- Significantly improved "add_initd" function in the update-binary shell script. Added support for (probably) all available Samsung's platforms (e.g. Exynos) and all available firmwares (based on Android 4.4+)

- In case of installation with Xposed framework installer checks if Xposed Installer app is present in /data/app and installs it automatically if necessary

- Minor intaller's optimizations/improvements

v3.0

(not released for N960F):

- Entire installer has been re-written from the scratch! All "magic" moved to update-binary which is a shell script. It opens up new possibilities never possible before!

- Introduced new customization method - you can change most frequently switched options just by renaming installer's ZIP file name. Currently supported "strings" in the file name:

"noroot" (means "do not root"), "deodex", "xposed", "initd" (no other comments are required, I hope..)

- Starting from v3.0 init.d support is disabled by default

v2.3

(not released for N960F):

- Added option to install suitable Xposed framework in one step while installing DevBase (for maximum comfort). There is a new xframework.sh script - device independent structure and full Android 5.1+/6.0+ support. Backup method is compatible with well known Xposed uninstallers (tested with @wanam's)

v2.2

(not released for N960F):

- Significantly improved root_supersu.sh script - device independent structure and full Android 5.1+/6.0+ suport including on the fly kernel/ramdisk/sepolicy patching if necessary. SU binaries are still copied to /system as it is the best choice in case of custom ROMs

- Changed order of performed operations in the updater-script due to new root_supersu.sh script advantages

- Installer wipes partitions designated for RAW content (e.g. kernel / recovery image) before writing to them

- Minor additions in dex_injector.sh script related to Android 6.0+

v2.11

(not released for N960F):

- Fixed some minor installer's issues ("set_perm" function in set_csc.sh did not work correctly while using wildcards in the path (it was exclusively FlashFire issue! no problem with TWRP / CWM). Fortunately - only /system/etc/csc_*.txt were really "affected" - it didn't cause real issues as these files are empty)

v2.1

(not released for N960F):

- As some people felt a bit disapointed / worried about DevBase v2.0 ROM file size - finally I have decided to debloat stock system.img (in same way as in v1.x => "Safe De-Bloat") and remove option to install all available bloatware. ROM file size has been reduced from about ~2GB to about ~1.6GB.

Note for Devs / Chefs:

Do not use Windows tools - you need Linux with "selinux" package installed (to handle SELinux contexts) to mount (rw) system.img safely. If you want to add / change any system content this way - remember about proper chown/chmod/chcon

- Added device check during install as flashing directly to EMMC block is potentially more risky for "other" devices. Installer will abort installation if device is not N910F (trlte(xx)). If you want to try this ROM on other N4 devices - you need to remove this check manually from updater-script (it is more conscious procedure)

v2.0

(not released for N960F):

- Completely new concept of ROM development that makes it easy to build most tuned and nuanced custom ROMs. No more arduous manual analysis or (often) invalid permissions / SELinux contexts taken from a kitchen. The main idea is to flash original, stock /system image as EMMC block (in same way as PC Odin does) instead of extracting ZIP's contents to mounted partition, then setting permissions, then creating symlinks, etc. However, it requires more knowledge related to sh scripts as ALL necessary changes need to be done on the fly, while installing (e.g. by injecting modified classes.dex and/or modified images/xmls to /res/../* into an apk). There are no limits, all depends on your creativity!

- One common ZIP installer for Odexed and Deodexed ROM - you can control it by new "deodexed.rom" entry in options.prop (there is new dex_injector.sh script which can deodex on the fly the whole ROM using previously processed classes.dex files)

- ROM is still Safe De-Bloated by default but removing bloatware during install is not mandatory - you can control it by new "safe.debloat" entry in options.prop (there is new protection included to avoid overfilling /system in case of large size of additional MODs and/or large multi CSC package)

- Major improvements in csc_detect.sh script - it is able to detect previous CSC even in cases of flashing over e.g. CM based ROM and/or previously formatted system partition. However, if detected CSC is NOT included in my multi CSC package, in both mentioned cases it is still not possible to keep detected CSC (as there is no CSC related content to backup / restore)

- Improvements in all sh scripts - additional "metadata" entries in updater-script (related to processed contents) are not required

- Improvements in root_supersu.sh script - it is suitable for 32 and 64 bit OS

- Added full zip support from the command line

v1.x

(initial version, further improvements, not released for N960F):

- Built without using a kitchen. All set_metadata* / symlink entries are result of arduous manual analysis. For more info about the method - see hidden content for Devs / Chefs in THIS thread.

- New customization method without using Aroma (options.prop)

- Many useful scripts for easy installation: CSC applying/autodetection, backup/restore of security files, backup/restore of existing CSC package, XML modding on the fly, root, init.d support

- Many small changes and improvements "in the meantime" which I simply do not remember...

- Safe De-Bloated (see post #1 for details)