yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ikarisan:
This is not working for me. If I touch outside the popup then SuperSU gets closed and when I start it again it tries to update the binary. No chance to enter the settings after dismissing the popup. :(
[SuperSU] brinsleyparagao:
!!! Failure on Boot Image Patcher !!!

Error ON >>> /dev/block/mmcblk0p33

Moto X 2014

CM13 - 22/07

TWRP v3 + Unlocked Bootloader
[SuperSU] arifxxi:
Link2sd error

After updating Binaries, Link2sd cannot install script. :(

Sorry for bad english
[SuperSU] TimSchumi:
Try to remove it's SU-permission and add it again
[SuperSU] lucadalba:
- Device model

Samsung Galaxy S5 SM-G900F

- Firmware version

G900FXXU1CPG1

Security patch: 1 July 2016

http://www.sammobile.com/firmwares/download/81072/G900FXXU1CPG1_G900FVD21CPF1_VD2/

- Android version

Android 6.0.1 Marshmallow

- SuperSU version

No SuperSU running before, trying to install SuperSU 2.76 Stable.

- Interfering apps

No one.

- Update methods tried

Trying to install SuperSU 2.76 Stable in SystemLess mode (zip says it was installing in SystemLess mode) keeping compatibility mode (BINDSYSTEMXBIN=true in /data/.supersu)

NO "TWRP fix root" tried

- What kind of root are you left with?

No root before.

- Recovery used

Official TWRP 3.0.2-2 for klte

https://dl.twrp.me/klte/twrp-3.0.2-2-klte.img.tar.html

- Logs from TWRP, when updating SuperSU completely via ZIP:

http://cloud.tapatalk.com/s/5796bc27a6874/recovery.log.zip

Hello [MENTION=631273]Chainfire[/MENTION] and thanks for all your incredible work.

Since when I'm on Marshmallow I've flashed supersu SystemLess zips without problems.

But now I've installed G900FXXU1CPG1 firmware via Odin on my S5 G900F and when I've tried to flash supersu 2.76 I got failure from supersu zip.

I noticed it when it try to patch SEPolicy but there are a lot of other errors in recovery.log ..

And obviously supersu app says supersu is not installed.

Hope this info can help.

I'm available for provide logs, provide more info, provide files and test eventual fixes.

Hope this info will help SuperSU development and obviously I hope problem will get solved[emoji4]

Thanks to everyone

lucadalba
[SuperSU] lucadalba:
[MENTION=631273]Chainfire[/MENTION]

Continuing my previous post (Here's the post) I want to say I've searched some errors by myself and I've found that a lot of errors are rm errors.. but because I've seen you check for correct script execution after every operation (if you detect uncorrect execution you break installation with failure setting CONTINUE=false) and because script never breaks for rm errors, I think they are not important or influent.

But at the end I've found that this code in your update-binary (one of the highlighted strings)

ui_print "- Patching sepolicy"

[color=blue]check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-extract /sutmp/ramdisk sepolicy /sutmp/sepolicy"

if ($CONTINUE); then
if ($PERMISSIVE); then
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.patched "permissive *"
else
LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/supolicy --file /sutmp/sepolicy /sutmp/sepolicy.patched
fi[/color]
if [ ! -f "/sutmp/sepolicy.patched" ]; then
ui_print_less "$UI_PRINT_LAST"
ui_print_always "--- Failure, aborting"
CONTINUE=false
fi
fi

Returns this error in recovery.log

- Patching sepolicy
sukernel v2.76 (ndk:armeabi) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk] ...

Saving to [/sutmp/sepolicy] ...

[color=red]error: only position independent executables (PIE) are supported.[/color]
--- Failure, aborting

I want to remember that Security Patch is latest (1 July 2016) for S5 (more info for firmware in the previous post).

Hope this additional info can help.

Thank you

lucadalba
[SuperSU] Cj7Andy:
Samsung Galaxy s6 edge + Sprint

First thanks for the time and effort [MENTION=631273]Chainfire[/MENTION] . This is my first root on a Samsung. I have an S6 edge +. Sm G928P. I used Odin and was able to PASS the root. When I open SU it works and three root checker apps say it's rooted but I cannot get any root apps to work. Most say their is a missing binary. I have tried to uninstall the root and do it again but it will not uninstall the root. I do not know where to go from here.

Im using V 2.74 SU free.

Thanks in advance for any help.

---------- Post added at 05:01 PM ---------- Previous post was at 04:38 PM ----------

I updated SU to 2.76 and it said binary needed to be updated. Did that successfully and rebooted the device. Root hiding apps won't work still. Greenify won't work either. Permission is granted but errors pop up Everytime i try to use their rooted function.
[SuperSU] Foxxxtrot:
Fail flashing SU 2.76 in Moto X Play (XT1563) [Help!]

Hi !

I have a problem when I try to install the last SU 2.76 in my Moto X Play (XT1563).

I have flash firmware "XT1563_LUX_RETAR-MvSTAR_6.0.1_MPD24.107-52_cid12_subsidy-MOVSTLA_CFC.xml" (Marshmallow 6.0.1) from (3w-github-com/motoxplay/stock)

Is the same firm for Movistar Argentina... but not is stock firmware... (lolipop 5.1)

Then Flash the last TWRP Lux 3.0.2-f3 ... So far so good.... but

when I flash the SuperSU 2.76 from TWRP the phone not boot anymore. Only stays at the start screen....

How I can solve this problem ??

Thanks !

PD: This isue was solved with SSU 2.62 ...
[SuperSU] migoblu:
Supersu will not update binary

After rooting my Samsung S4 Verizon I545 with RootKing and installing Supersu, Supersu ask for a binary update. I try normal with no luck. I downloaded the Supersu update ad tried updating through the Recovery process, with the update zip file on a SD card. That failed too. In the recovery process I get a can't verify signature error and the update install fails. What do I do?

Phone Samsung S4 Verizon Model SCH-i545

Android Version 5.0.1

Baseband version I545VRUGOF1

Build # LRX2CC.I545VRUGOF1
[SuperSU] Ch3vr0n:
Disable signature verification, you don't need it with superSU.
[SuperSU] TimSchumi:
You can't use the recovery method, as you're probably still on stock recovery, which only supports signed zip files. The update.zip from SuperSu isn't. You can try to open it with a Zip viewer, and move the su file to it's proposed place (look in MANIFESTS/com/google/android/updater-script.sh for the place where tge su file should have been extracted, or just look at the path to the su file inside ihe zip) with something like ES File Explorer (I guess you had root access with RootKing before installing SuperSu). After that, install SuperSu and the binary should update automatically. Then you can remove RootKing.

WARNING:

I am NOT responsible for a bricked Hard- and/or Software-Setup. YOU are making these changes to YOUR device, which may make your device slower or even UNUSABLE, which may be possible to recover or not. ALTHOUGH I TEST THE ADVICES BEFORE I GIVE THEM, MISTAKES CAN HAPPEN. AFTER ALL, I'M ONLY HUMAN, TOO.
[SuperSU] migoblu:
How do I disable signature verification

How do I do that? I can't find any instructions for that.
[SuperSU] Ch3vr0n:
You don't. You need to enable signature verification usually with custom recoveries like twrp. They don't have it enabled by default. If you're using a stock recovery perhaps, you'll need to flash a custom one.
[SuperSU] ldeveraux:
It sounds like you do have a stock recovery, so just flash the update zip using flashfire.
[SuperSU] Ch3vr0n:
Might not work. 1st requirement of flashfire: functional superSU or cm rom with permissive kernel.
[SuperSU] CollisionFactor:
I have SuperSU V2.65 on my T-Mobile LG H631 (stylo). I installed the zip via unofficial TWRP recovery yesterday. When I opened the app today it states that the binaries need to be updated. If I update the binaries through the play store and it fails to update will it bootloop my device or will su continue to run?
[SuperSU] Gina Baron:
I try to update afte the problem this time, the camera would nt work,close apps,usually if my phone runs out of battery,I have to recharge & then continually power & up down vol,then the flash, flashes continuously, on doing this I have to keep removing the battery, then hours later my phone may switch on, I updated on this instance SuperSU binary needs updating says reboot, then when I do phone switches off again & I have to go through the whole thing again, at the minute binary needs updating but I dare'nt do it cos my phone wil turn off umi Rome by the way,a really excellent phone otherwise. Please help
[SuperSU] migoblu:
I don't know how it happened, but I found a download (https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/) to remove KingRoot, it removed KingRoot, I rebooted and the SuperSu loaded and all is fine now.
[SuperSU] MJest:
I still can't update su binary of my samsung galaxy core 2, i've already tried the 3 methods of updating su binary like flashing the updated version thru CWM,TWRP and in the SuperSU app in normal mode. but still have root access. Sometimes it says root is not installed properly in this device and i just flash again the supersu zip so that i can get root access again.

Any suggestions please?
[SuperSU] KabalLV:
Hi, I'am failing to update SU binary. Tried flashing through TWRP, tried normal and scripted variant but it just fails. I have root because I'am able to allow root access to apps and adb through developer settings, but I can't manage to get SuperSU app working. And if I try to do scripted variant, not normal, then I even get bootloop for some reason.

Moto X2 XT1092, TWRP(twrp-3.0.2-2-victara.img), tried flashing SuperSU(UPDATE-SuperSU-v2.76-20160630161323).

Thanks.
[SuperSU] ralex76:
Hi, I can't update supersu through app. My phone is s4 mini lte with cyanogenmod cm 13 . I tried both method normal and through binary but they fail.

The second fails because phone stucks on booting ....I want to use flashfire app, but it says "root access could not be acquired ..."

How can I fix?

Thanks
[SuperSU] migoblu:
Did you root with KingRoot? I used KingRoot and I could not get the su binary to update. I used this to get rid if KingRoot: https://www.droidmen.com/remove-king...-with-supersu/ and SuperSu loaded fine with no su binary update needed.
[SuperSU] seanpc13:
Kingroot removal script works

Just ran this removal script on a StraightTalk Samsung Galaxy Core Prime SM-S820L running Android 4.4.4. It removed Kingroot version 4.9.6 just fine. No problems so far...
[SuperSU] Rommel1991:
I need help, do you have a latest verion of .inb file? to root my lenovo k900. i hope you response, thanks.
[SuperSU] magicphone:
I'm here: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip

I'm not quite sure:, how do I get the SuperSu .apk outside the Play Store? I find no clear instructions for this, I guess, basic question. Thanks.
[SuperSU] egingell:
What do you mean? The file linked is a flashable zip file, but more importantly, it's just a regular old zip file which can be opened with any old zip file browser.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] nieohl:
Hi there, I've been having problems with the Titanium Backup recently and tried some troubleshooting method such as unticking Mount namespace separation in SuperSU. They didn't work until i get to the point on updating the SuperSU from Play store. Then asked me to update the binary which i selected TWRP and it rebooted. After the installation from TWRP, it only boots to recovery. Tried turning off the phone and it still go to recovery even if i select reboot system.

Now i tried re-flashing the 'CF-Auto-Root-a7lte-a7ltexx-sma700fd.tar' via Odin3. It completed but then it's only boot looping. Sure i know it would reset multiple times but it has been more than 30mins doing like that over and over again. Tried to flash the TWRP again via Odin and wiped data/system/cache. And tried installing the Ressurection rom but it fails it gives me error "E:Error executing updater binary in zip '/external_sd/A7 Root and all/Roms/RessurectionRemix........"

Error flashing zip........

Then tried rebooting system. It said no OS installed proceed to reboot then saying device does not appeared to be rooted and asked me to install SuperSU which I did and it just restarted and still on boot loop....

Any help, please? TIA

I had no rom installed on it when I was using it. I just rooted it using the CF auto root and installed a TWRP and that was it..

I think it's China version.. Not quite sure of. A700FD it is.

Edit: I tried flashing A7000ZCU1BPB1_A7000CHC1BPB1_A7000ZCU1BPB1_HOME.tar which i downloaded from sammobile and it's just failing.
[SuperSU] magicphone:
I mean, I want to install SuperSu on my phone, I need a clean .apk file from outside the Play Store. I know .zip files, but where's the .apk? :)
[SuperSU] egingell:
Did you look in the zip file?

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] KabalLV:
Hi, I'am failing to update SU binary on Moto X 2014 xt1092. Tried flashing through TWRP, tried normal and scripted variant but it just fails. I have root because I'am able to allow root access to apps and adb through developer settings, but I can't manage to get SuperSU working. And if I try to do scripted variant, not normal, then I even get bootloop for some reason.

In logchat when flashing SuperSU, it says:

*****Boot image patcher*****

- Finding boot image

--- Boot image: /dev/block/mmcb1k0p33

- Extracting ramdisk

- Decompressing ramdisk

--- Failure, aborting

Maybe that is an indicator of something ? I don't really know.

Tried flashing UPDATE-SuperSU-v2.46.zip but after that i had bootloop and tried flashing UPDATE-SuperSU-v2.65-20151226141550.zip but it didn't work like with v2.76.

Some more info:

Moto X2 XT1092(latest victara nightly), TWRP(twrp-3.0.2-2-victara.img), tried flashing SuperSU(UPDATE-SuperSU-v2.76-20160630161323) and no custom kernel.

If need more info, just ask and I will provide.
[SuperSU] tamanaco:
I get these same messages when I try to install SuperSU 2.76 Beta zip using TWRP 3.0.2-0-fugu.img on a Nexus Player running 7.0 Nougat build NRD90M. There's still no TWRP 3.0.2-1 image for the Nexus player that I can test. Any idea as to what might be causing this error?... Thanks.

EDIT: I also just tried using the new SuperSU 2.77 Beta zip, but had the same result.

EDIT2: As suggested in the Nexus Player thread using SuperSU 2.71 Beta zip to root Nougat on the Nexus Player... WORKED!
[SuperSU] jakob_2704:
Update not working

Device model: Sony Xperia Z1 Compcat (D5503)

Firmware version/Kernel: 3.4.0-perf-gaee6e5a BuildUser@BuildHost #1

Android version: 4.4.4

Build number: 14.4.A.0.157

SuperSU version: Pro v2.76

Interfering apps: It doesn't work with or without Xposed Installer/BusyBox, I can't even install them.

Update methods tried:

Normal: It fails

TWRP/CWM: Just reboots phone

What kind of root I'm left with: Root seems to mostly still work, but it often doesn't have access to /system.

Various logs: writing to sulog.txt didn't work, but I copied it from the adb console:

pastebin,com/aDybsPUQ
[SuperSU] trulosdoulos:
When update fails it tells me how-to thru root browser. Rename su to .su move to system/xbin then i get lost. What is chmod 0777 etc. Is there a tutorial for thia? Can figure it out if someone can walk me thru. Thank you
[SuperSU] Eyrdan:
Nexus Player + Nougat installation failure

Hello! I just noticed that my Nexus Player had been updated to Nougat, and as a side-effect, I had lost root. Figured the safest way would be a fresh install, so I re-flashed stock partitions and went through the TWRP recovery and SuperSU installation steps that have always worked before. I believe this is the first time I have tried the systemless version though.

I tried the current UPDATE-SuperSU-v2.76-20160630161323.zip build, as well as the BETA-SuperSU-v2.77-20160827190633.zip version. Both failed to install in systemless with the same error, and tried them both in system-mode instead and resulted in boot loops. Between all attempts, I reflashed stock boot/system to make sure a failed install did not cause an issue.

Device: Nexus Player (fugu)

Firmware: Stock Nougat 7.0.0 (NRD90M) from developers.google.com/android/nexus/images

Android 7.0.0

SuperSU 2.76 & 2.77 (I had Pro, but right now it's uninstalled since I factory wiped when reflashing the stock images)

Interfering apps: I haven't installed anything else yet from default installation, so no BusyBox, Xposed, or anything else that could interfere

Update methods tried: As stated above, tried re-installing from fresh stock images, with TWRP (twrp-3.0.2-0-fugu.img downloaded fresh today from official TWRP)

Logs from latest attempt with 2.76 in regular system-less (can't actually create links since I am new to XDA and you need to have made at least 10 posts to link):

recovery.log: pastebin.com/dHf7C3eb

sulog.txt: pastebin.com/FcRceycX

EDIT: I have commented-out the ramdisk backup step in the install script and it appears to install fine now... so it seems it's only that step that segfaults
[SuperSU] becksterorange:
Device: LG Rebel LGL43AL

Android 5.1.1

Super SU 2.76

No interfering apps. I uninstalled everything that needed root access.

I can root my phone but whenever I try to install SuperSU binary it fails and I lose my root. Unfortunately, on this phone the stock recovery only has one option is to factory reset the phone.
[SuperSU] d8389:
http://xdaforums.com/showpost.php?p=68482690&postcount=5
[SuperSU] Ch3vr0n:
Euh no, that post should be in here, not the other way around.
[SuperSU] suk_ram:
hello guys. sry for my bad english, im from germany.

i have huawei mate 8, unlocked bootloader, rooted, kangvip custom rom, twrp.

yesterday i updated supersu via playstore to 2.78.

now when i restart my phone it tells me to update the binarys of supersu. the update is succesfull.

i restart my phone and then it want to update the binarys AGAIN. and it never stops.

can anybody help me?

much thanks.

markus:cyclops:
[SuperSU] Chewy58204:
I'm having the exact same problem with my Huawei Mediapad X2. Luckily I had a nandroid backup with 2.76 still on it. I confirmed that 2.78 was the issue when I updated through GP again. Had to restore backup again in order to not see outdated binary messages. I'm having no issue with 2.76 only with 2.78. I'm on Marshmallow KangVIP ROM along with being unlocked and rooted.
[SuperSU] suk_ram:
ok. lucky im not alone. im not an android expert, so can u perhaps help me and tell me what to do?

much thanks :highfive:
[SuperSU] ipdev:
[MENTION=6056604]Chewy58204[/MENTION] [MENTION=7703005]suk_ram[/MENTION]

You could try flashing the SuperSU-v2.78-201609011115.zip from new official thread.

http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

TWRP / FlashFire installable ZIP :

s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip

[MENTION=7679092]becksterorange[/MENTION] (edit : missed a name.)

Since you mentioned that you only have a basic / stock recovery, you might want to look into FlashFire.

https://flashfire.chainfire.eu
[SuperSU] suk_ram:
so now i flashed supersu 2.78 with flashfire. but after the phone restarted i have no supersu installed on my phone :confused: but i cant install supersu from the playstore because of the binary problem in 2.78. what to do now? why is supersu now deinstalled :laugh: ?

much thanks

markus
[SuperSU] suk_ram:
ok now i flashed supersu 2.65 via twrp and it was succesfull. but after rebooting my phone there is still no supersu app installed?!

Then i installed the supersu 2.65 apk and now i have the app installed.

but why twrp or flashfire cant install the supersu zip?

and is my system now slowed in any way?

much thanks

markus

edit: also when i flash kangvip rom it dont install supersu, but i thought kangvip rom got supersu already preinstalled?

rootchecker says my device is rooted.
[SuperSU] ipdev:
The manager (apk) is in the zip file. (/common/Superuser.apk)

If you need to install it, just make sure to pull from the same version that you flashed. (2.65, 2.76, 2.77, 2.78)

kangvip-slim-b211, was just updated a few days ago to 2.77

kangvip-slim-b357 looks to have 2.76

-Not sure if you are using either of these just an example and what I skimmed to get an idea of the rom.

Some roms that incorporate supersu, the manager (apk) is moved into the settings menu.
[SuperSU] suk_ram:
thanks for ur answer.

but why is supersu not installed when i flash it seperatly or with kingvip rom?

much thanks

markus
[SuperSU] becksterorange:
I tried using flashfire. But I can't grant it superuser access because I have no SU binary installed at all. I have rooted a LG Optimus fuel with no problem. I think That maybe the boot loader is locked on this phone and I don't know how to unlock it. Any command I put in ADB just reboots this phone. I'm at a loss. I figure I just need to wait for TWRP to make a recovery for my phone.
[SuperSU] ipdev:
Not sure. I remember mention of it in the beta thread, awhile back. I only ran into twice. (once on a stock rom, and once on a custom rom. I was playing around trying to learn about systemless.) Binary updated but I had no manager installed. What had root before the changes still worked but, I could not grant or deny new root requests. Instaing the manger (apk) worked for me.

(I now run systemless on all I can.)

FlashFire works with alot of devices. Including ones with locked bootloader and stock recovery. (I have a few.)

From your prior post :

I assumed you had 2.76 installed. FlashFire only works with cm or SuperSU.

I see you started a thead for LG Rebel. I'll continue there.
[SuperSU] suk_ram:
so thanks for ur answer.

should i change or flash anything now?

or dont change a running system?

but i still dont understand why supersu isnt installed when

i flash it with twrp? thats my big questionmark.

how does the supersu binary look like and where do i find it?

is it in system/xbin ?

Thanks for the help

markus
[SuperSU] ipdev:
With as much as you have done, I normally would reflash stock, newest rootable, and start fresh. (Reroot, flash current custom rom - gaps if needed.)

If you are happy with the way it's running - leave it. (By asking that question I assume you are not.)

If I remember right, system su is installed into.

/system/lib

/system/xbin
[SuperSU] néonaloj:
Hello,

Not an update problem here, but an installation one on a galaxy tab 4:

I succesfully installed TWRP recovery, then tried to flash superSU. At the beginning, only had Force Closed of the SU app at reboot. Now I have the "no su binaries installed, that's a problem....".

What I did : tried TWRP 2.8.7.0 official, 3.0.0.0 unofficial -> FC of SU app. TWRP 3.1.0-0 and 3.2.0-0 official did not boot (bootloop).

Then I tried an old TWRP 2.8.0.1 and this time I have the "no binaries" message.

I have flashed SuperSU 2.46, 2.56, 2.65, 2.74 systemless, 2.76, 2.77, and 2.78, always the same results.

- model : Galaxy tab 4 sm-t235

- firmware : KOT49H. T235XXU1AOD1

- Android 4.4.2

- As I said, not updating but trying to install (flash) : 2.46, 2.56, 2.65, 2.74 systemless, 2.76, 2.77, and 2.78.

- Maybe something could interfere.. The owner tried to use "Kingroot" before I got the device. I have erased all what I found but not sure all is gone...

- method : flash trough TWRP

- No root at all!

- I cannot get logs from SuperSu app, because I can only open it to get the message "no binaries installed, that's a problem...". I can only clik on "how to root"...

I cannot get TWRP logs because the device is not recognized trough adb when into recovery. Yes, the drivers are well installed ...

I do have a adb shell sulog : http://pastebin.com/KcHfYmxA

In closing, I've installed many TWRP versions. With most of them I only have a Force Close of superSU app at reboot.

With a old TWRP (2.8.0.1) I can get superSU on the device, but with the message "unfortunatly no su binaries installed, that's a problem. You'll have to root again......."

I have tried with multiple version of SU, always the same.

Can't figure out what more to do, help would be greatly appreciated! Thanks!!