Excuse me for my ignorance or if someone else has already pitched this error, I tried to look but I couldn't find anyone experiencing the same problem.
I am using this post FROM STOCK 6.0.1. for reference.
I successfully flashed CataclysmMOD + ElementalX using TWRP. I reboot after each flash to be certain that none of these files are causing me any issues, which they are not.
However, as soon as I flash superSU 2.6.4 & reboot to system, I get the message "Unfortunately, Phone and Messaging storage has stopped". I also get this message for youtube, hangouts, play store, and even settings...
On top of that, it also does NOT recognize my sim card & I no longer get data connection, though it was working perfectly fine on CataclysmMOD & ElementalX before the superSU Flash.
I followed nathanchance's post word for word and it still doesn't work. What can I do to get superSU working?
Sorry, wrong forum. I meant to post in troubleshooting
amhoot said:
Excuse me for my ignorance or if someone else has already pitched this error, I tried to look but I couldn't find anyone experiencing the same problem.
I am using this post FROM STOCK 6.0.1. for reference.
I successfully flashed CataclysmMOD + ElementalX using TWRP. I reboot after each flash to be certain that none of these files are causing me any issues, which they are not.
However, as soon as I flash superSU 2.6.4 & reboot to system, I get the message "Unfortunately, Phone and Messaging storage has stopped". I also get this message for youtube, hangouts, play store, and even settings...
On top of that, it also does NOT recognize my sim card & I no longer get data connection, though it was working perfectly fine on CataclysmMOD & ElementalX before the superSU Flash.
I followed nathanchance's post word for word and it still doesn't work. What can I do to get superSU working?
Sorry, wrong forum. I meant to post in troubleshooting
Click to expand...
Click to collapse
If you don't need systemless root use SSU 2.52. I have exact the same setup as you except that i use SSU 2.52. Android pay doesn't exist where i live so i don't care about systemless root
Droidphilev said:
If you don't need systemless root use SSU 2.52. I have exact the same setup as you except that i use SSU 2.52. Android pay doesn't exist where i live so i don't care about systemless root
Click to expand...
Click to collapse
Is there a way to go back to the point where I had Cataclysm + EX working without going back to stock and doing everything all over again?
Thanks for the quick reply!
amhoot said:
Is there a way to go back to the point where I had Cataclysm + EX working without going back to stock and doing everything all over again?
Thanks for the quick reply!
Click to expand...
Click to collapse
Well... i guess if you started from a stock factory image you might have to do it again, yes (to be sure). Still there's a way to completely uninstall supersu system (you need to flash unsu for this) or systemless (you have to delete some files). What i would do is start over but instead of using a full stock image i would use Tupac4u. This rom is stock but debloated and can be flashed in TWRP. I tried to read what caused your problem as others reported this too but no cause was posted.
In TWRP:
-flash Tupac
-flash Cata MOD (!!!)
-flash Ex (i disable selinux enforcing for various reasons)
-flash ssu
In this order.
Rom:
http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
Droidphilev said:
Well... i guess if you started from a stock factory image you might have to do it again, yes (to be sure). Still there's a way to completely uninstall supersu system (you need to flash unsu for this) or systemless (you have to delete some files). What i would do is start over but instead of using a full stock image i would use Tupac4u. This rom is stock but debloated and can be flashed in TWRP. I tried to read what caused your problem as others reported this too but no cause was posted.
In TWRP:
-flash Tupac
-flash Cata MOD (!!!)
-flash Ex (i disable selinux enforcing for various reasons)
-flash ssu
In this order.
Rom:
http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
Click to expand...
Click to collapse
Thank you so much! I went ahead and just flashed from stock again. I will try 2.5.2 as you said!
What I did to get back on track:
- uninstall supersu 2.64 from the app;
- flashed UNsu.zip in recovery (google it);
- flashed 21 Dec Beta;
- flashed supersu 2.52;
- (optional) flash custom kernel ( i use now elite kernel and is really awesome )
That's it. Hope it helps. At least it worked for me.
amhoot said:
Is there a way to go back to the point where I had Cataclysm + EX working without going back to stock and doing everything all over again?
Thanks for the quick reply!
Click to expand...
Click to collapse
Ususaly after you flash a custom rom and kernel you need to unroot with the superSUunroot.zip (here on XDA) and after that flash superSU 2.64 systemless zip file. That should eliminate issues.
gee2012 said:
Ususaly after you flash a custom rom and kernel you need to unroot with the superSUunroot.zip (here on XDA) and after that flash superSU 2.64 systemless zip file. That should eliminate issues.
Click to expand...
Click to collapse
Or delete supersu from the rom zip before flashing
Still in this case: Cata isn't rooted so there is nothing to unroot after flashing.
I guess OP used the echo command to force systemless root and that went wrong, but not sure.
That didn't work for me. As I understand in order to get rid of all errors supersu 2.64 should be flashed using a command in TWRP. Otherwise it brings errors. If there is the need for Android Pay then I recommend flashing 2.62-3 which works ok with no errors.
yep, flashing to 2.5.2 instead of 2.6.4 fixed the problem, thanks all!
Related
Hey,
I've been getting constant Magisk Manager crashes every time I try to run it even after multiple "full wipes" (except internal sdcard data) and I can't even get the logs because it doesn't let me access them and there's no folder with logs in them. What am I supposed to do? I already flashed the stock kernel and it didn't fix it. My ROM is the XtreStoLite and I'm using a Galaxy S6 920F. What could be causing it to crash even after "full" wipes?
Thanks
EDIT: Additionally, I can install Magisk without any problem in recovery but whenever I try to run an app that requires root rights, it shows the "Magisk Manager stopped working" error
I just did a complete wipe of literally everything I had on my phone, internal storage included and installed the rom back and magisk manager still crashes... what the hell?
Edit: Installed a logcat app to look at the logs when it crashes and here is the important part, I think:
E/AndroidRuntime(13780): Process: com.topjohnwu.magisk, PID:13780
E/AndroidRuntime(13780): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.topjohnwu.magisk/com.topjohnwu.magisk.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
Click to expand...
Click to collapse
Edit 2: Alright I've no idea what's wrong but v4.1 works fine, v4.2 crashes all the time even though it was working literally yesterday. Welp, whatever
Im on Resurrection Remix and when I install a Rom update, the managers "loses the root" too, I download the zip (and flash it) again and its a lucky strike if when the phone reboots, the magisk returns to normal and regain the root.
GolpeadorMágico said:
Im on Resurrection Remix and when I install a Rom update, the managers "loses the root" too, I download the zip (and flash it) again and its a lucky strike if when the phone reboots, the magisk returns to normal and regain the root.
Click to expand...
Click to collapse
That does not sound like the issue in the OP...
After a ROM update you'll have to flash the Magisk zip again, since the ROM most likely also updates the boot image, thus removing the Magisk modifications (including MagiskSU).
Didgeridoohan said:
That does not sound like the issue in the OP...
After a ROM update you'll always (well, almost) have to flash the Magisk zip again, since the ROM most likely also updates the boot image, thus removing the Magisk modifications (including MagiskSU).
Click to expand...
Click to collapse
So you are saying that I have to flash it in the same process, all together*, not flash, reboot and later flash the magisk zip?
*(Flash> mount rom zip+gapps+magisk)
GolpeadorMágico said:
So you are saying that I have to flash it in the same process, all together*, not flash, reboot and later flash the magisk zip?
*(Flash> mount rom zip+gapps+magisk)
Click to expand...
Click to collapse
You can boot up after updating, to make sure it's working and then flash Magisk. Doesn't really matter...
I usually flash the update, custom kernel and lastly Magisk zip, all in one go.
Didgeridoohan said:
You can boot up after updating, to make sure it's working and then flash Magisk. Doesn't really matter...
I usually flash the update, custom kernel and lastly Magisk zip, all in one go.
Click to expand...
Click to collapse
Oks. that´s is how I usually do it. I´m going to try again.
Guys, I´m sorry for the double post but I reinstaled it and nothing, the magisk managers says that the phone is not rooted.
***NEW: The problem is busybox. Uninstall it, reinstall magisk and problem solved.
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.
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)
So, I am on stock 7.1.1 - N6F27C no-root.
-- have unlocked bootloader & latest TWRP installed.
I am wanting to root, but not have SU.... and not really sure how to accomplish that.
-- do i use the Unified Toolkit in "original development" ?
What I am wanting to accomplish:
- Load PureNexus
- use Magisk (to hide root from PokemonGo, and AndroidPay)
I've seen people talk about un-SU, which i don't anything about, as i haven't rooted or modded a phone since my note3, so I am kind of in the dark here.
UPDATE -- after some reading this seems to be what i need to do.... right?
Reboot to twrp
Make backup
Wipe system, data, cache, and dalvik cache.
Flash PureNexus
Flash BeansGapps
Flash Magisk
Flash FrancoKernel & Reboot
Install Magisk Manager & update
is that all correct? (to have PoGo & Pay working?)
Ph0z3 said:
So, I am on stock 7.1.1 - N6F27C no-root.
-- have unlocked bootloader & latest TWRP installed.
I am wanting to root, but not have SU.... and not really sure how to accomplish that.
-- do i use the Unified Toolkit in "original development" ?
What I am wanting to accomplish:
- Load PureNexus
- use Magisk (to hide root from PokemonGo, and AndroidPay)
I've seen people talk about un-SU, which i don't anything about, as i haven't rooted or modded a phone since my note3, so I am kind of in the dark here.
Click to expand...
Click to collapse
If you want to use Magisk, then flashing Magisk will root your device using phh's root. Just download Magisk and flash. Of course, read through the original post and at least the last several pages of the thread.
If you flash PN, beans-gapps (as specified by PN), then Magisk in the same flash que then boot, you should be good to go. The first 4 posts of the PN thread helps with installation instructions.
The primary reason to use osm0sis' unsu.zip is to remove an existing root prior to replacing it with a different one. Not necessary if you're flashing a new ROM, since you'd lose root anyway. Switching roms should always be a clean flash (system, cache, dalvik - not user data which holds your "sdcard" stuff).
ktmom said:
If you want to use Magisk, then flashing Magisk will root your device using phh's root. Just download Magisk and flash. Of course, read through the original post and at least the last several pages of the thread.
If you flash PN, beans-gapps (as specified by PN), then Magisk in the same flash que then boot, you should be good to go. The first 4 posts of the PN thread helps with installation instructions.
Click to expand...
Click to collapse
awesome!
thank you for the rapid reply. :highfive: :good:
Ph0z3 said:
awesome!
thank you for the rapid reply. :highfive: :good:
Click to expand...
Click to collapse
You're welcome. See the edit I made to add info.
ktmom said:
You're welcome. See the edit I made to add info.
Click to expand...
Click to collapse
ok, so lemme make sure i got this 100%
Reboot to twrp
Make stock backup
Wipe system, data, cache, and dalvik cache.
ALL IN ONE QUE:
Flash PureNexus
Flash BeansGapps
Flash Magisk
Flash FrancoKernel & Reboot
Install Magisk Manager & update
I also want to point out, IMHO, hold off switching kernels until you have stuff set up. Then do a backup, flash your new kernel and Magisk again (after the kernel). That's the safest way to keep things headed the right direction.
Flashing Magisk gives you the manager as well.
ktmom said:
I also want to point out, IMHO, hold off switching kernels until you have stuff set up. Then do a backup, flash your new kernel and Magisk again (after the kernel). That's the safest way to keep things headed the right direction.
Flashing Magisk gives you the manager as well.
Click to expand...
Click to collapse
good point.
alright, well i will hold untill i have it all squared and setup, then flash Franco after im all restored and good to go.
thank you again! you kick ass!
Ph0z3 said:
Flash PureNexus
Flash BeansGapps
Flash Magisk
Flash FrancoKernel & Reboot
Install Magisk Manager & update
Click to expand...
Click to collapse
One thing to add. If you install Franco Kernel after flashing Magisk, you'll lose root since Magisk modifies the kernel. Flash Franco Kernel after flashing Beans GApps, then flash Magisk and boot.
one last question...
what about xPosed?
I used to use Amplify a while ago & would like to use that again... will that work with Magisk?
Ph0z3 said:
one last question...
what about xPosed?
I used to use Amplify a while ago & would like to use that again... will that work with Magisk?
Click to expand...
Click to collapse
Xposed doesn't work on nougat. You'll need to go back to marshmallow.
ktmom said:
Xposed doesn't work on nougat. You'll need to go back to marshmallow.
Click to expand...
Click to collapse
Well poo... Anyhoo thank you for all the help.
Personally, I wouldn't bother with Xposed, but to each his own.
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.