Flash the “permissiver.zip” from here after the rom flashing procress on TWRP.
It will change the kernel mode from Enforcing to Permissive and it should boot normally.
Couldn’t figure out a way to boot with Enforcing mode
1 Like
Unfortunately atm there is no way to boot the kernel in enforcing mode, as it needs to correct neverallows caused by the BT audio fix and address some denials in sepolicy rules in the source, at the moment as an alternative you can install this module, then it will change to enforcing during the boot stages
Unfortunately, root will be required for this
And regardless of the kernel u install, on the A13 ROMs in the Galaxy sdm845 devices, it only boots in permissive (Except GSIs) It would also be interesting to keep the A12 builds up to date, since it works normally in enforcing mode there
2 Likes
I thought the permissive bug was present on GSIs too.
At least the ones I’ve found that could boot also all had the permissive mode set.
Is there anyway to at least update the security patches on A12 to mach 2025?
I’m not very concerned about features, I just wanted to have the device up to date in that regard.
Thanks for the info!
Yes, it’s possible, since e/OS is based on LineageOS, which still maintains Android 12 (Lineage 19.1) but with a lower priority, compared to Android 13 (Lineage 20.0), so to speak, but they’ve already merged it in the March SPL, check it out on LOS gerrit
https://review.lineageos.org/q/topic:"S_asb_2025-03"
even in the release of e/OS 2.9-s it also mentions that it’s updated for the March SPL
1 Like
In this case would be nice to boot /e/os 2.9-s on the device with an enforcing kernel, I can live without Bluetooth.
I’m no developer so I’m just hoping that someone will figure it out eventually 
1 Like
Regarding bluetooth, it is already functional on both Android 12 and Android 13, without any need for modification by the user to do the same, using the source mentioned in previous posts