Can Anyone tell me the difference in the Superuser app from Chain Fire and the Superuser from Chain SDD? I have always used the Older version!
Sent from my DROID BIONIC using Tapatalk 2
crazytrain69 said:
Can Anyone tell me the difference in the Superuser app from Chain Fire and the Superuser from Chain SDD? I have always used the Older version!
Click to expand...
Click to collapse
To quote a portal post by jerdog:
In the context of Android, Superuser has become synonymous with the Superuser app created by XDA Recognized Developer ChainsDD that grants you (and applications) root privileges by allowing you to accept the request or not. His app and process for obtaining root were the only options on the block for a long time, until XDA Elite Recognized Developer Chainfire sought a different solution to requesting and granting root privilege requests. The result of that endeavor was SuperSU, which has increasingly become a mainstay and is being included in more and more new custom ROM development these days.
Click to expand...
Click to collapse
In short, Chainfire's SuperSU app uses a slightly different approach, and he added the one or another feature the app from ChainsDD didn't have. For example, the paid SuperSU Pro can be set to survive a OTA update so you stay rooted.
ChainsDD actually discontinued development of his Superuser app quite some time ago.
While it's a matter of personal preference about which one you want to use, running with SuperSU may be the better approach.
Related
Hi,
I'm looking for a way to avoid updates for my KFHD by Amazon over OTA.
Is there an software hack or firewall solutions?
My device running version 7.2.3 and is rooted.
I did read that also rooted devices will get OTA updates. And this will remove root and other changes.
Best regards!
Rooting is required to stop ota updates, there are scripts on this forum that look unhealthy to run, some people freeze apps with titanium backup, others use droidwall, I personally just gained root then renamed a file named otacerts.zip to otacerts.bak from etc/security and that worked fine for me...
People from all these forums claims any one of these solutions do not work, I can attest that otacerts.bak worked for me. But they should all be viable solutions.
I am still on 7.2.1
Sent from my KFTT using xda app-developers app
Thank you very much and a happy new year!
mrkhigh said:
Rooting is required to stop ota updates, there are scripts on this forum that look unhealthy to run, some people freeze apps with titanium backup, others use droidwall, I personally just gained root then renamed a file named otacerts.zip to otacerts.bak from etc/security and that worked fine for me...
People from all these forums claims any one of these solutions do not work, I can attest that otacerts.bak worked for me. But they should all be viable solutions.
I am still on 7.2.1
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Thanks very much
I've followed a root guide (not able to link due to account restrictions), however I am not sure whether I have rooted correctly (Superuser has been installed via the root). I'm a beginner in rooting and thought it would be straight forward (due to the number of tutorials around), but I don't know how to proceed now.
My basic objective is to install jelly bean with no issues in usage as the owner isn't very tech literate. The tutorials I have tried to follow thus far have had some steps which aren't possible in my circumstance or certain steps which aren't possible due to a change in the app.
If possible I will appreciate it if someone helps me, whether here, or on skype/teamspeak; preferably on the latters as it will speed up the process and I am quite time restricted. If possible I don't mind completely resetting the kindle to its original software and such and starting again just to be sure If I have rooted, but I don't know how to do that.
Thanks in advance
Details: [Rooted?] Kindle fire HD running 7.3.1 software; Model X43Z60
This work for me
https://www.youtube.com/watch?v=oT3L0VEt3IE&feature=youtube_gdata_player
Sent from my SGH-T989 using Tapatalk 2
esema1o said:
This work for me
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Thats to Root; I've already rooted (assuming from the video when it says you can see the superuser app)
Well if you have rooted right go to your browser and search for an app called Root Checker. It does not require root. It checks to see if your rooted right. If you are not rooted right the app will say so but if you are rooted right you get a message saying "You have successfully rooted your device." Hope I helped you.
jetblast787 said:
Thats to Root; I've already rooted (assuming from the video when it says you can see the superuser app)
Click to expand...
Click to collapse
Oh ok just download titanium back up when u open the app it will tell u if ur root or not
Sent from my SGH-T989 using Tapatalk 2
Titanium says I have rooted. Ok, what do I do now as per my requirements above?
Thanks
Ok, I've now installed the play store and disabled ads using this VERY useful tutorial (thanks prok!). Is there a similar tutorial on how to install jelly bean on it now?
Well the best rom out there right now is Unofficial CM10.1 from Hashcode. Yes, you could install a different one but Unofficial CM10.1 is currently the best in my opinion.
seems I don't have root access on cm12. I did previously on 2/2 build then I flashed a 2/4 and it messed up my os so had to format and install 2/2. I have root access to apps and adb in developers options but for some odd reason my apps say I don't have root. What can I do to fix this.
Flash SuperSU from recovery
But cm has built in su
Sent from my Nexus 6 using Tapatalk
coldconfession13 said:
But cm has built in su
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
does it matter what file you use for su, really?
Would just prefer to use default if its supposed to work
Sent from my Nexus 6 using Tapatalk
You'll have to enable root in developer options.
It's just off by default.
coldconfession13 said:
Would just prefer to use default if its supposed to work
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Built in superuser has been flaky on lollipop. SuperSU works much better and has a higher compatibility with apps that Superuser. Personally I prefer to use the one that works best
rootSU said:
Built in superuser has been flaky on lollipop. SuperSU works much better and has a higher compatibility with apps that Superuser. Personally I prefer to use the one that works best
Click to expand...
Click to collapse
That's silly.
This is something that either works, or doesn't.
As much as I dislike CM, they do have su down VERY well. Its even integrated with appops.
Its also open source. For something with that kind of security implications, I *absolutely would NEVER* trust a blob, which is what supersu is.
I had to wipe and reflash again and now it works. I guess it was a bad flash
Sent from my Nexus 6 using Tapatalk
doitright said:
That's silly.
This is something that either works, or doesn't.
As much as I dislike CM, they do have su down VERY well. Its even integrated with appops.
Its also open source. For something with that kind of security implications, I *absolutely would NEVER* trust a blob, which is what supersu is.
Click to expand...
Click to collapse
Does it now do all the stuff that SuperSU does to prevent the requirement for permissive mode?
rootSU said:
Does it now do all the stuff that SuperSU does to prevent the requirement for permissive mode?
Click to expand...
Click to collapse
It absolutely does NOT require selinux to be set permissive.
Also FYI: what you refer to as "all the stuff" is actually a pretty simple little adjustment to the selinux configuration.
...
CM actually has the whole selinux issue a lot simpler than SuperSU does, since as the system builder, you have the freedom to set your own selinux policies, whereas SuperSU had to hack around existing policies set by AOSP.
doitright said:
It absolutely does NOT require selinux to be set permissive.
Also FYI: what you refer to as "all the stuff" is actually a pretty simple little adjustment to the selinux configuration.
Click to expand...
Click to collapse
All I'm asking is "back in the day", when we first got our hands on Lollipop developer previews, we had to use permissive mode. Over time, through various SuperSU beta's - there was a point where the modifications to selinux were sufficient for *most* apps to not need permissive. Sure, some apps that have not been updated still require permissive mode to be set... So you're saying Superuser does that now?
Personally, I've always found superuser the lesser of the 2 root providers and was a long way behind in the early lollipop days and if they've got to a useful point now, great - though I dare say not without a lot of input from chainfire.
rootSU said:
All I'm asking is "back in the day", when we first got our hands on Lollipop developer previews, we had to use permissive mode. Over time, through various SuperSU beta's - there was a point where the modifications to selinux were sufficient for *most* apps to not need permissive. Sure, some apps that have not been updated still require permissive mode to be set... So you're saying Superuser does that now?
Personally, I've always found superuser the lesser of the 2 root providers and was a long way behind in the early lollipop days and if they've got to a useful point now, great - though I dare say not without a lot of input from chainfire.
Click to expand...
Click to collapse
"superuser", if you're referring to Koush's su setup, was actually booted from CM some time ago.
Opensource is ALWAYS the superior option when dealing with security. ALWAYS WITHOUT EXCEPTION. You can't trust what you can't AUDIT.
... there wouldn't have been any *need* for input from chainfire. This isn't rocket science, its root. Every top tier Linux distro in existence has root with selinux set to enforcing.
doitright said:
"superuser", if you're referring to Koush's su setup, was actually booted from CM some time ago.
Opensource is ALWAYS the superior option when dealing with security. ALWAYS WITHOUT EXCEPTION. You can't trust what you can't AUDIT.
Click to expand...
Click to collapse
I'm happy as I am to be honest
Hello,
few months ago I've flashed R-Mod V3 http://forum.xda-developers.com/showthread.php?t=2775977
great software for my phone.
but few day ago I tried to install cSploit (open source app, known as dSploit, sold etc) when my SuperSU app informed me that I have to pay money for premium use of SuperSU because CSploit uses some of unpaid chnuks that SuperSU supervises.
Is there any way to remove this stupid SuperSU app/reflash with something normal that will allow install apps that I like?
Thank you.l
hi,
I don't know if this is specific to fire or a general cyanogen question, but I work with fire- so there it is.
According to the tutorials I see (most notably Rootjunkies https://www.youtube.com/watch?v=4dwguHoxTvo) when I install CM I also need to put in SU in TWRP (or any other bootloader). Can I not to? What would happen?
I'd rather that apps I'll install be at their maximum segregation possible and have no loopholes to wiggle through.
Thank you very much.
You don't have to start a new thread, for every question
you have a few other threads, that you were are getting answers in
starting a new thread just means you have to wait
till someone with an answer sees your new thread
rather than getting an notification that you replied in an existing thread
it's up to you...
Sent from my KFFOWI using XDA Labs
Oh,
I actually thought it's more proper and organized that way. Separate issues- separate threads, and only those who are knowledgeable on that question would reply .
I'll try better next time.
thank you.
oy-ster said:
hi,
I don't know if this is specific to fire or a general cyanogen question, but I work with fire- so there it is.
According to the tutorials I see (most notably Rootjunkies
) when I install CM I also need to put in SU in TWRP (or any other bootloader). Can I not to? What would happen?
I'd rather that apps I'll install be at their maximum segregation possible and have no loopholes to wiggle through.
Thank you very much.
Click to expand...
Click to collapse
SU and SuperSU are entirely different things. SuperSu is a root manager that controls application access and elevated permissions. It is optional with CM 12.x which has an integrated root manager. SuperSU is a well respected third party tool that offers additional capabilities.
Davey126 said:
SU and SuperSU are entirely different things. SuperSu is a root manager that controls application access and elevated permissions. It is optional with CM 12.x which has an integrated root manager. SuperSU is a well respected third party tool that offers additional capabilities.
Click to expand...
Click to collapse
Wait, so if I understand you correctly CM already comes rooted?
Also, SU- so this is the command/file that gives the instruction to android to give administrative rights?
oy-ster said:
Wait, so if I understand you correctly CM already comes rooted?
Also, SU- so this is the command/file that gives the instruction to android to give administrative rights?
Click to expand...
Click to collapse
yes prerooted, off by default
yes, you will be prompted to allow or deny
Sent from my XT1254 using XDA Labs
oy-ster said:
Wait, so if I understand you correctly CM already comes rooted?
Click to expand...
Click to collapse
Yes - but disabled by default. Consult the CM 12-1 thread or do a Google search for instructions on enabling developer options for access to the root toggle.
oy-ster said:
Also, SU- so this is the command/file that gives the instruction to android to give administrative rights?
Click to expand...
Click to collapse
http://www.makeuseof.com/tag/su-important-using-linux-effectively
Google is your friend
Is there some way to remove the capability, not just turn it off? like with a stock?
and when i deny this su command to the kernel, does it happen in programs like supersu?
by the way, I wanted to thank you but apparently I'm limited to 8 thanks a day.
oy-ster said:
Is there some way to remove the capability, not just turn it off? like with a stock?
and when i deny this su command to the kernel, does it happen in programs like supersu?
Click to expand...
Click to collapse
Short answer - no. Curl up with a preferred beverage and search engine to advance your understanding of root, root managers and SU.
Davey126 said:
Short answer - no. Curl up with a preferred beverage and search engine to advance your understanding of root, root managers and SU.
Click to expand...
Click to collapse
thank you.