FORUMS
Remove All Ads from XDA

[CM12] How to make xposed framework work on MOTO G

2,259 posts
Thanks Meter: 1,608
 
By reversegear, Senior Member on 16th February 2015, 07:01 AM
Post Reply Email Thread
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/t..._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
Attached Files
File Type: img BP_boot_SEL_0.img - [Click for QR Code] (6.26 MB, 1064 views)
The Following 5 Users Say Thank You to reversegear For This Useful Post: [ View ] Gift reversegear Ad-Free
 
 
16th February 2015, 09:37 AM |#2  
Member
Flag Salamanca
Thanks Meter: 409
 
Donate to Me
More
Quote:
Originally Posted by reversegear

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/t..._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

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.
16th February 2015, 11:18 AM |#3  
reversegear's Avatar
OP Senior Member
Thanks Meter: 1,608
 
More
Quote:
Originally Posted by SergioSanchezR

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.

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
22nd March 2015, 06:40 PM |#4  
star-lord's Avatar
Senior Member
Flag Madurai
Thanks Meter: 60
 
More
Wink Cool !!
wow!, the terminal method is vv easy method. Works perfectly!!
1st May 2015, 04:20 PM |#5  
Senior Member
Thanks Meter: 17
 
More
SELinux-Status: Moderat
Hi!
I used the Terminal method.
However, the SELinux-Status is now: Moderat (see screenshot).

Can you please instruct?

THX
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2015-05-01-17-16-50.png
Views:	384
Size:	51.7 KB
ID:	3291500  
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes