yashsingh1/xdaforums huggingface dataset:
[SuperSU] egingell:
Stock recovery has never been able to flash SuperSU or any other third-party zip files.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Sam Nakamura:
Why don't you flash a custom recovery via Odin... That would solve all problems, even in future..
[SuperSU] mash4077fan:
At this point in time my phone is not letting me and custom recovery without problems so I can't do that

---------- Post added at 07:36 AM ---------- Previous post was at 07:34 AM ----------

My phone will not let me add custom recovery. So that is not an option at this time
[SuperSU] timz1313:
Yeah that's kewl.. BRO...
[SuperSU] Ch3vr0n:
Quoting the entire first post without actually having a problem or adding something constructive is NOT! BRO...
[SuperSU] ipdev:
Have you tried cf-auto-root?

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

I believe Galaxy s3 is GT-I9300 (models very, prior post I think that is yours?) and is a supported model.

If you have the ability to restore a rooted backup, then restore it to regain root.

FlashFire is a great way to flash zip and ota files. (Along with backup and restore.)

http://xdaforums.com/general/paid-software/flashfire-t3075433

Both are by chainfire. (One hell of a dev.?)

My mistake, I just reread the post and saw that was a combined reply to two posts. Might still be worth looking to see if yours is on the list.
[SuperSU] mash4077fan:
I was finally able to get root and custom recovery back on my phone. A friend of mine brought this thread to my attention and it worked. http://xdaforums.com/note5/orig-development/toolkit-skipsoft-android-toolkit-galaxy-t3399829
[SuperSU] :
No i tried it but it shows signature verification failed.
[SuperSU] Rootcarrot:
LG G2 stuck on cm13 logo after flashing supersu via TWRP

Today, I installed CM13 and later that day i downloaded super su because the inbuilt one is very buggy. so it asked to install su binary, I pressed normal, but it kept saying failed, so I tried TWRP, it said success as i remember, then I rebooted my phone, the cm logo appeared and it like 20 minutes past it still "booting". I tried the hardware keys to reflash the rom but it doesn't work. Please help me, is there any solution to flash the rom via pc, or something like that. Please help
[SuperSU] Ch3vr0n:
You quoted the entire first post that's asking for logfile yet you didn't provide any of them. Did you read it? There's no reason to quote the entire op.
[SuperSU] MigoMujahid:
HI, I realize that supersu isn't working on s2 device with cm13 because of the unsupported compression type of the ram-disk, but is there a possibility that it would support it in the future?

Please reply...thanks.
[SuperSU] TomSka:
When i rooted my LG G3 SuperSu was installed, then i opened it and it said that SuperSu binary needs to be updated, I try to update it but every time it goes unsuccessful, and root checker says that I have no root, and still the same problem after rooting with 2 different methods... Please help!
[SuperSU] bjbirch:
Did you install a custom recovery when you first rooted your phone
[SuperSU] TomSka:
No, I tried to install TWRP via AutoRec after rooting, but when i downloaded it and opened AutoRec it did nothing....
[SuperSU] tonyafc:
Hey used cf auto root, galaxy s7, carrier h3g problem is i tried updating using odin with latest firmware from sammobile, but it failed (dm-verity failure) can someone give me some idea as to how i can update thanks in advance
[SuperSU] ldeveraux:
Can you use flashfire to flash the latest stable zip?
[SuperSU] TomSka:
Nope. As my SuperSu has a Su binary update failure, it does not ask me to grant access to anything that requires root and flashfire app says that my root access could not be acquired or i'm not using any superuser app...
[SuperSU] Wahaj.47:
My mmc got fried so I partitioned my sd card to use as /data and /system. How am I supposed to install the su binaries ???? please help !!!
[SuperSU] Ch3vr0n:
Binaries get installed the same way they always do. Flash the zip file
[SuperSU] Wahaj.47:
Not working. So far i ve tried installing through app and by flashing the zip but its no use.
[SuperSU] andrehsu:
After flashing supersu.zip v2.76, it asks to update binary, then fails. Previously when I flashed supersu v2.65, I didn't have this problem.

Log from TWRP

Device Model: z00ed

Firmware: WW-13.10.7.1

Android version: 6.0.1

Supersu version: 2.76
[SuperSU] karrouma:
Yes bro same problem
[SuperSU] alexsdlc:
Same here
[SuperSU] mnetwork:
Stuck in a bootloop after v2.76

Just did a 'normal' binary update this morning and wound up getting stuck in a boot loop. I've done these in the past and never had issues. Another member just posted the same issue before me also. http://xdaforums.com/showthread.php?t=2760380&page=1270

- Exact device model

US Verizon Note 3

- Exact firmware version

Jasmine ROM 6.1

- Exact Android version

Lollipop 5.0

- Exact SuperSU version

Last version updated to v2.76

- Interfering apps

- Xposed

- BusyBox (symlinked)

- Update methods tried

In-app 'normal'
[SuperSU] Nayibmc:
I have a Z5 (E6603) with Android 6.0.1 (32.2.A.0.224), SuperSU 2.76 and I have Xposed installed. Recently the app updated and my problem is that it doesn't give me the option to choose between normal and TWRP/CWM, as soon as I tap on continue, it starts updating but always fails. Also, my KitKat Galaxy Tab 4 could install the update, it did give me the option to choose between normal and TWRP/CWM
[SuperSU] efan3719:
just did a fresh ROM install on two different devices and after flashing SU 2.76 I did not have root until i manually installed Super SU from the Play Store. After that everything worked as normal.
[SuperSU] egingell:
If you're looking for support, you'll need to be *way* more specific.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Chainfire:
The symptom appears to be clear now, it cannot overwrite the backup su binary. Do you remember if you've used OTA survival mode before, especially no a 4.2 or older firmware?

It's a really strange issue... Must think a bit more on how to find the real issue without having to give you a crash course in debugging mobile apps .... :)

Been using SuperSU on the previews for a while now. And the final 5.0 won't be released for a few more days, so who knows what'll happen then... Probably nothing good :)

Could you possibly have a broken TWRP ? If TWRP can't see system, then the ZIP can't put anything on system either, as it relies on TWRP for seeing system. See the problem ?
[SuperSU] power2top:
Errr....no. My lousy Phone vendor provides no OTA updates for android. No playing with firmwares ever. Considering that 2.01 works like a charm, I wonder what 2.16 is doing differently. Is there some workaround and future prevention strategy you can think off? I have only flashed SuperSU from CWM as you know it by heart by now :)
[SuperSU] RudyH246:
Could be. TWRP seems to be pretty wonky for me lately. The latest version (2.8.1.0) may've been responsible for bricking my last HTC Jewel last week when I tried to flash CM11 M11 Snapshot via TWRP.

Perhaps I should downgrade my TWRP back to 2.5.0.0. That's the last time I remember TWRP having no real significant issues.

Would TWRP 2.5.0.0 be able to flash the latest snapshot of CM? cm-11-20141008-SNAPSHOT-M11-jewel.zip

I'm unsure because I seem to see people talking about F2FS and MTP (things I don't know much about) and saying there are reasons older versions of TWRP won't work to flash newer OSes?

Frankly I don't even want to flash a whole new OS at the moment. I just need to get root access on my stock ROM for the time being.

EDIT: I downgraded to TWRP 2.5.0.0 and flashing SuperSU worked fine.
[SuperSU] rammburst:
how to update binarys?

I have tried all methods throught my samsung galaxy tab 2 7.0 p3113 with cwm recovery installed. I still have root but can't access anything to do with SuperSU and everytime I restart keeps telling me to update Binaries; could someone please direct me to how to manually do this or a work around that doesn't require me trying to figure out how to unroot it and start over.?
[SuperSU] Takamoto:
Hi guys..I have a Y300 with aosp rom by H3ROS and I'd like to upgrade supersu. Actually I have v 2.01..
[SuperSU] fifo209:
I'm using a device I can root, remont and set the system to R/W. I can start the SU demon manually and other apps successful call it, but then SuperSU hangs and the os eventually time it out. I tried it with the latest SU. Is it possible we need a new SU for Android 5.0? Same configuration work fine on 4.4.4

Thanks
[SuperSU] power2top:
[MENTION=631273]Chainfire[/MENTION]: Any updates on this issue? Reverting to 2.01 until I see a working SuperSU :silly:
[SuperSU] mitushorizon:
Can anyone post a link to the most up-to-date SU binary file? Thanks.

EDIT: Never mind that, I already found a suitable one!
[SuperSU] Ken.my:
Cant update binary for SuperSU 2.16

- Exact device model: Samsung Galaxy Note 4; SM-N910L

- Exact firmware version: SphinX V1b (Link: sphinx.vn/post/99645771611/rom-galaxy-note-4-n910l-sphinx-v1b-fix-het-loi-on) - Sorry due to the fact that this is my first post, I wasn't able to make it a link

- Exact Android version: Android 4.4.4.

- Exact SuperSU version: Pro – OTA Survival mode NOT enabled

- Interfering apps: installed BusyBox v1.20 but then removed it already

- Update methods tried: I tried Normal. It failed so I tried TWRP/CWM but the box simply closed. Nothing changed. (I rebooted and tried both, didn't work).

- What kind of root are you left with?

Nothing changed on my device except for the part that everytime I start SuperSU, it asks me to do a binary update

- Logs from TWRP, when updating the binary using the TWRP/CWM button inside the SuperSU app

I cannot pull out the last_log file after running adb pull /cache/recovery/last_log

However, as stated above, when I choose to update using this method, the box simply closes, the phone is not rebooted. Nothing change.

- Logs from SuperSU (very important): attached below

- Various logs (very important): attached below

Please help me update the binary. Thanks in advance!
[SuperSU] Chainfire:
Seems like your /system is actually full... all the relevant root files are 0 bytes big
[SuperSU] Ken.my:
/System

Here it says I still have >1 GB free. Weird. What should I do now? :confused:
[SuperSU] Chainfire:
I don't know - all I know is that the logs say the files are 0 bytes big. That's the reason it doesn't work. That sort of thing is usually caused by running out of free space...

For funsies, removed /system/app/YouTube and /system/app/Maps (you can re-download these from Play anyway), and try rooting again.
[SuperSU] Ryanrioz:
that's weirdo on my Nexus 4 after rooting via TWRP :(.

i think no luck for me :'(
[SuperSU] calvinobel:
Hi, I just updated my Nexus 4 to Android 5.0 Lollipop from 4.4.4 KitKat via ADB.

Now the problem is, I can't get my root access back.

I used Nexus Root Toolkit by WugFresh and install TWRP + SuperSU v2.19 BETA. (I forgot which TWRP version, as I know, it's the newest version)

Then, when I open up SuperSU, there's a Message:

"There is no SU binary installed, and SuperSU cannot install it. This is a problem!

If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!"

Please help :)

Thank you!
[SuperSU] :
You can use the CF-Root method instead.
[SuperSU] calvinobel:
Does CF Root Wipe your data?
[SuperSU] :
It doesn't, unless you use it to unlock the bootloader.
[SuperSU] Khaon:
Hello,

- Exact Android version

Android 5.0

- Exact SuperSU version

SuperSU 2.20

could you include f2fs drivers in the kernel of your next release of CFAR?

That would be awesome!
[SuperSU] calvinobel:
Thanks man! Beer sent!
[SuperSU] Chainfire:
CFARs are stock kernels. If the stock kernel supports F2FS, then CFAR will. However, it doesn't attempt to mount F2FS. Is your /system F2FS, or...?
[SuperSU] panecondoin:
Xperia Z5 Compact with the same specs (Android 6.01, 32.2.A.0.224, Xposed) here. Same scenario here. Although root is still there (tested by uninstalling system app via Titanium Backup). Flashing the latest superSu.zip didn't change the prompt for updated binaries. It also always fails to update via app.

Could SELinuxmode, which is set to "permissive" to enable titanium backup, have to do with this?
[SuperSU] nickaa827:
Galaxy Note 3 stuck in bootloop

Hello, what I think is because of a recent SuperSU update, my phone is stuck in a bootloop. I dont know what to do.

Model: Verizon Note 3 N900V

Firmware: Jasmine ROM 6.1

Android version: Lollipop 5.0

SuperSU: latest version

Possibly interfering apps: Xposed

Update method used: In-app 'normal'

---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------

I'm having the EXACT same problem as you, I have the exact phone model and Jasmine ROM installed...did you find a way to fix it? what did you do to fix it, if you did???
[SuperSU] Ikarisan:
I am having the same problem with my Xperia Z5 E6653 on 32.2.A.0.224 and XPosed v85. :(
[SuperSU] mnetwork:
There was nothing I could do. I had to do a factor reset from stock recovery which brought me back into the device. I had to accept some data loss for data on internal storage. The only good thing now is that you can do the bootloader unlock and flash TWRP to recovery and have that in your back pocket in the future. There is literally nothing we can do because we don't have a custom recovery available. You are the 2nd person I've heard of now (not including myself) with this exact issue. After I did a reset and unlocked the bootloader I did an SU update again and it went fine.
[SuperSU] ldeveraux:
factory reset is literally the last thing you should ever do to fix boot problems, apart from using odin. The first thing you should have tried was to reflash your rom...
[SuperSU] mnetwork:
Oh? And how was I supposed to reflash a CUSTOM ROM with FACTORY recovery? :rolleyes:
[SuperSU] ldeveraux:
flashfire? Didn't realize you didn't have custom recovery...
[SuperSU] mnetwork:
Safestrap was removed when moving to JasminROM 6.1 while on the stock ROM slot and Flashfire wasn't available. If I had custom recovery I could have at the very least backed everything up.
[SuperSU] ipdev:
Quick question. (More curiosity than anything.)

I only have one device that uses safestrap. After I flashed a rom, SuperSU and rebooted. I did not have safestrap so I just reinstalled it. I take it this is not an option for other devices?
[SuperSU] YasuHamed:
Rooted Z5p E6633

the APK of 2.76 from google play never update binaries

the flashzip version found here https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip

shows 2.74 as version after installation and google play keep notifying me to update...

can figure out why? reinstalled many times

flashed UPDATE-SuperSU-v2.76-20160630161323.zip via recovery many times :(
[SuperSU] Ikarisan:
Hmmmm... that's strange. After investigating my Xperia Z5 I have found an installations of SuperSU, located directly under /.

It contains a "SuperSU.apk" and the two directories "lib" and "bin".

SuperSU.apk is dated to 2008-02-29 and the directories are dated to 2016-06-16.

And from /xbin/su this folder is linked. Is this correct?!
[SuperSU] YasuHamed:
yes exactly the same!

super su is stuck on 2.74 and not updating, but it was updated from 2.65 to 2.74 last time via flashable zip

also therei s one more thing on google PLAY the 2.76 is updated on 7july2016

where on the chainfire.eu the file name has 7 days older date with version 2.76

UPDATE-SuperSU-v2.76-20160630161323

i think there is no flashable zip available even on the chainfire.eu and the one given is typo in the file name , its actually 2.74
[SuperSU] egingell:
No, it's definitely 2.76 and it's definitely on Chainfire's website. See the OP of the stable thread and that is the correct file name. They have different dates because the Play Store and the flashable zip are not the same in that one is by Chainfire and one is by CCMT (or whatever it's called), but they are built from the same source.

But it's definitely not 2.74 with 2.76 in the name.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] YasuHamed:
in that case only they can tell why this time its not updating ....
[SuperSU] mikuru396:
Xperia Z3TC Android 4.4 user here:

Updated SuperSU to 2.76, binary update request happens each time when I turn on superuser access, and sure it failed ...

Rollback to 2.74 BETA, problem still exist.

Now go back to 2.65 seems solve the problem ...

--------

In case someone need it I also include the link to 2.65 below

apk (extracted from below flashable zip): https://goo.gl/exeK1a

flashable zip: https://goo.gl/3XsMdW
[SuperSU] irfanjunaid:
[MENTION=631273]Chainfire[/MENTION]

Have deep sleep issues and lag when answering call on Samsung J2. Everything was working good until 2.71. With 2.74 deep sleep issue was observed and with 2.76 there is a 2-3 second delay when answering call.

Device: Samsung J2 2015(j2lte)

Firmware: J200GDDU1APB1(India)

Android version: 5.1.1

SuperSU: 2.76
[SuperSU] mrgbuzz:
I too have binary needs to be updated. I have a Jaiyu S3 with TWRP. Where can I find the binary zip file that I can update my root access?
[SuperSU] Ch3vr0n:
There is no 'binary zip' file. Only the standard su zip which also updates the binaries in the process.
[SuperSU] mrgbuzz:
Oh right. And this is available from chain fire? I reinstalled the su apk but still getting the same result. :confused:

Edit: Found it. Thanks
[SuperSU] mikuru396:
Finally get some for testing various version of SuperSU apk, and come out with some interesting finding ...

Starting from 2.67, SuperSU apk will try to update the binary at first launch and fail to do so (even install via flashable zip)

The latest version that have no such problem is 2.66

Further investigation on 2.76, I've managed to have a way to "have the binary updated" as follow:

1. Update SuperSU via flashable zip, make sure all dependencies is updated

2. On first launch, it will ask for binary update, go on and fail :( on the popup dialog select reboot

3. After reboot, SuperSU will inform you about binary update, please do so

4. This time, after it fail to update binary and the popup appear, DO NOT select "How to Root" or "Reboot". Instead touch outside the popup to dismiss it.

5. Go to setting, untick Enable superuser. Wait for a few seconds, and tick it again.

6. When ask for update binary, please go ahead. I finally get the binary updated at this stage, and after reboot the update binary notification has gone :)

Some more interesting thing behind: If it is disabled for games and enable it again for system r/w, it will fail and rebooting cause another update binary notification.

I am not sure what is happening, but it seems that twice update without leaving SuperSU do the trick. Anyone can confirm?

P.S> SuperSU 2.66 flashable zip: https://download.chainfire.eu/896/SuperSU/

P.S.2> I have my SuperSU installed as normal app ...
[SuperSU] r25txe:
Hi [MENTION=631273]Chainfire[/MENTION]

Are you getting many/any reports of the latest 2.76 version not installing on CM13 based ROMs. I'm quoting the post above as my issue is the same, except I am installing Resurrection Remix 5.7.1 (CM13 based) on a Samsung Galaxy SIII (GT-i9300).

I tried installing both by the flashable zip and via Play Store. I have always used the flashable zip before without issue.

The ROM developer is aware of issues (see post), he is telling users of the ROM to NOT install SuperSU and use built in superuser. I don't understand the issues he refers to. The same as the user quoted, the built-in superuser is not as reliable as SuperSU. The main issue I have found so far is restoring Android_ID with Titanium fails.

Is this a CM13/ROM issue or should I provide logs to help you fix an issue with SuperSU?
[SuperSU] Rootcarrot:
Thanks for the help, i my managed to reflash the rom myself and everything is kow working :)
[SuperSU] r25txe:
@Chainfre

A followup ...

A user in that ROM thread pointed out that 2.63-2 BETA worked for him, so I flashed that. I noticed that this version installed systemless.

I booted successfully into my ROM and the binary asked to be updated and I did that and also rebooted from there successfully. It would seem that systemless is required.

Titanium was able to restore my Android ID using SuperSU after the binary update, too.

If gthere is anything you want me to provide to see the issue, let me know. My USB port is busted, but I can probably get you logs from a terminal on the phone itself.
[SuperSU] ldeveraux:
Systemless isn't required on cm13, it's just a checkdown. If your system can properly run systemless, it installs that first. If not, it installs to the system.
[SuperSU] r25txe:
Fair enough, but if system-mode is compatible with CM13 it did not work on my CM13 based ROM so I am unsure where the issue lies.

If systemless-mode is needed for my ROM, then v2.76 zip did not recognise that. Xposed and Titanium installed to my /system partition fine, and I disabled the /system write protection in TWRP (swipe to allow modifications) before flashing the ROM.
[SuperSU] juniecho:
not exactly an update failure, but install failure when re-enabling superuser

issue: Can't "enable" superuser in one shot, when no app has asked for superuser privilege yet since device is powered on.

how to reproduce:

- stock rom, with no root-related apps installed (that is, no app to ask for root privilege)

- install supersu 2.76 and run it (system install. not sure with systemless)

- go to settings tab, and uncheck 'Enable superuser'

- re-check the same thing

- NOW, install will fail.

- if you look at /system/xbin at this point everything EXCEPT 'su' is there. in other words SuperSU cannot restore /system/xbin/su.

- running SuperSU again and updating binary will succeed, but same thing will happen if you uncheck 'enable superuser' option again. (unless you made another app, e.g. titanium backup, ask for root during the process)

how to avoid:

- if you (by adb or shell, etc.) or at least one app has asked for root (=accessed su command) after powerup, install will not fail.

device model : LG G2 (Korea, LG U+) LG-F320L

f/w version : 22h

android version : 4.4.2 KOT49I

supersu version : 2.76 stable

interfering apps : none, pure stock and no apps except supersu

logcat:

1. disabling superuser first : http://pastebin.com/AeSf1TCS

2. enabling superuser again: http://pastebin.com/Xx4XHKqz

3. re-running and updating su binary: http://pastebin.com/paR27u4j
[SuperSU] 0on:
Device: LeTV/LeEco Le1 (X600)

Firmware: stock ABXCNOP5801507012S-5.8.015S

Android version: 6.0

SuperSU: 2.65

TWRP: 3.0.2.0

(Xposed: v86-sdk23-arm64)

---

Keep losing (systemless) root after each reboot. Reboot into TWRP, flashing SuperSU 2.65, wiping dalvik/cache, works again, reboot: root gone. Same problem here.

-edit- fix: flashed 2.76. Works fine :D
[SuperSU] Lagcams:
-Device model

HTC Desire 626s Cricket USA

-Android version

5.1 lollipop 1.23.506.6

-SuperSu version

2.76-2

- Interfering apps

Previously had Xposed installed, and I think I still have BusyBox installed.

- Update methods tried

I've tried both in app and via recovery.

- What kind of root are you left with?

No root at all.

Previously flashing the zip would install the app and it would want to update binaries, however now the phone reboots before the flash is completed.

Still asking to update binaries.
[SuperSU] Johnathan0:
Installation failed ! Please reboot and try again.

- Device model

Sony Xperia E3 D2203

- Firmware version

18.4.C.2.14

- Android version

4.4.2

- SuperSu version

v2.76 . Just got it from the Play Store and it is asking me to update the binary.

- Interfering apps

Possibly Kingroot.

- Update methods tried

Normal.

- What kind of root are you left with?

Kingroot still has full root access, even after SuperSU tries and fails to remove Kingroot.

Is there any reliable solution to this problem that I am missing, or will I have to learn all kinds of cryptic magic to have a chance of finding a solution? I did a simple root with Kingroot so didn't have to bother with TWRP or CWM, but Kingroot is kind of intrusive and bloated with other junk so I want to remove it.