Database Develop

OTA Updates and Magisk

Hey y'all - I saw this and am wondering if this is still applicable?
I'm on v7 with phh's SuperUser r259; so if, say, the November security patch drops, I can accept, download, and install directly from the notification panel? Or am I reading this wrong?
TIA!

alamo76 said:
Hey y'all - I saw this and am wondering if this is still applicable?
I'm on v7 with phh's SuperUser r259; so if, say, the November security patch drops, I can accept, download, and install directly from the notification panel? Or am I reading this wrong?
TIA!
Click to expand...
Click to collapse
You should be able to, but you will have to reflash the magisk zip so that the boot image is re-patched. I accepted an OTA on my Nexus 6P without any issues although I did use Flashfire.

ryaniskira said:
You should be able to, but you will have to reflash the magisk zip so that the boot image is re-patched. I accepted an OTA on my Nexus 6P without any issues although I did use Flashfire.
Click to expand...
Click to collapse
I want to try to start from stock and be able to get OTA updates.
First post in phh's SuperUser states that phh's SuperUser r259 "Magisk compatible, no boot image modifications are required"
So then I am guessing we don't need to reflash Magisk again since boot image is untouched.
Also what about the recovery? Will OTA update replace the twrp and therefore, TWRP needs to be reflshed after each OTA update.
Maybe someone who experienced this can write what needs to be done in order to successfully flash OTA update.
Thanks.

Orochi77 said:
I want to try to start from stock and be able to get OTA updates.
First post in phh's SuperUser states that phh's SuperUser r259 "Magisk compatible, no boot image modifications are required"
So then I am guessing we don't need to reflash Magisk again since boot image is untouched.
Also what about the recovery? Will OTA update replace the twrp and therefore, TWRP needs to be reflshed after each OTA update.
Maybe someone who experienced this can write what needs to be done in order to successfully flash OTA update.
Thanks.
Click to expand...
Click to collapse
Yes because Magisk itself modifies the boot image. So that's why the Magisk version of PHH Superuser doesn't modify the boot image.
Also, you can use FlashFire to install OTAs and preserve the custom recovery, also you can set it to reflash Magisk after the OTA. (With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire)

ryaniskira said:
Yes because Magisk itself modifies the boot image. So that's why the Magisk version of PHH Superuser doesn't modify the boot image.
Also, you can use FlashFire to install OTAs and preserve the custom recovery, also you can set it to reflash Magisk after the OTA. (With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire)
Click to expand...
Click to collapse
But FlashFire says it needs SuperSU or cm's SU

KaMonsieur said:
But FlashFire says it needs SuperSU or cm's SU
Click to expand...
Click to collapse
PHH's Superuser technically is CM's SU, it's a fork of Koishik's Superuser that was used in CM up until MM.

ryaniskira
With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire
Click to expand...
Click to collapse
I am on stock samsung kernel which is set to SELinux enforcing.
What are my options in terms of getting OTA and what needs to be done?
Do I accept OTA, then flash recovery and flash Magisk + PHH Supersuser?
Can I use Flashfire with supersu instead of PHH superuser, will it work with SELinux enforcing?
Thanks for your time.

ryaniskira said:
PHH's Superuser technically is CM's SU, it's a fork of Koishik's Superuser that was used in CM up until MM.
Click to expand...
Click to collapse
I once used SuperSU and FlashFire. But I did not set SElinux to permissive myself. Does SuperSU automatically do it?

KaMonsieur said:
I once used SuperSU and FlashFire. But I did not set SElinux to permissive myself. Does SuperSU automatically do it?
Click to expand...
Click to collapse
SELinux does not need to be set to permissive when you use SuperSU because SuperSU modifies SEPolicy to allow his apps to work with SELinux set to enforcing.

ryaniskira
So to get OTA update in a reliable way. One has to do the following steps.
1. TWRP
2. SuperSu
3. Magisk 7
4. Flashify
Let me know if this is correct?

ryaniskira said:
SELinux does not need to be set to permissive when you use SuperSU because SuperSU modifies SEPolicy to allow his apps to work with SELinux set to enforcing.
Click to expand...
Click to collapse
Thanks for your help!

Answering to my previous post.
In my case flashfire was useless as it could not detect ota zip update at all on my S5, even when I pointed flashfire to the exact location.
It is possible that the OTA zip is encrypted. I could not even open it as archive.
Even if system is untouched, updater detects custom boot image (patched by supersu) and custom recovery. I was able to fool the system by turning the device status to official. Then flashing original recovery and flashing the OTA. Of course after this, you would have to flash custom recover, root and magisk. Unless the process with stock recovery and stock boot is automated, it seems like too much work.
For now, the easiest solution is just to flash an updated firmware when it comes out. This way it will update everything while preserving your data partition.
This begs me to ask this question. Why even bother with systemless this or systemless that. At the end after flashing an updated firmware, the system partition will be overwritten whether it was systemless or not.

Orochi77 said:
Answering to my previous post.
In my case flashfire was useless as it could not detect ota zip update at all on my S5, even when I pointed flashfire to the exact location.
It is possible that the OTA zip is encrypted. I could not even open it as archive.
Even if system is untouched, updater detects custom boot image (patched by supersu) and custom recovery. I was able to fool the system by turning the device status to official. Then flashing original recovery and flashing the OTA. Of course after this, you would have to flash custom recover, root and magisk. Unless the process with stock recovery and stock boot is automated, it seems like too much work.
For now, the easiest solution is just to flash an updated firmware when it comes out. This way it will update everything while preserving your data partition.
This begs me to ask this question. Why even bother with systemless this or systemless that. At the end after flashing an updated firmware, the system partition will be overwritten whether it was systemless or not.
Click to expand...
Click to collapse
For me, the greatest benefit with Magisk is that after an update (by flashing relevant parts of the factory image) all that is needed for my different system modifications is to flash Magisk. It has cut the time it takes for me to update by a huge factor.

Didgeridoohan said:
For me, the greatest benefit with Magisk is that after an update (by flashing relevant parts of the factory image) all that is needed for my different system modifications is to flash Magisk. It has cut the time it takes for me to update by a huge factor.
Click to expand...
Click to collapse
What tool are you using to flash your firmware?

Orochi77 said:
What tool are you using to flash your firmware?
Click to expand...
Click to collapse
Big update, fastboot from my PC. Small update (monthly security update), flash boot and system image in TWRP.

Didgeridoohan said:
Big update, fastboot from my PC. Small update (monthly security update), flash boot and system image in TWRP.
Click to expand...
Click to collapse
Ok thanks. I have to use odin as I have Samsung phone.
When you flash system and boot, don't you lose root?

Orochi77 said:
Ok thanks. I have to use odin as I have Samsung phone.
When you flash system and boot, don't you lose root?
Click to expand...
Click to collapse
Flashing boot image means I need to reflash Magisk (and my custom kernel), but that's it. I use Magisk compatible phh's superuser, which means that's all I need to do. That's why I use (and love) Magisk.

I'm sorta n00b these days been years since ive been much into modding, but got a couple simple questions, i think i know the answer from what i've seen and read, but just want to verify. Save myself a bit of time if i screw it up.
My Device:
LG Nexus 5x Stock ROM 7.1.1 (Recently Flashed clean image that included Feb 2017 security patch) w/ElementalX Kernel
Magisk v11.x (whatever the most recent is, it's up to date) w/phh superuser
I want to flash the new March 2017 Security patch, ideally without losing any data or having to restore all my apps and data from backup ect.. This is what it seems i should do, i think i can use Flashfire (yes it detects my OTA packages and asks to prepare to flash):
I do backups regularly via otg to an external drive. Just completed one before this post
1. Flash OTA, allow flashfire to handle
2. (RE)flash magisk zip
3. (RE)flash phh superuser
4. (RE)flash elementalX kernel
This should leave everything as it was when i started relatively unmodified besides having the new security patch added yes?

g0d0fmischief said:
I'm sorta n00b these days been years since ive been much into modding, but got a couple simple questions, i think i know the answer from what i've seen and read, but just want to verify. Save myself a bit of time if i screw it up.
My Device:
LG Nexus 5x Stock ROM 7.1.1 (Recently Flashed clean image that included Feb 2017 security patch) w/ElementalX Kernel
Magisk v11.x (whatever the most recent is, it's up to date) w/phh superuser
I want to flash the new March 2017 Security patch, ideally without losing any data or having to restore all my apps and data from backup ect.. This is what it seems i should do, i think i can use Flashfire (yes it detects my OTA packages and asks to prepare to flash):
I do backups regularly via otg to an external drive. Just completed one before this post
1. Flash OTA, allow flashfire to handle
2. (RE)flash magisk zip
3. (RE)flash phh superuser
4. (RE)flash elementalX kernel
This should leave everything as it was when i started relatively unmodified besides having the new security patch added yes?
Click to expand...
Click to collapse
PHH Superuser is not compatible with v11
1. It is either Systemless SuperSU (installed before Magisk, or the included MagiskSU (if systemless SU is not installed before Magisk).

jhedfors said:
PHH Superuser is not compatible with v11
1. It is either Systemless SuperSU (installed before Magisk, or the included MagiskSU (if systemless SU is not installed before Magisk).
Click to expand...
Click to collapse
I did it with a previous version, and upgrade to version 11. As long as i follow those steps to get back to 11 it shouldn't matter does it? Meaning flash the other version of magisk i did to start with along with the corresponding phh su, then allow it to update to v11. This is how i got to v11. I planned on using the very same files to flash and root that i did before and allowing it to update. I read the magisk thread about the updates and changes to it. If this isn't a good idea, or just flat out won't work on that basis of trying to flash the older version and allowing the upgrade as i did initially, should i just flash magisk v11? Didn't want to stray from what worked in this regard. But yea ive read this from the magisk thread
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
I will have lost root by flashing the OTA, right? So say i flash just magisk v11 afterwards, what would i need to flash for root and the app to use once started?
This is the method for rooting and magisk install that i used.. Just allowed it to update to 11 after it starts. Do you mean to say this won't work again?
http://www.theandroidsoul.com/systemless-root-magisk-android/

After installing magisk, root not working

After installing the magisk as I was rooted, I installed 2-3 mods ie flashed in twrp but after I rebooted my root is gone. Magisk manager is showing not rooted and when I re flashed supersu in twrp, installation was successful but still no root. What happened I don't know. Also I didn't install any phh supersu or busybox. Please help me regain my root.
HELP

It was a known bug in Magisk that you would lose root.
Magisk
v10.2
- [Magic Mount] Remove apps/priv-app from whitelist, should fix all crashes
- [phh] Fix binary out-of-date issue
- [scripts] Fix root disappear issue when upgrading within Magisk Manager
Click to expand...
Click to collapse
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.

brichardson1991 said:
It was a known bug in Magisk that you would lose root.
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
Click to expand...
Click to collapse
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root

Vaibhunk786 said:
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Click to expand...
Click to collapse
After installing from play store, did you "FLASH" magisk ?

brichardson1991 said:
After installing from play store, did you "FLASH" magisk ?
Click to expand...
Click to collapse
No I didn't flash anything. It was an automatic process which installed magisk and prompted me that installation success and reboot. Then I rebooted and root was gone

Now should I run magisk unstaller zip in twrp followed by supersu and then again flash magisk v10. 2 via twrp.. Should I follow these steps to gain my root again.. Anyone please help. I'm stuck @brichardson1991

Try installing PHH superuser from play store.

I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.

Same problem here, have to investigate whats going on.

MattBooth said:
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Click to expand...
Click to collapse
yeah flashing the stock rom was the only viable option i think .

I have the same problem with latest magisk. After i installed mods root is gone and i can not root again. Only with supersu i have root. Magisk is very bugy.

Yeah it does appear the latest version now causes you to lose supersu

Same problem with me, on the OP3 running Open Beta 11. Reflashing SuperSU did not work. Rather than extract the boot.img to reflash that, I ended up reflashing the firmware (and ended up mistakenly using the 4.0.1 file instead of the OPB11 one!) ... Yet to try SuperSU and Magisk again on this, but figured better to investigate the issue before I attempt to reinstall.
From what I understand here, v10 won't have this problem, and its only on v11 that its cropped up again? Can anybody with v10 confirm this?

Can't Uninstall Systemless Xposed (Moto G4 Plus)

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.

snapchat fail login after root?

Hey everybody I rooted my device this morning, and I was setting everything up again since it gets wiped during the process. So finally I come and try to login in to Snapchat and it says something similar to "log in has failed please try again later" anybody have this problem or a way to fix it? Thanks in advance!

Snapchat checks for root and purposely prevents you from logging in if it find it. If you rooted with SuperSU, try installing Chainfire's SUHide. Otherwise, if you rooted with Magisk, enable MagiskHide in Magisk Manager.

I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.

martinsavvy said:
I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.
Click to expand...
Click to collapse
so i just do the full unroot option, sign in, then just flash the SU again?

sakumaxp said:
so i just do the full unroot option, sign in, then just flash the SU again?
Click to expand...
Click to collapse
Yeah that's what works for me.

martinsavvy said:
Yeah that's what works for me.
Click to expand...
Click to collapse
OMG thank you so much that was so easy!!!!

magisk is better though because you can still use android pay and mobile banking applications.

If I throw on a custom ROM after wiping will I need to do this process again?

Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.

Anova's Origin said:
Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.
Click to expand...
Click to collapse
I shouldnt brick if i have to loose root and reflash super SU when I'm running a rom right? Sorry for all the questions

Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.

Anova's Origin said:
Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.
Click to expand...
Click to collapse
Yeah cos I would need to flash the ROM, then sign in to Snapchat, then go back to TWRP and flash super SU

Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you dirty flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. ROMs like OOS will either replace TWRP with stock recovery or trigger dm-verity if you don't root immediately after clean flashing.

Anova's Origin said:
Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. You might trigger dm-verity if you clean flash a ROM like OOS without rooting before booting.
Click to expand...
Click to collapse
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?

sakumaxp said:
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?
Click to expand...
Click to collapse
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.

Anova's Origin said:
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.
Click to expand...
Click to collapse
I'm on stock ROM, so I guess I can go into super su and loose root then download magisk and get it that way

Thanks mate, it took forever to find this solution, it worked!
I use SU and it was simple to "unroot" from within the SU# app
1. settings scroll down to the "cleanup" section, select full unroot, accept all the warning messages, the phone will reboot into recovery and then reboot the phone after it finishes. Your phone may cycle through the reboot process a couple of times
2. log back into your phone, then you can log into the Snapchat app.
3. now you can re-root your phone, if you want to.
Cheers.

how to switch from super su to magisk?

Hello, I am currently rooted on stock oos 4.0.3, with latest TWRP and super su free v2.79, can anyone help me out and tell me how to switch to magisk please, thank you!
Can I just use super su full unroot option then flash magisk?

Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.

palesaint said:
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
Click to expand...
Click to collapse
so flash unsu, then flash magisk. simple?

Dr Grato said:
so flash unsu, then flash magisk. simple?
Click to expand...
Click to collapse
If you use the unSU script the process is:
unSU
stock boot image
Magisk

This method did not work for me.
I am on KETAN n10 and initially, viper did not work. I installed magisk but that didn't fix it. nor the meefik busy box. So i decided to uninstall magisk and go back to superSU and it magically worked...

I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:

SourPower said:
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
Click to expand...
Click to collapse
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?

JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
If there's a proper backup of the boot image for the SuperSU app's full unroot option to restore, then that process should work perfectly (I've done it on a few devices myself). It's when it can't properly restore the boot image you might have issues and you'll have to do it yourself.
Take a look in the Magisk Troubleshooting guide, under "Moving from another systemless root solution to MagiskSU".

The nuclear method might be, to just flash the full stock OOS zip (can flash in TWRP) which will unroot and restore the boot.img (and everything else!). Then immediately flash Magisk before rebooting (so have the Magisk zip on the phone before updating). This should fully remove SuperSU, install Magisk, and keep TWRP on the phone.
Seeing as the original poster is still on OOS 4.0.3, you may want to update, anyway!

JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
I've done this on my 3t but I do have a G3 coincidentally lol, but yes I unrooted from su, it restarted my phone, before booting back into the system I went in twrp right away and then flashed magisk.

There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?

hypothrax said:
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
Click to expand...
Click to collapse
I chose the Full Unroot option. Then flashed magisk. Worked perfectly.

Use the full unroot option. Catch here is that you might get dm-verity warning. It won't affect the phone in anyway but Android Pay might not work and you will see the warning for 5 seconds, everytime you restart the phone.

Thanks so much for ths thread. I am on Resurrection Remix OS and inititally installed SuperSU over Magisk (which came with the ROM). I decided that I wanted to use Magisk instead and followed the instructions in this thread and it worked a treat.