yashsingh1/xdaforums huggingface dataset:
[SuperSU] giannid99:
hello everyone.

After i install from recovery superSU.zip when i turn the phone i don't find the app,why?

i tried to install it from app airdroid,but when i open it says me "executable SU is not present,.SuperSu can't install it.This is a problem". What must I do? please help me
[SuperSU] nicolap8:
[MENTION=7376958]bearr[/MENTION]: missing something!

I just installed beta 2.71, no go.

If an app try to get su permission the SuperSU shows the common dialog but it seems that the su daemon doesn't get back the info, waiting for the timeout.
[SuperSU] DirkStorck:
I can't confirm that. I have just grated two log apps SuperSu access.

Gesendet von meinem SM-G900F mit Tapatalk
[SuperSU] Aadarsh_003:
I can't update binary of my SuperSU app neither I'm able to uninstall it. Please, help me. I use Huawei Honor Holly which runs on android 4.4.2. Made in China. SuperSU PRO v2.65. Yes, survival mode is on.
[SuperSU] Spartacus500:
[MENTION=631273]Chainfire[/MENTION]

Hello, on my Galaxy S4 I9505 4.4.2 the most current version 2.66 Beta, from 2.67 to 2.71 I had a problem with the update binary files is there a solution to this problem ? This is my log cat :
[SuperSU] avicohh:
Hi [MENTION=631273]Chainfire[/MENTION]

I'm trying to make a pre-rooted firmware for Galaxy J1 Mini (J105H), by repacking the system.img with the SuperSU binaries.

I used the last stable version (2.65), and I followed the comments in the update-binary file.

The device running android 5.1.1 version, and he has armv7 cpu.

Here is what I did.

Unpack and mount the system.img under linux.

Copy the files from the folders common and armv7 to the right places.

Run this script I made to set the permissions and the SELinux context to the new files, change the app_process, and create the symlinks. (I run it from inside the system folder)

#!/sbin/sh
cp bin/sh xbin/sugote-mksh
rm bin/app_process
mv bin/app_process32 bin/app_process32_original
cp bin/app_process32_original bin/app_process_init
ln -s /system/xbin/daemonsu bin/app_process
ln -s /system/xbin/daemonsu bin/app_process32
ln -s /system/etc/install-recovery.sh bin/install-recovery.sh

chmod 755 app/SuperSU
chmod 644 app/SuperSU/SuperSU.apk
chmod 755 bin/.ext
chmod 755 bin/.ext/.su
chmod 755 bin/app_process32_original
chmod 755 bin/app_process_init
chown 0.2000 bin/app_process32_original
chown 0:2000 bin/app_process32_original
chown 0.2000 bin/app_process_init
chown 0:2000 bin/app_process_init
chmod 755 etc/install-recovery.sh
chmod 644 lib/libsupol.so
chmod 755 xbin/daemonsu
chmod 755 xbin/su
chmod 755 xbin/sugote
chmod 755 xbin/sugote-mksh
chmod 755 xbin/supolicy

chcon u:object_r:system_file:s0 app/SuperSU
chcon u:object_r:system_file:s0 app/SuperSU/SuperSU.apk
chcon u:object_r:system_file:s0 bin/.ext
chcon u:object_r:system_file:s0 bin/.ext/.su
chcon -h u:object_r:system_file:s0 bin/app_process
chcon -h u:object_r:system_file:s0 bin/app_process32
chcon -h u:object_r:system_file:s0 bin/install-recovery.sh
chcon u:object_r:zygote_exec:s0 bin/app_process32_original
chcon u:object_r:system_file:s0 bin/app_process_init
chcon u:object_r:system_file:s0 etc/install-recovery.sh
chcon u:object_r:system_file:s0 lib/libsupol.so
chcon u:object_r:system_file:s0 xbin/daemonsu
chcon u:object_r:system_file:s0 xbin/su
chcon u:object_r:zygote_exec:s0 xbin/sugote
chcon u:object_r:system_file:s0 xbin/sugote-mksh
chcon u:object_r:system_file:s0 xbin/supolicy

Finally, I repack the the partition to a new system.img, make a tar and flash it by Odin.

For some reason after I flash the new system.img the device stuck in boot loop.

I double checked the new img by unpack it again, and all the permissions and SELinux context are exactlly as they should be.

After some testing It turned out that the problem is in the app_process, I did it all without touching the app_process and the device work's fine but with no root of course.

Anyone know what cause the problem?

What I'm missing here?

I would very appreciate the help.

Thanks.

Update:

Problem solved.

I use this method of patching the sepolicy and repack the boot.img and now the bootloop is gone :)

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[SuperSU] blcpl:
I'm having issues with my G pad (8.3, V500 model), running Android 6.0.1_r17 (the rom is the one from March 25 from here: http://xdaforums.com/lg-g-pad-83/development/rom-android-6-0-marshmallow-20151028-t3235794).

After installing TWRP (version 3.0.2-0) and flashing the rom, I've installed (via TWRP) the stable version of Supersu (UPDATE-SuperSU-v2.65-20151226141550). I had the app in the app drawer, but no root access, and launching the app just told me that it was not installed and I could do nothing about it. Outside of that, the device was fully functional.

I went back into TWRP and flashed the latest version (BETA-SuperSU-v2.71-20160331103524.zip). After that, I got stuck at boot with a message saying "Secure booting error! Cause: boot certification verify". I could still access recovery, and the recovery itself works just fine, but I could not boot into android proper. A wipe has had no success, I had to reflash the entire rom to boot.

So... what happened? Why did it happen? How am I supposed to get root?

update: after reconfiguring the device (and making a backup in TWRP, this time), I tried again with the stable version, and had the same issue, being stuck at boot. The installer did not display any errors during the flashing (it wrote something about a systemless install and patching the boot image, which I suppose is the cause of the issue), but I don't really know.

update 2: systemless install doesn't work, had to install an older version of SuperSu.
[SuperSU] sketchdesigns:
cant update binary on galaxy s5

I've updated the binary a few times since I first rooted the device but just recently failed about a week ago,

I'm currently using...

samsung galaxy s5 (sm-g900f) rooted

and running exodus (5.1-20151231) rom

on android version android-5.1.1_r24

kernel version 3.4.0-cynaogenmod-g71044b3

I've tried updating as normal through the app (which has worked at least once before)

and also through the recovery option (twrp)

I havent tried installing from a zip in recovery as I couldnt find a link to the file (if there is one)

I believe I'm using v2.71 of SuperSU

I'm not exactly new to rooting and such though I'm by no means any expert so I should be able to follow anything with instructions and should presume that I've tried the most "obvious" steps already

P.S. by the way SuperSU still seems to be working pretty much fine (as in allowing access to apps) as far as I can tell other than the annoyance of the constant "needs to be updated" message

EDIT: I also have busybox installed and have tried a few solutions that have worked in the past, managed to get superSU v2.65 installed, said to update the binary.... which competed this time and is not asking me to update now, May be working properly now
[SuperSU] michael64child:
failure report

Samsung s6(SM_G9250)

ANDROID 5.1.1 SDK22

carrier: CHINA TELECOM

version of SuperSU:2.71

intervening apps: idoneapps

advanced signal status

fqrouter

shadowsocks

methods both tried(dont even have an idea of TWRP )

SU still works, but requiring for the update of binary
[SuperSU] zammer159:
hi bro can u tell me pls wer i can find the pre- rooted stock rom for sm-j105h my phone stuck on gmail account and i tried every thing to remove the frp lock so i want to root sm-105h then try reset frp with any tool.
[SuperSU] Ch3vr0n:
Wrong place to ask. This topic is for superSU update issues, not to ask for device prerooted roms. Ask in your device forum

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] kumaranwade:
im using moto e2 xt1521 when i tried to flash supersu 2.62.3 through twrp it completed and while reboot it stucks at blue android m logo not going further still animation shows... im newbie any help apreciated .. I need this devices for my college purpose please help me to recover it ... Baseband changed to not available on this process
[SuperSU] akbaryahya:
*Device model: Advan T1K

*Firmware Version:

Baseband: 1.4.16.0

Karnel: 3.10.17

CPU: arm7 *broadcom?

*Android 4.4.2

*SuperSU version: Free Last Update (BETA-SuperSU-v2.49)

*Interfering apps:

- Apps2Sd

- BusyBox

*Update/Install methods: Clockworkmod V6.0.3.2 no official , flash zip

*What kind of root are you left with?

Root worked but did not able to update binary, because the folder system only can read not write, I also tried kingroot but it did not work

I tried to change file system.img so the system folder can write, but it does not work.

I was very frustrated to find ways to make system folder can write, help me :/

*Current file that I change:

boot.img -> default.prop

recovery.img -> default.prop

boot.img -> fstab.java

Log:
[SuperSU] crazyrain:
some of supersu features does not work with cm13

Hi,

I am try to use mobileanjian app (anjian.com) in cm13, mobileanjian need root to execute virtual key press, but it does not work with supersu and cm13, it works with supersu and cm12.

I tried for oneplus one and Lenovo k30-E, same for both of them.

And the builtin root of cm13 works with mobileanjian .

Any help for it ?
[SuperSU] Ch3vr0n:
Not a superSU problem, tell the developer to update its app and not use hardcoded SU paths
[SuperSU] gdaver:
I recently updated my samsung gt-i9300(international) to:

Android 6.0.1 - CyanogenMod 13.0 - 20160428-Nightly version

and then flashed open_gapps-arm-6.0-super-20160428.zip

I use philz_touch_6.48.4 for flashing.

flashed BETA-SuperSU-v2.71-20160331103524.zip

Set up my accounts and and compatible 4.4.4 applications back.

Everything seemed fine at first but I saw I cant reach Titanium Backup, so checked SU .

Error : "There is no SU binary installed..."

I used phone for a day. No errors or halting.

Checked the new rom and found root access was disabled under developer options. Opened them for both Apps and ADB.

Restarted.

SU halted on a black screen.

SU is not responding and RootChecker can not get access to verify root info.

Taught that may be because of the BETA release and flashed back to stable version:

UPDATE-SuperSU-v2.65-20151226141550.zip

After this,

Nearly all apps running background stopped.

SU is not responding and RootChecker can not get access to verify root info.

I disabled the Root access rebooted

SU asks for permission I granted it.

Root Checker and SU are listed under apps but error info There is no SU binary installed still persists. And also titanium backup could not acquire root privilages.

Problem may be because of the rom or SU. But probably SuperSU v2.65 is not working on 6.0.1.

Is there a known issue?

I may give further information to developers as asked. except mondays and tuesdays
[SuperSU] shinestones:
Unable to root my stock sc-03e japan s3 on firmware JSS15J.SC03EOMUBOG5

Please help me to root the galaxy s3 japan stock firmware latest JSS15J.SC03EOMUBOG5 already tried your current cf auto root for sc-03e but not working. Please help me sir. Need to urgent root my phone.
[SuperSU] Ch3vr0n:
This topic is for SuperSU update failures, not rooting help. You need to use your device forum.
[SuperSU] buatlo:
hi all,

I was try flash supersu 2.65 or 2.71 always failed with:

1. TWRP 3.0

2. Fastboot >>> failed (image is not a boot image)

kindly need your help guys
[SuperSU] seacowx:
>please define "failed" while using TWRP.

>you cannot flash using adb, superSU is in .zip ext. NOT .img ext.

*update your twrp to latest ver. or stable ver. that matched your device or the OS you are currently on. then flash superSU.zip using your updated twrp.

**or you can try using adb sideload to install superSU
[SuperSU] manuelsaborio:
SuperSu does not update

Hello, today I saw a message mention that binaries must be updated. I have tried in normal way, with TWRP, but it does not update.

My phone is Lenovo K3 Note, Vibeui V3.1-1614 Lemonade
[SuperSU] Ch3vr0n:
How did you initially root and with what?
[SuperSU] manuelsaborio:
It was rooted using TWRP from Recovery, making wipe. It was the only way to get it rooted.
[SuperSU] Ch3vr0n:
So you didn't use kingroot or something? Try flashing the 2.72 beta zip.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] manuelsaborio:
Kingroot didn't worked, so I had to use TWRP and install ROM and SuperSu
[SuperSU] Ch3vr0n:
Try zip
[SuperSU] manuelsaborio:
Where may I download it?

Any instructions?
[SuperSU] Ch3vr0n:
The superSU topic, instructions? Boot into custom recovery, flash zip, done.
[SuperSU] manuelsaborio:
What about if I try with KingRoot instead og SuperSu. Could it works?
[SuperSU] Ch3vr0n:
No, flash the zip. King creates its own su app, binaries and locks them.
[SuperSU] seacowx:
flash the superSU 2.65 zip. it's stable, no update binaries problem whatsoever.

look into http://xdaforums.com/showthread.php?t=1538053
[SuperSU] Ch3vr0n:
Bad advise, don't say that. The latest 2.72 is recommended.
[SuperSU] seacowx:
excuse me? it meant for people who facing updating binaries problem after installed 2.71/2.72 BETA. v2.65 works for all. latest BETA 2.72 does not. *don't say that. and don't gt it wrong way
[SuperSU] manuelsaborio:
I just checked the version I have now, it is 2.72
[SuperSU] Ch3vr0n:
There is no info on what zip he used until now. It's still the recommended one, it contains numerous fixes and improvements over 2.65.

[MENTION=7465382]manuelsaborio[/MENTION] but did you flash the zip? That's the question, my guess would be twrp messed something up initially. You could try a full unroot from within superSU, then boot into twrp and flash the latest beta.
[SuperSU] seacowx:
good, if you don't have any problem with that so keep going. if you were facing one, then go for 2.65. simply as that.
[SuperSU] manuelsaborio:
OK, it was not easy. It is necessary to go into Supersu and unistall it, laterinstall it again from Play or thru recovery. I did by recovery, but after restart, it is necessary to update it from googlePlay. Ch3vron and seacowx, thank you very much for your Help. I appreciate this too much.
[SuperSU] Ch3vr0n:
Just glad we could help. Now that superSU has control over the binaries you shouldn't have any more issues.
[SuperSU] blue whale:
Hello

I have a nook tablet 16gb on android 6 under AOSP by amaces and twp 3.0.2 with the log of the failure to install supersu 2.72 here

http://pastebin.com/RR2kdVfZ

version 2.65 fails too.

Before using the zip and twrp, I tried to go through the application from the store and it fails because the application could not find some binaries.

see here for the ROM
[SuperSU] blue whale:
Note that CM13 has indeed the root functioning, but rooting comes with the ROM: I just need to tap 7 times the build number and then rooting is activated.
[SuperSU] egingell:
That's Developer Options. I don't think it's the same as root.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] blue whale:
Indeed, but they manage to gather dev options+root to speed up the process of getting root

In AOSP, once you activate dev options, there is no superuser by default and I cannot install it...
[SuperSU] shyyist1114:
Su binary failure

Pls can you help,

I'm rooted on Samsung Galaxy S7 edge international

Variant, on android marshmallow 6.0.1, everything was

Working fine but lately when I open Supersu I get this error

Saying ( there in no Su binary install, and supersu Can not

Install so I need to manually re-root)

I use rootchecker too see if my device is still rooted

But is saying I have no root

Pls can you help me solve this problem

( SM G935F ) thanks
[SuperSU] rxk:
I have notice the same problem today.

I lost root on my G935F (XSA). I tried uninstall and reinstalling SuperSU but the message "no Su binary install, and supersu Can not

Install so I need to manually re-root" when it try to run SuperSU.

I tried flashing AutoCFroot but still no luck.

I need help.
[SuperSU] BartVCD:
already a known problem

source: https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
[SuperSU] shyyist1114:
Su binary failure

So pls should I wait for the the update from chainfire

Or do a hard reset, plus is it not going to course further

Problems for me if I wait any longer,

And pls how do you do a hard reset anyway?

Thanks

---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------

So pls should I wait for the the update from chainfire

Or do a hard reset, plus is it not going to course further

Problems for me if I wait any longer,

And pls how do you do a hard reset anyway?

Thanks
[SuperSU] BartVCD:
chainfiire says "a few days" if you can wait a few days you better should wait, there is a good chance that samsung updates your phone again, so hard reset your phone is not a long term solution
[SuperSU] shyyist1114:
OK, i have tried to flash superuser v2.72 beta with twrp to see if the problem will be resolve, but no luck

so maybe i have to wait for the update from chainfire

anyway thanks for your help

am still digging around for a solution
[SuperSU] BartVCD:
I have the same problem with my s7, if you find a "workaround" it would be nice if you inform us ;)
[SuperSU] gouster3:
I want to integrate SuperSU to my private rom. I have installed latest SuperSU beta using flashable zip. It works good.

Then i backed up this files from my system:

And used in my ROM installer.

After i wiped system and reinstalled rom with this copyred files su command is working in terminal and all apps working too. But when i open SuperSU app i get message: su binary need to be updated.

So, is there some file that i forgot to copy?

XPERIA NEO (MT15i) | 4.1.B.0.587 (mod) | ICS 4.0.4 | armv7 | BETA-SuperSU-v2.72-20160510112018.zip
[SuperSU] unknowN-:
Coming from 2.46 -> 2.65 or higher I get a secure boot error on vs985...

Using CM13 if I use 2.46 I just get stuck at boot animation...

edit: changed SELinux to Permissive before installing 2.65 via Play Store and all is well...
[SuperSU] drpvp:
kindle fire, rooted supertools,

supersu failed and now googleplay dont work?
[SuperSU] Ch3vr0n:
superSU has no impact on play services whatsoever.
[SuperSU] drpvp:
just seems wierd it worked before

i instal it before kingroot tbh and worked, then in do kingroot and instal supersu and it fails, and play services wont update cant get on play says ''authentication is requred please log in'' but i am lohged in, cleared cashe everything

also another note my kindle wont turn off, power button>turn off kindle>ok>nothing

p.s. just noticed that google play worked BEFORE i did the downgrade form 5.1.2.1 to 5.1.2

just reset and restred unroot stock and gplay doesnt work (it did before i downgraded)

im about to try root again

ok so i reformated all, rerooted and supersu worked!! kingroot is gone!!!! supersu is superuser,

BUT google play stil aint flippin workin
[SuperSU] Vorridor:
Make sure your date and time are correct, clear cache, clear data, reset app pref's, clear app defaults. Those are some of the most common fixes for play store. Hope it helps.
[SuperSU] Giallograle:
Stuck in recovery

I flashed TWRP 3.0.2-0 and CM-13 snapshot 2016-04-19, Android 6.0.1, on my OnePlus One A0001 . I'm a Pro user but only installed the free app from Play Store which asked me to update the SuperSU binary although it didn't reboot the phone.

As I'd lost root I reflashed the SuperSU v2.65 zip from TWRP, which seemed fine, but afterwards I could only boot into recovery, not the OS. I can boot into the bootloader using the Vol-Up + Power keys; flashing TWRP from fastboot and then CM-13 from recovery gets me running again, without root.

I've attached last_log from TWRP and the sulog Android logs.

I'd appreciate any suggestions for getting SuperSU working again.
[SuperSU] phyerz:
update binary failure what ever install directly or update from v2.49

### Exact device model

Meizu Note2 China

### Exact firmware version

My device use the official edition of Meizu belowed:

download.meizu.com/Firmware/Flyme/m2_note/5.6.5.24/cn_beta/20160520092347/13b00a0c/update.zip

### Exact Android version

Meizu flyme 5.6.5.24. Based on Android 5.1

### Exact SuperSU version

supersu V2.65 and above. I'm not sure how about 2.5X, at lease V2.49 no problem in my case.

### Interfering apps

- Meizu flyme buildin root access management, when supersu apk installed and permited root access by it. It would be transparent to user.

### Update methods tried

in app normal

### What kind of root are you left with?

- when I run 'su -v'; '2.73 SUPERSU' showed.(when I installed V2.74 apk)

- Logs from SuperSU (very important)

Nothing found filter by 'installer' in logcat.txt.

And other info about supersu belowed:

```

I/WindowManager( 965): Gaining focus: Window{247990a u0 eu.chainfire.supersu/eu.chainfire.supersu.MainActivity-Material}

I/WindowManager( 965): Losing focus: Window{19f765e5 u0 SuperSU EXITING}

I/WindowManager( 965): Gaining focus: Window{14bd7b61 u0 eu.chainfire.supersu/eu.chainfire.supersu.MainActivity-Material}

```

### Various logs (very important)

The sulog.txt outputed is [here]webresource.gz.bcebos.com/supersu/document/log/sulog.txt
[SuperSU] darkobas:
http://pastebin.com/hd5m6Q2C

i get dd: writing '/dev/block/mmcblk0p34': No space left on device

so i am stuck in bootloop.... any suggestions ?
[SuperSU] RR-99:
IGNORE PLEASE - I finally got to the bottom of this

I have a Note 4 SM-N910F, Android 6.0.1

Installed CF-Auto-Root-trlte-trltexx-smn910f using Odin

When I run SuperSU, there is no mention of SU binary.

APPS and LOGS are both blank.

Phone appears unchanged.

I installed SuperSU Pro v 2.74, this makes no difference.

What have I done wrong please?
[SuperSU] bjbirch:
Try going into settings>about phone>tap on build number til developer options are enabled>go to developer options,you should find root access options,enable root from any of the options listed.This method of enabling root access is in nearly every cyanogen ROM
[SuperSU] Mano1122:
Sir i have rooted my anroid samsung gt i8262 from this application FRAMAROOT but supersu instaal after rebot my devise but then open supersu Apps and click on continue and then alxo click on normal but he says to me instalation failed whats the reason plx solved my issue sir i am very thankfull to you.....!!
[SuperSU] bjbirch:
Download SuperSU beta from this thread: http://xdaforums.com/showthread.php?t=1538053

Then either flash it with TWRP,CWM or Philz recovery or boot into stock recovery and try apply update from SD card>download to install SuperSU to system
[SuperSU] coolnessMonster:
Using Samsung Galaxy S3:

http://xdaforums.com/galaxy-s3/orig...lies-i9300-t3272811/post67282828#post67282828

Unable to update su binary using SuperSu with nightly 20160610. Did a clean formatted install. Couldn't update using SuperSU through TWRP either. Phone was stuck in infinite booting (even after a factory reset)

Seems others are having this problem as well. Let me know if you need log dumps or anything and I'll figure out how to get those.
[SuperSU] mash4077fan:
So yesterday I got this message about superuser could not update binary and I lost root. Now all the changes I made with xposed are still there but some of the apps I use will not work cause they need root access. I want to know if there is a way to update binary without using custom recovery as I still dont think I can install custom recovery. I did try to odin cfautoroot again but that did not work. If anyone has ideas or suggestions I would appreciate it. If I were to convert the superuser update zip file to a tar file could i use odin to flash it.
[SuperSU] bjbirch:
You could try downloading SuperSU zip file from this XDA thread:http://xdaforums.com/showthread.php?t=1538053

Then boot into stock recovery, go to install update from SD card,go to download folder,choose SuperSU zip file press OK button and see if this restores root
[SuperSU] mash4077fan:
Ok I am in stock recovery and when I click go to sdcard to install update I get this error message on the bottom, update from external storage is disabled. How do I enable it, if I even can
[SuperSU] bjbirch:
You will have to move the SuperSU zip file to internal SD card( labeled as sdcard1) use a file manager like es file manager to do so
[SuperSU] mash4077fan:
I did put it there and it wont show in recovery, i got same error. Thanks anyways