how to switch from super su to magisk? - OnePlus 3T Questions & Answers

Hello, I am currently rooted on stock oos 4.0.3, with latest TWRP and super su free v2.79, can anyone help me out and tell me how to switch to magisk please, thank you!
Can I just use super su full unroot option then flash magisk?

Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.

palesaint said:
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
Click to expand...
Click to collapse
so flash unsu, then flash magisk. simple?

Dr Grato said:
so flash unsu, then flash magisk. simple?
Click to expand...
Click to collapse
If you use the unSU script the process is:
unSU
stock boot image
Magisk

This method did not work for me.
I am on KETAN n10 and initially, viper did not work. I installed magisk but that didn't fix it. nor the meefik busy box. So i decided to uninstall magisk and go back to superSU and it magically worked...

I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:

SourPower said:
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
Click to expand...
Click to collapse
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?

JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
If there's a proper backup of the boot image for the SuperSU app's full unroot option to restore, then that process should work perfectly (I've done it on a few devices myself). It's when it can't properly restore the boot image you might have issues and you'll have to do it yourself.
Take a look in the Magisk Troubleshooting guide, under "Moving from another systemless root solution to MagiskSU".

The nuclear method might be, to just flash the full stock OOS zip (can flash in TWRP) which will unroot and restore the boot.img (and everything else!). Then immediately flash Magisk before rebooting (so have the Magisk zip on the phone before updating). This should fully remove SuperSU, install Magisk, and keep TWRP on the phone.
Seeing as the original poster is still on OOS 4.0.3, you may want to update, anyway!

JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
I've done this on my 3t but I do have a G3 coincidentally lol, but yes I unrooted from su, it restarted my phone, before booting back into the system I went in twrp right away and then flashed magisk.

There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?

hypothrax said:
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
Click to expand...
Click to collapse
I chose the Full Unroot option. Then flashed magisk. Worked perfectly.

Use the full unroot option. Catch here is that you might get dm-verity warning. It won't affect the phone in anyway but Android Pay might not work and you will see the warning for 5 seconds, everytime you restart the phone.

Thanks so much for ths thread. I am on Resurrection Remix OS and inititally installed SuperSU over Magisk (which came with the ROM). I decided that I wanted to use Magisk instead and followed the instructions in this thread and it worked a treat.

Related

After installing magisk, root not working

After installing the magisk as I was rooted, I installed 2-3 mods ie flashed in twrp but after I rebooted my root is gone. Magisk manager is showing not rooted and when I re flashed supersu in twrp, installation was successful but still no root. What happened I don't know. Also I didn't install any phh supersu or busybox. Please help me regain my root.
HELP
It was a known bug in Magisk that you would lose root.
Magisk
v10.2
- [Magic Mount] Remove apps/priv-app from whitelist, should fix all crashes
- [phh] Fix binary out-of-date issue
- [scripts] Fix root disappear issue when upgrading within Magisk Manager
Click to expand...
Click to collapse
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
brichardson1991 said:
It was a known bug in Magisk that you would lose root.
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
Click to expand...
Click to collapse
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Vaibhunk786 said:
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Click to expand...
Click to collapse
After installing from play store, did you "FLASH" magisk ?
brichardson1991 said:
After installing from play store, did you "FLASH" magisk ?
Click to expand...
Click to collapse
No I didn't flash anything. It was an automatic process which installed magisk and prompted me that installation success and reboot. Then I rebooted and root was gone
Now should I run magisk unstaller zip in twrp followed by supersu and then again flash magisk v10. 2 via twrp.. Should I follow these steps to gain my root again.. Anyone please help. I'm stuck @brichardson1991
Try installing PHH superuser from play store.
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Same problem here, have to investigate whats going on.
MattBooth said:
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Click to expand...
Click to collapse
yeah flashing the stock rom was the only viable option i think .
I have the same problem with latest magisk. After i installed mods root is gone and i can not root again. Only with supersu i have root. Magisk is very bugy.
Yeah it does appear the latest version now causes you to lose supersu
Same problem with me, on the OP3 running Open Beta 11. Reflashing SuperSU did not work. Rather than extract the boot.img to reflash that, I ended up reflashing the firmware (and ended up mistakenly using the 4.0.1 file instead of the OPB11 one!) ... Yet to try SuperSU and Magisk again on this, but figured better to investigate the issue before I attempt to reinstall.
From what I understand here, v10 won't have this problem, and its only on v11 that its cropped up again? Can anybody with v10 confirm this?

snapchat fail login after root?

Hey everybody I rooted my device this morning, and I was setting everything up again since it gets wiped during the process. So finally I come and try to login in to Snapchat and it says something similar to "log in has failed please try again later" anybody have this problem or a way to fix it? Thanks in advance!
Snapchat checks for root and purposely prevents you from logging in if it find it. If you rooted with SuperSU, try installing Chainfire's SUHide. Otherwise, if you rooted with Magisk, enable MagiskHide in Magisk Manager.
I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.
martinsavvy said:
I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.
Click to expand...
Click to collapse
so i just do the full unroot option, sign in, then just flash the SU again?
sakumaxp said:
so i just do the full unroot option, sign in, then just flash the SU again?
Click to expand...
Click to collapse
Yeah that's what works for me.
martinsavvy said:
Yeah that's what works for me.
Click to expand...
Click to collapse
OMG thank you so much that was so easy!!!!
magisk is better though because you can still use android pay and mobile banking applications.
If I throw on a custom ROM after wiping will I need to do this process again?
Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.
Anova's Origin said:
Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.
Click to expand...
Click to collapse
I shouldnt brick if i have to loose root and reflash super SU when I'm running a rom right? Sorry for all the questions
Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.
Anova's Origin said:
Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.
Click to expand...
Click to collapse
Yeah cos I would need to flash the ROM, then sign in to Snapchat, then go back to TWRP and flash super SU
Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you dirty flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. ROMs like OOS will either replace TWRP with stock recovery or trigger dm-verity if you don't root immediately after clean flashing.
Anova's Origin said:
Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. You might trigger dm-verity if you clean flash a ROM like OOS without rooting before booting.
Click to expand...
Click to collapse
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?
sakumaxp said:
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?
Click to expand...
Click to collapse
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.
Anova's Origin said:
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.
Click to expand...
Click to collapse
I'm on stock ROM, so I guess I can go into super su and loose root then download magisk and get it that way
Thanks mate, it took forever to find this solution, it worked!
I use SU and it was simple to "unroot" from within the SU# app
1. settings scroll down to the "cleanup" section, select full unroot, accept all the warning messages, the phone will reboot into recovery and then reboot the phone after it finishes. Your phone may cycle through the reboot process a couple of times
2. log back into your phone, then you can log into the Snapchat app.
3. now you can re-root your phone, if you want to.
Cheers.

Help in sideloading custom ROM from ADB

Hey everyone. I just got my new OnePlus 3T a week back. I was loving it till today but I wanted to mess with my phone and I guess I did just that. Long story short, I was on 7.1.1 and unlocked OEM and installed TWRP. Phone booted up and i went into recovery and installed Super SU and the dm verity. After this step, my phone is stuck on the boot animation. I'm able to access TWRP as well as Fastoot ADB. I want to sideload the stock OxygenOS ROM into my phone through ADB, but i'm unsure which file to flash and the exact process. Could someone please help me out? :crying:
That's why you always make a nandroid back up
I figured out why the adb sideload wasn't working. I tried to do the sideload directly from the ADB cmd while my phone was in fastboot mode. So, I tried an alternate method by going into TWRP and doing the sideloading from the advanced menu. It worked and I'm setting up my OP 3T now Guess I jumped the gun by posting here without thinking.
On a side note, my device doesn't have root access now. Maybe it never got installed properly before getting bricked. I think it had to with the fact that I had updated to 7.1.1 by using a VPN. I'm pretty good at following instructions so i couldn't have gone wrong. Can anyone tell me if i can go ahead and root my device now that I'm back on stock OS?
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
kunal1540 said:
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
Click to expand...
Click to collapse
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Rahulsingh9367 said:
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Click to expand...
Click to collapse
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
fluster84 said:
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
Click to expand...
Click to collapse
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Azar_98 said:
Try the latest version of magisk, v11.6.
http://tiny.cc/latestmagisk
Click to expand...
Click to collapse
Worked perfectly and no hassle at all. Thank you so much!
Rahulsingh9367 said:
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Click to expand...
Click to collapse
Always flash the latest magisk, and you don't need to flash phh or anything else. Magisk now comes with magisksu that works great with OOS 4.1.1.
Check the link below for latest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless
If you don't mind losing your data, you can try this 100% clean but slightly painful install. It might be overkill for most but you can start from a clean slate. Backup your stuff to the PC before you do this.
1. Flash compatible stock recovery (stock recovery for android N) in fastboot
2. Now choose to wipe everything (even music, photos) from stock recovery. You will lose everything on your phone.
3. Sideload OOS 4.1.1 rom
4. Reboot and complete phone setup
You are now completely stock except with a unlocked bootloader. In order to gain root, continue further -
5. Enable developer options in Settings and then enable Advanced Reboot and USB debugging
6. Reboot to fastboot and flash twrp 3.0.4.-1
7. Reboot to twrp and flash Magisk v11. 1 zip
8. Reboot and install Magisk Manager from playstore.
Congratulations, you have a stock 4.1.1 with working root and it will even pass safety net check (enable magisk hide in magisk manager)

How to remove SuperSU after having installed Magisk?

So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?
Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.
thany2 said:
So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?
Click to expand...
Click to collapse
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk
Dirty flash should remove all su or magisk, then you can install magisk again
abacate123 said:
Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.
Click to expand...
Click to collapse
Uninstalling Magisk results in a boot loop, like I said. So it's a no-go.
What other reasons could it have when SafetyNet doesn't pass with that error message?
tropicanapure said:
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
SuperSU has that option greyed out because of a locked binary, like I said, so that won't solve anything.
adekboreanaz said:
Dirty flash should remove all su or magisk, then you can install magisk again
Click to expand...
Click to collapse
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.
thany2 said:
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.
Click to expand...
Click to collapse
No it is not, dirty flash is flashing your rom again without deleting /system /data partition, that can replace your boot.img with the stock one, so the supersu will be disappeared
reflash boot.img from the rom you used via twrp on img mode (click zip or img to switch between modes) or reflash your desired custom kernel.

Magisk manager v13 not working

I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Jô$èph D said:
I have a blu r1 hd custom build v6.5 I have tried to install magisk manager (i have rooted with super su) but it fails every time I try I get an error message I'm the app and in TWRP I just want to know if anybody else has this problem and if there is any way to solve it
Click to expand...
Click to collapse
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
Ok then ill give it a shot
freespeechdev said:
I believe Magisk dropped SuperSu support at some point before v13. Magisk now includes its own systemless root solution, so SuperSu is not needed. Try uninstalling Magisk and SuperSu and flashing the latest 13.3 zip.
Click to expand...
Click to collapse
I need to get stock boot img I don't have it pls help
Jô$èph D said:
I need to get stock boot img I don't have it pls help
Click to expand...
Click to collapse
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Can you pls link me the post for that file
freespeechdev said:
Two options:
If you have a pre-supersu/Magisk backup, restore it (at least the boot part).
If you don't have a backup (I encourage you to make them in the future...):
You need to go to the forum post with the fixed prime 6.5 zip downloads. Download the ~1gb zip, unzip it, and grab the boot.img from there. Flash it in twrp by going to install, install image (bottom right). Choose boot. When the flash finishes, reboot to recovery and flash Magisk.
Click to expand...
Click to collapse
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks
Jô$èph D said:
Never mind man. I can't say thank you enough I found the stock ROM with the info you gave me. Flashing boot.img was successful and so was flashing the Magisk.zip again thanks and I will stay active on this and other threads
Click to expand...
Click to collapse
Sure thing. See you around!
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
I wanted to use systemless xposed framework because the official version is not supported on my device. Also I wanted to use the modules that are specifically for magisk
yaconsult said:
Why would someone use Magisk instead of traditional root? Are there some apps that you need to use that won't work on the rooted phone? I guess that there are a few, like snap chat and maybe Netflix but I don't use those on the Blu R1 HD.
I followed Colton's original root thread and while he, at first, included Magisk, he later advised switching to the non-Magisk root and I did. What would I gain by switching back to Magisk?
Click to expand...
Click to collapse
Systemless xposed does not work either found this out earlier today device would not boot after installation of xposed through magisk
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
yaconsult said:
Ah, that would be a problem for me. I wouldn't want to use a phone without xposed. I have to have all the tweaking and customizations available in gravitybox and a few other modules.
So what will you do now? Give up xposed or Magisk? Or try to find or wait for a version of xposed that works on Magish?
It was a long time ago, but I think I remember running into problems running xposed on Magisk and Colton provided some helpful advice in his original thread about reflashing the rom, getting root, then installing xposed - he had seperate threads for those.
Click to expand...
Click to collapse
I will have to see if it works when a new version of magisk is launched.

Categories

Resources