yashsingh1/xdaforums huggingface dataset:
[SuperSU] Skretax:
SuperSU Problem!

I've rooted my device (GT-1335 - Android 4.4) with Windershare Rooting Toolkit, After rooting I've installed Root checker basic from the market and run it. It says your device is rooted. But when i wanted to go to root using FX explorer, it says you need permission from Advance user. When i click SuperSU after that it says that "There is no Su binary installed, and SuperSu cannot install it. This is a problem!", After that i checked whether my device is rooted or not with Root checker basic, but now its says that my device isn't rooted!

Please Help, and replay soon!

Note: My device isn't original samsung model!
[SuperSU] gokunjp:
super su still loading

After update super su in playstore my s4 octacore in app tab on supersu still loading but nothing happened...
[SuperSU] ycon:
I had problems with using Stock 4.4.4 on my i9305.

Was freezing/not opening, then when it did it wouldn't update.

So I went to the SuperSu site and downloaded the latest to instal via CWM.

Now working fine. Hope this helps someone.
[SuperSU] p220fhf:
I tried to reroot on my s4, but nothing changes, when updating the SU to 2.14.

So, I think, maybe, the main problem is SU 2.14 on 4.4.2 and 4.3.

My s4 was 4.3 rooted, before the SU update, everything was fine. But after updating, the SU app said I didn't root. Then I updated my FW to 4.4.2(I9505ZHUFNB3), and used CF-root to root. Still ok, but when the SU updated to 2.14, thing happened again. (Now my s4 is temp unroot for playing game :p, but can't root again as it says "You didn't root")

Sorry for my bad English.
[SuperSU] BIG-MOEP:
SuperSU 2.14 not working on s4 4.3

same problem here on my S4-quad-16G with samsung 4.3-stock, which was rooted mothns ago via AutoROOT+twrp2.7.01

same here update 2.14 from PlayStore f.cked-up the SuperSU app (i have waiting-donut on APPS and LOGS-tabs...)

Device stays rooted, and root-requests from other apps seems to work too, because there is a typical SuperSU-reuqest popup there....

So please fix the APP for Samsung 4.3 4.4 firmwares...

Versions 2.01+2.06 worked flawlessly.

what i have already tryed:

1) On the [Settings]-TAB: => UNINSTALL APP: Effect 'uninstalling...'-popup stays 4ever w/o effect

2) On the [Settings]-TAB: => UNINSTALL APP for a NEW SuperUserApp: Effect 'uninstalling...'-popup stays 4ever w/o effect

3) Booted into TWRP => INSTALL the SuperSU-2.14.ZIP, rebooting phone -> in SuperSU (the same waiting donuts on APPS/LOGS...) :(

Phone: i9505-OpenEUROPE quad-core/16G Samsung-stock-FW 4.3
[SuperSU] SirVss:
Device I9505

Android Version: Stock 4.3 MKF

BusyBox v1.22.1

Wanam Xposed installed

Stock Recovery

Kingo Root

Google Play Update

Issue: After update from 2.13 to the latest 2.14 when supersu try to reinstall it stuck more than 5 minutes, I reboot my phone, reopen supersu but now in my "APPS" and "LOGS" I have some kind of neverending loop load, I can't manage to see my rooted apps there, and in my SETTINGS if I try to make some changes it stuck and need phone reboot, otherwise all my rooted apps work fine!
[SuperSU] p220fhf:
I think i figure out the problem, is the SU bin update. My note 2 is rooted and is using SU 2.14 pro, but i don't update the bin. It works fine, but when opening the su app, it asks you to update the bin.
[SuperSU] mrdreamers:
my brand new Zeki Quad Core 4.4.2 TBQG855 Android Tablet gets update binary fails everytime in supersu 2.40, i successfully rooted it with kingo and it works great but just the update binary fail what can i do? :confused:

i still have stock recovery but do have flash gordan installed.

i do have busybox pro but this happened before i installed it.

is there a way to see if i have more than one superuser? :confused: far as i know i only have one.
[SuperSU] Megadave123:
Unable to update SU binary

Device is Kyocera Rise C5155

Stock factory-installed Android 4.0.4 "Software Version 1.004VM"

SuperSU Free 2.37

I have the Busybox installer installed, but it is not able to get root therefore not able to "install" busybox.

Tried using "Normal" update method. I have neither TWRP nor CWM installed, neither of these apply.

I *am* able to attain root from adb shell.

I am attaching logcat and various info from the shell as requested.

Any advice would be appreciated.

If you need me to test something just let me know.
[SuperSU] e.m.i.n.e.m:
i root my device (galaxy s dous 2 ) with kinguser>?????

then i download subersu >>>>>ok

suberus need update

but the update fald :confused:

i use normal way for update coz i dont have CWM of TRW

TANX
[SuperSU] d00lar:
yep i have same problem as above

i rooted using kingroot

now have kinguser and would like to replace it with suerSU!

my deice is psp5508 duo android 4.4.2 - i had no other way to root ;/

now after install (from market and from twrp also) i have message about binary update that fails always

does the logs will help you guys ?

or it is some common problem after kingroot?

thanks and regards!

edit

ok nevermind :D that was on version 2.04

on 2.40 everything is fine ;)

regards!
[SuperSU] Atikun:
Hi everyone. I bought a new phone. It's a local brand called General Mobile Discovery. I updated to Android 4.4.2 from developer website. 2 days ago i tried to root the device using framaroot 1.9.3 but it failed. I installed Kingo Root on my pc and root the decive in 2-3 minutes without problems.

My phone had a notification yesterday that SuperSU needs to be updated. So i clicked the notification and updated it from google play store. Then there was another notification. "SuperSU code needs to be updated"

I tried to update but failed all the time. You can see screenshots in the picture below. It's Turkish language but i think it won't be a problem. I always chose "Normal" because i don't know what "TWRP/CWM" means. In the last image it says "Failed. Restart the phone and try again"

Did i do something wrong? Please help me guys. Have a nice day all.

View attachment 3101710
[SuperSU] reekotubbs:
Experiencing the same issues:

Device: Samsung Galaxy Tab 4 SM-T230NU

Root Method: Kingo

Busy Box: installed

Custom Recovery: TWRP

SuperSu installs and gives root access to applications, but after update to v2.40 I get constant update binary warning. On every attempt it fails.

Its weird, I don't have this problem on my Note 4.

Any word from Chainfire on this issue?
[SuperSU] Chainfire:
Seems to be a common theme with Kingo root users...

I know I hardly ever reply to this specific thread, but I do log all the issues and look at them. There's just usually nothing interesting to say about individual cases. And typing non-interesting things is a waste :)

There's always the ZIP installer that should always work (providing you are running a well-built and compatible recovery).
[SuperSU] d00lar:
yep i also belive that it can be kng/kongo root problem

before install i have unroted - kingroot in optons have unrot and it deleted itself

then i installed .zip 2.4 version without any problems and it work great!
[SuperSU] Atikun:
Thanks for the advice. I unroot my device with kingo root. Then i opened my phone in recovery mode. Started installing supersu 2.40.zip. It says "Installation aborted" at %20-25. Can you please help me? I am new to all this stuff. Did i do something wrong?
[SuperSU] reekotubbs:
I appreciate the response. I will try the zip installer after un-rooting using kingo.
[SuperSU] d00lar:
i have no other idea ;/

it worked for me ;)
[SuperSU] Atikun:
Thanks. I used stock recovery mode. Someone said i should ise custom recovery mode so i'll learn and try it. :)
[SuperSU] d00lar:
yep it have to be custom revocery

on stock you canot install any zip exept signed update file ;)

regards!
[SuperSU] reekotubbs:
So, the process of un-rooting if you use kingo and installing the zip using custom recovery seemed to do the trick.

Now I am fully rooted and supersu is not asking for binaries anymore.
[SuperSU] bro jo:
both option failed

im using galaxy s advance . i cannot update super su on my phone . plss:confused:
[SuperSU] yuukimoonstar:
hi,

I currently have the LG G3 D851 on version 10r, when trying to root with purple drake i get that the process was successful. But when i download SuperSU i get that there are no SU Binary installed.

could someone provide help with this issue?
[SuperSU] Solar7:
Samsung Galaxy S3 Mini - update methods failed..

Device Name: Samsung Galaxy S3 Mini

Device Model: GT-I8190T

Firmware Version: 3.0.31-833942

Android Version: 4.1.2

SuperSU Version: SuperSU Pro v2.40

Interfering Apps: Non

Update Methods Tried: In-App, ZIP ( download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip )

-- Installing package...

Finding update package...

Opening update package...

Verifying update package...

E: failed to verify whole-file signature

E: signature verification failed

instalation aborted.

Kind of Root: Nothing seems to have changed.

I hope this is enough info I do not know how to get the other info.

Best regards,

Sol7
[SuperSU] egingell:
Looks to me like you're trying to flash third-party zips with the stock recovery.

Edit: in-app ("normal") will give you a different error (logcat) on fail.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Solar7:
I am using Kingo Root, so what you are saying is I should unroot.

Then update and then re-root?

Cheers!

Sol7
[SuperSU] Lutfi Belwael:
Failed Binary Update

Samsung Galaxy Note GT-N7000

CyanogenMod 12-20150102-UNOFFICIAL-n7000

Android 5.0.2

SuperSU Free (CM) v2.40

No interfering apps

Update methods tried: In-app 'normal', in-app via recovery, and ZIP via recovery.

CWM-based Recovery v6.0.5.0

CWM "fixed" root after initial install

- What kind of root are you left with?

I don't know. SuperSU keeps asking to update binary files.
[SuperSU] RvGilead:
KingoRoot

Yes, seems to be, that most of the KingoRoot-Users have a problem with updating the binary.
[SuperSU] shatteredruby:
ASus Memo Pad HD 7 Binary Update Fail

Device Name: Asus Memo Pad HD 7

Android Version: 4.2.2

SuperSU Version: SuperSU Free v2.40

Interfering Apps: Non

Update Methods Tried:

-Update both in-app normal/TWRP options when installing binary

-Tried Install SuperSU into /system option after version update

-Tried google play clean up option and reinstalled SuperSU , reboot

Kind of Root:

- Still have root (checked using Root Checker Basic)

- All Current Root Needed Apps Usable

- SuperSu still asks for grant permission for all root needed apps (so assuming root didn't disable)

- Used 'Kingo Root' to install root on device

Random Question

Even though SuperSU binary isn't updated is it still possible to full unroot my device if I need to through SuperSU?
[SuperSU] TonyA.:
Binary update error

Recently I update SU via Google play, and I've been asked for binary update. Basically I press continue, normal (like every time) and then Installation failed. I try couple times, even afer restart. Error still appear. On the other side, app running as normal. Still provide root access for two apps.

P.S. SU runs as system app. Device: Samsung Galaxy Core. Jelly been 4.1.2.
[SuperSU] rom1g92:
Bootloop

Bootloop after flash 2.45

I've a bootloop with my OnePlus One after i've flashed 2.45 update.

Somedy else have this issue?

Sorry for if my english isn't good
[SuperSU] Chainfire:
It is absolutely no use posting unless you let us know which exact firmware version you were running, what version of SuperSU you came from (if any), and which method you used to install.
[SuperSU] rom1g92:
Oh sorry, my previous version was 2.44. My ROM is the stock rom of OnePlus : 44S. And I have flashed SU via recovery.

It's not my first flash, not my first time so it's why I don't understand this issue.
[SuperSU] Chainfire:
There are no significant changes between 2.44 and 2.45 so a bootloop when upgrading from one to the other is strange. Try wiping dalvik cache from recovery.
[SuperSU] rom1g92:
I tried a dalvik wipe and a cache wipe. But it doesn't work.

So i did a factory reset :(
[SuperSU] Solar7:
Updated to "latest of now" 2.45.. SuperSU keeps asking me to update..

Device Name: Samsung Galaxy S3 Mini

Device Model: GT-I8190T

Firmware Version: 3.0.31-833942

Android Version: 4.1.2

SuperSU Version: SuperSU Pro v2.45

Interfering Apps: BusyBox

Update Methods Tried: CWM (passed flawlessly)

Kind of Root left: Nothing seems to have changed, as ROOT as always.

SuperSu keeps asking for new update after installing latest, am I installing wrong? :eek:

Best regards,

Sol7

ps. All you guys who work your guts out to help all people here, MUCH appiciation out to you! Cheers!!

pss. so you think im not a robot.. huh? :P
[SuperSU] xXxRSxXx:
installation failed

pls help me to fix the installation failed ... i updated the su in google play.... after that i run the apps. then show the " the Su binary to be updated . continue?" iclick continue..... then show the " if you have custom recovery like TWRPor CWM, that can be used to (try to) install the subinary. this isrecommended for HTC devics. how would you like to install the SU binary?" the i choose "normal" then after that installation process ... then after a min show a "installation failed please reboot and try again" then i try to reboot and try the process so many times but did not work .....

my phone is samsung S3 rooted ....please help me to fix this issue ....

thanks!!!!

samsung S3

GT-19300

4.3
[SuperSU] phamhoangthai1994:
Update failure supersu

I do not know when I shall have root rooting success, when in SuperSU it will report "su binary needs to be updated" When I hit continue to update it after a few minutes the error "Installation failed "I do not know all how to overcome? Do not in any way SuperSU. root test application called "Root checker basic" when I activate it indicates a successful root then but super ask themselves constantly updated::(
[SuperSU] damienMTL:
SuperSU binaries update Failure on HTC One S (Fido)

Hi,

I just try to ROOT my phone. ROOT access seems to be ok according to ROOT CHECKER but I have issues updating the SuperSU binaries. All attempts to reboot to recovery etc from the software is a failure.

My phone is an HTC One S from FIDO Canada. (Android 4.1.1, HTC Sense 4.63)

I proceed in a very regular way

:

1. I Unlocked the bootloader via HTC website

2. I flashed ClockworkMod Recovery v5.8.1.5 (recovery r2-modaco-recovery-clockwork-touch-ville*.img) with an OSX command line (ok)

3. I Installed SuperSU pack from recovery (SuperSU v.0.94) (ok)

4. I tried to install the binary update (failed)

5. I Installed the SUperSU update via GOOGLE Play (ok)

6. SuperSU ask to update the binary

7. I clicked yes for an install by CWR > failed several times (sometimes crashes)

8. I clicked yes for a normal install > failed several times

9. I tried to install the latest SuperSU via recovery pointing to the zip > failed during install

May I flash the latest CWR recovery pack in ovewriting it and start from scratch with all the latest versions of SuperSU and binaries?

Can someone please help me to have everything working 100% Ok? Thanks a lot in advance
[SuperSU] damienMTL:
Hi,

I reply to myself :)

I flashed the latest CWM Recovery available

then did a Nandroid backup

Then flashed the latest SuperSU .ZIP available

and it worked ok this time

My phone is rooted and I don't have this annoying library update popping up anymore. I still have some trouble to remove the stock apps/bloatware, it crashes the phone and reboot without any effect via AppMaster. I will try to install a clean fresh ROM later on.

Thanks
[SuperSU] Nekromantik:
Same issue here:

Device Name: HTC One

Device Model: M8

Android Version: 5.01

SuperSU Version: SuperSU v2.45

Interfering Apps: BusyBox

Update Methods Tried: both, notmal does not work and twrp causes supersu to force close

Root left: No root
[SuperSU] Senzi:
Problems with SuperSU

I have installed chainfire, but still not working. says there is no binary fil to SU installed. What to do now?

My version is 4.4.2

device model

Samsung Galaxy GT 19505
[SuperSU] Gakuseinozen:
- Exact device model

Galaxy Note 4 (T-Mobile) - SM-N910T

- Exact firmware version

Stock firmware. Baseband version N910TUVU1ANJ7, Kernel version 3.10.0-2796035, Build number KTU84P.N910TUVU1ANJ7

- Exact Android version

4.4.4

- Exact SuperSU version

App version is 2.40. After attempting to update, the app says version 2.40 but when I run the su -v command in adb shell it says "2.35:SUPERSU"

- Interfering apps

The superuser apps I run are as follows:

Titanium Backup

Wanam Xposed

adb Insecure

Terminal Emulator

- Update methods tried

I have tried both in-app and through TWRP - both result in my phone force-rebooting in the middle of the process and the update not succeeding. In the case of the TWRP method, the phone reboots back into recovery - hopefully this did not prevent me from getting a proper last_log file.

I have a similar problem when trying to update files in my /system/ directory (hosts file and platform.xml, specifically) - when I try to edit the file directly in ES File Explorer and save it, my phone force-reboots and the save is unsuccessful. When I try to copy the file, paste it somewhere outside of the /system/ directory (Downloads, or wherever), edit it and then copy-paste it back into the /system/ directory the same thing happens. When I try to push the file via ADB, the same thing happens. I've also tried to update the platform.xml file via the market "NextApp SD Fix" app, and get the same result. I believe this issue and my inability to update the SuperSU binary are caused by the same thing, but I do not know what that is.

- What kind of root are you left with?

Nothing seems to have changed at all, even the GUI still shows the old version number. All apps still have root access.

App version is 2.40. After attempting to update, the app says version 2.40 but when I run the su -v command in adb shell it says "2.35:SUPERSU"
[SuperSU] doveman:
Hi

- Exact device model

Lenovo A8-50 A5500-H tablet

- Exact firmware version

A5500HV-A442_000_024_141007_ROW (flashed with HV firmware from here http://xdaforums.com/showpost.php?p=58181619&postcount=36 ,stock as far as I know)

- Exact Android version

Android 4.42

- Exact SuperSU version

Tried with v2.40 and now v2.44

- Interfering apps

None, just formatted Data from TWRP to remove encryption

- Update methods tried

Normal, TWRP and zip flash from TWRP. Normal fails, TWRP reboots to TWRP and appears to be flashing something from cache/updater.zip and zip flash from TWRP worked to update from v2.40 to v2.44 but it still says the binary needs to be updated when I open SuperSU.

Installed TWRP is update_TWRP_281_A8-50.zip from here http://www.4shared.com/folder/1QQs_w_w/A8-A5500.html?detailView=true&sortAsc=true&sortsMode=NAME

- What kind of root are you left with?

root and SuperSU works and shows v2.44, it's just the "binary needs updating" message that keeps coming up. su -v shows 2.02:SUPERSU

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

The adb pull command says the remote object does not exist but I found it with ES File Explorer (in the /cache/recovery folder, so I don't know why pull couldn't find it) and copied it to my PC that way and attached it.

- Logs from TWRP, when updating SuperSU completely via ZIP

The abd pull command doesn't work for this either and there doesn't appear to be a /tmp folder on my device (I'm using Root Explorer in ES), only a tmp-mksh which only has a tmp-mksh file in of 149.74KB.

- Logs from SuperSU (very important)

Attached.

- Various logs (very important)

Attached.
[SuperSU] 31N5731N:
Binary update not working

Model No. SGH -1547c

Android version 4.1.2

SuperSU v2.40

I have Avira but I don't know if that interferes.

Tried Normal and I'm lack the experience (as of yet) to properly try the TWRP

nothing has changed after the failed update.

If you can help cool. If not that's cool as well I guess
[SuperSU] jerwam:
Unable to update binaries

Unit: Asus AIO P1801-t

su v: 2.40

And v: 4.2.1

method: normal

others tried: none, no custom recovery for P1801-t yet

Cheers
[SuperSU] swampdog:
Hi Folks,

First posting here but just in case I've stumbled upon something that's been missed..

supersu (free) 2.45

Kango (latest but doubt it matters)

For reasons unimportant here, I accidently rooted my cheapo tablet.

It appears kango wrote to /system/sbin/su whereas supersu wrote /system/xbin/su and subsequently supersu would keep wanting to update 'su' then fail.

The long and the short of it is once I manually removed /system/sbin/su supersu stopped telling me 'su' was outdated. I don't know android but I do know linux.

$PATH on my tablet has /system/sbin/ prior to /system/xbin/ so it would appear supersu is issuing 'su -V' as opposed to '/system/xbin/su -V' when it checks the version. The kingo 'su' was older than the supersu 'su'.

Dunno what the solution is 'cos the older 'su' is going to get called first & I figure there's nothing but trouble to be gained from changing $PATH globally. Nevertheless it might be enough to check $PATH for unwanted 'su' and flag them, possibly offer to remove them? In my case I renamed it "/system/sbin/su.ORIGINAL" so that it's still runnable in an emergency.

Cheers!
[SuperSU] doveman:
Man you're awesome! That fixed my problem too.

I'd originally tried rootmaster.apk which didn't work. It actually installed apotide and then iroot, which said it had worked but after rebooting, Root Checker showed it as not rooted.

So then I did it with Vroot which worked and subsequently I uninstalled all of these and flashed a rooting zip for my A8-50 and SuperSU but clearly it hadn't uninstalled /system/sbin/su.

I might actually be able to give this tablet to my Mum now that's sorted :)
[SuperSU] Chainfire:
Interesting... can you guys with /system/sbin issue confirm post your shell environment ?

adb shell set
adb shell printenv

(one of those should work, if they both do, their output is the same)

Next update will remove these sbin files (and some others as well)
[SuperSU] swampdog:
Attached file contains 'z0' (set for root) and 'z1' (set for a normal user).
[SuperSU] swampdog:
Sorry for replying to myself. Firefox won't display the captcha & opera doesn't display a cursor when editing!

Something's dodgy with my usb cable but "wow, just discovered my phone (gingerbread) has no 'find', 'tr' or 'awk'" unlike my tablet. Dunno if supersu supports gingerbread (I have superuser on that) but a possible shell only method..

#!/bin/sh

echo '{'$IFS'}'

(IFS=':'

for i in $PATH

do

[ -d "$i" ] || continue

[ -f "$i""/su" ] || continue

#found a su

echo "[$i]"

done

)

echo '{'$IFS'}'

..only tested under centos tho - I haven't the eyesight to type that into my phone!
[SuperSU] egingell:
Don't those commands come with busybox?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] RvGilead:
I've deleted:

/system/sbin/su

and kept

/system/xbin/su

This fixed also my problem with the UpdateBinaryFailed after using

KingoRoot

.
[SuperSU] Gakuseinozen:
Any suggestions for those of us with different types of issues?
[SuperSU] Frank Westlake:
I take it that you have the binary update issue and that you do not have a 'su' in '/system/sbin'.

The problem is that there is another 'su' that exists in the search path prior to SuperSU's 'su'. The path can be changed at any time so you could still have a conflicting 'su' that is found by SuperSU but not by you. To look for ANY 'su' on your device run this as root:

type / -name su

It will take a few minutes and you should find only:

/cache/cfroot/su

/system/xbin/su

If you find others, say so here.

Frank
[SuperSU] Gakuseinozen:
Fairly sure my issue is completely separate (see my previous post), but when I type / -name su in the terminal emulator I get "can't execute: Is a directory"
[SuperSU] Frank Westlake:
OK, your previous post only said different types of issues. That wasn't very clear so I made the assumption just in case.

Sorry, I meant to run the command 'type' followed by the directory and file name, as:

type / -name su

If your's isn't a binary update problem then that won't be useful.

Frank