After Upgrading to Android 10 Beta
My Phone Is Failing SafetyNet check.
How To Fix It?
iamgulshan said:
After Upgrading to Android 10 Beta
My Phone Is Failing SafetyNet check.
How To Fix It?
Click to expand...
Click to collapse
Wait for a stable release of Android 10. There is no option to fix it.
Beta releases typically aren't signed for CTS profile matching until a while later (e.g. last I checked I think Beta 4 passes CTS now, though I am now on Beta 6).
Best just to wait for a stable Android 10 release like suggested then all will be good.
Try HiddenCore module for edxposed https://repo.xposed.info/module/com.cofface.ivader worked for me on A9
Related
As title, is the last beta 19.4?
Thanks for help.
Go to the Magisk setting, tap the Update field by selecting DEV Canary Channel, it will update itself, then you press update.
Just for some clarification:
Magisk v19.4 is not a beta release but a pre-beta Canary release for those who are willing to test new and possibly broken code.
And, if you really want to install the Canary release, you'll find the information you need here: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Thanks a lot!!
Sent from my OnePlus 7 Pro using XDA Labs
After upgrading to the beta, I cannot use Google Pay at all. It says something like software not verified.
Is there any possible workaround to this?
benjaminllim said:
After upgrading to the beta, I cannot use Google Pay at all. It says something like software not verified.
Is there any possible workaround to this?
Click to expand...
Click to collapse
dont update to the BETA.
benjaminllim said:
After upgrading to the beta, I cannot use Google Pay at all. It says something like software not verified.
Is there any possible workaround to this?
Click to expand...
Click to collapse
Nope, beta aren't certificated for safety net so no google pay (you can use samsung pay anyway)
Question to add -
I upgraded to the OneUI 2.0 beta, to get onto Android 10 sooner, but when OneUI 2.0 is out of beta, will I be placed on the next beta release or will I just be converted to release software. I'd like to use Google Pay, but i can deal without until Android 10 is officially on the note 9
halfcreative said:
I upgraded to the OneUI 2.0 beta, to get onto Android 10 sooner, but when OneUI 2.0 is out of beta, will I be placed on the next beta release or will I just be converted to release software. I'd like to use Google Pay, but i can deal without until Android 10 is officially on the note 9
Click to expand...
Click to collapse
I think you'll automatically are opted in for future beta releases
Hello everyone,
I just received a new Magisk update. Does it mean that I don't need Canary for android 11 anymore? Since there's a new version?
I am just afraid to root with Canary, heard stories and don't want to take the even bigger risk.
Thanks
I'm currently on canary with 11. Having no issues.vehat are you referring to?
Sent from my Nexus 5 using Tapatalk
TY53 said:
Hello everyone,
I just received a new Magisk update. Does it mean that I don't need Canary for android 11 anymore? Since there's a new version?
I am just afraid to root with Canary, heard stories and don't want to take the even bigger risk.
Thanks
Click to expand...
Click to collapse
You are still on 10, waiting?? Pretty sure you will still need canary to root 11. What does the changelog say on your stable version? Until it says "supports Android 11" you'll still need to use the canary version which by the way is quite safe if you are using pretty much any mainstream phone. There is no risk at all. Use canary to patch the stock boot image. Put both in the same folder. Flash the patched image. If you don't have immediate success, you simply flash the stock boot.img and you are back to stock. Any stories you heard are just that... stories.
TY53 said:
Hello everyone,
I just received a new Magisk update. Does it mean that I don't need Canary for android 11 anymore? Since there's a new version?
I am just afraid to root with Canary, heard stories and don't want to take the even bigger risk.
Thanks
Click to expand...
Click to collapse
The new Stable Magisk Manager (8.0.0) is fine to use on Android 11. The latest Beta Magisk (21.0) is also fine to use on Android 11. Both were just updated to be Android 11 compatible. Soon the Beta Magisk will be moved to the Stable channel once any bugs (if any) are worked out.
By the way, the latest Canary also works fine on Android 11.
Installation instructions and documentation have been updated. https://github.com/topjohnwu/Magisk
Thanks for answering ?. I'll see if it says supports android 11. Yes I was on 10 waiting, root is a small risk, but Canary is a bigger one that I didn't want to take. Hopefully it supports it and I can root to Android 11.
By the way, do you know if the Soli motion sense module works with Android 11?
Thanks in advance
TY53 said:
Thanks for answering ?. I'll see if it says supports android 11. Yes I was on 10 waiting, root is a small risk, but Canary is a bigger one that I didn't want to take. Hopefully it supports it and I can root to Android 11.
By the way, do you know if the Soli motion sense module works with Android 11?
Thanks in advance
Click to expand...
Click to collapse
The latest Beta does support Android 11. https://twitter.com/topjohnwu/status/1312342107139440640
Make sure you set the channel in the Manager to Beta.
I don't know anything about the Soli motion sense module..
Lughnasadh said:
The latest Beta does support Android 11. https://twitter.com/topjohnwu/status/1312342107139440640
Make sure you set the channel in the Manager to Beta.
I don't know anything about the Soli motion sense module..
Click to expand...
Click to collapse
:good:
TY53 said:
Thanks for answering ?. I'll see if it says supports android 11. Yes I was on 10 waiting, root is a small risk, but Canary is a bigger one that I didn't want to take. Hopefully it supports it and I can root to Android 11.
By the way, do you know if the Soli motion sense module works with Android 11?
Thanks in advance
Click to expand...
Click to collapse
It's ready to go now. Latest version 21 (MM v8.0.0) stable supports 11. I don't use the Soli module so can't comment on that.
TY53 said:
Thanks for answering ?. I'll see if it says supports android 11. Yes I was on 10 waiting, root is a small risk, but Canary is a bigger one that I didn't want to take. Hopefully it supports it and I can root to Android 11.
By the way, do you know if the Soli motion sense module works with Android 11?
Thanks in advance
Click to expand...
Click to collapse
I'm on 11 with canary rooted. Patched EnableSoli.Magisk20.2.V1.2 via magisk is working
Hi,
I know MagiskHide is going away, and I am planning to upgrade to the Pixel 6 Pro in the next 1-2 weeks.
However, my Pixel 4 XL is still rooted on Android 11.
I opened Magisk last night and saw that there was an update and updated to:
Magisk: d7e7df3b (23010)
App: d7e7df3b (23010)
When I did this, Magiskhide and SafetyNet Check were completely removed. i know this will probably be inevitable in the future, but can anyone ptovide me link to the previous Magisk flash and app version, so I can reverse everything?
As of now, I can no longer use Android Pay and many of my previously hidden apps will no longer run.
diesteldorf said:
Hi,
I know MagiskHide is going away, and I am planning to upgrade to the Pixel 6 Pro in the next 1-2 weeks.
However, my Pixel 4 XL is still rooted on Android 11.
I opened Magisk last night and saw that there was an update and updated to:
Magisk: d7e7df3b (23010)
App: d7e7df3b (23010)
When I did this, Magiskhide and SafetyNet Check were completely removed. i know this will probably be inevitable in the future, but can anyone ptovide me link to the previous Magisk flash and app version, so I can reverse everything?
As of now, I can no longer use Android Pay and many of my previously hidden apps will no longer run.
Click to expand...
Click to collapse
If you are referring to the latest stable version, 23.0, it's in his Github.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Thanks.....so I'm planning to revert back to 23.0 and then use 23.0 to repatch the stock boot.img. Hoping that will restore Magiskhide and everything I had before the update.
At this point, I am planning to stick with Android 11 and just want to reverse the upgrade from last night.
Really appreciate your help.
You can try Magisk Alpha (t.me/magiskalpha)
It is a forked version of Magisk by one of its former lead developers. It has option to choose between zygisk and magisk hide. I tested it on Pixel 4 XL and 6 Pro where it was able to pass safetynet checks.
If you happen to have a Redmi Note 10 Pro (SWEET) with the latest ROM: sweet_global_images_V13.0.12.0.SKFMIXM_20220801.0000.00_12.0_global,
Can you please check these applications and post the results?
https://play.google.com/store/apps/details?id=rikka.safetynetchecker YASNAC
and
https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck Play Integrity api checker.
Because I can't understand why I have only one green on Play integrity checker and CTS fail on YASNAC.
This can be helpful for everyone.
And lead to a better understanding of the checking process.
I suspect that xiaomi did something wrong and the lates rom is not certified.
Zibri said:
If you happen to have a Redmi Note 10 Pro (SWEET) with the latest ROM: sweet_global_images_V13.0.12.0.SKFMIXM_20220801.0000.00_12.0_global,
Can you please check these applications and post the results?
https://play.google.com/store/apps/details?id=rikka.safetynetchecker YASNAC
and
https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck Play Integrity api checker.
Because I can't understand why I have only one green on Play integrity checker and CTS fail on YASNAC.
This can be helpful for everyone.
And lead to a better understanding of the checking process.
I suspect that xiaomi did something wrong and the lates rom is not certified.
Click to expand...
Click to collapse
Redmi Note 10 Pro GlobalStable BetaRecoveryV13.0.12.0.SKFMIXM12.03.4 GB2022-08-05
Unlocking bootloader leads to CTS failing. But if you have locked bl and you fail CTS then yeah idk what's the problem, maybe format can help.
NOSS8 said:
Redmi Note 10 Pro GlobalStable BetaRecoveryV13.0.12.0.SKFMIXM12.03.4 GB2022-08-05
Click to expand...
Click to collapse
???
I tried both STOCK MIUI 13.0.12 both 13.0.8.
I always get that the device is not certified.
Reflashed everything.
Zibri said:
I tried both STOCK MIUI 13.0.12 both 13.0.8.
I always get that the device is not certified.
Reflashed everything.
Click to expand...
Click to collapse
it is because the bootloader is unlocking.
Install a Xiaomi Eu rom
https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
Zibri said:
???
Click to expand...
Click to collapse
STABLE BETA is not STABLE
tried now.. it checks out fine only if the bootloader is locked and everything is untouched.
Mine's rooted, MAGISK. YASNAC all good, but fails 'MEETS STRONG INTEGRITY' IN other one
NOSS8 said:
STABLE BETA is not STABLE
Click to expand...
Click to collapse
I got v13.0.13 on o stock Redmi Note 10 Pro after I had booted the phone for the first time with a locked bootloader fyi
RAMBO29 said:
Mine's rooted, MAGISK. YASNAC all good, but fails 'MEETS STRONG INTEGRITY' IN other one
Click to expand...
Click to collapse
Strong Integrity means Hardware backed. Theres no way to get that unless you relock the bootloader. No need to worry if you only pass Basic and Device Integrity, afaik only 3 apps seem to check for Strong Integrity API.
jnsson said:
I got v13.0.13 on o stock Redmi Note 10 Pro after I had booted the phone for the first time with a locked bootloader fyi
Click to expand...
Click to collapse
V13.0.13.0.SKFEUXM is a stable beta too.
NOSS8 said:
V13.0.13.0.SKFEUXM is a stable beta too.
Click to expand...
Click to collapse
Ive been running this version over a month now, All the tests ive done show that although its listed as stable the Battery life is less than previous Miui versions. Perhaps thats not a bug, maybe something changed in the firmware.
gazza35 said:
Ive been running this version over a month now, All the tests ive done show that although its listed as stable the Battery life is less than previous Miui versions. Perhaps thats not a bug, maybe something changed in the firmware.
Click to expand...
Click to collapse
It shows as stable on the phone but look at my link.
For a few years, Xiaomi has provided stable beta builds on the stable circuit, but sometimes the beta version doesn't have too many bugs but sometimes a lot.
Sometimes also the stable beta version is renamed to stable without any changes with or without bugs.
redmi note 10 pro autoupdates 12.5.9 to 13.0.12.0. And that's not a beta... it probably was.
Anyway, with unlocked bootloader and magisk, even with safetynet fix 2.3.1 it passes only BASIC and not even device integrity.
Same goes for 12.5.9 ... they must have changed something.