yashsingh1/xdaforums huggingface dataset:
[SuperSU] shiningwizard:
Sure thanks guys. I admit I did post my question in the wrong thread. Should have posted it in the beta thread.

And yea I did read but I couldn't find the answer. FWIW, I switched from stable 2.5 to 2.65 and then to beta 2.71 and finally to 2.74. I just didn't find the right answer that I was looking for and I spend half a day poring over threads and googling. I had thought it was an issue with selinux enforcing but seems I'm wrong and gotten myself ridiculed. I thought it was that those apps aren't requesting super user permission but secure settings is.

Anyway thanks, I shall find the answer.
[SuperSU] shiningwizard:
Anyway to answer my own question, I found what was the problem and I fixed it using sym links install of the bindsystemxbin. It was a simple fix and painless, once I knew what was the problem.
[SuperSU] gimpy1:
Deleted, wrong thread.
[SuperSU] Vegerot:
Attempting to flash SuperSU via TWRP on CyanogenMod 13 Moto X results in a bootloop.
[SuperSU] fmc000:
As expected... (if you're flashing the stable version).
[SuperSU] Vegerot:
Attempting to install SuperSU on Cyanogenmod 13 on Moto X 2014 results in bootloop. I've tried making it systemless, but it still causes a bootloop that requires me to reflash the system
[SuperSU] shawkes:
You got an answer so you asked again? Have you even looked in the beta thread?
[SuperSU] ktmom:
He has, he's cross-posting.
[SuperSU] Vegerot:
My apologies. Trying to install the beta causes the "decompressing ramdisk error" and nothing happens. Trying to install the stable version causes my phone to bootloop. I've tried installing both, and I get different errors for each.
[SuperSU] su35:
I had installed the v2.62-3 via TWRP. Now, I want to update to v2.65. Could I install v2.65 via google play directly to cover the old version or have to install via TWRP?
[SuperSU] ABHISHARMAKMJ:
direct update via google play store
[SuperSU] smartyouth92:
Dears

I've tried to install root for the device but I faced the below problem

1- I've Unlocked the Bootloader for the device

2-Installing TWRP recovery also finished

3- the state is ( S-ON )(Unlocked)

3- After applying the root device stucked on this message { "this build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action" }

4- I've changed the ROM to "Android Revolution HD 20.0" but also sticks on this problem

Your feedback is appreciated

My Device Information

Product : htc_himauhl

version: 1.0

version main : 3.35.401.12

version boot loader : 1.0.0.0000

MID: OPJA10000

CID: HTC_J15

What should I do to solve this problem
[SuperSU] fmc000:
Which Android version?
[SuperSU] smartyouth92:
Version 6 < < I've Restored the TWRP Backup using the below link

http://xdaforums.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698/page1

But after that i've got this message

unfortunately setup wizard has stopped

and also stucked > ?

Do you have any solution ?
[SuperSU] ktmom:
Did you wipe davlik and cache? Try rebooting?

Version 6.0.0 or 6.0.1?
[SuperSU] fmc000:
I suspect you have to use the beta version and not the stable one to four Android M.
[SuperSU] smartyouth92:
The Wizard Problem has been solved after applying another ROM , But SU authority still not granted, It's fail whenever apply

BETA-SuperSU-v2.74-2-20160519174328.zip OR UPDATE-SuperSU-v2.65-20151226141550.zip

And It's stuck on this message through booting

"this build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action"

My Device Information

Product : htc_himauhl

version: 1.0

version main : 3.35.401.12

version boot loader : 1.0.0.0000

MID: OPJA10000

CID: HTC_J15

Android Version: V 6.0

TWRP Recovery version: V 3.02
[SuperSU] fmc000:
It's something very HTC specific I'm afraid. I suspect you'd get better luck on the XDA product forum.
[SuperSU] grep_i:
I'm not absolutely sure but it was my understanding that on HTC devices you need to set them on S-off to get root working.
[SuperSU] smartyouth92:
Thanks for replaying

I don't think that I should make S-Off to be able to root the device ? Anyway Is it applicable to make S-off ? and in case of Yes , Do you have any resources ?

Thanks
[SuperSU] ktmom:
As said before, this is a HTC specific problem. Scroll through the HTC forum to find your device and ask there. http://xdaforums.com/htc

Resources for specific devices don't really belong in this thread and it confuses other people when they are linked to here.
[SuperSU] pables123:
K
[SuperSU] RodrigoSaka:
I'm using 6.0.1 with superSU 2.74 is working, but security settings can't find root.

I have installed superSU 2.67 and security settings can find now.

In the next versions might create some compatibility?
[SuperSU] ktmom:
What ROM are you using? What phone? Is 2.67 installed as a system app and 2.74 as a systemless?

There are lots of posts on compatibility within the 2.74 beta thread.
[SuperSU] RodrigoSaka:
I'm using moto x play with Marshmallux v2.0 , I believe that in this case the rom and device does not influence .

I know very well that the plugin of tasker, Security Settings not updated for long time and it should be updated , but I think it should not be forgotten apps compatibility trying to find the root of the old way.

After a few tests identified it only works in versions 2.68 below , above that in versions 2.69-2.72 is not listed in superSU and version 2.74 says it can not find root

Thank you for your attention!
[SuperSU] ktmom:
Again, there are plenty of posts on compatibility work arounds (e.g. sym linking) in the beta thread. Just search the beta thread.

Aside from the fact that if you want cutting edge root (e.g. Systemless), it's silly to blame SuperSu for the failings of app developers.
[SuperSU] ianmacd:
Secure Settings has its own thread. You'll find the systemless root workaround there. It can work perfectly well with SuperSU 2.74 once you apply the fix.
[SuperSU] RodrigoSaka:
I fully understand the position, thanks for the help and sorry for posting in a place not so appropriate
[SuperSU] MOReMEMeROM:
/system/su.d

Love your work of course. Specifically, I've recently noticed the /system/su.d folder. It seems from what I've read as an alternative to init.d. It also seems to load slightly earlier in the boot process? Before I bring it too much attention, are you wanting to it viewed as an alternative to init.d, or is it more like a personal use type thing for SU specific applications, and maybe a few developers that notice it, or wholly notice and used by the masses?? I'm not seeing many people write about it, and wanted to bring it some more attention via this thread. I love it!!! I've had issues in the past with link2sd, apps2d, etc not always mounting the 2nd partition soon enough on Samsung device and occassionally need to hot reboot immediately after a regular boot. Using su.d has eliminated that problems altogether. Thank you very much!! 3 questions... I'm trying to figure out what app/apk/bin specifically do I need to install to enable su.d functionality. Secondly, does it follow the same rules as init.d, such as order of execution, no extensions in filename, etc?And tertiary, and perhaps why no one writes thirdly.... it may be "top secret" and you don't have to ansewr, but I'm also very curious what you could have hooked into to enable the su.d service? I've seen debuggerd used for init.d, but didn't see any other file hijacks for su.d.... assuming it's part of the daemon which is why I ask the 2nd question above about what to install to specifcally enable the su.d service. I lied... I do have something thing, more of a comment/request/concern though.... realizing all of this may under the wrong thread and su.d may not come directly from su at all, but I also use liveboot (another great product) and don't get the onscreen logs during a hot reboot?? Related? IDK??. Thanks again for a great app!!!
[SuperSU] lolle.santoso:
The SU binary needs to be updated. Continue? Normal Installation failed! Please reboot and try again.
[SuperSU] Ja_som:
http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] 3lMghraby:
could someone provide me a link to 10.05.2016 - v2.72 - BETA zip

thanks in advance
[SuperSU] Ja_som:
https://download.chainfire.eu/960/SuperSU/
[SuperSU] shantanumishra:
how to update super su binary??its showing super su binary needs to be updated..bt its not updating..pls help..
[SuperSU] ktmom:
From the first post in this thread:
[SuperSU] lolle.santoso:
The SU binary needs to be updated. Continue? Normal Installation ! Please reboot and try again.
[SuperSU] Pkt_Lnt:
Look at the link to the update support thread in the post above yours.
[SuperSU] Ja_som:
You already get answer here:

http://xdaforums.com/showpost.php?p=67336212&postcount=10736

!!!
[SuperSU] grep_i:
Have you tried and flash the .zip binaries through custom recovery (I use TWRP) or with the flashfire app from [MENTION=631273]Chainfire[/MENTION].

This should do the trick works for me anyways.
[SuperSU] bjbirch:
Try going to Google play store>settings>my apps>installed apps and see if SuperSU has an update
[SuperSU] donatoaguirre24:
Which version should flash

I'm not sure about which version should flash for my moto g 2014 with marshmallow.

Could flash the latest stable version? What do you advise me?
[SuperSU] Sam Nakamura:
Go with the latest stable version... I run android 6.0 x32 and everything works like charm...
[SuperSU] donatoaguirre24:
I will do that, thanks bro
[SuperSU] bvramana:
SuperSU-Superb access management tool of the future

By the way flashed this superb tool v2.65 today using custom recovery TWRP on LAVA IRIS 504QP(Plus) MT6582 running 4.4.2. Thanks a lot for your hard work:good:

On your OP you have made a sweet request "It would be nice if you would include minor advertisement in your ROM description, such as "Powered by SuperSU" kindly advise how to incorporate the same to my device please.

Thank You:svetius:
[SuperSU] Sam Nakamura:
I think it is more a notice for people who compile roms like cyanogenmod, BlissPop, Resurrection Remix etc. So not for privately used systems..
[SuperSU] bvramana:
Thank you for your generous reply:)
[SuperSU] nines99:
Hello

I have Note 5 running Marshmallow 6.0.1 with a stock rom.

My problem is that from time to time now I get this error message "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" all of the sudden, I've had this problem about 4 times, I flash the latest SU zip and the problem is solved.

My question is why does this happen?

I can confirm that I did NOTHING to provoke this problem. I only have Greenify and Titanium Backup.

Also, I added SuperSu to the white list in DOZE mode.

What would cause this so I can avoid this problem in the future.

Thank you in advanced.
[SuperSU] TKil9:
how do I properly install Super Su so it doesn't brick?

I have a moto x pure edition running marshmallow. Everytime I flash super su it bricks my phone and I have to restore from backup.

I have flashed 2.65 and 2.74 with the same result.

I have read about systemless root, but it says super su is supposed to automatically install the proper root method.

Is there a solution to my problem?

what is my problem? lol

I've read a lot about what the problem may be regarding the bootloader not verifying root files but have not come across any solutions to address the issue.

Advice please.
[SuperSU] kh34d:
Try this method [emoji4]
[SuperSU] TKil9:
what method is that?

cyanogen mod?
[SuperSU] kh34d:
I'm sorry I forget,

Here http://xdaforums.com/showthread.php?t=3286120

But it needs,

Requirements :

- Unlocked Bootloader

- Custom Recovery

- Custom Kernel
[SuperSU] OldBaldy:
Moto x requires a modified bootloader, and supersu did not detect it. Install it in systemless mode by using the echo command listed in this thread. Just search for systemless mode and ui should find it.

(Btw, I'm running stock Tim with supersu 2.74-2 in systemless mode with no problems)
[SuperSU] TKil9:
Where can I find a modified bootloader?
[SuperSU] OldBaldy:
Sorry, I misspoke myself. What you need is a modified boot image. Supersu will create it if installed as systemless. To force systemless mode do the following either from the terminal in TWRP or a terminal emulator:

echo SYSTEMLESS=true >> /data/.supersu

Then flash the Supersu.zip of your choice, version 2.65 or greater. The latest beta 2.74 works fine.
[SuperSU] nines99:
Please, any answer?
[SuperSU] ipdev:
log files would help.
[SuperSU] nines99:
Currently, everything is running smoothly. log files won't show anything strange, but i know it will happen again.

Also, after looking this up online, many people faced this problem, but about all of them are only interested in the fix. I just hope to know what is the cause.
[SuperSU] Heisenberg:
[Size=+1]Thread cleaned.

If you're not a moderator it isn't your place to moderate other members, so please don't. Also, it is not a breakage of the rules for a member to bump a question that wasn't answered, as long as it isn't bumped within 24 hours of being posted originally. With that being said, stay respectful please folks, if you don't want to answer someone helpfully then don't post at all.

Thanks.[/size]
[SuperSU] ipdev:
Grab your current logs. Even is you miss the error (and still can grab logs after), you might find what triggered it when you compare the two.

(Before and after.)
[SuperSU] nines99:
Good idea. will do. Thank you! :)
[SuperSU] CCJ22:
Are all superSU's systemless now? I remember some months back that some of us were going systemless others weren't. And it's been awhile since I've been back (was in the hospital)
[SuperSU] zelendel:
It depends on the rom you run. The one I use doesn't use system less. It is just built into the rom. Most custom roms are like that. Systemless is used by most people that use stock roms.
[SuperSU] grep_i:
Systemless is used on Stock Android rom like on the Nexus devices.
[SuperSU] tag68:
Does 2.74 work fine in the sense of "it detects that Motorola devices need systemless" or in the sense of "it works fine if you tell it to do systemless"? If it does not detect, is that detection supposed to work in future versions?

As i read, nearly all Motorola devices have that problem. And many users get bootloop trying to root, just flashing current SuperSU using TWRP. No matter if beta or release version. Some guides recommend SuperSU 2.62-3 as it defaults to systemless, and current version does not work without configuring via command line. I'd wish that situation could be improved.
[SuperSU] OldBaldy:
it works fine if you force systemless. None of the recent releases detect the need for the Motorola boot image to be modified, but the fix is simple and painless.
[SuperSU] kostassfirakis:
what's that o.o

Spoiler content hidden.

how I am not able to download it from the supersu latest link and it is on aptoide?
[SuperSU] sandeman11:
Hey Guys.

I have this strange problem with my 1+1, recently i cleaned up my 1+1 by installing from scratch (with bootloader)

everything worked well (no issues so far) after installing the latest CM13 for the Oneplus i flashed (with TWRP) SuperSU, this results in an sort of Bootloop. Its not actually an bootloop, phone is not rebooting but when it starts the screen remains in the android logo.

Tried several versions of SuperSU (incl. the beta) but problem still is there. Wile flashing SuperSU reports that everything worked well. "Googling" this problem learns that there are more users with this problem, on the Cyanogenmod-forum there is this https://forum.cyanogenmod.org/topic/118363-supersu-v252-boot-loop-with-cm13-rooting/ topic.

sadly enough one of the moderators / dev reports that this is an SuperSU-problem and says basically to figure it out yourself, so what better way then post here? :D
[SuperSU] dadnammit:
block adb root?

Sorry if this is noob; I'm trying to understand this stuff. I guess that CyanogenMod's superuser allows root to be denied or enabled for adb specifically. Does SuperSU allow that? Is there any way with SuperSU to deny root via adb? Or is sufficient to just disable USB debugging to prevent access that way?
[SuperSU] fmc000:
If you disable USB debugging you will prevent adb altogether, root or not.
[SuperSU] ktmom:
This was discussed at length in the beta thread. Start 4 or 5 pages back from the most recent post.
[SuperSU] Jackamy:
where 2.75
[SuperSU] ReyPaez:
http://xdaforums.com/showpost.php?p=67483272&postcount=6543
[SuperSU] ktmom:
This is the stable thread.

2.75 isn't actually released yet (in spite of appearances on the web). When it's released it will be in the OP of the beta thread. Over the final 5-6 pages of the beta thread you'll find the discussions of why there appears to be a 2.75 release.
[SuperSU] rahim11:
I have the exact same problem..I'm using the note 5 N920C variant, on marshmallow. I tried reflashing super SU.Does the trick for me.But I'd prefer a more permanent solution to this if possible, definitely.
[SuperSU] egingell:
It happened to me exactly once on a different phone/ROM (SGS5 - Lollipop TW). I just rebooted and it was fixed. I don't know why it did it, either.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] ApriliaM3:
I note that:

20.12.2015 - v2.64 - BETA

- (systemless) Samsung: prevent "KERNEL IS NOT SEANDROID ENFORCING" warning

But on later versions this is not implemented.

Any chance this can be included in future releases?
[SuperSU] KillersEnergy:
On the 2.74-2 version i get only "set warranty bit" warning...try to use that
[SuperSU] ApriliaM3:
I was hoping to avoid all warnings.
[SuperSU] KillersEnergy:
"KERNEL IS NOT SEANDROID ENFORCING" warning is avoidable by tricking the bootloader to think that the kernel is Enforcing the Selinux Policy...but remove the "set warranty bit" it's impossible because you can't trick the bootloader to think that your boot.img or recovery.img is signed by Samsung...so unless you crack the Samsung signing keys is impossible:)
[SuperSU] ApriliaM3:
Thanks for the explanation. So this has all happened since when?

When I was on KitKat I didn't have any of these warnings.. it's only since updating to Marshmallow and later version of SuperSU
[SuperSU] KillersEnergy:
Because on marshmallow "system root" doesn't work anymore i tried myself and when i type "su" on terminal emulator it doesn't work, because to gain access as root you must patch the sepolicy that are located in ramdisk,and when you modify the ramdisk ,hash of the kernel get changed, and i think when the bootlader decrypt the cryptohash of kernel and compare that value with the hash of the kernel(i'm not sure 100% that the verification work like that)and the value mismatch,output that message and a SMC call(into TEE) to set the warranty bit to 1...
[SuperSU] skyn3t:
Hi Chain,

just made some Portuguese translation changes on the site you gave on the 1st post, can you please check them?

Regards,

Cláudio
[SuperSU] bsoplinger:
I've been having issues when I reboot. It seems SuperSU is causing my phone to hang as the launcher and GUI initialize. I have a workaround. If I go into SuperSU right as the launcher starts and change the default permission to grant vs. prompt I can get through startup/initialization. Once past that I can go back to prompt and everything seems fine until my next reboot. Any ideas why I'm having this problem?

Sent from my HTC Evo V 4G (PG86100) using Xparent Purple Tapatalk 2
[SuperSU] sutty_monster:
Anyone got a backup link for the CWM-SuperSU-v0.93.zip file. I need to root my One x and the link supplied at the start of the thread wont let me download. Just get a database error each time
[SuperSU] G3-SCORPIO:
Hi Chainfire! Please tell me this is a global error, or can live comfortably and do not pay attention to it? And it works and does not cause any FC.

If this no be correct, please correct.

Firmware 2.2.1 Froyo my ROM
[SuperSU] Chainfire:
How should I know if this is an error ?
[SuperSU] G3-SCORPIO:
First it was FC when I took over your program. Then FC ceased to be. In the super user of this error was not

I bought your version of the program and want to find the answer. Should I worry or not?

Kernel installed speedmod for Froyo. K13e voodoo sound 7 driver.

If you need logs, I can send them to you. If you gave the source code, I would have corrected this mistake myself.

Do not ignore me please! Help to find out what the problem. You are the author of the program, not i am.
[SuperSU] felixjet:
download is down :(
[SuperSU] Pkt_Lnt:
ChainFire has been posting on twitter all day about his file host company issues. Patience, it is out of his control.
[SuperSU] alljokingaside:
Hey,

SuperSU came with the ROM I flashed. It seems cool, but is a little harder to use than what I'm used to.

eg. With Gemini App Manager, when attempting to revoke a program's autorun at boot privileges, the program tells me that "I need root and USB debugging". Since the device is rooted and debugging's on, and since I wasn't prompted to allow root privileges to Gemini App Manager aswith other programs (in settings, accesss is set to "Prompt"), I'll go ahead and assume that I couldn't because SuperSU isn't granting su privledges to the app.

So how do I get around this? Or add it to the access list manually?

The only way I've been able to use Gemini and a few other programs when involving things root is when I have Superuser installed on it concomitantly
[SuperSU] papayayoghurt:
Hi

There is a UI bug in newest version 0.93.

Look at "Einstellungen" in the right top. I use the German Language. Please fix, it looks ugly.

Sent from my ICS-powered arc S. From Austria! You don't know Austria? Google!

PS: Thank or PM me if you like the Rubiks Cube! :-)
[SuperSU] Infy_AsiX:
I started using supersu since the original superuser updates and binary prevented anything from gaining root access for me.

I recently installed auto memory manager and denied it root access as I only want to use it's app memory category sorting. I'm on supercharger and noticed my ram levels had in fact changed to what auto memory manager uses which is even lower than default. Supercharger script thinks that it's still set at it's levels but it's clearly not. So I think auto memory manager somehow gained root even though it's denied? At this stage i'm going revert back to old superuser where things just worked.

Sent from my Optimus 2X using Xparent Cyan Tapatalk 2
[SuperSU] TeamHackura:
not working for me

i searched the thread and couldnt find an answer. randomly after flashing a rom i'll lose the ability to mount system. Ive tried super user and super su. any ideas?
[SuperSU] jna9000:
I can't confirm this.

Gesendet von meinem GT-I9000 mit Tapatalk 2
[SuperSU] nkojic:
Ok i did clean install of the rom. Did i super wiped. I havent install any mods. Start rom ok and update binary on supersu. and when i root my es file explorer, supersu stop working?? How to fix this?? I didnt have this problem with 0.91 supersu
[SuperSU] shaggyskunk:
What do you mean "stopped working"? You granted permission, right?

If you check the logs in SU, what do you see beside esExporer?

Sent from, The Eclectic Chair.
[SuperSU] nkojic:
yes i granted permission and right after that it says supersu has stop working
[SuperSU] shaggyskunk:
Was SU working with other apps that require root?

Sent from, The Eclectic Chair.
[SuperSU] nkojic:
some yes and some no. 0.91 works with everything on 6.6.7 but on 6.7.0 not even 0.91. What do i do?
[SuperSU] shaggyskunk:
What are you referring to with 6.6.7?

Edit: your talking about your rom.

I'm not familiar with your phone or rom, but you may find the answer in your phone's forum or the dev that made the rom?

You could revert to the previous version until you get a more helpful answer. sorry

Sent from, The Eclectic Chair.
[SuperSU] nkojic:
On 6.6.7 Supersu v0.91 works ok with every aplication, but whe n i update it then the problem again. On the 6.7.0 where is 0.93 in rom, problem is with es file explorer and now i am going crazy. This is so stupis because i dont have any help from nobody....