yashsingh1/xdaforums huggingface dataset:
[Magisk] CSX321:
Yeah, I'm getting kind of frustrated. I haven't been able to make a payment with any of this on my N5 running stock 6.0.1 w/August patch plus nothing but Magisk and the compatible phh Superuser. I've tried v1 and v2 of both. It all appears to work fine. Mounts and unmounts as it should. Safetynet check fails/passes when it should. But if I unmount and try to make a payment, I get the message in AP that says to unroot my device.

I've just reflashed stock boot, system and recovery. Then decided to get crazy and flashed TWRP and ElementalX, and pushed my own ad-blocking hosts file while in TWRP. Tried a payment...boom...it works fine, unrooted but with all these other changes. I don't know what I could be doing differently from anyone who's reportedly gotten AP to work using Magisk. I'm a developer and pretty well know what I'm doing, but I can't make this work.

Really the only thing I can think of at all is that I haven't changed the card. It was added a while ago. Are the people getting this to work adding the card *after* installing Magisk/Superuser? Since I'm getting the unroot your device message, I feel like that's irrelevant, but maybe not?
[Magisk] topjohnwu:
Magisk v3 is now live.

The new disabling method will now not only kill the background process - su daemon, but also kills all possible processes that has acquired root access.

Root shells and root apps will "NOT" survive after switching to disable. "Nothing", seriously, is able to gain root access, or has root access at that period of time.

The results of Android Pay is mixed with some success and some failure, but in these few days I've kept in touch with several people testing actual transaction for me.

The result is positive, Even with Magisk Xposed (v86.3+) installed!!

As you can see, Google has no possible way to check if your device is rooted or not, and no single trace and background process has root privilege.

If this update still don't work, then Google is definitely detecting other factors, not root itself.

One thing I suspect is boot image detection. All failures seems to be Nexus devices.

The reason I think of this is the fact that Nexus device checks your boot image when receiving OTA updates.

So people unable to get Android Pay working, please try to delete "/data/magisk.img" through custom recoveries and reboot.

This will disable all Magisk functions, but your boot image is still modified. See if Android Pay still refuse to work.

If that's the case, I still have ways to bypass this. But first of all I need to know the actual point why Android Pay fails before I can start fixing the issue.

Thanks a lot!
[Magisk] exodius48:
Does possible to fix "SU binary might not work reliably on some Android 4.3+ ROMs..blablabla" on Titanium Backup app?

Cc [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] yochananmarqos:
There's nothing to fix. Titanium detects you're not using SuperSU, so that message is displayed. You have the option to never show the message again. As far as I know, Titanium works fine with phh.
[Magisk] FurySh0ck:
There is, but you have to flash factory images.

Check out on the YouTube.

Anyone knows what to do in order to avoid flashing factory images? I also want to switch from cf to phh, but can't find a way around.
[Magisk] Didgeridoohan:
I've absolutely no idea what PDA or Csc is... Some Samsung thing, I assume?

This is what I did on my Nexus 6 (android Marshmallow at the time) and my wife's Nexus 6P (android Nougat at the time). Your mileage may vary...

-Extracted boot image from the current applicable factory image (optional).

-Chose full unroot option in SuperSU app (it can restore the backed up boot image from prior to rooting). I had SuperSU 2.7x-something installed systemlessly.

-Booted into TWRP and flashed the extracted boot image through TWRP's install image function (optional). This step is just to be sure to have a clean boot image.

-Flashed custom kernel (optional).

-Flashed Magisk.

-Rebooted.

-Uninstalled SuperSU app and the SuperSU Pro license file.

-Installed Magisk Manager and phh's superuser app.

-Done.

If you don't want to flash the stock boot image yourself, just let SuperSU restore the backup and hope it works. Make sure to have a backup of your own...
[Magisk] Jsilver73:
Xplore file manager from play works ;)

---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------

Could anyone link me to the unofficial phh super user manager please - my search is fruitless :confused:
[Magisk] Mao04:
https://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394/post70150700
[Magisk] popper668:
will this work in conjunction with Titanium Backup?
[Magisk] mobileman88:
Yes it does for me
[Magisk] smk513:
Deleted
[Magisk] jhedfors:
Did you install Magisk v10.2?
[Magisk] xstormli:
hey chief wu, i ran into a lot of shiet on my cell.

i installed v10.2 and 3.0 manager

1. there is no installed module displayed after xposed installed.

2. there is no repo for me to see or download.

3. root is driving me nuts.

4. manager is FC on me, i don't think it is functional at all on my cell.

after my xposed is installed, i can't stand my phone without root, so i uninstalled magisk sadly.

my variant is redmi 3 pro running cm13, android 6.0.1, by [MENTION=6083514]Anik_khan[/MENTION]
[Magisk] andrew2432:
Do you have a twrp backup before root? Restore and only check boot
[Magisk] FurySh0ck:
As far as I can tell, it's defining the source of the phone (country it was produced in, vendors, etc...)

I think every Android based device has it. It's at phone status under build section.

I don't have a twrp backup before root, but I have a similar device which I didn't root. How can I check the boot?
[Magisk] andrew2432:
I meant a backup. Do a restore in twrp but only the boot prior to flashing magisk
[Magisk] smk513:
yes, magisk v10.2 + phh topjohnwu r2.
[Magisk] FurySh0ck:
I have a backup through TWRP prior to Magisk (but the device was rooted in that time, not sure it has an effect on the the boot though).

Where can I check the boot?
[Magisk] Didgeridoohan:
Nope, I think it's a Samsung thing. I did a quick search about it and all hits refer to Samsung... A well, doesn't really matter.

Anyway, like I've said a few times already now, SuperSU should have a backup of your boot image from before rooting. It should be able to restore that when using the full unroot option in the SuperSU app. YMMV...
[Magisk] FurySh0ck:
All right, I will try it. Thanks for advice.
[Magisk] andrew2432:
That will unmagisk it. The magisk uninstaller will also find stock boot and replace yours with it if you haven't moved it around.

It depends where the root is located. If its system root its in /system if its systemless your boots patched and its in.../data?? Not sure exactly how phh and cf su do it, skid. But your boot needs patched, so if you restore an old one you can't access root and should pass all checks.

Twrp, hit restore and uncheck everything but boot. Cache, art/dalvik, system, data, boot, efs. Only check boot. If its before magisk it will bring your old boot. The uninstall zip may do it if you flash it from twrp
[Magisk] crusader727:
Fix trouble with F2FS /data partitions

"An Explanation of why SuperSU has Trouble with F2FS Data Partitions" from xda main

https://xdaforums.com/showpost.php?p=70492947&postcount=8793

--> caused by a missing patch in kernel
[Magisk] inotrest:
I can confirm that, this solved it for me. This Xposed Module just tricks the MagiskManager. If you use a different app, e.g. SafetyNet Helper it actually shows a payload validation error.
[Magisk] inotrest:
In case it is helpful. I'm using a OnePlus 3 with Sultan's latest January Rom. Without Magisk I have no problems passing the test. As soon as I install v10.2 I fail the test. Here is the log:

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Preparing modules
* Stage 1: Mount system and vendor mirrors
* Stage 2: Mount dummy skeletons
* Stage 3: Mount module items
* Stage 4: Execute module scripts
post-fs-data: /magisk/xposed/post-fs-data.sh
Xposed: Mount: /magisk/xposed/system/lib64/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib64/libart.so
Xposed: Mount: /magisk/xposed/system/lib64/libart-disassembler.so
Xposed: Mount: /magisk/xposed/system/lib/libsigchain.so
Xposed: Mount: /magisk/xposed/system/lib/libart.so
Xposed: Mount: /magisk/xposed/system/lib/libart-compiler.so
Xposed: Mount: /magisk/xposed/system/bin/patchoat
Xposed: Mount: /magisk/xposed/system/bin/oatdump
Xposed: Mount: /magisk/xposed/system/bin/dex2oat
Xposed: Mount: /magisk/xposed/system/bin/app_process64
Xposed: Mount: /magisk/xposed/system/bin/app_process32
* Stage 5: Mount mirrored items back to dummy
* Enabling systemless hosts file support
Mount: /magisk/.core/hosts
** Magisk late_start service mode running...
service: /magisk/phh/service.sh
phh: Live patching sepolicy
phh: Moving and linking /sbin binaries
phh: Mounting supath
phh: Starting su daemon
* Removing tampered read-only system props
* Starting Magisk Hide
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=mnt:[4026534112] Zygote(1) ns=mnt:[4026534131]
MagiskHide: com.google.android.gms.unstable(PID=8001 ns=mnt:[4026534290])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: Unmounted (/system/bin/app_process32)
MagiskHide: Unmounted (/system/bin/app_process64)
MagiskHide: Unmounted (/system/bin/dex2oat)
MagiskHide: Unmounted (/system/bin/oatdump)
MagiskHide: Unmounted (/system/bin/patchoat)
MagiskHide: Unmounted (/system/lib/libart-compiler.so)
MagiskHide: Unmounted (/system/lib/libart.so)
MagiskHide: Unmounted (/system/lib/libsigchain.so)
MagiskHide: Unmounted (/system/lib64/libart-disassembler.so)
MagiskHide: Unmounted (/system/lib64/libart.so)
MagiskHide: Unmounted (/system/lib64/libsigchain.so)
MagiskHide: com.google.android.gms.unstable(PID=11455 ns=mnt:[4026534325])
MagiskHide: Unmounted (/sbin)
MagiskHide: Unmounted (/magisk)
MagiskHide: Unmounted (/system/etc/hosts)
MagiskHide: Unmounted (/system/bin/app_process32)
MagiskHide: Unmounted (/system/bin/app_process64)
MagiskHide: Unmounted (/system/bin/dex2oat)
MagiskHide: Unmounted (/system/bin/oatdump)
MagiskHide: Unmounted (/system/bin/patchoat)
MagiskHide: Unmounted (/system/lib/libart-compiler.so)
MagiskHide: Unmounted (/system/lib/libart.so)
MagiskHide: Unmounted (/system/lib/libsigchain.so)
MagiskHide: Unmounted (/system/lib64/libart-disassembler.so)
MagiskHide: Unmounted (/system/lib64/libart.so)
MagiskHide: Unmounted (/system/lib64/libsigchain.so)

SELinux is Enforced.
[Magisk] Didgeridoohan:
Have you tried without Xposed? Magisk can't hide that... Or you could try disabling it.
[Magisk] inotrest:
OK it is Xposed. But I installed system-less Xposed from the MagiskManager. And with MagiskHide I was able to hide Xposed from e.g. VMWare Boxer. I thought that this was the point of this modified Xposed package for Magisk.

Why is Magisk able to hide Xposed from apps, but not from the SafetyNet Check?
[Magisk] Didgeridoohan:
Magisk isn't at all designed to hide Xposed from Safety Net. It hides itself and it's modules, yes, so I guess an app that doesn't look too hard will be able to be put on the Magisk Hide list and not see Xposed. Safety Net isn't one of them... When I think about it, what I just wrote doesn't really make any sense, I think. I just have no idea. All I know is that Magisk cannot hide Xposed from Safety Net.
[Magisk] inotrest:
Thank you for the clarification. I just thought that installing Xposed through MagiskManager would make Xposed a Magisk-Module and hide it from the system, especially since it shows up in Magisk's Module-Section.
[Magisk] Didgeridoohan:
Well, yes. But it also makes a lot of modifications and adds stuff to the system (systemlessly, but still). The kind of heavy modding that Xposed is, isn't easy to hide... I'm not too familiar with the actual inner workings of Magisk to give you a good answer though...
[Magisk] FurySh0ck:
I told I have a backup prior to Magisk, not prior to root.

Anyways, this is what I think I ought to try:

1. Use the "full unroot" cf has to offer.

2. Go to twrp

3. Flash the Magisk Uninstaller, the new Magisk version, and then phh's supersu according to the Magisk version (in that order)

4. Hope for the best.

In case this won't work (what will probably happen), do you know where can I get a boot image for my device? It will probably make things much easier.

I use galaxy S4 GT-I9515. I couldn't decide which firmware I should get from sammobile, so maybe you know other trustworthy site.

Anyway thanks for the help, I think I know what I've been doing wrong all this time.
[Magisk] LucentBirch:
Does my ROM have to have selinux enforced for safety net to pass even with magisk?
[Magisk] Shadowghoster:
Yes, SafetyNet requires enforced selinux to pass.
[Magisk] LucentBirch:
Poop. Okay...Guess I'll have to wait until they fix that.
[Magisk] Captain_Throwback:
Have you read the official thread? [MENTION=4470081]topjohnwu[/MENTION] is busy with school. Please stop insisting that someone look into this. There's only one dev for Magisk, and he can't solve everyone's problems, especially for a device he doesn't have. Maybe what you provided will be enough, or maybe not. Honestly, the easiest way would be to donate a device to him, and then he can troubleshoot directly. Are you willing to do that?
[Magisk] Oki:
We all understand his situation, some of us already have that problem, maybe not school now, but work. I just insisted because I thought someone else could have found a way to overcome this issue.

If the answer was "I do not have time to look into this", it is OK, but no answer means the message didn't went through. Now your answer is loud and clear. Thanks.
[Magisk] andrew2432:
That should work. You can manually delete the folders.. Maybe /data/bin/su and xbin as well. But you can also find what they are in forums. The magisk uninstaller SHOULD find your boot image itself and reinstall it. You have magisk plus cfsu right?

I have a file called stock_boot.IMG on my extSD card. I didn't put it there, see if you have one too. Just lying around
[Magisk] inotrest:
Thank you for your explanation. Just on question; ks Magisk as powerful as Xposed? What I mean is, could the functionality of an Xposed-module be implemented as an Magisk-module? So at some point in time one could get rid of Xposed?
[Magisk] Captain_Throwback:
They're not the same thing, nor do they have the same purpose. They are mutually exclusive, so one will never replace the other.
[Magisk] felipe.vella:
There is Axon 7 compatibility ?? Thanks!
[Magisk] JohnCorleone:
It seems like there are questions being asked about several very different types of devices...fortunately my HTC 10 has a bare bones Sense on Nougat..my quick toggles and such are not any different than the Nexus devices unlike the Samsung devices...then those have Knox. I am just searching for the newest phh superuser beta if anyone has it..I think it's 275 maybe??
[Magisk] Didgeridoohan:
Yes, unfortunately all devices are not equal...

For Magisk there is nothing newer than phh's superuser topjohnwu r2. If there are newer commits I guess you could build them yourself. Phh's r275 you can find in phh's thread.
[Magisk] JohnCorleone:
Let me tell you...i have been up all night long and I suddenly can't run a RUU full stock update! This has literally only happened once and I have owned 6 Samsung devices, 7 HTC models, 2 LG phones, several tablets and a few pure Nexus devices....every now and then things I have been doing for YEARS suddenly decide to drive me crazy! And I was really hoping to get everything dialed in before my birthday tomorrow...of course I need to go to the DMV today but DAMN...the most basic "plug in the phone and click start" full updates refuse to work!!!
[Magisk] Didgeridoohan:
I feel you... It sucks when it happens. I'm just now trying to figure out why flashing a new Magisk module suddenly almost wiped my phone. All text messages gone, all permissions wiped, notification sounds are gone, and a few more things. And of course, Magisk root doesn't load either. :confused:
[Magisk] lampel:
Unplug the usb, reboot the pc, reopen the ruu, and reconnect - sometimes it helps...
[Magisk] JohnCorleone:
I just saw a post in another thread and the guy had the EXACT SAME problem! He is on Windows 10 though...i am still on Windows 7 because I only use the laptop to customize my phone! It starts then gets a "Installshield error" and something about things open in the background. I am going to have to just reflash the first Nougat RUU then OTA because I am not the only one who has the exact same problem....too bad it took me 8 straight hours to find that post! Thanks for the tips though.. I have to run to the DMV and renew my license real quick and then I will get back to it. MAYBE we both got corrupt downloads. I did download it on my phone and pushed it to my laptop so who knows?!
[Magisk] 3dawg:
Hello. On any device which doesn't have an official Nougat, I have been unable to pass safetynet when using Magisk. N5 with purenexus, Moto G with CM14.1, and most recently LGG3 D855 when using CrDroid 7.1.1.

I am flashing zero extra mods, simple the rom followed by magisk. Why is it that all of these roms fail to pass?

I have included a log for the G3 which could hopefully provide you with some insight. Thank you for any help!

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

* Preparing modules

* Stage 1: Mount system and vendor mirrors

* Stage 2: Mount dummy skeletons

* Stage 3: Mount module items

* Stage 4: Execute module scripts

* Stage 5: Mount mirrored items back to dummy

* Enabling systemless hosts file support

Mount: /magisk/.core/hosts

* Enabling BusyBox

Mount: /magisk/.core/busybox

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Moving and linking /sbin binaries

phh: Mounting supath

phh: Starting su daemon

* Removing tampered read-only system props

* Starting Magisk Hide

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

Zygote(0) ns=mnt:[4026534792]

MagiskHide: com.google.android.gms.unstable(PID=6925 ns=mnt:[4026534852])

MagiskHide: Unmounted (/sbin)

MagiskHide: Unmounted (/magisk)

MagiskHide: Unmounted (/system/xbin)

MagiskHide: Unmounted (/system/etc/hosts)
[Magisk] yochananmarqos:
Wrong thread. Your Magisk log is normal so your problem lies elsewhere.
[Magisk] 3dawg:
Thanks and apologies for the wrong thread.

Do you perhaps know what causes safetynet to pass or fail on a ROM by ROM basis? Magisk works great on the N6/6p/5x/Op3 from what I've tried but then fials here. The one thing they all have in common is official builds of Nougat. Is it something related to that?

Where would be better to post this? I appreciate the help.
[Magisk] yochananmarqos:
Magisk General Support / Discussion
[Magisk] Kurai Kitsune:
Just adding my comment in case someone is searching for an answer.

Phone: HTC10 UK version.

Had to change CID and MID to a US standard so that the latest Nougat RUU from HTC would install. This requires Bootloader unlock and S-OFF with Sunshine.

Followed usual steps for TWRP and Magisk installs.

Using Magisk Manager making sure that "Enable Magisk Hide" is enabled.

Worked perfectly.
[Magisk] de.er:
Hi mate, did you find a solution for this?
[Magisk] popper668:
This was suggested. I did not try it.

Originally Posted by Jimsilver73 View Post

Xplore file manager from play works

If you get it working could you reply back? Thanks
[Magisk] de.er:
I'm using Mixplorer and am able to access sticks connected by usb by accessing /mnt/media_rw but what I really need is to mount the usb drive. I'm using a syncing app to sync a number of folders to a stick and the app only works with mounted drives. StickMount was doing the job brilliantly, but doesn't seem to work with magisk....
[Magisk] popper668:
That's exactly what I thought. Thanks, looks like a dead end. I've switched back to Superuser
[Magisk] tjluvu:
i have wierd problem.... i am able to pass safety net ..... pokemongo works fine ..... even magisk hide works well on some apps ... but there are some apps which still detect root even after selecting them in the magisk hide app list.... any thought about what might be the problem ... i am on a lineageos based rom.... which had cm root before i flashed magisk
[Magisk] tag68:
Installed Magisk 10.2 via flash on Moto Z Play 1635-2 6.0.1 Patchlevel Nov 16. Magisk Manager says No root. Flashing phh superuser 20170112 I get root, but Magisk can not hide anything. Restore original, flash Magisk 10.2, flash phh's SuperUser topjohnwu r2. Magisk says No Root. Flashing phh superuser 20170112 (until I know what to do), got root. And now? What logfile do you need?
[Magisk] Didgeridoohan:
A recovery log from flashing phh's SuperUser topjohnwu r2 (or Magisk v10.2 if you've uninstalled it) and a Magisk log from the following boot. You can pull the Magisk log from /cache through recovery.
[Magisk] tag68:
Did restore boot partition, try SuperSU 2.79SR3 with error, restore boot partition, try topjohnwu r2 with error. Log of this action is attached here, hope that is ok. Just ignore there is SuperSU 2.79SR3 at beginning of logfile please ;)

Is the Magisk log still needed when there is an error about readonly to see in the log and no su available?
[Magisk] naughty6t9:
yup unfortunately NAB detects Magisk despite of using Magisk hide

any solutions [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] mastabog:
I'm on a Galaxy A5 2015 (SM-A500FU). A few months ago I installed phh's superuser for magisk (256) + magisk + xposed systemless. Everything worked fine until a few days ago when the phone just rebooted out of the blue (literally) and came up without root ... just like that. TWRP 3.0.2-1 is still working fine.

I tried uninstalling magisk using the magisk uninstall zip, and reinstall it, which is supposed to install phh's root (the open source ver) but still unrooted.

I then uninstalled magisk again using the magisk uninstall zip and installed phh's superuser topjohnwu r2 from here.

I get phh's superuser app and if I open it I can see my old apps which were allowed root access, but if I tap on one of them, it opens a blank screen (it used to have controls for log and prompt and other info).

Out of desperation, I tried flashing chainfire's SR1-SuperSU-v2.78-SR1-20160915123031.zip ... which did root the phone, but was obviously conflicting with one of the above as it could not update the SU binary (keep trying for minutes and then failing) and I know it's not supported by Magisk.

I _REALLY_ don't want to wipe everything just to fix this.

Is there a way to completely uninstall phh's superuser and start fresh, so I can install root+magisk+Xposed without wiping?

Thanks in advance for any help.
[Magisk] mbs.yaswanth:
phh superuser doesnt work on yu yuphoria

i had tried all the versions of superuser:phh_superuser-magisk-r259,r266,r266-2,r2 to flash via twrp on my yu yuphoria.

nothing worked........ it shows error "unable to update su binary in that phh super user..........".

pls help.... i actually want to run apps like pokemon go, irctc rail app and other secured apps on my device without uninstalling root.......!

i sucessfully installed magisk.... but when i tried to install phhs superuser, the app 'unfortunately stopped'

i am tring to do so all the day!!

pls help
[Magisk] Didgeridoohan:
Some clarifications are needed. Where are the errors showing (I'm assuming TWRP), what app crashes and please provide a recovery log from flashing. What ROM and Android version? Also, since you say you have Magisk successfully installed a Magisk log would be good. It's in /cache and you can get it through TWRP.

For Magisk Hide to work you'll need the latest version of Magisk superuser (currently topjohnwu r2), ignore the others.

With a stock unrooted system, on a compatible device, all you should need to do is flash Magisk v10.2 in TWRP. Phh's superuser topjohnwu r2 is installed by default.
[Magisk] yochananmarqos:
Magisk 10.2 will install phh superuser for you, no need to flash it manually.