Hi Friends--
I'm having trouble getting dt2w to work on reboot.
I tried putting it into an init.d script, but that doesn't seem to be working...I have to run in manually on every boot.
Anyone have any suggestions?
Kernel Auditor has an option.
Running Franco kernel, and he doesn't have the option in his app....
elementalx kernel has it enabled via the kernel. you might want to try that
Related
Hello!
I have a problem on stock 5.0 Rom. It's rooted, init.d enabled by "universal init.d", Busybox is instaled also, UKM flashed. When i turn on Synapse it says "No UCI support detected". I dont know what's happend. On preview 5.0 it worked. Universal init.d show on test: "your kernel does not have init.d support". Can anyone help?
Sorry for poor language.
WielebnyRay_PL said:
Hello!
I have a problem on stock 5.0 Rom. It's rooted, init.d enabled by "universal init.d", Busybox is instaled also, UKM flashed. When i turn on Synapse it says "No UCI support detected". I dont know what's happend. On preview 5.0 it worked. Universal init.d show on test: "your kernel does not have init.d support". Can anyone help?
Sorry for poor language.
Click to expand...
Click to collapse
Did you flashed a permessive Boot image?
You mean CF-auto-root?
I mean this: Permissive boot.img for LRX21T
It worked for me, did have same issue. Flash that, then reflash Ultimate Kernel, UKM and reinstall Synapse. Should work...
kowalski7cc said:
i mean this: permissive boot.img for lrx21t
it worked for me, did have same issue. Flash that, then reflash ultimate kernel, ukm and reinstall synapse. Should work...
Click to expand...
Click to collapse
work fine!
Thank you
Hi
Xposed is here. if you are wondering it does not work for you its because the SELinux status is set as Enforcing which doesnt allow xposed framework to modify at system level. though some modules are not compatible yet
Bonus : Also if you are using Viper4Android it wont work unless the SELinux is Permissive
there is a workaround for this. 3rd being the easiest and permanent fix
1. Terminal method
Code:
Su
Setenforce permissive
soft reboot to make xposed to work
OR
2. Using SELinux Mode Changer APP
Use this app SELinux Mode Changer
change it to Permissive and soft reboot to make xposed to work
Else
3. With a modified Kernel(CM12 only) easiest method
Here is the modified Kernel which is set to permissive by default.
it is a boot.img not flashable.zip
How to flash
1. Flash this using TWRP(TWRP can flash img files now ) or apps like RASHR can be used to flash boot.img
for more info check this https://source.android.com/devices/tech/security/selinux/validate.html#switching_to_permissive
Tested with BlissPop 13th release works as intended
i have used BlissPop kernel. it is as good as CM12 Kernel
Better to have a backup(Not mandatory its upto you)
All credits to original developers
reversegear said:
Hi
Xposed is here. if you are wondering it does not work for you its because the SELinux status is set as Enforcing which doesnt allow xposed framework to modify at system level. though some modules are not compatible yet
Bonus : Also if you are using Viper4Android it wont work unless the SELinux is Permissive
there is a workaround for this. 3rd being the easiest and permanent fix
1. Terminal method
Code:
Su
Setenforce permissive
soft reboot to make xposed to work
OR
2. Using SELinux Mode Changer APP
Use this app SELinux Mode Changer
change it to Permissive and soft reboot to make xposed to work
Else
3. With a modified Kernel(CM12 only) easiest method
Here is the modified Kernel which is set to permissive by default.
it is a boot.img not flashable.zip
How to flash
1. Flash this using TWRP(TWRP can flash img files now ) or apps like RASHR can be used to flash boot.img
for more info check this https://source.android.com/devices/tech/security/selinux/validate.html#switching_to_permissive
Tested with BlissPop 13th release works as intended
i have used BlissPop kernel. it is as good as CM12 Kernel
Better to have a backup(Not mandatory its upto you)
All credits to original developers
Click to expand...
Click to collapse
Hi,
great post, thanks!
I have two questions:
- Can you provide more information about this kernel please?. Is stock cm12 kernel, only with SeLinux changed?
I don´t use cm12 because SeLinux is set to enforcing and have problems restoring nandroid backup with TWRP (no problems with philz recovery).
- I don´t have tested, but i think that if you make init.d script that change SeLinux, you would´t have to make soft reboot.
Regards.
SergioSanchezR said:
Hi,
great post, thanks!
I have two questions:
- Can you provide more information about this kernel please?. Is stock cm12 kernel, only with SeLinux changed?
I don´t use cm12 because SeLinux is set to enforcing and have problems restoring nandroid backup with TWRP (no problems with philz recovery).
- I don´t have tested, but i think that if you make init.d script that change SeLinux, you would´t have to make soft reboot.
Regards.
Click to expand...
Click to collapse
1. as i said kernel i used is from BLISSPOP rom from 13th experimental build. i dont think Bliss Team made any changes to the kernel. i guess you can flash custom kernel like optimus / Attacked on top of the modded kernel because both provide only Zimage. so that SELinux status is retained to Permissive
2. i Tried init.d script unfortunately it wont work on CM based rom so i thought of modifying in boot.img itself
Hope this helps
Cool !!
wow!, the terminal method is vv easy method. Works perfectly!!
SELinux-Status: Moderat
Hi!
I used the Terminal method.
However, the SELinux-Status is now: Moderat (see screenshot).
Can you please instruct?
THX
Im Running RR on my Note 3, can't seems to apply settings on Kernel Auditor that came with the rom. It keeps reverting even after applying on boot
Hi all,
maybe it is a dumb question or I am doing something wrong, but now I am facing a problem with losing root on Lineage os, when I use custom kernel. I use Magisk and flash everything through twrp recovery.
What I tried:
I completely wiped telephone, for to be 100% sure it is clean, so I went back to stock rom, lock bootloader.... and so on. After this I unlocked...root....
And even when I have only custom rom, without any additional apps only clean LOS, Magisk and custom kernel with developer app, for example Boeffla kernel and his app or from Flar2 elementalx kernel and his app and change something in their app, lets say frequency It automatically breaks root on next restart and after this root is not avaliable everytime when I boot up. I tried reflash magisk but without success. (And I am not using kernel for OOS on LOS, everytime the kernel is built for LOS)
On freedom OS 1.8 I dont face to this issue, for now I am on Freedom OS with Boeffla kernel and his app without problem. But really I am familiar more with LOS than OOS due to more clear system than OOS. (But this is my opinion :-])
Always I am using the newest versions - LOS - 02/10, Magisk 14.0....
And next note - I used LOS on OP3T with same settings and custom kernels without any issues only now on OP5 I have this problems.
Can you please tell what is wrong or if you have the same problem? Thank you for a help.
Hello! I want to install Extreme Kernel on stock ROM, but I want to backup stock kernel in order to get OTAs (everytime I received an update, I would install/restore stock kernel). How can I do that? Thanks!
The easiest way is to use Magisk Manager.
Stock system -> install Magisk (it automatically creates backup of currently flashed kernel) -> install custom kernel. When OTA arrives, restore stock boot.img from withing Magisk Manager, install OTA, reboot, install Magisk, install custom kernel.
Doublecheck if custom kernel uses only stock Wifi drivers. Some kernels install custom driver in system partition, breaking OTA.
_mysiak_ said:
The easiest way is to use Magisk Manager.
Stock system -> install Magisk (it automatically creates backup of currently flashed kernel) -> install custom kernel. When OTA arrives, restore stock boot.img from withing Magisk Manager, install OTA, reboot, install Magisk, install custom kernel.
Doublecheck if custom kernel uses only stock Wifi drivers. Some kernels install custom driver in system partition, breaking OTA.
Click to expand...
Click to collapse
Does it work in all custom kernels except Void which indicated it won't? If I remember correctly it only works with Franco.
whrynox said:
Does it work in all custom kernels except Void which indicated it won't? If I remember correctly it only works with Franco.
Click to expand...
Click to collapse
I've been using it personally with Franco kernel, but in theory should be fine with any kernel. But I didn't try other kernels, because most of them break OTA..