I have noticed there are two popular zips to root a device, CWM-SuperSU and Superuser. They both apear to function the same way. Is one of these preferred? I have only ever used the Superuser files since I joined the Android team. Am I missing anything? Thanks.
SuperSU it gives super user permissions much faster.
Sent From My Toro+ via RED Tapatalk
Supersu is one that I prefer
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz
FYI, SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted, etc.
SuperSU v0.94
How can i switch superuser to supersu if superuser is built into my rom?
Sent from my Verizon Galaxy Nexus using xda app-developers app
woot_galaxy_nexus said:
How can i switch superuser to supersu if superuser is built into my rom?
Sent from my Verizon Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Flash http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip in CWM
buzzcomp said:
Flash http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip in CWM
Click to expand...
Click to collapse
cool, so does this remove superuser or do i have to do that manually?
woot_galaxy_nexus said:
cool, so does this remove superuser or do i have to do that manually?
Click to expand...
Click to collapse
the .zip will remove Superuser and install SuperSU
buzzcomp said:
the .zip will remove Superuser and install SuperSU
Click to expand...
Click to collapse
sweet, it worked great! thanks
Thanks guys, looks like I will be flashing SuperSU v0.94 tonight.
Have been using superSU for a couple of weeks now instead of the old trusted superuser. Besides the fact it does seem to allow root access a bit faster, there really is little difference between the two.
Sent from my Galaxy Nexus using Tapatalk 2
Superuser is open-source.
From the Superuser's github:
"Superuser should be open source. It's the gateway to root on your device. It must be open for independent security analysis. Obscurity (closed source) is not security."
I've used SuperSU by Chains for a few years now on the various ROMS, and when MMuzzy switched over to Superuser, it was a simple transfer that hasn't affected anything really. I haven't noticed any differences besides (like everyone else is saying) it is a bit slower at allowing permissions.
Related
On my Galaxy Y I installed SuperSu and I installed the lasted binary from the SuperSU app 'did hide superuser in options' but it's still there I can't seem to get rid of superuser (I want to switch to SuperSu because superuser is dead now and SuperSU is the newest root manager from Chainfire...
So can someone help me
GianniDPC said:
On my Galaxy Y I installed SuperSu and I installed the lasted binary from the SuperSU app 'did hide superuser in options' but it's still there I can't seem to get rid of superuser (I want to switch to SuperSu because superuser is dead now and SuperSU is the newest root manager from Chainfire...
So can someone help me
Click to expand...
Click to collapse
i think SuperUser is faster than SuperSU i think nothing beats the original xD
Use a file manager
And go to system then apps then delete superuser
I agree with cosminx13 that superuser is better than supersu
Sent from my thanks button
cosminx13 said:
i think SuperUser is faster than SuperSU i think nothing beats the original xD
Click to expand...
Click to collapse
I agree wid u cosminx13....
I got rid of SuperSU, when I installed Hybrid ROM.....
this time old is gold
superuser works!!!
cosminx13 said:
i think SuperUser is faster than SuperSU i think nothing beats the original xD
Click to expand...
Click to collapse
Same here
Sent from my GT-S5360 using xda premium
There is only one app in this category and that is and remains our favorite of all, superuser.for me the still the best.
I'm running 4.1.1 via Bugless Beast and am loving it. Odd issue though.
When I reboot my phone, it takes like 3-4 minutes before SU can grant root access to root apps. So, if I try to run any root apps before SU "catches up" they just fail. Don't think this was a problem before upgrading to JB.
This may be related, so I figured I'd mention it too: My Trinity Kernal settings don't seem to stick though a reboot. Any ideas?
Just tried re-installing SU from CWR -- no dice. This isn't a deal breaker, but it is rather annoying. Everything works fine after 5 minutes or so.
Maybe try updating the binaries
SuperSU is the recommended superuser solution for JB. You might try making the switch and see if it works better for you.
Sent from my Galaxy Nexus using xda app-developers app
athakur999 said:
SuperSU is the recommended superuser solution for JB.
Click to expand...
Click to collapse
Since when?
athakur999 said:
SuperSU is the recommended superuser solution for JB. You might try making the switch and see if it works better for you.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I haven't had much luck getting SuperSU to work at all.
efrant said:
Since when?
Click to expand...
Click to collapse
since jelly bean. superuser has been giving many people issues.
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
the_grobe said:
I haven't had much luck getting SuperSU to work at all.
Click to expand...
Click to collapse
here is a flashable SuperSU. after flashing it and booting, open up the SuperSU app. if it asks you to update the binaries, go ahead and do so. if it doesnt, then youre good at that point http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip
simms22 said:
since jelly bean. superuser has been giving many people issues.
Click to expand...
Click to collapse
Those people must have been using an old version or had other issues. There is nothing wrong with Superuser. http://androidsu.com/superuser/
efrant said:
Those people must have been using an old version or had other issues. There is nothing wrong with Superuser. http://androidsu.com/superuser/
Click to expand...
Click to collapse
then rom developers have been adding an older version of superuser. whatever it is, super su seems to have fixed many peoples issues with su in jelly bean..
simms22 said:
since jelly bean. superuser has been giving many people issues.
Click to expand...
Click to collapse
I can second this. With Jellybro CM10, I have the 4-5 minute wait time with SuperUser, but zero wait time with SuperSU. It's happened on every single one of the nightlies that I've flashed.
I'm currently running rbox's updated 51.1.4.0_user_514006420 ROM. I can still grant superuser access to apps that request it, and apps that require su function properly, but I can't open the SuperSu app itself, it just crashes. When I try to open it from the KFTV launcher, the screen blinks and it returns to the applications menu. If I try to open SuperSu from XBMC, it causes XBMC to crash as well.
Logcat after trying to start SuperSu: http://pastebin.com/QNTd684U
BlaqkAudio said:
I'm currently running rbox's updated 51.1.4.0_user_514006420 ROM. I can still grant superuser access to apps that request it, and apps that require su function properly, but I can't open the SuperSu app itself, it just crashes. When I try to open it from the KFTV launcher, the screen blinks and it returns to the applications menu. If I try to open SuperSu from XBMC, it causes XBMC to crash as well.
Logcat after trying to start SuperSu: http://pastebin.com/QNTd684U
Click to expand...
Click to collapse
+1. Me too.
mine has no option to launch. is that what you mean?
it seems to work fine when apps request root but cannot be opened itself.
a bit annoying.
jarayn said:
mine has no option to launch. is that what you mean?
it seems to work fine when apps request root but cannot be opened itself.
a bit annoying.
Click to expand...
Click to collapse
I think it has to do with the way I'm installing it. In theory if you were to delete the SuperSu.apk from /system/app and sideload the apk yourself, it might work better. And if you horribly break things, you can always just reinstall the prerooted rom to get it back.
rbox said:
I think it has to do with the way I'm installing it. In theory if you were to delete the SuperSu.apk from /system/app and sideload the apk yourself, it might work better. And if you horribly break things, you can always just reinstall the prerooted rom to get it back.
Click to expand...
Click to collapse
I deleted it and sideloaded it back. Same behavior. Just want to get into its settings. I used the latest PlayStore version APK.
Yeah, same here. I ended up installing Clockworkmod's Superuser and uninstalling SuperSU. All I needed was the ability to disable notifications on a per app basis.
BlaqkAudio said:
Yeah, same here. I ended up installing Clockworkmod's Superuser and uninstalling SuperSU. All I needed was the ability to disable notifications on a per app basis.
Click to expand...
Click to collapse
Could you explain that? Where is CWM's SuperUser?
jmerrilljr2 said:
Could you explain that? Where is CWM's SuperUser?
Click to expand...
Click to collapse
+1. I installed latest ChainFire's SuperSU. Is there another? Is that our problem? Is there a CWR SU?
jmerrilljr2 said:
Could you explain that? Where is CWM's SuperUser?
Click to expand...
Click to collapse
schneid said:
+1. I installed latest ChainFire's SuperSU. Is there another? Is that our problem? Is there a CWR SU?
Click to expand...
Click to collapse
Direct download from CWM website
You'll have to re-approve superuser requests since it's a different app. I believe this is the same superuser app that comes with Cyanogenmod
BlaqkAudio said:
Direct download from CWM website
You'll have to re-approve superuser requests since it's a different app. I believe this is the same superuser app that comes with Cyanogenmod
Click to expand...
Click to collapse
I can start including this one in the prerooted instead of supersu if it works better.
rbox said:
I can start including this one in the prerooted instead of supersu if it works better.
Click to expand...
Click to collapse
From what I read the supersu is always the best one to choose. Certainly with phones.
I just dont know why we cant launch the app as normal to adjust settings.
Can you launch yours? Can anyone?
jarayn said:
From what I read the supersu is always the best one to choose. Certainly with phones.
I just dont know why we cant launch the app as normal to adjust settings.
Can you launch yours? Can anyone?
Click to expand...
Click to collapse
I don't know about "always the best". It's all the same crap really. CM ships with Superuser and it seems to work fine for everyone using that.
I can't launch it either.
jarayn said:
From what I read the supersu is always the best one to choose. Certainly with phones.
I just dont know why we cant launch the app as normal to adjust settings.
Can you launch yours? Can anyone?
Click to expand...
Click to collapse
Mine launches fine. I can review which apps have been granted, add and remove them, etc.
Sent from my SCH-I545 using Tapatalk
I also had the same issues. However, I was able to fix it by deleting "/system/app/SuperSu.apk" and then side-loading an older version of SuperSu (2.01). So, it looks as if the issue may be with compatibility with more recent versions.
wunderdrug said:
I also had the same issues. However, I was able to fix it by deleting "/system/app/SuperSu.apk" and then side-loading an older version of SuperSu (2.01). So, it looks as if the issue may be with compatibility with more recent versions.
Click to expand...
Click to collapse
same story here + can not erase "Supersu.apk"
"rm failed for /system/app/Superuser.apk, Read-only file system"
I am on pre-rooted 51.1.4.0_user_514006420
opened towelroot again, clicked "make it rain" it tells me "device is not supported" (since pre-rooted rom ?)
getting confused here
coops_one said:
same story here + can not erase "Supersu.apk"
"rm failed for /system/app/Superuser.apk, Read-only file system"
I am on pre-rooted 51.1.4.0_user_514006420
opened towelroot again, clicked "make it rain" it tells me "device is not supported" (since pre-rooted rom ?)
getting confused here
Click to expand...
Click to collapse
Did you mount the file system as read/write before you tried to delete it?
Sent from my SCH-I545 using Tapatalk
collindv said:
Did you mount the file system as read/write before you tried to delete it?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
nope, did not
thanks for the tip!
SuperSU 2.00 running :victory:
collindv said:
Mine launches fine. I can review which apps have been granted, add and remove them, etc.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
What version of SuperSU are you running ?? And what PreRooted FW are you on too ??
Y314K said:
What version of SuperSU are you running ?? And what PreRooted FW are you on too ??
Click to expand...
Click to collapse
Install SuperUser. I moved on form supersu as I too wanted to change and couldn't. Superuser works just fine.
navigates said:
Install SuperUser. I moved on form supersu as I too wanted to change and couldn't. Superuser works just fine.
Click to expand...
Click to collapse
Is this the SuperUser that is working for all on the FireTV... Does it matter what version ?? So latest works just fine...
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
If so.. Is there a correct order to get rid of the SuperSU & Sideload the new one ??
Ok, so I have been looking into some of the SuperSU.zip files and sound that there are a few that actually dont make the phone go into boot loop. I double checked the system/xbin and su is installed as well as busybox. Then When I replace a 64 bit su file into Superuser 2.19, supersu app keeps telling me to update the binaries. Thats where Im stuck. So to recap.
I used the root method from CF-autoroot.
Once it failed I pulled the battery and flashed SuperSU-v2.19zip..
Now I get the binary update notification...
If I can just get some help from anyone that knows what they are doing that would be awesome..
Here is the Modded zip.. https://drive.google.com/file/d/0B6opNIGQWcVYT1JRMmtrNFUtbE0/view?usp=sharing
BTW: I got the 64 su file from root junky...
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
samep said:
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?
I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?
TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
z31k said:
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.
Ive been at it for like 2 weeks.. lol..
Click to expand...
Click to collapse
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Edit 2: if using custom kernel, don't need liboemcrypto.so
Sent from my SM-N910P using Tapatalk
samep said:
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?
None of the su binaries work?
Regards,
Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
pbedard said:
How can u swap it with a locked boooader
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
The OP says he can flash mods. I'm assuming here and you know the consequences of such, but thought it also possible to mount system and use the TWRP file manager to edit system.
I'm still OB7 but following with interest regarding the root of OG5 and recovery methods.
Edit: If L Speed Mod flashes successfully, default mode should give more freedom if using ADB and it doesn't need root. I think it's all shell scripts. (ADB Insecure required for booted mode adb access.)
Sent from my SM-N910P using Tapatalk
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Ill look into it flashing l speed mods.. maybe that can be a door... I know that Selinux and fix permissions can be applied via TWRP. SU binaries are applied.. they were in the system folders. So su is where its supposed to be. Busybox is where its supposed to be, 2.49 does not work just older builds. Its all a matter of figuring out how to update binaries??
pbedard said:
Yea i debloated it wothout root in an adb abell
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
I would love to debloat in adb shell, however whenever I make a shell environment the device will not detect in adb shell. regular adb commands is fine, just when I start shell.. Suggestions?
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
z31k said:
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
Click to expand...
Click to collapse
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
samep said:
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.
Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.
Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.
https://youtu.be/zOUrd04dvI4
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
z31k said:
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
Click to expand...
Click to collapse
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
samep said:
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.
Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, that's the thing. I need all the help i can get. I posted over here because you guys have development. I have been watching your forum like a hawk, just waiting for you guys to get 5.1.1. Lol....We dont in the sprint note edge forum. But i figure its the same hardware.
So with all that said, i really appreciate your help. Its a great step at a fresh direction.
I tried the systemless root method several times.. None of it works.
If my superSU app says I'm rooted, Android pay doesn't work. Only way to get it working again is if I UNROOT using the superSU tool.
Sent from my Nexus 5X using Tapatalk
insang-droid said:
I tried the systemless root method several times.. None of it works.
If my superSU app says I'm rooted, Android pay doesn't work. Only way to get it working again is if I UNROOT using the superSU tool.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Root with the systemless root method, and delete "/su/xbin_bind". Android Pay will work. However, you might break root compatibility with older apps that haven't been updated.
LancerEVA06 said:
Root with the systemless root method, and delete "/su/xbin_bind". Android Pay will work. However, you might break root compatibility with older apps that haven't been updated.
Click to expand...
Click to collapse
Can confirm this allowed me to add my CC again, have not yet tried paying yet. I have 2.66 beta, and using AdAway, TiBu, and Greenify. So far no issues.
am I deleting the whole SU folder? or just the XBIN_BIND?
insang-droid said:
am I deleting the whole SU folder? or just the XBIN_BIND?
Click to expand...
Click to collapse
Just XBIN_BIND
Sent from my Nexus 5X using Tapatalk
yes, mine definitely works.
FYI, greenify breaks it, just having it installed for me (even if disabled)
adaway does not have to though, long as you flash the systemless hosts zip file before installing and applying it