yashsingh1/xdaforums huggingface dataset:
[SuperSU] osm0sis:
I've flashed franco.Kernel AnyKernel2 zips after 2.74 on my N5 and N7 '13 with no issues as well, so it's not just ramdisk mods in general, must be whatever FIRE-ICE specifically does. :good:
[SuperSU] ashyx:
[MENTION=631273]Chainfire[/MENTION]

What exactly is in the SPOTA folder? Is it just an updated SEPOLICY?

Is it possible to put a patched SEPOLICY in this folder to allow a prerooted rom to boot without bootloop?

The reason I ask is because I have a 5.1.1 Samsung device that I can flash a modified system.img to, but am prevented from patching the boot.img because of a locked bootloader.
[SuperSU] Pauls57:
I recently installed a custom rom which automates supersu installation, root works and shows in the app as systemless. When I look at the filesystem, I do not find data/. supersu . I see two folders named su.d one is su/su. d, this is empty. The other is system/su. d and contains 1 file permissive.sh Is this correct for a systemless install?
[SuperSU] Fif_:
SuperSU only reads /data/.supersu.

If you (or maybe your ROM) do not create this file, a SuperSU installation won't create it.
[SuperSU] Pauls57:
Should the system/su.d directory be there?
[SuperSU] drewski_1:
I don't have that folder after flashing v2.74 for a systemless root.
[SuperSU] joaonds:
Please:

I flash supersu 2.65 in CM13 (LG G3) and had bootloop.

Whats version is correct to flash in LG G3 CM13 ?

Thanks for attention.
[SuperSU] DingoBat:
Don't use SuperSu with CM. It's well documented that they don't go well together.
[SuperSU] Pastinakel:
As long as you don't enable root in the developer options, you can use SuperSU with CM.
[SuperSU] DingoBat:
[MENTION=3148740]joaonds[/MENTION]

It appears there is also a need to Bump the system img. Possible solution here.
[SuperSU] Fif_:
Yet it's okay.

SuperSU runs all the scripts in /system/su.d at startup. It's akin to /system/etc/init.d.

SuperSU does not put anything in there again, but just executes any file that exists in that directory.

The script in there is probably from either your ROM or a root app.
[SuperSU] rtoledo2002:
finally got this to install . maybe now I can fall in love with the M9 .

EDIT: it seems the first bootloader unlock from HTCDEV.COM somehow dis-appeared , I think because I did a RESET , anyways the first few times I tried I kept getting errors about S=on and so forth. so I re unlocked the bootloader today .

btw once TWRP installed , I bypassed the posted instructions and installed SU from TWRP, but I did not catch fast enough the warning from BETA-SuperSU-v2.74-2-20160519174328 telling me to say NO TO TWRP when it also offered to install SU. so when I rebooted , it was in a loop of the HTC white screen with red writting. finally held down ALL 3 buttons in and got the dam thing to shut off. then I rebooted with DOWN VOLUME button pushed in and POWER button. went to bootloader then into RECOVERY mode and booted TWRP .

I was panicking so I went down to SU 2.66 , but it rebooted in a loop again, by then , I had already DELETED my file for 2.64. so I downloaded it agin put it in my mini USB drive and had TWRP clean ou the cache files (don't remember how I got there ) but then after clearing the cahe directories , I installed BETA-SuperSU-v2.64-20151220185127.zip and this time the reboot went fine with the updating 14 files ? after then I went thru a whole bunch of updates, re downloaded my SUperSU PRO v2.64 from google apps, and then kept updating , just now it updated to SUperSU PRO v2.65 app.

so far I tried un-installing TWITTER , but there is still no uninstall button under apps , but I have already how to get around the dam program putting my followed people in my phone dialer "people" by removing permissions in 2 different spots and using CONTACT DELETER AND THEN UPDATING contacts from my ext usb drive, where I exported my contacts to after doing this a bunch of times.

thanks for your hardwork , will be sending you paypal thanks too, give me a week or so.
[SuperSU] gggirlgeek:
Thank you!!! This was driving me crazy. It turned out my ROM placed it in the Android Settings. But this helped until I figured that out. *Embarrassing*
[SuperSU] Uky8652:
How u flashed TWRP ?? It get stuck on teamwin logo
[SuperSU] yung40oz84:
If you get stuck at the TWRP logo then your not decrypted, I flashed everything in fast boot , and even recovery in fast boot and immediately booted to recovery from boot loader and all worked. Then I flashed superSU 2.74-2 in recovery, even the modified boot can be flashed in ADB.
[SuperSU] fifthelement:
Hello guys,

What is the proper method of detecting systemless root in an Android app ? do you have any code to share ?
[SuperSU] egingell:
Why? Just get root using the soft path (e.g. "su -v").

If you must, the systemless binary is /su/bin/su.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Captain_Throwback:
I think you meant /su/bin/su....

The most reliable way to "find" the su binary is to use "which su" as [MENTION=4544860]osm0sis[/MENTION] mentioned previously.
[SuperSU] egingell:
Indeed, but my point was to just soft-code it. If that fails, then maybe try to find it.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] pables123:
B.
[SuperSU] Androidwarrior:
My Sprint note 5 bricked when i flashed SU v2.74. I tried flash my Stock TARBall and nothing. It will try to start up and just reboot, it will power up and go to the main screen and then reboot. What can i try to Remedy this?
[SuperSU] Ch3vr0n:
Wrong thread, ask in your device forum
[SuperSU] Androidwarrior:
How is this the wrong thread? I flash this the SU v2.74-2 Zip and after that this issue starting happening?
[SuperSU] Ch3vr0n:
Because I'm pretty sure your kernel needs to be 'bumped'.
[SuperSU] Androidwarrior:
I flashed the Stock TARBALL that comes with the stock kernel, I flashed it to go back to stock everything and i'm still getting reboots, but the rebooting issue didn't happen until i flashed v2.74-2
[SuperSU] egingell:
If you reflashed your ROM and it's still happening, the problem is not with SuperSU. Just because B happened after A doesn't mean A caused B.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Androidwarrior:
So you're saying it's not a coincidence that right after i flashed the updated SU 2.74-2 My phone starting boot looping? and continued to do so after i flashed it back to stock.
[SuperSU] egingell:
I said your problem is with something else. Something that's not SuperSU. Some unknown C caused B to happen.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Androidwarrior:
Are you saying there is no way Flashing this SU ZIP cause can an issue like this?
[SuperSU] ktmom:
I think the goal is to get you help. The fact that you are in a bootloop after flashing back to stock takes it out of the experience of this thread. You really need help that is specific to your device. For example, nothing I would do on my Nexus 6 would apply to your Note. The Samsung devices are pretty specific and the best help you'll get to resolve the bootloop is from others most familiar with your device.
[SuperSU] gorilla p:
I was using 2.67 on my N5X - Dirty Unicorns . I finally decided to upgrade. Flashed 2.74-2. The flash completed, booted normally and now root it missing. SuperSu app was uninstalled as well. I rebooted to recovery, flashed unsu, flashed 2.67 again, rebooted and root won't come back. SuperSu app missing again upon reboot

Let that be a lesson - make sure you are not using LZ4 RAMDISK compression. The SuperSU installer states there is an error, but it looks like it completed so unless you're paying close attention during the flash process, you may miss it like I did.
[SuperSU] Chainfire:
The previous reply was correct: the right way to detect root access is simply by calling 'su'. If doing something like 'su -v', you should be aware that '-v' is not a standard parameter and is certainly not supported by all su binaries out there in the wild - in other words, be prepared for that command opening a shell. This is all written up in How-To SU.

'which' has only become an Android standard command in Marshmallow, and as such should not be relied upon by root app developers for a few more years, unless the app ships with its own tool/toy/busybox.

I see no practical reason to need to know where the binary is. It's on the PATH, that's all you need to know.
[SuperSU] xdamami:
After one week usage 2.72 with s6 stock kernel and fw today when i tried change my mac Adress app showed popup root not avaliable. Than flashed 2.74 now all is ok.

Sorry for bad eng.
[SuperSU] osm0sis:
A root app might want to know if some modification needs to be installed systemless to /su/xbin or otherwise to /system/xbin, in which case checking the location of su would be a good indicator, no?

Testing for /su directory/existence would probably be just as easy and avoid using "which" however, so a better solution overall than caring about where the su binary is located. :)
[SuperSU] Chainfire:
That is an edge case rather than the norm. And for the norm my statement stands.
[SuperSU] toopty:
To remove compatibility mode do I just change this to false and then re-flash supersu? The app I was having an issue with was updated today.
[SuperSU] ianmacd:
No, it's much simpler than that:

$ rm /data/.supersu
[SuperSU] TopDroid:
I'm not able to root my device. I flash the most recent zip file but nothing happens. I don't get root access.

Please help.

Device : Samsung S5 G900H (k3gxx)

ROM: Official Stock Android 6.0.1
[SuperSU] aidy.lucas:
Flashing just this supersu zip will not root your phone. You need to root it first then flash supersu. I'd go and spend a few nights reading up on rooting and rooting Samsungs and read through a few threads in the Samsung forums

D2303 5.1 deodexed z2 port+z5+X apps+themes, be,xr,sv,ad,XZRt2urecovery,xposed,z5 cam2.0,xLOUD,S-Force,viperaudio+more
[SuperSU] CVAngelo:
Flashing the SuperSu zip from a CUSTOM recovery will indeed root many phones! Step 1...flash a custom recovery via SPFT/ODIN/etc. Step 2...flash SuperSu zip from SD card while in custom recovery. Maybe this is no longer the case with Android 6?
[SuperSU] USBhost:
It seems if

init.flounder64.usb.rc
init.recovery.flounder.rc
init.recovery.flounder64.rc
init.zygote32.rc
ueventd.flounder64.rc
fstab.flounder64
init.flounder64.rc

are removed before, supersu will fail with that error.
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION] I tried to root Moto G4 Plus with the BETA 74. It bootlooped my device. Is there any zip that can be used to unroot or something? Or flashing back the boot.img alone will help?
[SuperSU] egingell:
The boot image is backed up to /data. It's gzipped. I imagine it would need to be decompressed first, but regular old disk images can be flashed directly with TWRP.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] :
Is there any log or something that I can provide to [MENTION=631273]Chainfire[/MENTION] that could help him bring root to the Moto G4 Plus community? What kind of logs do we need?
[SuperSU] egingell:
My guess would be everything he asks for in the OP of this thread.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] xda-unknown-developer:
I'm in safe mode after flashing supersu on Developer Preview 3. Nexus 6 stock N encrypted.
[SuperSU] SCDroid:
Any reason my binaries won't update on N preview 3, superuser 2.74? I have root on my nexus 6p but keeps asking me to update binaries but then it fails
[SuperSU] grep_i:
It's abnormal how many times this question has been asked around here a little bit of searching is a basic requirement for this forum.

I never update binaries from within the app I always flash binaries sometimes with flashfire but most of the time I do it through custom recovery TWRP.

Thumbs up [MENTION=5201515]Ja_som[/MENTION] for constantly answering this same question.
[SuperSU] SCDroid:
Awesome.... ? ?

Anyways set to permissive and still getting it. Root works so I'm not worried about it. Thanks for your help though.
[SuperSU] snej81:
Hey. Anyone knows if it´s possible to root a Nexus 10 with MM 6.01, and in that case which SuperSU version should I use?

Thanks in advance.
[SuperSU] ktmom:
This question is a device specific question. Please ask it in the Nexus 10 forum.
[SuperSU] drewski_1:
There is no official MM 6.0.1 for Nexus 10, only Custom ROM which probably (mostly?) are pre-rooted or will have instructions for root.

I'm on rooted OmniROM, btw ;)
[SuperSU] grep_i:
Please set SELinux back to enforce mode if possible, why you disable your phone's security mechanism in favor of an update warning that's not best common practice.

Have you tried to download the .zip binary from the first post and flash it through custom recovery or flashfire or tried the suggestion of [MENTION=5201515]Ja_som[/MENTION]
[SuperSU] Androidwarrior:
Okay. I just got a replacement phone after waiting 3 days. I couldn't resolve my bootloop issue, i tried everything. I just updated to PD2 on my sprint note 5. If i flash this SU file, do you think it will brick my phone?
[SuperSU] ktmom:
Why cross post here when you have actually posted in the right forum?

http://xdaforums.com/sprint-galaxy-note5/help/pd2-questions-t3387838
[SuperSU] pables123:
Rr
[SuperSU] Androidwarrior:
I'll briefly entertain you're question. The SU question is strictly for here. The other question pertains to an overall standpoint to my phone. Someone may have a better answer here than where i posted the question that is referring with 2 other questions. This is a Question just for SU on here. So would you like to answer? Or do like you going around posting irrelevant information?
[SuperSU] ¿GotJazz?:
Hi - I installed SuperSu Beta 2.74 on my CM13 OnePlus One. While SuperSu seems to be working for some things, I can't get it to work with ES File Explorer (which says the "Test failed" when I try to enable root access)

Is there a fix or something else I needed to do? ES File Explorer worked fine in the past with SuperSu v2.65 on this phone.
[SuperSU] Dor71:
Flashing super su 2.68 with with twrp solved the problem.
[SuperSU] RandomPooka:
ES contains known malware, and doesn't conform to new standards concerning location of the su binary. You're better off ditching the app entirely than to seek a workaround. This has been addressed repeatedly in this thread, and the answer is always the same. Switch file explorer apps. There are countless ones available.
[SuperSU] damador:
Using root explorer without problems. I dropped es after buying pro version to see that it hidden instal some crap charge app.
[SuperSU] Dnorris55:
Using SuperSU 2.74 with 2 MM ROMs (dual boot) on my SM T800. ES Explorer Pro works great with both ROMs. No fuss, no muss, no problems.
[SuperSU] mielletseed:
probably you're not using systemless install?
[SuperSU] damador:
Did you try to open something from sd card. ES is only editor that give "permision error"
[SuperSU] mondohow:
Read: https://plus.google.com/+Chainfire/posts/N6EARb8LF3d

Especially the bit under Compatibility
[SuperSU] Dnorris55:
Like /system/build.prop? Opens just fine using ES File Editor.

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=MOB30J

ro.build.display.id=cm_chagallwifi-userdebug 6.0.1 MOB30J 989658f105 test-keys

ro.build.version.incremental=989658f105

ro.build.version.sdk=23

ro.build.version.preview_sdk=0

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=6.0.1

ro.build.version.security_patch=2016-05-01

...
[SuperSU] ¿GotJazz?:
Thanks, [MENTION=5357999]Jm_Willing[/MENTION], [MENTION=5888813]mondohow[/MENTION], and all - I did search the thread for ES File Explorer, and it was hard to find the wheat from the chaff. I think I'm done with ES File Explorer for good now. I recently bought the Pro version, but I'm going to throw in the flag. I hate how much they have ruined a really great product. I will try the suggested "Solid Explorer", and see how that turns out. It looks like the Classic version is free (with ads), and the newer Solid Explorer has a 2 week trial.
[SuperSU] ipeedalil:
Has anyone tried to use this on the verizon Galaxy s6 edge+
[SuperSU] smohanv:
Sorry for this silly question..... I have flashed systemless 2.74-2. Don't know how to check whether my root is "System root" or "Systemless root"....

Thanks in advance..
[SuperSU] edzamber:
Look in system/xbin

If su is inside, its not System Less
[SuperSU] smohanv:
Thanks. I am seeing su under xbin. Why am i not getting systemless root though I flashed Beta SuperSu 2.74-2 several times. Also, I did full unroot in SuperSu and again reflashed.
[SuperSU] grep_i:
Search this thread a little harder the answer is posted in here a couple of times
[SuperSU] smohanv:
I am using PureNexus with my Nexus 5X which is rooted with system root.

Thanks, I found resources in different place and achieved systemless root. It would be nicer if this can be mentioned in the OP page.

This is all I did.

1. Boot in to TWRP

2. go to Advanced / File Manager and delete folder named supersu

3. go to Advanced / Terminal and enter these two commands

echo SYSTEMLESS=true>>/data/.supersu

echo BINDSYSTEMXBIN=false>>/data/.supersu

The first one forces systemless, the second prevents /su/xbin_bind from existing.

4. Flashed Beta SuperSu 2.74-2 (we can notice while flashing this zip after the above script, we will not see the line saying "Disabling OTA". Also, end of flashing it warns that it takes longer time to boot.

5. Reboot device and enjoy systemless

6. To check if we have achieved systemless root, go to system/xbin folder and we should not see the file named "su".

Enjoy.....
[SuperSU] grep_i:
I am glad you found out how to flash systemless, congratz
[SuperSU] Evo_Shift:
If I have modified the system (like by adding an app to the system or editing the host file) and then changed the system back to stock before an OTA drops will the OTA actually work? Does the method used to check the system integrity or whatever only look for the proper files or does it somehow actually look at whether the files have previously been edited?

I am using the systemless root but trying to decide if it actually helps me accept an OTA or not as there are a couple things i like to edit (moto gallery system app, black google calculator, host file...etc) but are easily deleted or changed back. If the OTA can detect these previous changes, even if they have been reverted, I think it won't really help me and I'll start deleting system apps instead of disabling or freezing them and trying to preserve a working OTA update.
[SuperSU] corkiejp:
Any changes to system image will cause OTA to fail, even just mounting the partition R/W.

You could flash stock system image to accept the OTA, but it is just easier to flash the newer image, instead of doing that.

Check out the Adaway Sytemless ZIP for host file editing that doesn't modify the system.
[SuperSU] danielcr12:
is there any chance to go systemless on lollipop?
[SuperSU] egingell:
Guh?

Mine is. Well, one of mine is.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] danielcr12:
I mean other than samsung, more like aosp and cm
[SuperSU] Bazilli:
How can i force systen-mode install or is is possible with original SuperSU? I need to use this modified build with my Huawei P8 Lite Marshamllow: http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

---------- Post added at 09:14 ---------- Previous post was at 09:13 ----------

If i make systemless install, it stops working after few reboots, system mode work fine with modified boot.img.
[SuperSU] M94Khaled:
FAILED

I'm trying to apply this steps. But the first thing is than i'm not seeing any folder called supersu to delete?
[SuperSU] tet-bundy:
I suppose its because the foldername is not "supersu" but ".supersu"

The dot indicates a hidden folder on linux systems

Gesendet von meinem ONE E1003 mit Tapatalk
[SuperSU] M94Khaled:
Ok, i see now, But i can't see it in TWRP. I see it when using a normal Root explorer but how can i delete it by TWRP?
[SuperSU] tet-bundy:
TWRP got a terminal right?

rm command should do the job ;)

Use -r option to make it recursively ;)

Gesendet von meinem ONE E1003 mit Tapatalk
[SuperSU] M94Khaled:
Ohh :D:D .. Ok thanks, totaly forgot it :silly:
[SuperSU] Azzarro-:
Does anybody have 2.72 version? I need to revert back from 2.74.
[SuperSU] corkiejp:
Here you go attached

edit or from https://download.chainfire.eu/960/SuperSU
[SuperSU] Azzarro-:
Thank you!!!!
[SuperSU] drewski_1:
Look 7 posts above yours . . . and do the opposite ;)
[SuperSU] inetman:
SuperSU bootloop on CM13 :( ,maybe it's a problem Latest Nightly...

UDP: yes. it's a problem on 4.06 build, sorry
[SuperSU] rasel800:
Hello,

Trying to unroot completely in Note5 N9208, I have SuperSU 2.74 installed (system-less).

1. Getting into bootloop after doing "Full Unroot" in SuperSU app.

2. Tried to flash stock image after that, still bootloop.

3. Flashed SuperSU 2.74 again in TWRP, able to boot but root is not removed (obviously).

Any suggestion, how to full unroot?

Cheers!
[SuperSU] Fif_:
Reflash the boot partition from your ROM, then uninstall the SuperSU apk.
[SuperSU] rasel800:
If I flash the stock boot.img i get into bootloop and phone won't boot. So I can't uninstall anything after that.

Or shall i uninstall the SuperSU first and then flash stock boot.img?

BTW, SuperSU.apk is the app, right? Or the flashable zip you are referring to that I've flashed through TWRP?

Will you please be a bit elaborative on the steps.
[SuperSU] Fif_:
Sorry but just flashing rootfs is enough to remove root for me.

Uninstalling the apk can happen before or after flashing rootfs.

It's best to do it after since you can easily check whether or not you successfully unrooted by launching SuperSU.
[SuperSU] rasel800:
Thanks, but as i said, i get into bootloop if i flash stock boot.img, any suggestions?
[SuperSU] Sickaxis79:
Try to flash a custom kernel instead of restoring stock. Don't know how its on your device,but when I restore stock boot.img my WiFi got broken and the only way to get WiFi back online is flashing a custom kernel or restore it from a nandroid backup with stock boot.img.
[SuperSU] teddy0209:
Try to wipe cache/art cache...
[SuperSU] NLBeev:
Why don't you flash a prerooted stock rom?

Completely new: boot, system and su; with wiping/formatting the system partition before flashing.

http://xdaforums.com/showthread.php?t=3059493
[SuperSU] FPSUsername:
I removed root from my prerooted rom and forced systemless install, now stweaks give timeout/no root issues, root works fine though. Does somebody know how to fix it?
[SuperSU] egingell:
Tell the "stweaks" dev to fix his app.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] magnamentis:
twrp has a file browser and most root explorers have a setting to show hidden files.
[SuperSU] grep_i:
Tell me if I understand you correctly.

You are trying to unroot completely (remove root completely from device).

Reflash stock image should do the trick and is the easiest method for most people.

There is an tool from Samsung called smart switch or you can flash stock with Odin.
[SuperSU] CVAngelo:
I think you missed the part where he said that flashing stock lead to bootloop. So the question is, how do you completely unroot a systemless root WITHOUT CAUSING A BOOTLOOP.
[SuperSU] grep_i:
What I miss is his method of flashing stock.

I replied with the 2 easiest methods to flash stock rom on his device.

Reason is he already did a lot of stuff to solve this problem but none of them worked even flashing stock which causes a bootloop but flashing root again on stock with bootloop solved it.

This confused me and I hope there will be more details
[SuperSU] magnamentis:
if he properly flashed stock rom the bootloop has nothing to do with root/unroot or anything while i strongly suspect user error.

firmware, bootloader, recovery etc. are the keywords for troubleshooting and of course proper wipes beforehand, especially data partition.