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
Related
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.
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.
MOD EDIT: PLEASE MIGRATE TO THE OFFICIAL CANARY BUILDS
THIS THREAD IS ABOUT UNOFFICIAL COMMUNITY BUILDS. OFFICIAL BETAS THREAD IS HERE: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589.
This thread is dedicated to the community-built next versions of Magisk and MagiskManager using latest source files posted by @topjohnwu. If you want to contribute in any way -- create a PR/issue on github.
These might be very unstable builds, especially in the early stages of development. You're highly advised to read the rest of this post and at least a few last pages of the discussion.
Downloads are here: https://github.com/TheComputerGuy96/MagiskFiles. Keep reading if this is your first visit to this thread or for the updates at the bottom of this post.
Current builds are courtesy of @kantjer. This project wouldn't have happened without @Deic's module to track the snapshot updates (which may be hindered by recent @topjohnwu changes in versioning) and his contributions to the build script, as well as major contributions in supporting fellow community members by @Captain_Throwback, @Didgeridoohan and @DodoGTA.
Installation:
Magisk: flash magisk snapshot from recovery, it should install over any previous version just fine.
Magisk Manager: The snapshot APK is signed with a different key than the release APK so you can't install snapshot magisk manager over magisk manager from Play Store. You will need to uninstall existing Magisk Manager and install the snapshot APK afterwards.
Commits Logs:
Magisk (master branch)
Magisk Manager (master branch)
IF SOMETHING DOESN'T WORK AND/OR CRASHING:
No support of any kind is implied, however it's a community forum so some users (including local experts) might be willing to help your and/or your report might be helpful to @topjohnwu, but please make sure to follow the below:
Magisk Manager crashing? Problem with Magisk module? Post installed versions of magisk, magisk manager, versions of all installed modules and the magisk log + logcat.
Downloads: https://github.com/TheComputerGuy96/MagiskFiles
Source code: https://github.com/TheComputerGuy96/Magisk (branch travisci-dev)
Travis-CI link: https://travis-ci.org/TheComputerGuy96/Magisk
That's nice of you. What is the change log?
Cool! I'm gonna give this a try and see if some of my issues are resolved.
Filip013 said:
That's nice of you. What is the change log?
Click to expand...
Click to collapse
We can check the commits log for now: https://github.com/topjohnwu/Magisk/commits/master and https://github.com/topjohnwu/MagiskManager/commits/master.
@topjohnwu, what's the reasoning for disabling MagiskHide when SuperSu is installed?
gamer765 said:
@topjohnwu, what's the reasoning for disabling MagiskHide when SuperSu is installed?
Click to expand...
Click to collapse
Because Magisk Hide don't work with SuperSU? Maybe...
Viper4android is working well S7 nougat
Verstuurd vanaf mijn SM-G930F met Tapatalk
Didgeridoohan said:
Because Magisk Hide don't work with SuperSU? Maybe...
Click to expand...
Click to collapse
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
Ok, cool... Did not know that was possible. Since topjohnwu himself have stated that Magisk Hide can NOT hide SuperSU, I assume he has a good reason to do what he does.
Think about saying stupid things, you should have respect for the guy. Just turn on magisk hide, do not tick supersu in gui
Verstuurd vanaf mijn SM-G930F met Tapatalk
afcaajax said:
Think about saying stupid things, you should have respect for the guy. Just turn on magisk hide, do not tick supersu in gui
Verstuurd vanaf mijn SM-G930F met Tapatalk
Click to expand...
Click to collapse
Not sure if you're directing that at me, but no one here is saying stupid things, except maybe you. Plus, I'm a dev/hacker myself so it doesn't really bother me, since I can always fix it myself.
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
If you haven't yet, please consider creating an issue for that on github and let @topjohnwu know.
AFAIK you can checkout the code one commit before the problematic one and build your own v10.
PS. Please don't feed the trolls.
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
That's unexpected, it never worked previously, I just added the detection I should have done in ages.
I'll try it myself when I got time, once confirmed working I'll revert this change
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
I'm not sure how you're accomplishing this, but it shouldn't be possible, unless you're also using some other hiding method (suhide, RootSwitch). Magisk Hide cannot hide SuperSU. I just installed it and tried it to confirm, since your post piqued my curiosity, but not surprisingly, SafetyNet came up all red, and my AirWatch app shows compromised.
Can you explain in detail what your setup is and confirm you're ONLY using SuperSU and Magisk Hide, and pass with green for SafetyNet?
Ah, well I am using suhide and rootswitch as well and everything works perfectly fine for me.
I've attached screenshots of SafetyNet passing for me. By all means, it's your project, you may do whatever you wish with it, I'll just fork it and make my own private builds where SuperSU does not disable MagiskHide..
gamer765 said:
Ah, well I am using suhide and rootswitch as well and everything works perfectly fine for me.
I've attached screenshots of SafetyNet passing for me. By all means, it's your project, you may do whatever you wish with it, I'll just fork it and make my own private builds where SuperSU does not disable MagiskHide..
Click to expand...
Click to collapse
Let me take a moment and just lay my palm against my forehead...
I'm gonna go out on a limb and guess what you're really using Magisk Hide for is hiding your unlocked bootloader with resetprop. There are other ways of doing that, you don't need Magisk Hide.
No, I do not. I use it for other stuff as well. All my mods are systemless. I'm on completely stock system with a custom kernel that does not pass bootloader unlock flags. I'm not a dumb person, but I see I'm being treated that way. I do things the way I do them for a reason. I will no longer partake in this conversation, I have better things to do. Maybe it's better to just stick to stock because ignorance is bliss. I need a break anyways from my work. Bye and thank you.
gamer765 said:
No, I do not. I use it for other stuff as well. All my mods are systemless. I'm on completely stock system with a custom kernel that does not pass bootloader unlock flags. I'm not a dumb person, but I see I'm being treated that way. I do things the way I do them for a reason. I will no longer partake in this conversation, I have better things to do. Maybe it's better to just stick to stock because ignorance is bliss. I need a break anyways from my work. Bye and thank you.
Click to expand...
Click to collapse
Well if you want to use SuperSU with Magisk Hide, just manually revert the change that disallowed it. That takes 10 seconds to do.
Captain_Throwback said:
Well if you want to use SuperSU with Magisk Hide, just manually revert the change that disallowed it. That takes 10 seconds to do.
Click to expand...
Click to collapse
His question still stands, if MagiskHide does work with SuperSu installed and there're viable use cases for that, why disable it?
stangri said:
His question still stands, if MagiskHide does work with SuperSu installed and there're viable use cases for that, why disable it?
Click to expand...
Click to collapse
I don't think @topjohnwu was considering those extended use cases when he disabled it. Maybe now that he knows, he'll revert that change. I think he was thinking that Magisk Hide can't directly hide it so it would always be detected. With several other tools, it's apparently possible to hide it, which is good to know. Personally, I'll just be sticking with the open-source solution anyway, so it doesn't really affect me.
EDIT: Besides the fact that there are many people who will enable it, not knowing that Magisk Hide can't hide SuperSU. I think the change was in an effort to prevent those types of questions.
I've always loved the idea of being able to pay (at a lot of places, now) using NFC technology. Unfortunately, root access, xposed, and now a custom rom (Props to the EpicROM team!) have always out prioritized the NFC payment feature.
I've read a great deal about Magisk, and so I know how it works, but afaik EpicROM is packaged with SuperSU and so there isn't a straightforward way to use one of the compatible superuser apps. So, my question is (and the custom rom issue might be a bit much to tackle, but it's worth asking), has ANYONE managed to get Android Pay working on their Mix?
Also, I searched around for a good bit, only to find the answer elude me: Are there acceptable substitutes for Android Pay that do the same thing (NFC payment, "tap and go"?) and are accepted by most point of sale setups?
bigcc32 said:
I've always loved the idea of being able to pay (at a lot of places, now) using NFC technology. Unfortunately, root access, xposed, and now a custom rom (Props to the EpicROM team!) have always out prioritized the NFC payment feature.
I've read a great deal about Magisk, and so I know how it works, but afaik EpicROM is packaged with SuperSU and so there isn't a straightforward way to use one of the compatible superuser apps. So, my question is (and the custom rom issue might be a bit much to tackle, but it's worth asking), has ANYONE managed to get Android Pay working on their Mix?
Also, I searched around for a good bit, only to find the answer elude me: Are there acceptable substitutes for Android Pay that do the same thing (NFC payment, "tap and go"?) and are accepted by most point of sale setups?
Click to expand...
Click to collapse
To pass safety net you need to
1. Be unrooted
2. Have an official rom, which is stable (not developer)
3. Have a locked bootloader
So most probably, Magisk will not help you on this
Sent from my MI MIX using Tapatalk
Nikos2k said:
To pass safety net you need to
1. Be unrooted
2. Have an official rom, which is stable (not developer)
3. Have a locked bootloader
So most probably, Magisk will not help you on this
Sent from my MI MIX using Tapatalk
Click to expand...
Click to collapse
Yeah the three things you listed there are things I think I'd rather have than the slight inconvenience of having to actually pull out my wallet to pay for things.
In an ideal world we'd all be able to pay with PayPal using NFC technology, but oh well.
There is a kernel patch which fakes a verifiedboot state; you can try that.
https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
Which you can apply to: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/scorpio-m-oss
adwinp said:
There is a kernel patch which fakes a verifiedboot state; you can try that.
https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
Which you can apply to: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/scorpio-m-oss
Click to expand...
Click to collapse
I'm usually pretty technologically literate, but I'm not sure what I'm looking at. Part of the first URL you linked includes the words "oneplus," suggesting to me that it might not be as simple as just running that command line script. I don't expect to be spoon-fed information, but links to any related threads would be much appreciated.
I relocked my bootloader after I installed the official Global rom. I can add my credit cards but I can't get it to pay for anything at a terminal. It just doesn't launch at all.
Instead of flashing patched kernel, I would recommend flashing resurrection rom instead.
hello,
i used the xposed module "app settings" version 1.13 with android marshmallow before i updated to nougat. this module enables you to change DPI, font scale, locale, force fullscreen, persist in memory, etc. on a per app basis.
here is a link to the module:
https://forum.xda-developers.com/xp...2014-05-14-t2437377/post63835421#post63835421
i have not found any possibility to get this working on nougat as there is no xposed for nougat and it seems there is no more custom rom with these options.
is it possible to get this module working with magisk?
satand said:
hello,
i used the xposed module "app settings" version 1.13 with android marshmallow before i updated to nougat. this module enables you to change DPI, font scale, locale, force fullscreen, persist in memory, etc. on a per app basis.
here is a link to the module:
https://forum.xda-developers.com/xp...2014-05-14-t2437377/post63835421#post63835421
i have not found any possibility to get this working on nougat as there is no xposed for nougat and it seems there is no more custom rom with these options.
is it possible to get this module working with magisk?
Click to expand...
Click to collapse
Downgrade to marshmallow or write xposed for nougat. The first is easy, the second will make many people happy over here.
Sent from my ONEPLUS A3003 using Tapatalk
satand said:
is it possible to get this module working with magisk?
Click to expand...
Click to collapse
Just to clarify on the above response: No.
Thanks Op, I also would love to have App Settings equivalent on Magisk or stand alone. Turns my 6.44" Mi Max into a desktop chrome browser almost
cobram3 said:
Thanks Op, I also would love to have App Settings equivalent on Magisk or stand alone. Turns my 6.44" Mi Max into a desktop chrome browser almost
Click to expand...
Click to collapse
It would be just ultra hard to code that, or just impossible.
years ago (before xposed got famous) some custom roms (paranoid,...) had these functions.
i would go back to marshmallow only because of this missing features but there is no marshmallow rom for my new oneplus 5.
is it really impossible to get it working with magisk? the code itself (version 1.13) worked without any problems on marshmallow.
satand said:
years ago (before xposed got famous) some custom roms (paranoid,...) had these functions.
i would go back to marshmallow only because of this missing features but there is no marshmallow rom for my new oneplus 5.
is it really impossible to get it working with magisk? the code itself (version 1.13) worked without any problems on marshmallow.
Click to expand...
Click to collapse
You'll need to manually edit files and apps and Magic Mount them with Magisk. Alternatively you could possibly do some things with some cumbersome scripts. Magisk can't change code of running apps, just replace/add already modified files and run scripts at boot.
In other words: No, IMO it's not worth the extreme hassle and you won't get the same thing as you would with Xposed.
Didgeridoohan said:
You'll need to manually edit files and apps and Magic Mount them with Magisk. Alternatively you could possibly do some things with some cumbersome scripts. Magisk can't change code of running apps, just replace/add already modified files and run scripts at boot.
In other words: No, IMO it's not worth the extreme hassle and you won't get the same thing as you would with Xposed.
Click to expand...
Click to collapse
thanks for your answer!
do you have more information about these "cumbersome scripts"? maybe it would work with tasker and a script per app.
i would be very happy...i like my smartphone much more with these features.
satand said:
thanks for your answer!
do you have more information about these "cumbersome scripts"? maybe it would work with tasker and a script per app.
i would be very happy...i like my smartphone much more with these features.
Click to expand...
Click to collapse
I wasn't gonna open up that can o' worms, but since you brought it up... :laugh:
Look up how to work with shell scripts. Tasker can run those (among other things). You could probably do some stuff with the resetprop tool as well (look here for details and syntax).
Don't expect miracles though...
Didgeridoohan said:
You'll need to manually edit files and apps and Magic Mount them with Magisk. Alternatively you could possibly do some things with some cumbersome scripts. Magisk can't change code of running apps, just replace/add already modified files and run scripts at boot.
In other words: No, IMO it's not worth the extreme hassle and you won't get the same thing as you would with Xposed.
Click to expand...
Click to collapse
Didgeridoohan said:
I wasn't gonna open up that can o' worms, but since you brought it up... :laugh:
Look up how to work with shell scripts. Tasker can run those (among other things). You could probably do some stuff with the resetprop tool as well (look here for details and syntax).
Don't expect miracles though...
Click to expand...
Click to collapse
thanks...but that is too high for me
Do we have a petition to develop this form? hahaha
I would like to have app settings on magisk too. I just wanted to change the app local instead of globe settings.
bush911 said:
I would like to have app settings on magisk too. I just wanted to change the app local instead of globe settings.
Click to expand...
Click to collapse
"App Locale 2" for Xposed can help you
And you can get Xposed systemlessly with Magisk.
Thank you so much for the advice.
My phone is 1st generation Pixel with latest android, mgaisk installed. I will try to figure it out.
daniel_m said:
"App Locale 2" for Xposed can help you
And you can get Xposed systemlessly with Magisk.
Click to expand...
Click to collapse
Anybody have a suggestion - I'm looking to change the dpi of chrome app (8.1) without Xposed
Maybe this could help
https://joyofandroid.com/change-screen-resolution/