Related
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/
How To Play Pokemon Go with Superuser (Root enabled)
Note:
IT MIGHT CAUSE BOOTLOOP OR MIGHT BRICK YOUR DEVICE. MAKE SURE YOU HAVE A BACKUP.
Requirement:
Fresh Installation of Rom or Dirty Flash of your current rom (I tested it on CM and RR- Fresh.It might work on other custom roms.)
TWRP Recovery
Magisk: http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
unSU Script : http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
Steps:
1. Reboot into Recovery
2. Flash unSU Script and Magisk in order.
3. Reboot into System. (Mobile should boot without bootloop, otherwise you have to reinstall the ROM and try again)
4. Install Phh Superuser from here: https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en.
4. Open Magisk Manager ( Update it,if it is asked) and it will ask you for SU permission. Allow it.
6. Go to Settings and Tick " Enable Magisk Hide " and Reboot your phone.
7. Once again Magisk Manager and it will show status of SafetyNet at 3rd row and It should Passed.
Install PokemonGo and Enjoy
Credits:
@topjohnwu
@phhusson
@Hw4ng3r
@Tikerz
Updates:
8/1/17
Updated the steps with New Magsik version 10.2
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Jowhee said:
I did a clan flash. Booted and let everything settle. The rebooted into TWRP recovery. Mounted system, and deleted (or renamed) the Su files from system/bin and system/xbin. This removes root but I can play Pokémon.
Click to expand...
Click to collapse
This guide is for keeping root AND passing SafetyNet.
BTW, this method also works on CM13 and OOS.
It didn't mention keeping root in the title.
Jowhee said:
It didn't mention keeping root in the title.
Click to expand...
Click to collapse
Sorry for the confusion.
Updated the thread.
SafetyNet Helper fails after following the steps:
SafetyNet request: success
Response Validation: success
CTS profile match: failure
Click to expand...
Click to collapse
Do we need to go back into fastboot and disabled the bootloader unlock?
nphillips said:
SafetyNet Helper fails after following the steps:
Do we need to go back into fastboot and disabled the bootloader unlock?
Click to expand...
Click to collapse
Not necessarily. Some kernels such as blu_kernel bypass the bootloader check. Try it out.
svprm said:
How To Play Pokemon Go with Superuser (Root enabled)
Click to expand...
Click to collapse
can Xposed work along with PoGo ?
samnaction said:
can Xposed work along with PoGo ?
Click to expand...
Click to collapse
I'm not sure. I didn't test it.
But you can install the Xposed Framework module through Magisk Manager.
In CM builds you don't need all this you just need this simple app:
http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
I'm gonna assume this doesn't work with CM12.1 right?
Yepi69 said:
I'm gonna assume this doesn't work with CM12.1 right?
Click to expand...
Click to collapse
I didn't try.
But you can try and post the result here that would help others.
I followed the steps in the first post and everything went OK. I'm using oxygen Os nougat 0.9
Thanks for your tutorial.
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
rdar_93 said:
Does this mean that CM14.1 passes safetynet now? I don't exactly need root but when I tried it a few weeks ago PKMN Go told me that the OS I had was not supported.
Click to expand...
Click to collapse
Yes, cm 14.1 could pass safety net with this.
This works for sure. But if you're running a secondary ROM using MultiROM the modified boot.img will cause safetynet to indeed fail. I hope they do bring an update soon to fix this though.
Daft question, but i'm unable to use an online banking app, due to being rooted. I know this relates to PokemonGo, but wondering if this could fool the banking app?
I am using H2OS beta (Nougat) and I followed the below steps, but safety net is failing.
1. Dirty flash current ROM
2. Flash UnSU.zip
3. Flash magisk and phh zips
4. Reboot
5. Install Magisk Manager and Phh superuser
6. check safety net
Is there anything which I'm doing wrong? Can you help me please. Thank you
Edit: A reboot and everything worked fine. Thank you so much
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
topjohnwu said:
If you're using Magisk v7+ with Magisk version of phh's superuser , or rooted with Official Systemless SuperSU (Android 6.0+ only)
If you choose to use SuperSU (only support Android 6.0+)
Click to expand...
Click to collapse
So I am really wondering about your step 2 ...
svprm said:
2. Flash unSU Script, Magisk and phh's SuperUser Magisk.
Click to expand...
Click to collapse
pathologo said:
Sorry to disturb this thread, but I am a bit confused because the official Magisk thread nowhere mentions that phh's su would be the only working su solution:
So I am really wondering about your step 2 ...
Click to expand...
Click to collapse
Actually i didn't try with SuperSu.So i mentioned phh's SU.
It might work with SuperSu too.
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.
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.
I am really trying to do it by myself; I already tripped my knox 5x.
I am using sm-t713 and flashed sdk24 arm64 in TWRP, however ones I do it I stock in TWRP and unable to boot to system. Flashing xposed doesnt give me any errors. What am I am doing wrong. I am on [ROM] [7.0] Nougat - Stock Lite v3. I installed xposed installer pre and post flashing xposed in TWRP - no success.
Please help
netgar said:
I am really trying to do it by myself; I already tripped my knox 5x.
I am using sm-t713 and flashed sdk24 arm64 in TWRP, however ones I do it I stock in TWRP and unable to boot to system. Flashing xposed doesnt give me any errors. What am I am doing wrong. I am on [ROM] [7.0] Nougat - Stock Lite v3. I installed xposed installer pre and post flashing xposed in TWRP - no success.
Please help
Click to expand...
Click to collapse
Probably not waiting long enough after reboot.
ashyx said:
Probably not waiting long enough after reboot.
Click to expand...
Click to collapse
After flashing xposed in twrp. I am unablebto boot at all.
netgar said:
After flashing xposed in twrp. I am unablebto boot at all.
Click to expand...
Click to collapse
The best way to install Xposed is via Magisk.
Unroot your device completely by flashing the stock firmware or just the boot image then flash Magisk.
Open Magisk manager and install the Xposed module.
Nothing else required. All without affecting system or permanently breaking anything. It's as simple as removing the module to revert.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268/post67074423
ashyx said:
The best way to install Xposed is via Magisk.
Unroot your device completely by flashing the stock firmware or just the boot image then flash Magisk.
Open Magisk manager and install the Xposed module.
Nothing else required. All without affecting system or permanently breaking anything. It's as simple as removing the module to revert.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268/post67074423
Click to expand...
Click to collapse
Thx ashyx
I installed magiks and looks ok; still need to do more reading which kind of xposed to install
netgar said:
Thx ashyx
I installed magiks and looks ok; still need to do more reading which kind of xposed to install
Click to expand...
Click to collapse
You don't need to decide. The latest version is dynamic and will install the correct version.