yashsingh1/xdaforums huggingface dataset:
[SuperSU] andro1duser:
Fail To Update Pro version On Google Play Store

Samsung Galaxy Nexus (i9250)

Android Version 4.4.4

Paranoid Android Version 4.4.5

After i update paranoid android rom from 4.4.3 to 4.4.5, my apps lost root access so i tried to update supersu from play store (sorry, i forgot which version), but play store forced close and cant be open anymore, found the latest supersu version 2.36.zip, installed, all apps gain root access again, playstore also working, so i tried to update my supersu pro version, again playstore force closed and cannot open, but apps still have root access, i only know how to install zip from phone, i dont understand adb or anything, unless i can follow exact step by step :( now a message pop out from time to time saying "unfortunately google play stopped .."
[SuperSU] Supereloaded:
ouups my mistake I desactivated SU !!!!

did it again and no error messages but when I starts knox it goes down a few seconds after ...

Any idea ?

by the way , i have a galaxy S4 GT-I9505.
[SuperSU] absentrecall:
Nexus 7 (2012) supersu installation failed

- Exact device model

Nexus 7 (2012) 3568A-ME370T

- Exact firmware version

Kernel version: 3.1.10-g5d8ecd2

Build number: LRX21P

- Exact Android version

Android 5.0

- Exact SuperSU version

To: SuperSU Free v2.36

From: don't remember

- Interfering apps

There are some apps that can interfere with SuperSU installation, primarily:

- other Superusery apps NONE

- Xposed NONE

- BusyBox (symlinked or non-symlinked) YES (symlinked ... I think)

- Update methods tried

In-app 'normal',

- What kind of root are you left with?

- Root seems to still work.

- Logs from SuperSU (very important)

Attached. Collected via catlog

- Various logs (very important)

Attached. Collected using local console (Connectbot).

su --self-test >> sulog.txt produced a loop where Connectbot was granted root repeating. Stopped it by rebooting and then continued with log collection.
[SuperSU] schaggo:
Directed here by [MENTION=1199571]creesch[/MENTION] from the general SuperSU thread. See his report below:

My original post in the SuperSU thread can be found here: http://xdaforums.com/showpost.php?p=57108963&postcount=7601

Your reply: http://xdaforums.com/showpost.php?p=57109710&postcount=7604

My reply: http://xdaforums.com/showpost.php?p=57130449&postcount=7622

Exact device model

Sony Xperia Z1 Compact D5503, unbranded Switzerland/Western Europe build

Exact firmware version

Latest stock 4.4.4 which is 14.4.A.0.157 for this model

Exact Android version

Android 4.4.4

Exact SuperSU version

I was running 2.05, updated to 2.35 via android market, after updating su binary from within app (normal mode as no recovery running) noticed write operations to /system failing. Complete wipe and reflash of /system partition, re-rooting with 2.36, still failing write operations to /system partition. Subsequent reflash of /system partition, re-rooting with 2.05, things running smooth again.

Interfering apps

I use Xposed and have busybox symlinked.

Update methods tried

As per above, 2.05 was running by using the one-click-root of Androxyd's flashtool for Sony devices. Root is effectively gained through towelroot and SuperSU incl. su binary is then pushed to /system. APK update came through play store, binary update was done using normal mode in app, as I have no recovery running. Binary update from 2.05 to 2.35 eventually worked after several retries, binary update from 2.35 to 2.36 did not work.

What kind of root are you left with?

Root apps work, apps requesting root access trigger SuperSU. Several apps which rely on root access work flawlessly. Only apps trying to mount /system r/w and writing to /system fail.

Various logs (very important)

Attached.
[SuperSU] feriber:
I knew that.

In my other devices i've updated from 2.35 to 2.36 and they did not asked me to update binaries.

It's my Samsung SII who does not want to update binaries.

That was what i was trying to say. It doen not update with neither versions.

Thanks
[SuperSU] egingell:
That's weird. You must have stated your ROM and provided logs, but I can't seem to find either.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] feriber:
Excuse me ??

I think we all should be a bit more cautious.

Look at the link above: post #108
[SuperSU] egingell:
If I can missed it, so can [MENTION=631273]Chainfire[/MENTION].

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] feriber:
Nothing is further from my intention to call attention to anyone......

And much less to [MENTION=631273]Chainfire[/MENTION] who (i guess) will be very busy.

I was only trying to give new information.

I'm not demading anything to anybody.... so I kindly ask you please to be careful with your supositions.....
[SuperSU] dzigi.bau:
Issue here.

TV Box, rooted, emulated as Nexus 7.

With the version 2.35 I began to have binary update, through Normal button, ending with Installation failed. TWRP is the same.

Could you check it out and probably fix binary update through Normal button.

Tried to re-install SuperSu, no result here. Application works, giving permission to my apps, but the binary update remains a problem.
[SuperSU] titetanium:
Problem updating to v2.35 fixed.

Hi, I have two devices that are rooted, a 2013 Moto X, and a EVGA Tegra Note 7 tablet. I updated both with failures with both the normal and twrp/cwm options.

Tablet: Did not have custom recovery, original installed version 2.01, tried normal update to binary from play store and it failed. Just for giggles tried twrp/cwm and that knocked root off the tablet. Flashed a custom twrp recovery and tried to flash it directly but that didn't update the binary either. Tried the normal option and that failed but when I tried twrp/cwm, it finally updated the binary. Weird, I chalked that up to not having custom recovery in the first place so considered that done.

Phone: Has philz cwm recovery, original installed version 2.01, used twrp/cwm option to update binary and lost root. Used recovery to reinstall root and get a prompt to install from play store. Reinstalled from play store and of course used twrp/cwm option with same result as before. Reflashed root from recovery and reinstalled from play store, this time using normal and it updated the binary.

Both devices updated but in different ways. I don't know what accounts for the inconsistency as I didn't get the logs for either one but thought you might want to know.

Updating from 2.35 to 2.36 had no problems on both devices.
[SuperSU] moeaeon:
can i dump logs that can help you, without PC?
[SuperSU] egingell:
There are loads of apps on the Play Store. Plus, terminal emulators.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] feriber:
Version 2.37 solved my troubles

Now with version 2.37, my binaries have been updated.

Thank you very much to [MENTION=631273]Chainfire[/MENTION] and also to everybody who has helped to deal with this issue.
[SuperSU] egingell:
SuperSU 2.37 - SGS2 - update successful.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] blocka:
Update Successful

Hi,

v2.36 second update success.

thank you!!!
[SuperSU] absentrecall:
v2.37 updated the binary correctly on Nexus 7 (2012). Thank you.
[SuperSU] moeaeon:
how can i make needed dumps from terminal?
[SuperSU] egingell:
Google "logcat". I'm not about to post a tutorial here.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] bjorn96:
- Exact device model

-XPERIA Z2 D6503

- Exact firmware version

23.0.1.A.0.167 (from OTA)

- Exact Android version

Android 4.4.4

- Exact SuperSU version

2.37

- Interfering apps

XPOSED FW is not able to install/uninstall. It says system is read only.

Other apps says root is there...
[SuperSU] guhvanoh:
I'm pretty sure this is not a SuperSU issue but a Sony one. I have the same /system write issue. So far I've not been able to sort it out. You need to sort out the Sony ric.
[SuperSU] bjorn96:
But the thing is that it fails on .314 too...
[SuperSU] guhvanoh:
Same for me too. I decided to stick with 4.4.4 for the moment. At least I can backup with Titanium backup to my internal drive and still read from the external sdcard...
[SuperSU] schaggo:
Same issue, reported twice already in this thread. See here and here.

I downgraded to SuperSU 2.05 and root works a treat. How I did it:

Get Flashtool; get most recent still rootable kernel (in case of locked bootloader); get most recent firmware FTF

Flash /system only with system part of downloaded FTF *1

Flash kernel only of most recent still rootable FTF *2

Root device using Flashtool one-click-method (pushes SuperSu 2.05 to device)

Once root is obtained, flash kernel only from newest FTF (same version as /system) *3

*1 gets rid of all root leftovers and modifications to /system

*2 exposes system to towelroot, as towelroot needs vulnerable kernel not system

*3 matches system build and kernel build to newest version

Leaves you with fully up-to-date system, matching kernel and full root including write access to /system with SuperSU 2.05.
[SuperSU] Chainfire:
I really have no idea what's going on with Sony. It is odd though, that 2.05 works while 2.37 doesn't. Has anybody tries disabling mount namespace separation setting in SuperSU and rebooting?

I haven't seen any useful logs on this issue yet, though tbh they issue is pretty vague to me still.

Does remount r/w and modifying system work in adb shell?

Can root explorers modify /system?

It may end up simply being a minor thing somewhere...
[SuperSU] bjorn96:
Sorry, cannot give that log. Just went over to CM... And it works fine...
[SuperSU] Frank Westlake:
That last sentence could mean that mount and write always fail, but the comments previous to that which I've also quoted indicate that the failures are intermittent. This might be a synchronization error. Maybe 'mount' is sometimes returning before the mount has been completed, so writes fail. A test for that could insert a delay between mount and write. Or maybe there is some type of quota on mounts; maybe reattempting the mount and write a few times could help determine this.

Frank
[SuperSU] janusman:
I have had update failures with latest version.

Asus TF300T - Android 4.4.4

Omni Version - 4.4.4-20140803

Kernel Version - 3.1.10

I tried up uninstall, reinstall from Google play, tried updating in app (normal & TWRP) and everything failed. Finally, downloaded the zip and flashed from TWRP and it worked without any issues. Looks like I have to update with zip every time an update is released?
[SuperSU] power2top:
Just came in to write that 2.37 has resolved all the su binary update issues I was facing. Thanks [MENTION=631273]Chainfire[/MENTION] for eventually resolving the issue. :thumpsup.
[SuperSU] creesch:
I just tried disabling the mount namespace separation which had no effect.

As far as logs go, I have posted all those you requested here a few days ago. If you need more I'll glady provide them.

Trying to remount through ADB shell gives an "Operation not permitted" error.

Any root app that required modifying /system does not work anymore, this includes root explorers.
[SuperSU] nand.96:
[MENTION=631273]Chainfire[/MENTION] I'm Using SuperSU v1.99r4, i Go to play store hit Update,it downloads and then it says Wrong update package! Please,give me a solution,i am using Samsung Galaxy Core!
[SuperSU] Given92:
cannot flash binary.

I failed to flash latest supersu v2.37 but the old version(supersu v1.94) works. I download all the zips from your website.

The recovery.log followed.

My android version is 4.3.1 and my recovery is a self-built CWM-based Recovery v6.0.5.1 .

After flash v2.37:

$ adb shell mount /system
$ adb shell ls -l /system/xbin/su
-rwxr-xr-x 1 root root 71264 Jan 10 18:07 /system/xbin/su

istead of which of v1.94

-rwsr-sr-x 1 root root 113036 Jan 10 18:10 /system/xbin/su

Maybe because of this, when I reboot from CWM, it noticed that Root access possibly lost, Fix?

It doesn't make change by selecting yes.

It's more stranger that, when I boot into Android, I find:

$ adb shell ls -l /system/xbin/su
-rwxr--r-- root root 71264 1970-01-11 02:12 su

Could you please give me some help?
[SuperSU] ummkiper:
No matter what version I use.I get update binary notification.If I update and reboot supersu says no binary is installed.i have tried through recovery and normal either way breaks root.

I'm using a Sprint note 2 sph-l900 running [Rom][4.4.2]AllianceRom_Sprint Build 1- 30 Themes [12/5/14][Fully Customizable][NE2]

https://www.androidfilehost.com/?fid=95832962473397688

kernel version is

3.0.31-1561791

dpi@SWDD5716 #1

currently using supersu 2.37

I have to use dr ketans kit to reinject root then get supersu from play store and I have root again till I update binary.
[SuperSU] harm007:
update superSU binary files with adb or fastboot ?

Hello.

On my HTC One M7 rooted, I can't update binary files of superSU.

(cid HTC__203, S-ON, firmware 6.09.401.5, android 4.3, sense 5.5, software number 3.63.73.2,

With "normal mode", my HTC One reboots immediately.

I can't use TWRP/CWM method because I don't succeed in installing custom recovery.

(believe me when I say I don't succeed : I unlock bootloader, ... but nothing to do).

My question is : "is it possible to update superSU binary files with adb commands or with fasboot commands" ?

Thanks for all.

Regards.
[SuperSU] :
Cannot update SU Binaries with ver. 2.40 Please update version in Play Store. Running a GPE Android 5.0 ROM on a Verizon HTC M8 device.
[SuperSU] lchupacabras:
Try flashing the update su zip.
[SuperSU] :
Already successfully flashed the zip through recovery; however, the version in the Play Store should be fixed.
[SuperSU] Chainfire:
No logs (see first post) == nothing I can do
[SuperSU] ismaeel96:
SuperSu doesnt work after binary update

sprint galaxy note 2 SPH-L900

3.0.31-1561791 dpi@sqdd5716 #1 (pretty sure stock)

android 4.4.2

supersu 2.40

when i update binary for SuperSU it stops working. i dont get a message or anything but when i try to use an app that need root sometimes the app tells me that it doesnt have root permission or some apps dont ask for it at all when i open supersu app the screen goes black. i tried updating binary using normal and cwm. also, when promted to fix root on cwm recovery (when trying to reboot) i tried both fix root, and not fixing root.
[SuperSU] mjfiori:
Moto X Pure Edition msg: There is no SU binary installed...This is a problem!

I bought this phone on Swappa and it was unlocked. Looks like your app was installed.

It seems like Google is trying to send me an update to 5.0.1 but it is failing. I thought I would use your app to un root the phone but I can not even open the app (see screenshot below)

I read your Uninstall instructions but have no idea what other Superuser app there is on the phone that would replace SuperSU.

Unfortunately, I can not even open the app (see screenshot below) and I would appreciate it if you could help me please.

In spite of having attempted to read about it, I am clueless on rooting. I also have a Mac running 10.10 and the Motorola USB drivers don't seem to work with this machine so I can't even connect the phone to the laptop to use a terminal window or ADB (not that I really know what ADB is to begin with).

Here is a screenshot of the msg that comes up when I attempt to open SuperSu from the Play Store

[IMG="Fail toast"]https://drive.google.com/file/d/0Bx4GqGCe0GPjQzhOVnR2SVJWQW8/view?usp=sharing[/IMG]

Here are answers to the questions that you asked above.

- Exact device model

Moto X Pure Edition (2014) XT1095

- Exact firmware version

Which exact firmware are you using?

You mean Kernel?

See Attached screen shot if that's not what you meant, I don't know where to get the Firmware info.

[IMG="Phone info"]https://drive.google.com/file/d/0Bx4GqGCe0GPjTnN4VzBJd1VLcTA/view?usp=sharing[/IMG]

- Exact Android version

Android 5.0 (I think Google is trying to send me an update to 5.0.1 but it is failing to install).

- Exact SuperSU version

Which version were you running?

As I said above, never used/ran it.

and to which version are you updating?

2.05 is the version I see in the App info.

- Interfering apps

None of these things listed below are installed on the phone.

- other Superusery apps

- Xposed

- BusyBox (symlinked or non-symlinked)

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

- Update methods tried

In-app 'normal'

- What kind of root are you left with?

no idea

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

After pressing the TWRP/CWM button

I can not open the app on the phone. (see attached screenshot above)

- Logs from TWRP, when updating SuperSU completely via ZIP

no idea how to do this

- Logs from SuperSU (very important)

all I have is a mac running 10.10 and the MDM USB drivers do not appear to run on here yet so I do not appear to be able to use ADB.

- Various logs (very important)

all I have is a mac running 10.10 and the MDM USB drivers do not appear to run on here yet. so I do not know how to do this and get any of these files.

If you can help, it would be greatly appreciated. As I said, I'm generally clueless but I can follow instructions and I will respond to questions/communication.
[SuperSU] ZMOT7S:
Fixed the Issue. Used the reinstall option in settings and when I rebooted the update worked. Thanks for a great app Chainfire!

SuperSU binaries quit responding when trying to update with TWRP and fail when updated normal. Not sure what is causing it. Just installed a new rom, clean install.

Exact device model - HTC One M8 Verizon USA

Exact firmware version - Beyon Stock Firmware from this thread http://xdaforums.com/showthread.php?t=2716306

Exact Android version - 5.0.1 running this rom http://xdaforums.com/showthread.php?t=2716306

Exact SuperSU version - Free 2.40 from the play store

Interfering apps - No xposed, no other SU apps. I'm not sure about busybox. I haven't installed it but it may have came with the rom.

Update methods tried - Both normal and TWRP. The version of TWRP is 2.8.0.1 official.

What kind of root are you left with? - Fully functional root still..

Logs from TWRP, when updating the binary using the TWRP/CWM button inside the SuperSU app - Didn't make it to this step. Says does not exist in adb

Logs from TWRP, when updating SuperSU completely via ZIP - Didn't update from zip

Logs from SuperSU (very important) - Attached below.

Various logs (very important) - Attached below.
[SuperSU] WORF84:
I don't get a message in SuperSU app, only in notification.

Tried reinstall and flash SuperSU zip from http://download.chainfire.eu/supersu

Same thing always.

I even delete the SuperSU in root path in TWRP Recovery File Manager.

Is this a bug?
[SuperSU] s3icc0:
binary problem

Hi [MENTION=631273]Chainfire[/MENTION],

sorry not to post required logs, atm no access to adb.

I switched from CM11 to CM12 early build today with my i9505 (which was originally cf autorooted). And I lost root. Now after re-rooting the device, new recovery I finally have root access, but superSU still says I need to update binary - but non of the methods is working. I started with 2.40 now I tried 2.41 but still the su binary is requested to be updated.

How can I update when "normal" and CWM/TWRP ways are not working?

Thanks for help (or tell me what logs exactly do I need to generate for you)

or maybe better question: How can I manually update the su binary?
[SuperSU] manjowafu:
no su binary installed

Device GT-i9295

Android Version: 4.4.2

Rooted phone using CF-auto root (odin)

Files intalled that needs root: titanium backup, rootexplorer(I haven't change a lot to my phone except removing the pre-installed apps)

Issue: Im not really sure what happened, but it all started when I copied some files(pictures videos..) from my pc using samsung kies and accidentally disabled supersu. When I wanted to enable it again, it wont let me because it says that no su binary installed and cant update it. So I went to apps store to update the supersu. But I still get the same problem. Im new to android, I just rooted my phone a month ago and everything works fine till now. I have no Idea how to see the logs so I cant post it here.

Now im thinking to root again my phone but im not sure if it will solve the problem. Or should I unroot it first eventhough it seems im not rooted anymore?

Thanks in andvance.
[SuperSU] altecck:
Problem Updating Binary

I have a Nexus 5 running Android version 5.0.

SuperSU Free version 2.40

I just rooted my phone a few weeks ago, I didn't think I had any problems. New to Android, so after I was acquainted with it I followed a guide on YouTube after some reading. Everything went fine, SuperSU installed and seemed everything was working. Note: I encrypted my phone after rooting few weeks ago. No problems there. Few days to maybe a week ago I kept getting the notifications to update my SuperSU binaries. No method I have tried has worked. I tried just hitting ok and Update and it says "Please wait, updating.. If you still see this screen in 5 minutes reboot your device" I wait and wait and end up rebooting. I tried to Uninstall through SuperSU to re-install at the Google Play store and it gets stuck on Uninstalling.. no matter how long I wait. I tried dropping the .zip onto my device to try and flash it through recovery mode in TWRP but I couldn't find it. I did see an older SuperSU .zip on my device when I did that (When I plugged it into my PC, on my PC file manager)

I downloaded Root Checker and tried to verify root and it says my device is not rooted and Titanium Backup is stuck on verifying root.. upon load. So I think I screwed something up. But this all started happening once I got the notification to update the binary and tried all this. That said, SuperSU is still giving out permissions and works. So.. :confused:

I have to update my Android to 5.0.1 but want to wait to see what the hell is going on. Do I have to re-wipe my device and root from scratch again? What is going on? What happened? And how can I fix this? :crying:

Please, I hope someone can help. Thank you.
[SuperSU] ahh37:
Hi there

Reroot after unroot my phone and restart it again. What's the problem?

Is there a solution?
[SuperSU] tzeus:
Boot loop

Hello!

Device: LG Nexus 4

OS: Android 5.0.1 Official

Recovery: TWRP

Steps:

I flashed TWRP via fastboot, then i flashed superSu 2.40 from TWRP. I am now stuck in a boot loop.

LOG file: http://www.hastebin.com/zakiyejaca.vhdl

Diregard this post:

I just checked and i was using an old version of TWRP(because i downloaded the first one in the list which is the oldest), i updated to last version of TWRP, flashed 2.40 again, android just started.
[SuperSU] bahrosuz:
.

Gesendet von meinem SM-N9005 mit Tapatalk
[SuperSU] Shinkoku:
Hello

I cannot update my SuperSU no matter how I try, manually or cwm/twrp. Install goes seems ok but binary update fails.

Could you help me on that? Details below.

Thanks!!!

Device ID: SC-01F (Samsung Note 3 Japanese model by Docomo)

Android 4.3 official, SC01FOMUCNC3

Tried to install 2.02, then 2.40 through CWM

Try to install it on newly-bought phone, so, nothing interferes I believe

Tried both manual and through recovery update, recovery is CWM 6.0.4.5, taken here

Root isn't present. Terminal says su: not found

Couldn't get either of twrp/cwm logs - got "does not exist" message in adb.

SuperSU and sulog logs attached.

P.S. Tried versions 2.02, 2.40 and Beta 2.42
[SuperSU] xCHAOSNCx:
I'm running Echoe Rom v29.1 on my i545 for about two weeks now and it runs excellent except the supersu binary won't update I personally purchased supersu pro have but still won't update need help please HUGE THANX to CHAINFIRE you are the man.......

Update 12/31/14: tried installing from recovery but it kept taking me to stock recovery used the ss recovery and it installed the updated binary first try now everything workin great my titanium backup is up and running and the viper4android.apk has my subwoofers about to knock my rear view mirror off :cool: ... so once again you are a legend much thanx
[SuperSU] ArYaNsH:
Updated the app recently and i got this error :

Device: ippo v12 tablet

Android 4.4.2