yashsingh1/xdaforums huggingface dataset:
[SuperSU] dreamland2000:
Just reading the release notes and not sure if it's me being paranoid but it says this latest release fixes a vulnerability to the kernel etc, this seems to have happened with the release that ccmt released with notifying [MENTION=631273]Chainfire[/MENTION] and this new release has fixed the security risk.

Normally I wouldn't question this as I've used SuperSU for as long as I've had android but with the knowledge that an unknown Chinese company is in control and suddenly there is a security vulnerability in an app that can pretty much have few reign of your system begs the question as to the actual security behind this app anymore. We all know these Chinese dev companies are renowned for spamming apps or provide back door security issues in apps.

Like I said I may just be being paranoid and reading to much into this but it just raised the question as to how secure is this app becoming now it's in the hands of an invisible entity.
[SuperSU] coldconfession13:
I flashed it but don't see the supersu in app drawer and not in settings. I think it's not installing for me. I'm on PureNexus on 6p
[SuperSU] dratsablive:
Wot you talking about Willis? SuperSU is now a Chinese company?
[SuperSU] Chainfire:
Just to be clear, I wrote the buggy code, and now I fixed it.

This conspiracy thing has gone far beyond healthy skepticism at this point, and I will not tolerate it in my threads.
[SuperSU] dreamland2000:
If you follow back through the thread you should see the chainfire sold SuperSu to a company called CCMT, no solid details can be found about this company other than that it's based in China. All the info we can find seems to point to a name and that's about it. I may be wrong but I'm going on what info I've found and what hasn't been said. Details of the company have been kept very quiet and almost secretive so that on its own raises more questions than answers.
[SuperSU] Ch3vr0n:
You know what i don't get? When i responded in one of the first posts in the main stable releases topic about ccmt's superSU site and no info that existed about them, a moderator deleted the posts. Yet these conspiracy posts which are worse, get to stay. Measure with 2 cups much?
[SuperSU] KaMyKaSii:
Not related to the subject, but why you never quotes the person who wants to answer?
[SuperSU] creeve4:
Truth dispels misinformation.

While i don't subscribe to any of the "conspiracies," I do find it very strange that there is very little available information about CCMT and that all comments about the sale of SuperSU to them have been quite vague.

The absence of information has created this conspiracy environment.
[SuperSU] Ch3vr0n:
Because I don't want to piss off the wrong person, or any staff member. That response was just a general observation of measuring with 2 cups.
[SuperSU] anttaz:
v2.78 SR1 fails installing on HTC One M8 when it gets to ramdisk part and superuser is no longer installed upon boot
[SuperSU] chazall1:
I am running PureNexus and in settings Just under PureNexus Settings mine showes SuperSu.
[SuperSU] mbutandola:
I can't agree more on this. superSU being a very popular and sensitive app, people will want to be certain that they can still trust it. And a simple "yes you can trust us" won't cut it.

Envoyé de mon Nexus 6P en utilisant Tapatalk
[SuperSU] snke:
I have Magisk on N6P with Pure Nexus + ElementalX can I flash latest SR1 over Magisk SuperSU version?
[SuperSU] grep_i:
Yes you're being paranoid the release notes stated in my eyes that [MENTION=631273]Chainfire[/MENTION] found a bug in his own code and fixed it.

This is normal for a developer to do, they do that to create even more stable apps for you to use.

I really don't know why you are so scared because the company who owns the intellectual property is Chinese.

If you followed the news you would have known that company's from all country's in the world have the tendency to gather your information even if they tell you about it they gather more than they tell you about.

Please give the creator and developer of SuperSU credits where due.

If he thinks this Chinese company is to trust why can't you trust him on his opinion, he repeatedly stated this and even rebuild a version they created to prove there was nothing malicious about it.

You trusted him in his opinions before please do so again now or just stop using his app and stop with the negative comments.
[SuperSU] :
You may need to flat out state that CCMT isn't doing anything questionable. Link it in the OP. And squash the conspiracy parts with an iron fist.

Let's face it. We root. We accept the risks. If we, as users, don't trust root control apps (SUPERSU included) we shouldn't be rooting. Bottom line.

If you state is fine. I personally take that at face value. If other people don't... That their hangup.
[SuperSU] bon122728:
is the latest update 2.78 SR1 systemless? how can i have systemless root?
[SuperSU] Ch3vr0n:
Every release since 2.56 is systemless by default, if your system supports it.
[SuperSU] bon122728:
sorry to ask, but I'm new to this, I'm using custom roms sfor a long time and theyre all rooted but how do I know if its systemless? or how could i make it systemless?
[SuperSU] egingell:
Open SuperSU, click Settings, scroll down, read.

As for changing it to systemless:

1. Why? It's not necessary if it's not needed.

2. You'd have to completely unroot first and flash SuperSU zip. It will decide if it needs systemless. If it doesn't, it uses system.

Note: A prerooted ROM is probably system root.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] grep_i:
Is there any way to avoid flashing custom kernel and Xposed by every update of SuperSU or is that the culprit of using systemless ?
[SuperSU] bon122728:
To play pogo because it is our family bonding and at the same time use my xposed modules for optimization, tweaks etc.
[SuperSU] Ch3vr0n:
Pogo doesn't work atm, systemless or otherwise. If you'd read the last couple pages you'd know that. This isn't a Pogo topic. Pogo added saferyNet and that thing got updated and doesn't pass with root atm system or systemless.
[SuperSU] bon122728:
well okay thank you for some clearing, and sorry for being off topic. Maybe suhide can do the job?if it gets updated? :confused:
[SuperSU] Ch3vr0n:
Same answer suhide or otherwise. Read the topic
[SuperSU] egingell:
I had no problem playing Pogo (assuming it's the EA game we're talking about) just now on my rooted SGS5 (systemless). I'm just about to try on my SGS4 (system).

Edit: Works fine on my SGS4. It must not like Xposed (I don't have Xposed installed on either phone and I'm not going to change that just for this). Regardless of the culprit, this is definitely not the place to discuss it.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] bon122728:
xposed work on your' SGS5? or you installed systemless?
[SuperSU] egingell:
I don't have Xposed installed. I updated my post, but you replied before the update.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] bon122728:
Thank you! :o

---------- Post added at 03:42 AM ---------- Previous post was at 03:38 AM ----------

[MENTION=4587767]egingell[/MENTION] can i try to full unroot, and then flash this v.2.78 RS1?
[SuperSU] Ch3vr0n:
[MENTION=4587767]egingell[/MENTION] you assume wrong. The abbreviation Pogo stands for Pokemon go, last time I checked your 'pogo' game by ea doesn't use safety net.

So [MENTION=5510030]bon122728[/MENTION] no you can't. Safety net won't let you, systemless root of otherwise.
[SuperSU] Dead-neM:
Yes but...

Boot does not proceed until all scripts have been executed

unless scripts run longer than the timeout (now 60 seconds, previously 4 seconds)

The problem for me is :

I'm using su.d folder to execute

- liveboot

- one script with simple echo, until, grep, function the name of the script start with a d so i will start after liveboot

but why i'm using su.d instead of init.d for a script to just write some value ?

-because the script will not be deleted after a rom update . yes i know i can simply add a addon.d script to keep the file on init.d

-i'm using busybox which is installed in /su/xbin for the same reason above

the problem for me with this change is that :

--- unless scripts run longer than the timeout (now 60 seconds, previously 4 seconds)"

will make phone not boot because, i guess, i'm using

until [[ -d /sdcard ]]; do
sleep 6
done

so i think the script is stuck on those lines and phone won't pass bootlogo

i know that path to sdcard is /data/media/0 on my nexus device but perm will not the same and my log file ouput of the script will not be deletable or readable etc... if i change path to from /sdcard to /data/media/0.

maybe it's something else in the script that give conflict so i attached it here.

as a workaround I've try the following

place my script in /su/xbin

create a script in /su/su.d to launch my script as follow

#!/su/bin/sush
MYSCRIPT=/su/xbin/myscript
/su/bin/sush $MYSCRIPT

With this the command work on a terminal as expected but phone would not pass the bootlogo again... so i've add the precious "&"

#!/su/bin/sush
MYSCRIPT=/su/xbin/myscript
/su/bin/sush $MYSCRIPT &

but now in terminal the script run but doesnt exit even if there's an exit line at the end of it. so i can't use this because a process loop in ram is not a good idea i guess

I'm not requesting a change revert or contesting it. I understand your changes. I just want to know if there's a way for me or for you to make things work for both. like something in my script that should be not used now etc...

Thanks !!!
[SuperSU] egingell:
That makes sense. The EA game was the first thing that came up when I searched the Play Store for "pogo".

I'm out of the loop with PoGo--I quit paying a week after it came out. Too much effort.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] bon122728:
Tried to update my su to RS1v2.78 by flashing but after it boots when i open SU in my settings it says I am not rooted and have no SU binaries installed.

(i didn't unroot, just tried to flash the latest su v.2.78)
[SuperSU] osm0sis:
I agree with Chainfire, we just need to think a bit differently when writing scripts now that we know the true nature of su.d. I made my boot_completed run asynchronously by making it:

until [ "$(getprop sys.boot_completed)" == 1 ]; do
sleep 1;
echo 1 > /sys/kernel/mm/ksm/run;
done&

Feels needless in my head to try and write the value every time, which is why I used to have that just below the wait loop, but it keeps everything that needs to happen later in the subshell, and that's the important thing now.
[SuperSU] Dead-neM:
Ok thanks, so I'll rework some part of mine.

until [ "$(getprop sys.boot_completed)" == 1 ]; do
sleep 1;
echo 1 > /sys/kernel/mm/ksm/run;
done&

Is bad cause it will loop the echo cmd inside the until your code should like this

until [ "$(getprop sys.boot_completed)" == 1 ]; do
sleep 1
done
echo 1 > /sys/kernel/mm/ksm/run

Like that you doesn't need to write the until do done part for every echo. As it will loop until the prop is 1 and then start working.
[SuperSU] Ja_som:
Only a small report...

Nexus 5x Android 7 NRD90S and Nexus 7 II AOSP Android 7 NRD90U no issue with SR1

;) :good:
[SuperSU] osm0sis:
No, I explained that. The echo needs to be in the asynchronous subshell as part of the until loop using the &, otherwise it holds up the boot. Like I said, we need to rethink things/retrain ourselves with things like this now that we know su.d works like Chainfire explained. Please reread my post. :good:
[SuperSU] Dead-neM:
Oh ok my bad i didn't get it the first time. I'll try this on my script.
[SuperSU] egingell:
I'm pretty sure he knows that because it needs to run asynchronously (hence the ampersand) after the code-block.

Maybe

do
until [ "$(getprop sys.boot_completed)" == 1 ]; do
sleep 1
done
echo 1 > /sys/kernel/mm/ksm/run
done&

Disclaimer: I'm not entirely sure do...done can be used like that.

Edit: Why was there so much blank space?

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] USBhost:
I can confirm done can be used like that "done&"

"You learn something everyday"
[SuperSU] NLBeev:
I agree with you, but there is in my view hardly a risk. Normal apps are more risky, because most users don't expect a risk.
[SuperSU] Dead-neM:
Yes but this code is incorrect as the first do will do nothing and return an error. I think when [MENTION=4587767]egingell[/MENTION] said " I'm not entirely sure do...done can be used like that " he was talking about the place where do done was not the "&"
[SuperSU] egingell:
I was talking about wrapping lines of code inside a do...done block and then running that block asynchronously. I don't know if it'll throw errors or not. "Unexpected 'do' on line 1"?

E.g.

do
Stuff
done

Edit: This all seems clunky, but what about:

if true; then
Whatever stuffs
fi&

A separate file that executes the script would probably be the best option, though.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] USBhost:
O so that's what you meant ...

Something like

do

do

done&

done

Edit or I'm lost and to sleepy... Don't mind me
[SuperSU] egingell:
Yeah, but with the ampersand outside the block. ;)

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] bon122728:
what happened?

Tried to update my su to RS1v2.78 by flashing but after it boots when i open SU in my settings it says I am not rooted and have no SU binaries installed.

(i didn't unroot, just tried to flash the latest su v.2.78)
[SuperSU] osm0sis:
Nah, that if statement will run asynchronously, but for no reason since it just runs immediately anyway; that's why you need a sleep and a loop of some kind (while or until, usually).

The sneakiest/best way I know to do what we're talking about is actually this:

while sleep 1; do
if [ <whatever> <comparison> <value> ]; then
<commands and stuff>;
break;
fi;
done&

That way it waits in a subshell, only runs the necessary commands once, and then breaks the loop to end the subshell as well.
[SuperSU] egingell:
Wait... So the if block will run asynchronously, but the until loop inside it won't? That's... weird, man.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] osm0sis:
You didn't have a loop in your if.. but... maybe that would work? `while sleep` is still probably the best way; same idea basically.
[SuperSU] 0.0:
[MENTION=631273]Chainfire[/MENTION] I am having strange behavior with SuperSU SR1...

From a stock boot.img, I installed SuperSU first, then ElementalX kernel, then Magisk. I now keep getting asked to update the binary when entering the SuperSU app. I ignored it temporarily but when I open and use root apps to test if they work (e.g. AdAway, EX Kernel Manager, etc.), there is no error and I am able to perform rooted functions without confirmation ("Allow"). I tried Magisk and toggling root off and it is able to do so without asking me to "Allow." So it seems, any root app will work without "Allowing" which is concerning. I am using a Nexus 5X.

edit: more details that I forgot to add. In the SuperSU app, a list of the "Allowed" rooted apps do not appear nor any logs because all apps bypass the "Allow" or "Deny" function
[SuperSU] ianmacd:
It's not so much the done as it is the until. while and for work the same way, as does anything that is a command.

---------- Post added at 10:29 ---------- Previous post was at 10:15 ----------

The simple fact of the matter is that no-one can be certain they can trust SuperSU, except for Chainfire and the few other people with access to the code who are capable of properly auditing it. Nothing else can provide that certainty, so there is nothing that will "cut it"; and this is actually how it has always been.

Really, it's time to get over it now; and the rampant sinophobia that has reared its ugly head these last few weeks.

If you think SuperSU might secretly be trying to take over your device and impose communism on the free world, don't use it. Otherwise, you're going to have to exercise a little faith, and reassurances from Chainfire actually don't add anything to what you already have. You already know the man's reputation. Have faith in him or don't, but please stop asking him to testify. It's rather rude.
[SuperSU] NLBeev:
Don't forget that only the light half of the world is facing the sun. ?
[SuperSU] grep_i:
Is there any way to avoid reflashing custom kernel and Xposed by every update of the SuperSU binaries or is that the culprit of using systemless ?
[SuperSU] osm0sis:
If you're on a custom ROM, you could flash the custom kernel, then Xposed, then SuperSU, so the SuperSU zip is backing up the modified ramdisk. Then flashing subsequent SuperSU updates over top should retain those changes.

If you're on stock ROM, you'll probably want to keep your SuperSU backup as the untouched boot.img for OTA purposes. In that case, yes, you'll need to reflash anything like Xposed or a custom kernel that further modify the boot.img each time.

That said, you could rig up a FlashAfterUpdate type functionality as part of a /data/custom_boot_image_patch.sh script so the SuperSU zip will flash them itself automatically, but, really, is it that hard to queue this stuff up in FlashFire or TWRP? No. SuperSU updates aren't frequent enough for it to be too bothersome.
[SuperSU] grep_i:
Thanks for the answer.

I am on stock rom Nexus 5 MOB31E firmware and my custom kernel is ElementalX N5 6.21 which prefer to be rooted before flashing it.

I do not know exactly when this problem started but I guess it was when SuperSU started with a modified boot.img probably to help support systemless Xposed and they both started with automatic cleaning of caches and dalvik after every flashing.

Or maybe it was always like this and I never had to deal with it because I did only full rom install which would already require me to reflash, custom kernel, Xposed and root.

Last 2 or 3 SuperSU updates I updated only the SuperSU binaries and was surprised I got to reflash custom kernel and Xposed too.

I know why it happens and it's not a big deal to do it but the recreating of the caches with dex2oat takes so long every time.

In the past I never did clean dalvik and cache and had no problems and for me it speeded up my update process.

Before all this updating Supersu was 5 minutes with rebooting to system again note it takes almost 30 minutes.

Updating full rom was 10 minutes now almost 30 minutes.

Maybe I can find out how to stop the flashing to clear the caches.

Thinks for helping me think in another direction.
[SuperSU] swapgut:
Same thing happened to me, I'm on PN 8/3. I didn't think my got-root? prerequisite apps would work so I had to revert to 2.78 from the app store.
[SuperSU] coldconfession13:
I had flashed unsu. Reboot then went back to recovery and flashed the zip and that fixed it
[SuperSU] swapgut:
OK.... I had not used unsu at all. I did update to TWRP 3.0.2-2 recently.
[SuperSU] andrei1015:
Got a bootloop when trying to update the binary. Reflashing today's nightly solved the problem. Why does this happen?

Tried again, and still can't update the damn binary :(

EDIT: also can't install the app to /system..
[SuperSU] mielletseed:
Would you mind to inform yourself - [MENTION=631273]Chainfire[/MENTION] announced a statement about ccmt - coudn't we wait for that before endlessly discussing ccmt? Or could all you chinese skeptic or not chinese skeptic but "strange finding" guys not just stop using SuperSU than endlessly discussing that fact in that threads? :rolleyes:
[SuperSU] rrobertk:
root

are who know where can i get root for my samsung galaxy s (gt i9000)

baseband version: i9000bujv4

karnel: 2.6.35.7-i9000bujvg-cl719381 root@DELL1403#2

build: gingerbread.bujvg

thanks for help :o :good:
[SuperSU] rrobertk:
i know i saw all this site but i cant find root for my version..need help :(
[SuperSU] Pkt_Lnt:
That thread IS meant to HELP. THIS thread is NOT the place. You are off topic here, try your device forum, and please don't tell me there is not one.
[SuperSU] egingell:
You can use z4root on that archaic phone.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] matlala:
Anyone know why supersu not logging on nougat? I trying v2.76 to 2.78. SR1. No changes,still not logging.

J have nexus 5X with latest factory rom, elementalx kernel and systemless adaway. Maybe problems is only on arm64 device. My N7 2013 with aosp nougat haven't this problem.
[SuperSU] ulxerker:
here's the subforums for your device, please look there and ask there for help if necessary: http://xdaforums.com/galaxy-s-i9000

:D:good:
[SuperSU] ech1:
Unable to root Nexus 5X

I am currently unable to root Nexus 5X NRD90S

It is failing at

boot image patcher

adding daemon launcher

failure, aborting

Am I missing something?
[SuperSU] Alxoom33:
No problems flashing 2.78 SR1.zip in TWRP on Nexus 6 and Pixel C both running latest 7.0 OS.
[SuperSU] ech1:
Bootloader unlocked, using TWRP 3.0.2-2, worked in NRD90M but not in NRD90S

2.78 caused bootloop

2.78SR1 is failing
[SuperSU] Dead-neM:
NEWS from su.d script

Ok i've finnaly find that the better way for me to run my script was the "liveboot way" which was explained by chainfire on the first post of the debate

It's working for me like i said previously but it will not exit the script if launched from a terminal but if you run the liveboot script to run the test script it will not exit too so i think that's not so bad exept if you have loop in your script that write value on conditional and until they write an other one

things are not clear ok just try the below:

-move myscript into /su/xbin

-create a script (named "ZzZ" to be run after every other one):

#!/su/bin/sush
MYSCRIPT=/PATH/TO/MYSCRIPT
/su/bin/sush $MYSCRIPT &

voila

this work and i can boot 2.78-sr1 with this and my script is fully working
[SuperSU] Alxoom33:
What device? Not Nexus 6?
[SuperSU] hunafaa:
At your recommendation I installed FlashFire. I flashed SuperSU via FlashFire even though I have TWRP installed.

I was amazed at the utilities included in it. Most importantly the ability to do a full backup including internal storage.

Thank you very much.!
[SuperSU] ech1:
Nexus 5x
[SuperSU] Crazy Chuckster:
I downloaded NRD90S on my Nexus 5x yesterday with an unlocked bootloader and the update was OTA as I had uninstalled supersu and reflashed stock boot, vendor, etc before upgrade.

After update was finished I flashed twrp 3.0.2-2 and then installed the latest SR1 version of supersu with no problems. Root is working perfectly as well.
[SuperSU] nefescalanadam:
Any problem with supersu + superhide on Cm13 for mako (nexus 4) ?
[SuperSU] Ja_som:
I have no issue with 2.78 and also with SR1 on my N5x with NRD90S
[SuperSU] Renix63:
Not work 2.78 SR1 on S3 Neo Lollopop 5.1.1 TW motion rom....
[SuperSU] H4X0R46:
What exactly is the SR1 update? I'm late to the party here, how is it different?
[SuperSU] Ja_som:
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post68698877
[SuperSU] H4X0R46:
Ah thanks man! I searched a few pages back for it but must have skipped right over that post! Thanks!
[SuperSU] nefescalanadam:
Supersu + suhide with Cm13 for mako (nexus 4 ) isnt work.
[SuperSU] bon122728:
I succesfully flashed the latest su 2.78RS1 but when i try to open supersu app it say ls there is no binaries installed. Is this normal? If not how to fix this?

Im using zenfone 5 with RR5.7.2 6.0.1
[SuperSU] nefescalanadam:
Same thing to me, cant solved on Nexus 4
[SuperSU] ApriliaM3:
Similar here... My supersu app has disappeared completely.
[SuperSU] ciopik:
Same thing to me, cant solved on Z5C
[SuperSU] Strephon Alkhalikoi:
SR1 worked flawlessly on both my Nexus 6 (Pure Nexus 6.0.1) and my Galaxy S4 (AOSP 7.0.0) without issue. On a lark I tried SR1 on my five years old phone still running Android 2.3.3, but it didn't work.

Before anyone asks, no I'm not sending a logcat. This was only to see what would happen, and not for serious work.
[SuperSU] ech1:
Do you have fbe enabled?
[SuperSU] Ja_som:
Eh, no. If you wrote it before, then sorry i did not see it...
[SuperSU] radz_:
2.26 works fine for me.. S4 4.4.42