I used to be able to have the Magisk App undo the binary patches while still root, let the OTA update run, then have the Magisk App repatch the alternate root and reboot. There was an option for this in the Magisk App. I haven't seen it since the Magisk App GUI changed a while ago.
Is there still a way to do this? I'm on a Pixel 3XL.
Related
As the title describes DirecTV Now/AT&T has decided that root users can't watch with their app. I am using a Nexus 6 with Nitrogen OS, with phh superuser with magisk. Using magisk hide on the directv now app and superuser itself. I am also using the root kill switch 1.3.3.2. All of these things activated and DirecTV Now still doesn't work. Anyone have a step by step guide to get this app to work with root?
rester555 said:
As the title describes DirecTV Now/AT&T has decided that root users can't watch with their app. I am using a Nexus 6 with Nitrogen OS, with phh superuser with magisk. Using magisk hide on the directv now app and superuser itself. I am also using the root kill switch 1.3.3.2. All of these things activated and DirecTV Now still doesn't work. Anyone have a step by step guide to get this app to work with root?
Click to expand...
Click to collapse
I think it's because your bootloader is unlocked, you can check with the app "SafetyNet Helper Sample" on Google play. There maybe a kernel that will help, I heard ElementalX but not sure.
Solved the problem of annoying error 40 code!
Ok for everyone with DirecTV Now and a Custom ROM with unlocked bootloader(maybe even stock rom). Here's the way to see the video on DirecTV NOW and keep root/unlock.
Disclaimer: This method is with phh superuser and magisk v9 with Magisk Manager 2.5 (haven't tried it on SuperSu, but might work with suhide). Also, I was on 7.1.1 Nitrogen OS build 12/06. This is also with Android's latest December 5, security patch.
Before doing the steps, clear data and cache on your direcTV Now app
1.) Flash the ROM, flash Gapps, flashed unSu if not using phh superuser or built in su app, flashed magisk v9, flashed phh superuser r266-2, boot phone
2.) Installed magisk manager.
3.) Activated magiskhide through magisk manager
4.) rebooted device
5.) Checked in magiskhide the DirecTV Now app and checked supersu
6.) rebooted device
7.) went into build.prop in /system
8.) changed ro.build.type=userdebug to ro.build.type=user
9.) changed ro.build.tags=test-keys to ro.build.tags=release-keys
The SuperSU/Magisk v9/MagiskHide combo 'works' too.
Just (A) deny DTV NOW root access in SuperSU, and (B) hide it with magiskhide in MagiskManager.
(This assumes you have Magisk set up to properly use SuperSU)
rester555 said:
Solved the problem of annoying error 40 code!
Ok for everyone with DirecTV Now and a Custom ROM with unlocked bootloader(maybe even stock rom). Here's the way to see the video on DirecTV NOW and keep root/unlock.
Disclaimer: This method is with phh superuser and magisk v9 with Magisk Manager 2.5 (haven't tried it on SuperSu, but might work with suhide). Also, I was on 7.1.1 Nitrogen OS build 12/06. This is also with Android's latest December 5, security patch.
Before doing the steps, clear data and cache on your direcTV Now app
1.) Flash the ROM, flash Gapps, flashed unSu if not using phh superuser or built in su app, flashed magisk v9, flashed phh superuser r266-2, boot phone
2.) Installed magisk manager.
3.) Activated magiskhide through magisk manager
4.) rebooted device
5.) Checked in magiskhide the DirecTV Now app and checked supersu
6.) rebooted device
7.) went into build.prop in /system
8.) changed ro.build.type=userdebug to ro.build.type=user
9.) changed ro.build.tags=test-keys to ro.build.tags=release-keys
Click to expand...
Click to collapse
Anyone know if it is required to use buildprop still?
Sent from my Nexus 6 using Tapatalk
To my knowledge yes.
Did you allow or deny permissions?
Sent from my Nexus 6 using Tapatalk
Build prop edits still a yes... as of last night on N6 w/ pure nexus rom
A slightly easier solution, if you already have Xposed installed, is Root Cloak: https://www.youtube.com/watch?v=C6CzzenVoF4
Delete, fixed my issue.
Hi all,
So I've just flashed Oxygen OS 4.0.1 for the OnePlus3T, flashed SuperSU 2.79, downloaded Magisk from playstore, installed it, uninstalled SuperSU app. Root is working fine
Two green ticks, installed and properly rooted, but the SafteyNet failes. I read that you need to enable Magisk hide, so I do, and it tells me to reboot, so again I do, but the option keeps resetting/.
Anyone else having this issue/ has a solution?
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Edit: New info added to OP after my answer... Magisk Hide does not work with SuperSU.
Didgeridoohan said:
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Click to expand...
Click to collapse
That's a shame ./. I'll ask reddit
Thanks
I'm using phh's superuser and Magisk hide is working for me on the open beta and people seem to say that the current beta and the release versions are virtually the same, so it might be an issue with how SuperSU is handled.
afaik Magisk Hide needs phh's root, not SuperSU
Snappiestjack said:
Hi all,
So I've just flashed Oxygen OS 4.0.1 for the OnePlus3T, flashed SuperSU 2.79, downloaded Magisk from playstore, installed it, uninstalled SuperSU app. Root is working fine
Two green ticks, installed and properly rooted, but the SafteyNet failes. I read that you need to enable Magisk hide, so I do, and it tells me to reboot, so again I do, but the option keeps resetting/.
Anyone else having this issue/ has a solution?
Click to expand...
Click to collapse
Ok... I believe you've added some information since my first answer...
Magisk Hide does NOT work with SuperSU. You have to use topjohnwu's phh's superuser that's provided with Magisk.
Didgeridoohan said:
There's been several users with OnePlus devices having problems with Magisk Hide. Might be a device specific issue that's not user solvable at the moment...
Click to expand...
Click to collapse
Nope, nope, nope. It's a problem with USERS who use magisk hide options. In THREAD is info about supersu + magisk hide = NOT WORKING. This is only fault of wrong su binaries, so it's not device specific issue.
And for this issue - probably flash a unsu script. It will (probably) delete all of supersu files, then in magisk manager or twrp flash modded phh binaries for magisk and then, finally install ph manager from google play. That is config to be able to use magisk hide.
ENJOY.
mucha.k1994 said:
Nope, nope, nope. It's a problem with USERS who use magisk hide options. In THREAD is info about supersu + magisk hide = NOT WORKING. This is only fault of wrong su binaries, so it's not device specific issue.
And for this issue - probably flash a unsu script. It will (probably) delete all of supersu files, then in magisk manager or twrp flash modded phh binaries for magisk and then, finally install ph manager from google play. That is config to be able to use magisk hide.
ENJOY.
Click to expand...
Click to collapse
Yeah, I know... OP edited with SuperSU info after my answer. I edited my post as well. Thanks for the reminder.
Not going to quote everyone, but YES! Removing SuperSU and using phh SU works just fine!
Thanks all.
I am having OnePlus7T which does not have TWRP. Magisk was installed through patched boot image while rooting many months back. At that time Canary version was recommended and I had installed that.
I have updated the ROM, Magisk Manager and Magisk in these months via OTA.
Everything works except this app, https://play.google.com/store/apps/details?id=in.org.npci.upiapp&hl=en. It detects even though hidden with MagisK Hide. Magisk package manager is also hidden but this app does not work. It opens, registers the user but later detects root.
Since last few days Magisk is crashing when opened for no apparent reason. Restarting the phone didn't make any difference. If I long click on the app and select Magisk Hids or Supeuser or Modules it opens but when I try to go to main Manager screen it crashes. How to resolve this? Phone is still working as intended and I have root access for apps not hidden in Magisk Hide.
How do I update Manager from Canary to Stable? Can I just download a stable Manager apk and install it on top of the Canary? Which version should be used? Will Magisk also need to be installed again? Will I lose root?
Can anyone explain the steps in detail as I am bit confused.
My Magisk also crash like this
I installed a new ROM on my tablet and couldn't get Magisk to work, so I restored the ROM I was using previously. But Magisk wasn't working in it anymore. In researching the problem, it seems that Google has not only removed Magisk Manager from the Play Store, but also found a way to keep previously installed Magisk from granting root privileges.
lewmur said:
I installed a new ROM on my tablet and couldn't get Magisk to work, so I restored the ROM I was using previously. But Magisk wasn't working in it anymore. In researching the problem, it seems that Google has not only removed Magisk Manager from the Play Store, but also found a way to keep previously installed Magisk from granting root privileges.
Click to expand...
Click to collapse
You don't get Magisk from the playstore but from the Magisk thread.
Magisk
Magisk - The Universal Systemless Interface, to create an altered mask of the system without changing the system itself.
forum.xda-developers.com
Tulsadiver said:
You don't get Magisk from the playstore but from the Magisk thread.
Magisk
Magisk - The Universal Systemless Interface, to create an altered mask of the system without changing the system itself.
forum.xda-developers.com
Click to expand...
Click to collapse
If you read my later post you'll see that I found that out and tried it. None of the versions work with the ROM based on Android 11. I have always just installed an the latest version Magisk.zip I happen to have handy and let it install Magisk Manager. Then I'd use Magisk Manager to update Magisk. That didn't work with the Android 11 ROM either. The update failed and the older version didn't root.
Hi there,
i used Magisk with a hidden Magisk Manager (As "Settings" in the app drawer) and i got a update notification about a new Magisk version. I updated and afterwards i read Magisk Manager is dead and isn't used anymore. When i now click on "Settings" it force closes and i can't open Magisk. What can i do now?
Device is a Oneplus 7t Pro with Stock rom.
Thanks
Try reinstalling magisk through recovery. Works for me on my Pixel 3 running LOS18. 1. Just flash the magisk zip through twrp or whatever you have.
Shouldn't be necessary to hide the magisk app. I have Gpay etc working nicely with the magisk app not hidden. Unless of course there's some other app you're running that won't work without magisk being hidden?
Okay i try to reinstall it but i think i'll wait for Android 12 to come and then start from scratch. Magisk Hide or at least hiding root is necessary for my banking app.
Same happened to me. Oneplus 8T with Android 11.