Followed the install but phone is not rooted - Magisk

What should i do/try/check when i have followed the install procedure (correctly and tried severel times) but my phone is not rooted?
LineageOS 20.0, Magisk 23.0

Use magisk 25.2? Did you direct install?

Yeah, well. I need magiks-hide so 23.0 is the latest i can use. Not sure what direct install means, i downloaded the boot.img, install magisk into it using the app, and then did the fastboot flash-thingy.

revt3949 said:
Yeah, well. I need magiks-hide so 23.0 is the latest i can use. Not sure what direct install means, i downloaded the boot.img, install magisk into it using the app, and then did the fastboot flash-thingy.
Click to expand...
Click to collapse
Use magisk delta. It has magisk hide, and a lot more on the latest magisk.

Great, where can i find this magisk delta?

revt3949 said:
Great, where can i find this magisk delta?
Click to expand...
Click to collapse
Where is this?

Yeah well, that does not look like it is matured software: no explaination what magisk delta is, where magisk delta is different from normal magisk, no details on how to install, etc.
Not sure that i want to brick my phone with this tool.

revt3949 said:
Yeah well, that does not look like it is matured software: no explaination what magisk delta is, where magisk delta is different from normal magisk, no details on how to install, etc.
Not sure that i want to brick my phone with this tool.
Click to expand...
Click to collapse
Lmao. Look at its Xda thread. Much better alternative. Has material you, bootloops protection, system installation, different ways to load zygote, sulist, magisk hid, etc,etc. Its like magisk on steroids, while being twice as reliable.

revt3949 said:
Yeah well, that does not look like it is matured software: no explaination what magisk delta is, where magisk delta is different from normal magisk, no details on how to install, etc.
Not sure that i want to brick my phone with this tool.
Click to expand...
Click to collapse
You install same way.

Arealhooman said:
You install same way.
Click to expand...
Click to collapse
How do you mean "the same way"?
I mean with magisk, i unzip the boot.img, patch it using the magisk app and then fastboot flash it on the device. But sure i can not use the magisk app to patch Magisk Delta into the boot.img, right?
So, is there a magisk delta app somewhere that does the patching?

revt3949 said:
How do you mean "the same way"?
I mean with magisk, i unzip the boot.img, patch it using the magisk app and then fastboot flash it on the device. But sure i can not use the magisk app to patch Magisk Delta into the boot.img, right?
So, is there a magisk delta app somewhere that does the patching?
Click to expand...
Click to collapse
Yes. On the GitHub. You can also flash thru twrp. Use previous links I sent.

Just install the magisk delta app and got it all working. The MD app even recognised the existing magisk kernel and offered to do a direct install.
Very happy and thank you for all the support. Will make a donation soon.

lol tried the magisk delta and flashed the .img but in boot loop now.on moto g play 2023.. so maybe no support for that yet.. reflashed original patched boot.img and back

Same here. Direct installed Magisk Delta. But after restart phone become non rooted, unable to prompt magisk. But only magisk delta able to hide the root from banking apps. It is quite irritating. Did you figured anyway on this issue?

Hey Victorlmy i had to flash the original magisk patched file back to get it to boot again... hold the volume down and power buttons till you get it to boot to bootloader and reflash.. still tring to figure out why it didnt boot

Related

Magisk and custom ROM update

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.

How do I install MagiskSU?

Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Keagel said:
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Click to expand...
Click to collapse
Try flashing Magisk in recovery.
jhedfors said:
Try flashing Magisk in recovery.
Click to expand...
Click to collapse
It's what I did, that's where it tells me to install SuperSU first :/
Keagel said:
It's what I did, that's where it tells me to install SuperSU first :/
Click to expand...
Click to collapse
Can you give more details? What ROM, Magisk version, logs, etc?
I would suggest flashing osmOsis's UnSU zip, then Magisk v11.2.
Keagel said:
Hey,
I've been trying to install Magisk and it asks me to have SuperSU installed before I do, which I don't want. How do I install MagiskSU or even Magisk if it asks me to install SuperSU?...
Thanks
Click to expand...
Click to collapse
Your boot image is pre-patched for SuperSU. Flash a clean boot image.
Yeah I found the original boot.img of the stock rom my rom is based on and flashed it and it fixed it! Thanks guys
how to find the original boot.img?
ydstark23 said:
how to find the original boot.img?
Click to expand...
Click to collapse
in twirp
restore> select correct folder > check boot > flash
ydstark23 said:
how to find the original boot.img?
Click to expand...
Click to collapse
In the ROM zip.
In case it has built-in superuser, I would suggest flashing osmOsis's unsu zip as well.
Is MagiskSU just another name for Magisk? A module I want to install has the following requirements:
Requirements:
Magisk v13.x/14.0
MagiskSU
I have Magisk v14.5 installed so does that mean I automatically have MagiskSU or is that something additional I have to add?
alryder said:
Is MagiskSU just another name for Magisk? A module I want to install has the following requirements:
Requirements:
Magisk v13.x/14.0
MagiskSU
I have Magisk v14.5 installed so does that mean I automatically have MagiskSU or is that something additional I have to add?
Click to expand...
Click to collapse
That requirement is probably a remnant from when Magisk also was compatible with SuperSU. It's not anymore, so when installing Magisk you get MagiskSU along with it.
Didgeridoohan said:
That requirement is probably a remnant from when Magisk also was compatible with SuperSU. It's not anymore, so when installing Magisk you get MagiskSU along with it.
Click to expand...
Click to collapse
Thanks! I was confused by that and I couldn't find a good answer when searching. Your help is greatly appreciated!
Oddly, I don't have any root after installing Magisk v15 via recovery. Magisk is working, integrity tests are both green, can install all the modules with no problem and integrity tests are still green, but no root.
Interesting, isn't it?
How i know i've got magiskSU?
Leogur said:
How i know i've got magiskSU?
Click to expand...
Click to collapse
Did you install magisk? Or is it included in your rom? Do you see magisk manager app?
Yes i've. But i still can't fix safetynet problem.

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.

Updating Magisk version

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

Question Magisk 24.3 Bootloop

Anyone else the latest Magisk update causes Bootloop when installing modules?
use 24.1, is perfect
OK THANKS, I HOPE FUTURE UPDATES WILL WORK CORRECTLY ON THE DEVICE
a question: do u have repatched boot.img with new magisk version? you must do it
wetito said:
use 24.1, is perfect
Click to expand...
Click to collapse
I'm still using v23 .. just to be sure lol ! but now i know 24.1 is good thank you!
PonchoNz said:
Anyone else the latest Magisk update causes Bootloop when installing modules?
Click to expand...
Click to collapse
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Done.
i have flashed 24.1 using fastboot. for 24.3 fastbiitd is necessary? i ask just i case in the future i will decide update to latest version
wetito said:
a question: do u have repatched boot.img with new magisk version? you must do it
Click to expand...
Click to collapse
Yep but update it by TWRP
nguadien said:
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Click to expand...
Click to collapse
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop
PonchoNz said:
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop
Click to expand...
Click to collapse
Then the problem is the modules you installed, not "latest Magisk update" like you stated.
Not all modules work for all devices, each device reacts to modules very differently, so boot loop caused by modules should not be mistaken for the whole Magisk.

Categories

Resources