yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] gaganit:
I was hoping the same.. Tried the su.d method. Xposed works fine. No need to soft reboot anymore... However xprivacy still does not work.
[Nexus 6  General] bmg1001:
Can anyone confirm for me that the new alpha of Xposed works without setting SELinux to permissive?
[Nexus 6  General] HiGhDRo3o5:
I had to set to selinux to permissive on prevoius but not sure about latest. Are you on enforced?
[Nexus 6  General] bmg1001:
Darn, someone on reddit had mentioned not having to set SELinux to permissive anymore
[Nexus 6  General] HiGhDRo3o5:
Ill check now not sure to be a 100% but i think i had issue also.

Edit : on enforcing right now and all seems ok. Xposed is working fine
[Nexus 6  General] Novakingwai:
Can you post again? I swore I did it last week and it's still not fixed on reboot.
[Nexus 6  General] shivindera:
Read the Op thread (1st thread)... the link is in option 5.
[Nexus 6  General] theone_s_me:
Deleted
[Nexus 6  General] s2d4:
Permissive is no longer a requirement, enforcing will do.
[Nexus 6  General] theone_s_me:
The Dev has just updated Xposed to alpha2.. it fixed all the issues with Nexus 6... No need for a custom kernel with the latest update.. enjoy everyone

Just flash the new zip file and update the apk

Here is the link: :o

http://xdaforums.com/showthread.php?t=3034811
[Nexus 6  General] bmg1001:
Updated OP and title!
[Nexus 6  General] theone_s_me:
Thank you for this thread.. it helped a lot before alpha 2 release...
[Nexus 6  General] rubin110:
Should have actually posted this here than the main Xposed thread. Any help would be appreciated...

When the first alpha was released I went ahead an installed the framework along with the APK onto my rooted Nexus 6 running stock 5.0.1, no special kernel or anything like that. After fidgeting with it, and then reading up about the SELinux softboot workarounds, I got it working. However something on my device (most likely not Xposed related since the issue was around before installing all that) and so at least once or twice a day the device would hard reboot or I would have to force a reboot when the thing would go into sleep death.

Anyhow, about two weeks ago I installed LastPass which has some neat tricks to auto fill forms in apps and Chrome through the app accessibility stuff. For whatever reason this caused my device to stop asking me for my full system encryption passphrase on boot. After I turned this back on, I could no longer get Xposed to start up correctly after setting SELinux to permissive and softrebooting.

I found this current thread, so this morning I tried all the methods on the original post except for switching to a newer custom kernel, and none worked. Later in the day I noticed Xposed alpha 2 was released, flashed that but sadly it hasn't helped my issue.

Going through logcat right now, I don't really see anything related to why this is happening, then again I'm not exactly sure what to look for. I've gone through and removed both variations of init scripts and also set back SELinux to enforced, no dice. :(

So my question is are there any other stock Nexus 6 users who've seen this and possibly have a fix? Thanks!
[Nexus 6  General] wrongway213:
Lol @ this entire chain of events. So. I finally found the definitive way to get Xposed to work in enforcing and without any scripts (yes, before the alpha 2 update - I first got this to work like a week ago but could not figure out why), had been testing it for several days, made a couple confused posts in this and the Xposed discussion thread but got no responses, so I just kept messing with it, and finally got confirmation as to why it was working and that it would work for others as well. So I came in here to post the solution: Hydra Kernel actually did allow users to use Xposed in enforcing, as it boots up permissive but defaults back to enforcing shortly after the modules are loaded. Then I open the thread and see we no longer need a permissive kernel at all, let alone permissive boot. Irony is a funny thing.
[Nexus 6  General] rubin110:
Ok I feel like such an idiot. 2 seconds looking at the debug log output of the Xposed app and I notice something about /data/data/de.robv.android.xposed.installer/conf/disabled being around. Deleted it and now it works. I don't understand how that lock file came to be. But yay stuff is working again.
[Nexus 6  General] danarama:
I had that after my phone shut down once.
[Nexus 6  General] Novakingwai:
I wouldn't call it irony. That's not really the right word. Anyways, I was never sweating it as I knew a permanent fix would eventually come around.
[Nexus 6  General] wrongway213:
I've been rabidly looking for a fix for 3 weeks, found it finally, finally had the workaround explained to me in detail enough to properly explain it and let others start doing it: before I am able to share my findings they are no longer needed. Yeah, I'm sticking with irony :p However I'm definitely not sweating it, I am quite glad to have a working permanent real fix.. I just find it funny I opened the thread to share my "fix" and a real fix had just been announced.
[Nexus 6  General] s2d4:
Anyone seen this in the logs for alpha2?

Doesn't appear to impact on the modules I am using but the fatal errors are concerning.

03-09 22:09:51.071 F/libc (12309): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x7bb51053 in tid 12309 (main)
03-09 22:09:51.071 F/libc (12309): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x7bb51053 in tid 12312 (Compiler driver)
03-09 22:09:51.071 F/libc (12309): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x7bb51053 in tid 12313 (Compiler driver)
03-09 22:09:51.072 F/libc (12309): Fatal signal 11 (SIGSEGV), code 2, fault addr 0x7bb51053 in tid 12314 (Compiler driver)

EDIT: this was because of dex2oat crapping out because I had some apps patched to not have ads. Used adblockers instead and no more issues with those apps freshly reinstalled.
[Nexus 6  General] Waynehead69:
Can we install Xposed on 5.1?
[Nexus 6  General] the_rooter:
I think all mod kits like xposed has to be updated so no it wont work
[Nexus 6  General] Waynehead69:
I didn't think so, just wanted to make sure. Thanks
[Nexus 6  General] Nesor:
echo "#!/system/bin/sh" > /system/su.d/permissive.sh "file or directionary not found" why?
[Nexus 6  General] gdonanthony:
greenify not working ?
[Nexus 6  General] Nesor:
Greenify works, but i have problems to set SE permissive ..... same to Xposed cause of permissive problem...:(
[Nexus 6  General] gdonanthony:
i mean greenify donate boost xposed 5.1.1
[Nexus 6  General] redpansen:
Wont work, phone restarts

root@htc_m8:/ # echo "#!/system/bin/sh" > /system/su.d/permissive.sh

sush: can't create /system/su.d/permissive.sh: I/O error

1|root@htc_m8:/ #

Phone reboots instant after that.
[Nexus 6  General] pgellen:
can i do this from twrp in recovery? dumb question i know but,,,
[Nexus 6  General] purplecircle:
chmod line change

The last line should read:

chmod 755 /system/su.d/permissive.sh
[Nexus 6  General] Ice_machinE:
Thanks for that, everything worked well, until the last command.

something about wrong syntax and that chmode needs 2 arguments.
[Nexus 6  General] JimSmith94:
The correction is right above your post!

chmod 755 /system/su.d/permissive.sh
[Nexus 6  General] bustato:
How do you make it executable?
[Nexus 6  General] Cm4nXD:
If I did this, but then say switched to a different super user, would system still boot onto permissive? Also does this work on Nougat?
[Nexus 6  General] Strephon Alkhalikoi:
No Xposed for Android 7.x, and no one should expect to see it anytime soon, if at all. The superuser you use should not prevent the command from executing.
[Nexus 6  General] sumit_leo:
Please share the command line to change from permissive to enforcing. Currently I am on Lineage OS.
[Nexus 6  General] dcpathak:
I am trying to change Selinux to permissive in android 7.1.2 on note 2 (xenon hd rom). everything goes well before the last line: chmod...." I get a lot of error message like chmod should have two arguments etc., and nothing happens. Any help?
[Nexus 6  General] loopypalm:
can you please tell me what is the content of permissive.sh ???

Edit

i did test on a rw partition and find out it's :

echo 0 > /sys/fs/selinux/enforce
[Nexus 6  General] ttabbal:
Not all modules work. I have CrapaLinks and YouTube Adaway working. I think YouTube works anyway... App settings for per app dpi doesn't work though. Something like tinted statusbar is probably the easiest way to test. Check the logs in the xposed installer app.
[Nexus 6  General] danarama:
Cool. And also just to confirm, you have selinux mode changer app, set to permissive. After you reboot you then do soft reboot in xposed app?
[Nexus 6  General] GeekMcLeod:
Worked like a charm! Thanks a lot, really appreciate it!
[Nexus 6  General] flonker:
Tinted status bar works...

Edit: Although any app that was already formatted to change the status bar color natively now shows a black status bar, I'm sure that's just the module needing to be updated, but it's not worth the tradeoff.

2nd Edit: Yes, I'm too lazy to figure out which apps are already updated to material design and block them from the app. lol.
[Nexus 6  General] danarama:
Ah that's good. Just module choice is the issue
[Nexus 6  General] ttabbal:
One thing that should be mentioned...

Please do NOT post on ROM threads with problems if you have xposed installed. They can't really help you as you have modified the OS. If you think it's a ROM bug, backup and clean flash. If you can still reproduce it, then post with a logcat. If you can't make it happen, you broke it with xposed and/or a module.
[Nexus 6  General] thavet:
ok I set the SeLinux to permissive and xposed is installed but when I open the app the framework says "installation is only possible manually via recovery for now". Am I missing something, how do I install through recovery? SORRY IF THIS IS A NOOB QUESTION.
[Nexus 6  General] smclaughlin3:
Stupid se linux app keeps telling me it cant gain gain root acces everytime i reboot and xposed has the manual recovery install method only available. Running lean kernel which i thought was already permissive guess not...... Any ideas? Thanks
[Nexus 6  General] danarama:
Install the app, flash the flash able zip. Ensure selinux app set to permissive. Boot then soft boot
[Nexus 6  General] wrongway213:
So let's think guys - we have to have a good kernel that's default permissive on the Shamu - anyone think of anything? Might make this a lot easier until a better solution than constant soft reboots arises if the issue is really permissive not being set on boot as rootSu suggested (and I am inclined to agree with)
[Nexus 6  General] poczynek:
Hmm so which ones are?
[Nexus 6  General] thavet:
I followed your directions still no luck plus every time i reboot selinux goes back to enforcing and I'm still getting the same message. could the rom that im on just not be compatible? This is what I keep getting.
[Nexus 6  General] danarama:
Selinux is set to enforcing in the kernel. Everytime you boot up from off including a reboot, selinux is enforcing. That's why xposed doesn't work. The selinux mode changer app doesn't change mode until it is too late so every time you reboot or power up, you must do a soft reboot immediately as mode doesn't change.
[Nexus 6  General] wrongway213:
So are you saying if we flash a permissive kernel as opposed to using the app you believe we will be able to use Xposed on reboot normally?
[Nexus 6  General] danarama:
It is my assumption, yes.
[Nexus 6  General] wrongway213:
I know I've seen kernels set to default permissive on this device.. trying to think of what they were to test this.
[Nexus 6  General] ScottIsMyName:
I think if we could set permissive mode in init.d then it should work. I have tried messing around with this, but I am not very experienced in doing so. Basically, in /system/etc/init.d if there is a script that runs to set permissive mode then we should be golden:

su 0 setenforce 0

I have verified that if I run the above command in a shell (without using the permissive app), and then soft reboot, then it will work. However, when I stick this script in the directory it doesn't seem to work. Anyone more experienced have any ideas?
[Nexus 6  General] danarama:
Kernel needs init.d support too. Also I dont think you can call root like that in init.d though I'm not sure you'd need it...
[Nexus 6  General] ttabbal:
Try making the first line this..

#!/system/bin/sh

And make sure the execute permission is set.

And you don't need su in there. Init.d runs as root.
[Nexus 6  General] ScottIsMyName:
I did have that in there actually...here's the whole script actually (with permissions set to 0755):

#!/system/bin/sh
#Init.d Permissive SELinux

busybox mount -o remount,rw -t auto /system
busybox mount -o remount,rw -t auto /data

setenforce 0
SELINUX=permissive

According to an app I downloaded, the kernel I'm using does have init.d support. Still no dice :(
[Nexus 6  General] wrongway213:
I am unable to get "su" to run in terminal - can anyone else confirm issue?
[Nexus 6  General] ScottIsMyName:
When you request root make sure your phone screen is on so you can grant root permissions.
[Nexus 6  General] wrongway213:
I'm not sure how I could type with my screen off?
[Nexus 6  General] smclaughlin3:
Selinux app says cant grant root access at boot up...i think this is the people having with the app...well with stock based rom for me which is what I'm using... Tried forcing in su app no luck
[Nexus 6  General] ScottIsMyName:
Thought you might have been using your computer with adb. Weird that when you type su in terminal that it's not requesting root access.
[Nexus 6  General] CrashTestDroid:
adb shell works with screen off but you need the screen on to enable root for adb

setenforce 0 followed by soft reboot works but isn't working in an init.d script as previously reported. Xposed LP is worth it just for the CPUfreq and CPUtemp modules :)

Maybe the SuperSU injection method has something to teach us about installing Xposed. Pulling it apart now.
[Nexus 6  General] wrongway213:
Is everyone else able to get root in terminal still? Can anyone test?
[Nexus 6  General] poczynek:
Yep works for me.
[Nexus 6  General] danarama:
This is similar to.a.script I tested but also wasn't working for me.
[Nexus 6  General] wrongway213:
It works fine for me without Xposed.. But not with it.

Figured it out. Always correct! module messes terminal up.
[Nexus 6  General] ScottIsMyName:
I now have this as a script and it's NOT outputting to /sdcard/SELinux.log when rebooting, (but it does if i run the script manually from shell). So it seems like init.d is not actually working for me. Gonna investigate this more.

#!/system/bin/sh
#Init.d Permissive SELinux

busybox mount -o remount,rw -t auto /system

setenforce 0
SELINUX=permissive

echo "Permissive SELinux set" >> /sdcard/SELinux.log
[Nexus 6  General] danarama:
Echo to system or data. Sdcard won't work I don't think.
[Nexus 6  General] wrongway213:
I found the cure to our woes until a real fix is found or implemented - newest LiquidSmooth kernel is permissive by default, and yes [MENTION=2872010]rootSU[/MENTION] that does in fact allow Xposed to persist through reboots, tested it just now. Sensor_ind is disabled so no worries LK and Franco users, flar2 wake gestures as well. Enjoy guys!

Also, if you update your ROM you have to flash Xposed arm again apparently.
[Nexus 6  General] my95z34:
What rom are you using? Last I checked, init.d doesn't work on CM. I maintain PAC and we use CM as a base and we don't have init.d either. I tested on a stock CM build as well and no dice.

I found this script which fixes it. Just remove /system/bin/sysinit and run the script and you'll be good to go. (I have tried just copying the sysinit file that the script generates into a clean build and it doesn't fix it, so there's something else the script does that fixes it. You have to remove the file before running it or it won't run and will just say that it should already be working.)
[Nexus 6  General] ScottIsMyName:
I'm using Chroma rom. I might give this a go.

Edit: Can't get this to run, how are you running it?
[Nexus 6  General] my95z34:
After running the script I posted, I created a 01permssive in my init.d folder with the permissive script you posted earlier, and it works!
[Nexus 6  General] elevatorguy:
When you get it up and running will frameworks still show app processes - - - under active? Everything seems to work just that's throwing me for a loop. Will give the ls kernel a shot. Thanks [MENTION=5964313]wrongway213[/MENTION]
[Nexus 6  General] wrongway213:
Yes, 61 under XposedBridge.jar should mean you're good I believe
[Nexus 6  General] my95z34:
Ok, one last thing. I updated the init.d enabler to make it a bit more simple after a rom flash. I changed it to automatically remove the sysinit file, and it will also create the init.d script that will set SELinux to permissive. Haven't tested it, but in theory it should work.

http://hastebin.com/ahifazadal.dos

Also, [MENTION=2133630]skaforey[/MENTION], copy it into a text file, save it as whatever (enable-init.sh), chmod so it's executable, and then run it in terminal.

$ su

# sh /sdcard/enable-init.sh

And you should be good!
[Nexus 6  General] elevatorguy:
Thanks man. That's all it says compared to my M8 lots missing. Did the liquid kernel work out? If so what build date did you use. Maybe we can get the dev who does despair kernel to make us a special build. Nice to run into you again.
[Nexus 6  General] wrongway213:
02-13, worked like a charm bro
[Nexus 6  General] elevatorguy:
Thanks will flash it now ?
[Nexus 6  General] ttabbal:
I'm on Despair kernel, Chroma ROM. The initd script works. Here's a ZIP with the files. No need to make the initd script executable if you call it as a parameter to sh...

su

/system/bin/sh initd.sh

Then copy the 01selinux script to /system/etc/init.d and make it executable. Though I think the scripts the enabler puts there fix permissions for you. Rebooted and xposed was working.
[Nexus 6  General] ScottIsMyName:
Yep just got it to work too, good work everyone!

Just to be clear, for everyone that wants to get this to work, this is what you need to do to get this to work (if your kernel is not already set to permissive by default).

1) Download the zip from the below post (post 65)

2) Extract the file to your sdcard (initd.sh)

3) Open a terminal emulator and type the following commands:

su
cd /sdcard/
sh initd.sh

5) Reboot

6) Make sure xposed works
[Nexus 6  General] my95z34:
Tested the last script, didn't properly create the permissive init.d script. This one should work though.

Like I said, it will delete the /system/bin/sysinit file, fixes init.d, and then should create the permissive file. It reduces the number of steps required from 3 to just 1.

Lemme know if it works!
[Nexus 6  General] mflow:
your workaround works like charm mate!
[Nexus 6  General] ScottIsMyName:
Ugh, I just modified the script to do the same exact thing and came here to post it....guess we both did it at the same time :)

Awesome work guys! One command is way better than 3 :)
[Nexus 6  General] my95z34:
lol, I posted it about an hour ago, but i didn't put enough '>>'s and it didn't create the permissive file correctly. But, it should work now!
[Nexus 6  General] ScottIsMyName:
Yeah I noticed the file only had the very last line from the original script. I guess your original script had the last line as > instead of >> ? :)
[Nexus 6  General] my95z34:
Yep, lol. I'll test it tomorrow, I'm in bed now.
[Nexus 6  General] wrongway213:
New test build of leanKernel in permissive, no soft reboots required
[MENTION=4550123]bmg1001[/MENTION] you may want to add this to OP, will save a lot of people a lot of grief for now http://xdaforums.com/showpost.php?p=58836627&postcount=2502
[Nexus 6  General] poczynek:
Yes anyone got a full reboot working with this lk kernel? Mine still doesn't.
[Nexus 6  General] Astraeus85:
Just tried this, worked for me!
[Nexus 6  General] wrongway213:
Yeah it works you still have to soft reboot a module to get it working after you first install the kernel but from there it works, reboot a million times if you want. You just have to soft reboot every time you intstall a module after you tick the check box or it'll stop working again - if you do that, though, this workaround should keep us all going until a proper fix comes along. I've already got it all the way figured out to where I have no issues and I just played around with the rebooting and modules for like 15 minutes, you guys will be good to go on this setup. If you still can't get it working let me know - it definitely works and I'll help you get it going if those instructions aren't enough.
[Nexus 6  General] poczynek:
Yeah I installed lk, reinstalled xposed arm and apk, installed a module, soft booted and it worked. But then when I did full reboot it was back to not working again.
[Nexus 6  General] micmars:
If I'm reading this correctly, that's exactly how Xposed has always worked...activate a module requires reboot once and only once, then you're good to go on that module until you uninstall it or deactivate it.

What am I missing here? I see no additional workaround, as it appears to be an actual solution to what was needed, a truly permissive kernel.
[Nexus 6  General] wrongway213:
You mean you had it working after a soft reboot on the leanKernel I linked, then you did not mess with any other modules at all, rebooted and Xposed was no longer active? I tried to make that error happen and I couldn't, only errors if I don't soft reboot when I am supposed to.

Soft rebooting between modules is new - normally you could just hit "activate and reboot" and let it reboot normally, but that for some reason even on a permissive kernel makes Xposed stop working until you untick a module, check it again and soft reboot. Then you can reboot normally again and it will not stop working unless you install another module. Also, I do not know if a permissive kernel requirement is intentional - I know it wasn't needed on KitKat's Xposed as I ran a ton of modules on my very, very locked down S5. So the "workaround" I speak of is the combo of permissive kernel and soft reboots as opposed to normal Xposed usage in order to minimize reboots necessary to get modules working.
[Nexus 6  General] poczynek:
No so a full reboot for me will mean xposed won't work even with a permissive kernel. So every time I do a normal reboot I will then have to do another soft reboot. It's no big deal but it's not how xposed normally works.
[Nexus 6  General] micmars:
Noted...and thanks for clarifying.

I would add that this is a new version for a new operating system, and still in ramp up mode. To expect anything less would be a welcome occurrence but unlikely.
[Nexus 6  General] wrongway213:
No - just every time you mess with modules. You don't have to do a normal reboot on every reboot, only when you first flash a ROM or kernel, when you first install Xposed, or when you first install and activate/deactivate a module. Other than that, Xposed should persist through reboots if you follow my instructions.
[Nexus 6  General] poczynek:
Yeah it didn't work for me. Lk then xposed then module then activate module then soft boot and works. Then full reboot and no longer works.

But yep agreed - this will fixed quickly so no big deal.
[Nexus 6  General] wrongway213:
Oh yeah, I'm definitely not surprised or disappointed that there are some new kinks or possibly just some new processes to deal with to use this amazing repo - I'm just trying to get a grip on what exactly these new kinks and processes are so that I can learn how to most efficiently deal with them and help as many of the rest of the users here to do the same, as N6 users had a particularly rough go of the initial launch today - no one could get it working.