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."
Related
Lots of apps are beginning to block me from being able to use (Prime Video, ADT are a couple) with bootloader unlocked. It's not the root, because I have Magisk Hide. Is it possible to relock the bootloader and keep root and twrp? This is the H918 running 10s debloated.
No. Unlocking the bootloader is what stops it from checking the integrity of boot and recovery. If you lock your bootloader, it will bootloop.
This is where all other models have an advantage. The debug bootloader reports that it is locked even though it isn't.
-- Brian
pre4speed said:
Lots of apps are beginning to block me from being able to use (Prime Video, ADT are a couple) with bootloader unlocked. It's not the root, because I have Magisk Hide. Is it possible to relock the bootloader and keep root and twrp? This is the H918 running 10s debloated.
Click to expand...
Click to collapse
I am able to play prime video content on my h918. I do not know about adt, but I am able to use bank apps with magisk. I suspect Google Play thinks your device is "uncertified". Go to the Play Store then settings and check the very bottom for device certification. I find a lot of apps use this check to disable app/content.
darkknight1812 said:
I am able to play prime video content on my h918. I do not know about adt, but I am able to use bank apps with magisk. I suspect Google Play thinks your device is "uncertified". Go to the Play Store then settings and check the very bottom for device certification. I find a lot of apps use this check to disable app/content.
Click to expand...
Click to collapse
Before I did the update to 10s,it did say uncertified. Now it says certified, so it's not that. Directv now wouldn't work until I hid root, but both those apps still said my system was modified even hiding root from them. Oh I should also mention Netflix works fine. Those 2 apps tho, they will not.
I have a moto e4 safety net check says ctsprofile false basicintegrity false how fix
happymedium22026 said:
I have a moto e4 safety net check says ctsprofile false basicintegrity false how fix
Click to expand...
Click to collapse
Are you using Xposed? Then you will never pass safetynet. One will always fail because of dmverity. You need a custom boot.img
It had been working up until a couple days ago i havent install anything different
Check in your magisk hide settings. Make sure it's all set right.
It shouldn't just change to false. You have to change something for that. Are you using Xposed?
Make sure if you're using Magisk for root that your root apps aren't doing something to trip SafetyNet, like installing new System apps or removing them, since SafetyNet checks to make sure your system.img matches the stock firmware for your device.
I heard something about an update to SafetyNet recently that's producing some false positives. For example, my SafetyNet checks out clean, but I keep getting kicked out of Pokémon Go saying that there's something wrong with the device.
chuman72486 said:
Make sure if you're using Magisk for root that your root apps aren't doing something to trip SafetyNet, like installing new System apps or removing them, since SafetyNet checks to make sure your system.img matches the stock firmware for your device.
I heard something about an update to SafetyNet recently that's producing some false positives. For example, my SafetyNet checks out clean, but I keep getting kicked out of Pokémon Go saying that there's something wrong with the device.
Click to expand...
Click to collapse
Pokemon go is a very different situation. It's checking more than just safetynet. There are threads devoted to that.
Benefits/downsides of doing that?
Thanks
I think you can't. Magisk overwrites your boot.img and that's the issue. Guess your phone won't boot afterwards.
Indeed. I tried it and it just got to the mi logo and rebooted itself over and over.
You can lock bootloader by restoring previous boot image in Magisk manager, then you should be okay.
You can't or it will show something like "Your device is destroyed"
You cannot lock bootloader after *any* system mod. Plain and simple.
Hi, please I have a question about this.
So, How do you use banking or paying apps like Google Pay if it checks for unlocked bootloader?
I would like to use Magisk + Google Pay and I dont see the way.
Thanks!
skorzo said:
Hi, please I have a question about this.
So, How do you use banking or paying apps like Google Pay if it checks for unlocked bootloader?
I would like to use Magisk + Google Pay and I dont see the way.
Thanks!
Click to expand...
Click to collapse
With unlocked bootloader, you must install Magisk to pass SafetyNet. If you don't have Magisk installed and you have an unlocked bootloader, you will fail SafetyNet with ctsProfile being false, rendering you unable to install and run apps requiring you to pass SafetyNet. As long as you pass SafetyNet, you can run banking apps and Google Pay with no problems.
why so many people afraid to keep bootloader unlocked? ok is a security risk, but if high unlikely to have issue if you dont install/run bad stuff on your phone... or i mistake?
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
Hello. I have some issue with gpay on oos13. In2023 11_f_64.
I have root with magisk26.1 hidden.
The safetynet passed with safetynet fix module.
the problem is Gpay work for some hours on my device then after hours i got a message saying my device dont match the security requirement and that i can not use gpay. When i clean all the data of the google play store and the google play service. I can use gpay again. But after some hours i got the same message. I think it may detect the unlocked bootloader. Do somebody face the same problem ? Any solutions ?
stell52 said:
Hello. I have some issue with gpay on oos13. In2023 11_f_64.
I have root with magisk26.1 hidden.
The safetynet passed with safetynet fix module.
the problem is Gpay work for some hours on my device then after hours 192.168.100.1 192.168.1.1 i got a message saying my device dont match the security requirement and that i can not use gpay. When i clean all the data of the google play store and the google play service. I can use gpay again. But after some hours i got the same message. I think it may detect the unlocked bootloader. Do somebody face the same problem ? Any solutions ?
Click to expand...
Click to collapse
Google Pay uses SafetyNet API to check for device integrity and security. If any modifications have been made to the system or if the bootloader is unlocked, it can trigger a SafetyNet failure, leading to GPay not working properly.
SAMI_AI202 said:
Google Pay uses SafetyNet API to check for device integrity and security. If any modifications have been made to the system or if the bootloader is unlocked, it can trigger a SafetyNet failure, leading to GPay not working properly.
Click to expand...
Click to collapse
Thanks you for your reply. I still always pass the safetynet test but gpay is not working