yashsingh1/xdaforums huggingface dataset:
[Magisk] Oswald Boelcke:
In case you don't know there's a dedicated [Discussion] PokeMon Go Magisk Discussion Thread thread.
[Magisk] dedo1996:
Hi everyone,

I got a Xiaomi Mi8 SE ("sirius") (MIUI rom) on which I cannot install any Magisk newer than 16.7 version or it gets stuck into bootloop.

So I cannot even see every magisk module available...

Anyone knows a solution?

Thanks
[Magisk] nowster:
Canary 18108 (660e0dc0) seems to be more stable than 18.1 so far. (It's only been 24 hours.)

Google Pay might also be affected by the buggy Google app update (9.27.3.21.arm64) which removes Podcasts from Android Auto. I rolled Google back to 9.23.3.21.arm64.
[Magisk] ryandanger:
Canary worked for me yesterday however today it's stopped working with GPay. Uninstalled Magisk and Google Pay, reinstalled Magisk and GPay, hid gpay in magisk and not working, even though that worked yesterday.
[Magisk] fasho:
I think something wrong with new update the Google play take along time to open after close recent app also speed test and many other app this issue only in android 8 my phone galaxy s8
[Magisk] bigknowz:
I'm having an issue with BlackBerry. Work functions properly, but BB Access and BB Appstore detect root. Canary will resolve? Anyone having the same problem? Thanks in advance.

P2XL Magisk 18.1 and DirtyUnicorns
[Magisk] GTMoraes:
Hey! I'm currently on a Pocophone F1, running the latest xiaomi.eu ROM (9.2.21).

For some reason, the root confirmation window just stopped showing up. Old apps that I had already conceded root works fine (although without the root access toast), but newer apps just hang until they say they've been denied. The built in Magisk log just shows "su: request rejected"

In short, su and root works, but the manager doesn't seem to be willing to show the confirmation dialog.

In the past I had a little issue with the MIUI energy management, but since I've been completely disabling the battery optimization for Magisk. I can't really pinpoint when this issue began.

I've already tried restarting the phone, reinstalling the app, unhiding the Manager, hiding the manager, disabling or enabling the fingerprint confirmation etc

Any clues? What can I do to help fix this?
[Magisk] paarnoutse:
After a fresh install of Magisk, the Magisk Manager app can be hided after your first system boot via MM Settings (rename to random package name). This means that during the first boot after a fresh install, Magisk Manager will not yet be hided.

Unfortunately, at my device this means that root will immediately be detected at next system boot by various apps for my company's email and internet/intranet access. As a result, my device will immediately be blocked by my company...

Theoretically this could be prevented by temporary freezing such apps before an uninstall/reïnstall of Magisk (so they will not start at first boot while Magisk Manager isn't yet hided). However, freezing an app will also remove its Device Administrator rights. Admin rights can only be added again after unfreezing, but an unfreeze will also always automatically start the app. Result: Root detected, because it will recognize that it hasn't Admin rights anymore (and obviously they know that this can only be removed when your device is rooted).

Question for preventing such issues:

Is there any possibility to already hide Magisk Manager (rename from 'Magisk Manager' to 'Manager', and implement a random package name) immediately after the fresh install of Magisk while still in TWRP (so before your first system boot after a fresh install of Magisk)?

A flashable Magisk module that performs this action once would be interesting, but never seen it. Possibly an interesting challenge for someone? ;)

Or, as an alternate bypass:

Are there somewhere Magisk install-zips available that can be used to install Magisk Manager in hided implementation (so using a random package name, and renamed from 'Magisk Manager' to 'Manager')?

Nb.

In my opinion the latter solution would be a good idea for implementing as the standard behavior for a fresh install of Magisk. Although hiding Magisk Manager is not a requirement for anybody, I don't see why it couldn't be implemented as the standard/default behavior.
[Magisk] kathynw:
Hi thanks for your response. I reinstalled my stock rom (android 5.0.1), no supersu. Then I was able to load TWRP and install the latest Magisk ZIP (18100) and then reboot. Magisk manager still said uninstalled so I patched the stock boot.img file correctly using the maanger this time and the phone rebooted with no boot loop(acknowledging in yellow that the warranty had been voided so it was rooted).

So now that everything was completed correctly both ways, MAGISK manager is still saying uninstalled.!?!? Does it simply not work on this phone or is there a step I missed?
[Magisk] Oswald Boelcke:
"Latest" version is v18.1
[Magisk] beatschubser:
Is the Magisk uninstaller mandatory, or did you do it just to be safe? Have you already tested paying in a store after the update?
[Magisk] ang3l:
Thanks for the replies guys!

I use MagiskHide for Gpay and Gplay, and I'm also hiding the Magisk Manager, but Gpay still won't work unfortunately.

The device indeed looked as Not Certified, but clearing cache and data fixed it after a reboot. Gpay still doesn't work.

In the meantime I see a few more reports coming in on this issue, so I guess I'll stand by to see if someone comes up with a solution/workaround :)
[Magisk] martyfender:
Yes, there other users in the Canary development thread with the same issue. I am at a bit of a handicap, since I have never used it, nor have a need for it on my tablets. Has google made changes to it to detect rooted devices?

On my devices, I see the ability to activate it under settings, security, device administrators. I am hesitant to activate it, since I don't need it and don't know how it would affect my devices?
[Magisk] ecko2010:
looking for module Do (disable auto-sleep while in selected apps)
[Magisk] raptorneutron:
+1 here, i'm pretty desperate because I want to restore a titanium backup. Any solutions yet?
[Magisk] Digital God:
Google pay stopped working today. Even after update to canary channel. SafetyNet check passed.
[Magisk] linuxsaravanan:
After some days it's official version how to solve this
[Magisk] nowster:
My suspicion for the recent GPay failure is on the newer Google (search) app (9.27.3.21, dated 18 Feb 2019), which broke other stuff. Roll it back to a previous version, clear its data and GPay's.
[Magisk] Coumodo:
uninstaller is highly recommended, but I guess not necessary.

paying works without issues
[Magisk] paffo:
Sorry Coumodo, but "highly recommended" and "not necessary" do not fit together and by using word "gues" (or "guess" more probably) you mark your statement irrelevant.

Did you had problem with Google Pay and fixed this by installing Canary build?

Please provide more details, which version exactly helped.
[Magisk] ang3l:
I'm actually on 9.31.5.21 (arm64) atm. How would you roll back? Find an .apk, manually install, and disable updates in Gplay?
[Magisk] beatschubser:
To add some more information: I called PayPal yesterday to check if the issue is related to Google Pay or PayPal. They told me Google is aware of the issue and working on a fix. Of course this could be made up, but who knows.

[MENTION=3636052]Coumodo[/MENTION] It would be great if you could answer paffo's questions and let us know which Google (not pay) app version you are using, see nowster's post.

And do you guys know if the certified Play Store is necessary for Google Pay?
[Magisk] nowster:
That's exactly what I did. I went back to 9.23.3.

https://www.apkmirror.com/apk/google-inc/google-search/google-search-9-23-3-release/
[Magisk] Leejhay1714:
My device is oneplus 6 running pixel experience rom, rom boot successfully, but magisk is not installed, tried to download and istall it again on twrp but still got this error
[Magisk] garylawwd:
Is magisk manager installed to internal storage? Make sure it is
[Magisk] Leejhay1714:
Yeah, oneplus has internal storage only
[Magisk] luiskabes:
Root detection?

I'm a driver of an online application like UBER, but here I use Grab Driver. I have rooted my cellphone, my device now is the Xiaomi Mi A1 with a custom Android 8.1 Resurection Remix, this application can detect root even though magiskhide is working and safetynet has already passed the check, especially in version 5.59.0, before that in version 5.58 it still not detected, can you help me know where he can detect that my cellphone is rooted

This is an app : play.google.com/store/apps/details?id=com.grabtaxi.driver2

Thanks before
[Magisk] ang3l:
So I uninstalled updates, cleared cache/data, installed this .apk, disabled updates in Gplay, cleared cache/data in Gpay, rebooted, and unfortunately this doesn't solve the Gpay issue for me.

For the record, I've got Magisk Hide active for Gplay, Gpay, and Gsearch.
[Magisk] elreydenj:
I do not believe this has anything to do with Magisk directly. Whatever custom kernels & or Magisk were doing to hide the fact that the device has an unlocked bootloader is no longer working properly. Or, there is in fact an issue on Google's end and we will see it begin working once they fix it.
[Magisk] Digital God:
In my case, everything worked in the morning, at lunch I got a message when I tried to pay.
[Magisk] fd.svensson:
Sorry if you already know about this, I'm a newby and don't understand better.

I found this on Google help

Edit / Don't use Gpay myself.
[Magisk] beatschubser:
I was able to use Google Pay in a store again.

What I did since in store-payment broke:

- Updated Magisk to v.18.2-5764f0c8 without uninstalling 18.1 first

- Re-packaged Magisk with random package name

That is all.

More information

- Device: Moto Z Play

- Location: Germany

- Play Store status: Not certified

- Google Pay is added to Magisk Hide, nothing else

- Google app-version is 9.27.3.21
[Magisk] SharjilAbdullah:
Same issue

I am also having the same issue .. I have already installed an then uninstalled it.. and also i have magisk manager on internal storage
[Magisk] elreydenj:
Thanks for the info. Works again for me as well. I didn't change a thing. Was an issue on Google's end. it appears.
[Magisk] SharjilAbdullah:
Hi all..

I am unable to install the Magisk after i have flashed the safety net on my OOS...i have tried all the options i have uninstalled and reflashed the module again..but it didn't worked for me..i have also checked that the Magisk manager is installed on my internal memory.

Any suggestions on how to resolve this.

Thanks in advance.
[Magisk] fluxus_pt:
Try to install v18.0 from official github. that worked for me in latest LOS15.1.

cheers,
[Magisk] Solid_Eye:
since one week I can't access google pay or my bank's apps, hope 18.2 is near :(
[Magisk] ryandanger:
Wish this worked on my Pixel 3 XL :(
[Magisk] Coumodo:
I'm just a stupid user sharing the experiance I've got trying to fix my own issue with gpay.

All additional information needed for canary Magisk is given in the GitHub directory that I've linked.

I also shared the detailed way I falshed it.

"I don't know" wouldn't help either - but according to my experiance with Android the clean way is always to update just a clean/wiped devices. In most cases a dirty flash also don't cause issues, but you'll can never be sure...

so clam down and read the manual :p

And just by the way: vaccinatuons are highly recommend, but I guess there are some folks thinking the are not necessary, right?

---------- Post added at 07:11 AM ---------- Previous post was at 06:43 AM ----------

I'm on Google app 9.31.5.21. But I don't know what that has to do with app specific root detection?
[Magisk] Har0sud3:
Hi, I'm using OnePlus 6. When I update OOS to OpenBeta 13 from OpenBeta 12, I disabled all modules. After enabling any modules and rebooting, my device instantly reboot into recovery. recovery log screen says Rescue Party. Can't update phone without removing modules?

I'm sorry for my bad English.
[Magisk] beatschubser:
Me neither, I just mentioned it because someone wrote that downgrading the Google app fixed Google Pay for him. Which doesn't seem to be correct.

I guess it really was a backend-issue after all and the only solution was to be patient.
[Magisk] paffo:
It can be a good track. Today I still see Google version 9.27.3.21.arm64 on Google Play store, so your version is not available in Poland.

[MENTION=5711694]beatschubser[/MENTION] Can you try to clear all data in "Google" and "Google Pay" and clear in TWRP "Cache"?

Maybe its good to clear data on Google Play store as well...

I am doing the same right now, but have older version of Google.
[Magisk] beatschubser:
I don't wanna make any changes right now since it's working fine for me, hope you understand :)
[Magisk] mad jebon:
how to fix this,,cts profile fail,,when reboot its okay and a few minutes this problem come again
[Magisk] beatschubser:
... and it's broken again. Guess I'll just use my regular credit card until Google gets its **** together.
[Magisk] nowster:
And for me too. Worked yesterday. The Google (search) app must be a red herring.
[Magisk] kleest:
According to Google's help pages, it is necessary.

Regarding the GPay issue:

GPay transaction denied in-store, adding a new card is also prevented due to "rooted or altered in some other way". Play store shows "Play Protect certified" and SafetyNet check is successful (both ctsProfile and basicIntegrity).

Now, the interesting thing is, that Google's help pages covering issues when using GPay in stores show a personalized information for troubleshooting when signed in using your Google Account, regardless of the device you are opening that page. For me, it says "Google Pay can't be used on your device. Check to make sure you meet the device requirements for setting up the app.".
[Magisk] riyosakura:
I still detected as root in com.telkom.mwallet (LinkAja) app even though i've already hide root for it.

Is there maybe anything i can do to make magisk hide work properly in this app?

Such as log or anything if it necessary?

Other apps are working properly.

Edit :

After Repackaging magisk, apps work properly. Thanks btw.
[Magisk] beatschubser:
For me it says "We don't have enough info about your account at the moment.".

What I can definitely say from my own experience is that a certified Play Store is not necessary for Google Pay to work. Maybe the PayPal guy I talked to was right after all and Google is currently trying to resolve some issues.
[Magisk] PWn3R:
[MENTION=5711694]beatschubser[/MENTION] are you saying you repackaged the app, or you repackaged the magisk installer? I have the same problem, both pieces of SafetyNet pass, but GPay doesn't let me add a card.

Edit: content gateway at work was hosed <read web spying server> and they rebooted and posted all three messages that timed out.
[Magisk] vladone97:
Non-developer here asking a potentially stupid question. You have been warned.

So, I noticed that my phone's free storage seemed lower than usual. DiskUsage showed about 4 GB of "System Data". I find factory resetting to be a huge pain because I have a few apps that are really hard to back up and restore (such as keepsafe), so I decided to look around and try to find the culprit. Turns out, there's a file in /data/adb/ called "magisk_debug.log" that takes up 1.4 GB and I'm not sure if it's safe to delete because, on the one hand, it's a log, but on the other hand, as I stated at the beginning of the post, I'm not a developer, which means there are a lot of things I don't know about Android's file system, plus I sometimes tend to do stupid things with my phone that cause me a lot of trouble. So, can I delete it or should I leave it be?

I'm using a Galaxy S8 with Android 7.0 if that's relevant for anything
[Magisk] Damian93mad:
hello people, sorry for the inconvenience, someone would help giving me a tutorial of how to add lines to build.prop? since in oreo with magisk normally (editing with root explored or another app) can not,

I have a motorcycle z play, with oreo 8.0.0 magisk and twrp latest version of both

Pd:i got modulo magiskhide props confi and app terminar installed
[Magisk] jcmm11:
You can delete it. What version of Magisk are you currently running? What's the date on that log file?
[Magisk] jenslody:
With MagiskHidePropsConfig you can add custom props (or change existing props) without editing build.prop .

In a terminal type "su", wait for the popup to grant root rights, do it and type "props", wait some time and open the "add/edit custom props" menu and follow the instructions.

In most cases it's enough.
[Magisk] Didgeridoohan:
You've already got the answer on how to set prop values with the module. But if you have a lot of props you want to set, using the terminal ui can be a bit tedious. In that case it's much better to use the configuration file (download here). Fill in the variable for custom props (see the instructions in the file for examples), place the file in /cache or /data and reboot.
[Magisk] Damian93mad:
Tanks [MENTION=4667597]Didgeridoohan[/MENTION] and [MENTION=8340552]jenslody[/MENTION] I was finally able to do it thanks to you

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

Tanks [MENTION=4667597]Didgeridoohan[/MENTION] and [MENTION=8340552]jenslody[/MENTION] I was finally able to do it thanks to you
[Magisk] vladone97:
I have Magisk 18.0. I don't know the date in the log because it takes forever to load if I try to open it. But I checked the file's properties and it says it was last modified on 08.07.2018
[Magisk] jcmm11:
The modification date is what I meant. It's as I suspected - it's old. 18.0 shouldn't be creating that anymore. (By the way, 18.1 is newest)
[Magisk] iMystic:
Is anyone having trouble with snapchat locking their accounts? This is mostly happening to people running magisk 18.1 or 18
[Magisk] MetalIris:
I know quite a few people having this issue, me included. Just got to sit it out until a fix is released I guess
[Magisk] iMystic:
I'm glad to hear that others are having this issue. I know some other people that are also having this issue are posting on XDA but I felt that for something as big as magisk, there would be more people talking about it when there is barely anyone. I thought maybe it was only affecting people with certain apps they had installed on their devices but I guess not. If you don't mind, I wish to ask a couple questions. Do you know if it's only magisk causing these issues or if it was apps installed on their system? And while I did say it was affecting magisk 18.0 users, I haven't used this version of magisk myself but I have heard few people saying they were banned for using that version too. Do you know if the problem is affecting only 18.1 users or both 18.1 and 18.0? And if the cause is really only magisk, are there any people that are using these versions without any issues? If that is true, I wonder why some people don't have issues with these versions. But it would make sense why there have been very few people making posts on their accounts getting locked.
[Magisk] Didgeridoohan:
[MENTION=8696710]iMystic[/MENTION] Both Magisk v18.0 and v18.1 have a bug where MagiskHide will sometimes fail, for some users (far from all).

MagiskHide has now been rewritten from scratch, hopefully making it more stable, but this is currently only available in the Canary builds.
[Magisk] nowster:
So, GPay failed at lunchtime on Thursday. I wiped its data then uninstalled all updates so it was identifying as "Android Pay". It worked in that configuration on Thursday evening. No reboot. No change to Magisk. I didn't even need to re-enrol any cards.

:confused:
[Magisk] iMystic:
I'm glad to hear that. I was just wondering if this matters for someone that keeps magiskhide on in the settings, but doesn't enable magiskhide for Snapchat. The reason I ask this is because I am not sure if a certain app is triggering the ban for me or if it is only magisk. I have reverted magisk to 17.3 now to see if it is fine. I'm still a bit curious but do you know why some people are affected and others are not?
[Magisk] Didgeridoohan:
No idea whatsoever...
[Magisk] cyb0y:
Excellent job. It works! Thank you
[Magisk] royhanks3:
You are very lucky. I've done the same thing, and I still can't get Google pay to work. This is very weird
[Magisk] Absam:
I installed magisk for the first time but after flashing the zip (didn't wipe cache /davilk cache) i rebooted my phone and then got apps unfortunately stopped message.i don't know what to do I'm basically a noob here , i need help pls.

I'm using galaxy s4 with stock rom 5.0.2
[Magisk] sisqoboy:
Google pay chat service said my device is rooted.

Have the latest magisk and hide the g apps. Hopfully we will, have solution… thanks god banking apps are working…
[Magisk] Snearde:
Hi,

Just noticed this yesterday. G Pay says i'm rooted. I tried Magisk Canary builds, wiping g pay data, re-adding bank card, etc. : nothing worked. I'm glad to hear that I'm not the only one ! :)

Hope a fix will be found
[Magisk] mdxdave:
Same problem with Google Pay and other apps like Payback or banking apps.

I think Google play services got an update and breaks Magisk Hide.
[Magisk] rogeriskira:
I can also agree that with Magisk 18.1 with Magisk hide, hiding Gpay it still doesn't work. I was able to use it before but now I can't use it to pay in stores. (No change in modules).
[Magisk] takur69:
please see what I marked why the partition capacity was zero after I installed the dnscrypt module and I used magisk v18.1 :)
[Magisk] Hopie:
Now i'm back on Viper10 5.11.0 Nougat Rom.

I can't update to 18.1. All apps are closed.. Rom rebooted..

Anyone a idea or must stay at 17.1
[Magisk] Twml:
EDIT: Magisk Canary 18.2 (18112) fixed it for me. GPay working so seems topjohnwu has a fix in the works...

Disclaimer: Canary is developer focused builds looking for testing and latest features it may not be stable or work correctly on your device. Stay on stable if you can live without GPay for now.

Same here.

My OnePlus 6 is no longer working on Google pay. I'm on magisk 18.1 (18100) with magisk hide enabled. Running Android 9.0 OOS 9.0.4. when I "setup contactless" and put my CVC in it says my device is rooted and won't work in shops.

It was working on OOS 9.0.2. not sure if that or a Pay app update did it.
[Magisk] PuffDaddy_d:
I use Google Pay every morning for breakfast. I did not update my GPay or Magisk but suddenly lost the ability to use GPay Friday morning. My wife's phone is not rooted and her GPay works fine.

Hoping something solves our problem because I hate paying the old fashioned way ?
[Magisk] RandomPooka:
That could very easily be something with the background google service framework changing. You don't need to have updated the Google Pay app for it to have updated the services automagically in the background.
[Magisk] royhanks3:
Same here with me. I hate actually having to take my debit card out now lol. I hope [MENTION=4470081]topjohnwu[/MENTION] can figure this out for us
[Magisk] gregwee:
I'm on OP6T, running 9.0.7.

Suddenly had the GPay not working issue like everyone here. It was working a few days ago, but suddenly GPay detects root.. Didn't change or update anything...

I then went to Magisk to check, and realised there is an update to Magisk Manager to 18.5, so decided to install the update to see if it worked, but now, it seems I installing Magisk Manager 18.5 doesn't stick. After downloading the update and installing, I click on "Open" to go to the app, and it's hanging in the screen as attached. If I reboot the phone or close Magisk at this point, it goes back to Magisk Manager 18.0 like the screenshot attached.

How do I update the Magisk Manager to 18.5?
[Magisk] martyfender:
You can't.

Even in the Canary channel, there is not yet a v18.5. I believe v18.2 is the latest Canary build.
[Magisk] gregwee:
I'm referring to Magisk Manager 18.5.. Not Magisk 18.5..

See the attached screen shots in my above post...