yashsingh1/xdaforums huggingface dataset:
[SuperSU] stokholm:
I want to I unroot and completely remove SuperSU, but I want to do it *manually*. Why? Because. Call it educational purposes if you like. Paranoia if you like.

I rooted my 6P Nougat by flashing the zip in TWRP. Is this the correct procedure to undo this?

- Uninstall SuperSU app.

- Reboot to bootloader.

- Flash stock boot.img.

- Reboot to recovery.

- Delete /data/su.img.

- Clear cache.

- Reboot.

Any traces left over? What about the boot.img backup, where does SuperSU keep that?
[SuperSU] corkiejp:
Added an extra step above.
[SuperSU] Alxoom33:
I did not have any issues with the automatic 2.78 update on My Nexus 6 and Pixel C both running Android 7.0
[SuperSU] stokholm:
I said I want to do it manually. And wouldn't the full unroot include my other steps?
[SuperSU] fmc000:
Doesn't clear any caches, because it's obviously useless. Full unroot asks if you want to rollback directly to the kernel it had backed up during the rooting process and even if you want to go back to stock recovery.
[SuperSU] stokholm:
Okay, but that still doesn't answer my original question. I want to remove all traces of SuperSU and unroot manually. I don't want to use the "full unroot" feature of SuperSU *at all*. If you can't/won't help you don't have to reply.
[SuperSU] fmc000:
And if you can't read, don't quote me. My answer was meant to say "yes, this is more or less what full unroot does". Is that clearer now, son?
[SuperSU] stokholm:
You're right, I didn't read that properly. Sorry.
[SuperSU] fmc000:
That's OK, no hard feelings :)
[SuperSU] Only4givenOnceOfficial:
how does one contact mr chainfire?? I have a possibly simple task I need help with. Grandprime SM-G530T1 I need help getting a working rooted rom with a twrp that can get xposed on it. I have a twrp that works with my phone currently on hand. The CF-Autoroot for the SM-G530T not the T1 works on my phone but is a little buggy eventually starts to say this or that has stopped working., also I would like to know how to add a updated version of supersu to the rom. End goal here is.. instead of needing that stock rom and recovery, I want to use a custom one as a stock to go back to if I mess something up instead. I would really appreciate help as I am not doing this just for my self but for a few people I helped get unbrcked on here and taught them how to get rooted. The TWRP I have is for the SM-g530t so it claims but when you boot into recovery mode the phone connect to the computer saying that it is a g530w. I keep losing root and having minor issues. I am new to this an only have a few more days with a computer to use. :( I am using ASSAYYED Kitchen for windows to try to make a custom rom but it is giving me hell. messing up my keyboard functions such as swype and a few others so I am trying to figure out how to get everything ported smoothly to my phone so I can make a decent rom and upload it for everyone needing it. :) My email is Only4givenOnce@gmail.com if You can help me or Chainfire if you read this and feel awesome enough to hook me up. :) I can supply any data you need more than likely. Please help. I hate this phone. lol
[SuperSU] purian23:
You just contacted him. If he's interested, he'll respond. There is a new thread for the fold who took over SuperSU though. You might want to look there first.
[SuperSU] Only4givenOnceOfficial:
oh ok thanks.. what is the thread. I have been trying to get a working rom and recovery going for a couple months and got nothing stable yet.. Don't own my own computer my ex stole my last one so it doesn't make it easy. lol
[SuperSU] purian23:
You can find the new official thread here.
[SuperSU] jalizi:
Hi

I have the latest TWRP recovery and rooted MM 6.0 on G3-D855 , but when I try to update SuperSU to newer version higher than the 2.52, the following error appears and root access lost:
[SuperSU] ktmom:
Look here: binary update thread
[SuperSU] Pkt_Lnt:
Flash the zip file in post # 1 in TWRP. It has the update and the binaries.
[SuperSU] Adzkii:
Is 2.77 BETA systemless?
[SuperSU] ktmom:
Yes

Systemless capabilities started with 2.56 and subsequent releases have been improvements. There is a script that performs checks to determine what mode to install in. Search this thread for more info on that.
[SuperSU] jalizi:
I did exactly what you say, but it was not updated.
[SuperSU] Pkt_Lnt:
Post the recovery log from TWRP so we can see why not.
[SuperSU] Adzkii:
Suggest any keywords so i could find this check script? :P
[SuperSU] ktmom:
Somewhere around here.
[SuperSU] jalizi:
Where can I find (or get) recovery log from TWRP?
[SuperSU] Pkt_Lnt:
In TWRP > Advanced > Copy Log

Flash the zip firlst, then copy the log
[SuperSU] jalizi:
I try to update supersu from 2.52 to 2.77, but after update and reboot phone there is no supersu in applications list !
[SuperSU] NLBeev:
You jumped probably from system root to 'systemless root'.

Uninstall 2.5x first and flash 2.77 again as the last file before reboot.
[SuperSU] Pkt_Lnt:
The install was successful. Some ROMs place the app in Settings somewhere, search through there. Also try the keypad commands from post #1 to see if it will open. If you open a root app, are prompted to grant root?
[SuperSU] jalizi:
1- But when I check root access by root checker app, it shows that I don't have root access.

2- Which keypad commands you mean? I don't see any keypad commands in post #1.
[SuperSU] egingell:
Try a different more current root checker.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] Pkt_Lnt:
Post # 1 Stable thread, linked in post # 1 of this thread.

"Launch from dialer"

http://xdaforums.com/showpost.php?p=23427715&postcount=1
[SuperSU] ktmom:
If you have a terminal app, you can issue the command "su". You should get a prompt to allow, but if under some other root than SuperSu, you might just get a # prompt. It'll change from the $.
[SuperSU] ktmom:
Way back when.. [MENTION=4544860]osm0sis[/MENTION] posted a script to automate the removal of pre-systemless SuperSu (e.g. 2.52) prior to installing the systemless capable version (e.g. 2.56 +).
[SuperSU] Bingley:
I've just unlocked my Nexus 7 2013, rebooted, flashed the whole stock rom as per google's instructions, started the device, signed in, enabled usb debugging, rebooted into fastboot, followed these instructions, flashed the boot image (tried both for this device), booted twrp.img and flashed/installed 2.56 (also tried latest 2.66) and it says sucess. Upon booting up I open su app, it updates the app from the play store, I open this, and it says I'm not rooted.

Can anyone tell me what I'm doing wrong?
[SuperSU] Ch3vr0n:
Yeah, you don't need a custom boot image. You only need 3 steps

1. Unlock bootloader

2. Boot into custom recovery through adb boot (or flash it)

3. Flash su zip and reboot ( the latest is definitely not 2.56 nor 2.66, it's 2.78)

All done
[SuperSU] ipdev:
Google has good instructions on restoring stock roms.

(I'll look back but, it does seem like a step is missing or has been changed?)

Which one did you use?

https://developers.google.com/android/nexus/ota

https://developers.google.com/android/nexus/images

Best off to ignore the last bit of instructions if you plan to run custom roms, or just want the ability to use fastboot without limitations.

IGNORE THE BELOW STEP.

Once the script finishes, your device reboots. You should now lock the bootloader for security:

Start the device in fastboot mode again, as described above.

Execute:

fastboot flashing lock

or, for older devices, running:

fastboot oem lock

IGNORE THE ABOVE STEP.

I use fasboot to boot twrp (In your case I believe it would be)

fastboot boot twrp-3.0.2-0-flo.img

Then use twrp-advanced-sideload

adb sideload SuperSU-v2.78-201609011115.zip

I will hopefully have a 2013 7 by next week to play with.

(Might just give up on my Samsung(s) if I like it.)
[SuperSU] jalizi:
Can anyone tell me how to work with supersu through the windows terminal ? please get me the tutorial link of this
[SuperSU] egingell:
Type "su" and hit enter or, if you have to do it in one command, type "su -c COMMAND". End of tutorial.

Edit: Oh, for Windows? Search for "adb".

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] Bingley:
Thanks, I did exactly that but I think I had an old beta su - using your numbered one worked, thanks!
[SuperSU] lorvix:
where i can find supersu 2.78 TWRP zip ?

edit: i find it :)
[SuperSU] tohtorin:
Does sush read sushrc ? Where should it be located? /su/etc ?

EDIT: Found solution already. Sush was just /system/bin/sh with different selinux stuff and reads /system/etc/mkshrc which I made systemless with loop mount
[SuperSU] ipdev:
Glad to hear good results.

:)
[SuperSU] bobika.99:
Hallo,

i have simple question. Works supersu on the Samsung Galaxy SII (i9100) with CM13? TWRP report error 'failure aborting' (v2. 76, 2.77). CM12 with supersu works perfectly.

Thanks and sorry for my bad English.

Odesláno z mého GT-I9100 pomocí Tapatalk
[SuperSU] ktmom:
Don't apologize, your English is fine ☺

Take a look at the TWRP log. Probably the easiest way is after flashing the SuperSu zip, tap on advanced and the use the "Copy Log" button. This will place the log in internal storage, usually "/sdcard/recovery.log" or maybe "/data/media/recovery.log".

If reading the log doesn't help you, paste the log to pastebin.com and post a link here.
[SuperSU] bobika.99:
How do I attach a link?

"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showthread.php?t=1069298
[SuperSU] bobika.99:
Here is log:

http://pastebin.com/R8iw96cV
[SuperSU] snachez:
Can anybody suggest a method to prevent the play store from offering updates to 2.78 if you already happily have installed 2.76/77 and are not wanting to upgrade ?

Something similar to resigning an .apk with test keys (like the QuickPic situation)... but as SuperSu is a little more complex than a simple apk this doesnt seem to be a straight-forward option. I'm open to all suggestions :)
[SuperSU] grep_i:
I did answer you in the stable thread already, please do not cross post.
[SuperSU] b*_gently_*d:
SUhide on GT-i9070p Samsung Galaxy S Advance, Android 6.0.1beta?

Hi guys!

To fully understand my question, you perhaps want to read this post or have a look at the whole thread.

The point is: Is there a chance of fooling my device in the future? - because as for now, I'm stuck with the stock firmware and would love to have a working customROM that still can provide a working bank app ...

Thanks a lot for a short reply :rolleyes: :fingers-crossed:
[SuperSU] agentfazexx:
http://www.androidpolice.com/2016/0...okemon-go-plus-support-blocks-rooted-devices/

Anyone have a workaround for this stupid block that is using SuperSU?
[SuperSU] corkiejp:
Also posted about it on XDA: -

Latest Update to Pokémon GO Blocks Rooted Devices from Entering the Game

You might try suhide from chainfire.

Edit: Just check the thread and it doesn't work for it.

I haven't played for the last few weeks for medical reasons (don't want to post what), game has not updated yet, might be time to delete the game.
[SuperSU] agentfazexx:
Yeah like I've paid for it yet they're blocking users who aren't cheating and have paid money for it...this game is going downhill pretty quick.
[SuperSU] force70:
The fact that grown adults even play this is hilarious...i mean just for fun or to try it hell why not...I did for 5 minutes before i realized thats 5 minutes of my life Ill never get back :D

The fact that grown adults take it even remotely serious is just wrong lol.

That said yeah...id be unhappy if I paid for it and they blocked me...what you do with your phone when it comes to root etc is totally your business. You paid for something it shouldn't matter if your device is rooted or not.
[SuperSU] Blueblob:
Nice help, big mind ?

I guess systemless should work

Where is my Pure Nexus ROM ? ?
[SuperSU] RandomPooka:
Hush with the nonsense about whether you think it's ok for an adult to play. Literally nobody cares if you think it's appropriate for them. I feel the same way about football as you do about Pokémon Go, but you don't see me making fun of people that watch it.

As far as paid.. It's a free game.

As far as root users being blocked, I would imagine that it's to prevent GPS spoofing. I wonder if they're using the Safetynet that AP uses
[SuperSU] force70:
Never made fun of anyone, perhaps your reading into what i wrote or your reading comphrension is not the best?

i just happen to think its ridiculous. An opinion I am allowed to have and express if I feel like it.

I do like football and watch it (good guess lol) i dont take any offense or have any feelings for that matter to the fact that you may not like it or may even think its ridiculous!

Thats your opinion and I respect that 100%.

And that's enough OT for me, sorry for that fellas..my bad.

I am curious as to how they are blocking it though.

Im sure someone will find a workaround...we always do here :D
[SuperSU] agentfazexx:
I played it in middle school man, it's not that "hilarious." But, judge away. That's your right.
[SuperSU] RandomPooka:
Yes, there's nearly ALWAYS a workaround. That's why I was wondering if they were using the same detection methods as AP.

---------- Post added at 07:44 PM ---------- Previous post was at 07:40 PM ----------

Also, you literally said that it's wrong for an adult to play it. I understand that this isn't a direct attack at anyone in particular (unlike your comment about my reading comprehension), but it's a vague statement implying that anyone who is an adult and plays it should not. I'm thinking my reading comprehension is fine and maybe that was worded in a way that made it read differently than you meant it to. It's ok, though. As grown adults, we can all get over it and move on to figuring out how to prevent the problem.
[SuperSU] :
Let's not be judging each other for our entertainment choices folks. I bet no one here would like anyone seeing their web cookie cache? :silly:

Let's keep it civil. Alright?

Cheers,

Darth
[SuperSU] corkiejp:
[Off-Topic] Quote from XDA link posted earlier.

I'm adult and only played the game a small bit to try it out. Never been to a gym. As mentioned earlier haven't played in weeks.

In the XDA link, there is a workaround for it but involves using an alternative root method, won't mention it here.
[SuperSU] RandomPooka:
I'm guessing it is magisk related?
[SuperSU] egingell:
You're all aware that most "grown adults" were the prime demographic when Pokémon first hit the stores, right?

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] NLBeev:
Delete OT
[SuperSU] nathanchance:
A senior moderator already posted to end the off topic conversation of Pokemon Go. Let's move on for real this time.
[SuperSU] RandomPooka:
We're keeping it civil, as asked, and were discussing workarounds.
[SuperSU] ktmom:
It belongs in a Pokemon thread.
[SuperSU] RandomPooka:
Or a Safetynet with root thread, sure.
[SuperSU] bobika.99:
Any solution or any owner i9100 with supersu and cm13? Thanks
[SuperSU] ktmom:
It's trying to edit the boot.img

Try forcing system mode by typing into a terminal before flashing SuperSu:

echo SYSTEMLESS=false>>/data/.supersu
[SuperSU] bobika.99:
1. i flash cm-13.0-20160829-NIGHTLY-i9100.zip

2. wipe cache

3. insert code by terminal

echo SYSTEMLESS=false>>/data/.supersu

4. flash BETA-SuperSU-v2.77-20160827190633.zip

5. wipe cache

6. restart

... and phone does not start, displays a blue cyanogenmod logo. Here is log: http://pastebin.com/5XVf3iy4

Some solution? Thanks
[SuperSU] mielletseed:
I'm just guessing but for Samsung since 5.1 and for others since 6.0 patching of SELinux policies is necessary. Without patching the kernel image my device didn't boot too. So system mode is not longer possible I'm afraid ...
[SuperSU] mochamoo:
I don't have /data/.supersu under root. ???
[SuperSU] egingell:
And you wouldn't. It's a text file that gets written when issuing the command mentioned.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] mochamoo:
Duh! Thanks.
[SuperSU] Kamal363:
Try rootcloak module...

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] Chainfire:
v2.78 SR1 released

v2.78 SR1 (aka beta) has been released.

Release notes are here: https://plus.google.com/+Chainfire/posts/8mPirmjhgqT
[SuperSU] robot_head:
Does this not have an interface, can't find supersu app for settings once flashed, for sr1
[SuperSU] osm0sis:
Was the intent of that last item to increase the boot time by a minute? That seems to be the case on my N5 running stock ROM.. just hangs at the Google logo for a long time before continuing.. :confused:

I've definitely never had any issues with su.d scripts running out of execution time.. my gappsintegrator script always continues to run for up to several minutes after boot completes no problem.

To reproduce the issue I'm assuming you just need a su.d script that sleeps until sys.boot_completed like mine currently does (to set a sysfs value overriding the ramdisk). Hopefully things can go back to executing in the background and not holding up the boot.
[SuperSU] Dead-neM:
[MENTION=631273]Chainfire[/MENTION]​ i wonder why increasing the su.d script launch time to 60 from 4 seconds?

I haven't tested it but doesn't it cause problem for LiveBoot? And also i have my script to setup lots of things and i want it to be run when bootanim is launched.

But maybe i haven't understand it correctly and it make su.d script 60 secs to excute and passing this delay scripts won't be launched. Which is this case avoid some problem i guess and i have nothing to complain.

Anyway your work is awesome. Thanks for your work! ﻿
[SuperSU] dratsablive:
This won't work for latest version of Pokemon Go. It now uses Safety Net to detect root.
[SuperSU] Kamal363:
Sorry then... not playing anymore...

Send from SM G900F xXx v5.3 Neox-Boeffla-Zram Twrp 3.0.2-0
[SuperSU] KaMyKaSii:
I was happy to hear about the possible compatibility fix with Magisk, then decided to test. I was in TWRP, mounted /data/magisk.img, deleted the related folder to another super user manager, and I install SuperSU. Already I got a little confused when it was installed in system mode, which before always installed in systemless even without the /data/.supersu terminal command. I thought I'd give bootloop because before when i tried to force the system mode (i was without PC was and could not run the risk of running out of root/TWRP) always entered bootloop, but this time I believe that the changes in the boot.img made by Magisk cause Android boot. I opened the SuperSU app and said no binary was found, but when I opened the FX File Explorer and navigated to /system/xbin/ the binary "su" was there. I thought it was a bug first boot then restarted, but again the same thing. I went back the TWRP, installed the stock boot.img (removing Magisk) and reinstalled SuperSU now installed in systemless and it worked perfectly. So I do not know how it is in other devices, but at least in my seems that compatibility does not work yet

My device:

Quantum GO 4G, Android 6.0

http://www.meuquantum.com.br/smartphone-quantum-go-4g-32gb/t/20
[SuperSU] Chainfire:
On some custom ROMs it is under "Settings". Otherwise, it may be that the system has not picked up the change.

You can take the APK from the ZIP and do "adb install -r /path/to/apk" from your computer to fix it, probably.

I think you both misunderstand how su.d is supposed to work. These are the guarantees:

- All SELinux patching is complete before su.d scripts are executed

- All scripts inside su.d are executed in alphabetical order (0-9a-z)

- Scripts are run serially. The next one in order is not started until the previous one has finished.

- Boot does not proceed until all scripts have been executed

--- unless your boot image does not support exec (very rare)

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

If your script does not need to delay the boot process, the script itself should make sure its actions are run asynchronously.

These scripts must delay the boot process, otherwise mods like (the first versions of) systemless xposed just aren't possible. And those sorts of mods are exactly what su.d was made to enable.

Example case: LiveBoot

/su/su.d/0000liveboot: (due to 0000, almost guaranteed to be the first thing run)

/su/bin/sush /data/user/0/eu.chainfire.liveboot/files/liveboot &

It calls SuperSU's copy of the shell, and has it execute /data/user/0/eu.chainfire.liveboot/files/liveboot. But due to the & sign at the end, this happens asynchronously in a background shell (standard scripting stuff).

In other words, LiveBoot delays the boot only for the few milliseconds it takes to spawn the background shell. It has no need to delay the boot process, and thus it doesn't.

Conclusion

If this delays your boot by one minute, one of your scripts needs adjustments. It was always delaying the boot process, now it just delays it a lot more and makes the problem apparent.
[SuperSU] Chainfire:
Some compatibility issues with Magisk were indeed fixed, but compatibility is not complete. There are still changes and fixes that need to be made inside Magisk; hopefully the next Magisk version will see full support, [MENTION=4470081]topjohnwu[/MENTION] is aware of the issues.

One of the things that Magisk breaks is the PATH, systemless su is removed from it. So you must enable BINDSYSTEMXBIN in SuperSU, and then still some commands will not work. Of course, Magisk's root toggle will not work with SuperSU either currently.

But that is why I am building suhide :)
[SuperSU] KBanause:
I just updated to 2.78 SR1 and some apps are having problems detecting that the device is rooted (Nexus 7 (2013) stock, build MOB30X and Nexus 6P, stock, build NRD90U). For example Helium or Secure Settings. Titanium Backup or Recently for example don't have any problems.

I can't tell which version was the last one working. I just noticed it after I have reinstalled Secure Settings on my Nexus 7 with SuperSU 2.77 BETA installed and it's telling me now that it's not rooted.
[SuperSU] Chainfire:
Sounds to me like you had the old app compatibility mode enabled (BINDSYSTEMXBIN) previously, and you have it disabled now.

From adb shell (or Terminal Emulator), run 'su', then:

echo "BINDSYSTEMXBIN=true">>/data/.supersu

Then, reflash SuperSU.

Note that if your TWRP cannot decrypt your /data partition, this solution will not work.
[SuperSU] KBanause:
Thanks. Even though I didn't find /data/.supersu (on both devices) it has worked after I created the file and added the line you mentioned.
[SuperSU] ashyx:
Im curious as to why cache isn't used instead of data to circumvent that issue if the command only has to be set once?
[SuperSU] robot_head:
My problem with no ui was possibly from flashing over 2.77. Clean installed everything and all is good now. Thank you for the response.
[SuperSU] danmaman:
hi

I'm on stable playstore version 2.78

can i flash this SR1 with flashfire over this?

or comes in near future an playstore update?

thanks in advance
[SuperSU] ulxerker:
yes.
[SuperSU] smitharro:
Just did that! Works like charm! (CM13, Lenovo Moto G4 Plus).

Send with my Moto G4 Plus (XT1642) with CM13 using Tapatalk!
[SuperSU] Chainfire:
You can use /cache/.supersu if you want. It also works :)

I am hesitant to rely on /cache though. Many people wipe it out of habit. And some tools do automatically.
[SuperSU] chazall1:
All working here after updating.

Thanks
[SuperSU] JayKudo98:
Can someone post link for SuperSU pro n its procedure?
[SuperSU] egingell:
:confused:

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] Pkt_Lnt:
Go to the Google Play Store, buy SuperSU Pro, the Play Store will install it for you. Done.