Hey guys,
has somebody managed to install magisk with zombie kernel? As far as I see its the best kernel for stock ROMs like existenz.
But since its rooted with SuperSU it doesnt pass SafetyNet...
I removed SuperSU from installer script of existenz and flashed zombie kernel.
No root so far and SafetyNet still did not pass.
Than I flashed magisk, but magisk manager says that there is no root, but atleast SafetyNet passed. I also tried to patch the boot.img of zombie kernel and flash it through recovery, but it still says there is no root installed.
Anyone an idea?
Related
I just decided to get rid of my root, so i uninstalled Magisk with the uninstaller .zip. Then i went on to try to flash the Xposed Uninstaller but it says that i need magisk to uninstall Xposed for some reason. Did i flash the wrong .zip or did i do anything else wrong. I also unrooted with the SuperSu app but i still cant pass the safety net check. Can anyone help with either of these issues? Plz reply
-Me
Try deleting Xposed.img under /data, and if you need to unroot, do not use the super su app, use the unsu signed zip instead, search it up on XDA
If you were using Magisk systemless Xposed it was uninstalled together with Magisk.
And if you were using Magisk, you don't need to do anything else to unroot.
Easiest way to make sure you get back to a clean slate would be to dirty flash your system and then lock your bootloader (be real careful though so you don't brick your device). SafetyNet triggers by more things than just root, among other things an unlocked bootloader...
LordIndigo said:
I just decided to get rid of my root, so i uninstalled Magisk with the uninstaller .zip. Then i went on to try to flash the Xposed Uninstaller but it says that i need magisk to uninstall Xposed for some reason. Did i flash the wrong .zip or did i do anything else wrong. I also unrooted with the SuperSu app but i still cant pass the safety net check. Can anyone help with either of these issues? Plz reply
-Me
Click to expand...
Click to collapse
i was facing the same issues with my Moto X Play Stock firmware 7.1.1 (squid kernel) rooted using magisk and systemless xposed installed.... it was working fine until i installed some xposed modules( iFont, perAppFont, xinsta etc.) and somehow it screwed my phone and bootlooped . after searching for long, this thread https://forum.xda-developers.com/showpost.php?p=76064855&postcount=12 works like a charm !
other xposed disabling method ( Power button combination on booting ) didn't worked for me , maybe i was using systemless xposed module that's why.
Hey guys, just a quick question.
Does magisk work on latest stock rom?
If so, what are the advantages comparing with supersu?
I have my device rooted with superSU, I am on latest stock rom.
Thanks in advance!
I uninstalled superSu... but unable to make magisk install on device Magisk v17.1 .. am on DOt OS 7.1.2
Did clean flash and installed magisk... it worked.
I had a rooted OP3t (4.1.3) with SuperSU 2.79.
I just flashed the latest full OOS (OnePlus3TOxygen_28_OTA_054_all_1706101907_0c4fa6) (4.1.6) to my device with TWRP 3.1.1.2
I have _not_ installed the latest version of SuperSU, so I do not have root right now. I do have the SuperSU app on my phone though.
If I want to install Magisk root, are there any additional steps to first completely remove SuperSU?
Thank you!
I figured it out:
- Flashed signed zip
- Removed SuperSU apk from phone
- Flashed Magisk-v12.0.zip
- profit!
Would have been better flashing v13 Magisk
Can't I just flash that over v12 when a stable version of v13 is released?
Hello
Recently i changed stock ROM on my HTC 10 Evo to debloated ROM with Magisk pre-installed
https://forum.xda-developers.com/bolt/development/rom-stock-ish-7-0-nougat-debloated-t3519195
Code:
Stock 7.0 Magisk Debloated/Deodexed + Mods
Whats Included:
Magisk Version 13.xx <- Passes Safety-net As of 8/19/17
Magisk Manager couldn't check updates or check safety net test so i decised to update it.
Downloader 7.3.1 Magisk Manager but couldn't update app so i uninstalled it and then tried to install the fresh one.
It ended up that the old one is gone and new downloaded app hangs while i try to i install it.
Could anyone tell me what to do?
Should i run uninstaller.zip in recovery and then install both Magisk and Magisk Manager?
I couldn't find updating guide for pre-installed Magisk anywhere...
pasiasty29 said:
Hello
Recently i changed stock ROM on my HTC 10 Evo to debloated ROM with Magisk pre-installed
https://forum.xda-developers.com/bolt/development/rom-stock-ish-7-0-nougat-debloated-t3519195
Code:
Stock 7.0 Magisk Debloated/Deodexed + Mods
Whats Included:
Magisk Version 13.xx <- Passes Safety-net As of 8/19/17
Magisk Manager couldn't check updates or check safety net test so i decised to update it.
Downloader 7.3.1 Magisk Manager but couldn't update app so i uninstalled it and then tried to install the fresh one.
It ended up that the old one is gone and new downloaded app hangs while i try to i install it.
Could anyone tell me what to do?
Should i run uninstaller.zip in recovery and then install both Magisk and Magisk Manager?
I couldn't find updating guide for pre-installed Magisk anywhere...
Click to expand...
Click to collapse
Preinstallation doesn't change general rules. It's like the manual patching the bootloader so do exactely what you wrote. Uninstall it in custom recovery via uninstall.zip and then install any version of Magisk you want using the magisk.zip and manager.apk.
Sent from my SM-N960F via Tapatalk
Thank you for help. Just wanted to make sure that I won't damage my rom. The uninstallation and then installation of newest Magisk went perfectly fine and the updated Magisk Manager were already in the drawer.
Internet connection in Magisk Manager is back and safety net test is passed.
Hey guys,
So I've got an A/B device which makes taking OTA updates tremendously easy. I've actually took OTA updates with Magisk installed no problem.
The tricky part is, I use Stock ROM in combination with a custom kernel, I have backups of the stock kernel but my question is hard to ask. I'll write as clear as I can so please bare with me...
I installed the vanilla stock rom, It comes with the stock kernel. What I did was, Patch the kernel with Magisk 19.3, took a backup of it and then installed a Custom kernel with Magisk retain script on it. So my Magisk 19.3 installation was intact. Now that v19.4 is going to be released soon, I will have to install the stock kernel back. So my question is - If I install v19.4 on my custom kernel and then revert to the stock kernel which has 19.3 installed, Will it cause any trouble to my modules or will it revert back to v19.3?
TIA for any answers.
CarbonGTR said:
Hey guys,
So I've got an A/B device which makes taking OTA updates tremendously easy. I've actually took OTA updates with Magisk installed no problem.
The tricky part is, I use Stock ROM in combination with a custom kernel, I have backups of the stock kernel but my question is hard to ask. I'll write as clear as I can so please bare with me...
I installed the vanilla stock rom, It comes with the stock kernel. What I did was, Patch the kernel with Magisk 19.3, took a backup of it and then installed a Custom kernel with Magisk retain script on it. So my Magisk 19.3 installation was intact. Now that v19.4 is going to be released soon, I will have to install the stock kernel back. So my question is - If I install v19.4 on my custom kernel and then revert to the stock kernel which has 19.3 installed, Will it cause any trouble to my modules or will it revert back to v19.3?
TIA for any answers.
Click to expand...
Click to collapse
I own a 6T, so yes I'm also in the A/B scene
I have a similar setup as yours, just I'm not using Custom Kernel.
AFAIK, it's best to install Magisk on Stock Boot Image. But IMO, if you upgrade to Magisk v19.4 from your current v19.3-patched boot image, I think you'll not be facing any issues. If you do face it, you can simply dirty flash the ROM zip & that'll help you out
And regarding that question, if you restore the stock kernel, you should re-flash Magisk v19.4 zip after restoring it to avoid any issues caused by incompatibilities.
Sent from my #FlagshipKiller6T using Tapatalk
DarkSJ1998 said:
I own a 6T, so yes I'm also in the A/B scene
I have a similar setup as yours, just I'm not using Custom Kernel.
AFAIK, it's best to install Magisk on Stock Boot Image. But IMO, if you upgrade to Magisk v19.4 from your current v19.3-patched boot image, I think you'll not be facing any issues. If you do face it, you can simply dirty flash the ROM zip & that'll help you out
And regarding that question, if you restore the stock kernel, you should re-flash Magisk v19.4 zip after restoring it to avoid any issues caused by incompatibilities.
Click to expand...
Click to collapse
Upgrading is not an issue for me
It's that the stock kernel backup has v19.3 installed on the boot image. Now that v.19.4 is going to be released soon, I will have to upgrade and when the OTA comes I will have to go back to my stock kernel with 19.3 installed, I just need to know if going from v19.4 to v19.3 will give me troubles.
Cheers.
Update - I just updated my Magisk Stable v19.3 to Beta v19.4 and then rebooted my phone so my Magisk is updated. Now, I restored the stock kernel with magisk v19.3 over the custom kernel with v19.4 beta and observed that my Magisk installation reverted back to v19.3. Nothing happened to the system or my modules. So I guess it safe to downgrade but I will never recommend doing that.
So there's the answer to my question and maybe yours...