yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
You're going to have to 'walk' the audits and allow them one by one, I guess. I'm pretty sure I changed only the execute_no_trans in my original attempt, though.

Changes from zygote -> init (if not actual transition) are relatively safe, as nothing runs as init aside from daemonsu anyway.

Try installing to /su/bin , its on the PATH, it has some space, and it is persistent between reboots.

System-less root is limited to 6.0 and up, though.

You need both the boot.img and the SuperSU zip. If you only factory reset, you need to reflash SuperSU zip. If you switch ROMs, you also need to reflash boot.img.

This post has no place in this thread.
[SuperSU] natemup:
And in what order should I proceed? Once I've flashed stock /system, the boot.img, and SuperSU (and booted?), do I then go back into TWRP, Factory Reset (since I'm going to AOSP), install new ROM, then to bootloader to flash boot.img again, and then back to TWRP to flash SuperSU again? I feel like I'm making it too complicated if I go that route...
[SuperSU] phishfi:
Can't you flash the boot.img in TWRP? When you select a zip, just press the "Images..." button on the bottom corner and it will switch to looking for *.img instead of *.zip
[SuperSU] pc323:
My Nexus 7 2013 (flo) has been upgraded to Android 6.0 and applied the stock rootable kernel and SuperSU v2.52 by TWRP Recovery. This rooting works fine for me. However, I would like to play "Puzzle & Dragon" which is root-sensitive game. When the tablet was using Android Kitkat, changing the name of "Superuser.apk" and unchecking the "Enable Superuser" inside SuperSU can bypass the root-detecting of the game. In Android 6.0, the file "daemonsu" is required to be hidden besides hiding the "su" file but bootloop may be caused if daemonsu does not exist.

The "update-binary" script have mentioned that:

# 21+ /system/bin/app_process32 *5 /system/bin/app_process32_original 0755 u:object_r:zygote_exec:s0 required
# 21+ /system/bin/app_process64 *5 /system/bin/app_process64_original 0755 u:object_r:zygote_exec:s0 required
# 21+ /system/bin/app_processXX *5 /system/bin/app_process_init 0755 u:object_r:system_file:s0 required
# 21+ /system/bin/app_process (symlink to /system/xbin/daemonsu) required
# 21+ *5 /system/bin/app_process32 (symlink to /system/xbin/daemonsu) required

which the app_process is depending on the daemonsu file and I assume the reason of boot loop is invalid symlink.

I have restored the file app_process32 from the backup file(app_process32_original) but the game crashed to desktop again (same as root-detected by the game). Then, I removed this file and the game works. Moreover, there is no bootloop problem when I tried to reboot several times.

Is there any bad effect if the app_process32 is removed? As I know, "am" is using app_process but not "32". Thank you.:D
[SuperSU] gonzalotrianon:
The last supersu works on 5.1.1 touchwiz?
[SuperSU] zero100101:
Is this the newest version? So no need for the modified boot img?
[SuperSU] Ja_som:
Yes

Depends on your Android version, with Android 6 you need modified boot, see:

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[SuperSU] provolinoo:
has the new systemless boot image forceencrypt disabled like the standard mod? Or do I have to flash another patch afterward like FED-Patcher?
[SuperSU] extenue:
Hi Community,

i have nexus 5 , flashed factory MM then flashed SuperSU-v2.56-20151030013730.zip & hammerhead-mra58k-boot-systemless.zip as described , so far so good ........ except Secure Settings ... SuperSU does not recognize it so i can't turn on / off plane mode with Tasker anymore like i could with previous root method
[SuperSU] Dougshell:
I just want to clarify something. I understand that this requires stock rom, but would have a custom kernel make this root not work. I am trying to avoid doing a clean install.
[SuperSU] Captain_Throwback:
Apparently AirWatch isn't fooled by the systemless root, though. I think it performs a simple call to su, which will succeed with any SuperSU root method. So I guess I'll have to wait for Xposed to be updated to 6.0 as well (so I can use the unWatch module). It'd be nice to have that working without any system modifications too, but that's a question/request for [MENTION=4419114]rovo89[/MENTION].

But I can at least report that after decrypting my device (the SuperSU installer can't create su.img on /data if TWRP can't decrypt it), modifying my boot.img, flashing the SuperSU 2.56 zip in TWRP and manually installing the SuperSU 2.56 APK, systemless root is working on my very new, as yet unavailable HTC device :). Great work, [MENTION=631273]Chainfire[/MENTION].
[SuperSU] street675:
Nexus 5 stock MM, did not root MM until today. Tried the systemless boot and supersu 2.56 zip as described .

After reboot supersu asked to update, i did , then phone rebooted again but ends up in bootloop.

Reflashing stock MM boot, system, ........and so on , still no success, phone won't start up anymore. I'm trying to avoid flash all.

Really feeling stupid right now. After years of rooting my android phone's, never having this troubles.
[SuperSU] teshxx:
Were you encrypted? The new boot.img is only for unencrypted devices. You can try fastboot flash format userdata and try rebooting.
[SuperSU] natemup:
Is it possible that something in CM13 alphas that already makes it incompatible with the new systemless method? I have been trying to get it to boot for some time now, and after all the steps it just shows the CM boot animation for a few seconds and then cuts to black. At first I thought this was because CM13 forces encryption, but even with the patch that prevents it from doing so, it still won't boot.
[SuperSU] Lrs121:
Systemless requires a modified boot image to mount the su directory at /su or something like that. Which is not something the stock cm13 boot image can do. Also the systemless doesn't play nice with other root methods that use the standard /system/xbin method especially since cm13 uses its own root
[SuperSU] mustafa000xxx:
Note5 + Supersu 2.56 = bootloop
[SuperSU] provolinoo:
anyone? :(
[SuperSU] Lrs121:
Forced encrypt is disabled, though it'll leave your device encrypted if it already was.
[SuperSU] jonny68:
HI, Ive searched and cant seem to see if i install this apk on Samsung Galaxy S6 Edge plus will it root the phone, so far ive tried the rooting method as per the thread on the S6 Edge plus forum and it didnt work.
[SuperSU] Gungrave223:
Ok so I read through all the post since yesterday but didn't see an definitive answer to my question which is, does this method works with custom roms? can i just flash the boot img provide with the su2.56 with a custom rom?
[SuperSU] natemup:
Dang, so no CM13 + systemless root. Bummer...
[SuperSU] karthikrr:
Just an update to those that care: [MENTION=631273]Chainfire[/MENTION]'s "patch sepolicy and mod ramdisk to achieve root in Samsung on Lollipop 5.1.1" method worked perfectly for me on the P607T Note 10.1 (2014) tablet. Nothing else needed to be changed, other than the sepolicy file. The one hiccup was that come what may, Odin would NOT flash this new image, always resulting in an "Unsupport dev_type" error. Finally, with the help of [MENTION=336863]garyd9[/MENTION] and [MENTION=6367467]SHM[/MENTION], I was able to flash the new boot.img using TWRP (2.8.7.0 KK) and then flashed SuperSU 2.52 Beta to successfully get root with a fully stock kernel and SEAndroid still Enforcing. Busybox installed without any issues and Titanium works. Will spend the next few days to make sure all else with the device is normal and confirm that this method is the best one to get root on Samsung LL devices.

Once again, thank you to Chainfire, garyd9 and SHM for their efforts!
[SuperSU] provolinoo:
Thanks for the reply man, I'm going to format my data partition so it's not a problem :)

---------- Post added at 11:37 PM ---------- Previous post was at 11:29 PM ----------

Yes, no systemless root on CM13... that's why I decided to keep stock MM rom for now... ability to hide root on many apps (including Android Pay) is a must have for me :)
[SuperSU] osm0sis:
It shouldn't be hard to patch CM's ramdisk to support it if you read the WIP thread post where Chainfire documented the changes and you look in those files in his modified ramdisk for the changes he mentioned. My AnyKernel2 template could even be used to inject them into any Marshmallow ramdisk quite easily to add systemless root support, but Chainfire said he doesn't want people automating things just yet, so I'll stay out of it. ;):good:

Sidenote: I discovered ad blocking from a patched hosts file wasn't working via a symlink to /data/hosts but does when I patch /system/etc/hosts in-place. Not sure if a policy fix or something is needed but it worked via symlink before I switched to systemless root.
[SuperSU] phishfi:
I think it's HIGHLY likely that CM would implement this alternative method of obtaining root. It limits users' reasons for modifying the system partition, fixes ANY issues related to root by simply having the user conduct a factory reset, and making a small modification to the kernel image is much easier than maintaining an entire system modification.

EDIT: I guess it's not entirely true that any issue which results from root could be fixed with a factory reset, since it's possible that a root app could alter the system partition irreparably, but it's less likely to cause an issue.
[SuperSU] provolinoo:
Hi guys,

if I want to enable double-tap-to-wake on my N6 without compromising the systemless root what's the best way?

As far as I know since I flashed a modified boot I can't flash a custom kernel (with dt2w support) on top of it
[SuperSU] kmandel:
I have a Nexus 6 running stock 6.0, which means its encrypted. To use systemless it needs

to be unencrypted. Is there a way for me to unencrypt it?

---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------

I have a Nexus 6 running stock 6.0, which means its encrypted. To use systemless it needs

to be unencrypted. Is there a way for me to unencrypt it?
[SuperSU] Lrs121:
I'm encrypted and using systemless root without any problems.
[SuperSU] FPSUsername:
Aptoide market already has v2.56, where can I get the zip of that one?
[SuperSU] ashyx:
As far as I know all the changes are in the Ramdisk, so dont see why you can't use a custom kernel.
[SuperSU] provolinoo:
Oh, so are there no modifications kernel-side?
[SuperSU] osm0sis:
That's the systemless zip.
[SuperSU] gundal:
[MENTION=631273]Chainfire[/MENTION]

I applied the following modifications, as well as the sepolicy, and also altered the supersu 2.56 installer shell script to allow sdk '22' to also check the override testing bit

I can /su boot root my note5 into enforcing with a stock /system that should pass dm verity

however.. SuperSU is asking me to update binary.. which installed partially back to /system/xbin and .ext/su

edit: on second attempt with twrp ro bit set, after restoring /system, it just says su binary not found, executing it from /su/bin/ in terminal and daemonsu have no effect,

was interested in keeping /system untouched
[SuperSU] ashyx:
Haven't seen it mentioned, but can anyone fill me in the reason why this only works on MM and not LL?
[SuperSU] Ch3vr0n:
There is no reason. Beta should work just fine on lollipop

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] AnkitChowdhury:
Hey [MENTION=631273]Chainfire[/MENTION], need a bit of help. On Marshmallow, even after patching a couple of policies using the supolicy tool, the app is denied access to the input event files. Although the Supolicy tool return message suggests that patching was successful with everything ok. These policies worked great on Lollipop.

"supolicy --live 'allow appdomain input_device dir { open read write search ioctl }'"
"supolicy --live 'allow appdomain input_device chr_file { ioctl read write getattr lock append open }'"

Patching the policies through your SuperSU android library. And Using JNI to access the events and not spawning a separate daemon file. Any help would be really appreciated. TIA.
[SuperSU] darkera13:
[MENTION=631273]Chainfire[/MENTION] i just test new method on Note 5 rom, it work great. But i must change SDK to 23 and it broken all my google apps. So can you make SuperSU 2.56 support SKD 22 and smaller?

Thank you.
[SuperSU] osm0sis:
unSU Script zip -- Unroot with ease!

Originally this was a little zip to help with uninstalling the old system-modifying version of SuperSU. It properly restores all the original files the SuperSU installer backed up (so, file-based OTA friendly!) and removes any files added by the installer/app. I figured other people might find it handy as well so it's attached below. Be aware, if you flashed SuperSU twice mistakenly, the SuperSU installer wasn't written to recognize that and so you've lost your originals; a system.img flash WILL be necessary in your case.

Due to popular demand by the custom ROM community using this to unroot and pass SafetyNet checks/use Android Pay, etc., the script has been expanded to unroot Koush's SuperUser, ROM su binaries, as well as SuperSU Systemless (su.img and BINDSBIN), phh's Superuser (which is also systemless), and now Magisk and LineageOS addonsu.

Note: To completely remove all traces of the systemless roots, you still need to flash a different, unrooted boot.img, likely the default one that came with the ROM. You can extract it from the ROM zip (or a /data/stock*.gz backup from your root solution before flashing unSU) and flash it using TWRP's awesome "Flash Image" functionality, or, "dirty flashing" the ROM zip should also work.

My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!

P.S. If you found this handy then please check out my Odds and Ends thread for more flashable goodness. :D

Previous download counts: 58944; 158506; 59850; 226692
[SuperSU] shoey63:
Systemless root is working great on Sony z3 mm concept rom. :thumbup:
[SuperSU] notfaded1:
Has anyone tried this on 6p that's encrypted userdata?

Correct if I'm wrong but since systemless root doesn't modify userdata or /system couldn't you boot twrp and:

- Flash the attached boot image

- Flash the attached SuperSU ZIP in TWRP sideloaded

then just reboot leaving stock recovery in place and now have systemless root with crypted userdata?

I saw post on this thread saying someone on Nexus 6 was running systemless root encrypted. Would the above method I listed work for the 6P with crypted userdata?

Also uniofs or overlayfs does sound like even better option but since this works it'll do nicely for easier updates.
[SuperSU] claytonjn:
TWRP for the Nexus 6 can decrypt, TWRP for the Nexus 6P cannot (yet).
[SuperSU] osm0sis:
Depends. If you're using a device which launched with Lollipop or later (ie. has system.dat patch OTAs) you probably want to keep /system RO so that you can still flash OTAs (provided your root apps also don't alter /system). If you have a device that didn't launch with Lollipop or later (ie. has file patch OTAs) it doesn't matter, your choice; OTAs will flash fine as long as you don't modify the files it tries to patch.
[SuperSU] elreydenj:
So with the new factory images dropping as of today for the 6P and 5X we would have to wait for the systemless root kernel versions before flashing the system image if we want to upgrade and maintain root correct?
[SuperSU] M Diddy:
Can anyone tell me the steps needed to modify the stock boot.img to allow root using Android image Kitchen? I know how to disable encryption, just not how to make the other changes needed to root with the new factory image that was posted today.

Thanks!
[SuperSU] Smultie:
New images for Nexus 5 and Nexus 7 (2013) as well. Wondering if we need new boot.img....
[SuperSU] NYZack:
Have you just tried running this shell command (in a terminal after typing 'su' or using Tasker with root privileges):

echo 'AUTO' > /sys/bus/i2c/devices/1-004a/tsp

Doesn't survive a reboot, but that's not necessarily a bad thing. Shouldn't need to flash a custom kernel just for this.
[SuperSU] OMJ:
[MENTION=631273]Chainfire[/MENTION] testing new nexus 7 (razor) image MRA58V, apparently flashing SuperSu 2.52 causes no boot...still investigating
[SuperSU] _litz:
It looks like all the Nexus devices got new factory images today w/the November security updates .... MRA58N is the replacement for MRA58K.

Presuming this means waiting for new boot.img for either method, for one's specific device?
[SuperSU] trebills:
I just got my N6p today and I have build MDA89D and it says up to date. Is there a way to root this version? How to I root with this new method?
[SuperSU] kibmikey1:
The systemless boot image works fine with the 08M update for the 6P.
[SuperSU] trebills:
How do I use that method to root?
[SuperSU] kibmikey1:
Download the 08M for Angler here, and make sure you get the Angler modified boot image and superSU 2.56 beta from Chainfire here, also make sure you get TWRP recovery and flash it via fastboot from here.

Completely unzip the 08M factory image. Once your bootloader is unlocked (fastboot flashing unlock), flash each image via fastboot. You should flash the bootloader, then reboot. Then flash the radio, and reboot again. After that, flash the modified boot image from Chainfire. From there, flash the cache, system, userdata and vendor images from the factory image. Once that's done, flash the TWRP image. After that, adb sideload the supersu 2.56 zip to your device. Restart. TWRP might ask you to install supersu to root, do not install! Once it boots up, you can download a root checker to verify (I personally download the supersu app and re-sideload 2.56 in twrp to update the binary), but everything should be done after that.
[SuperSU] trebills:
Thanks that seems to work except after flashing supersu via twrp The play store and play services are missing. Any ideas?

Edit: NM I flashed it again and all is well. Do you know of a way to get rid of the corruption warning on boot?
[SuperSU] kibmikey1:
Unfortunately, not yet.
[SuperSU] peanutplanters:
Does this work with an encrypted device ?
[SuperSU] ViRb3:
Nexus 5X, any modified boot image causes the camera to not work with a "Cannot connect to camera" error. If I use an external camera app, it says that it cannot save to the specified location (symlink issues?). Please update me with anything, because the best thing in this device is the camera and not using it is quite a bummer.
[SuperSU] kill_kim78:
catlog, error repeat, not stop. how to fix it

E/SMD ( 2955): connect error:13

E/audit ( 5266): type=1400 msg=audit(1439403930.925:853): avc: denied { connectto } for pid=4658 comm="smdexe" path="/data/.socket_stream" scontext=u:r:smdexe:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket permissive=0

E/audit ( 5266): SEPF_SAMSUNG-SM-G925A_5.0.2_0011

E/audit ( 5266): type=1300 msg=audit(1439403930.925:853): arch=c00000b7 syscall=203 success=no exit=-13 a0=f a1=7f9f4f1ab8 a2=6e a3=7f9fccf000 items=0 ppid=1 ppcomm=init pid=4658 auid=4294967295 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=4294967295 tty=(none) comm="smdexe" exe="/system/bin/smdexe" subj=u:r:smdexe:s0 key=(null)

E/audit ( 5266): type=1320 msg=audit(1439403930.925:853):
[SuperSU] skvalex:
Here's the answer: http://xdaforums.com/showpost.php?p=63627668&postcount=4744
[SuperSU] provolinoo:
Yes, I'm using that way and it works but I would like to use a kernel since the original way doens't implement a proximity sensor check.
[SuperSU] Tanveerul:
Will Nexus 6P device be eligible to recieve OTA update from google even after rooting using this new method of rooting android 6.0 ?
[SuperSU] andresee:
Any one get busybox working with the systemless root yet?
[SuperSU] AnkitChowdhury:
I don't really understand this rising intolerance for Root apps. Why doesn't Google just ban all Root apps from the Play Store including SuperSU. Why this double face.

SELinux pretty much destroys the Root privileges anyway. Now they stop Supolicy. Sad days really.
[SuperSU] provolinoo:
It looks they aren't against root apps, they are just focusing on SELinux security (due to security demands I guess).
[SuperSU] Captain_Throwback:
Sure. I just put the busybox binary in su/bin. Since it's in the PATH, you can then run busybox commands. You could probably install it there as well and have access to the applets that are symlinked to the busybox binary.
[SuperSU] TiZiO.Cover:
Is the old MRA58K boot.img still working for the new MRA58N Update?
[SuperSU] JsChiSurf:
Yes, I had brought this up a few days back, and chainfire had suggested installing to /su/bin, since it has adequate space and it part of the current PATH, meaning a custom location install won't require a modification to the ramdisk to add your own PATH.

See Here: http://xdaforums.com/showpost.php?p=63580261&postcount=2418

What I found, however, is that despite offering it as an available feature, for installing to a custom location, the free version of busybox will not install to /su/bin, but the PRO version will.
[SuperSU] provolinoo:
hey guys what's the best kernel you suggest I can flash on the Nexus 6 without breaking the systemless root?

I always used Franco's one but since he hasn't implemented ramdisk changes yet I need to find a replacement :(
[SuperSU] osm0sis:
I still have busybox installed to /system/xbin/ and it appears the symlinks aren't taking precedence over /system/bin/ anymore, so I'm thinking there's a definite problem with system partition symlinks using the systemless root currently. I'm guessing it's something [MENTION=631273]Chainfire[/MENTION] can fix with an sepolicy change.

Good workarounds, I'll give it a shot. Prefacing with busybox still works with a /system/xbin install a well. :good:
[SuperSU] placebo_domingo:
Also wondering this.
[SuperSU] a g bell:
Not sure this the right place to discuss that

---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------

But yes it is
[SuperSU] flamand:
flamand

Which file did you flash? I thought they were for Nexus devices only. I've got a Z3 compact I'd love to try this on.
[SuperSU] markassbuster:
It failed to flash for me in TWRP 2.8.7.1
[SuperSU] kartikb:
You have to flash the MRA58K boot.img via fastboot not through TWRP. I personally haven't tried it but I will surely when I have time.
[SuperSU] markassbuster:
Damnit you're right! I'm a clown.

---------- Post added at 05:49 PM ---------- Previous post was at 05:21 PM ----------

OK it works. I flashed the boot.img from hammerhead-mra58k-boot.zip via fastboot then flashed BETA-SuperSU-v2.52.zip via TWRP.
[SuperSU] ViRb3:
Just an update, I got the camera issue resolved by re-flashing stock images (all of them) and then re-rooting! System-based SuperSU (2.52) runs smooth as butter and all of my root apps just as well!
[SuperSU] osm0sis:
TWRP actually has image flashing support too for boot and recovery images, you just have to select Image instead of Zip flashing. :)
[SuperSU] TriguyRN:
How experimental is the 6.0 systemless root? Can anyone share their experiences? I just got my nexus 6 and have never rooted before so I'm not sure whether to give it a try or not. I'm looking to keep it stock I just want to use lightflow.
[SuperSU] GROGG88:
Here is MRA58N repack with sepolicy.
[SuperSU] jblazea50:
Can you do the same for Nexus 6 (Shamu)?

Thanks
[SuperSU] GROGG88:
It's untested (I don't own Shamu), but should have proper changes in place.
[SuperSU] smelenchuk:
Booting up on mine as we speak; we'll see how that goes.
[SuperSU] hkkp:
It's working with v2.56 with mra58u systemless boot image.

Look at post #2:

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[SuperSU] GROGG88:
Working with 2.52.
[SuperSU] smelenchuk:
Working beautifully.

I took the opportunity to bake in the systemless root modifications to boot.img, which are also working beautifully (standard disclaimers apply; you risk blowing up your device etc. etc.)