Hi,
i recently installed magisk and xposed on my OnePlus One and it worked flawlessly.
Yesterday, i updated my Nexus 9 (CM 13, nightly) and unrooted it.
- Uninstalled SuperSU
- Reinstalled SuperSU from the PlayStore
- Let SuperSU fully unroot my Nexus 9
After that, i installed magisk and phh superuser.
Everything worked fine, until i installed xposed 86.5 systemless.
After a reboot, root is gone.
Magisk can't mount root anymore and if i try it within adb "$(getprop magisk.supath)/su -c "setprop magisk.root 1"" it throws an error, that "su" cannot be found.
After uninstalling xposed, magisk can mount root again.
Any suggestions?
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.
Hi all
I have used xposed for a long time now, but I noticed something strange lately.
My setup:
Oneplus One without Gapps, with Magisk and Xposed, Android 6.0.1 Sultan ROM.
Xposed reports the framework v.87.0 systemless by topjohnwu is installed but not active.
However, my xposed modules (deny location consent, fakegapps, greenify, magnet sensor control, statusbar headset icon) seem to work perfectely.
I already checked, if there is a disabled file, but could not find one.
I already did reboots, disabled xposed&rebooted, enabled xposed&rebooted, reinstalled v87.0 sdk 23 from topjohnwu, but no change.
The yellow sign wont go.
I noticed something strange:
I wanted to update my busybox inside system/xbin, but was not able to remove it, even with root explorer I could not delete the 22 (?) Mb busybox file in system/xbin.
Magisk seems to work fine though.
I then uninstalled all busybox installation apps and installed the busybox module from Magisk.
Could you help me getting proper xposed?
Or is this an error?
xposed log:
https://pastebin.com/XVP0UGim
I installed xposed through magisk and everything worked fine, I installed modules and they worked, but after a reboot the modules list in xposed is suddenly empty. in xposed I get the following log:
Code:
Unable to open /vendor/framework/oat/arm to prepare apps for Xposed: Permission denied
Unable to open /vendor/framework/oat/arm64 to prepare apps for Xposed: Permission denied
I was wondering if anyone else is using xposed and got similar errors, or even has a solution?
Edit: Turns out the cause was a (self made, very old) xposed module that somehow broke all the others - removing this fixed it.
@Abomb - Just curious, are you running Xposed on Oreo or Nougat? - TIA
I'm running Xposed on Oreo (through magisk)
@Abomb i'm using Oreo V 11.0 based Rom & Unable to install Xposed Module with Riru V 23.3 By Rikka
My device Poco f1 8GB 256 GB i install google pixel experience rom via twrp but i can't install xposed module
Hey!
I've successfully rooted my S10 (3rd time in a row) with Magisk. I've installed my daily apps, including Greenify, AFWall, AdAway etc. They all were prompting for SU access, and it went fine.
I had to reboot my phone. Since reboot, no app is asking for SU access. Apps that were granted SU access before reboot are working fine in Root mode, yet I can't SU any more apps.
Magisk Logs are fine, no errors, no crashing. I don't want to factory reset once again...
My Magisk modules: Busybox, Energized Protection.
What i've tried:
Updating Magisk to stable / beta
Running Magisk in safe mode
Hiding and restoring Magisk Manager app
Changing any option in Magisk Manager
Removing all modules
Using Magisk hide / disabling Magisk hide
Removing Magisk from battery optimisation mode
Everything else that I could find online...
I have no idea what to do now...
I can't grant SU to any other app...