yashsingh1/xdaforums huggingface dataset:
[SuperSU] Valuta:
- Exact device model

MHA-L29C432

Huawei Mate 9 (EUROPE)

- Exact firmware version

MHA-L29C432 b197/b198

- Exact Android version

Android 7.0

- Exact SuperSU version

su -v reports 2.79:SUPERSU

2.82 (Currently displayed)

- Interfering apps

None

- Update methods tried

Normal in-app.

version from: https://xdaforums.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986

(i.e. https://www.dropbox.com/s/si0ictoj4rls6lb/SuperSU-v2.79-MATE9-init.d_support.zip?dl=0)

- What kind of root are you left with?

- Nothing seems to have changed at all, even the GUI still shows the old version number

su -v reports 2.79:SUPERSU

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

I do not see a TWRP button

- Logs from TWRP, when updating SuperSU completely via ZIP

Have not tried, not sure if this is safe.

- Logs from SuperSU (very important)

ADB not working. (It was before rooting)

- Various logs (very important)

No adb.
[SuperSU] Khaon:
The file system of my system partition is ext4. Thus CFAR is working great. However it fails for example to mount /cache partition.

I think there is no advantage to run f2fs on system partition since its r/o. However, I am using it on /cache & /data partitions like most of the people running my kernel. However, I understand you want to stick with stock kernels with the sh*tload of devices you are supporting.

In case, you got interested in the future to add f2fs support, I am using this patch to all stock kernels I use to build recoveries when I need a f2fs support.
[SuperSU] Chainfire:
CFAR will never be custom built kernels, so I will never apply any patch, as I don't compile from source *at*all*.

I can understand using F2FS on /data, but doing so on /cache is pretty much completely useless. It's not actually used for traditional cache purposes, but only for system maintenance. So you're trading 0 benefits for lots of incompatibility.
[SuperSU] Khaon:
Hm, that's why there is no binaries in the meta-inf but sh scripts (aming others) :p.

Indeed you are right, thank for your comment, I guess that's why Google use only data partition with f2fs on their devices supporting f2fs.

Any chance you can answer this question, with ART is there less writes than with dalvik? If yes the purpose of f2fs is less attractive.
[SuperSU] SSyar:
Fresh installed Android Lollipop,, unable to execute SuperSU, it popup the message,,

There is no SU binary installed..,, .,,

Nexus 7 2012 wifi

Android 5.0 LRX21P

CWM Touch 6.0.4.3

SuperSU-v2.16.zip
[SuperSU] SSyar:
CF Auto Root works for in this.,.,.

http://download.chainfire.eu/295/CF-Root/CF-Auto-Root/CF-Auto-Root-grouper-nakasi-nexus7.zip
[SuperSU] stickt73:
HTC One X+ International enrc2b UK-O2

Pure AOSP 4.4.4 by Lloir, http://xdaforums.com/htc-one-x2/orig-development/pure-aosp-4-4-4-international-rom-t2924122

Download link: http://www.plsdontpwn.me/?dir=enrc2b/pure-aosp/4.4

Elite Kernel OXP http://xdaforums.com/showthread.php?t=2012320

Download link: http://elite-force.eu/emoxp/oxp_elitekernel_kk_141026.zip

SuperSU v2.16 zip recovery install

Busybox v1.22.1 zip recovery install

Trying to install SuperSU via CWM 6.0.4.8, upon boot get error "There is no binary installed, and SuperSU cannot install it. This is a problem!". SU binary is in /system/xbin folder with the following properties: rwxr-xr-x, UID: 0, GID: 0. No binary updates have been performed since I am doing initial install for this ROM. SuperSU v2.16 works perfectly fine on OMNI ROM 4.4.4. Attached logs are only logs that could be compiled. Others were not found. Please help thank you.

Tim
[SuperSU] cynepmeh:
deleted
[SuperSU] Chainfire:
- Currently you need to use CFAR for Nexus 7 202 on Android 5.0

- CWM is out-dated and doesn't support all SELinux stuff, use a recent TWRP if you want support

- 2.16 is not the latest version, next time try the latest before reporting

- CWM is out-dated and doesn't support all SELinux stuff, use a recent TWRP if you want support

- 2.16 is not the latest version, next time try the latest before reporting

- It appears the su daemon is not started at boot time. Perhaps this ROM does not support starting install-recovery.sh at boot time? You can ask the (kernel) dev, but first you should update to the latest TWRP and the latest SuperSU and check again if it works.
[SuperSU] SSyar:
[MENTION=631273]Chainfire[/MENTION] its already done :)
[SuperSU] stickt73:
Thank you. I will try the latest version, switch to the latest TWRP for the HOX+ and get back to you. Will also speak with the dev as well. Thank you.
[SuperSU] Ch3vr0n:
Just updated to my nexus 7 2013 to lollipop then rooted using CFAR. Su asked to update binary which i told it to do the normal way, 5 min later. Still nothing. Rebooted, normal way again 10 min later. Still nothing. Running lastest play store superSU

the only thing that happens is continuous popups for "... has been granted superuser permissions..."

other than that i'm now at 10 min and counting on the spinning circle and i'd rather not flash a custom recovery

** edit ** flashed TWRP 2810, SuperSU failed to reboot into recovery. Manually booting into recovery works but then i've got NO clue what to do next. as i don't see any file to flash

** edit ** wiped/reflashed stock lollipop system & recovery. Re-ran lollipop CFAR, installed 2.23 test apk. Still stuck on "busy installing ..." using the normal method. I'm completely at a loss here

so currently i've got "root" but no root. The only thing that works is aps REQUESTING root, but that's where it all ends

CF lumen, stuck on loading, cyanogenmod, can't toggle root mode, busybox stuck on "installing", Titanium Backup stuck on "Requesting root access" when opening, etc ...

So far no root tool works and binary update doesn't either

only option i see is factory reset and i'd rather not do that

Current status:

"rooted" using CF autoroot

SU Pro 2.23 installed

"stuck" on "updating binary"

TWRP 2.8.1.0 installed

NO actuall root access

flashing beta zipfile results in "no su binary can be found"

** last edit ** download CFAR a 5th time. This time it seems to have worked. During rooting i saw a line "patching kernel" which didn't appear on previous versions. SuperSU changed to 2.20, and i'll stick with that till it gets updated through play store. I got my root back so i'm happy :)
[SuperSU] thworpitt:
2.16 update not working on Nexus 5

Hi there,

I have a Nexus 5, just updated to 5.0 using an OTA + adb sideload. I have reinstalled TWRP and am trying to get SuperSU working again. I've flashed the update for 2.16 in recovery but every time I try and open the SuperSU app it says that the SuperSU data is missing and can't be installed. A root checker shows no root.

What should I do?

Edit: Nevermind, I found out that rooting now has to be done with CF-Autoroot, and have done that.
[SuperSU] jayarremoroza:
SU Binary installing problem

Hi good day, I'm Jay ar Remoroza, I am using a free version of Super SU. Its a great application and I really enjoy the feature of the App. But when I change the setting of the Apps, I clicked the "use a SU to another SU Apps" it was automatically reboot my phone and when its backed it requires me to install SU Binary and when i choose normal its fails and when i choose the other nothings happen. Now when i want to back to default setting, it cannot back, so what should I do? I hope you will help me. Thank you in advance.
[SuperSU] aaron74:
i just rooted HTC Desire 510from thread xdaforums.com/desire-510/general/how-to-root-htc-desire-510-t2951744 with twrp and supersu2.16update. everything went fine. but just wanted to let you know when i activate pin code security. it doesnt take and reboots device with a "send debug to HTC"
[SuperSU] LastResort3:
keine SU-Datei

I have a GT-I9300 with Android 4.3 and rooted my device. I am a noob here. When I open Super-SU the program says that I don't have any SU-file installed and the program itself can't install it too. I have already updatet Super-SU with the Google Play Store.

Pls help me installing the latest SU-file to use SuperSU.

Tank you for your help
[SuperSU] Srandista:
Did you run CF-Auto-Root for your phone before installing SuperSU from Play Store?
[SuperSU] shawnbrennan55:
You need the su binary file installed in the system partition and the SuperSU app to have root access. Here's a good app to let you know if you have root access.

https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator
[SuperSU] LastResort3:
It says I have been denied root access, but it may be possible. "I should check for updates for my SuperUser application"

superuser were both possitive and busybox negative because i haven't it installed.

---------- Post added at 08:32 PM ---------- Previous post was at 08:20 PM ----------

Run it? What do you mean excatly with run, sorry but i am a real noob :)
[SuperSU] Srandista:
You can't just install SuperSU from store, and be rooted. You have to first have su binary in system. That can be inserted to the system with CF-Auto-Root.

You can find it here: http://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip

Run it with USB cable connected to your mobile, and after successful installation you should have rooted device.
[SuperSU] LastResort3:
yeah i did this, ofc

and afterwards SU was installed and i updated it on store.
[SuperSU] xodeus:
OnePlus One - Not working SU binary

- Exact device model

OnePlus One (bacon)

- Exact firmware version

CM12 by K900 - http://www.reddit.com/r/oneplus/comments/2moqig/cm12_nonscheduled_builds_discussionupdate_thread/

- Exact Android version

Android 5.0.0_r7

- Exact SuperSU version

2.30

- Interfering apps

None

- Update methods tried

TWRP zip

- What kind of root are you left with?

After a failed binary update, multiple outcomes are possible:

- Root is lost. Apps cannot get root anymore, you cannot get root using "su" from an adb shell, etc

- Various logs (very important)

Attatched ZIP
[SuperSU] LightningKitsune:
- Exact device model

AT&T HTC One M8

- Exact firmware version

1.58.502.1??

- Exact Android version

4.4.2

- Exact SuperSU version

2.35

- Interfering apps

- Xposed

- BusyBox (symlinked or non-symlinked)

- Update methods tried

In-app via twrp recovery.

Note that if you let TWRP or CWM "fix" root for you, or let them disable the firmware from flashing a new recovery (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.

Didnt do that.

- What kind of root are you left with?

After a failed binary update, multiple outcomes are possible:

- Nothing seems to have changed at all, even the GUI still shows the old version number

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

C:\fastboot>adb pull /cache/recovery/last_log

error: more than one device and emulator

???

- Logs from TWRP, when updating SuperSU completely via ZIP

Same error as above

- Logs from SuperSU (very important)

Same as above.

- Various logs (very important)

Same as above.
[SuperSU] revmra:
- Exact device model

2012 Nexus 7

- Exact firmware version

Stock Google build number LRZ21P

- Exact Android version

Android 5.0

- Exact SuperSU version

2.35

- Interfering apps

None installed

- Update methods tried

In-app 'normal'

I had used CF-Autoroot to get root after I updated to Lollipop. After upgrading to 2.35, SuperSU fails to update the su binary.

- What kind of root are you left with?

Root is still there, just using the old 2.20 su binary

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

N/A

- Logs from TWRP, when updating SuperSU completely via ZIP

N/A

- Logs from SuperSU (very important)

See attached

- Various logs (very important)

See attached

Please note that I got the su -V one out of order, but you should be able to figure that out.
[SuperSU] blocka:
SU Needs to be updated loop

Hi

Updated SuperSU to latest version today via Play Updates. (2.35)

Now I get the message "The SU Binary needs to be updated."

Went through the process via CWM Recovery. Rebooted and again the message, "The SU Binary needs to be updated."

Downloaded the zip and installed directly via recovery, rebooted and again "The SU Binary needs to be updated.".

I'm out of ideas!

HTC One X

4.2.2

CWM Recoevery. 6.0.4.8
[SuperSU] LightningKitsune:
I said F it and restored from rom stock, updated supersu, fixed. Only do this if you don't mind starting fresh again though.
[SuperSU] kren22:
Cant update binary for SuperSU 2.16 ie after each reebot SuperSU keeps asking for update binary, tryed normal /cwm way, no success.

Tryed update via cwm UPDATE-SuperSU-v2.16.zip as well .

- Exact device model: Coolpad F1 8297W

- Exact firmware version: CoolPad F1 8297W PURE-AOSP h t t p :/ / w w w. needrom. com/download/coolpad-f1-8297w-pure-aosp/

- Exact Android version: Android 4.2.2

- Exact SuperSU version: 0.99

- Update methods tried: I tried Normal. It failed so I tried CWM Recovery 6.0.5.0 h t t p :// w w w .needrom.com/download/cwm-recovery-6-0-5-0/ but nothing changed after update. 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 SuperSU (very important): attached below

- Various logs (very important): attached below

I ran adb commands separetaly, as after 1st didnt won't to execute 2nd and so on and packed them within "adb-logs.zip"

this way

edit: looks like cwm update with "UPDATE-SuperSU-v2.35.zip" did the job done.
[SuperSU] Chainfire:
You're running SELinux in permissive mode, which may be part of the issue.

You did not include the requested logcat, without which I'm just left guessing.

Adb sees multiple connected devices, and thus it cannot produce any logs. I can't do anything without these.
[SuperSU] feriber:
Galaxy SII - GT I9100. Binaries not updating

- Exact device model

Samsung GT-I9100 (Galaxy SII)

- Exact firmware version

ROM: standard

PDA: I9100BULSD

CSC: I9100ATLLSC

Radio PHONE: I9100BULS1

Kernel: 3.0.31-889555 dpi@DELL228 #3

SMP PREEMPT Thu Jan 31 14:48:54

KST 2013

Compilación: JZO54K.I9100XWLSD

- Exact Android version

4.1.2

- Exact SuperSU version

2.35

- Interfering apps

- Xposed 2.6.1

Intelli3G 2.16

Xposed Torch 1.8.0

- BusyBox (symlinked or non-symlinked)

BusyBox v1.20-2linusyang

Include in your report if you have one or more of these installed.

- Update methods tried

normal

- What kind of root are you left with?

$su -v

2.00:SUPERSU
[SuperSU] revmra:
I ended up doing something similar, but less destructive. I unzipped the boot.img out of the 5.0 rom, flashed that, and then ran the new CF-Autoroot. Now I have root working with SuperSU 2.35. Maybe my old logs can help Chainfire figure out why I couldn't upgrade initially.
[SuperSU] Pig Vomit:
I currently have:

Nexus 5

Running LRX21O

SuperSU 2.20 installed using CFAR

No custom recovery

****Bootloader Re-locked after root with 2.20****

Encryption On (locked bootloader and encryption crucial as my phone typically carries A LOT of very sensitive information to include numerous social security numbers (legal for me))

SELinux Mode Changer set to Permissive (required for ARUnchained, which is my whole reason for root also)

Play Store is advising me of the 2.35 update. I've read of problems people are having when they try to update via Play Store. Really don't want to wipe everything until 5.1 is released.

If I can just update SuperSU through the Play Store with no problem, I'm happy to take the plunge. But it sounds like maybe I should wait for 5.1, do a fresh & clean install (not a fan of OTAs ever, but a big fan of latest Android OS), and update then.

Can someone advise whether given my current set up I'd be able to successfully update to 2.35 via the Play Store with no problem and without having to re-unlock my bootloader (thus wiping the device)?

Thanks in advance.
[SuperSU] LightningKitsune:
Now it works, I got the logs now, not sure how useful they will be, but hopefully they will be.

*Edit* XDA is refusing me to post the logs, saying they failed?

I posted them on pastebin

Logcat: http://pastebin.com/gbT5gtiZ

Last_log: http://pastebin.com/P81DwpMc
[SuperSU] Frank Westlake:
Zip them, it won't accept text files.

Frank
[SuperSU] TheDarknessEffect:
Device Name: Fly IQ445
[SuperSU] yakudza_m:
- Exact device model

Thl W200

- Exact firmware version

N/A

- Exact Android version

4.2.1

- Exact SuperSU version

2.35

- Interfering apps

None

- Update methods tried

In-app via CWM recovery.

I also got this error about missed binary file after update. Please fix it ASAP. Thanks :)
[SuperSU] swazi1:
Device will not reboot at all, locked at brownish screen

Hi,

My Samsung Galaxy S4 mini updated SuperSU today and asked for the binary update. I tried the normal option first and as it failed several times I chose the CWM / TWRP option.

Now the device won't start:

I get the "recovery booting" blue message on top left followed by "set warranty bit :recovery" in yellow. (and my Samsung I9190 logo)

Then a WMshua recovery and logo

some lines that go to fast for me to read..

at the bottom I can read "unable to get recovery fstab".. (3 or 4 lines like that)

bottom line says completed outputting fstab

some more few lines that go way too fast :silly:

and then a brownish screen.

Tried hard reset... battery out.. I can't use the device at all, and can't really post its detail right here because I can't access it!

Any suggestion anyone?
[SuperSU] Frank Westlake:
Reinstall (Odin) the Recovery partition.

Frank
[SuperSU] Tommy RB:
Battery drain issue after updating binaries

Exact device model

Motorola Moto G (XT1032)

Firmare version

173.44.9.falcon_umts.AmericaMovil.en.CL

Android version

4.4.2 KitKat

SuperSU version

2.36

Interfering apps

None

Update methods tried

Normal and Via TWRP

What kind of root are you left with?

Nothing seems to have changed at all, even the GUI still shows the old version number

SuperSu 2.02

Extra Information

I have deleted (with the unroot button) SuperSU 2.36 and flashed an old 2.02 zip. The problem I had was that after updated the binaries on version 2.36, my battery drained almost instantly (from 33% to 20% in 15 minutes). I now have SuperSU 2.02 installed and it looks that my battery problem is still there, but I won't flash the newest version until the bug is fixed. (I'm sorry about the logs, but somehow they don't exist anymore. I might have deleted them by accident when trying to fix the issue)
[SuperSU] grumpyy:
Hi;

Help pls.

SuperSu v 2.35 updated failed.

Android 4.2.2 JB

THL W816GB
[SuperSU] moeaeon:
su binary update failed

Hi, i have:

Prestigio PAP3350DUO

1.0.11 firmware version

android 4.2.2

i'm using SuperSU v.2.26, trying to update to 2.35. i tried all versions, the last one, that updates binary is 2.26. all versions higher fails.

i have Xposed installed, but i've tried with uninstalled xposed.

i have no custom recovery, so only "normal" method of updating is for me.

after update failed root still work, su version is 2.26.
[SuperSU] evil.moron:
LG G2/SU Binaries issue/This is a problem!

LG G2/4.2.2 Stock (formerly rooted)/TWRP/ updated binaries using TWRP/ subsequently broken root access.

Flashed SuperSU 2.35 from TWRP. Now, everything seems back to normal.

Entered TWRP by following instructions here: http://xdaforums.com/showthread.php?t=2534981 (don't worry, pressing the power button on the "Factory Reset" screen takes you into TWRP, does not factory reset your LG G2 handset)

Thanks Chainfire for this very vital work.
[SuperSU] Chainfire:
I am reviewing all of those, but I have to stress again, no logs, no help. All you can do is hope that somebody else's logs lead to a discovery that also fixes your problem.
[SuperSU] swazi1:
Hi Franck,

Not sure if the reply was addressed to me...

My problem is that my phone doesn't boot AT ALL.

Brown screen and that's it, nothing else I can do.

To reinstall the recovery partition, could you direct me with a link of how to do?

I can't post any log file as I said, I can't do anything!

Thanks again for the help

---------- Post added at 04:46 PM ---------- Previous post was at 04:18 PM ----------

Ok.. An update. Very weird.

I plugged my phone to the computer.. It would vibrate every 4 seconds or so.

While doing that I used the hard reset combination and I managed to boot.

Scared of SuperSu now!
[SuperSU] feriber:
Update to 2.36 with no success

I've updated superSU to 2.36 version, but binaries still do not update.
[SuperSU] gr8dawgs:
Failure updating 2.35 --> 2.36 on both N10 and GN2

First, I am a happy (and thankful!) long-time user of SuperSu Pro, and until this week, I have never had any issues with any previous version; however, I have attempted to update both of my current devices this week from version 2.35 to 2.36 and encountered problems on both. About the only thing they two have in common is that they are Samsung devices:

Device 1: Samsung Galaxy Note 2 (SCH-I605)

Android version: 4.1.2

Build: JZ054K.I605VRAMC3

Device 2: Samsung Nexus 10

Android version: 4.4.4

Build: KTU84P

The update for both devices was attempted via the usual Play Store route. In the case of the GN2, I was not even prompted to update the binary, so the UI shows version 2.36 while the binary reports 2.35. For the N10, I was prompted as expected, and the first attempt via the "normal method" failed, so I allowed it to reboot and I tried again. The second time, however, I attempted to allow it to use recovery (TWRP 2.8.2.0, which I had installed since the last SuperSu update with the intention of updating the N10 to Lollipop soon). However, instead of rebooting into recovery, it rebooted to the system, and since that time it hasn't prompted me again either! However, like the GN2, the UI shows 2.36 while the binary reports 2.35. (BTW, this may or may not have any relevance, but I don't have any problem booting manually into recovery, and the QuickBoot utility program I have installed can also do that from a running system.)

The only apps which may be candidates for interference are Xposed, with the XPrivacy and BootManager modules. And while those have been installed "for quite a while", I have recently updated those to the most recent versions and my most recent XPrivacy update (to V3.4) was after the last previous SU update to 2.35. (I have added no restrictions on SU!!)

On both devices, root appears to be working as expected - it just via the previous version.

I am attaching the logs from the N10 (which I use a slightly annotated script to produce):

So, as far as I can tell, I [still] have a working version of V2.35, but given that you have great product for which I have been a grateful user since my Nexus One days, I thought I'd pass this information on in the hope it helps you identify an issue with the latest version, interference from another app, or some other weirdness. I did find the way the issue manifests itself on both my devices a bit interesting.
[SuperSU] Supereloaded:
reboot of my galaxy S4

Hello

since I updated to new version supersu v2.36 , it asked me to desactivate knox , so did I but since my device reboots unexpectedly a lot !!!

Is there any way to reactivate knox or to solve the pb ?

Thanks in advance ...
[SuperSU] Chainfire:
There is no binary update 2.35 --> 2.36

There is no binary update 2.35 --> 2.36

adb shell su -c pm enable com.sec.knox.seandroid