Hi guys,
My Pixel are systemlessly rooted with Magisk since many months now, but for some reasons I'm tired by the method of Magisk: I want to touch at the /system partition, move or delete or edit system files and apps, and with Magisk I can't do it.
Okay, Magisk was pretty useful for keeping Safetynet pass, but with Xposed this ability becomes useless for me. Only things I'm still using is Magisk Hide for using Netflix or NFC paiment app, and Sony Framework module for using PS4 Remote Play.
Before I'm using Magisk and his systemless mode I was using SuperSU, and with it I had no problem with the system partition or with différents things like flashing Viper4android (didn't works whatever the way I use, magisk module or old system mode, it says the drivers need to be reinstalled), mouting partition/making file partition in Linux Deploy, stop background app, modifying the booting apps...
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
billiepreks said:
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
Click to expand...
Click to collapse
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
nine7nine said:
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
Click to expand...
Click to collapse
Thanks for your help ?
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
- installing Viper4android drivers, it says "drivers needs to be reinstalled" everytime I launch it
- Linux Deploy, an app for running GNU/Linux distrib on your device, works the first time I launch it, but after reboot he said he didn't get root permission or found busybox, it's very strange.
Many things who worked before with SuperSU 2.79.
Edit : and what about SuperSU and CCMT ?
billiepreks said:
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
Click to expand...
Click to collapse
You should look in Magisk's log to get a better idea of how it changes your system. trting to modify /system is pointless since it is a tmpfs mount (temperary)...
unfortunately, i can't help much with xposed. i don't use it. after it didn't work with Nougat, i ported a couple of it's modules to my rom (at the time) and then i got the pixel and i run Oreo + my own custom kernel + magisk...
xposed isn't providing any 'suhide' tyype functionality?
billiepreks said:
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
Click to expand...
Click to collapse
again, no point in editing your /system partition, it's a tmpfs mount, of course - any modifications will disappear on reboot.... you probably need to edit the real /system partition to make any change stick.
as far as the other apps, they obviously are trying to modify your aystem partition, which is why they don't work.... i think that you could install soumd mods via magisk modules?
i would recommend.consulting relevant forum threads on specific topics/apps though. u are bound to get better solutions&.
@billiepreks
Did you find the solution?
I'm in the same situation.
Did you try using TWRP's filemanager? I think it has true system access. You just need to mount the partition.
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
SuperSU is not working in the Pixel with 8.1
Sh0X31 said:
SuperSU is not working in the Pixel with 8.1
Click to expand...
Click to collapse
Oh. I had no idea.
Do any root methods that aren't Magisk work?
daddylonglegs said:
Oh. I had no idea.
Do any root methods that aren't Magisk work?
Click to expand...
Click to collapse
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
daddylonglegs said:
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
Click to expand...
Click to collapse
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
Click to expand...
Click to collapse
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
daddylonglegs said:
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
Click to expand...
Click to collapse
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
Click to expand...
Click to collapse
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
daddylonglegs said:
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
Click to expand...
Click to collapse
I don't flash twrp zip, just boot it, I know twrp on pixel oreo has still some troubles.
You can try to put your pin and AFTER (when you are on the main scrren with all the actions) plug the otg. On nougat this worked for me, now I just put the 2 or 3 files in internal storage so I don't use otg anymore from recovery so I don't know if this method works or not.
daddylonglegs said:
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
Click to expand...
Click to collapse
Install ElementalX before TWRP if you wish to install TWRP.
SuperSU is no longer maintained and will not work any longer on modern versions of Android until further notice.
About the "internal problem" this can be completely ignored and does not harm the functionality of the device whatsoever.
Magisk 16.3 is the best version of Magisk and mounting USB-OTG shouldn't be problematic whatsoever. Mounting the drive in TWRP has no effect on it mounting in the system and vice-versa.
To mount the OTG in TWRP, plug it in, go to "mount" and select storage location, here you can choose between the internal sdcard and the USB-OTG storage device.
Regarding the mounting of the USB-OTG device in Android the drive must be formatted using a filesystem/partition scheme that Android is capable of mounting. I think FAT32 is the most compatible option.
Applications won't just magically see the external storage unless they're made to support such devices. Google kinda messed up some external storage functionality in Nougat and Oreo, it's kind of quirky. :silly:
I was about to put this in the main discussion thread of FlashFire, but it was closed so i decided to post it here.
So this is what happened, i rooted my Xiaomi Redmi Go with Magisk, the latest one, and when i opened FlashFire, it basically said that i have root, but access couldn't be acquired. It added "Found root: 19.4:MAGISKSU".
It was said in the Supported roots that Magisk is included so can't i use this app? I also tried to change my SELinux to permissive mode by going to the terminal and putting "setenforce 0", and the app still won't let me.
Any solutions to this? I was about to do perform a live backup through this app because the current TWRP version for this device is defective for my phone, the Backup option doesn't work and I've been looking for ways to backup my phone without custom recovery, but still with root of course.
Any help would be appreciated, thankyou!
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
You might try going back to a older Magisk. It's definitely going to be before 19.3 but it may need to be older than that. There are two ways of doing this.
Set a custom channel in Magisk manager (install the older manager first).
Download the older release. If you're not familiar with github, expand the assets link under the release you want. The zip files will be listed there.
Make sure to remove the newer Magisk first.
spider1163 said:
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
Click to expand...
Click to collapse
So is there solution that i can bypass that error ?
Hi all,
Am on Android 10 and phone has the latest TWRP, Magisk and busy box. In Magisk the Ramdisk is a YES. Titanium can disable internal apps no problem and seemingly uninstall them but after restarting the phone those apps re-appear. Also, though the latest MixPlorer and Root Explorer can edit/change Mixer_Paths, the original values come back after restarting the phone.
Can anyone advise how to solve this mystery.
Thanks in advance.
A10 and later , doesn't allow changing system files you need to do this via a magisk module systemless.
@soka said:
A10 and later , doesn't allow changing system files you need to do this via a magisk module systemless.
Click to expand...
Click to collapse
Thanks for that. I googled 'magisk module systemless' but it came up with loads of different things. Not sure what I should look for.
Use the magisk module Debloater from magisk repo, you also need BusyBox module and Termux app from playstore.
RokCruz said:
Use the magisk module Debloater from magisk repo, you also need BusyBox module and Termux app from playstore.
Click to expand...
Click to collapse
Much appreciated. Cheers
My phone is rooted with Magisk after installing TWRP recovery and it's working fine except banking apps which do not run due to rooted phone
I don't use functions of rooted phone so much, only in extracting whatsapp keys to backup my whatsapp chats etc
1) Can I uninstall/unroot Magisk anytime and reinstall/root again smoothly whenever the need arises?
2) Does installing/uninstalling root wipe data?
3) I saw following para in https://magiskmanager.com/uninstall-magisk
Your phone will be rebooted automatically. Don’t worry it is normal
That’s it! You have successfully uninstalled Magisk from your phone.
This process will completely delete all the files from your phone, and you don’t need to worry about anything.
Click to expand...
Click to collapse
What's meaning of "This process will completely delete all the files from your phone" here?
Thanks & regards,
Maria.
AFAIK any tampering of a phone's Stock ROM can get detectected by banking / payment apps - if they want to. IMO the very only method to remove all traces of modifcations applied to phone's Stock ROM is to re-flash phone's Stock what in turn causes the loss of all user data stored on phone.
1) Can I uninstall/unroot Magisk anytime and reinstall/root again smoothly whenever the need arises?
Yes.
2) Does installing/uninstalling root wipe data?
No. As long as you're not locking/unlocking your bootloader, you should be fine. Always a good idea to back up your data and system bacakup since you have TWRP anyway.
3) I saw following para in https://magiskmanager.com/uninstall-magisk
I believe this is reffering to all the MAgisk data only.
Andrologic said:
1) Can I uninstall/unroot Magisk anytime and reinstall/root again smoothly whenever the need arises?
Yes.
2) Does installing/uninstalling root wipe data?
No. As long as you're not locking/unlocking your bootloader, you should be fine. Always a good idea to back up your data and system bacakup since you have TWRP anyway.
3) I saw following para in https://magiskmanager.com/uninstall-magisk
I believe this is reffering to all the MAgisk data only.
Click to expand...
Click to collapse
Thank you very much for your reply
Maria2014 said:
I am having the same problem. I want to ask if you tried uninstall magisk ? What happened ?
Click to expand...
Click to collapse
My dear, I install and uninstall Magisk all the time. Legitimately speaking, never once did it wipe my data ever. Unless you unlock or relock your bootloader, you will be completely fine.
Shabeeh Manappurath said:
My dear, I install and uninstall Magisk all the time. Legitimately speaking, never once did it wipe my data ever. Unless you unlock or relock your bootloader, you will be completely fine.
Click to expand...
Click to collapse
Hi,
Could you advice pls.
After updating magisk it stopped working..
Shuld I uninstall it and then reinstall?
Will my modouls be earased? I am very worried taking this step..
Thanks in advance
tuvia_g123 said:
Hi,
Could you advice pls.
After updating magisk it stopped working..
Shuld I uninstall it and then reinstall?
Will my modouls be earased? I am very worried taking this step..
Thanks in advance
Click to expand...
Click to collapse
My advise is, Incase you feel your modules will be erased, just take a screenshot of ur magisk Modules. Screenshot which you can use to later download the exact same modules. Or u can keep magisk module downloaded before hand. Now if magisk is not working, magisk Modules will not show for you.
If magisk is not working, you don't need to uninstall it. Just go to recovery and reflash the magisk.zip or magisk.apk. both will work, bcos that is how it is. Magisk.apk can be directly flashed from recovery menu. Once you reinstall magisk from recovery and it should start working. If after reboot, it is still not working, then just install magisk.apk while you are in android. (Not in recovery, but normal mode) and then open it and see what it says.
If I can help, I will surely. Let me know how it goes. Usually no data is erased. Don't worry. Magisk Modules or magisk, don't effect the system. U can also download magisk uninstaller.zip if you want to completely uninstall magisk.
Shabeeh Manappurath said:
My advise is, Incase you feel your modules will be erased, just take a screenshot of ur magisk Modules. Screenshot which you can use to later download the exact same modules. Or u can keep magisk module downloaded before hand. Now if magisk is not working, magisk Modules will not show for you.
If magisk is not working, you don't need to uninstall it. Just go to recovery and reflash the magisk.zip or magisk.apk. both will work, bcos that is how it is. Magisk.apk can be directly flashed from recovery menu. Once you reinstall magisk from recovery and it should start working. If after reboot, it is still not working, then just install magisk.apk while you are in android. (Not in recovery, but normal mode) and then open it and see what it says.
If I can help, I will surely. Let me know how it goes. Usually no data is erased. Don't worry. Magisk Modules or magisk, don't effect the system. U can also download magisk uninstaller.zip if you want to completely uninstall magisk.
Click to expand...
Click to collapse
Thank you very much for your detailed and clear answer.
In the next few days I will find time and try.
Of course I will update you.
tuvia_g123 said:
Thank you very much for your detailed and clear answer.
In the next few days I will find time and try.
Of course I will update you.
Click to expand...
Click to collapse
Alright Dear, take your time, and let me know, I hope everything works out for you. And Your Welcome
Shabeeh Manappurath said:
Alright Dear, take your time, and let me know, I hope everything works out for you. And Your Welcome
Click to expand...
Click to collapse
Hello dear friend,
Looks like I deleted the original zip file.
Can you pls. attach a link that wont be malware of a magisk zip?
Thanks a lot
tuvia_g123 said:
Hello dear friend,
Looks like I deleted the original zip file.
Can you pls. attach a link that wont be malware of a magisk zip?
Thanks a lot
Click to expand...
Click to collapse
The best, and only official place to download magisk from is GitHub. At least I think. And well there is one another website I download it from, it's not malware, but I will provide you with the GitHub link itself.
For Magisk v23.0 (One with MagiskHide)(This release also has online module repo, where you can download extra supported modules for your device from online repo of magisk)
https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
For Magisk v25.2 (It does not have MagiskHide, but this is much more better, and there are more effective ways to hide root using Zygisk (new feature in Magisk v24 onwards I believe) (This one does not have Online Repo for Magisk modules, it was also removed in a previous version of Magisk, and you can use Fox's Magisk Modules manager if you want to access and download magisk Modules for any of the future releases for Magisk) If you want the link for Magisk v25.2 then here it is:
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Just if u face any difficulty in flashing the apk file in recovery, just rename it to magisk v23/v25.2 (whichever u choose, I kinda recommend using the latest version) and rename it into . Zip. And if u plan on going with v25.2 and want to access the latest online repo and some of their own Magisk modules, then here is the link for the latest version of Fox's Magisk Modules manager:
Release 0.6.1 - Maintenance Update · Fox2Code/FoxMagiskModuleManager
Add Androidacy test-mode fix to non test-mode Update Brazilian translations by @DanGLES3
github.com
I am currently using the latest Magisk v25.2 on my phone, and currently running on the latest version of Fox's Magisk Modules manager as well. And also, using the method for hiding root that I mentioned before, I am completely successful in covering my root, and my safety net is passed. Completely Passed. Play store or any other app I don't want it detecting root, does not detect root. So we all good if you want to flash the latest update of Magisk.
Shabeeh Manappurath said:
The best, and only official place to download magisk from is GitHub. At least I think. And well there is one another website I download it from, it's not malware, but I will provide you with the GitHub link itself.
For Magisk v23.0 (One with MagiskHide)(This release also has online module repo, where you can download extra supported modules for your device from online repo of magisk)
https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
For Magisk v25.2 (It does not have MagiskHide, but this is much more better, and there are more effective ways to hide root using Zygisk (new feature in Magisk v24 onwards I believe) (This one does not have Online Repo for Magisk modules, it was also removed in a previous version of Magisk, and you can use Fox's Magisk Modules manager if you want to access and download magisk Modules for any of the future releases for Magisk) If you want the link for Magisk v25.2 then here it is:
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Just if u face any difficulty in flashing the apk file in recovery, just rename it to magisk v23/v25.2 (whichever u choose, I kinda recommend using the latest version) and rename it into . Zip. And if u plan on going with v25.2 and want to access the latest online repo and some of their own Magisk modules, then here is the link for the latest version of Fox's Magisk Modules manager:
Release 0.6.1 - Maintenance Update · Fox2Code/FoxMagiskModuleManager
Add Androidacy test-mode fix to non test-mode Update Brazilian translations by @DanGLES3
github.com
I am currently using the latest Magisk v25.2 on my phone, and currently running on the latest version of Fox's Magisk Modules manager as well. And also, using the method for hiding root that I mentioned before, I am completely successful in covering my root, and my safety net is passed. Completely Passed. Play store or any other app I don't want it detecting root, does not detect root. So we all good if you want to flash the latest update of Magisk.
Click to expand...
Click to collapse
Hi,
I prefer v 23 because it has the hide option builtin.
However after flashing it(i think succesfuli) i do not find any new app in my fhone..
tuvia_g123 said:
Hi,
I prefer v 23 because it has the hide option builtin.
However after flashing it(i think succesfuli) i do not find any new app in my fhone..
Click to expand...
Click to collapse
Alright your preference is your own, but maybe hear me out, v23 will soon become outdated, as in some magisk Modules will stop working for it. And the magisk hide, according to the founder of Magisk @topjohnwu, he said that magisk hide is become really ineffective in blocking root, or stopping apps from detecting root. If you want a more powerful version of Magisk hide, update to v25.2 and I will show you how to activate it step by step. It's not built-in, rather it is a new module. So yeah.
Alright and about your question; if you don't find the app in your phone, in your apps drawer, just open file explorer, go to the location where u have kept the magisk.zip file or magisk.apk file. If u have the apk file then just install it once more, from android while in normal mode. If you have the zip file, then just rename to .APK and install it same like above. Then open magisk to continue (mostly after proper install, magisk will reboot your phone once more). Any steps you are stuck in, pls sent me a screenshot, so that I can help.
Shabeeh Manappurath said:
Alright your preference is your own, but maybe hear me out, v23 will soon become outdated, as in some magisk Modules will stop working for it. And the magisk hide, according to the founder of Magisk @topjohnwu, he said that magisk hide is become really ineffective in blocking root, or stopping apps from detecting root. If you want a more powerful version of Magisk hide, update to v25.2 and I will show you how to activate it step by step. It's not built-in, rather it is a new module. So yeah.
Alright and about your question; if you don't find the app in your phone, in your apps drawer, just open file explorer, go to the location where u have kept the magisk.zip file or magisk.apk file. If u have the apk file then just install it once more, from android while in normal mode. If you have the zip file, then just rename to .APK and install it same like above. Then open magisk to continue (mostly after proper install, magisk will reboot your phone once more). Any steps you are stuck in, pls sent me a screenshot, so that I can help.
Click to expand...
Click to collapse
Hi,i took your advice and flashed v. 25.2, however i think that the installation failed..
tuvia_g123 said:
Hi,i took your advice and flashed v. 25.2, however i think that the installation failed..
Click to expand...
Click to collapse
Hey, I see, okay use magisk uninstaller to completely remove v23 first, and then flash v25.2 afterwards.
From what I researched, it seems u can easily uninstall magisk by renaming magisk v25.2.apk (the file we downloaded) rename it into uninstall.zip
And then reboot to recovery, flash it from recovery to completely uninstall magisk v23. (Make a copy of the file before renaming into uninstall.zip.) that way we can flash v25.2.apk /v25.2.zip directly.
Hope everything works for you.
Shabeeh Manappurath said:
Hey, I see, okay use magisk uninstaller to completely remove v23 first, and then flash v25.2 afterwards.
Just to be sure,v. 23 that I want to uninstall not to rename?
From what I researched, it seems u can easily uninstall magisk by renaming magisk v25.2.apk (the file we downloaded) rename it into uninstall.zip
And then reboot to recovery, flash it from recovery to completely uninstall magisk v23. (Make a copy of the file before renaming into Uninstall.zip.) that waysure that I understood.. we can flash v25.2.apk /v25.2.zip directly.
not sure that i understands.
Click to expand...
Click to collapse
Shabeeh Manappurath said:
Not
Hope everything workNs for you.
Hey, I see, okay use magisk uninstaller to completely remove v23 first, and then flash v25.2 afterwards.
N
From what I researched, it seems u can easily uninstall magisk by renaming magisk v25.2.apk (the file we downloaded) rename it into uninstall.zip
And then reboot to recovery, flash it from recovery to completely uninstall magisk v23. (Make a copy of the file before renaming into uninstall.zip.) that way we can flash v25.2.apk /v25.2.zip directly.
Hope everything works for you.
Click to expand...
Click to collapse
Not sure that I understood.
Not to rename Version 23 that I want to uninstall?
Rename v25 that we want to keep?
https://drive.google.com/uc?export=download&id=1XvA2wCzCfSgQGJRgzJ-yklOYn99DDjBQ
Just Flash that, in order to uninstall Magisk from your device. And then, install the latest Magisk v25.2
Shabeeh Manappurath said:
https://drive.google.com/uc?export=download&id=1XvA2wCzCfSgQGJRgzJ-yklOYn99DDjBQ
Just Flash that, in order to uninstall Magisk from your device. And then, install the latest Magisk v25.2
Click to expand...
Click to collapse
Hi dear,
First of all thank you again.
After flashing this when i am entering again to recovery I don't get the screen of twarp as before.
However installation of v. 25.2 (in recovery)failed again..
Atached screen shots.