yashsingh1/xdaforums huggingface dataset:
[SuperSU] ipdev:
You may just want to start from scratch.

If you have a backup with KingUser installed, restore and try this.

http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Worked for me on few different devices, then updated SuperSU.

(I normally update su by flashing the zip with FlashFire.)

Or restore stock from :

Samsung Kies (SmartSwitch) / flash stock rom with odin. (Reboot as normal is fine on stock rom.)

- Using stock rom, you will need to flash twrp .tar (md5) with odin. DO NOT reboot system. Make sure to boot into recovery (twrp) first and install su.

Samsung Galaxy Note 4 Exynos 3g (tre3gxx)

https://twrp.me/devices/samsunggalaxynote4exynos3g.html

Samsung Galaxy Note 4 Exynos LTE (treltexx)

https://twrp.me/devices/samsunggalaxynote4exynoslte.html
[SuperSU] néonaloj:
Thank you very much for your input!

As for KingRoot, the owner of the tab never got superuser rights with this method, so it doesn't help.. but thanks!

As for the stock rom, the problem is that it's not my tab and, at the moment, the owner doesn't want to loose his data. So I can't flash it.

But I do know the method of not rebooting directly, but the problem here is well the su binaries that are not installed correctly!

As I said, I can have multiple recoveries versions to be installed on the device, only with the "old" 2.8.0.1 does the superSU app to be installed, with that binaries problem... Any other idea??

Thanks!
[SuperSU] ipdev:
Some. ;)

Unfortunately I haven't gotten them to work yet. (Trying on my stock T230NU)

(I have no problems flashing on T230 but, I am trying alternative methods.)
[SuperSU] néonaloj:
Lol, thanks anyway!

So I finally managed to install CM13 on this tab, root is included, so far all seems to go well.

Thanks again for your help! Maybe next time... :)
[SuperSU] nyitharkyaw:
my root error.help me
[SuperSU] egingell:
What do you expect anybody to do without any useful information from you?

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] pgeraldes:
Hi can someone help i have a teclast x 98 plus 3g a6c9 with android_5.1_mirek190_v3.0 rom but when trying to update the binaries fails.

Can someone help, thanks
[SuperSU] rabby38:
- Device model

Samsung Galaxy Grand 2 SM-G7102

- Firmware version

Custom Rom

http://xdaforums.com/galaxy-grand-2/development/rom-adityarom-v3-0-t3387388

- Android version

Android 5.1.1

- SuperSU version

No SuperSU running before, trying to install SuperSU 2.65 and 2.78

- Interfering apps

Busybox 1.24.1( flashable.zip not app)

- Update methods tried

zip via recovery and update normal via app

NO "TWRP fix root" tried

- What kind of root are you left with?

No root before. (it's not pre-rooted rom)

- Recovery used

TWRP 3.0.0.0 (unofficial)

http://xdaforums.com/galaxy-grand-2/orig-development/recovery-twrp-2-8-6-0-touch-recovery-t3107535

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

see it below

Logs from Supersu

i don't know where it is. someone help me

plz [MENTION=631273]Chainfire[/MENTION] sir help me to fix root

Thanks to everyone
[SuperSU] Mr.MEX:
[MENTION=631273]Chainfire[/MENTION]

Hi, I'm a developer Nitrogen OS based on AOSP 7. I have a problem that I can not solve, the SU is eternal boot and system-less is not what I am it, I can not be integrated into the ROM su, is traversed each time to flash over . What is the reason? When sewn the system then calls the eternal loading without any logs, probably via UART, you can learn what's going on, but I do not have such equipment, please help!
[SuperSU] amageek:
I am getting problems while updating SuperSu from 2.67 to latest 2.78. Here are the specs:

Mobile : Huawei P8 Lite

Model: ALE-L21

Build: ALE-L21C432B574

Firmware: Sokkoban's Deodexed B574 with rooted and zipaligned http://huaweip8lite.blogspot.com/2016/07/custom-romtwrpemui-40p8-lite-ale.html

Android: Android 6.0 Marshmallow

Busybox: Yes, installed

Xposed: Yes, v 85.1

Thank you..

Note: Sokkoban's Deodexed B574 already came with SuperSu v 2.76, but I wiped/formatted it and get it again with SuperSu v2.67
[SuperSU] Wordzperfekt:
I got this error but luckily I still had the. Tar file on my comp and I just reflashed the root file and was able to get back in ( unknown software not authorized by att has been installed on this phone. PLEASE turn phone off and go to your nearest att store for help

---------- Post added at 06:00 AM ---------- Previous post was at 05:47 AM ----------

When I'm able to post pics I have the error pic

Thanks

---------- Post added at 06:01 AM ---------- Previous post was at 06:00 AM ----------

G930a att variant running Qualcomm with echoe rom

---------- Post added at 06:34 AM ---------- Previous post was at 06:01 AM ----------

Device:g930a

Processor:Qualcomm

Rom: echoe rom

Busybox pro: 1.24

Super Su pro: 2.78

Root method: Odin by Prince modified

OK I got it to work finally. Sorry guys I didn't realize I had current version already.. I didn't have updated Busybox
[SuperSU] -Duir-:
Can't install >2.74-2

It's not really an issue with updating, as I'm trying to clean install, but this is the only support thread I've found and my post (and others with this issue) in the now closed SuperSU thread started by chainfire went unanswered.

I am unable to install any version of SuperSU as systemless above 2.74-2, that is the most recent version that will work. The installer fails due to a segmentation fault while backing up the ramdisk. Though the log makes it appear to just dump the entire contents of "init.rc" which is actually causing the script to abort.

My Device: HTC One M8 (M8_UL_CA) fully converted to GPe.

FW: 5.07.1700.15

TWRP: 3.0.2-0

Android Version: 6.0 (July 2016 patches)

SuperSU Version: 2.76, 2.77, 2.78, 2.78 SR1 (log from 2.78 SR1 is what's attached).

Interfering Apps: None

Methods tried: ZIP via recovery

Left with: NO ROOT

Logs: Only logs available are from TWRP as SuperSU never installs itself (see attached).

For what it's worth, it will install successfully in /system mode, but that method is useless for me.
[SuperSU] cicuye:
Okay, here's where I'm at. I found a Galaxy S3, SCH I535, on Swappa which the owner had not allowed to update from what must have been the original Jelly Bean 4.2.2 or lower. Verizon is the carrier, so it has the I535OYUDNE1 build. He was running CM 12 (Android 5.0.1) on it with TWRP recovery. I downloaded and flashed CM13 on it with the accompanying gapps package. I went into settings and allowed adb and app root access in developer options, but jrummy's root checker app didn't recognize that as a working root. I downloaded busy box, installed it and then chainfire's superuser app, which needed the binary updated. I believe installing busy box got me rooted, which jrummy's app then recognized as such. I got on google and found chainfire's latest updating file, SR1-SuperSU-v2.78-SR1-2016091512031.zip, which I downloaded and flashed with twrp and found after booting successfully updated the su binary. So this is the first time I've flashed CM13, gotten root and been able to update the superuser binary. CM13, rooted, runs real crisp and clean with all the Marshmallow features. Hope this helps.
[SuperSU] Pagn93:
Binary Update Boot Loop

I do apologize for the lack of info in this post, I am just looking for some guidance here. My wife and I both have Kyocera Hydro Icon C6730 from Boost. Sadly there are no Rom images nor any way to flash a recovery that I could find. I was able to root them using KingRoot and flash Super SU (I don't remember how exactly at this point). I have never had any issues with any rooted application until my wife thought her SU binary update was just another update and hit the first option to flash using twrp/CWM rather than normal. Now her phone is stuck in a bootloop that just gets past the android logo then shows Andy attempting to apply a flash for about 1.5 seconds before it reboots.

I have tried to enter the stock recovery, update, drain the power, and even ADB (which doesn't even register a connection). It just continuously loops until I pull the battery, no other access is available. Do any of you have any suggestions as to what to try now? Thanks for your time.
[SuperSU] ZaKaRia OuH:
Hi all.

i have a white nexus 5 32 Gb version.

lately,i've flashed Lattest version of twrp 3.0.2.0,and flashed supersu.zip

then,flashed a nougat Rom 7.0 by santhosh Lattest build 19092016 NRD90U.

it's working fine except some two lil problems(slow charging,and video play back stutter).

then again,flashed supersu through recovery,and unstalled busybox and xposed installer.

busybox asked me to disable an option which has to do with scanning supersu,i confirmed it,then my phone rebooted and figured out that i lost root access as supersu says "No Su binary is installed and supersu cannot instal it.

i tried flashing supersu.zip again through recovery. it flashed succesfully but it doesn't show in the app drawer,then installed root checker which says ''no root access''.

i tried with kingroot,nexus toolkit root but to my avail.

i uninstalled busybox and xposed though.

help me re-root my nexus again please.
[SuperSU] d4nvjpl0ng4n:
What is my problem and how can I fix it? :crying:

thank you
[SuperSU] ZaKaRia OuH:
what's your problem dude.

i can help you i have fixed my problem with supersu :D
[SuperSU] d4nvjpl0ng4n:
I would like to use supersu + suhide to play pokemon GO but when I flash superSU, I can not pass SafetyNet (see picture below)

When I check root with Root checker, it shows:

But when I check with Root validator, it shows:

Could you help me??
[SuperSU] ultrawin:
help

after failing to update,i cant install anything on my device.It kept showing insufficient storage even though i have enough space. I'm using samsung GT-p3100
[SuperSU] ameel:
Device: Zenfone 2 ZE551ML

CPU: x86

Android: 6.0.1 MM

Issue: Does not boot to system, and instead boots to recovery.

Fix: Patch Zenfone 2 boot signature to boot.img (signature file in attached zip) using additional command in install script:

cat $BIN/zf2_6_sig >> /sutmp/boot.img
[SuperSU] -Duir-:
Still having this issue - unable to clean install ANY version of SuperSU above 2.74-2. Flashing any version of SuperSU over 2.74-2 in TWRP results in the stock boot.img being restored and the installer crashing in the same spot.

Any help with this would be appreciated.

NOTE: My recovery.log can be found attached to my quoted post.

EDIT: Updated post because updating SuperSU isn't an option, appear to need clean to install 2.78 SR1 to use suhide.
[SuperSU] egingell:
As with every single version of SuperSU, you can pull the apk out of the zip and install it like any other app not downloaded from the Play Store.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] -Duir-:
Yeah, I was just thinking that after posting. I remembered the same thing happening when trying to flash 2.76 but that I could do 2.74-2 and then update via Play store. It still doesn't explain/fix the original problem, but it does get around it.
[SuperSU] -Duir-:
Turns out this method doesn't work. I need 2.78 SR1 to be able to use suhide, but suhide doesn't work using the method of installing 2.74-2 and then installing the apk and updating the binary. I'm guessing it requires a clean install of 2.78, which I am unable to do. So, back to my original problem.
[SuperSU] justjr:
Moto G1 XT1034 - CM13 stock kernel

Zip via recovery (only way to install systemless mode?)

System mode work. Systemless keep asking to upgrade binary.
[SuperSU] vinzz123:
Xiaomi MI3W AOSP android 7.0

ZeurionX v2.5 nougat kernel

i recently installed android 7 aosp. i have supersu in my 6.1 before but now its gone in 7.0

tried flashing through twrp (supersu 2.78 stable)

edit : nvm 2.52 worked like charm
[SuperSU] - Conax -:
Samsung S3 LTE (I9305) Android 6.01 ResurrectionRemix v5.7.4-20160920 superSU binary

Phone: Samsung S3 LTE (I9305)

OS: Android 6.01 ResurrectionRemix v5.7.4-20160920

Recovery: TWRP-3.0.0-1

superSU Version: SR1-SuperSU-v2.78-SR1

I flashed superSU via TWRP recovery and after first boot it was running fine. My Firewall (AFWall+) which needs root access was running fine so first it intends that there werent any problems. To get Pokemon Go to run (that was my main target) I installed Magisk v7 (the tutorial says its neccessary for xposed framework and suhide) so I installed/flashed (also via twrp recovery) Magisk v7 and phh-superuser-magisk-r259 and after that the trouble with superSU began. When I open superSU I'm always getting the message that I'm missing some binary file and when I try to install (superSU offers me that option) it doesn't work. I also installed "Root Checker Basic" and the app is telling me that I haven't any root access also my Firewall (AFWall+) is telling me that I haven't any root privileges. I guess (I'm very new in this kind of stuff so maybe I'm wrong) that I've started a conflict between superSU and a other installed "rooting app" - normaly my custom rom is offering me root access (I have the option to activate it what I'm normaly doing). Problem is that for Pokemon GO it seems that it's only working with superSU (all tutorials on the internet a telling me you have to install superSU and magisk and xposed and suhide but sadly non of these tutorials I found are going into detail and explaining why this and that is neccessary).

What did I wrong and how can a possible solution look like?

Sorry for my bad english I'm from Germany.

Thanks in advance.
[SuperSU] Ch3vr0n:
The problem is your phh and magisk. They must be locking the su binaries. You'll have to ask them. And for the record, you do NOT need magisk or phh for suhide. The last magisk free version is linked in the suhide topic op.
[SuperSU] - Conax -:
[MENTION=1754043]Ch3vr0n[/MENTION]

Thank you very much. I found a solution to get rid of phhs superuser than I was uninstalling superSU and after that I installed superSU again. Result is phhs superuser module in magisk is removed (sadly magisk is still there I take a look tomorrow how I can remove this also) and the good thing is superSU is running again and it works great with AFWall+ - so in general superSU should be a great solution. So thanks for your great help. There is just one thing I'm wondering my custom rom (resurrectionremix) has in general root support but now superSU is offering that root support (or should I better say superSU is managing the root permissions) what happens with the old "root handler" which is build in my custom rom (I mean they are all build on cyanogenmod and they are offering in general their own "root handler")?

When I install suhide is there anything else I need that newest Pokemon GO Version is running?

Thanks in advance and thanks to the great community for offering this kind of software - rooting my phone was one of my best decisions I don't wanna miss AdAway or AFWall+ anymore.
[SuperSU] Ch3vr0n:
Afaik superSU takes over root handling even on cm based Rom's. As var as Pogo goes, suhide alone currently isn't enough. safetyNet detects it. Some claim success with 'root toggle' and a certain command that needs to be done through terminal as a temp patch but I'll wait on a full fix from chainfire.
[SuperSU] cseven7:
Update failure

Device

Digiland DL718M

Firmware

Stock

Build Number LMY471 release-keys

Custom Build Version - ALPS.L1.MP8.V2_HCN8127.M_P15

Kernel Version 3.10.72

Android Version

5.1

SuperSu Version

SuperSu Free v2.78

Interfering Apps

Kingroot

busybox

Update Methods

In-app Normal

TWRP and CWM not available for device

Root

Nothing seems to have changed at all

logcat.txt

E/WindowManager(16638):	at eu.chainfire.supersu.Installer$2.a(Unknown Source)

E/WindowManager(16638):	at eu.chainfire.supersu.Installer$2.a(Unknown Source)
[SuperSU] Ch3vr0n:
Your problem is with KingRoot. It locks the binaries that SuperSU can't update them. Remove KingRoot
[SuperSU] cseven7:
Well that puts me in a bind because SuperSU needs root and KingRoot is the only thing I have found that will root the Digiland.
[SuperSU] Ch3vr0n:
Once you're rooted just flash a custom recovery. There are scripts that can replace that thing with SuperSU.
[SuperSU] neo_mat:
cannot boot into android miui

Cannot boot into android MIUI 8

- Exact device model

LG nexus 5 32G

carrier b&y France

- Exact firmware version

MIUI 8 6.10.20 from official team http://en.miui.com/download-232.html

Direct link

http://bigota.d.miui.com/6.10.20/miui_Nexus5_6.10.20_e15261db99_6.0.zip

model number: AOSP on HammerHead

Kernel version 3.4.0-g2aa165e

build number MRA58K

- Exact Android version

Android version 6.0 MRA58K

- Exact SuperSU version

SR1-SuperSU-v2.78-SR1-20160915123031.zip

- Interfering apps

none, just install the rom

- Update methods tried

zip in recovery:

boot TWRP 3.0.2.0

wipe /system

wipe /data exept sdcard

install miui ROM

boot miui is ok

boot and reinstall TWRP 3.0.2.0 (miui install it own recovery)

echo SYSTEMLESS=true > /data/.supersu

install SR1-SuperSU-v2.78-SR1-20160915123031.zip

unable to boot stuck at first MI android screen

- What kind of root are you left with?

unable to boot normaly

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

not applicable unable to boot into android

- Logs from TWRP, when updating SuperSU completely via ZIP

see SR1.txt

- Logs from SuperSU (very important)

not applicable

- Various logs (very important)

see sulog.txt

Thanks sorry for my bad english and comprehension.
[SuperSU] d4nvjpl0ng4n:
I am using HTC one M9 SPRINT (himawhl) - Firmware 3.41.651.4 - Android 6.0.1 - super su 2.65.

Using the ROM http://xdaforums.com/one-m9/development/rom-s-team-s4-1-m9-android-6-0-1-t3388123

It is rooted already when I flash this ROM.

error: I cannot update to ver. 2.78 via TWRP as well as update binary after updating GUI from CHplay.

How can I update it to ver 2.78?
[SuperSU] Barzoul:
Huawei P9 lite + 2.78 SR2 => Ramdisk error

Hello !

My device is a Huawei P9 Lite VNS-L31, with Emui 4.1.1 (tried on 4.1 too) a (****) system based on Android 6.0.

I use TWRP 3.0.2-0 and when I flash 2.78 SR2 in systemless mode all the installation is good but at the last line => "Creating ramdisk backup => Error, aborting" => The SuperSU isn't installed and doesn't work at all :/

Could you help me please ?

Thanks in advance !
[SuperSU] militiaOfDeath:
Not exactly an update failure, but just curious. Atm I'm running v2.78 which I flashed in TWRP. Yet, whenever I reboot my phone I get a message about the binaries needing to be updated to the newest version at every single boot. If I accept and let the app try to update it fails and tells me I should update in a different manner. Is there any "solution" to this? It should be noted that this doesn't pose any problem for me at all; it's just a notification at boot and when entering the app, which I can just ignore. Root and everything else works as expected.

Some info:

Sony Z5 compact (E5823)

Android v6.0.1, security patch level April 1. 2016

Kernel: 3.10..84-perf-gf1cfa5f

Build number: 32.2.A.0.253

SuperSU Pro v2.78 installed (flashed via TWRP), o other superuser app installed.

Otherwise only Xposed (v3.0 alpha 4 of the app, v86 of the framework)
[SuperSU] :
I had a similar issue after uninstalling magisk.

I ended up doing a factory reset.

I'm guessing there was left over files that prevented supersu from installing even when i flashed uninstall magisk and uninstalled suhide and supersu. Rather then hunt for the files i did a reset.

After the reset everything was fine.
[SuperSU] Mike_68:
Update failure

I'm currently running CM 13 6.0.1 on my OnePlus and my phone became unrooted. Not sure if one my rooted apps updated and messed up the root. I downloaded and reflashed SuperSU 2.78 (and it appeared to flash without an issue). All seemed to work well but when I rebooted my phone, I noticed SuperSU was not installed and root checker confirmed that I was not rooted.

I tried to reflash and atill nothing! Has anyone ever come across this issue? If so, what can I do to fix this?

- Exact device model

OnePlus One

- Exact firmware version

CM 13

- Exact Android version

Android 6.0.1

- Exact SuperSU version

2.78

- Interfering apps (I have uninstalled them all in hopes of making it work)

- Xposed - removed framework and uninstalled

- BusyBox -uninstalled the busybox

- greenify (uninstalled)

- SDMaid (uninstalled)

- Root Checker (still installed

- Update methods tried

- Installed zip via TWRP 3.0.2-0

- What kind of root are you left with?

- Root is lost. Apps cannot get root anymore, you cannot get root using "su" from an adb shell, etc

- SuperSU states "SU binary is not installed and SuperSU cannot install it, there is a problem!"

If there is nothing I can do, I will do a clean factory reset.
[SuperSU] Zaparl:
Hi! I have reported a malfunction in SIM cards derived from updating the binaries. It is not that SuperSU is malfunctioning but causing the problem. That's why I didn't post it here first. In case you consider it a proper post I appreciate if somebody could check it out. Here's the original link. Thanks!

http://xdaforums.com/apps/supersu/supersu-binaries-update-disables-sim-t3501765
[SuperSU] Claps1775:
I have installed Computerfreek274_MM_1.0 Android Stock 6.0.1 rom today. Let it settle and finish restoring all my apps. Only 35. I installed the supersu with twrp. 3.0.2-0-mod_03 2.78 and would stick at M logo screen. Found out I need the 2.76 super su. I had to wipe both cache and reinstalled Computerfreek274_MM_1.0 Android Stock 6.0.1 to get my phone to work. When I installed supersu 2.76, I have to same out come. Phone sticks in M logo screen. Also, phone will shut off. I have my phone in twrp on the charger as it is low. Love qi-wireless charging. I did not install the BHB27 v200-8-M kernel. But, I am leaning that I need to since CFs mm rom is that base rom. Once phone is charged above 80%. I will flash the BHB27 v200-8-M kernel and then Supersur.
[SuperSU] CaptainPhantom:
I tried updating my SuperSU via the Play Store app today. I have a OnePlus One with the latest TWRP and CM 14.1 (Android 7.1), and it was already rooted with an older SuperSU. I chose the option to reboot update with TWRP. It seemed to work, but my phone was unable to boot beyond that point. Like the poster above me, I also had to reflash the latest CM nightly and clear all caches to get the phone to boot again.
[SuperSU] onetwoselekta:
I have the same problem
[SuperSU] magicphone:
Seriously, I didn't expect to look into all directories to search for where the .apk file is hidden. :) For me, the user, it would be logical to search for it in the 'arm' directory for my phone, your different logic may put it in the 'common' directory. But since you are the developer, I, as a user don't have access to your logic.

Hint: I understand proper documentation is not widespread in the Linux community (Android is Linux), only BSD folks care deeply about these things, but how about a hint for your users - in the 1st sticky post, or on your download page, you can write something like this: 'hey users, you are looking for the .apk file, you don't have to open every directory and guess where we put it, go straight to the 'common' directory, there it is what you are looking for.'

Thanks, I truly appreciate your work, by the way, this was meant to be an small, but important improvement idea with a positive tone.
[SuperSU] Giallograle:
Tricky to access Settings when the device won't boot past recovery....
[SuperSU] sonyvn123:
After update SuperSU, my phone is stuck at logo sony.

My phone is Sony Acro S. Waiting for your help...
[SuperSU] zzzhead:
Closed
[SuperSU] 64erbaz:
Hallo, I have the same problem, same phone but build 32.2.A.0.305, Supersu Pro 2.79 and always fails with the update of the binary. Do you already have a solution?

Thanks.
[SuperSU] BainStain:
Mine did the exact same thing :(