So im trying to root the stock s7 boot.img (G935U) and so far I've gotten Xposed, Dolby, and a ton of build.prop tweaks. So I obviously disabled all the Knox and TIMA stuff, as well as kap and Selinux.
Now, after flashing eng boot, and running the root.bat (system root, not systemless like usual) it is rooted. Then I flash stock boot.img and all the apps are present, and in SuperSU is says that the SU binary is occupied.
I pulled a logcat and it was a SELinux issue, SELinux being set to Enforcing seems to be preventing root and scripts to run.
So, my question... With Xposed being fully functional, is there any way to set SELinux to permissive with ONLY Xposed, no root?
Thanks for reading, awaiting a response
Edit: Forgot this isn't an s7 thread.... Whoops. So let me clerify the eng boot:
The eng boot is what we use to root, it's insecure and adb is insecure, and dm verity is disabled (aside from custom images like twrp, the eng boot is still signed by Sammy) and with it being insecure and no dm verity, we can do about anything we want. Dope right? Well, aside from the horrendous lag and crappy battery life, hence my efforts towards root on stock.
Craz Basics said:
...So, my question... With Xposed being fully functional, is there any way to set SELinux to permissive with ONLY Xposed, no root?
Click to expand...
Click to collapse
From what I know, xposed is more "system-mod-inject", so simple script like selinux changer are not made for xposed, instead they are for magisk.
Just asking: since supersu is slowly dying and magisk growing, why not try with Magisk, which adds/replaces things systemlessly?
I found a guide for your phone: here
Not sure if there is a better method now, but then you will be able to install useful magisk modules + xposed systemless with other useful modules, everything easy to remove or update.
So, no need to set permissive for root. Just saying.
TENN3R said:
From what I know, xposed is more "system-mod-inject", so simple script like selinux changer are not made for xposed, instead they are for magisk.
Just asking: since supersu is slowly dying and magisk growing, why not try with Magisk, which adds/replaces things systemlessly?
I found a guide for your phone: here
Not sure if there is a better method now, but then you will be able to install useful magisk modules + xposed systemless with other useful modules, everything easy to remove or update.
So, no need to set permissive for root. Just saying.
Click to expand...
Click to collapse
I would definitely try Magisk, but I'm unable to. First and foremost, I don't have the Exynos variant so my bootloader isn't unlockable.
Because of that, I can't flash custom boot/recovery imgs. Magisk modifies the boot.img. I'm able to do some system mods because of a dm-verity "spoof" where it allows system mods on stock. I use eng to flash everything and then flash stock boot again.
Thanks for the reply though
Related
I haven't seen a thead posted about this so I figured I'd get some input from people that have used both or either of the 2 root options.
What do you prefer and why? What are the pros and cons?
I know SuperSU is very well known and I'm familiar with it from the Galaxy S phones. Magisk is fairly new, but from what I heard it works well with Nougat and the other nice thing is that magisk can be toggled.
I'm not sure if there is any benefit to that or not, but I'd like to hear some feedback.
I'm interested to know more about this as well, but this is what I read about it.
Yes, Magisk can be toggled, so you can use Android Pay when you need it and then get back to being rooted.
However, for some reason, my AdAway adblocker just wouldn't work with Magisk+phhSU. No idea why. Everything else root worked well. When I had to clean flash the official Nougat, I decided to stick to good'ol SuperSU. I don't need the toggle function and everything worked great since.
So I've used both and can say this. Magisk works on both SuperSU and phhSU, although the later offers a different functionality. The toggle feature is an older feature of Magisk as they now have a hide feature baked in. This is the same as SUHide for SuperSU. I have yet to get SUHide working on the 3t, but I have it working on a few other phones. SuperSU+SUHide is great if you only want to run Root on your phone and hide systemless root from applications without having to really toggle Root. From my experience (YMMV), toggling root breaks things more than hiding. The only reason I have found to run Magisk is if you want to run Xposed as well. Xposed works with SuperSU, but Magisk does a pretty good job of UI integration with some of the pieces.
DarqAnshin said:
So I've used both and can say this. Magisk works on both SuperSU and phhSU, although the later offers a different functionality. The toggle feature is an older feature of Magisk as they now have a hide feature baked in. This is the same as SUHide for SuperSU. I have yet to get SUHide working on the 3t, but I have it working on a few other phones. SuperSU+SUHide is great if you only want to run Root on your phone and hide systemless root from applications without having to really toggle Root. From my experience (YMMV), toggling root breaks things more than hiding. The only reason I have found to run Magisk is if you want to run Xposed as well. Xposed works with SuperSU, but Magisk does a pretty good job of UI integration with some of the pieces.
Click to expand...
Click to collapse
Awesome, thanks for the input! That's definitely helpful. So you would recommend going with magisk? Would you say magisk works equally as well on all versions of OOS? 3.5.* and the new 4.*+ (nougat) version?
m0d hipp¥ said:
Awesome, thanks for the input! That's definitely helpful. So you would recommend going with magisk? Would you say magisk works equally as well on all versions of OOS? 3.5.* and the new 4.*+ (nougat) version?
Click to expand...
Click to collapse
Keep in mind, your mileage may very and these are only my opinions. With that said I will say this:
I've only had my OnePlus 3t for about 3 weeks, so I only really used it on the latest version of OOS 3.5. It seems to work fine on 4.*, however, it did take me a few extra steps and sideload.
I honestly would go with SuperSU / SUhide if I could get it to work on 3T correctly like it does on my other devices. Right now I have this weird forever and a day boot time with SUHide.
Magisk works almost as well in my experience and on the devices I do run xposed on runs even better in my opinion. The new Magisk doesn't turn root off but does mask root from certain apps such as android pay. The interface, in my opinion, has gotten better over the iterations. Magisk also does allow you to flash from the direct input, which depending on your skill can help out greatly.
I would say this. If you require
Xposed
UI
live updates of actual software similar to TWRP's new loader
ability to flash from app
Use Magisk
If you like simplicity and raw power go with SuperSU. I did try the SUHide Gui but found Magisk's version much easier and reliable.
Thanks again! That's super helpful!
Guys, Im running Tugapower and I cannot root the rom. Any of you know how to fix it? I run the zip file to root and I start to phone and looks that works but after couple of minuts is not rooted anymore. Anyone else?
Has anybody used the the latest version of superuser with oos 4.0?
That's the SR2 2.79 version. The one before turned off sims and a reflash of 4.0 sorted out.
And the info on Magisk has been informative. Thanks!
As someone who has used phhSu and SuperSU (I've also paid for SuperSU Pro) I find either do the job and that SuperSU is good for getting a ROM going while I prefer to then re-root with phhSU after I have my ROM set up for daily use, although the only annoying thing with phhSU is that TB detects the su binary as being a non-SuperSU one so it pops up an extra warning.
Either is fine, just pick the one you like better I guess.
How did you guys flash a systemless root without triggering DM-Verity?
From my understanding, we flash superSU after flashing TWRP and allowing modifications, because superSU disables/bypasses DM-Verity
Am I missing something here?
Freyelis said:
How did you guys flash a systemless root without triggering DM-Verity?
From my understanding, we flash superSU after flashing TWRP and allowing modifications, because superSU disables/bypasses DM-Verity
Am I missing something here?
Click to expand...
Click to collapse
With SuperSU 2.79 you don't need no-verity patch.
m0d hipp¥ said:
I haven't seen a thead posted about this so I figured I'd get some input from people that have used both or either of the 2 root options.
What do you prefer and why? What are the pros and cons?
I know SuperSU is very well known and I'm familiar with it from the Galaxy S phones. Magisk is fairly new, but from what I heard it works well with Nougat and the other nice thing is that magisk can be toggled.
I'm not sure if there is any benefit to that or not, but I'd like to hear some feedback.
Click to expand...
Click to collapse
Actually Magisk doesn't give root but the modded version of Phh's Superuser does.
One of the main difference is that Phh's Superuser (and Magisk) are open source. Once Chainfire will leave his SuperSU project you will have to fully trust CCMT.
A few days ago I posted a question about not being able to install any Xposed modules here, so far no one answered: https://forum.xda-developers.com/xposed/xposed-framework-installed-running-t3567230
I thought this problem had something to do with the modules specifically, but it turns out that on my phone, for whatever reason, installing the framework subsequently prevents ALL apps from installing, even those from Google Play itself, displaying a "-504" error.
I see people have asked this question before, but are also not getting answers: https://forum.xda-developers.com/xposed/install-apps-installing-framework-t3430922
Please, if anyone has any idea of why this can be and how to fix it, let me know. Any help will be infinitely appreciated!
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
Hey, thank you for your answer!
I am using a Sony Xperia M4 Aqua E2306, rom is 26.1.A.1.112 Latin America Generic. It is rooted and with TWRP installed accroding to this thread: https://forum.xda-developers.com/m4-aqua/general/root-e2306-m4-aqua-guide-t3270521
I also have a locked bootloader, and it cannot be unlocked, so unfortunately that shuts the door on most rooting options.
I never heard of Magisk before, but from what I'm seeing, it looks it TWRP is required to get root with Magisk, but some kind of root is already required on my phone in order to get TWRP. So I'm not sure how to go about this.
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Anova's Origin said:
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Click to expand...
Click to collapse
Oh well, thanks anyway. I might try it anyways, maybe it will work, you never know. Don't have much to lose at this point
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
FIY Magisk cannot hide Xposed...
I also facing these problem on my rooted Asus zenfone 2 (ze550ml 2gb ram version, Stock ROM, bootloader unlocked) and Asus Zenpad C 7 (p01y, stock rom, bootloader unlocked). The xposed firmware (version 86) is successfully install but can't install any apps from play store and using apk...
I really hope that dev team can solve it.....
Sorry for any grammatical mistakes....
The only way is to flash the firmware
I'm getting the same problem on my LG G4 with v88.2 of Xposed :/
I don't Know if this is too late,but I also have this problem. But there is a work around, go into the xposed installer and turn the switch off so its disabled on the next boot. rebot the device and exposed and its modules are disabled, allowing you to install apps from play store and downloaded .apk files... it would still be nice to install applications while its still on.
Sent from my LG-K550 using XDA Labs
I had this issue on my LGG3. This happens when you have Lucky Patcher enabled in your xposed modules. Disabling it (Lucky Patcher) should solve the problem.
Title says it all. Im currently using using SuperSU so looking for Systemless root and looking for Xposed to work as well.
Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Do I remove SuperSU thru it's manager and then flash Magisk?
riahc3 said:
Do I remove SuperSU thru it's manager and then flash Magisk?
Click to expand...
Click to collapse
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.
jhedfors said:
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.
Click to expand...
Click to collapse
This just flash Magisk? No Xposed issues?
riahc3 said:
This just flash Magisk? No Xposed issues?
Click to expand...
Click to collapse
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.
jhedfors said:
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.
Click to expand...
Click to collapse
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....
When SuperSU asked if I wanted to recover the boot image (I think it was that) I said no.
Issues with that?
Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.
Says Ive lost root....
Magisk does say it is installed.
riahc3 said:
Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.
Click to expand...
Click to collapse
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch
riahc3 said:
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch
Click to expand...
Click to collapse
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.
Didgeridoohan said:
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.
Click to expand...
Click to collapse
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed
riahc3 said:
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed
Click to expand...
Click to collapse
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.
Didgeridoohan said:
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.
Click to expand...
Click to collapse
Doesnt systemless Xposed pass SafetyNet?
riahc3 said:
Doesnt systemless Xposed pass SafetyNet?
Click to expand...
Click to collapse
No.
Didgeridoohan said:
No.
Click to expand...
Click to collapse
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.
riahc3 said:
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.
Click to expand...
Click to collapse
Magisk works fine with SuperSU. It's if you'd ever want to hide root from some process or app that you might have some trouble, since Magisk Hide is developed with MagiskSU in mind.
There are some banking apps, Android Pay, Pokemon Go other apps that utilise SafetyNet. I do believe that more and more apps will use in the future and the cat and mouse game of hiding root is gonna continue...
riahc3 said:
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....
Click to expand...
Click to collapse
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks
anshulsingh said:
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks
Click to expand...
Click to collapse
I use Xposed modules in my daily life and cannot afford to be without them.
I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer
akash.galaxy07 said:
I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer
Click to expand...
Click to collapse
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know
manor7777 said:
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know
Click to expand...
Click to collapse
Thanks bro, and, is it stable too? I mean, are there any risks involved?
akash.galaxy07 said:
Thanks bro, and, is it stable too? I mean, are there any risks involved?
Click to expand...
Click to collapse
There are risks with any kind of root on your phone, as an app developer, you should know that.
You could get a virus that takes advantage of root to encrypt all of your files.
Again, you should know this if you are an app developer, there is a difference between creating a single app, and developing applications as a whole!
Magisk is very stable though, more so on OxygenOS but it will be pretty stable with LineageOS too! I have had no problems whatsoever! I have been using android pay and all my root apps without my phone ever crashing! And if you are careful, you won't get a virus (root will not cause a virus, user stupidity gets virus') - enjoy
I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.
Didgeridoohan said:
I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.
Click to expand...
Click to collapse
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.
vipivj said:
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.
Click to expand...
Click to collapse
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.
Didgeridoohan said:
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.
Click to expand...
Click to collapse
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?
vipivj said:
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?
Click to expand...
Click to collapse
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.
MagiskHide
You can use apps like Android Pay or Snapchat on a rooted device
Didgeridoohan said:
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.
Click to expand...
Click to collapse
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?
vipivj said:
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?
Click to expand...
Click to collapse
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...
Didgeridoohan said:
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...
Click to expand...
Click to collapse
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along ?
vipivj said:
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along
Click to expand...
Click to collapse
Ah... Ok. Those kind of issues are easy to work around and the next version of Tasker will have official MagiskSU support.
Use Magisk Manager
I also used Magisk Manager in my old device at it worked fine and as magisk allow you to root Android without effecting on system files I could also install root unsupported apps as well. So i think Magisk is the best solution for you.
link deleted by Moderator due to untrustworthy site will be a help full site to gather more info about magisk from one place.
Topjohnwu has strictly stated that any website which spreads Magisk is not official and cannot be trusted. The only official place is the XDA Thread. If you see any Member promoting an external site related to Magisk, please report the post.
Hi there,
I'm in the process of deciding whether to root my next phone with Magisk or SuperSU. The point I want to discuss here is the risk of bricking the phone. I found rather little information on how Magisk actually links into the system, but it seem that it modifies the /boot image. Now my concern is that if anything goes wrong with this, the phone may be bricked with no return. If I compare this to installing SuperSU to /system, if something goes wrong with that, I still have a working boot loader to boot into recovery and install a working system image. But if /boot is damaged, there should be no return.
So my question: is my understanding of how Magisk works correct, and does this mean higher risk of bricking the device?
Thanks
Tom
I use Magisk for 1 month and I have no problems. Even that Magisk is much better than SuperSU because you can hide the root for your applications.
The boot.img is not your bootloader, it's basically the kernel (part of it anyways). Reflashing your stock boot.img and wiping data would likely reverse anything magisk does. So risky? Not if you backup your stock boot first in twrp. But we backup everything before we flash anything right? Magisk is doesn't modify system at all, everything it does is in /data (besides patching boot.img)
So the question becomes, do you need to pass safetynet for any reason? And would you like to be able to take ota updates?
madbat99 said:
The boot.img is not your bootloader, it's basically the kernel (part of it anyways). (...)
Click to expand...
Click to collapse
Thanks for the clarification. That basically answers my question!
You can use magisk it safe
The best feature of magisk you can hide root from other app like pokemon go, banking app etc
And also you can modify the the system make some app system app or uninstall system without modification of system
And lots more for more details check the magisk official thread
And ya don't download magisk from magisk.com or other site it not offical
I am using magisk in miui rom, Samsung note 4
Moto G5 plus without any problems
can i use magisk on rokit io pro 3d?