yashsingh1/xdaforums huggingface dataset:
[SuperSU] egingell:
Um... Why are you using touch? Touch only creates an empty file. Of course that broke root. TiB is trying to execute an empty file.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] pkelly517:
Use ln -s instead of touch.
[SuperSU] RBA5901@gmail.com:
SuperSU version 2.76

I recently rooted my Samsung SM-G935A phone using a SuperSU-v2.74-2.img. Using the engineering bootloader method and a a 2.74 image.(worked very well)

I tried to kill KNOX and accidentally created a problem, then did a factory reset. (It removed the binary but the phone still thinks that it installed)

I Ran SuperSU 2.76 (my mistake) and it did not complete, however it seems to have changed the image version to 2.76 even though there is no su binary installed on the phone.

Removing and reinstalling the app does not help. Even using the adb switch for allowing a downgrade does not work. I seem to be stuck with 2.76.

If I could do the downgrade, I think the 2.74 image would work.

What I think I need is a SuperSU 2.76 image file as I now get an adb error concerning failure due to a version downgrade when trying to re-root with the 2.74 image.

Any help would be appreciated.
[SuperSU] egingell:
Factory reset wouldn't have fixed Knox and it would have deleted both the su binary and the SuperSU app. Whatever is making it "think" it has root it's getting from the bootloader. And the "downgrade" error only happens when attempting to install an app via "pm install" which has a switch for allowing downgrades.

Edit: I missed the part where you said the adb switch didn't work. Why are you trying to install an image with the package manager?

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] SCrid2000:
Sorry if I'm posting this in the wrong place, but is the SuperSu Pro version in the Amazon App Store the most recent version?
[SuperSU] egingell:
The Amazon app hasn't been updated in who-knows-how-long, but it's just a key. It *should* still unlock the pro features of SuperSU.

Edit: I can't find it on Amazon. Is it even there anymore?

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] ktmom:
I don't think so. The pro key on the play store is now under Codingcode.
[SuperSU] egingell:
I found it, but...

...and...

But it's not the Pro key. I don't think the Pro key was ever on Amazon.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
Yes indeed this is possible.
[SuperSU] CLETjB:
http://xdaforums.com/nexus-5x/help/tasker-secure-settings-systemless-root-t3316450
[SuperSU] Pkt_Lnt:
Just because someone posted that, does not mean it is the best way. Search for the "compatibility mode" solution that Chainfire posted in this thread.
[SuperSU] Chainfire:
After daily nagging by Amazon for months (I kid you not), both SuperSU and SuperSU Pro were available through Amazon for a short time. They were such a major hassle to deal with (a black hole of time and effort) while hardly moving any product, so I quickly ditched them.
[SuperSU] PalmCentro:
What about XDA Labs?
[SuperSU] casonswag:
I can't get this to work on the new nougat update the app keeps freezing for some reason n can't grant root?
[SuperSU] Ja_som:
How you rooted?

On my N5X it works fine, rooted with CF Auto root, then updated via Google Play Store...
[SuperSU] casonswag:
I flashed the latest supersu in twrp but the app isnt working right now and its freezing

---------- Post added at 06:22 PM ---------- Previous post was at 06:11 PM ----------

I got it to work now
[SuperSU] ulxerker:
how did you do it as current TWRP doesn't support N encryption? its not N you have, is it?
[SuperSU] krkhaha:
Samsung 0
[SuperSU] JNewms:
You don't need TWRP to root N. If TWRP isn't working, it's not needed
[SuperSU] nldxda:
There's a new twrp today, check the thread (don't have the link handy)
[SuperSU] MrKaon:
TWRP updated for N support.
[SuperSU] dreamland2000:
Is it showing yet as I checked the website and nothing is showing for a new build??
[SuperSU] kaparo81:
The latest version of SuperSU is compatible with Android N? Thanks ;)
[SuperSU] ulxerker:
look here for your device, after that hit "Primary (Recommended)" under downloads. new version is twrp-3.0.2-1-bullhead.img.
[SuperSU] casonswag:
There's a newer twrp out
[SuperSU] casonswag:
And im unencrypted too
[SuperSU] MrKaon:
What is your device ? for Nexus 6P is here.
[SuperSU] dreamland2000:
I've got the S6. I've got the update now thanks.
[SuperSU] backslashV:
pixel c running android 7

I have the latest beta installed and according to root checker I am rooted. The problem appears when I try to run some apps like BetterBatteryStats, /system app mover, GMD Gestures, ...

Even though I grant root to them, they do not function. properly. For example, BetterBatteryStats refuses to install as a system app. /system app mover shows "Could not remount /system". GMD Gestures gets stuck at "Check for root access". SELinuxModeChanger says "App was unable to gain root access", ... All of these are when root access is granted.

-Is the problem from SuperSU, Android 7, or perhaps the SELinux being enforced?
[SuperSU] Yuaru:
Hello to dev. I want ask why I cant update my su binary from 2.62 > latest. It say "Could not find 'META-inf/com/google/android/update-binary' in the zip file.

Device: Honor 7 TWRP
[SuperSU] hacknmtk:
It's an SELinux problem on Lollipop and up.

---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------

You may have a bad download. Try to download the newest zip and flash it again. That should fix the problem, [MENTION=631273]Chainfire[/MENTION] may have a better answer if that doesn't work.
[SuperSU] RandomPooka:
Also worth checking that you've got the most current TWRP for your device
[SuperSU] grep_i:
[MENTION=7344816]Yuaru[/MENTION]

If I recollect this good from my memory, honor 7 is still not compatible with newer versions of Supersu binaries.

So even if you do all that is asked it won't work.

But it's worth the try.
[SuperSU] HansiHusten:
So I updated my Nexus 9 with Nougat a couple of minutes ago, also noticed TWRP doesnt work and found the new version twrp-3.0.2-1-flounder.img which boots fine, sadly supersu does not work after a flash, guess we will have to wait as many sources say its hard, maybe even impossible, to root Nougat. Lets see and wait :)
[SuperSU] hacknmtk:
If I'm not mistaken, the new version checks a lot on the phone to make sure it gets installed correctly.

You may also want to check the stable version thread for a download too. I'm not sure if the beta version posted here is the same as the stable one.
[SuperSU] corkiejp:
Successfully rooted properly.

Haven't flashed the newest TWRP to the device. Maybe your problem is that TWRP for some reason has not flashed supersu properly?

Try flashing it again with Flashfire or CFAR method.
[SuperSU] HansiHusten:
Thanks for mentioning, I will have a look into Flashfire or CFAR (havent used those methods before so I need to read a bit first)

SuperSu was installed correctly but doesnt work (yet).

Hmm I see ElementalX is a custom kernel, im not a friend of changing kernels so I guess I will pass on this one and wait
[SuperSU] Pkt_Lnt:
Binary update failure support thread is here.

http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] backslashV:
It's odd because I didn't have this problem previously on my pixel c. Also I can successfully run setenforce permissive but that doesn't help.
[SuperSU] MSH2000FF:
Big big thank to [MENTION=631273]Chainfire[/MENTION]
[SuperSU] turilo:
Excellent work on getting SuperSU to work on the Exynos note 7! Thank you
[SuperSU] charlypaez:
I tried to send you 2 beers for Paypal master [MENTION=631273]Chainfire[/MENTION], but your account can't receive transfers from Mexico.. Any suggestions? Thank you

S7 G930F.
[SuperSU] Chainfire:
v2.77 released with support for the Exynos Note 7. Release notes here: https://plus.google.com/+Chainfire/posts/S4ucYdfqPhq
[SuperSU] Farach Amer:
Help me guys î want to root my sony xperia z ultra with supersu but it dosent work and î dont want to du that with Pc plz Help me :gut:
[SuperSU] RandomPooka:
So, no need to update if not using a device affected by this nonsense, then?
[SuperSU] Pkt_Lnt:
Start here.

http://www.xda-developers.com/root/
[SuperSU] chenxiaolong:
Instead of patching UID check, would it be easier to replace "bootmode" with eg. "cf_magic" and then add "cf_magic=2" to the cmdline field of the boot image? That would fool the check into thinking it's booted to recovery mode.

I haven't gotten my Note 7 to test this out yet.
[SuperSU] grep_i:
It's not the same version the stable one is 2.76 and this one is 2.77

I guess your comment was meant for [MENTION=7344816]Yuaru[/MENTION].

I don't have any troubles flashing or installing anything at all.
[SuperSU] AmBugs:
Rooting MMB29K.G925IDVS3EPH2 ?

I would like to root my Samsung S6 Edge - 6.0.1 and Build - MMB29K.G925IDVS3EPH2. How do I go about it?

The reason for rooting is to recover my deleted files.
[SuperSU] white7561:
Think the best way is by flashing recovery. TWRP is preferable . And just flashing the newest supersu

Idk if we need custom kernel or not
[SuperSU] ulxerker:
like almost evry other phone, the Samsung Galaxy S6 Edge has it's own subforums with discussions, howtos and tutorials. you can find it here.
[SuperSU] Chainfire:
This is the first thing we tried, but in our testing it seems the cmdline field of the boot image is completely ignored by the Note7's bootloader, and not passed to the kernel at boot.

Keep in mind though, everything we did was remotely, I don't have a device myself, so it is certainly possible something was overlooked, the tester did something wrong, a miscommunication, etc. Will probably revisit this when I finally have my own device, but that will be at least two weeks from now.
[SuperSU] benmater:
Thinks ..the best app
[SuperSU] ricco333:
I did the same, I updated my Nexus 9 to N, and installed the newest TWRP via fastboot, I just flashed SuperSU 2.76 and then ElementalX, reboot and was un-encrypted and rooted, if you don't want a custom kernel just don't flash ElementalX.
[SuperSU] HansiHusten:
Well thats exactly what I did (but the kernel) :) SuperSU is shown in Android and there are prompts when an app tries to gain access. But in the end the access fails. Are u sure this should work without that specific kernel? Ive only read that it works with ElementX
[SuperSU] NLBeev:
Stock kernel = forced encryption.

It's essential to flash SU before a reboot when using the stock kernel.
[SuperSU] ricco333:
Well, that's true as long as you don't boot the stock boot image, if you flash SuperSU before the first boot it removes the force-encrypt flag from the stock kernel.
[SuperSU] ipdev:
I've been using SuperSu on nougat for the last few months. (n-preview) Had no problem running the final ota to current public release. (Mind you I installed the ota(s) using flashfire.)

(Running volantis-flounder:7.0-NRD90M-3085278 + SuperSu 2.77)
[SuperSU] NLBeev:
Thx. My response was to short.

I will edit and add 'Flash SU before reboot'
[SuperSU] HackeRM76:
After that I went from 2.76 to 2.77 I can not move applications into the sd card ... (Insufficient memory) ... With 2.76 all right ... Galaxy s7 edge (Original Rom not ported)

Inviato dal mio SM-G935F utilizzando Tapatalk
[SuperSU] SkyboneNoya:
Hey so I can't for the life of me get my /system to mount, fix or allow me to install anything in TWRP Although, I can sideload this supersu!

Using:

- HTC 10 Bell Mobility CND, stock 1.90.666.4 rooted with s-off and unlocked.

- BETA-SuperSU-v2.77-20160827190633

- twrp-3.0.2-6-pme

Sorry if this has been covered already I'm just trying to cover all my bases.

Anyone have an idea?

Check my log below.
[SuperSU] egingell:
This has nothing to do with SuperSU. You have installed am app that replaces the sdcard and/or vold binaries. Folder Mount, Link2SD, and other similar apps do this.

Sent from: LG G4 - MM 6.0 / SGS4 - LP 5.0.1
[SuperSU] HackeRM76:
I have installed Mod edit and I can assure you don't work The movement of applications in the sd card after updating to 2.77 ... Returning to 2.76 with backup nand so good ... Because if I flashed on the 2.76 2.77 not working... .... Sorry for the language

Inviato dal mio SM-G935F utilizzando Tapatalk
[SuperSU] egingell:
You would literally be the only person in the world to ever have SuperSU break apps2sd. It can't possibly be SuperSU.

And who knows what Mod Edit is doing to your system. It's malware at best.

Sent from: LG G4 - MM 6.0 / SGS4 - LP 5.0.1
[SuperSU] H4X0R46:
If I was already encrypted and I flash SuperSU, then format my userdata, it would not force encrypt? I've always went with custom kernels, never had an issue, but does this work?
[SuperSU] nathanchance:
With systemless root, yes. It changes the forceencrypt flag to encryptable.
[SuperSU] H4X0R46:
Cool thanks! Is the actual apk installed to userdata for systemless? Would it be removed from formatting userdata?
[SuperSU] nathanchance:
And the su image too. So format your userdata partition first, then flash SuperSu.
[SuperSU] noobSU:
Latest stable release (Binary) breaks the game. I always loose my phone service whenever i try to update SuperSU. (No Service). Old version is working all fine. Please fix.

LG G Pro

LP 5.0.2
[SuperSU] Pkt_Lnt:
1 - You should post reports about Stable in the Stable thread.

http://xdaforums.com/showthread.php?t=1538053

If you need help updating the binary, that thread is here.

http://xdaforums.com/apps/supersu/support-update-failures-t2907365

2 - There is absolutely now way anyone can fix anything without a log showing what happens.
[SuperSU] pruwait:
MMB29K.A310FXXU2BPH2 root needed

1. If I use experimental SuperSU to Root my Android 6.01 Without Modifying /system (MMB29K.A310FXXU2BPH2 - Samsung SM-A310F) - Knox is tripping? Need KNOX 0x00!

2. Which file I need to use with MMB29K?
[SuperSU] ktmom:
This isn't a how to root thread. You'll get real help if you post (or search) in your device forum.
[SuperSU] fubo73:
You are making confusion between rooting a phone and granting root access to apps. Root access must be gained in some way (CF-Auto-Root for example), and SuperSU can then provide root access to all apps.

Up to now, there is no way to root a 6.0 Samsung and keep Knox at 0x0.
[SuperSU] Sytis:
I used the search function in this thread but didn't find anything related to my issue: Tried to root with both latest Beta systemless and systemmode in cache and data f2fs environment but didn't manage to obtain root. On systemless it boots up but Supersu says "No Binary found" and on systemmode it just bootloops. (Using Oneplus 3 with latest OOS and custom Kernel do make it work with f2fs) Just asking if this problem is known or if further logs are needed (or maybe not even relevant to this thread) :confused:
[SuperSU] zalcsooo:
Has anyone tried with Nougat's new file encryption? I got bootloop. :(
[SuperSU] Chainfire:
I've never specifically tested with both /data and /cache in f2fs format, though /data should work. Can you try converting only /cache back to ext4 ?

Not supported yet.
[SuperSU] jazzaddict:
Hey guys!

are there specific instructions to install SuperSU Beta v2.77 in systemless root mode?

I flashed BETA-SuperSU-v2.77-20160827190633.zip through TWRP - Bootloader now say BINARY: Custom instead of official

I was expecting SuperSU Beta v2.77 patch boot.img and not touch /system

This is for klte galaxy S5
[SuperSU] egingell:
Flashing TWRP is what made it say "custom".

Anyway, just flashing SuperSU will make it systemless. I know this because my former phone was also a T-Mobile SGS5... still is, I suppose, it's Wi-Fi only without its SIM card.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] haseoxth:
I saw an updated 2.78 version in play store and local app store, is this version released by CCMT?
[SuperSU] Chainfire:
Yes
[SuperSU] burduli:
So, SuperSU is now fully compatible with Nougat, right? I just got the 2.78 update from Play Store. Pro app also updated
[SuperSU] j3yps:
Should we update to the latest version? Note 7 user here
[SuperSU] ulxerker:
Binary wasn't updated, right?
[SuperSU] aviraxp:
SU binary remains 2.77.
[SuperSU] buffal0b1ll:
Taking the playstore updates for supersu and supersu pro and then updating the binary thru the app bumped the app versions to 2.78 and the binary to 2.77
[SuperSU] Nomelas:
What app is that in the screenshot?
[SuperSU] Spannaa:
It's Root Check ;)
[SuperSU] buffal0b1ll:
Jrummy's
[SuperSU] Thelunchbox1:
Thanks! I just got the new pro update from the play store for my S5 that was still rooted, so awesome sauce. Unfortunately, my Tab E is almost FUBAR from the security patch.
[SuperSU] gothicVI:
Is there also a flashable version? I have had bad experiences with play store updated and thus would like to flash only.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] and00r:
yeah, skipping this release
[SuperSU] Chainfire:
Cannot reproduce, please double-check

Unfortunately no leads yet on what causes this for some users. Is your N5 encrypted? And if so, with a passcode (pin, pattern, whatever, you need to enter before Android boots), or just the new Lollipop 'default' encryption?

What 'all the bugs' ? Exactly one bug has been reported by more than one user, and that's the bootloop bug. Aside from that things seem to be working much better than before.

SuperSU not responding, 9 out of 10 times, is because you're using an overlay app of some sort. Lux seems to be the most popular one. Whitelist SuperSU, or disable tapjacking protection in SuperSU settings.

Regarding errors, I assume you're talking about errors inside the logs for an app? If not, please clarify. Those errors are generally not my domain, and pretty much nothing I can do about them.
[SuperSU] MikeRL100:
Thanks. I'll look into things and post back ASAP. Yeah I was too subjective. Maybe I came off on the wrong note and didn't realize it, so I apologize if I did. I will be more objective. A better word would be abnormal behavior.

I have edited my earlier post. I did mean the logs under the logs tab in SuperSu. I should mention I used CF Auto Root and tried to flash 2.25 with TWRP on the latest build (LRX21R) of Lollipop on my Nexus 9. I used CF auto root and the bundled version of SuperSu worked flawlessly. I do not have any app (as far as I know) that would interfere with Tapjacking protection. I don't have Lux installed. I do wonder if it's tapjacking protection, so I will try disabling it and rebooting.

Edit: Disabling tapjacking protection didn't change anything.
[SuperSU] dyval:
Beta 2.25 working good :) Thanks!
[SuperSU] SpritHansi:
I also have the bootloop.

I have stock 5.0 with root, use pattern and no encryption
[SuperSU] MikeRL100:
I see a bunch of "file not found" errors when the binary is being called.

As for the good news, I don't seem to have any issues on my devices running KitKat.
[SuperSU] landstander:
Yes, it's encrypted using a PIN. I flashed the full Lollipop stock image, rather than upgrading in-place from Kitkat, so it's definitely using the new encryption scheme.

I flashed SuperSU 2.25 via ADB sideload, using TWRP 2.8.1.0 (no visible error messages), and tried the APK update method as well. With 2.23 I only used the latter method, which worked successfully.
[SuperSU] MikeRL100:
Well, how strange this was. I managed to get the root prompts to come back by disabling SuperSu and enabling again inside of the app itself. I hope this helps someone else. If you have issues, try playing with the options. Yes it still works after rebooting, too.
[SuperSU] Chainfire:
Try this one: http://download.chainfire.eu/629/SuperSU/BETA-SuperSU-v2.26.zip
[SuperSU] argonick:
bootloop

Also in bootloop.

After a fresh install of the 5.0 image on my Nexus 5. I booted TWRP 2.8.1.0 and flashed Beta 2.25. It never turned back on.
[SuperSU] DiST_EL:
Is better battery stats working for someone? It doesn't show the wake locks here. I'm on ssu 2.22 beta but it also didn't work with other versions.

Gesendet von meinem Nexus 5 mit Tapatalk
[SuperSU] Chainfire:
I see you thanked the 2.26 post - did that actually fix the issue for you?
[SuperSU] SamuriHL:
Don't know if this has been reported yet, but, CF Auto Root for Shamu is working for me. MUCH appreciated.
[SuperSU] argonick:
Reflashed factory image 5.0 (LRX21O) and flashed Beta 2.26. System started OK.

Root not working:crying:. Message on SuperSU claiming that binaries are not installed.

Root not working tested on Titanium ans ES explorer.

Thanks
[SuperSU] landstander:
I won be able to try sideloading until morning, but can confirm that the APK method was 100% successful. :) Thanx!
[SuperSU] SpritHansi:
Sideloaded V2.26 now, and it worked :good:

Thanks :)
[SuperSU] Ja_som:
After you flash factory image you need to use CF Auto-root to root your device and after that update SuperSu to last version.

I think you don't need to do everything again, now just use CF Auto-root, then update SuperSu again.
[SuperSU] xanaxdroid:
I know this isn't a thank you thread but I have to say thank you for getting root on shamu. Your work is very appreciated and it is always stellar.

Sent from my One+
[SuperSU] Bhaskara Rao:
V 2.26 working fine on Galaxy Tab 2 p3100 with Android-Andi's CM11-Snapshot-M12 and Next Kernel 2.4
[SuperSU] TiZiO.Cover:
No Issues on Nexus 5 and 7 (2013 - WiFi).
[SuperSU] Bhargav Kansagara:
[Q]

hi

i had root access and i flashed 5.0 ROM with root but i lost the root access ...

so i want to ask which version of superSU is preferable to flash 2.19 or 2.25?

nexus 4 ...AOSP Android 5.0
[SuperSU] Kamal363:
Check with root checker..

Superuser binaries not install..

Send from SM G900F xXx 5.2 Odex Boeffla 2.1 beta4 Twrp 3.0.2-0
[SuperSU] grep_i:
Just updated Supersu to v2.78 through playstore but there is no binary update.

The app is not telling me to update binary so I guess this is only an updated root access management apk.

Probably that's why you can't find a binary zip file to download from anywhere.
[SuperSU] ktmom:
ChainFire has already started that he has not worked on a 2.78 release (yet?). The PlayStore update is from the people who bought SuperSu - CCMT. There is no zip to flash newer than 2.77. If it's not in the OP of this beta thread, then there isn't a zip to flash.

With all of the N release excitement, I think there is a percentage of people returning to the thread who have missed the switchover announcements.
[SuperSU] Pkt_Lnt:
CCMT website

http://forum.supersu.com/topic/152/supersu-v2-78-release/3
[SuperSU] ulxerker:
FYI nothing new with the available zip: app version = 2.78, binary version = 2.77

anyway, its good to have something to flash just in case.
[SuperSU] Pkt_Lnt:
FYI - I checked that BEFORE I flashed it. I ALWAYS do. I want to know BEFORE, what is in a zip.
[SuperSU] ktmom:
Here is CCMT's thread for 2.78 +
[SuperSU] Gandalforce:
Mine updated by itself via Google Play. Still stable.
[SuperSU] Praxbe:
Hi,

I've a LG G3 with stock Android 6, rooted, all is working fine since a long time and as i always do a backup before installing/flashing a supersu update for me it's not a problem ...

But i just notice this new update of supersu 2.78 from playstore this morning so i've installed it, and the result is a beautifull "Secure Boot error" after the restart !!

I've put back my backup and then tried to flash the same version (2.78) using twrp and zip file > Same result "Secure boot error" and led flashing blue/red in loop !

So i've put back my backup again and i keep the version 2.77 for the moment !!

Is someone else have this kind of issue ?

Have a good day

thx
[SuperSU] Ja_som:
Try to report it here:

http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
[SuperSU] Shraniksanghvi:
how shall i get twrp for my samsung sm-g600fy

kindly help with any file or link to get the twrp installed.
[SuperSU] Ja_som:
Search/ask in your devices forum...
[SuperSU] Shraniksanghvi:
where to find that ?
[SuperSU] Ja_som:
Use search function...