Related
Hi, All!
Are there any custom ROMs that have Android Pay working? I don't necessarily need root access; however, wouldn't mind having it with ability to turn it off.
Thanks!
PashaF said:
Hi, All!
Are there any custom ROMs that have Android Pay working? I don't necessarily need root access; however, wouldn't mind having it with ability to turn it off.
Thanks!
Click to expand...
Click to collapse
Lineage OS works fine. Rooted with magisk so I pass safetynet.
I was flashing the official Lineage OS with Magisk v11.1 . i was install the MagiskManager and the phh superuser also. However if i check my device status on MagiskManager the SafetyNet does not pass. It just looping and looping... Iam having MultiROM and my Internal ROM is OOS4.0.2 and Magisk works well, it giving SafetyNet pass.
So why does not work with official LineageOS??
Also was trying different LOS ROMs not just the official but none of them working.
Maybe you need to remove the unlocked bootloader notification before the phone boots.
Someone i read a post and this solved his prob.
Maybe try that. The process to do that in guides section
Navi44 said:
Maybe you need to remove the unlocked bootloader notification before the phone boots.
Someone i read a post and this solved his prob.
Maybe try that. The process to do that in guides section
Click to expand...
Click to collapse
Thanks.
However i was checking the guide section but have not find the tutorial about removing the unlocked bootloader notification. Only the dm-verity notification removal i have found what i have got already.
A link would be appreciated :good::victory:
Hi guys how I pass the safetynet?
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
tyler19820201 said:
Thanks.
However i was checking the guide section but have not find the tutorial about removing the unlocked bootloader notification. Only the dm-verity notification removal i have found what i have got already.
A link would be appreciated :good::victory:
Click to expand...
Click to collapse
UPDATE
I have solved the issue. I am using multiROM and have realized ONLY the Internal ROM getting the safetynet pass!! So i was swap my internal OOS4.0.2 ROM with the Lineage OS. And now the Lineage is the internalROM and the oxygen is the secondary. The Lineage getting safetynet pass but the oxygen does not. Before swapping Oxygen having pass but Lineage does not...
Hope will help this who want to set it up in the future.
Title says it all. Im currently using using SuperSU so looking for Systemless root and looking for Xposed to work as well.
Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Do I remove SuperSU thru it's manager and then flash Magisk?
riahc3 said:
Do I remove SuperSU thru it's manager and then flash Magisk?
Click to expand...
Click to collapse
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.
jhedfors said:
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.
Click to expand...
Click to collapse
This just flash Magisk? No Xposed issues?
riahc3 said:
This just flash Magisk? No Xposed issues?
Click to expand...
Click to collapse
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.
jhedfors said:
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.
Click to expand...
Click to collapse
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....
When SuperSU asked if I wanted to recover the boot image (I think it was that) I said no.
Issues with that?
Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.
Says Ive lost root....
Magisk does say it is installed.
riahc3 said:
Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.
Click to expand...
Click to collapse
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch
riahc3 said:
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch
Click to expand...
Click to collapse
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.
Didgeridoohan said:
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.
Click to expand...
Click to collapse
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed
riahc3 said:
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed
Click to expand...
Click to collapse
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.
Didgeridoohan said:
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.
Click to expand...
Click to collapse
Doesnt systemless Xposed pass SafetyNet?
riahc3 said:
Doesnt systemless Xposed pass SafetyNet?
Click to expand...
Click to collapse
No.
Didgeridoohan said:
No.
Click to expand...
Click to collapse
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.
riahc3 said:
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.
Click to expand...
Click to collapse
Magisk works fine with SuperSU. It's if you'd ever want to hide root from some process or app that you might have some trouble, since Magisk Hide is developed with MagiskSU in mind.
There are some banking apps, Android Pay, Pokemon Go other apps that utilise SafetyNet. I do believe that more and more apps will use in the future and the cat and mouse game of hiding root is gonna continue...
riahc3 said:
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....
Click to expand...
Click to collapse
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks
anshulsingh said:
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks
Click to expand...
Click to collapse
I use Xposed modules in my daily life and cannot afford to be without them.
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
andQlimax said:
Without hiding the status of the bootloader, for sure Google Pay won't work. But Magisk Hide, can hide root status and bootloader status.
That's what I want to know, if Magisk Hide working or not
Waiting more responses from other users
Click to expand...
Click to collapse
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Google Pay works fine with Magisk. You don't need to hide it or hide Magisk Manager.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
axelryder said:
Can you explain how you were able to make it work? Because whether I hide Google Pay in Magisk or not, when I try to setup my credit card in Google Pay it says "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I have a OnePlus 3 Oxygen 5.0.6 and Android 8.0.0 with Magisk 17.1.
Click to expand...
Click to collapse
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
That's odd. I didn't have to do anything to get it working. I'm on OOS 5.0.5 and Magisk 17.1.
Two question: is your phone encrypted and do you have a pin/password set?
My phone is encrypted and I use a password.
You could also try hiding Magisk Manager (I haven't needed to do this) and delete any Magisk folder on you internal storage.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I have a pin set, I don't think my phone is encrypted; although when I go to the Security menu, under "Encryption" it does say "Encrypted", but I don't remember setting it up. So I guess it is!
I did try to hide Magisk Manager from their option in the settings menu, but I still got the same error in Google Pay after;
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
axelryder said:
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
tetra96 said:
I had a message last time that tells me that if I have my bootloader unlocked, no matter if I have Magisk or not, Google Pay won't let me pay with NFC
Click to expand...
Click to collapse
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
axelryder said:
...
As a side note, in Magisk SafetyNet Check does "Success", but ctsProfile is false, and basicIntegrity is false too; does that matter?
Click to expand...
Click to collapse
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
namanjr said:
Did you try with a custom kernel? Your kernel needs SultanXDA's patch to pass safetynet with a unlocked bootloader. There is a magisk module here, that might work if you don't want a custom kernel. There's also some commands you can run on your devices terminal here, that might work too. I only have experience with using a custom kernel but the changelog for the module does say it was patched for OP3 support.
Click to expand...
Click to collapse
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
My Safetynet check is successful. Yet it doesnt work with Google Pay. I am told that PAY is not supported on my device as it is rooted.
przemcio510 said:
Yes; SafetyNet check means that app contacted with Google server with success, but the result of your device check is false, which means that your device is not certified "secure" in its current state.
Perhaps you tampered system partition?
Click to expand...
Click to collapse
BillGoss said:
You've definitely installed something that breaks SafetyNet. Xposed used to do this, though I think it's been fixed to work with Magisk.
Both Magisk and custom kernels patch the boot image so that it doesn't trigger dm-verity and pass SafetyNet. You don't need to use a custom kernel if you're using Magisk.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
axelryder said:
I do indeed have Xposed installed, V90 beta 3. I guess maybe it's not fixed for Magisk after all :/
@przemcio510 do you use Xposed ?
Click to expand...
Click to collapse
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
przemcio510 said:
Yes, I do, Xposed breaks SafetyNet and there's nothing you can do to keep it installed and have SN passing
Click to expand...
Click to collapse
Oh I see... well here's my problem I guess lol
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Sahil Shaikh said:
On my Redmi note 4 From recent update of miui 10 and magisk 17.1 update google pay stopped working even though safety net check is passed. Earlier google pay was working fine.
Is there any work around?
Click to expand...
Click to collapse
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
This is a OnePlus 3T forum. Ask the question in the Redmi forum.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
I think that your problem is specific to MiUI, because on our phones it works fine
Sahil Shaikh said:
Okay, don't consider redmi note 4. Still do you got any way out for one plus 3?
Click to expand...
Click to collapse
As per the previous post, Google Pay works just fine with Magisk installed. There's no need to hide it.
Sent from my OnePlus3T using XDA Labs
andQlimax said:
Hi,
It's a long time that I don't use root on my Oneplus 3T.
What I want to know is that if with the latest Oxygen Os, unlocked bootloader and latest magisk root / magisk hide I will be able to use Google Pay.
I know that Google can update SafetyNet detection algorithm, so usually if that happens after how long Magisk is updated to hide root again?
Thanks!
Click to expand...
Click to collapse
It is reliant on safetynet AFAIK, and that passes on my device when using Magisk - havent tried Android Pay as of yet, but am aware that Safetynet passes.
Hi everyone, I need your help please .. I updated the device to android 10 and I reset the factory settings, thus losing the enable camera2api. I have the bootloader already unlocked is there a way to enable camera2 api on android 10? :crying:
Yeah. Problems here too
TonyTerry99 said:
Hi everyone, I need your help please .. I updated the device to android 10 and I reset the factory settings, thus losing the enable camera2api. I have the bootloader already unlocked is there a way to enable camera2 api on android 10? :crying:
Click to expand...
Click to collapse
+1
Patched boot Android 10
is there a way to already have the patched boot of android 10?
lol y u guys doing a factory reset after the update?
And no, stop complaining, its not a problem. it was your choice.
Have you guys already tried enabling cam2api like you did on pie? if not try doing so before making a thread
Thats the same as pie just root and install magisk then enable camera 2 api with buildprop or magisk modules
Did anyone tried https://forum.xda-developers.com/apps/magisk/module-camera2api-enabler-t3656651 ?
salmonthefish said:
lol y u guys doing a factory reset after the update?
And no, stop complaining, its not a problem. it was your choice.
Have you guys already tried enabling cam2api like you did on pie? if not try doing so before making a thread
Click to expand...
Click to collapse
Ok
Sohailsamdani said:
Ok
Click to expand...
Click to collapse
I would like to retry the same method used with android pie, but where can I find stock image boot?
TonyTerry99 said:
I would like to retry the same method used with android pie, but where can I find stock image boot?
Click to expand...
Click to collapse
Why you need a patched kernel?
Unlock bootloader
fastboot boot twrp-3.3.1-0-jasmine_sprout.img
adb push Magisk-v20.3.zip /sideload
(go to /sideload in TWRP)
Flash Magisk
Reboot
(do the same steps to enable camera2api as ou did on Pie)
You didn't even touched the system.
If you only want to boot an 'Magisk' patched boot file.
I've created this just now. magisk_patched_androi10_a2_11.0.4.0.img
Unlock bootloader
fastboot boot magisk_patched_androi10_a2_11.0.4.0.img
(do the same steps to enable camera2api as ou did on Pie)
I got it by editing build.prop
No Magisk modules worked here.
Resolved . thank you all
I solved thanks to patched boot, temporary root with magisk and activated unlocked the camera 2 bees with termux, restarted and removed the root.
On android 10 ? Gcam n stock camera no crash.... if yes please guide me, how to install gcam,.
If someone finds a Magisk module which is working, please share
TonyTerry99 said:
I solved thanks to patched boot, temporary root with magisk and activated unlocked the camera 2 bees with termux, restarted and removed the root.
Click to expand...
Click to collapse
Does the stock camera crash now? ?
Zedsdeadbaby said:
If someone finds a Magisk module which is working, please share
Click to expand...
Click to collapse
Just edit build.prop
Look for the lines with the string "HAL3" (2 lines total) and change their value form 0 to 1.
Then look for persist.vendor.camera.stats.test line and change its value to 5.
I know it's easy, but the point of having a Magisk module doing this is to be able to disable it and use the stock camera app with just a reboot.
Zedsdeadbaby said:
I know it's easy, but the point of having a Magisk module doing this is to be able to disable it and use the stock camera app with just a reboot.
Click to expand...
Click to collapse
With Magisk, do we receive Security Patch via OTA?
Zedsdeadbaby said:
If someone finds a Magisk module which is working, please share
Click to expand...
Click to collapse
Try with this:
View attachment 4929815
Thank you !
Just tried it and it's not working
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
Did you remove all modules prior to rooting March update?
Tulsadiver said:
Did you remove all modules prior to rooting March update?
Click to expand...
Click to collapse
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
dimm0k said:
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
Click to expand...
Click to collapse
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Tulsadiver said:
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Click to expand...
Click to collapse
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Tulsadiver said:
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Click to expand...
Click to collapse
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
dimm0k said:
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
Click to expand...
Click to collapse
Is it the MagiskHide Props Config module the one you're talking about?
So, I can't get Magisk to patch the boot image. It crashes every time I click let's go. I was on canary, went to the stable channel, rebooted, pushed the boot file over a few times, still nothing. Any ideas?
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you figure out which module? I have the same problem.
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
dimm0k said:
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
Click to expand...
Click to collapse
I had some stuff running. Here you go.
Tulsadiver said:
I had some stuff running. Here you go.
Click to expand...
Click to collapse
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
arh2o said:
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
Click to expand...
Click to collapse
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
EVR_PR said:
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
Click to expand...
Click to collapse
Mine shows it as passing. I'm using beta channel.
Weiii said:
Did you figure out which module? I have the same problem.
Click to expand...
Click to collapse
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
dimm0k said:
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
Click to expand...
Click to collapse
For me it was smali patcher, i think. Not 100% sure because I booted from Tulsadrivers once I got stuck at the Google logo, this took me into safe mode inside of magisk. Every time I would reboot (after deleting the magisk cache file) with smali patcher enabled it would get stuck. After I disabled magisk safe mode I re-installed smali patcher(re-creating the zip on my desktop). After that everything booted fine and passed all safetynet checks.
EVR_PR said:
Is it the MagiskHide Props Config module the one you're talking about?
Click to expand...
Click to collapse
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
1dopewrx05 said:
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
Click to expand...
Click to collapse
I went ahead and installed the Magisk Props config module before I read your message and that fixed the problem. Apparently Google forgot to certify this specific build for ATT (the one ending 004.A1). Thank you for your help though.