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/
I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip
Nope, just flash the latest magisk zip and it's done. But yes, you also have to install the Magisk Manager when you boot up after flashing the zip.
I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.
equlizer said:
I installed the latest one that came out today and my phone took a crap! Phone became very laggy and would freeze and sometimes not even detect root. I had to restore my phone back to last weeks version.
Click to expand...
Click to collapse
Hm... Absolutely no issues on my OP3T, OOS 4.1.6 and Franco Kernel r25 with Magisk v13.1. Maybe you have a module causing issues (long shot, I know)?
No issues here with Open Beta 10, Stock Kernel, Magisk 13.1 and Manager 5.0.4.
Root is working, passes SafetyNet with all modules activated and properly hide root from my Banking App. All good!
Akhayev said:
I have the latest hydrogen OS and unlocked bootloader , and i want to root my phone but i just wants to know if theres any other files I need to flash other than magisk.zip
Click to expand...
Click to collapse
Just Simple flash the Magisk v13.1 and install the latest magisk manager v5.0.4.
I feel you should flash magisk immediately, while flashing the ROM through custom recovery. Install magisk manager after first boot.
You can do a dirty flash without formatting anything to get rooted.
Sent from my OnePlus 3T using Tapatalk
Has any of you guys tried the newest TWRP 3.2.0.0 for OnePlus 3T? Did you find a bug?
Thanks.
Info: http://www.androidpolice.com/2017/1...g-better-support-oreo-roms-pixel-2-bug-fixes/
Download TWRPfor OP3T from the official site: https://dl.twrp.me/oneplus3t/
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
jojlse said:
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
Click to expand...
Click to collapse
I assume you flash the updated Recovery followed by the patched firmware, which i assume you already have? I don't even know if the firmware is necessary but whenever i flash anything i also re-flash the patched firmware while I'm at it. No reason not to.
Alright, DM-Verity will be cleared if you flash the newest Magisk beta, and TWRP 3.2.X.X is working fine. I don't think Teamwin would release an official version of TWRP without making sure it's completely free of bugs. It flashes Oreo ROMs (Cardinal Xtended, N2Os) and also flashed OOS 5.0 very well. Add-ons such as Magisk and Magisk Modules flashed flawlessly.
Hello I am currently running lineage os 14 on my phone with a custom kernel installed and want to install magisk but I have read that you need to flash the kernel after flashing magisk but I don't want to lose my data. Therefor I am thinking about first flashing magisk and then emidlity after that flashing my kernel again. Would that work or could some problem occur.
If you have TWRP on your device, try backup everything and then flash magisk
1. Wipe dalvik & cache
2. Dirty flash your rom
3. 1 & boot into os
4. flash magisk & 3
5. flash your custom kernel & 1
I forgot about this rule and added magisk with the custom kernel already in place. Have I already lucked out or is the pain yet to come? Should I remove magisk before applying my next rom update?
Epilogue: updated rom, wiped caches, and everything turned out fine.
Fdraco10 said:
If you have TWRP on your device, try backup everything and then flash magisk
Click to expand...
Click to collapse
so you've got perfect battery life using glassfish? can I ask how
I use Magisk since years and my devices got always rooted after its installation, but today it's differenti ad you may see in the attached pic...
I've G8441 and I installed Lineage 16, I'd even like to have root access!
Waiting for your advices to solve my problem!
You need to give more details than that. What have you done and what was the result?
Take a look here:
https://www.didgeridoohan.com/magisk/MagiskHelp
I installed Magisk via TWRP, I can't provide any log but installation ended in the good way (no error) but Magisk is not installed.
I flashed Magisk before ROM and gapps, I rebooted after that and then I installed the rest (ROM and gapps).
That's still quite slim, information-wise...
But, if you flashed your ROM after Magisk there's a good chance that Magisk got overwritten with the stock ROM boot image. And if the LOS addon.d glitched (there's been issues with v2), you'd end up with no root.
Magisk goes last when installing.
Didgeridoohan said:
That's still quite slim, information-wise...
But, if you flashed your ROM after Magisk there's a good chance that Magisk got overwritten with the stock ROM boot image. And if the LOS addon.d glitched (there's been issues with v2), you'd end up with no root.
Magisk goes last when installing.
Click to expand...
Click to collapse
Knowing that Magisk needs to be the last during installation is good! Gotta try this!
Many thanks Didgeridoohan!