Develop Bugs

Superuser vs SuperSU

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.

Android Pay on a ROM w/ Root

Anyone get it working? I'm on viper tried disabling SuperSU, root cloak, and no device check. With no luck.

As far as I know there isn't a workaround yet. Maybe the nexus forums might be the best place to search for now
Sent from my HTC One_M8 using Tapatalk

Mine works with root. Try uninstalling and then disable in superSU. Install the app again, and go through the process to get it up and running. Then re enable root.

Funkquito said:
Mine works with root. Try uninstalling and then disable in superSU. Install the app again, and go through the process to get it up and running. Then re enable root.
Click to expand...
Click to collapse
Thanks for the suggestion but unfortunately it did not work.

rcicu said:
Thanks for the suggestion but unfortunately it did not work.
Click to expand...
Click to collapse
For me, running GPE, I couldn't get it to work until I uninstalled the xposed apk, dirty flashed my rom to remove the xposed service (probably could flash the xposed uninstaller zip), disabled supersu, and wiped the data/cache on the pay app.

henderjr said:
For me, running GPE, I couldn't get it to work until I uninstalled the xposed apk, dirty flashed my rom to remove the xposed service (probably could flash the xposed uninstaller zip), disabled supersu, and wiped the data/cache on the pay app.
Click to expand...
Click to collapse
I'll give that a shot later tonight.
Thanks

well that didn't work

Below are the experiments tried to add a card to android pay and results corresponding
I have an M8 with s-off supercid, and ATT latest firmware (4.28.502.1)
1. CM/AOSP Based - Not working. On some ROMS not even able to install the app (Device is not compatible) - Fail
2. Sense 7 ROMS - Able to install the APP but not working (Google is unable to verify the hardware or software.........) - Fail
3. GPE - Working with the unmodified GPe ROM (http://forum.xda-developers.com/showthread.php?t=2706441) with superuser disabled in the superuser app - Pass
Didn't worked with modified GPe ROM with cm features (http://forum.xda-developers.com/htc-one-m8/development/rom-m8-gpe-01232015-t3010825) -Fail
4. Sense 6 ROMS - Working on ROM MAXIMUS HD 11.0 (http://forum.xda-developers.com/showthread.php?t=2695706) and Skydragon 40.1 (http://forum.xda-developers.com/showthread.php?t=2700571) with super user disabled within the super user app - pass
On this ROM (Maximus HD), I tried the RootCloak with superuser enabled in the superuser app - Fail , superuser disabled with xposed installed - Fail

Can't get Android Pay working on my HTC One M8 GPE, haven't got root and never have had it.
Andoid Pay crashes when I click the plus logo to add a card.

Viper4Android Help

I've been trying to get Viper4Android driver installed but it keeps failing.
I've tested CM11 and Stock but no go when I hit install driver. I'm guessing it may have something to do with SE Linux as I have to set it to permissive but haven't had any luck with trying to change it as apps do not detect it.
Just looking to see if anyone else had any luck with the app on their Fire Phone?

I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here, no need to change anything...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
I had to use SELinuxModeChanger on other devices (they used "enforcing") because they didn't offer a setting to change the SELinux mode.

Bingo Bronson said:
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
Click to expand...
Click to collapse
I've reviewed the following thread
http://forum.xda-developers.com/showthread.php?t=2191223
I've tested 2.4.0.1 & 2.3.4.0 but can't install the driver. I have BusyBox Pro installed and running and reviewed the logs in SuperSU but i have no idea whats going on when I try the driver install.
Screenshot of Super SU Log: http://postimg.org/image/wdhvthr73/
I am currently back on CM-11 if you have any steps for me to try...

Kerrona said:
I have BusyBox Pro installed and running [...] I am currently back on CM-11 if you have any steps for me to try...
Click to expand...
Click to collapse
Hm, well that's interesting... I also used Stericson's busybox (non pro) and it worked right away... (I also used "ViPER4Android_FX_v2401_A4.x-A6.x.apk")
Maybe reinstall busybox... why isn't it able to find the "toolbox" / why is it calling the path with failsafe?
I see you have some security / privacy / permission tools running... can't really vouch for a hassle free install in such an environment.
You could try to flash this zip from safestrap recovery, this worked for me on other devices and the driver is already integrated, no need for a separate install from within the app.

This has something to do with superSU Binaries updated from normal method, if you have updated super su from playstore then you have to wipe the system partition reflash the rom and latest superSU zip. Otherwise you can flash the pre-build V4a zip as suggested above.

Thanks guys.
I got the driver installed and enabled now with the flash version.
Will probably wipe and start fresh and try the apk again.

Root not working, stock Nexus 5x using Root Toolkit, trying to avoid a wipe

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).

Uninstall Root on Cm13?

I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks

Isn't root enabled via settings? Maybe turn it off in the settings or reflash and don't enable root?

I tried that but the system is still seen as rooted
Sent from my SGH-T999 using XDA-Developers mobile app

Shack70 said:
I want to use the system less root so I can play Pokémon Go. Is there a way to remove root or do I have to be running a stock rom? I'm using the latest nightly of the regular Cyanogen Cm13.
Thanks
Click to expand...
Click to collapse
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"

mrrocketdog said:
in superSU app , under settings is a clickable box for "full unroot". tried that?
"err on the side of kindness"
Click to expand...
Click to collapse
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app

Shack70 said:
I can't get the supersu app to work. It wants to update and fails update. Updating through twrp creates a boot loop. Good idea though, thanks.
Sent from my SGH-T999 using XDA-Developers mobile app
Click to expand...
Click to collapse
hmmmmm well just for something to try , how about reflasing superSU then see if it will open. idk. just something to try
"err on the side of kindness"

CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install SUHide v0.54
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will hide your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
-Test Pokemon Go. You should have no problems!
6. Need a GPS spoofing app? I use Fake GPS (well worth the $2.99). It allows you to pin favorite locations (I bounce quickly between spots where I can hit multiple lured PokeStops at once), and has settings to randomly move within a radius at whatever intervals and speed. They also have a GPS Joystick and Routes app that I have not yet tested since they don't offer a trial or free version. I'll update on that if they do offer a trial.
I have fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
**UPDATE 10/7/2016 ** - edited to use updated suhide v0.54

FuNKSioN said:
CM13 has it's own baked-in implementation of ClockWorkMod's SuperUser, not SuperSU. You can install SuperSU, but it will conflict. You'll first need to delete /system/bin/su and /system/xbin/su, then you can "try" installing SuperSU, SUHide, etc..
1. install the latest version of TWRP for your device
2. boot into recovery and install SuperSU v2.78 SR1
-reboot system. open SuperSU and setup as normal
3. boot into recovery and install suhide v0.53
-reboot system. open an app that require root to make sure your root is functioning
-try Pokemon Go. It should work fine
Do you need some sort of GPS spoof? You'll need Systemless XPosed and a good module
4. boot into recovery and install Xposed v86.2 - Universal Systemless (make sure you select 86.2 - you DO NOT need Magisk)
reboot system.
5. install Material Design Xposed Installer APK
-run XPosed Installer. it should show you are using 86.2 systemless
-click top left button and select download. search for a module called "Snorlax" and install the most recent version.
-this will spoof your mock locations setting as well as show IV's, movesets, etc. of any Pokemon you encounter. it's all client side so no worries about bans!
-reboot system
Test Pokemon Go. You should have no problems!
***UPDATE***
I have just fresh installed CM13 on a Nexus 5, following the instructions above for systemless root + xposed. Pokemon Go v39.1 works without issue while spoofing GPS.
Click to expand...
Click to collapse
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.

Shack70 said:
I deleted all the support files but Pokémon ends telling it's unable to log me in. Many users are reporting this error. It might just be my phone, the s3 is kinda old.
Click to expand...
Click to collapse
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.

FuNKSioN said:
Hmm.. For ****s and giggles, I'll pull out an old S3 and give it a go. Will report back soon.
Click to expand...
Click to collapse
Wow! Thanks I appreciate it.

Shack70 said:
Wow! Thanks I appreciate it.
Click to expand...
Click to collapse
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.

FuNKSioN said:
Sorry took so long. This phone is slow as ballz! Everything appears to be working correctly though. I have Pokemon Go 39.1 installed (had to use apkmirror to install since it wouldn't let me from the Play Store on the S3), and am using Snorlax module to hide mock locations. I'm also using Fake Gps to spoof location.
I'd say it should work for you as well. What modules are you using? If you don't care about anything on your phone, wipe everything from recovery. Then under advanced, adb sideload CM13 and GApps Nano from opengapps.org (ARM/6.0/nano). Restart system and follow all the steps from there after you have the initial phone setup done.
Click to expand...
Click to collapse
Thanks for your help. I updated yo the newest nightly build, did a full factory reset and deleted the 2 su files. After rebooting i re-downloaded the newest version of Pokémon and installed it. Game is working fine.
I don't use root much so I'll see how it goes without root and if I need root i can put the su files back(I made copies and put them in Dropbox) or try superSU/hideSU.
I know the s3 is slow but I'm putting off an upgrade until i have to upgrade. Until i upgrade I won't really realize how slow my phone is
Sent from my SGH-T999 using XDA-Developers mobile app

Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.

FuNKSioN said:
Going forward, I don't think the CM baked-in SuperUser is going to cut it. At least not the version in CM13. The specific versions of SuperSU + suhide I linked seem to pass all current checks though. So if you want root, go ahead and use them.
Click to expand...
Click to collapse
Yeah i get this is a temporary solution. Thanks for all your help. You've really gone above and beyond
Sent from my SGH-T999 using XDA-Developers mobile app

no problem man!

Thanks!
FuNKSioN said:
no problem man!
Click to expand...
Click to collapse
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.

romehu2 said:
just wanted to chime in and say my own SGH-T999 is now running PG again, thanks to you FuNKSioN - so, thank you sir!!! wasted a LOT of time trying other solutions (mainly Magisk) with no luck, so i was pretty damned happy when your steps worked. first time i forgot to rename/delete the two su files, second time i did it immediately after flashing CM13 & GApps using ADB and then everything was fine. you rock!!! :victory:
and also, yeah - until Shack70 and i get a new phone, we have no idea what "slow as ballz" is! i will say, the S3 may be relatively slow but i have two backup batteries that take up very little space and are very easy to swap in and out.
Click to expand...
Click to collapse
Glad to help. I was in the same boat: so much info in all directions and none of it seemed to work. I keep up with ChainFire's G+ account. He had a few posts linked directly back to XDA. Those few posts had everything needed. I just put it in simple steps. All thanks to him really

Sigh
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?

romehu2 said:
And now SafetyNet is failing and PoGo won't log me in. Is this really worth it?
Click to expand...
Click to collapse
reflashed CM13 + GApps, used ADB to rename system/xbin/su & system/bin/su to /su-off, and SafetyNet is happy (and thus, so is PoGo). but now, of course, phone isn't rooted.
---------- Post added at 05:18 AM ---------- Previous post was at 05:05 AM ----------
on the plus side, CM13 comes with File Manager which allowed me, without root, to install the v39.1 PoGo apk that I downloaded last week.

Sit back and wait for an SU update... It's only been a hot minute.