yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Since it sounds like your ROM comes with Magisk pre-installed and you're posting this in the Magisk phh's superuser thread, I'm gonna assume you mean that installing Magisk phh's superuser fails. Is that right?

And if your ROM comes with Magisk pre-installed, it would be strange if it didn't also come pre-rooted... Which would mean, depending on what root method used of course, that you'd might have to remove that root before installing Magisk phh's superuser.

I think I'm confused. :) More information needed. A recovery log would be useful, if we're taking about flashing zips in recovery that is...
[Magisk] Nollog:
I've a note 4. 266 roots me but 266-2 doesn't. I've done it many times trying to make it work.

I wonder what's the issue?
[Magisk] Didgeridoohan:
We do wonder as well...

More information and logs needed or help will be hard to come by. Very few people on xda are mind readers. :D
[Magisk] Nollog:
I have no idea where to find any logs. Magisk manager log is empty, supersu (phh 2 beta 9) log has two magiskmanager entries.

Where do I find twrp logs? It installs fine as far as the GUI tells me.
[Magisk] Didgeridoohan:
If Magisk log is empty there's something wrong with your Magisk...

Recovery log can be saved in TWRP. From memory that should be under Advanced - Copy log and then recovery.log will be saved to storage.
[Magisk] Nollog:
Ok here's the twrp log of me installing 266, and then immediately 266-2

And magisk manager 2.5 with magisk v9 installed from this morning. The log is from just going directly from boot to opening the manager. Going to settings are checking or unchecking the hide root setting crashes it. Likely because it doesn't have root.

...uh I just typed all this out and all and now magisk manager isn't crashing and it has -2 installed as a module and... I have root.

I installed it like 10 times no kidding and it works as I gather all the logs...
[Magisk] Didgeridoohan:
Your logs look fine to me, except for Magisk Hide throwing an error on boot.

Try disabling Magisk Hide... The current iteration is known to sometimes cause root to be disabled until a reboot. Maybe that was your problem from the start.
[Magisk] HaoZeke:
Does anyone have titanium backup working with this? :( on nougat
[Magisk] aiola1982:
No problems with titanium backup on 7.1
[Magisk] HaoZeke:
Which version of titanium backup are you using? And rom? I can't seem to figure out what's wrong. Every other root app works. Titanium just keeps restoring forever :(

---------- Post added at 11:52 PM ---------- Previous post was at 11:52 PM ----------

I'm on aosp 7.0

---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------

I also have automagisk installed if that's an issue.
[Magisk] aiola1982:
titanium backup pro 7.5.0.3 on aosp 7.1 (updates a few days ago from aosp 7.0) and no issues on both rom.

I'm using 2.0 beta 9 version of superuser ui, maybe thats the difference
[Magisk] HaoZeke:
Well.. Out turned out to be one faulty backup which wouldn't restore anywhere... Everything else works wonderfully :D
[Magisk] drago10029:
so the intructions are pretty confusing, maybe it's just me. Do I just i need root on my phone and to flash the zip in the OP and then install app from play store in the OP?

Thanks

"INSTRUCTIONS

You can install/update phh's SuperUser in Magisk Manager's Download section

If you have no root in the first place, please flash the zip in the attachment through custom recovery

A root solution is part of a proper Magisk installation.

After phh's SuperUser is installed, please install the SuperUser manager Application through the Play Store"
[Magisk] andrew2432:
No root prior, just need custom recovery. Stock recovery may be able to install zips too...magisk, then phh. Then install phh gui from play store, magisk manager from somewhere as well. Some devices need root to get custom recovery
[Magisk] drago10029:
let me know if this is correct:

1. I install any of the zips in OP

2. install magisk manager

my confusion is why is the phh app needed and is that different than the zip in the OP?
[Magisk] andrew2432:
Yeah magisk is the boot, phh is root. Magisk zip first phh zip 2nd boot to system, install phh su gui, install magisk manager
[Magisk] mlazzarotto91:
I have CM 14.1 on my SM-N910F and I've removed root from TWRP. I have Magisk V9 but if I install the version 266 or 266-2 I get this error

Inviato dal mio SM-N910F utilizzando Tapatalk
[Magisk] Didgeridoohan:
Logs! Logs people! In this case recovery.log...
[Magisk] mlazzarotto91:
I am sorry. I have uploaded the log on Google Drive

https://drive.google.com/file/d/0B-QwFqwQlZcrN3hDV25PZUpxY2s/view?usp=drivesdk

EDIT

solved reinstalling Magisk

Inviato dal mio SM-N910V utilizzando Tapatalk
[Magisk] Syoenth:
i got an Issue with the phh superuser app, it always deny to grant permission to superuser :/
[Magisk] chrcol:
I gave this a try given I just learned that supersu is now considered dead by XDA and the safety net enhancements, however a fair chunk of my root apps break using this supersu so I guess its not yet fully stable? or that the default eng mode is not the most compatible mode.

So at least for now I am reverting to supersu.
[Magisk] Tkbf:
No problem using phh's superuser at all here.
[Magisk] yochananmarqos:
I'm guessing you're using Magisk Hide? Apps randomly losing root until rebooting is a known issue.
[Magisk] Bingoo90:
It seems to drain my battery on Galaxy S6E, stock Android 6.0.1

I made a clean flash of stock ROM, then TWRP, Magisk v9 and phh's SuperUser 266-2.

I charged it before going to sleep and when I got up it had lost ~70%, also sudden and huge battery drops.

I then flashed stock rom again and no battery drain anymore.
[Magisk] yochananmarqos:
Logs or it didn't happen. Root access does not cause additional battery drain.
[Magisk] Bingoo90:
I'm not saying it's the root access. But something is preventing deep sleep and it can only be Magisk or phh's SuperUser.

I figured it's SuperUser because on http://xdaforums.com/showpost.php?p=64916199 the change log for v 2.66 reads "(systemless): Add deep sleep fix for Samsung 5.1+".

I'm going to post logs later.
[Magisk] Didgeridoohan:
With that kind of battery drain it's bound to be some rouge app... Maybe triggered by Magisk. Check BetterBatteryStats, Gsam or something like that to determine what app, wakelock or process is screwing your battery.

And don't confuse Chainfire's SuperSU with phh's superuser. Just because something applies to one, doesn't mean it does for the other. But, you never know...
[Magisk] m2d3:
When I flash the latest phh superuser 266-2, I don't have any sound while calling.

I can' t hear anyone and I can't be heard.

I'm using a One M7 running CM14.1

Thanks in advance!
[Magisk] Razor1973:
Magisk v9 + phh's SuperUser v266-2 was hiding root from SafetyNet on my LG G4 (H811) until yesterday that T-Mobile released a new version of their software. It upgraded from H81120p to H81120q. This no longer seems to work. Any ideas?
[Magisk] drago10029:
downgrade you phone software. never take OTA or Update until you confirm with mod maker. OEM's are smarter these days, and update phone to block root, mods, etc.
[Magisk] yochananmarqos:
I would try flashing the Magisk uninstaller and the stock boot.img (or custom kernel). Then flash Magisk + the phh superuser module.

I do not recommend this course of action. The latest software updates contain important security patches that could leave you vulnerable if you do not apply them.
[Magisk] Razor1973:
Tried that. RootChecker kept saying my phone isn't rooted. I'm going back to stock.
[Magisk] Syoenth:
I'm on Cyanogenmod 13 installed on a S3 and when itry to give a app superuser permission it don't show the prompt to autorize it
[Magisk] Didgeridoohan:
Just to make sure: you do have phh's Superuser app installed, right? https://play.google.com/store/apps/details?id=me.phh.superuser
[Magisk] Syoenth:
Yes, I have installed
[Magisk] Link_of_Hyrule:
Every so often I get a message that my su binary is out of date how do I fix this because there doesn't seem to be a way in the app and unless there's something I don't know I thought the 266-2 was the newest version?
[Magisk] Captain_Throwback:
If everything still works, just ignore it. Seems to be

an occasional side effect of Magisk Hide.
[Magisk] bountyman334:
is there anyone on nougat using magisk v9..it works fine for my lg v20...but after awhile it bootloops...
[Magisk] HaoZeke:
It's as stable as a rock on my aosp based nougat rom...

---------- Post added at 10:22 PM ---------- Previous post was at 10:22 PM ----------

I thought Magisk hide was discontinued? O.o
[Magisk] Didgeridoohan:
Seconded, on stock Nexus 6 Nougat.

No, just a little buggy. But I'm sure topjohnwu's working on it.
[Magisk] namquang93:
does anyone have the solution ?
[Magisk] yochananmarqos:
Bumping your own post and cross posting the same question is bad forum etiquette. See my reply in the Magisk discussion thread.
[Magisk] MrBrady:
Any idea if the Magisk Pay Tasker script eliminates the need to "Add a credit card and back-out" trick in order to get Android Pay working?
[Magisk] yochananmarqos:
That post is old and no longer relevant. The latest version of Magisk is working fine. Check the Magisk release thread.
[Magisk] laggardkernel:
For those who experience su not detected by apps like ES Explore, Termux, etc. I modified phh's SuperUser r266-2(Magisk) to bind mount su binary to /system/xbin, which should fix the superuser undetectable problem. Here it is. phh-superuser-magisk-r266-2_xbin_bind.zip

This mod use a flag called "BINDSYSTEMXBIN" in /data/.magisk or /cache/.magisk, just like what SuperSU does with .supersu. Set the value true in /data/.magisk,

BINDSYSTEMXBIN=true

and the su will be mounted to /system/xbin. Or, you could create the empty file "/magisk/phh/xbin_bind/enable" manually to enable bind mount su to /system/xbin.

To disable the process, just delete the folder /magisk/phh/xbin_bind, or flash back original phh-superuser-magisk-r266-2.zip in the OP.

NOTE: BINDSYSTEMXBIN is set false by default.
[Magisk] Captain_Throwback:
FYI - Enabling this will break SafetyNet compatibility.
[Magisk] laggardkernel:
I'm clear of this. Hence the flag is set false by default to disable bind_mounting su to /system/xbin.

There are still some apps could not detect su under /sbin and I'm only offering an option to those who suffer the problem.
[Magisk] denvit:
My bank's app blocks some functionalities if it detects that su is present.

Following you'll find the path checked. It fails at /sbin/su.

Hiding root from Magisk Manager doesn't help: I also tried to hide the root from Juice SSH, but ls /sbin/su still shows a result, plus "su" in JuiceSSH when root should be hidden shows the Allow / Refuse dialog of PHH.

Is there a way to solve the problem?

---

/system/app/Superuser.apk

/sbin/su

/system/bin/su

/system/xbin/su

/data/local/xbin/su

/data/local/bin/su

/system/sd/xbin/su

/system/bin/failsafe/su

/data/local/su
[Magisk] Captain_Throwback:
Are you using Magisk Hide? Because that works fine for every app I've tried...
[Magisk] denvit:
Yes I do. But apparently it doesn't work (I can clearly see it if I hide su from JuiceSSH, it doesn't get hidden)

Forgot to add that it also checks for the su binary with /system/xbin/which:

--- Edit ---

The strange thing about it is that sometimes SafetyNet fails in the Response validation, sometimes it doesn't. It just shows CTS profile not match.

The only way to make my Bank's app work (it has something like Android Pay integrated, a feature to use you phone as a contactless card) is to reboot the phone, and quickly open the app.

Once the back button is pressed there is no way to make it work again, unless the phone is rebooted again

-- Edit x2 --

Flashed everything again (system + vendor + recovery) and then installed in order: Magisk, PHH SU, ElementalX. Now seems to work.

SafetyNet checker returns a positive result and the app works without amy problem. The root seems disabled at the moment, although it worked fine when I firstly booted (I'm pretty sure I had root + SafetyNet + my bank app working at the same time)
[Magisk] Randshot:
My setup is like this:

- Oneplus 3

- Oxygen 3.2.7 (6.0.1)

- Magisk v.9 (Manager v2.5)

- phh's SuperUser (266-2)

- ElementalX Kernel

The weird thing is that SN shows a green response, but my banking app (S-pushTAN) detects that I have rooted my phone.

It seems to 'just' detect the Magisk Manager apk and the phh's SuperUser apk, because when I uninstall these two (without flashing the uninstaller zips), it works without any problems (SN shows red).

Did I do anything wrong?

Edit:

I also selected the app in the Magisk Hide list.
[Magisk] yochananmarqos:
Flash ElementalX first, then Magisk & the phh superuser module.
[Magisk] Didgeridoohan:
Have you selected your banking app in the Magisk Hide list?
[Magisk] Randshot:
Yes, I have.

The log also says that it unmounted the Magisk stuff for the app.
[Magisk] Didgeridoohan:
Seems like your bank got worried about Magisk... Probably not much to do.
[Magisk] JRoebux:
I just flashed phh supersu + Magisk + systemless Xposed and enabled Magisk Hide on Android Pay and I can't get through the checks. I'm running SultanXDA's CM13 ROM on my Oneplus One. Do I need to do something else to hide SuperSU/unlocked bootloader/Xposed?

---------- Post added at 10:54 PM ---------- Previous post was at 10:22 PM ----------

Edit: It works if I uninstall systemless Xposed. I thought the point of systemless Xposed was to circumvent the SafetyNet check? Is there a way to hide Xposed from Android Pay?
[Magisk] Captain_Throwback:
Magisk doesn't hide Xposed. So, uninstall Xposed.
[Magisk] JRoebux:
That works and was able to add a card in AP. Do I need to uninstall Xposed everytime I want to pay with AP?
[Magisk] tdurdenn:
Anyway to make this work with systemless 86.2 xposed?
[Magisk] :
Not knowing but the root is getting lost after some use ,the magisk manager also doesn't show any modules but after a reboot it comes again all goes fine for a while and again same problem also force closing some apps i am using magisk v9 + phh superuser r-s66-2 + xposed v87 system less + appsystemizer 1.3 + magisk hide (for PoGO) plz... Help if possible..???
[Magisk] Captain_Throwback:
Known issue.
[Magisk] tejefa:
Root denied on CM13

Flashed Cyanogenmod 13 Galaxy S3 i9300.

Installed Magisk v9 and phh superuser 266-2

Installed phh superuser app from Play store and enabled root access to app and adb in application.

Blank root prompt and denied root even when I configure superuser app to auto allow all requests.

Uninstalling and going back to SuperSU

Please fix systemless root on Cyanogenmod.
[Magisk] adrman:
Misread. Deleted.
[Magisk] yochananmarqos:
You need to install Magisk Manager and the phh superuser module. You don't flash the regular phh superuser ZIP with Magisk.
[Magisk] tejefa:
I followed the instruction on the official page

http://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

which reads:

"If you're not rooted... and you need a clean start...

Download the latest Magisk Version phh superuser

Flash Magisk zip first

Then flash the phh superuser zip"

This same installation worked on my Galaxy Note 4 stock rom but not on Galaxy S3 Cyanogenmod.
[Magisk] guessingagain:
I am on cm13. Here's what I did:

Remove root completely (full unroot)

Flash magisk

Flash phh module.

Works perfectly
[Magisk] akk29:
Superuser permissions

Do SuperSU and phhsuperuser use the same method to detect when an app requests superuser permissions?

My ROM (JDC Team AOSP 7.1.1 for S4) comes prerooted with SuperSU. Unrooting and installing Magisk and phhsuperuser works for all apps except the STweaks app (https://github.com/AOSP-JF-MM/STweaks/tree/aosp-7.1.1) which doesn't not request superuser permissions with phhsuperuser (Magisk version).

Any ideas why with systemless SuperSU STweaks works fine but with phhsuperuser it doesn't request superuser permissions correctly?
[Magisk] FlemishDroid:
It's a known issue but I think it only happens when Magisk Hide is enabled. I'm not 100% sure tough.

Sent from my S7.
[Magisk] Captain_Throwback:
Yes, it's only when Magisk Hide is enabled. It's being worked on.
[Magisk] Oki:
I have a ZTE Axon 7, stock system image with unlocked bootloader. I have added a patch to the boot just to hide the bootloader unlocking to safetynet.

I am following the instructions: I installed the apps for Magisk and phh Superuser. Them I booted into TWRP and flashed Magisk v9, then phh Superuser Magisk r266-2. THe outcome is that the system is not rooted. I can't even execute su in the terminal.

Any clue on what is happening? Thanks in advance.
[Magisk] Captain_Throwback:
Magisk will hide the bootloader unlocking, once Magisk Hide is enabled - a separate patch isn't necessary.

Did the zips flash successfully? Where's your recovery log?
[Magisk] Oki:
I thought it was flashing properly. You can find the recovery log here. Any other idea?

After that I install both apps, but Magisk Manager is not detecting the binary and can't access the Data partition. It works when SuperSU is installed, but when paired with phh Superuser Magisk is like not having root at all for some reason.

Thanks
[Magisk] Captain_Throwback:
Have you tried the latest Beta version of the app from the phh Superuser thread? Have you tried the Beta versions of Magisk and Magisk Manager to see if they work?

The install log looks fine.
[Magisk] Oki:
I have tried with the latest Magisk V10 beta and MagiskManager v2.6 dated today. Same outcome. I haven't found any beta version of the phh-Magisk Superuser. Latest is r2.66-2.

SUperSU installs fine, but breaks SafetyNet.
[Magisk] acultr:
can you please provide me the link to the beta version? thank you
[Magisk] coderus:
Anyone successfully installed Magisk and phh superuser on OnePlus 3T with 7.1 Android? I flashed Magisk v9 zip and phh superuser latest zip, Magisk manager shows everything is up-to date, show phh superuser module, then i installed phh superuser from play store, when it launching popup is showed about outdated su binary. When i click on it new superuser window opened and nothing happened. Applications doesnt see root access.
[Magisk] adrman:
The latest beta can be found here.
[Magisk] coderus:
for my OnePlus 3T 7.1 Android 266-2 phh superuser not working. But previous 266 versoin works fine. Magisk v9.
[Magisk] Oki:
That is a beta for the app, not the binary. It seems the problem is the binary.
[Magisk] adrman:
Sorry if I misread the request. The unofficial thread is right here in the Magisk forum.
[Magisk] Nomelas:
is there any way to hide this root, similar to suhide for superSU? (I don't mean root toggle either, i mean always hide root from specific apps - not PoGo related)
[Magisk] tdurdenn:
Xposed+Pogo= NOGO (besides suhide+supersu 3+xposed86.2) have to hide root but xposed will work.
[Magisk] :
No the problem is not PoGo it's work well and good after disabling xposed and using magisk hide but the root loss due to magisk hide but it is now fixed i am now using magisk v10 beta and magisk manager 2.6 beta pre-releases, it also passes safetynet check when xposed is disabled and the root is also not getting lost it's fixed???
[Magisk] g96818:
you need to reflash phh if you get that msg or try using magisk v10. v9 unroots itself on random shut downs if magisk hide is activated and it's a known issue. I usually know it's unrooted if I need to hold down the power button for a significantly longer time to power on the phone so I'll just load twrp from the unlocked bootloader warning and reflash phh.
[Magisk] coderus:
I solved my problem by flashing 266 phh instead of 266-2. Also cant make working hide, busybox and systemless hosts. It never enables after reboot.
[Magisk] Oki:
The issue is that phh-superuser for Magisk is not rooting. However when using Superuser r259 or SuperSU, there is no problem with root, however they break SafeNet. Magisk or phh-Superuser apps are nor the problem. Something happen with The ZTE Axon 7 ROM, Magisk is not working, not even when using the latest v10 beta. phh Superuser for Magisk r266 is neither working.
[Magisk] lakid06:
titanium backup issues

I am unable to uninstall a system app but it says it did. After reboot it is still there. I also get a warning saying Your SU binary (version '17me.phh.superuser cm-subindsuint") is functional but might not work reliably on some android 4.3+ roms. Any ideas on how to fix this? Thanks
[Magisk] waylo:
The whole point of systemless root (and Magisk) is that it doesn't/won't touch /system. So in trying to remove a system app, you are doing exactly the opposite of why you install Magisk in the first place. Depending on your operating OS version, you could establish root the old-fashioned way 'system-full' and that will allow you to uninstall the system app.

Otherwise, just freeze the offending app.
[Magisk] H4X0R46:
Anyone having the issue where this module just disappears randomly leaving you unrooted? My phone does this and I have to go back into recovery and reflash this phh zip to get root back. Not sure what it could be. Using a Nexus 6 (Shamu).
[Magisk] Oki:
I gave up on Magisk. I have tried all the possible combinations and phh Superuser for Magisk doen't woth in the Axon 7 stock rom. I had to follow the SuperSU+SUhide+Xpose86.2+Root Switch app. I would love to have per app hide, but for some reason phh Superuser for Magisk can't root the stock rom of this phone while SuperSU and standard phh Superuser can.
[Magisk] Didgeridoohan:
I see you did provide a recovery log which as previously stated looks fine. But, I don't see any Magisk logs...

Since your root didn't work with Magisk you wouldn't be able to get the logs through Magisk Manager. Instead you'd have to install Magisk, let the device boot once and then boot back into TWRP to pull the magisk.log from /cache.

If you feel you have the time and energy... It could provide some insight.

Just a heads up though: Magisk cannot hide Xposed.
[Magisk] Captain_Throwback:
[MENTION=319057]Oki[/MENTION]

Logcat from bootup would probably also be helpful, and I didn't see if boot.img was provided, to make sure it actually got patched?
[Magisk] abel408:
I've tried installing phh super user at least 10 different times. I must be doing something wrong. I can see that phh is enabled in magisk manager, when I open the phh super user manager app, I just get a blank white screen that looks like this:

[IMG="phh"]http://i.imgur.com/ZtLj7ip.png[/IMG]

I can get to the settings of the app and I see that "Superuser Access" is disabled. Enabling it does nothing. Logging is enabled, but I'm not sure where the logs are.

Any help is greatly appreciated!
[Magisk] mucha.k1994:
Did you install (or flash) a superuser zip first? It's seems like app superuser don't see binaries or something like this.