What is the correct way to upgrade superuser? Right now I'm running the official CM 11 Nightly 2.03. The problem is, for example in Titanium Backup it gives me this,
"WARNING
Your SU binary (version "15 com.android.settings") is functional but might not work reliably on some Android 4.3+ ROMs. If you encounter any issues in TB, please try SuperSU instead."
Should I just install or flash SuperSU (chainfire) or Superuser (chains DD)? I don't know how to do it properly, I know there are risks of breaking root if not done correctly. Thanks
androidobsessed said:
What is the correct way to upgrade superuser? Right now I'm running the official CM 11 Nightly 2.03. The problem is, for example in Titanium Backup it gives me this,
"WARNING
Your SU binary (version "15 com.android.settings") is functional but might not work reliably on some Android 4.3+ ROMs. If you encounter any issues in TB, please try SuperSU instead."
Should I just install or flash SuperSU (chainfire) or Superuser (chains DD)? I don't know how to do it properly, I know there are risks of breaking root if not done correctly. Thanks
Click to expand...
Click to collapse
If you have root and the app works dont worry about it.
androidobsessed said:
What is the correct way to upgrade superuser? Right now I'm running the official CM 11 Nightly 2.03. The problem is, for example in Titanium Backup it gives me this,
"WARNING
Your SU binary (version "15 com.android.settings") is functional but might not work reliably on some Android 4.3+ ROMs. If you encounter any issues in TB, please try SuperSU instead."
Should I just install or flash SuperSU (chainfire) or Superuser (chains DD)? I don't know how to do it properly, I know there are risks of breaking root if not done correctly. Thanks
Click to expand...
Click to collapse
You can always download superSU from play store or from the xda forums and flash it with a customer restore
Sent from my HTC One using xda app-developers app
Related
I've just got round to re-rooting my X8 after having to use SEUS to restore my phone back to the stock 2.1.1 after bricking it with a theme install that went wrong and keep getting this error when trying to install BusyBox.
Root Access Denied!
BusyBox Installer was not allowed root access!
This may be an issue with Superuser, try opening Superuser and making sure that you are allowing us root access.
If you are still having an issue, please email [email protected] with details of the issue and log.
I've never encountered any problems installing BusyBox in the past. Does anyone know what the problem might be that is causing the BusyBox Installer to not allow me to install BusyBox?
Roland
Rolandh said:
I've just got round to re-rooting my X8 after having to use SEUS to restore my phone back to the stock 2.1.1 after bricking it with a theme install that went wrong and keep getting this error when trying to install BusyBox.
Root Access Denied!
BusyBox Installer was not allowed root access!
This may be an issue with Superuser, try opening Superuser and making sure that you are allowing us root access.
If you are still having an issue, please email [email protected] with details of the issue and log.
I've never encountered any problems installing BusyBox in the past. Does anyone know what the problem might be that is causing the BusyBox Installer to not allow me to install BusyBox?
Roland
Click to expand...
Click to collapse
which busybox version are u using ?
yeah... it happen to me too,, it caused by the rom[SU error-but somebody just fix it already],, wat rom u use, not every rom support newer busybox,, dont know why.. sometimes will get loop sonyericson logo,, after i updated with newer busybox, i use xcyaogengingerbread V3 for 5 a week now.. even still give random reboot[not to many],,,
We shall not install latest busybox or update it!
If we install latest busybox just change to old version 1.7.1 that should be ok.
Rolandh, you asked same thing in Development section.... Jesus! Read posts there first!
I couldnt find a solid answer, so i was looking for help. I unlocked my phone and installed TWRP. I then flashed the SuperSU and BusyBox .zip file via recovery. But when i open the SU app i get prompted to update binaries and it will crash if i attempt to do so.
I have not flashed the insecure kernel, but I was almost certain that this was not need to gain root access.
Can i get confirmation? Maybe some help too :laugh:
Questions go in Q&A
Sent from my EVO using Tapatalk 2
Same issue
dekend said:
I couldnt find a solid answer, so i was looking for help. I unlocked my phone and installed TWRP. I then flashed the SuperSU and BusyBox .zip file via recovery. But when i open the SU app i get prompted to update binaries and it will crash if i attempt to do so.
I have not flashed the insecure kernel, but I was almost certain that this was not need to gain root access.
Can i get confirmation? Maybe some help too :laugh:
Click to expand...
Click to collapse
I have this exact same issue and I AM running the insecure kernel so I don't think it is an issue of the kernel. I found that using the SuperUser app rather than SuperSU works to alleviate this problem, but now I can't figure out how to uninstall the SuperSU app. If anybody can help me with this let me know
SuperSU wont work you have to use superuser for now..i had the same mistake but when i removed everything and redid it with superuser it been working fine since
Ok, well here's an update. I installed SuperUser via the Play Store, and updated the binaries. Afterwards I reboot and uninstalled the new SuperUser app and. tested SuperSU again. It prompted me to update Binaries again, but this time it worked, and now I am working just fine.
http://www.youtube.com/watch?v=vAwfgi0suJQ&feature=youtu.be
this worked for me on the super user gaining root
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
I finally got root to work, but now some apps when requesting root re-boots my phone.
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
In regard to all fo the problems below:
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
wowens0822 said:
I finally got root to work, but now some apps when requesting root re-boots my phone.
Click to expand...
Click to collapse
theguitarhero94 said:
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
Click to expand...
Click to collapse
BigRed35m said:
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
Click to expand...
Click to collapse
eddiecanuck said:
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
Click to expand...
Click to collapse
Listen up guys I'm assuming most of you are bone stock and freshly unlocked the problem is the SuperSU APP it is stated in the OP for the unlock method and most of the root threads around here that currently the binaries we have for supersu that is flashed in recovery during the root process are not compatible with the SuperSU APP from the market. Downloading "superuser" from the market will fix all of your problems.
download this > https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=nav_result#?t=W10.
Until further notice this will be necessary. There are some people that have hacked in different binaries for their updates/roms just make sure you read OP's first before tryingto switch back to the SuperSU app.
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
eddiecanuck said:
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
Click to expand...
Click to collapse
Did you make a NAND b4 supersu app installed? Revert if so if not i recommend UKB in the development sections its a solid rom right now with lots of options. I'd say fix it now so it doesnt bite you later. Also you could try freezing in tibu then using tibu to uninstall SuperSU that is.
I did an uninstall updates for SuperSU to get it back to what was flashed, and I can uninstall Superuser. Haven't done a NAND yet but will. Looking at UKB, was going to stay stock for a while but after looking at that I probably won't.
Most likely flash it tonight, has some nice features. Thanks again for the input.
Hello guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
srv2D said:
Hello guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
Click to expand...
Click to collapse
Do you have a custom recovery installed? If not, you should. If you do, then you should be able to just install the latest zip from Chainfire to get your binaries up to date and working properly.
Install this via custom recovery (CWM or TWRP) http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
srv2D said:
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
Click to expand...
Click to collapse
UPDATE: Thank you so much! I installed this and now SuperSU works just fine, Titanium Backup works fine, and I can still use GravityBox!:laugh:
:highfive:
So, I'm just wondering if anyone can offer some insight.
I've been recently trying to get this all working with the PureNexus Rom (7.1). EDITI've isolated it to flashing Chainfire's SU app. Any ideas?
I need root for Adaway. I want literally nothing else from it but this beautiful app. Please assist!
I'm on pure nexus everything fine here
SuperSU icon doesn't appeared in app drawer but in settings
IF YOU HAVE FLASHED BS KERNEL THEN IT WILL END UP IN BOOTLOOP.
Leo7D said:
I'm on pure nexus everything fine here
SuperSU icon doesn't appeared in app drawer but in settings
IF YOU HAVE FLASHED BS KERNEL THEN IT WILL END UP IN BOOTLOOP.
Click to expand...
Click to collapse
Ah. Perhaps that's it. I will need to check.
I have been flashing the SU zip on top of the PN rom?
Edit: There's no superuser in settings.... And root checker fails.
Edit #2: Magisk is the compatible Root module for this ROM, per the PN thread here. Installed, system boots and root checks out.