Database Info

Bypass SafetyNet and V4A DRIVER

First of all i want to know how can i Stay encrypted and Install magisk 13.3 ?
currently i'm using SuperSU 2.82 SR3,My data is decrypted.
Rom:C185B184
Google Play: Uncertified
Last night,i've tried Suhide,and i couldnt pass ctsProfile...
and also Suhide has some bugs,like u cant uninstall any app when its activated and u cant Deactivate Suhide,unless u do full unroot.
And Also how can install Viper4Android's Driver Using SuperSU ?

Flash this for Magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Or 13.5: https://mega.nz/#!V8EXRRoB!Dlv4gxa7smUhnacjVzHRVemLtZtKKTBfdQ5z0NhCQwY
Though you say you are decrypted now, flashing 13.3 or 13.5 will re-encrypt your /data.
If you want to stay decrypted, flash official 13.3 or 13.5.
Flash back your stock B184 boot image first.
As for SafetyNet, the build you're using is a beta, and pretty recent so it may not be approved by Google (and since beta it might not be approved later either). The even more recent build for your model is B186, and that's definitely not approved yet (released 14th of August).
You should be able to install V4A if you set selinux for permissive. Or you can flash this: https://mega.nz/#!J1FyiSLT!WQVsJ3DWNq3l-HDKcg06ISB4J5COpdabR8Q36A_R_LE
Or if you switch to Magisk there's a V4A module for it in Magisk Manager - Downloads.

i've installed B186 and its certified.
so can tell me how to install magisk on a fresh rom ? 0- 100
cause i've tried this before and i've faced bootloop !

Safetynet Problem
So I've figured it out until u don't unlock bootloader, u can pass safetynet without any problems.
Once I've unlocked my bootloader, I've got CTS Profile error...
Plus I'll get random FC since upgraded to B184 using Hwota method!
I'm on B186 right now and I've got FC again in chrome during this reply :laugh:

Update!
Help me @ante0

ezraiil1 said:
So I've figured it out until u don't unlock bootloader, u can pass safetynet without any problems.
Once I've unlocked my bootloader, I've got CTS Profile error...
Plus I'll get random FC since upgraded to B184 using Hwota method!
I'm on B186 right now and I've got FC again in chrome during this reply :laugh:
Click to expand...
Click to collapse
Did it pass CTS and basic on B186 before flashing magisk?
The FC, does apps close suddenly without warning? If so I think it's something else because it happens to me too on C432 B194. Same for people on c636 B188.
Could be the phone manager that's too strict.

ante0 said:
Did it pass CTS and basic on B186 before flashing magisk?
The FC, does apps close suddenly without warning? If so I think it's something else because it happens to me too on C432 B194. Same for people on c636 B188.
Could be the phone manager that's too strict.
Click to expand...
Click to collapse
Yes,I've Tried it before unlocking bootloader and it passed successfully ,and google play Status was certified too.
before installing magisk,right after i unlockd bootloader!
and then i install magisk and tried again,then both basic integrity and CTS profile failed.
Yes,Sometimes when u r using apps,they suddenly close and jump into app drawer,and when i open them again they start over.
(like chrome,Clash royale,Last Day on earth,Instagram...)

ezraiil1 said:
Yes,I've Tried it before unlocking bootloader and it passed successfully ,and google play Status was certified too.
before installing magisk,right after i unlockd bootloader!
and then i install magisk and tried again,then both basic integrity and CTS profile failed.
Yes,Sometimes when u r using apps,they suddenly close and jump into app drawer,and when i open them again they start over.
(like chrome,Clash royale,Last Day on earth,Instagram...)
Click to expand...
Click to collapse
Is magisk hide enabled in Magisk Manager? If not, check log in Manager to see if it tried to enable. Else try enabling USB debugging and disable then enable Magisk hide.
If it enables after that you're in the same boat as the rest of us. Mine actually worked flawlessly for a week or so, then I had to keep enabling USB debugging to get it running....
Not sure of it's intentional by Huawei that USB debugging gets disabled. Same goes for adb, have to enable USB debugging after each reboot to get it running. I guess a Tasker script could be made to enable it, and disable/enable magiskhide at boot.

SafetyNet check suddenly fails with Magisk

I installed the DP3 build a month ago or so along with Magisk so I could use Android Pay. Android Pay was working fine for a couple weeks and then about a week ago, between breakfast and lunch, Android Pay stopped working. I did a SafetyNet check with Magisk and it failed. Today I tried reflashing DP3 (without a full wipe) and installed Magisk (via TWRP) and SafetyNet is still failing. Short of reflashing DP3 with a full wipe, what else can I try to get SafetyNet check to pass?

greenmaze said:
I installed the DP3 build a month ago or so along with Magisk so I could use Android Pay. Android Pay was working fine for a couple weeks and then about a week ago, between breakfast and lunch, Android Pay stopped working. I did a SafetyNet check with Magisk and it failed. Today I tried reflashing DP3 (without a full wipe) and installed Magisk (via TWRP) and SafetyNet is still failing. Short of reflashing DP3 with a full wipe, what else can I try to get SafetyNet check to pass?
Click to expand...
Click to collapse
Although Android Pay may work on DP3 Google make it clear that it fails CTS which means it will always fail Safety Test. So Android Pay is not guaranteed.
https://developer.android.com/preview/release-notes
Android P beta devices*aren't*Compatibility Test Suite (CTS)approved, but they have passed preliminary testing and provide the same set of APIs for developers. Apps that depend on CTS-approved builds might not work normally on supported devices.
Sent from my Pixel 2 XL using Tapatalk

If I had this issue, I would flash a custom kernel. I'm currently on the latest Sultan's and haven't had any issues with safetynet whatsoever.

I had this issue briefly. Clear data for Google Play Services and Google Play Store, then reboot. It cleared it right up for me.

DuckRuckus said:
If I had this issue, I would flash a custom kernel. I'm currently on the latest Sultan's and haven't had any issues with safetynet whatsoever.
Click to expand...
Click to collapse
I installed this Kernel after a complete wipe and resintall of DP3 and still no luck.

lightningdude said:
I had this issue briefly. Clear data for Google Play Services and Google Play Store, then reboot. It cleared it right up for me.
Click to expand...
Click to collapse
I tried this. I even reinstalled DP3 with a full wipe and still no luck.

Try toggle magisk hide and exit app. Usually a reboot fixes it also.

Google Pay with rooted Phone

Hi.
I have Pixel 2 on December patch. Stock kernel, and boot loader, but rooted with Magisk 18.1 installed. Yesterday my google pay stopped working. Jut kept getting error message that can't pay with this device, or something like that. I removed default card, and re-added. Now when I try to set it up to pay in store it keeps saying that it can't because phone is rooted, or modified. I haven't installed any updates, so not sure what changed.
Anyway, how can I get around this? Ran SafetyNet Check, but it didn't help.
Thanks

UDPoster said:
Hi.
I have Pixel 2 on December patch. Stock kernel, and boot loader, but rooted with Magisk 18.1 installed. Yesterday my google pay stopped working. Jut kept getting error message that can't pay with this device, or something like that. I removed default card, and re-added. Now when I try to set it up to pay in store it keeps saying that it can't because phone is rooted, or modified. I haven't installed any updates, so not sure what changed.
Anyway, how can I get around this? Ran SafetyNet Check, but it didn't help.
Thanks
Click to expand...
Click to collapse
+1 **bump** same thing happened to me about a week ago on in store payments. Was on November Patch....and 18.1 Magisk. Uninstalled Magisk....updated to March patch....reinstalled Magisk and Magisk manager....repackaged Magisk to hide it and hid google pay in Magisk Hide. I also pass Safety Net check so I am not sure why it isn't working
Everything was working fine and had been for well over a year until last week.
Just got off chatting with Google Pay support....apparently the bootloader unlock hide is no longer working and it is being detected somehow and not being hidden by Magisk. I guess wait on an update!
---------- Post added at 04:42 PM ---------- Previous post was at 04:15 PM ----------
bakemcbride21 said:
+1 **bump** same thing happened to me about a week ago on in store payments. Was on November Patch....and 18.1 Magisk. Uninstalled Magisk....updated to March patch....reinstalled Magisk and Magisk manager....repackaged Magisk to hide it and hid google pay in Magisk Hide. I also pass Safety Net check so I am not sure why it isn't working
Everything was working fine and had been for well over a year until last week.
Just got off chatting with Google Pay support....apparently the bootloader unlock hide is no longer working and it is being detected somehow and not being hidden by Magisk. I guess wait on an update!
Click to expand...
Click to collapse
We are not alone.....looks like the latest Google Play services is the culprit and is a little sneakier than before. There is a workaround posted in the thread:
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
I'll just wait for the Magisk Update.

I just updated my phone from 8.1 to 9.0 (edit: March security patch) and installed Magisk 18.1. Safetynet passes and I checked off every google-related app in Magisk Hide, but I still can not add my card because Google Pay is detecting root. My banking app (HSBC) is also able to detect root, but all that does it show a warning. Hoping the next Magisk version has a fix.
Edit: Just tried the fix linked above and it did not work.

jrbmed08 said:
I just updated my phone from 8.1 to 9.0 (edit: March security patch) and installed Magisk 18.1. Safetynet passes and I checked off every google-related app in Magisk Hide, but I still can not add my card because Google Pay is detecting root. My banking app (HSBC) is also able to detect root, but all that does it show a warning. Hoping the next Magisk version has a fix.
Edit: Just tried the fix linked above and it did not work.
Click to expand...
Click to collapse
It did work for me. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app

jasonbiggs said:
It did work for me. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah I don't know why since I followed all the instructions, but I'll just wait for the next Magisk update.

Well... Even though I had background data services disabled it still updated libraries to 15. Now it stopped working again [emoji50] How to stop it from updating?
Sent from my [device_name] using XDA-Developers Legacy app

Unsupported Magisk Version

Not sure how I got here.
Yesterday, went to pay at a Grocery Story with Google Pay, got a message that said "You can no longer pay in stores with Google Pay." Magisk seemed okay, seemed like I was passing SafetyNet (tried two different apps, including Magisk's built-in checker). No big deal, paid the old-fashioned way.
Today, I decided since Magisk or Google Pay was going to be that way, I might as well update EMUI—I've put it off for a good six months or so, because everything was working fine. Now that it wasn't, why not do the whole shebang?
Update went smoothly. Now on B376 (I think).
Updated Magisk. Patched boot.img, all that.
Now, however, I'm getting this screen, and I think somewhere I must have flashed the wrong Magisk. I'm still rooted (Adaway works), but MagiskManager won't get past this screen.
Any ideas on how to do this properly so Magisk and MagiskManager are on the same page?

Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]

Haluter said:
Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]
Click to expand...
Click to collapse
Thanks for this.
Just downloaded Magisk 18.1.zip from Github. It's currently on my computer.
My question is... how do I install it at this point? I don't have TWRP on my Mate 9, since it's so finicky to use. Yesterday, after I updated EMUI, I installed Magisk Manager, and had it sort of install/do its thing. I assume it downloaded its own Magisk, though which version, I have no idea. I used the custom channel found here.
However, now that I'm retracing my steps, I just noticed the verbiage in @Wirmpolter's guide, that says
Latest Magisk Manager and magisk work now so no longer need to setup and flash the specific version found in the original post from topjhnwu.
Click to expand...
Click to collapse
So... no need to use the custom channel URL from Magisk Manager. Got it.
Any advice on how to proceed? Currently... I have Magisk and Magisk Manager installed. Magisk Manager is 7.0, but Magisk itself, I suspect, is not 18+.
If I had to lay it out, I might try:
Uninstall Magisk (uninstall.zip, or whatever it's called)
Reinstall Magisk Manager 7.0
Use @Wirmpolter's instructions, pulling, patching, and re-pushing boot image (again!) in fastboot.
Is there an easier way to do this? Just curious.
EDIT: Another quick question to the big bad XDA world out there: do I flash the Magisk uninstall zip in fastboot, as well?

So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?

daina said:
So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?
Click to expand...
Click to collapse
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).

ante0 said:
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).
Click to expand...
Click to collapse
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...

daina said:
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/showpost.php?p=79029481&postcount=9
Its a temporary fix as well... But beats calling the bank I guess

Hi Daina,
after a short-lived success I ended with the same problems the next day. Afterwards I tried all suggestions from various forums but nothing worked.
After a short period of frustration I decided for a radical solution and installed a new OS on my HTC U11. (Lineage unofficial)
And... surprise! GPay works without any flaws.

how can i correctly install magisk in the new Q beta?

going insane with this. finally got the new Q beta booting. when i install magisk after booting i get immediate system ui crashes and i'm not sure why. normally i would try clearing data but it seems like you can't do this in Q twrp? not sure what the best thing to do is. any ideas?

Are you using 19.3 or 19.4?

coach0512 said:
Are you using 19.3 or 19.4?
Click to expand...
Click to collapse
figured it out, needed 19.4 and to uninstall swift. doesn't seem like swift installer works and if it gets launched everything gets screwed up.
ok google and youtube vanced not working either. damn