Hi, since 2 days they've been an update in the safety.net detection from google. I cannot log in pokemon go anymore. My configuration is 8.2.4 global, phone is not root, just unlocked, i had installed before superSu and Magisk. Has some people here recorded having the same problem ? Do you have some idea on a way to fix it ? My safety.net was not passing but the game was working, i have cts profile mismatch and basis integrity false.
You need to lock your BL for pass safetynet, or use Magisk and bypass It
Hello!
I am using a T-Mobile device converted to the newest Open Beta. Before, I converted it using the method which does not require a bootloader unlock; however, my device wouldn't pass Safetynet and I couldn't use Google Pay or download Netflix from the Play Store. Now, I've unlocked the bootloader, rooted my device, tried to use Magisk Hide and my device still doesn't pass Safetynet. It says "cts profile : false". Can anybody help me? What apps do I need to hide Magisk from? Are there any modules that can help with this? I would really like to be able to use Google Pay and be on Android Q, but I don't want to be stuck waiting on T-Mobile to roll it out.
Use magisk module called props to pass safety net
How I can cheat the "bootloader unlock detection" to use AI upscaling as AI-Enhanced?
I have UNLOCKED nvidia-shield-2019-pro with SW.8.2.0-dev_rooted
I'd like to use AI upscaling as “AI-Enhanced” mode while the bootloader is unlocked
Can I change the following parameter(s) manually after boot and cheat/bypass the "bootloader unlock detection" and device stay UNLOCKED after reboot?
Code:
getprop ro.boot.verifiedbootstate: orange --to--> [COLOR="SeaGreen"][B]green[/B][/COLOR]
or
Code:
ro.boot.vbmeta.device_state: unlocked --to--> [B][COLOR="seagreen"]locked[/COLOR][/B]
or
Code:
sys.oem_unlock_allowed: 1 --to--> [B][COLOR="seagreen"]0[/COLOR][/B]
Checking this, https://github.com/topjohnwu/Magisk...0c0/native/jni/magiskhide/hide_policy.cpp#L12
MagiskHide sets them as follow
ro.boot.vbmeta.device_state=locked
ro.boot.verifiedbootstate=green
ro.boot.flash.locked=1
ro.boot.veritymode=enforcing
ro.boot.warranty_bit=0
ro.warranty_bit=0
ro.debuggable=0
ro.secure=1
ro.build.type=user
ro.build.tags=release-keys
ro.vendor.boot.warranty_bit=0
ro.vendor.warranty_bit=0
vendor.boot.vbmeta.device_state= locked
Click to expand...
Click to collapse
But it seems like you are getting black screen after reboot?
Any news on this? Would love to be able to root and use AI upscaler..
cHECKjAM said:
Any news on this? Would love to be able to root and use AI upscaler..
Click to expand...
Click to collapse
Same for me I would like to have the root and the Ai Upscaler
thank you for all
So just to be clear, AI Upscaler works unrooted, but if it detects root then it will disable the feature?
If that is the case, has anyone figured this one out?
I'm also reading that Magisk Hide causes a black screen at boot?
The AI Upscaler is blocked when you unlock the bootloader, rooted or not.
xene1902 said:
The AI Upscaler is blocked when you unlock the bootloader, rooted or not.
Click to expand...
Click to collapse
Obviously! we are looking for a trick to cheat unlock/root detection process and magiskHide may help, but got boot-loop as much as I tried.
mrhamed said:
Obviously! we are looking for a trick to cheat unlock/root detection process and magiskHide may help, but got boot-loop as much as I tried.
Click to expand...
Click to collapse
Thank you very much
I just noticed this.
With the latest update, latest magisk canary build, lsposed installed, and magiskhide off
I am not getting the Unlocked Bootloader error for AI Enhance mode. I still get Unsupported Content, but that's probably down to my TV setup.
Might be worth looking into
LazorBlind said:
I just noticed this.
With the latest update, latest magisk canary build, lsposed installed, and magiskhide off
I am not getting the Unlocked Bootloader error for AI Enhance mode. I still get Unsupported Content, but that's probably down to my TV setup.
Might be worth looking into
Click to expand...
Click to collapse
hm this is really interesting you could be on the cusp of getting it to work, can you verify it is your tv setup to rule that out?
Installing sefetynet-fix as a module to magisk do the trick
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
I tried don't work, sorry.
Corti_Sonyx said:
Installing sefetynet-fix as a module to magisk do the trick
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Click to expand...
Click to collapse
does it really work?
Nope. It doesn't work
Rooting works, but ai upscaling don't. Also google play store uncerified , but it stills bypass the safetynet. Strange
Does this device have a physical fuse? Does AI upscaler become available when relook bl?
When you lock bootloader, ai upscaling is back. Don't know about the fuse.
Then it’s not fuse
Prob unbypassable, kinda like strong attestation.
abc1054 said:
Rooting works, but ai upscaling don't. Also google play store uncerified , but it stills bypass the safetynet. Strange
Click to expand...
Click to collapse
Found this advice on another thread.
"Make sure you clear data on Play Store and Services then reboot. If you're not clearing data the old failure will still be there."
Hey,
I had the PixelElxperience custom rom installed until I heard about the new android 11 oxygenos beta. So I installed the new beta. Only problem there is I don't pass the safetynet anymore. I locked the bootloader which lets me pass google pays safety as I can add paypal. But my banking app doesn't let me log in.
Use magiskhide...
I second MagiskHide with the additional option of setting your props config to OnePlus 6T on Android 10.
hi I have always managed to pay contactless with Gpay with magisk, but after this update I found no way to pay since Gpay tells i'm unable to add my cards since my phone is rooted.
Is it happening to you as well?
any solution?
It's because the update is reporting a wrong version, if you check your version in About Device it'll say C.21 instead of C.20.
People on the SafetyNet Fix git made this list to get it to work: https://github.com/kdrag0n/safetynet-fix/issues/188#issuecomment-1147295375
Here's the newer SafetyNet Fix they use (v2.3.0): https://github.com/frnode/safetynet-fix/releases