I use Magisk since years and my devices got always rooted after its installation, but today it's differenti ad you may see in the attached pic...
I've G8441 and I installed Lineage 16, I'd even like to have root access!
Waiting for your advices to solve my problem!
You need to give more details than that. What have you done and what was the result?
Take a look here:
https://www.didgeridoohan.com/magisk/MagiskHelp
I installed Magisk via TWRP, I can't provide any log but installation ended in the good way (no error) but Magisk is not installed.
I flashed Magisk before ROM and gapps, I rebooted after that and then I installed the rest (ROM and gapps).
That's still quite slim, information-wise...
But, if you flashed your ROM after Magisk there's a good chance that Magisk got overwritten with the stock ROM boot image. And if the LOS addon.d glitched (there's been issues with v2), you'd end up with no root.
Magisk goes last when installing.
Didgeridoohan said:
That's still quite slim, information-wise...
But, if you flashed your ROM after Magisk there's a good chance that Magisk got overwritten with the stock ROM boot image. And if the LOS addon.d glitched (there's been issues with v2), you'd end up with no root.
Magisk goes last when installing.
Click to expand...
Click to collapse
Knowing that Magisk needs to be the last during installation is good! Gotta try this!
Many thanks Didgeridoohan!
Related
Hi, I'm using Magisk on my LG G2 with RessurectionRemix 5.7 and am looking to update to the Nougat version 5.8. I want to start clean, so will wipe system before the update, but will I have to flash Magisk again after that? What are the steps here, flash the ROM + gapps, unroot, flash Magisk?
de.er said:
Hi, I'm using Magisk on my LG G2 with RessurectionRemix 5.7 and am looking to update to the Nougat version 5.8. I want to start clean, so will wipe system before the update, but will I have to flash Magisk again after that? What are the steps here, flash the ROM + gapps, unroot, flash Magisk?
Click to expand...
Click to collapse
Yep that should be about it. To be sure try safetynet after unrooting and after magisk
guessingagain said:
Yep that should be about it. To be sure try safetynet after unrooting and after magisk
Click to expand...
Click to collapse
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
de.er said:
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
Click to expand...
Click to collapse
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
The Flash said:
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
Click to expand...
Click to collapse
Was suspecting this might be the case, thanks for clarifying this. At least I know all the steps now, should be only getting more familiar with every flash
de.er said:
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
Click to expand...
Click to collapse
afaik Resurrection Remix has addon.d (check if /system/addon.d exists)
you can test this https://github.com/osm0sis/GN-Synap...mdisk/res/synapse/scripts/999-customkernel.sh or modify it to flash magisk instead of the backup (in case you got an updated kernel)
crusader727 said:
afaik Resurrection Remix has addon.d (check if /system/addon.d exists)
you can test this https://github.com/osm0sis/GN-Synap...mdisk/res/synapse/scripts/999-customkernel.sh or modify it to flash magisk instead of the backup (in case you got an updated kernel)
Click to expand...
Click to collapse
wow, that'd be great if it worked. I can confirm addon.d exists, I might try this next time. Do I just put the script into addon.d and flash ROM?
de.er said:
Do I just put the script into addon.d and flash ROM?
Click to expand...
Click to collapse
yes :good:
//btw:
yesterday I posted a feature request to add this to Magisk Manager: https://github.com/topjohnwu/MagiskManager/issues/72
crusader727 said:
yes :good:
//btw:
yesterday I posted a feature request to add this to Magisk Manager: https://github.com/topjohnwu/MagiskManager/issues/72
Click to expand...
Click to collapse
Flashed an RR update to 5.8.1 over the weekend and it went smoother than I expected, to be honest. Didn't use the script you mentioned in the end, just flashed the new ROM, gapps, unsu.zip, magisk and phh's su in TWRP and rebooted. Simple.
de.er said:
Flashed an RR update to 5.8.1 over the weekend and it went smoother than I expected, to be honest. Didn't use the script you mentioned in the end, just flashed the new ROM, gapps, unsu.zip, magisk and phh's su in TWRP and rebooted. Simple.
Click to expand...
Click to collapse
Yes, of course the manual method works :good:
phh-SU was removed in Magisk v11 btw - root is now integrated (MagiskSU).
I still need to have phh's Superuser management app installed. And now on boot I get a notification that my SU binary is out of date. The transition here has been a bit rough.
sweenish said:
I still need to have phh's Superuser management app installed. And now on boot I get a notification that my SU binary is out of date. The transition here has been a bit rough.
Click to expand...
Click to collapse
Are you on about updating your ROM or magisk? Phh su app is required for magisk v10.2, you need to remove it if you're using magisk v11 or later
The Flash said:
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
Click to expand...
Click to collapse
In reference to this, does reflashing Magisk alter anything within Magisk? Namely and really the only thing that would come to mind is it downgrading the Manager app to whatever is in the installer and possibly resetting it settings.
I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip
Nope, just flash the latest magisk zip and it's done. But yes, you also have to install the Magisk Manager when you boot up after flashing the zip.
I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.
equlizer said:
I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.
Click to expand...
Click to collapse
Hm... Absolutely no issues on my OP3T, OOS 4.1.6 and Franco Kernel r25 with Magisk v13.1. Maybe you have a module causing issues (long shot, I know)?
No issues here with Open Beta 10, Stock Kernel, Magisk 13.1 and Manager 5.0.4.
Root is working, passes SafetyNet with all modules activated and properly hide root from my Banking App. All good!
Akhayev said:
I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip
Click to expand...
Click to collapse
Just Simple flash the Magisk v13.1 and install the latest magisk manager v5.0.4.
I feel you should flash magisk immediately, while flashing the ROM through custom recovery. Install magisk manager after first boot.
You can do a dirty flash without formatting anything to get rooted.
Sent from my OnePlus 3T using Tapatalk
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
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
anykiel91 said:
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
Click to expand...
Click to collapse
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
I couldn't get it to boot up before firstboot. So I went with normal nonroot flash so I could use the phone.
I figured it would not matter if I installed Magisk later.
I might try to reflash everything over again
ast00 said:
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
Click to expand...
Click to collapse
topjohnwu says that you flash custom kernel after flashing Magisk
Immortalis said:
topjohnwu says that you flash custom kernel after flashing Magisk
Click to expand...
Click to collapse
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
ast00 said:
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
Click to expand...
Click to collapse
Yes, I had problems with 19.1 too, that the phone sometimes (if not always) would boot itself into fastboot mode instead of system, so at that time I moved temporarily to canary builds
I used this zip instead and it worked. Not sure what's different but I'm good now
https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.