Sorry, I'm new to using Magisk, and I want to ask if I can install a zip designed for TWRP/FlashFire through Magisk and expect it to work?
Sorry for the likely blatant stupidity. Thanks.
The Magisk Manager can only flash Magisk modules. Trying to flash anything else will simply fail with the message "this is not a Magisk module".
Didgeridoohan said:
The Magisk Manager can only flash Magisk modules. Trying to flash anything else will simply fail with the message "this is not a Magisk module".
Click to expand...
Click to collapse
Is it possible to flash a zip file in twrp that alters system files such as the pixelexperience. zip which changes bootanimation, ui sounds , etc?
matrix0027 said:
Is it possible to flash a zip file in twrp that alters system files such as the pixelexperience. zip which changes bootanimation, ui sounds , etc?
Click to expand...
Click to collapse
You kind of answered your own question there, didn't you? The answer is: yes.
Didgeridoohan said:
You kind of answered your own question there, didn't you? The answer is: yes.
Click to expand...
Click to collapse
I should have been more specific. What I meant was after flashing Magisk in Twrp can we still flash other zip files in twrp that are not Magisk modules or will Magisk no longer work after that? Sorry for being somewhat clueless on this subject. I understand that Magisk is systemless but not sure if flashing a zip from recovery would mess up Magisk or cause a boot issue.
matrix0027 said:
I should have been more specific. What I meant was after flashing Magisk in Twrp can we still flash other zip files in twrp that are not Magisk modules or will Magisk no longer work after that? Sorry for being somewhat clueless on this subject. I understand that Magisk is systemless but not sure if flashing a zip from recovery would mess up Magisk or cause a boot issue.
Click to expand...
Click to collapse
sure nothing will happen flashing any thing in twrp will be safe but the zip u will flash will touch ur system partition ...... i think so that
It all depends on what that zip does... Generally there shouldn't be any issues though.
matrix0027 said:
I should have been more specific. What I meant was after flashing Magisk in Twrp can we still flash other zip files in twrp that are not Magisk modules or will Magisk no longer work after that? Sorry for being somewhat clueless on this subject. I understand that Magisk is systemless but not sure if flashing a zip from recovery would mess up Magisk or cause a boot issue.
Click to expand...
Click to collapse
I get what you're trying to ask, you mean that flashing any mods via TWRP will break Magisk or not.
The answer is :No, they work perfectly
But flashing any mods via TWRP will modify your system partition and MAY stop Magisk Hide from working and will affect your ability to receive OTAs
Related
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.
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.
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
whoiam55 said:
So it was a nice monday morning and I decided to try out some magisk module on my coolpad note 3 lite running madOS8.1. After the reboot it got hang on Oreo logo, as it has happened before and usually what I do is force restart the device so I tried to force restart it using power button but it again hang in the same point. Now I tried factory reset it but I think I didn't performed it the right way ends up downloading madOS and Gapps again to flash using twrp. As I installed quite a few modules at once so can't say which one caused it but the thing I want to know is how can I prevent it to break again. Is it possible to remove a magisk module from twrp? Or is there any other way to save my *ss
Click to expand...
Click to collapse
You can remove a module via recovery (mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img to disable magisk then you can remove the module from the manager itself.
Sent from my MI 5 using Tapatalk
teddy0209 said:
(mount magisk, magisk manager for recovery)... Or just flash your unpatched boot.img
Click to expand...
Click to collapse
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
whoiam55 said:
From your reply it seems that mount magisk and magisk manager for recovery are magisk module? And where can I find my unpached boot.img (I'm a beginner ) and yes thanks for the reply.
Click to expand...
Click to collapse
You can find the latter in the download section, the first on the compilation of modules... Your unpatched boot.img/stock boot.img, you can find it inside your room zip, from your twrp backup if you did backup prior to installing magisk. Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Sent from my MI 5 using Tapatalk
teddy0209 said:
Magisk also creates a backup of the boot.img before patching if I'm not mistaken.
Edit: It's under /data
Click to expand...
Click to collapse
So your are saying that if it stuck on boot then I can go back to TWRP, select /data/boot.img and flash it to boot partition?
One more think suppose I install *X* module and it succeed, then I install *Y* module and it failed to boot. Now I flashed boot.img as written above will it contain *X* module or just a fresh boot.img?
Thanks again for the reply.
Can i install magisk through temporary twrp (using fastboot boot recovery xxx.img) in my poco f 1 ?
The answer to that would be a definite maybe.
Joke aside, that should work fine as long as TWRP is otherwise working as it should. There's no difference in functionality between flashing or just booting TWRP.
Why not flash it directly? That is, if there is a twrp for your phone.
As to Magisk, ask XDA
Sent from my SM-A605FN using Tapatalk
pr1jker said:
Why not flash it directly? That is, if there is a twrp for your phone.
As to Magisk, ask XDA
Click to expand...
Click to collapse
But i want to flash OTA
And before flashing OTA i will uninstall magisk
Didgeridoohan said:
The answer to that would be a definite maybe.
Joke aside, that should work fine as long as TWRP is otherwise working as it should. There's no difference in functionality between flashing or just booting TWRP.
Click to expand...
Click to collapse
If i flash temporary twrp , i can flash my OTAs too
I seen some of the people following this,
Flashing temporary twrp and flashing magisk and whenever OTA receives they are simply uninstalling magisk and flashing OTA.
Here my question if i go with this magisk will work perfectly or not ?
@Nicky Cheer There should be no issues with that setup. If you haven't already, I'd advice you to also take a look at @topjohnwu's OTA instructions.
Didgeridoohan said:
@Nicky Cheer There should be no issues with that setup. If you haven't already, I'd advice you to also take a look at @topjohnwu's OTA instructions.
Click to expand...
Click to collapse
Tq @Didgeridoohan and @topjohnwu for clarifying
But one more doubt what is the difference between restore image and complete uninstall under magisk manager ?
Nicky Cheer said:
Tq @Didgeridoohan and @topjohnwu for clarifying
But one more doubt what is the difference between restore image and complete uninstall under magisk manager ?
Click to expand...
Click to collapse
Restore image - only restore the stock boot image and leave all Magisk internals intact.
Complete uninstall - remove everything Magisk related from your device.
First option is preferred, since you then won't have to set everything up again afterwards.
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