yashsingh1/xdaforums huggingface dataset:
[Magisk] jonners59:
Thanks Teddy.

I took a look at it and it states "These builds are NOT for the faint of heart: professional users and developers only!" and I am neither. I think I may make things worse! :D

---------- Post added at 09:22 AM ---------- Previous post was at 09:09 AM ----------

Thank you Martyfender

That does seem to have all I need to do a short term, temporary fix whilst Magisk sorts the Goodgle Pay issue out. The problem I have with it though is the settings it suggests changing (1, 2 and 3), I do not seem to have access to. I suspect this was written for a specific device or ROM. But I really appreciate the help and will continue to try and find my way around my device to hunt these settings out. I've pasted here as it may help others. There seem to be a lot of us about.

The new Google Play services update caused this.

﻿Temporary workaround:

1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.

2. Search "Google Play services" in the Settings search bar.

3. Press the three dots and press "Uninstall previous updates".

4. Download this update - [URL="http://www.apkmirror.com/apk/google...-7-99-release/"]http://www.apkmirror.com/apk/google...-7-99-release/[/URL]
Pick your needed edition (arm or arm64, etc.), download it and install it.

5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.

6. Download Google Pay from the Play Store.

7. Set up your cards. Enjoy!

Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.

Tested Google Pay versions:

2.79.x-2.83.235070858 - working

Tested Google Play services versions:

14.7.99 - working

14.8.49-15.0.10 - not working, downgrade to 14.7.99
[Magisk] ManDone.vRs:
I have a Galaxy s8 with stock Android 9 . Just rooted but when i join on my wallet it's say : Your device has been rooted . If you lose money or transactions we are not responsable for that. Rooted device may be unsafe

But I selected in magisk hide the wallet and still say the same . Any solution ? Thanks.
[Magisk] wirelesskebab:
Sammy Galaxy Tab S2 Stuck

Samsung Galaxy Tab S2 SM-T710 Android Version 6.0.1 Security Patch April 2, 2016 Current Version: T710XXU2CPD9/T710XAR2CPE2 (Stock) (Exynos 5 with 32bit OS?)

Only TWRP + Magisk flashed this round, have tried different combinations such as also flashing your systemless exposed or only Magisk or preinstalling phh's superuser, have waited 5 minutes at boot and it never gets passed the boot screen. (Not the fancy samsung screen, but the one before it.)

No logs for Magisk were produced in the given directory as per your troubleshooting instructions, I need to know specifically what log you want from my tablet... ADB is not functioning for the same reason I believe, however I can copy logs manually via TWRP's file management system. (Assuming the ones you want have enough time to be generated...) I have found several logs under cache/recovery such as last_kmsg, last_last_kernel, last_log etc. :(

I appreciate your assistance and time spent on this and it seems very promising, I hope to get it working for my tablet, thanks. :good::eek:
[Magisk] Twacrs:
I have the same issue. I cant install phh's su because it gives an error in recovery. I'm running sultanxda's cm13 builds
[Magisk] edu4rd0zs:
Confirmed that Magisk works on Uberstock 8/2 build for Nexus 6p. I got it to work by performing these steps:

-Boot into TWRP

-wipe, advanced wipe = dalvik/cache,cache,system and data. Did it a second time.

-Flashed ROM, Banks 8/5 Gapps

-Flashed UPDATE-unSU.ZIP by 0smosis (system root remover)

-Flashed Busybox 1.24.2 by 0smosis (As I read that busybox offered by Magisk is broken or not working correctly)

-Flashed Magisk-v1.zip

-Flashed phh-superuser-magisk.zip

-Flashed Xposed-v86.3

-Booted into system

Boot up took a little while but Magisk was working flawlessly. Mount/unmount toggle worked. To my understanding, this ROM has kylo kernel built into the rom, which is not stock. Not sure why pure nexsus mod by kantjer, the toggle to moun/unmount supersu does not stick. Doubt this would work on garrykd's and nathanchance's rom either. Since Pure nexus and Chroma are based off google's stock kernel, Magisk might work. Hope this helps in your future development [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] MrBrady:
Yes, but with the stock kernel (Nexus 6 Chroma ROM). Tried earlier with Benzo kernel and it failed. Going to try with Elemental X this weekend.
[Magisk] DarkN3ss61:
Can we use Tasker with Magisk? If not who do I need to contact to get this implemented?
[Magisk] devilloki:
forgive my poor english.

my devices is : huawei honor7 TL01H

my soft ver is :Emui 4.0.1-6.8.1

my rom is stock boot,stock system.

flash Magisk-v1,cann't boot,display:

RESCUE MODE
Attention!
Please update system again

Error!
Func NO:10(boot image)
Error NO:2(load failed!)

upload log file,and boot image.

in log file,i found:

- Flashing boot image
dd: writing '/dev/block/mmcblk0p27': No space left on device
so,i guess new boot img is too big.

pls help me [MENTION=4470081]topjohnwu[/MENTION]

[MENTION=4470081]topjohnwu[/MENTION]

supersu 2.76 has same issue.
[Magisk] smohanv:
I am on Huawei P9. I took stock boot image from UPDATE.APP and flashed with TWRP. It damaged my boot and didn't complete booting. It was stuck in eRecovery screen. Finally managed boot image from custom ROM (i.e Future ROM which is kang based). I do not have stock image backup to start the process from fresh boot. Is there stock boot image available for Huawei P9. Also, I have flashed with magisk, supersu 2.76 and xposed 86.3. Can I dirty flash phh's supersu. Will this make AP to work. I am little reluctant to use phh's mainly because some of chainfire's app do not work (like Cf.Lumen).
[Magisk] topjohnwu:
A possible explanation for the Android Pay thing is that it is detecting the background su daemon process.

Or it is detecting the sepolicy changes etc. Or it is searching for a su binary file. Or any possible ways to detect it. Many things come to my mind.

Can any one confirm that by only using Xposed , will Android Pay work?

Personally I cannot use Android Pay in my country, I think there are still ways to overcome the detection, but it involves actual transaction so I cannot test. This project is actually aimed on the systemless interface part, the AP compatible thing is just one thing I'm playing with after Magisk is done.
[Magisk] devilloki:
stock boot img can flash?
[Magisk] topjohnwu:
OK guys, I got a way to really unroot your device temporarily. An update will come soon so you can test if it really works.

Currently Magisk will only unmount su from PATH, but the superuser daemon will still run in the background. The current implementation is that nothing can detect and invoke root, but those who know the real path of the su binary are still able to gain root (that's why Magisk manager is able to mount the root back). This will pass the Safety Net, but it seems that it's unable to do a real transaction.

So in the new update I will kill the daemon when disabling. What this mean is that nothing will be able to restart root. After thinking for a while for a possible solution, I think the only way is to set a countdown. So the for the new update I'll let you set a time to completely disable root. There is no way to get any kind of root access in that period of time, you have to wait until the count down goes to 0 and it will automatically setup root again.

If this won't work, then it means Google is actually not detecting root for Android Pay. If that's the case then I'll need further investigation what Google is actually detecting.
[Magisk] Droidphilev:
Thanks for this useful info. Is it ok to report about other apps that don't like root also? (since it's not the main purpose of the app...)
[Magisk] devilloki:
[MENTION=4470081]topjohnwu[/MENTION] excuse me. Can u help me.?
[Magisk] bobby janow:
Try Vol + plus power button for about 30 seconds to reboot the puppy?

---------- Post added at 07:44 AM ---------- Previous post was at 07:36 AM ----------

So perhaps AP is testing root access before authorizing a transaction rather than looking for something? That's interesting and then it would seem that if you have root at any level AP will fail. Unfortunately, I can't test that for this project since I'm running DP5 but the theory of disabling any root access is intriguing. If indeed that is how they're doing it.
[Magisk] Jacob_K:
Thought I'd share what I've found with android pay on my LG G4.

Flashed stock ROM, added card to android pay before magisk/root/xposed. Then flashed magic, phh's, xposed. Restored all my apps etc.

Disabling root via the toggle caused it to fail. However I realised I was modifying build.prop via changing dpi. So restored dpi to stock.

Tried again after a reboot in McDonalds, got the tick on my phone to say it was done, however card machine said it was declined by the bank.

But earlier it had been doing that on normal contactless cards, so I will try again today in another store.

If it works, is there a way to change dpi without affecting the build.prop?
[Magisk] devilloki:
i cann't understand what mean is "puppy"! did u said"boot to rec"?yes can boot to rec. after restore to stock boot ,can boot successed!
[Magisk] itechy:
Blacklist mount root? Or is it already possible via tasker?
[Magisk] WisdomWolf:
I'm assuming that there is some kind of daemon running in the background to reactivate root after the countdown. Is it possible to have the daemon check for the existence of a file and reactivate root only if it finds it? I'd think that might allow for a bit more flexibility if it's possible to structure it that way. We could then simply `touch activate.su` or similar and have the daemon remove it after activating root just before it exits.
[Magisk] MrBrady:
There seems to be a discrepancy between Android Pay actually working and SafetyNet Checker app. I'm always green in the SafetyNet app but transactions will not go through most of the time.

I've narrowed it down to either the kernel or Viper4Android since that modifies the system. I have tried with Benzo and Elemental kernel, both with no success.

The one time a transaction was successful I was in the stock kernel than came with Chroma ROM and I'm pretty sure Viper was installed as well. Just need to confirm with another transaction.
[Magisk] adrman:
I doubt it's the kernel, possibly viper, but payments still fail for me with just plain, rooted stock, no other mods. Someone posted a few pages back about having a successful transaction after deleting the su symlink in system/xbin, but that effectively removes root, so it's not a very useful short term solution.
[Magisk] TekRantGaming:
Its wired it was working the other day and there has not been an app update
[Magisk] Artim_96:
SafetyNet updates don't come as app updates, the Google play services constantly updates things like SafetyNet and detection algorithms for their verify apps feature to warn for our block known malicious apps. The only way to prevent it would be to completely freeze/uninstall them... But them nothing would work anymore.
[Magisk] TekRantGaming:
Thanks for the info never knew it was baked into play services
[Magisk] beatLeo:
Not working on Huawei Y6 scl-l03 with cm 12.1. It generates bootloop.
[Magisk] wolke7:
Hi,

on my OnePlus3 with clean flashed official CM13 (over TWRP) i've installed Magisk v6, phh's SuperUser 17, xposed installer (Material design) and Systemless Xposed from topjohnwu. If i toogle SELinux in Magisk Manager it works (SEL status changed to "Permissive". I checked 'getenforce' in a terminal, too). But if i toogle root i see the toast "Super User granted to Magisk Manager", but the toggle Button jumps immediately back and Magisk is still active. A 'mount' check in a terminal shows me, that all mounts are still on :( Any idea what's the problem?

thanks

w7
[Magisk] Seanbest:
I am running a modified nougat ROM and removed all root then flashed Magisk. I want to flash Franco Kernel r19 and was wondering what steps I need to take. TIA.
[Magisk] xCRUTCIOx:
Still no one can help with unable to detect boot image error when trying to flash magisk? Android 5.1.1 cm12.1
[Magisk] Nomelas:
So, following this example, how do I go about changing these lines in build.prop?

Change:

ro.qc.sdk.audio.fluencetype=fluence

to

#ro.qc.sdk.audio.fluencetype=fluence

Add:

persist.audio.fluence.voicerec=true

persist.audio.fluence.speaker=false

use.voice.path.for.pcm.voip=true

is it possible?
[Magisk] Seanbest:
Would uninstalling Magisk, flashing a new kernel, then flashing Magisk again work?
[Magisk] macschwag14:
Is your volume turned up more than halfway when it does this? Mine starts hissing as soon as I go from silent to audible. I'm curious if it's an Android driver issue like some experienced on older flashed versions or just the result of using a systemless version.
[Magisk] theredbaron1834:
Yeah, quite a bit. About 13/15 or so. I just turn down the master gate gain and it works for me. If I have the master gate's gain to 3.5db or lower never had an issue, but then it is too quite.

I also some times mess with viper clarity which can add the hiss as well.

O, and just thought of something. I have the EQ turned on to small speakers, which may be why it is only when loud.
[Magisk] Rhoban:
Normally, when you want to use Magisk with a custom kernel, you flash the kernel and then Magisk.
[Magisk] MrMiami81:
I'm running a AOSP nougat ROM on my Nexus 6. I rooted it the traditional way by just flashing super su 2.68. If I wanted to use magisk root method how would I go about that?
[Magisk] Rhoban:
Because you did not remove CM's root.

---------- Post added at 10:23 PM ---------- Previous post was at 10:21 PM ----------

Full unroot from within SuperSU, flash Magisk, flash phh or SuperSU from the OP, flash whatever other mod you want (Xposed or Viper4Android) and reboot.
[Magisk] MrMiami81:
Does unsu still work? Also what magisk version should I flash? I'm running a custom kernel too.
[Magisk] AnonVendetta:
Is there a reason why SELinux toggle doesn't work in Magisk Manager? I'm using the Magisk version of systemless SuperSU 2.76. If I try to toggle SELinux in Magisk, I still get "enforcing" in terminal when I type "getenforce". Sometimes the bar will turn blue then go to grey (option disabled). I also noticed that Magisk doesnt request root. Is it supposed to?

I don't want to use phh Superuser because it doesn't seem to support approving su requests during the booting phase (SuperSU does). It also doesn't seem to have to disable mount namespace separation (SuperS does). I have certain root apps that don't work properly if their su requests aren't approved during boot. I also have apps that work fine with SuperSU in system mode, but not systemless (they say I'm not rooted).

I don't use Android Pay, banking apps, etc, so I think I may be better off installing SuperSU and Xposed in system mode instead of futzing around with Magisk. But I figured I would give it a go anyway. I'm not impressed so far.
[Magisk] FahrenGrade:
When updating a custom kernel with MAGISK installed is there a need to re flash MAGISK ?
[Magisk] nyknight77:
Please fix issues with boot.img on older samsung devices. I flashed magisk on galaxy s2 i9100 and got bootloop. Luckily I was able to install odin CWM recovery and flashed the magisk uninstaller.
[Magisk] Son-j:
I'm actually at a loss on how to make this work...

My goal is to be able to play Pokemon Go on my Nexus 4 running Nitrogen OS (android 7.0) and Nvidia Shield Tablet (stock, android 6.0.1) using Magisk v6, phh supesu, and magisk manager.

I notice that every time I toggle the root switch to "unroot", I goes back to being "root" again after 2seconds. This is why the PoGo app didn't work. I also check this with the root checker.

Anyone can help pls?
[Magisk] Rls4ever12:
Try flashing unsu zip. Just Google unsu zip XDA and you will find it.

---------- Post added at 01:59 AM ---------- Previous post was at 01:57 AM ----------

I would suggest yes it couldn't hurt and if your flashing a update to kernel just add the magisk
[Magisk] Itachisasuke:
No permanent solution yet. Gotta toss our main man some beer money and be patient at this point.
[Magisk] stormPremier:
Hi guys,

I'm trying to understand how magisk play around with SafetyNet stuff ...

On the first install, after applying "magisk environment", safetyPet is OK, but whatever I do, even a simple reboot, and it completely fails, cts and basic integrity.

Any idea?

Thanks

----

EDIT: Hmmm, using magisk core only seems to be ok for SafetyNet, if I disable "core only" safety test fail again ...

I don't use any module yet, don't know what to do :/

----

EDIT2: Oukitel K6000 Plus, official Android ROM, 7.0
[Magisk] szakes1:
Google Pay doesn't work with Magisk 18.1 (18100) despite having a working SafetyNet pass on Oxygen OS Open Beta 13 on OnePlus 6.

Is there anyone here, who can tell when approximately Topjohnwu will release a new, fixed build?
[Magisk] Strephon Alkhalikoi:
When he gets around to it. It's bad form to ask for an ETA here, and besides, he's trying to figure out how to get Magisk running on Android Q.
[Magisk] BHUSHAN7988:
Deny telephone permission from Google Play service to pay from Google pay it works

I wanna make a Tasker task that does this for me any idea?
[Magisk] Didgeridoohan:
It's perfectly possible that the app is detecting something else than Magisk. More details:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

https://www.didgeridoohan.com/magisk/MagiskHideHelp

Sometime before summer 2045.

Seriously though, no. No-one can tell, and no-one even knows exactly why it's become such a hassle lately. [MENTION=4470081]topjohnwu[/MENTION] is just one guy, and he's got other priorities. S, o elseunless someone figures it out it might be a while.

Meanwhile there's a discussion going on here (with possible workarounds):

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] Faithful4real:
Please i need help magisk Root is not giving Root access
[Magisk] Faithful4real:
Magisk root is not giving root access.

Mine phone and version is 5.1
[Magisk] eliezerjk90:
Bruuhh... Maybe you need to consider to update... You're using a quite old version. Guess it has no point to ask for support for such old version. Everybody has moved on to newer version.
[Magisk] martyfender:
That does not look like a complete magisk.log. Is that all you get in the log?

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] guest4711:
Your kog contains one line only

03-17 18:01:11.578 8542 8542 W Magisk : su: request rejected (10096->0)

and does not show anything about your ROM, the version of Mmagisk and MagiskManager you use or your current setup. It does neither show wether you denied root access for apps (MM - Settings). But probably a compkete uninstall of all rooting solutions (like los-addon, superSu and Magisk) followed by flashingba clean boot image and a current magisk vould solve your problems. There are tools here on XDA to uninstall all traces of rooting solutions (afaik from osmosis, but I'm not sure and in a jiffy so cannot search). The search function should be your friend...
[Magisk] martyfender:
Osmosis tool is UnSu.zip that can be flashed in a custom recovery to remove root.
[Magisk] Wixcee:
Sadly, this doesnt worked. Everytime i try to put correct cvc, to verify nfc payment it says something went wrong, please check info and try again. It let me add the card, but doesnt let me to enable nfc payment... :(
[Magisk] fOmey:
Has anyone had any success with magisk on the S10? I just finished trying to patch stock boot.img & flash using ODIN.. magisk manager doesn't seem to detect the install.

I confirmed magisk manager was installed on internal also btw.
[Magisk] con4n007:
Can anyone help ?

Already hide magisk from setting, hide the app, safetynet check passed, still can open banking app Sakuku and some other indonesian banking app?

this what the logs looks like

03-18 13:12:11.794 704 722 I Magisk : proc_monitor: com.bca.sakuku/.view.state.StateActivityView PID=[10290] ns=[4026533900]

03-18 13:15:33.395 704 722 I Magisk : proc_monitor: com.dbs.id.pt.digitalbank/.DBID PID=[11141] ns=[4026534034]
[Magisk] SonOfTheRain:
Hello,

Yesterday my Mate9 got an update to Emui 9. Of course, Magisk has gone, but phone is still unlocked. I tried to install via patch bootloader, via Huawei Extractor i extracted RECOVERY_RAMDIS.img and patched it, installed via fastboot. Phone booted but Magisk Manager still says "Magisk is not installed".

What is the correct way (if any) to install Magisk to Mate9 with EMUI 9?

Thanks in advance
[Magisk] Didgeridoohan:
Don't think so, but [MENTION=4470081]topjohnwu[/MENTION] has recently bought a S10+ for development, so it's likely just a matter of time. Seems to be some new Samsung stuff going on that need to be overcome...

That log snippet is just telling us that MagiskHide detected the app and tried hiding from it. I tested Sakuku on my device, and with the Manager repackaged and the app on the Hide list it started without complaining. I'm using Canary build 18120 at the moment, so it might be because of the improved MagiskHide (completely rewritten from scratch actually), or it's possible that there's something else about your setup that is triggering the apps.

More:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Have you read the installation instructions?

https://topjohnwu.github.io/Magisk/install.html#emui-9

Particularly the part about booting via recovery...
[Magisk] el_muerte:
Having Problems with hiding root for German PayBackPay app.

What I did:

- Adding app to magisk hide

- hiding magisk manager

- disabled USB debugging

- disabled developer options

- clearing app cache

- using props config module to change fingerprint and also enabled device sumulation (which works fine - SafetyNet ist ok / CTS profile ok)

- rebooted device

- added some urls to adaway blacklist (taken from thread "santander bank app detects root")

Nothing helped - PayBack pay app still detects root....

Any advice?
[Magisk] fOmey:
I thought as much, Samsung sure do love over complicating things.. cheers
[Magisk] jonners59:
Sorry, all I have and it didn't work for me either. Guess we'll have to all wait patiently for the developer to come up with a fix or someone else.
[Magisk] SonOfTheRain:
I followed second point. I extracted recovery_ramdis and tried to patch with latest stable 18.01. One odd thing that Magisk while patching said "patching ramdisk" not recovery_ramdisk, if it matters, later I just flashed using fastboot fastboot flash recovery_ramdisk patched_boot.img

As I said Magisk still is not installed.
[Magisk] kotuamoalt:
What version of magisk are you using?
[Magisk] Chamelleon:
18.1 but already fixed my problem by downgrading Google Play Services.
[Magisk] martyfender:
Are you doing this everytime you boot into Android after the Magisk install?
[Magisk] kotuamoalt:
Untill a newer stable version is released, 17.3 is the one to use., IMO. Or use one of the canary builds. Personally, I just reverted to 17.3 and it works fine.

Keeping in mind that magisk manager 7 will not work with anything below magisk 18.0

---------- Post added at 01:48 PM ---------- Previous post was at 01:41 PM ----------

Yes. His name is "topjohnwu", and he will release the build when he gets around to it. I honestly cannot believe you asked that question.

---------- Post added at 02:00 PM ---------- Previous post was at 01:48 PM ----------

Yes. His name is "topjohnwu", and he will release the build when he gets around to it. I honestly cannot believe you asked that question.

---------- Post added at 02:07 PM ---------- Previous post was at 02:00 PM ----------

Yeah. You should be able to just flash it in TWRP and go. I am currently using 17.3 until such time that a stable version is released.