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.
Related
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?
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.
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.
Thought I'd share how I upgraded my T-Mobile Galaxy S6 to Nougat (G920TUVU5FQE1 ) with root, deep sleep and SafetyNet bypass.
*** Read all step before starting as you will need to download and copy several files to your phone first ***
NOTE: This method will trip Knox!
Reboot into Download Mode
Flash G920TUVU5FQE1_G920TTMB5FQE1_G920TUVU5FQE1_HOME.tar.md5 with Odin (I used v3.10.6)
Download from Android File Host | Google Drive.
Reboot into Download Mode
Flash TWRP img.tar with Odin
Flash Magisk zip with TWRP and reboot to system
Install Magisk Manager (and enable Magisk Hide in Magisk Manager settings)
NOTE: The steps below will re-enable Deep Sleep
Install Flashify
Flash stock recovery.img with Flashify
Download from Android File Host | Google Drive.
Wipe cache (twice for good measure) and reboot
(Optional) Flash TWRP img using Flashify and reboot to system
Enjoy Nougat with root and SafetyNet bypass on your G920T! :good:
You do know that Google pulled Magisk from the Play Store....
The Sickness said:
You do know that Google pulled Magisk from the Play Store......
Click to expand...
Click to collapse
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
KaneHusky said:
You do know that was inevitable and that there are other ways to obtain Magisk Manager?
Click to expand...
Click to collapse
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
The Sickness said:
Of course there are other ways......But your posting a link to Magisk that doesnt exist.
Click to expand...
Click to collapse
Uh... I linked to the main Magisk thread on XDA, not Google Play.
KaneHusky said:
Uh... I linked to the main Magisk thread on XDA, not Google Play.
Click to expand...
Click to collapse
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
The Sickness said:
Uhh.....thats because you just changed it. I'm not gonna waste my time posting about something that is'nt correct.
So have a very lovely day
Click to expand...
Click to collapse
Wow. Ok, dude. Do you see an edit anywhere for my post? No. I specifically linked to the XDA thread because I know it was taken off Google Play. :good:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
BigDaddy38 said:
Gonna give this a shot. Is this an official build or a port? And i wonder if i can use @stangdriver44 V4A Aroma installer hmmmmmm. Is the kernel stock or set to permissive?
Click to expand...
Click to collapse
It's pulled straight from Smart Switch so everything is 100% stock.
KaneHusky said:
It's pulled straight from Smart Switch so everything is 100% stock.
Click to expand...
Click to collapse
Sweet gonna give it a shot, Thankyou!!!!
i have no idea where to find magisk manager any help would be appreciated
BigDaddy38 said:
i have no idea where to find magisk manager any help would be appreciated
Click to expand...
Click to collapse
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
KaneHusky said:
There's a Downloads section with a direct link to it in the main Magisk thread which I linked to.
Click to expand...
Click to collapse
Your right i found it, the link didnt work earlier when i tried thankyou
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
EncryptedCurse said:
Do we not need to flash SuperSU prior to Magisk? I'm not too familiar with the process so I could be mistaken.
Click to expand...
Click to collapse
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
crashff said:
It seems kinda... excessive to put TWRP on, then go back to the stock recovery, then back to TWRP again.. Is there a reason for this part?
-> Flash stock recovery.img with Flashify
-> Wipe cache (twice for good measure) and reboot
-> (Optional) Flash TWRP img using Flashify and reboot to system
Click to expand...
Click to collapse
Yeah, to fix deep sleep not working after the first TWRP flash.
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
BigDaddy38 said:
Heres what I did lastnight.................I followed your setup. And then installed Noble Kernel set to permissive so i can run V4A. Well the kernel trips Safety Net and you get a continuous notification because of the permissive kernel. So I uninstalled magisk(I dont care for it till the dev keeps it updated for us). I then flashed Super SU 2.8+ through TWRP. Used @stangdriver44 V4A Aroma Installer. So you still get the security notification, I found that system app and froze it. No more annoying notification. This is where im at now. Stock Nougat Rooted w-SuperSU/Noble Kernel for Tmobile/Viper 4 Android. All working flawlessly. @The Sickness Are you gonna maybe try and get something going on nougat with that sickness. Maybe an S8 themed option. I bet between you and stangdriver44 it could be awesome. Because you know we probably wont get another Rom upgrade for the S6 after Nougat.
Click to expand...
Click to collapse
Read my rom thread and kernel thread.
KaneHusky said:
You don't have to, no. Magisk uses its own superuser called MagiskSU, which gets installed with the Magisk zip file.
Click to expand...
Click to collapse
Everything was working fine last night, but I seem to have lost root during some point today. Magisk Manager still says that Magisk is installed, but that I am "not rooted." Any ideas? Should I try to reflash Magisk or will that trip SafetyNet?
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
organicloot said:
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
Click to expand...
Click to collapse
You can update it from Magisk and as well as from TWRP...
organicloot said:
First of all, I have very limited android experience but I need too root my phone for the functionality of an app that's critical to my business. Anyways, I'm running a Moto x4 with Pie. I already installed magisk 17.3 and magisk manager 6.0.1 using twrp recovery following a tutorial on youtube. When opening the magisk manager, it asked me to update to 7.1.1, which I did. Then it told me that I needed at least v18.0 magisk to be able to run the new magisk manager. Am I able to update magisk by flashing the new zip version in twrp, or is another method required since a prior version is already installed? Is this how I would install all future versions of magisk that comes out? Is there anything that I should know before flashing? I really don't want to get stuck in a boot loop or brick the phone.... Any guidance will be greatly appreciated.
Click to expand...
Click to collapse
First of all: backup! Then you can bootloop, brick (or not!) with no worries. Do it with twrp.
Download latest (beta) Magisk 19.0, flash it under twrp and be happy.
Just to add to the above....
Since you're already rooted you don't have to flash the zip in TWRP. Just go to the Magisk Manager Modules section, click the "+"-button and select the Magisk zip. When it's done, reboot and you're updated.
Shubham259 said:
You can update it from Magisk and as well as from TWRP...
Click to expand...
Click to collapse
I'm not able to open manager because it says I need at least v18.0. The app wont open.
Didgeridoohan said:
Just to add to the above....
Since you're already rooted you don't have to flash the zip in TWRP. Just go to the Magisk Manager Modules section, click the "+"-button and select the Magisk zip. When it's done, reboot and you're updated.
Click to expand...
Click to collapse
If it's in the manager app, I'm not sure how to do it because it says that I can't open it with anything <v18.0.
wilsonhlacerda said:
First of all: backup! Then you can bootloop, brick (or not!) with no worries. Do it with twrp.
Download latest (beta) Magisk 19.0, flash it under twrp and be happy.
Click to expand...
Click to collapse
Good news! The flash has been successful. And I learned about NANDroid backups. Super helpful! Thanks for the help!!
organicloot said:
If it's in the manager app, I'm not sure how to do it because it says that I can't open it with anything <v18.0.
Click to expand...
Click to collapse
You could of course uninstall the incompatible Manager and reinstall the one that works with your Magisk version.
But, that's now besides the point.
A day when you learn something new is a good day. :good:
If you want to learn more, here's a trivia [emoji14]
Also install "Magisk Manager for Recovery Mode (mm)" module. Not promoting it, but I myself feel it's a good module that you need to have before playing with Magisk Modules
It allows you to manage Magisk Modules from TWRP itself. So next time you run into a bootloop, you know what to do
Sent from my #FlagshipKiller3T using Tapatalk