yashsingh1/xdaforums huggingface dataset:
[SuperSU] topgunsalemaker:
Post 5X Nexus Root Now Has SuperSU binary update issue

Model Phone: Nexus 5X

Android: 6.0.1

App: SuperSU Free (XBIN) v2.46

I used this zip file to load into device memory- SuperSU-v2.65-20151226141550.zip

Build: MMB29K

twrp-2.8.7.2-bullhead.img 15.9M was used

All of the root process seemed to go OK. However, after booting I am getting the "The SuperSU binary needs to be updated)

I am unfamiliar with most of the developer processes and platforms for Android platform up until this root process - however I can read, type, and click if given direction)

Any helpwould be appreciated.
[SuperSU] topgunsalemaker:
Unfortunately I tried load a separate version of SuperSU from TWRP and did not remove old versionand I am getting startup colors and will not proceed after that.

Is there a way to wipe and start process fresh, I can still get into TWRP recovery mode.

I'm an idot.
[SuperSU] Ch3vr0n:
Yeah it's called restoring your nandroid backup of flash the stock system & boot image.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] topgunsalemaker:
Thank you for the reply, I was able to figure it out and get back to the stock image . . . good to go. I should do one of those Nandroid back-up's next time. . . (220/221 whatever it takes?)

Is there a preferred root process using the systemless SuperSU on a LG Nexus 5X with MMB29K that does not result in the binary issue in the end?

I flashed a custom recovery with TWRP with the following:

SuperSU-v2.65-20151226141550.zip

twrp-2.8.7.2-bullhead.img
[SuperSU] accik:
Same thing

I have same thing when running my Nexus 7 2013 wifi with cm13

Binary update fails every time and flashing the beta zip causes bootloop.
[SuperSU] tcntad:
Im thinking its KNOX for me..

Flashed stockrom and tried root?
[SuperSU] accik:
I should try that yeah. The stock rom doesn't have the things I want to but we will see :)

Thanks for suggestion!
[SuperSU] tcntad:
Isnt CM13 already rooted? :)

Well root is fine (Checked with root checker)

I can even disable apps, use terminal emulator and Nobloat free.

SuperSU still doesnt work after disabling every KNOX-related app i could find.

The Xbin folder seems empty too..
[SuperSU] accik:
It is rooted but the usage is very clumsy and there isn't proper control over the apps. That's why I need it to work :confused:

Strange... I assume that you have tried the beta zip of su? It didn't work for me, neither the older ones.
[SuperSU] copsicle:
Root Problems

I own the Samsung GT-I9515 value edition with lollipop 5.0.1 on it.

I used CF-AUTOROOT to root my device.

I have SuperSU V2.46 and I had BusyBox installed after I rooted the device.

I tried updating the binary normally because I don't have CWM and all of that stuff and it failed I tried again for 3 times yet nothing.

Root is lost.

I couldn't retrieve any logs when I tried to run the commands you gave it said read only file system or something like that.

Any help would be appreciated.
[SuperSU] Marwan tarek:
It say update binary and i am trying but it says installation failed what should I do and I have the latest version 1.65 and I need super us only for busy box and xposed
[SuperSU] vorlon77:
Updating on Galaxy S5 5.1.1

Hello,

I rooted my Android 5.1.1 install using CF Autoroot, I have used this several times with previous versions of Android. This time the SuperSU app was missing, so I installed it again to restore the features. It fails to update after installation. I followed the troubleshooting steps I could find (remove potential app conflicts etc.). Here are the answers to the items you listed:

- 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

- Exact SuperSU version

2.65, I do have pro but I don't see an OTA survival mode option

- Interfering apps

I uninstalled Busybox and SecureSettings Pro to troubleshoot, they were previously installed from being rooted in the past.

- Update methods tried

In app only, not sure how to do the other methods.

Note that if you let TWRP or CWM "fix" root for you, or let them disable the firmware from flashing a new recovery (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.

I didn't use these, I did re-flash with CF Autoroot to gain root again just in case, check root app shows root is successful, once SuperSU is installed the checkroot app fails to complete (endless waiting for result)

- What kind of root are you left with?

At first root was working for some previously granted apps, after troubleshooting (uninstalling SuperSU, Busybox etc) there is no root granted by supersu working, aside from checkroot app shows successful root when SuperSU is uninstalled and ADB shell commands work.

After a failed binary update, multiple outcomes are possible:

su works from shell but no apps are working, with SuperSU installed they request, I grant, but it doesn't work, nor does updating the binaries.

- Logs from SuperSU (very important)

I have these but I can't see how to attach them and as a new users I can't post a link (I don't want to post a super long log in here, I can send separately)

- Various logs (very important)

I have these but I can't see how to attach them and as a new users I can't post a link (I don't want to post a super long log in here, I can send separately)

Thanks for looking into this, I'm happy to send additional details and welcome any troubleshooting tips. Cheers!

Adam
[SuperSU] slvrhwk:
I flashed 2.66 on HTC One M9 with Marshmallow, and the phone get stuck on htc boot animation.
[SuperSU] itline:
i flash my Nexus 5 with supersu 2.66 zip in TWRP and device got root but the supersu app warn me to update binary. but it failed!
[SuperSU] TheEarman:
I hope this is the right place to ask… When I flash Super SU Beta 2.65, the HTC One M8 gets stuck in the boot process.

My understanding was that after upgrading to Marshmallow, I should flash TWRP 2.8.7.0, then install BetaSuperSU2.65.zip from within TWRP. Am I missing a step?

I have just upgraded to Marshmallow, M60, Sense 7.0, WWE (on a DevEd M8).

When I rebooted into TWRP, it asked me if I wanted to leave the System R/O or modify it. I said to modify it. Maybe I should have left the System Read Only?

After flashing Beta-SuperSU2.65 it asked me if I wanted to install SU to root the phone before rebooting and I said NO as I had read that it can get the phone stuck in boot loop.

However, when I did reboot, it got stuck in boot mode...

I re-flashed the RUU and tried again, this time I said yes to the question in TWRP to install SU to root the phone at reboot, and I got stuck as well.

I don't think I need a systemless root right now, the old “modified system” way worked fine for me… I just redo the RUU before any upgrade. Of course I would go for Systemless if that's the way to go now.

I am wondering what I am doing wrong in the process. It had worked fine with Lollipop… I tried to find answers on the XDA site but what I find is for the M8 GPE, not Sense… Any suggestion? Thanks!
[SuperSU] slvrhwk:
They've mentioned in the instructions that when TWRP informs you about device not being rooted, do NOT install binary i.e. ignore the warning.

---------- Post added at 11:38 PM ---------- Previous post was at 11:34 PM ----------

I am facing a similar issue with my M9. I think they haven't patched boot image file for HTC phones yet, like they have for Nexus and Samsung devices. That's my assumption. Let's wait for one of the devs or senior members to confirm it.
[SuperSU] Ch3vr0n:
You assume wrong. If you would read the changelog you'd see that for the last few versions the installer does the modifying. Using a modified boot image in combo with the zip installer can CAUSE problems.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] Jon_94:
How to update file "su"

Please, I need help with the update of the binary file "su". First of all, I've to admit that I'm not so skilled in modding.

My device (a mediatek tablet MT6572, model alps B706, android version 4.4.2 KITKAT, kernel version 3.4.67 yxy@yxy-Z87P-D3#1, build ALPS.KK1.MP7.V1.22) results as "rooted", but I can't access to root permissions 'cause SuperSu doesn't work as it should. When I try to install the file su in the standard mode (as the app itself tells) the installation fails.

So, I were intentioned to install and use a CWM recovery to update this binary file from there, but I found out that to get it I need first to make a backup (and so get a file named "boot.img"). The problem is that MTKdroids tools doesn't make me do backups, 'cause I have no root permissions. In a nutshell, it's a kind of dead end. What can I do?
[SuperSU] amarnathsaha:
Supersu not getting update thats why it is not working and also not working root functionlites
[SuperSU] gem1ni:
Is it possible to deactivate the warning?

I used SuperSu 2.46 and it display on every boot in statusbar that the binary should be updatet.

But root still works and no other problems. Only the steady warning in statusbar is irritating.
[SuperSU] leizem:
Hi,

How can I update SuperSU?

I'm using CM13.
[SuperSU] TheEarman:
I was able to root properly, with proper binaries, by using the method described here: http://xdaforums.com/htc-one-m8/development/kernel-unlocked-developer-edition-t3262823. I selected the System Root, not Systemless, as I am used to that. Problem solved. Thanks!
[SuperSU] egingell:
You'll have to talk to the good people over at TWRP headquarters about that.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] tcntad:
Yup. I have tried the update/beta. It ends up in a bootloop.
[SuperSU] gem1ni:
Thanks, I thought this is the official Support Thread for the App, so the right place to ask :)
[SuperSU] kafakesq:
Stuck at bootloader unlocked screen

I've tried three different versions of SU, restoring to stock and flashing TWRP every time. The phone just gets stuck at the Warning Bootloader Unlocked screen. The phone otherwise works, but I really want the functionality of my rooted apps back!

Moto X Play Marshmallow unlocked

TWRP 2.8.7.0

SuperSU 2.66, 2.52, 2.46
[SuperSU] Ab.Shaheen:
I am using xperia z2 with 5.1.1, 264 lollypop and unlocked bootloader. I have rooted my cell with SuperSU chainfire 2.46 and its working but now I updated it by latest 2.66 flashable zip. Now nighter root is working nor SuperSU. Even it was rooted by 2.46 then also I was unable to get root permission in es file manager also can't mount my /system RW. is there any way to mount RW.. And SuperSU binary update.. Thanks in advance.. ☺
[SuperSU] Ch3vr0n:
Did you flash 2.66 over 2.46? If so you didn't follow instructions and caused any problems you are experiencing yourself.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] resrevni:
I successfully updated the latest January security update and am running systemless root, but my camera does not turn on. I simply get a black screen with camera controls.

bullhead-mdb08i-boot-systemless.zip

Any way to run systemless root and have a function camera? Anyone else seeing this behavior?
[SuperSU] Ch3vr0n:
Start by following the instructions. Don't use premodified boot images.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] newuser2016:
Can't update SuperSU binary (newbie)

Someone please help me, I'm *completely* new to this. I can't get SuperSU to work because it says "The SU binary needs to be updated, continue?" but when I say continue, another message asks whether I want to use normal or TWRP/CWM. On normal it just gets stuck, on TWRP it says no apps configured.

I have a new Xperia M2 on 5.1.1 build 18.6.A.0.175. No busybox, no other root apps just kingroot and SuperSU.

I have no clue what flashing or TWRP means so I have been fumbling around the dark. However, I did manage to unlock the bootloader and root the phone using Kingroot v.4.6.5. I have installed programmes called Flashify and TWRP Manager. Though I don't know how to use them! I downloaded a BETA-SuperSU-v2.64.zip file. I have tried doing 'flash zip' in Flashify with 'your recovery' (no idea what that is) set to CWM for this file. It seems to work but nothing has changed. I have tried the same file with install in TWRP Manager. (Again no idea whether to tick "wipe data, wipe cache, wipe Dalvik" or WTF I am doing!).

I can't get my phone to boot into Recovery mode, no matter which combination of volume up and power, volume down and power etc. I use, following instructions found online. This seemed to work previously when I was with a friend who helped me unlock the bootloader but the phone nearly got bricked and we upgraded from 4.4 using Emma to 5.1.1. Now it won't go into Recovery.

I'm absolutely at my wits end here and would pay someone $20 via Paypal to Skype with me and just get this thing working. :( Any instructions appreciated, please be gentle and make them detailed and simple.

I desperately need to get SuperSU working to run an app to keep my daughter safe on a phone I'm giving her, - this is totally genuine as you will see if you Skype me! I have tried calling local phone stores but they only fix phones, they don't do this sort of thing.

Moderators, feel free to move my message if I have posted in the wrong place etc.

Thank you very much.
[SuperSU] Ch3vr0n:
Your problem is kingroot, it uses is own binaries and locks them. Flash a custom recovery through adb. Download the latest beta and flash it in recovery, use TB to remove the kinguser app, launch superSU and update binaries, done.

If using twrp and it notifies 'not rooted, install binaries', do NOT let it do that or you risk breaking things.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] newuser2016:
Supersu binaries

Thanks so much for the reply, although for me it's a bit like reading a foreign language I'm afraid ;) So sorry but please could I have a bit more info/detail? Please bear in mind I have no computer experience whatsoever.

What does flash mean? Use flashtool to look for the file then press the flash button? What is a custom recovery and how do I get one? What is adb? Is the latest beta the zip file of supersu I found before? What is TB to remove the kinguser app please? If I get asked by twrp to install binaries I will say no, thanks so much for the good advice about that.
[SuperSU] mmonaghan34:
First of all, think of partitions kind of like different "drives" in windows. Flashing means installing new content through recovery, usually a kernel or something modifying the system partition, or overwriting a partition with the contents of a file, so flashing a custom recovery will replace the existing stock recovery with a custom one such as TWRP (Team Win Recovery Project) or CWM (Clockwork Mod), which allow you to create and restore complete system backups. Flashing a SuperSU zip is done in custom recovery, it doesn't replace the system partition. Adb stands for Android Debug Bridge, it's a command line tool which allows you to do things like open a shell and run commands on the device, reboot it, backup and restore apps or send or retrieve files to/from the device. TB means Titanium Backup, it is an app which you can use if you grant it root access to delete apps from /system, backup and restore app data.
[SuperSU] nomprenom:
cyanogem mod 13

samsung galaxy s4 mini (i9195)

cwm 6.0.5.1

i updated in cwm

i tried with super su 2.46 ou 2.52 beta

My device is stuck on the loading screen of cyanogenmod.

what can I do please ?

thanks

edit:

I fixed it by reading here http://forum.cyanogenmod.org/topic/118363-supersu-v252-boot-loop-with-cm13-rooting/

and flashing supersu 2.66
[SuperSU] newuser2016:
Hi, thanks again for trying to help. I have googled how to create a custom recovery and been struggling with this again for hours. I have tried installing Clockworkmod and asking it to download Rom but it doesn't seem to work. On the recovery setup it says Current Recovery: Team Win Recovery Project (TWRP) so I don't know if I managed to get it to make a custom recovery. I really appreciate that people have tried to explain things to me but I need simple step by step instructions unfortunately. I appreciate you are all too busy to provide these to a newbie like me.

Please, is there anyone out there who would be willing to Skype with me and talk me through this? I will pay you for your time, if it's going to take ages I can offer more than $20. Surely someone can spare an hour to help me and get paid for it?! Please?!
[SuperSU] Ch3vr0n:
You download twrp for your specific device, you start up adb, you flash the recovery through adb, done

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] saleh090682:


---------- Post added at 03:25 AM ---------- Previous post was at 03:00 AM ----------
[SuperSU] newuser2016:
"You download twrp for your specific device, you start up adb, you flash the recovery through adb, done"

So sorry, I'm still struggling, though thanks to the replies what I have to do is gradually becoming a little clearer.

I tried googling custom recovery for Xperia M2 and found a few boot images I tried. Clockwork Mod doesn't even do one for that make of phone (or any Sony's, as far as I could see). I downloaded a programme which helped me run the script and tried following instructions and it said it worked OK. But it put the phone into a loop whereby it wouldn't boot up, it just kept vibrating and going round and round. I tried with 3 different boot image files I got from different sources and nothing seemed to work. Eventually I got it in the blue screen recovery mode and tried flashing the supersu zip file but still no change and now the phone was unuseable as it was still in the booting loop. Eventually I had to reinstall 5.1.1 using Emma, so now I am back to square one.

If I can't persuade anyone to let me pay them to fix this for me, could someone please post a link to a custom recovery boot image file that works for the M2, or if not, please could someone explain why trying to do this put the phone in a reboot loop? What do I do next please?

If I can't fix this and no one will do it for me I must accept I wasted a lot of money on the Sony and buy a new phone and try again. If so, please can I have recommendations for phones which are EASY to run SuperSu on, without this ridiculously hard (for me) process of unlocking the bootloader, rooting the phone, installing a custom recovery and then opening the supersu zip to get the binaries or whatever it does.

I'm not sure who wrote supersu, and it's a great programme, but if it's so hard to get it to run, won't it become obsolete as phones get harder to 'crack'? I'd be happy to pay to support it. But maybe it's just me randomly picking a phone model it won't easily work on?

Thank you once again for your help and time, generously given.
[SuperSU] egingell:
TWRP *is* a recovery. Search for that.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] newuser2016:
Hello, I have searched twrp, read lots, tried instructions given on several sites and still can't get SuperSU to run. Please could somebody help me out by doing the following:

A: Give me the email of someone who is willing to be paid (very generously, at this point in time, as i just cant do it) to fix this

B: Please give me step by step instructions of the type a layperson could use.

C: Please suggest other phone models where its easier to get SuperSU working?

Thank you for your time.
[SuperSU] egingell:
A: No way.

B: There are tons available. Have you checked the Xperia forums?

C: Anything not made by Sony.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] yuripo:
Bootloop after unroot

Hi

I have galaxy S6 (sm-g920f). Android 5.1.1. Firmware g920fxxu3coj6. Stock Samsung firmware.

I didn't install any interfering apps. The installation of SuperSu 2.65 have been done with CF auto root via odin.

The systemless root process worked very good.

When i try to unroot via the application (just after the root process), everything works fine.

The problem happens when i root the device (with cf auto root) and the try to remount the system partition as RW.

After executing the command "mount -o rw,remount /system" from adb with su, unrooting from SuperSu app and rebooting. The device is stacked in a boot-loop. I have tried to wipe dalvik cache and cache partition but it keeps boot-looping.

Is there ant fix for that?

Thank you!
[SuperSU] Heraku:
I just installed adb.

with the apolo kernel I was not able to use the adb logcat command

I just flashed a dorimanx kernel and was able to extract adb logcat to a txt file.

Please have a look, maybe you guys can help what goes wrong on startup (everything?:(:silly: )
[SuperSU] power2top:
Issues in 2.14

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

I installed 2.14 from playstore after I already reported that 2.13 did not work for me due to the notorious binary update issue. Then I did the same stuff you mentioned and quoting you:

As given by you above, I selected 'No' for both disable recovery rom and 'fix' permission/root access in CWM and on phone start, I dont see 'Su binary needs to be updated' error BUT when I go to SuperSu app, the app fails with the error message: 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'

What to do now? Anything I did wrong in the above install process?
[SuperSU] Chainfire:
In case of issues, always flash the latest version (which is now 2.16) and see if that works.
[SuperSU] Frank Westlake:
The logcat might be sufficient for Chainfire to see what the problem is but if you have time we can try to get more information.

The debug.zip failed for you in Recovery and I can't tell why from here, but if you have ADB working you could try the script "collect.cmd" from your Windows or Linux machine. Extract it from debug.2.0.zip onto your computer and try as much of this procedure as you can:

1. Boot device into Recovery.

2. Connect it to the computer.

3. Install SuperSU 2.16.

4. Run "collect.cmd" on the computer.

5. Boot device into Android system.

6. Run SuperSU.

7. Run "collect.cmd" on the computer.

Steps 4 and 7 both write a data archive to your computer in the directory with "collect.cmd", send those archives to Chainfire. These data archives can be merged if you wish. The first will have a sub-directory named "adb_recovery" and the second "adb_device". Just copy "adb_device" to the same place as "adb_recovery", or you could just send both archives separately.

This debug system is experimental and I have essentially only two types of devices to test it with, so if it fails for your device it is not likely a fault of that device.

Frank
[SuperSU] zaChicken:
Excuse for my noob thing, i put the icon on invisible and now i dont know how to launch supersu to disable it :))
[SuperSU] the_rooter:
Correct me if I am wrong anyone but if you flash a latest update su zip in custom recovery wouldn't this fix the issue?
[SuperSU] sndrdg:
http://xdaforums.com/showthread.php?p=53186275
[SuperSU] power2top:
Hi [MENTION=631273]Chainfire[/MENTION],

As per your suggestion, tried "flashing" 2.16 but I face the same problem. In CWM, I selected 'No' for Disable Flash recovery and Fix root. On phone start, when I try to start SuperSU app, I get the message 'Su binary not installed.....This is a problem!'. So 2.16 is yet not working. 2.01 is working flawlessly so something has gone wrong since then.
[SuperSU] Chainfire:
Then provide all the logs as requested in the first post of this thread.
[SuperSU] power2top:
Please find attached. I tried ZIP Flash method via CWM SuperSU 2.16. The commands shown in the first post for TWRP/CWM etc did not work(perhaps they pertain only in case of TWRP and I have CWM). Other details reg. device, android is available from my signature. I was able to successfully run the sulog commands and have attached the output with this post. Hopefully, I can get back my once healthy running SuperSu back. Please let me know incase you need any other details.
[SuperSU] Chainfire:
Hmmm, strange. Does adb shell work in CWM ? If so, try this (when booted in CWM, not Android):

adb shell
mount /system
chmod 06755 /system/xbin/su

Then reboot and see what happens.