Recently bought supersu premium and I want to replace superuser with supersu any ideas on how to?
From memory (which isn't very good) I'm sure I went to Setting>>Apps then cleared cache of Superuser then deleted it. installed SuperSU. and it works fine
2 options
1: using root explorer delete the superuser.apk leaving the binaries and than install SuperSU and let it update
2: install superSU than from market install superuser and than uninstall same.
issue fixed
Related
since my phone is already rooted can't super su do everything I need? Can I uninstall superuser from the apps tab without messing up my rootability?
Yeah SuperSU will do everything superuser does and better . Just make sure you install and run SuperSU before removing superuser.
Hey everyone,
This is my first post, so sorry it's a question. I'll try my best to help out in the future.
I've just rooted my Note 2 running 4.1.1 using CF-Auto Root. I installed Sterricsons Busybox installer from the Play Store and installed Busybox to system / bin.
Now the app is saying it can't uninstall Busybox. Is this something I should be worried about?
Thanks
Or another thought... would a factory reset clear the installation?
Factory reset won't do it. Leaving it installed isn't gonna hurt. Just leave it.
this is XXXDDDAAA
Ok, I'll leave it installed.
I must admit though I'm curious why this happened. This is my 5th Android phone, all of them have been rooted and had Busybox installed, but this is the first time I've not been able to uninstall.
This is common issue when you install busybox from market. You should flash busybox installer flashable zip whenever you need busybox (very few app needs busybox installed separately)and same way you can flash busybox uninstaller flashable zip to uninstall it.
Try flashing busybox uninstaller zip. As you said you have rooted with CF root, you may not have CWM so use mobile odin OR flash CWM to use busybox uninstaller flahable zip
Thanks dr.ketan, at least I know the problem wasn't due to me or my phone.
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
kroogar said:
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
Click to expand...
Click to collapse
First flash a good recovery. Personal opinion PhilZ touch---first go though the page and u can notice an super user option first do that it'll remove all root environment then install Busybox on Rails app from playstore, though i've been using TWRP since a long time coz of it's simple UI themable too but it's having binary-update script issues (root-->need busybox ---environment issues) , then u can use either on of em Superuser/SuperSu disable Superuser in CM to use SuperSU.
kroogar said:
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
Click to expand...
Click to collapse
Also try uninstalling both rebooting & reinstalling Superuser.
OffcerClancy said:
Also try uninstalling both rebooting & reinstalling Superuser.
Click to expand...
Click to collapse
are you even able to remove stock superuser that's baked into the rom?
t1.8matt said:
are you even able to remove stock superuser that's baked into the rom?
Click to expand...
Click to collapse
Can't answer categorically, but, w/ROM I am running it was listed in Settings, Apps, Downloaded, and allowed for Uninstall option.
OffcerClancy said:
Can't answer categorically, but, w/ROM I am running it was listed in Settings, Apps, Downloaded, and allowed for Uninstall option.
Click to expand...
Click to collapse
Yeah, then it can be uninstalled. But on a rom like CMetal that I'm running right now, you can't uninstall superuser like that, it's baked in which might be what the OP is dealing with. To not use the built in superuser you just flash supersu over it and the system uses that for root access and not superuser.
I'm using SuperSU on the unlocked version of the M8. S-Off ARHD. I have rooted and everything, but I seem to be hacing issues with most apps not requesting SuperSU permissions. Greenify and FX File Explorer are the only 2 that have asked for them. So far, I can't run BusyBox, Auto-hide SoftKeys and the GSam root companion because none of them will request SU permissions.
I've attempted uninstalling and reinstalling through both the play store and TWRP recovery. Any other suggestions?
ryno9100 said:
I'm using SuperSU on the unlocked version of the M8. S-Off ARHD. I have rooted and everything, but I seem to be hacing issues with most apps not requesting SuperSU permissions. Greenify and FX File Explorer are the only 2 that have asked for them. So far, I can't run BusyBox, Auto-hide SoftKeys and the GSam root companion because none of them will request SU permissions.
I've attempted uninstalling and reinstalling through both the play store and TWRP recovery. Any other suggestions?
Click to expand...
Click to collapse
have you got it to allow all in settings
jaythenut said:
have you got it to allow all in settings
Click to expand...
Click to collapse
I don't see that option in there. I'm using the free version if that matters.
ryno9100 said:
I don't see that option in there. I'm using the free version if that matters.
Click to expand...
Click to collapse
Open app then it should be in settings allow all ,deny all and ask
jaythenut said:
Open app then it should be in settings allow all ,deny all and ask
Click to expand...
Click to collapse
It's set to prompt. Still not asking for permission in apps.
Edit:
I just set it to grant, and it still won't run BusyBox or any of the other apps I mentioned. But I have SU on FX and Greenif, and can confirm both of them work. What the heck?
ryno9100 said:
It's set to prompt. Still not asking for permission in apps.
Edit:
I just set it to grant, and it still won't run BusyBox or any of the other apps I mentioned. But I have SU on FX and Greenif, and can confirm both of them work. What the heck?
Click to expand...
Click to collapse
in aroma on ARHD theres 2 supersu opinions try the 2nd one instead just dirty flash
jaythenut said:
in aroma on ARHD theres 2 supersu opinions try the 2nd one instead just dirty flash
Click to expand...
Click to collapse
I'll have to try that one later. Apparently, my work internet blocks the mirror he gives on the original thread. :/
Not sure if i should start a new thread, but I am also having problems with SuperSu pro v2.14 (chainfire) Its not asking for permissions when trying to install the drivers for the viper4android app. been trying the for days. I have an htc one max (sprint) unlocked and rooted running 4.4.2, and root checked. busy box v1.22.1 installed, using twrp recovery v2.8.0.1. Other than that its all stock. SuperSu has granted permissions for other apps, but not viper4android. I have been browsing and trying many different ways to install, even found a zip file to try and flash, but the install failed. probably cause the zip file is old. I also tried to install the viper4android xhifi and it DID ask for superuser permissions. In the process of installing drivers, it asked to choose cpu. I chose CortexAx with NEON option and it failed install and told me to check root and busybox installation . Im not a master of this kind of stuff but not a newb either, and any help with this would be greatly appreciated.
Update: got the super user to give permissions, but still couldn't get viper4android to install drivers...
S-off?
HTC One M8
Hey all,
I realize this might need a wipe, but honestly if there is a fix it will save me a few hours headache of reloading and re-configuring everything.
Currently my phone will not root properly. I'm using the latest release MTC19V. I used the Nexus Root Toolkit to upgrade without wipe from the previous version like I normally do. After upgrading, I used the root function. There were no errors, however some applications are stating SU is not present.
SuperSU thinks everything is fine. Root requests are popping up normally.
BusyBox states "the su binary was not found on your phone", even after SuperSU pops up and I grant it permission. I assume BusyBox is no longer installed.
AdAway states "su binary could not be found" after I grant permission.
Greenify gets root access fine.
Xposed is working.
Also, after it is rooted, I no longer have access to DATA services over the 2G/3G/LTE networks, there is a "!" icon by the signal bars. WiFi works fine. If I flash back to stock without wipe, everything works normally.
I have tried:
- Unroot, flash back to stock MTC19T
- Removing all apps and installs of Xposed, SuperSU, BusyBox
- Using the uninstall and clean options in SuperSU
Going to keep messing around, but if anyone can point me in the right direction to avoid a full wipe, that would be fantastic.
Thanks.
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
PiousInquisitor said:
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Tarv said:
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Click to expand...
Click to collapse
Ok, the regular ole busybox and adaway don't work with systemless root. There are additional things that need to be flashed. When I get to my computer I'll post a link to the files.
Sent from my SM-G930V using Tapatalk
---------- Post added at 05:00 PM ---------- Previous post was at 04:51 PM ----------
Flash the systemless hosts file from THIS link to get adaway working.
Try THIS busybox. If it doesnt work try THIS one.
Hi Tarv, I've given you a "thanks" because you've saved me the time of writing pretty much what you wrote regarding my Nexus 6P. I started to experience this problem yesterday. Here are some details.
Everything was working fine. All my Nexus rooting through the years has successfully been done via NRT. NRT is not the problem, as this problem began long after already being rooted and well after using it recently to update to the newest 6.01 security patch.
I think the problem might be a corruption of the Busybox installation, though I'm open to being told that I don't I have a clue of what I'm talking about. I'm referring to the applets or whatever they're called, not the installation app.
The reason I think this is because I noticed a few days ago that when I tried to update Busybox to the newest version (1.24.2 from 1.24.1) via the Busybox Pro installer by Sterickson, it indicated the installation was successful, but the version number shown as being installed was still the old one. When I looked at the directory where Busybox was installed (/su/xbin), all of the applets were zero bytes. This bugged me, so I foolishly decided to uninstall the applets via the Busybox Pro installer and then reinstall, even though a warning popped up that this might cause problems.
It was after this that I lost my data connection (LTE, HSPA, etc.). Also, as you described, the Busybox installer will no longer proceed beyond saying that the su binary can't be found. Other installers also fail, including Busybox on Rails. Most root apps work fine, but not Adaway. Otherwise, the 6P with root works as expected, including using Xposed modules.
Upon unrooting, everything goes back to normal regarding the data connection. Rooting again results in no data connection.
There's probably a method via ADB to correctly reinstall Busybox, but I don't want to do that until someone confirms this is the likely issue. Otherwise, I suspect a full reinstallation of the OS might be needed.
OK guys and gals, ideas?
Sent from my Nexus 6P using XDA Labs
Spikedude said:
I think the problem might be a corruption of the Busybox installation
Click to expand...
Click to collapse
Spikedude,
I think I was in the same boat. Before it stopped working, I too was seeing BusyBox 1.24.1 and not able to upgrade to 1.24.2. I also did an uninstall.
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
I used the other method of installing BusyBox as PiousInquisitor mentioned, and it installed properly, although it's using 1.24.1. BusyBox by Stericson still does not show it's installed.
I also think the installer from Stericson is busted and what caused this whole mess.
Tarv said:
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
Click to expand...
Click to collapse
Hey Tarv,
Thanks for the update. When you wiped the phone, what method did you use? Factory reset from within settings, or using NRT to flash stock and unroot with the "no wipe" option to preserve user data disabled?
Also, you might be right about the broken Stericson Busybox installer. Busybox on Rails looks like a good alternative. I've disabled the NRT option to install Busybox by Stericson when rooting, so I'll just install Busybox on Rails after the fact.
Sent from my Nexus 6P using XDA Labs
Spikedude said:
When you wiped the phone, what method did you use?
Click to expand...
Click to collapse
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Tarv said:
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Click to expand...
Click to collapse
Thanks Tarv,
Followed your procedure and am once again rooted and have data connectivity.
Unfortunately, installation of Busybox was not successful. Tried the BB on Rails version, but it only installs to /system/xbin, not /su/bin. As a result, the same root apps that didn't work previously still don't work. BB by Stericson pops up the success message, but then indicates BB is not installed.
So almost back to square one. I'll try going back to stock and rerooting using NRT again, but this time enable BB installation as part of the rooting process. Maybe...
UPDATE:
First, I may have spoken too soon about BB on Rails not working. I based that on root mode of ES File Explorer not working properly, but that might be an ES problem. Play Store reviews are also complaining about the ES root problem. So maybe installation of BB to /system on systemless root is ok?
I wiped and rebooted with NRT, and allowed it to install BB by Stericson. This worked fine, allowing installation of 1.24.2 of BB to the /su/xbin directory. Originally it indicated /su/bin, and that the "cat" file was missing (whatever), but after reinstalling to xbin a couple times and some restarts it all looks normal. Adaway works, full data connectivity works, etc. Trying to flip the root mode switch in ES pops up an error, but I can still explore root, so no big deal (I'm using Solid Explorer more anyway).