yashsingh1/xdaforums huggingface dataset:
[SuperSU] power2top:
Tried that i.e connected to my PC while I flashed supersu 2.16 while still in CWM(did not reboot after installing 2.16). On phone reboot, got the dreaded SuperSU binary needs updating, I selected CWM/TWRP boot, phone boots in recovery, I allowed installation and selected 'No' for fix root and disable flash recovery. reboot. After phone boot, I again select SuperSu app icon and it now say 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!.'

Edit: I rebooted in CWM to patch back to 2.01 working version then thought, let me try the steps given by Chainfire again. I did the adb shell, mount, chmod stuff, restart phone. once started, I try to start SuperSU and it says 'The SU binary needs to be updated. Continue?' :(. Then I start terminal app and tried 'su -' and SuperSU is asking for grant/deny!?!?!? I granted access and was allowed root access!!. [MENTION=631273]Chainfire[/MENTION], whats up with SuperSU? Why is all fine and yet showing this error.
[SuperSU] Chainfire:
Did you allow it to do the update?

Please provide the logcat with installer info mentioned in the first post.
[SuperSU] RudyH246:
I'm not "updating" my SuperSU; I'm just trying to install it for the first time so I can root my HTC Jewel. Doesn't seem to be working at all, even though TWRP says "Success!" when I flash the .zip. Also tried to flash using adb sideload, but that gave an error. Not sure what to do.

- Exact device model

HTC EVO 4G LTE (Jewel)

- Exact firmware version

JEWEL PVT SHIP S-ON RL

HBOOT-2.09.0000

RADIO-1.13.11.0830

OpenDSP-v31.1.0.45.0815

eMMC-boot

Oct 18 2012, 15:46:20

- Exact Android version

Android 4.1.1 (w/ HTC Sense 4+)

- Exact SuperSU version

Not currently running any version of SuperSU. Trying to perform an intial root on my HTC Jewel.

- Interfering apps

None listed. ROM is relatively clean. Haven't installed much since I got it yesterday.

- Update methods tried

ZIP via recovery using TWRP 2.7.1.0 and UPDATE-SuperSU-v2.16.zip

- What kind of root are you left with?

- Nothing seems to have changed at all. SuperSU is not listed in the App drawer, and I cannot make my file browser run in root mode. Pretty sure there's been no change.

- Logs from TWRP, when updating SuperSU completely via ZIP

remote object '/tmp/recovery.log' does not exist

- Logs from SuperSU (very important)

N/A. Not installed.

- Various logs (very important)

Attached.
[SuperSU] gmx.tel:
I'm sorry, after supersu update fail i cannot put the phone into recovery/download mode, it just stays in an infinite startup screen. Any way to repair?
[SuperSU] power2top:
[MENTION=631273]Chainfire[/MENTION], I had done update in CWM previously and had provided all the info then. Please find the post below. It shows 'Su binary not installed...." error. Then you asked me to get logs which I had provided in post after that and then you gave me those commands to run which chmod's su via CWM and still it did not work and the outcome I posted in my last post. What additional info is needed now is not clear.
[SuperSU] Chainfire:
Indeed it seems none of the changes to /system stick. Very strange. In TWRP, you can try first manually mounting /system, then flashing the ZIP, see if that helps.

See the quote below. You did provide logs, but not these logs, last time.
[SuperSU] power2top:
Ahh. Like I mentioned in one of my posts, none of the other commands worked for me. This one yields no output. I tried starting SuperSU, it gives me binary update error. I tried running this command and there is nothing in the logs. Should I be running this in some particular fashion? BTW, 'find /i' or 'grep /i' does not work for me. I am on Arch Linux. Does SuperSU have some text log which I can access and provide to you? The GUI of SuperSU is currently useless for me coz on startup itself it gives error and closes.

Edit: I figured you meant 'grep -i' so I did and got the attached logs. These are generated when I try opening the SuperSU app from launcher. Hope this helps.
[SuperSU] fifo209:
SU for lollipop 5.0

any ETA on SU for lollipop 5.0?

Thanks,
[SuperSU] RudyH246:
Alrighty, I booted into TWRP (2.7.1.0) and went to "Mount" and checked "System". Then I went back and went to Install, selected the SuperSU.zip, and flashed it. It said, "Success!". I rebooted the system. But there's still no change.

It may be worth noting that whenever I attempt to reboot the system in TWRP, it says, "No OS detected! Are you sure you want to boot to system?" And then says, "No root detected! Want to install SuperSU?" I hit Yes and No to these respectively. I tried once to have TWRP install SuperSU at that last prompt, but it had an error and didn't do anything.
[SuperSU] neolovich:
Fairphone 2

Android 5.1 Stock

SuperSU 2.46 and 2.66 Beta

I had phh's SuperUser installed and removed it. Nothing changes.

At the moment i've only the possibility to update 'in-app' and this doesn't work. Flashed SuperSU 2.66 also with Team Win Recovery, doesnt work.

My root Acces isn't affected. When i install phh's SuperUser it works and i can use Root Explorer, Titanium Backup etc.

The command "su -v" brings following: 17 me.phh.superuser cm-su subind suinit

Here you can find the logfile. I hope it is the right one.

Maybe someone can help me? Thanks for your time.
[SuperSU] pentruexperiment:
I have gt-i9192 with rooted cuanogenmode13. SuperSu fails to update its binary :what:. Any ideas?
[SuperSU] indestructible master:
j
[SuperSU] indestructible master:
o
[SuperSU] indestructible master:
h
[SuperSU] waheedzaman1998:
I'm not using any recovery or custom ROM and still my su can't upgrade
[SuperSU] waheedzaman1998:
Can anyone help me with it!! Please
[SuperSU] indestructible master:
p
[SuperSU] yuri76:
problem. I did flash through recovery but stops the boot. s6 galaxy edge with carhdrom by carotix
[SuperSU] tjordan707:
Did you get an answer?

Did you get an answer to this?

Having very similar issues.

- Tim
[SuperSU] Evaveer:
Update your supersu binary using .zip file with the help of TWRP or CWM or any custom recovery
[SuperSU] vorlon77:
This is what I did and it worked for me on my Canadian phone

- Exact device model

Samsung Galaxy S5 SM-G900W8 Rogers Canada

- Exact firmware version

Firmware 5.1.1 Released October 15, 2015

I have the exact link but I can't post the URL as a new user

G900W8VLU1COI4

- Exact Android version

Android 5.1.1

I figured it out eventually, here is what I had to do:

- First root with CF Autoroot, check and confirm that root works (root checker)

- Download the latest beta of SuperSU, for me it was 2.66, put the zip file on your SD card

- Next use the same process (ODIN) to flash TWRP recovery, now you will have TWRP as an option when booting to recovery

- Hold power / volume up to boot into recovery again, now you will have TWRP

- I think the option was install ZIP within TWRP, use that and browse to your 2.66 SuperSU zip file, install it.

Now you should be able to boot up and SuperSU should work. A couple other notes:

- SuperSU does not work well if you have a screen overlay app like bluelight filter or twighlight, just turn them off and SuperSU popups will work properly

- There is still an issue with CF Autoroot, it relates to "a race to load" scenario where sometimes a part of android loads before the root loads and you loose root. I think we have to wait until the chainfire guys figure that out. The result is that sometimes root doesn't work and I reboot and it comes back.
[SuperSU] MaE_sTrO:
i'm having troubles updating binary .

HTC Desire 816 A5_UL android 5.0.2 , latest Supersu version, i had CWM now i flashed twrp recovery same issues i can't update binary, when i press the normal phone reboots, and if i choose CWM/TWRP it reboots to recovery and i can see "done proccessing zip file" but when it reboots the update msg shows again , i also tried to reflash through twrp nothing seems to work.
[SuperSU] ayet1:
i have updating my binary cam you help my i already root my asus zenfon 4.5c

Can you help me i have problems to updating binary my emil ayet1983@gmil.com
[SuperSU] Ch3vr0n:
I suggest you read the first post again. A lot more info is needed such as logs, what you rooted with, errors,...

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] 1990.anmol:
cant update SU Binary. its failing

i am using Sony Xperia J ST26i

Andriod jellybean 4.1.2

what to do???
[SuperSU] J4jks:
Struck on Boot logo(Moto G 2014)

I have flashed SuperSU 2.67 via TWRP3.0 on Moto G 2014 (Marshmallow) then it struck on boot logo:crying:
[SuperSU] JohnSmit268:
Do you use a custom ROM?
[SuperSU] kh34d:
Me too, I'm on marshmallow and I can't install binaries??
[SuperSU] JohnSmit268:
Try flashing the latest stable version or latest beta version through twrp or cwm.
[SuperSU] TechMillz93:
im having update failers, with supersu 2.67. when i do it normally
[SuperSU] kh34d:
I tried, but no use
[SuperSU] spainter:
First try completely unrooting from the SU app and reflash 2.67 from TWRP. If that doesn't work then you will have to reflash boot and \system then reflash SU
[SuperSU] wallah:
Hello,

I have Meizu pro 5 with flyme 5, have the root but not yet custom recovery. When a try the latest version of the Supersu 2.67 I have update failed. I know that if I flash with the custom recovery thus will work, but for this phone no custom recovery yet. How I can update binary in the other way?

Thank you in advance

Meizu pro 5 V5.1.3.0G + xposed
[SuperSU] Sirocco.ukr.lviv:
supersu 2.64 and supersu 2.67

TWRP 2.8.7.0 and TWRP 3.0.0.0

no root. SU binary is missing after reboot.

twrp log:

http://hastebin.com/ipojiviyeg.diff
[SuperSU] J4jks:
No No I'm on Stock only .
[SuperSU] tcntad:
Thanks alot. I did this by using v2.67 instead. Seems to be working:)
[SuperSU] shegeloaf:
I have trouble. On note 4 n910c Erobote 13.4 rom' twrp 3.0.0.0 Kernel UK and Suemax.

I used the zip flahes for 2.67 but phone never boots into rom. Please help.
[SuperSU] Arjun322:
Super SU shows black screen

After installing superSU, I tried to update it and showed error to update. I tried rerooting from PhilZ (CWM) Recovery and the super SU started showing blank/black screen. I tried clearing data and the app showed

"Unable to update binary please manually reroot. Consult your device forms"

I'm on a Galaxy Note (GT-N7000) international version.

My OS version is: 5.1.1 (CM 12.1 BUILD 20160109 UNOFFICIAL N7000)

Root is enabled but the checker shows no root available
[SuperSU] Dharmik Sanghvi:
Why su binary install failled. ?? I'm new user tell pls solve it how to update SU binary. ..??
[SuperSU] kingersj1:
CM13 unofficial Quark

SuperSu version 2.65

normal method failed,

twrp 3.0.0

now stuck in CM boot animation after reboot
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION],

I got bootloop after flashing supersu 2.65 version zip using official twrp 3.0.0-0 recovery for titan motoG 2014 xt1068

What I did-

-flashed supersu 2.65 version zip,

-wiped ART/delvick cache and caches

-rebooted

-stuck on Motorola boot logo (not boot-animation)

detail device information

device model- Motorola motog 2014/ titan/ xt1068

android version- official android marshmallow 6.0

firmware version- MPB24.65-34 / 24.41.34.TITAN_RETAILDSDS.RETAILDSDSALL.EN.03 RETIN

boot.img- stock kernel

supersu version- update-supersu-v2.65-20151226141550.zip

update method tried- zip via recovery

providing kmsg log and recovery log
[SuperSU] :
I further tried to flash older beta versions of su on clean installed firmware. In that case only BETA-SuperSU-v2.62-3-20151211162651 I got working. Version 2.64 beta booted but I got so many FCS and sim cards disabled. Other betas after 2.64 gives bootloop.
[SuperSU] lazer9:
Similar situation here. Note 4 910T. Odin FULL DOK2 base latest firmware. Setup some apps, accounts, ect...

Proceeded to Odin TWRP 3.0.0-0 successfully

Had latest 2.65 Stable SuperSU at the ready on externalSD

Flashed and noted messages about not to worry if phone bootloops/reboots several times.

I am now 20 minutes later and it continues to bootloop :(

Forced back into recovery and did a Dalvik & Cache wipes 3x

Attempt to boot back to system with same results = eternal bootloop atleast 15x and counting.

Can't locate above user's mention of v2.62-3-20151211162651 and would like to try.

Any help appreciated!
[SuperSU] :
Here you go

http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
[SuperSU] lazer9:
Thanks. Had just did a google search and found it. Unfortunately damn Windows 10 for whatever reason won't recognize my Note 4 via TWRP 3.0.0-0 even when toggling "Disable/Enable MTP" in recovery.

Funny thing is, works flawlessly once booted into Android OS, even prior Roms when rooted.

My search shall continue because apparently unless the MTP feature in TWRP is broken, my device drivers are amiss. :silly:

---------- Post added at 12:38 PM ---------- Previous post was at 12:32 PM ----------

Update: Luckily I found SuperSu .Zip version 2.52 beta in one of my External SD previous lollipop Rom folders and flashed, phone is rebuilding apps now and appears to be booting. Time will tell if I actually have root or not. :cowboy:
[SuperSU] :
[MENTION=650592]lazer9[/MENTION] for me beta 2.52 requires modified boot.img to work.
[SuperSU] lazer9:
Stability back 910T Note 4 DOK2 Stock & SuperSU v2.52 beta

I don't know. Mentioned beta 2.52 has worked for me on Sammy's stock DOK2 full firmware. I know I've been on higher versions since. Why I couldn't flash and succeed w/ latest stable is a real mystery to me.

1) Maybe issue since upgrading to TWRP 3.0.0-0

2) Maybe incompatible with 910T stock DOK2

Who knows.

Brief history... I've been on many Roms on my Note 4 over the past year+ ranging from KitKat thru current Lollipop. Things became unstable for the first time ever after some flashing of different kernels and using some custom profiles & Kernel Aiuditor both also found here on XDA. In fact it was so bad, even clean re-flashing would produce random screen freezes/reboots with several buzz's (vibrations). Note: I could stream Pandora for hours straight at work with no problems, be on a phone call, yet texting, scrolling through Metal browser, Chrome, Firefox, ect... would produce mentioned issue. :confused:

Thus far on STOCK with most apps back on, along with above mentioned SuperSU version = only way I could get system to boot, all is well.

I will be testing over next few days. Making a Nandroid of course real quick. Then adding Xposed Framework by Wanam - specifically for Sammy devices. Testing some more. Then flashing desired Rom with fingers crossed :fingers-crossed:
[SuperSU] W3ND31:
same situation here, but with Thea xt1078 6.0

XT1078, Motorola Moto G 2Gen LTE Brazilian Version

24.41.34.thea_retbr_ds.retbr.en.BR retbr

Android 6.0

Super Su 2.67 Beta and 2.65 Stable

Zip Via Recovery

The zip is installed normally, but the phone won't boot. Still on bootlogo

need some modification on kernel?
[SuperSU] :
root with supersu beta 2.62 (download link) first then then after rooting u can flash 2.65 stable supersu. no need to use modified kernel now. su will itself do required modification during flashing. this what i did on titan xt1068
[SuperSU] nbi1:
play store update failure

The play store SuperSU (v2.46) fails to complete installation. It installs partially then displays a message that the binary needs to be updated. Hitting continue prompts for an installation method for the binary. As I have only the stock Lollipop 5.0.2 I choose "normal" vs. "TWRP/CWM". Then the circling "installing" status is displayed for a few seconds before the "Installation failed" message. My phone is rooted according to RootChecker and BusyBox is installed. The consequence of this failure is that apps like USB OTG Helper complain they can't find the su binary, effectively rendering them inoperable.

HW: T-Mobile LG G2 D801

SW: Lollipop 5.0.2, Build LRX22G, SW version D80130c

I'd be happy to provide any other info as needed. Thanks for your help.
[SuperSU] UpInTheAir:
Note5 SM-N920C 6.0.1

Hi [MENTION=631273]Chainfire[/MENTION]

The Note5 users would greatly appreciate your assistance.

Device: Samsung Galaxy Note5 SM-N920C (international model)

Firmware: N920CXXU2BPB6

Android version: 6.0.1

Recovery: twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar (others won't boot into recovery or fail flash)

Knox warranty void: 1

SuperSU v2.67

Device state:

Install TWRP

Wipe: system, data, cache, dalvik-cache

Flash N920CXXU2BPB6 with Odin3 v3.10.6

Boot and initial setup for start-up (skip where possible).

No apps installed or any other changes made except enable developer options and check:

a) OEM unlock is enabled

b) enable USB debugging​

Reboot into DL mode & Install TWRP again

Boot into TWRP

Flash SuperSU v2.67

recovery.log (attached)

Reboot into system

No root access from SuperSU app (no SU binary installed)

Other logs not obtainable due to "Read-only file system"

I have also attempted to force inject su into system (2.52 & 2.67) via ramdisk modifications that had worked on my 5.1.1 kernels. No luck. I patched sepolicy and tried a few other things = no luck, but I believe we stll need a “permissive” kernel for that to work. Kernel source hasn't yet been released for me to compile. . . Is it SELinux preventing root and system mount and write ? Thing is, I can create a service from init.rc for deep sleep fix (only briefly checked though), so can write to scsi sysfs. I don't think having the N9208 recovery matters here, it appears to work OK.

For further info, you can please check my post HERE, where [MENTION=3931450]dr.ketan[/MENTION] has opened a thread and trying to help users out.

Cheer,

UITA
[SuperSU] eeausli:
Sounds like the exact same problem, we got on the Galaxy S5 (g900f) with a leaked mm firmware.

Systemless root doesn't work, since /su is not created on boot and mounting doesn't since somehow we're not allowed to access the loopback devices.

wrote here about it already.

Installing SU system way does work though. But results in massive battery drain and sometimes the device freezes. Mostly when granting an app root permissions for the first time.
[SuperSU] Dougmeister:
Problem with my Galaxy S5. Posted a thread here. Sorry if that was the wrong thing to do.

Please respond at your earliest convenience as my phone is currently useless. Thanks.
[SuperSU] ob1silvia:
I have this same exact problem ,I dont have a computer to run adb commands Im having issues with rom manager not seeing my backups . I still have root . Samsung s6 edge 5.1.1 stock firmware 0j7 expose installed super su pro 205 wanted to update to 265 it will update binaries and everything but opening rom manager it lists no backup although the backup is there. Have to boot into recover twrp and recover old backup please help
[SuperSU] egingell:
You clicked PhilZ's "install root" (paraphrased) twice despite warnings not to - that's what soft-bricked you.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Dude_Virus:
I got an update via play store for supersu. It then told me binaries need to be updated which I did. Now there is a wierd issue, in 5he file manager app the internal SD card shows 0 files if root Explorer is enabled. The moment I turn off root Explorer it displays the contents. I have tried removing root permissions and granting them again. Also tried uninstalling file manager app and reinstall but no luck.

Clearing caches also do not help.

Shall I flash the supersu via twrp again and check. Root in general works fine it just the internal SD card contents are blank when explorer root access is enabled.
[SuperSU] MigoMujahid:
I've asked this question before in the cm13 thread for the gt-i9100 but no response

I used TWRP 2.8.7.0 isorec by arnab for cm12.1, and also isorec kernel TRIM cm12.1, to flash the cm13(first nightly) + gapps + supersu beta v2.67.zip

but when flashing the supersu i get this:

Installing '/external_sd/BETA-SuperSU-v2.67-20160121175247.zip'...

..

*****************

SuperSU installer

*****************

- Mounting /system, /data and rootfs

- Extracting files

- Detecting system compatibility

- System-less mode, boot image support required

- Creating image

- Mounting image

- Creating paths

- Removing old files

- Placing files

******************

Boot image patcher

******************

- Finding boot image

--- Boot image: /dev/block/mmcblk0p4

- Extracting ramdisk

--- Failure, aborting

and after rebooting there is no supersu app installed

PS: i get the same error with clean flashing and dirty flashing and with xposed and without xposed.

I'm using galaxy s2 gt-i9100, cm13, android 6.0.1, stock kernel, isorec recovery twrp 2.8.7.0 coming from cm12.1 (dirty flash)
[SuperSU] brinsleyparagao:
Moto X 2014 on CM 23/02/2015

Install via Recover twrp 3: Super Su 2.67 Beta and 2.65 Stable

Binary not updates... Try on normal mode and twrp/cwm mode
[SuperSU] MigoMujahid:
You don't get it

There's no supersu app installed, after installing it from the play store, binary needs to be updated, tried with normal and recovery not working.
[SuperSU] phaze3131:
I was on 2.46 or whatever is in the playstore, I download 2.65 and 2.67, tried flashing both on my s6 edge+ but nothing happens.
[SuperSU] Ohmster:
Dumb Question - Root MXPE

Excuse me, but I want to help someone root their new Moto X Pure Edition and am failing at the process. I am showing her the method I used for SuperSU 2.56 on my Moto X Pure and that means adb and fastboot boot.img, su.img, and superSU.2XX.

Of course it is failing, we are losing WiF, but peeking into these zips, they now appear to do *everything* and maybe do not need to flash boot.img and su.img anymore. If I am doing that and it is no longer necessary, then I am screwing this up for her.

What is the correct way to root an Moto X Pure Edition XT1575 US? Just flash the latest SuperSU in TWRP and that is all? Reboot to joy and a rooted phone?

This sounds dumb but I am missing something here. Can you help me out please? Thnx. :)

EDIT:

The roots I am looking at are here, in post #3, and I don't know what "WIP" means:

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmallow-t3219344/post64161125

Thanks for your help.

EDIT 2:

Got my answer, Work In Progress, Flash and go in TWRP! Hurray!
[SuperSU] brinsleyparagao:
I have super su intaled...

i told.

after install i try update binary, but have errors...
[SuperSU] Ohmster:
Yeah I am asking about that right now in the discussion group, here:

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page508#post65517691

Answers seem to come pretty fast in that thread so just monitor my post #5073 and when I get my answer, you will get yours as it is the same question.

I did my phone in October and now everything is different. So I am waiting on the same answer as you. We will get the right answer. :)
[SuperSU] MrTrip:
I've flashed SuperSU 2.65 on the latest Verizon Marshmallow 6.0, HTC One M9 S-OFF

It will not install SuperSU. Attached is what you requested, I am the ONLY one having this issue on the face of the planet at this moment I guess...

Before it is asked, NO I did not let TWRP do anything with Root.

- Exact device model

HTC One M9 Verizon Wireless - 3.37.605.7 Kernel 3.10.84-perf-g3391b7f

- Exact firmware version

Stock

- Exact Android version

Android 6.0

- Exact SuperSU version

Trying to install 2.65 or 2.67, any version that will work really.

- Interfering apps

No root apps installed yet

- Update methods tried

Tried flashing zip from TWRP. Was never offered to have TWRP install Root. Root is never installed no matter how many times I flash SuperSU

- What kind of root are you left with?

No root at all.

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

Cannot retrieve.

- Logs from TWRP, when updating SuperSU completely via ZIP

Attached to recovery.log

- Logs from SuperSU (very important)

I have no SuperSU running.

- Various logs (very important)

Attached sulog.txt
[SuperSU] MigoMujahid:
Don't worry you aren't the only one, all the s2 devices have this issue with cm13 (android 6.0.1)
[SuperSU] MrTrip:
Updated my post with full information and recovery.log