I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
You can get it to pass by installing a couple modules in Magisk. The first one is busybox as a requirement. The second on is MagiskHideProps; it does the work. Use it to change the fingerprint to a Pixel 3 on Pie. I do not know the drawbacks of doing this, but you will pass the ctsprofile check and be able to use GPay.
Meatmassuse said:
I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
Click to expand...
Click to collapse
cmrntnnr said:
You can get it to pass by installing a couple modules in Magisk. The first one is busybox as a requirement. The second on is MagiskHideProps; it does the work. Use it to change the fingerprint to a Pixel 3 on Pie. I do not know the drawbacks of doing this, but you will pass the ctsprofile check and be able to use GPay.
Click to expand...
Click to collapse
Yea, that's the eventual option I came too as well. Haven't noticed any ill effects yet but who knows if it'll work forever. One amusing side effect was a free 100gbs on google drive when I opened the app. Some pixel promo ot said, haha.
Meatmassuse said:
I'm on an lg-v350, originally from at&t but it is currently unlocked, rooted with magisk and running Android 9. My device has been "ctsprofile:failed" for a awhile now. Not the biggest deal but if anyone has a certified device fingerprint I'd be very appreciative.
Click to expand...
Click to collapse
From stock AT&T V35 with latest PIE and security update. These should work with the Magisk props module to pass CTSProfie. I haven't cross-flashed, unlocked or rooted mine due to concerns with widevine L1 and the lack of an AT&T stock backup ROM.
[ro.build.fingerprint]: [lge/judyp_lao_com/judyp:9/PKQ1.181105.001/200341345c8c9.FGN:user/release-keys]
[ro.build.version.security_patch]: [2020-02-01]
Config attached (remove txt extension and place in sdcard directory, then choose custom fingerprint in props module).
rlw6534 said:
From stock AT&T V35 with latest PIE and security update. These should work with the Magisk props module to pass CTSProfie. I haven't cross-flashed, unlocked or rooted mine due to concerns with widevine L1 and the lack of an AT&T stock backup ROM.
[ro.build.fingerprint]: [lge/judyp_lao_com/judyp:9/PKQ1.181105.001/200341345c8c9.FGN:user/release-keys]
[ro.build.version.security_patch]: [2020-02-01]
Config attached (remove txt extension and place in sdcard directory, then choose custom fingerprint in props module).
Click to expand...
Click to collapse
I want you too know that I'd divorce my wife for you sir haha. For real though, thanks bruv.
Meatmassuse said:
I want you too know that I'd divorce my wife for you sir haha. For real though, thanks bruv.
Click to expand...
Click to collapse
Glad to help. I learned a while back to back up my props before hacking on my android devices...
Does anyone have the Oreo fingerprint for AT&T V35? I would very, very much appreciate it. I have cross-flashed to Oreo ULM and can't get CTSprofile to pass using the Pie version.
Edit:
Nevermind. Fixed it by upgrading to ULM Pie and flashing FTM, modemst1 and modemst2 from AT&T.
Related
Hey guys, I'm stock, rooted, s-off with magisk and I'd like to be on Lee Droid or Viper Nougat with working Magisk and Verizon features. The way I'm reading their guides, it seems I would have to be on Nougat firmware for that. Does that mean I can convert to US Unlocked Nougat with updated firmware, then to Lee Droid or Viper Magisk and pass safety net while having nougat and advanced calling and such?
Thanks guys
I'd love to know the answer to this as well. I don't have many friends using Verizon, so I don't use the Verizon features much. I'm just kind of tired of Verizon being slow with their updates. For some reason I keep being stupid and buying Verizon phones despite the long updates for 4 different phones that have been on Verizon. :/
you guys have to flash the US unlocked RUU and then flash the Verizon radio for it to work. From what I've read you'll have the features you want. But since I haven't personally tried I cannot be 100%. there is guides on how to do this.
IMHO, I would wait for Verizon, it is always best to use your carriers firmware. It wont be much longer even though itll feel like a lifetime.
I'd love to get a confirmation on this as well. I can say however from my own experience that running VZW firmware with viper10 4.x.x ROM that everything works great EXCEPT volte (HD calling/ advanced calling features) I'd like to mention to others who are experimenting as well that I can format data, flash 3.5.0 and have volte back up and running no problem. My theory is the issue lies in the VZW firmware being a MM version. My next step is to flash the nougat RUU, flash the VZW radio, and then the viper nougat ROM. I'll share the results once I get the chance to do everything. Again if anyone can chime in on this method that would be greatly appreciated.
ROMs now support Advanced Calling with Magisk.
now just need vzw nougat.
andybones said:
ROMs now support Advanced Calling with Magisk.
now just need vzw nougat.
Click to expand...
Click to collapse
Really? What changed?
Im on viper with 1.85 firmware and advanced calling works for me
jhorn85 said:
Im on viper with 1.85 firmware and advanced calling works for me
Click to expand...
Click to collapse
Did you do anything special when you installed the ROM? Could you tell me what steps you took installing it? Just wondering if I'm missing something. I have the latest VZW firmware installed as well. Are you positive that advanced calling is working? I notice that when you make a call the data signal icon will remain on the status bar (unless you go into venom tweaks and change it to anything other than the stock icon, then it will disappear) but there won't be any traffic and I can confirm it by trying to load a web page.
aer0zer0 said:
Really? What changed?
Click to expand...
Click to collapse
Some team work from lee, captn, nkk, baad, and testers.
on multirom with advanced calling and wifi calling, leedroid N.
https://forum.xda-developers.com/showpost.php?p=70525234&postcount=5074
andybones said:
Some team work from lee, captn, nkk, baad, and testers.
on multirom with advanced calling and wifi calling, leedroid N.
https://forum.xda-developers.com/showpost.php?p=70525234&postcount=5074
Click to expand...
Click to collapse
So this is the last intermediate step to getting the extra verizon functions to work? Im assuming once androidkitchen is fixed to set the values properly, we should be able to build it in directly?
aer0zer0 said:
So this is the last intermediate step to getting the extra verizon functions to work? Im assuming once androidkitchen is fixed to set the values properly, we should be able to build it in directly?
Click to expand...
Click to collapse
That's what it's looking like to me. With some work it is possible to get ROMs working on MM firmware with VoLTE and Wi-Fi calling. Santods rom has had this for a little bit and now with this new information, if one was to say combine both, the outcome is great. But I'll leave that to those more experienced than myself, but it is possible now thanks to all these brilliant minds.
Is the magisk files in the magisk repo?
aer0zer0 said:
Is the magisk files in the magisk repo?
Click to expand...
Click to collapse
That I am not sure of, sorry.
aer0zer0 said:
So this is the last intermediate step to getting the extra verizon functions to work? Im assuming once androidkitchen is fixed to set the values properly, we should be able to build it in directly?
Click to expand...
Click to collapse
Need verizon to update to n, that's the step we need. On mm it's still broken on n based Roms
Other Than that yes
afuller42 said:
Need verizon to update to n, that's the step we need. On mm it's still broken on n based Roms
Other Than that yes
Click to expand...
Click to collapse
on a personal build combined from Santods mostly I am able to be on Leedroid N on latest Verizon MM firmware with multirom with VoLTE and Wi-Fi calling.
andybones said:
on a personal build combined from Santods mostly I am able to be on Leedroid N on latest Verizon MM firmware with multirom with VoLTE and Wi-Fi calling.
Click to expand...
Click to collapse
Works now on latest Viper 4.6.0 also
sdamark said:
Works now on latest Viper 4.6.0 also
Click to expand...
Click to collapse
Still not working for me, ill try a clean install at some point. Volte never broke for me on any update, been lucky on that i guess
@andybones also
sdamark said:
Works now on latest Viper 4.6.0 also
Click to expand...
Click to collapse
Even better. Didn't realize that 4.6.0 was out, so I don't know of the change log.
Wasn't bragging by any means also.. Was just stating that it works, and was sure smarter devs would get it soon.
I can confirm that the viper 4.6.0 upgrade does fix volte for vzw devices running mm firmware. The changelog says only working for non magisk version, I suppose that's due to no nougat firmware/RUU released from Verizon yet. If that's a deal breaker your gonna have to wait, otherwise make sure your running the supersu only version. I upgraded from 4.5.0 and it works perfectly. Something I've noticed over the last few months with all the flashing I have done is that if you go into the hidden network info screen, if it shows 3107 for your carrier, it won't work, if it says Verizon wireless as your carrier, then everything is working as it should. Thanks for the update in the rom guys this is GREATLY appreciated for the hard work.
Got a message from Google Pay saying that my phone is rooted or is running uncertified software.
I have a T-Mobile variant that I converted , without root, to international. Anyone else see this issue?
Read. This is an old problem for years. Is your bootloader unlocked? Not rooted? Yes this breaks GPay. Hence, Magisk, root, systemless and Hide.
Easy fix.
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
coolmaster121 said:
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
Click to expand...
Click to collapse
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
plasmamax1 said:
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
Click to expand...
Click to collapse
Thanks for the suggestion.
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
coolmaster121 said:
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
Click to expand...
Click to collapse
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
p51d007 said:
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
Click to expand...
Click to collapse
It was a zip I downloaded and did a local update.
Caltinpla said:
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Click to expand...
Click to collapse
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
Yep
No, works fine. But I don't have a converted variant - all stock.
If you go back to stock as it is with T-variant (search for MSM tool), is it certified again?
https://forum.xda-developers.com/showpost.php?p=80844361&postcount=7
noideas4thisname said:
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
Click to expand...
Click to collapse
Nope, I tried everything I heard of but nothing worked. Hopefully, OP releases an update with the fix soon!
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
Seems to be working just like everyone else's T-Mobile Android 10 OP6T. This is a known issues on our devices.
bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
It's a bug, you're going to have to wait until it's patched, no ETA from OnePlus yet.
Sent from my ONEPLUS A6013 using Tapatalk
I converted my T-Mobile phone using the MSM tool (no root) a while ago and never had trouble with Google Pay. It stopped working only after the latest update (Android 10.0). I hope OP will fix this in their next update.
Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?
Scott said:
Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?
Click to expand...
Click to collapse
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...
cultofluna said:
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...
Click to expand...
Click to collapse
The latest magiskhide props module has a valid 6T A10 fingerprint, I'm using it and my device is certified.
Hi, I have a T-Mobile version of OnePlus 6t and it is unlocked. I converted to global room but Can I update to oxyen os 10.3?
I saw posts that T-Mobile version needs to wait T-Mobiles OTA but I am not sure this applied to post-unlocked one.
Ruin2580 said:
Hi, I have a T-Mobile version of OnePlus 6t and it is unlocked. I converted to global room but Can I update to oxyen os 10.3?
I saw posts that T-Mobile version needs to wait T-Mobiles OTA but I am not sure this applied to post-unlocked one.
Click to expand...
Click to collapse
I have a converted TMobile op6t and upgraded to 10.1 then just local upgraded to 10.3 without issues but just last night I flashed the open beta 3. Your fine to upgrade.
Ruin2580 said:
Hi, I have a T-Mobile version of OnePlus 6t and it is unlocked. I converted to global room but Can I update to oxyen os 10.3?
I saw posts that T-Mobile version needs to wait T-Mobiles OTA but I am not sure this applied to post-unlocked one.
Click to expand...
Click to collapse
I went from 9.0.17 to 10.3 with a local upgrade - all seems to work fine. Except for Google certification that will not be available till TMobile release A10 and certify the device. So some applications will not show in Play Store (Like Netflix) and GPay will not work.
polzovotel said:
I went from 9.0.17 to 10.3 with a local upgrade - all seems to work fine. Except for Google certification that will not be available till TMobile release A10 and certify the device. So some applications will not show in Play Store (Like Netflix) and GPay will not work.
Click to expand...
Click to collapse
Question, I have the apk saved and I install say Netflix apk onto android 10, would I be able to use the app or would it be unable to install/work?
ozzmanj1 said:
Question, I have the apk saved and I install say Netflix apk onto android 10, would I be able to use the app or would it be unable to install/work?
Click to expand...
Click to collapse
Yes, you can. You better install Netflix BEFORE upgrading. The reason is Netflix deployment is not one APK - you will need to use 3d party to deploy Netflix apk.
polzovotel said:
I went from 9.0.17 to 10.3 with a local upgrade - all seems to work fine. Except for Google certification that will not be available till TMobile release A10 and certify the device. So some applications will not show in Play Store (Like Netflix) and GPay will not work.
Click to expand...
Click to collapse
Did you install safety net on magisk? My playstore is certified on 6t, 10.3, rooted etc
bigjailerman said:
Did you install safety net on magisk? My playstore is certified on 6t, 10.3, rooted etc
Click to expand...
Click to collapse
I do not have root
Sent from my [device_name] using XDA-Developers Legacy app
beany23 said:
I have a converted TMobile op6t and upgraded to 10.1 then just local upgraded to 10.3 without issues but just last night I flashed the open beta 3. Your fine to upgrade.
Click to expand...
Click to collapse
Did you use the incremental or full package? The incremental fails as soon as you click it. I am giving the full pkg a try.
vibraniumdroid said:
Did you use the incremental or full package? The incremental fails as soon as you click it. I am giving the full pkg a try.
Click to expand...
Click to collapse
For those of us on converted TMO devices, you can only use full packages. The incremental will fail Everytime.
What steps did you use to root? Did you do it after installing A10?
---------- Post added at 03:34 PM ---------- Previous post was at 03:33 PM ----------
bigjailerman said:
Did you install safety net on magisk? My playstore is certified on 6t, 10.3, rooted etc
Click to expand...
Click to collapse
polzovotel said:
Yes, you can. You better install Netflix BEFORE upgrading. The reason is Netflix deployment is not one APK - you will need to use 3d party to deploy Netflix apk.
Click to expand...
Click to collapse
May I ask, when you went from 9.0.17 to 10.3, did you use Oxygen updater? I have converted twice now from A9 to A10 and both times had to msmtool back to A9.17 due to various issues. I would like to update to A10, but don't want to have an issue and have to re-wipe everything and go through the ordeal of unlocking bootloader again as well as copying all my files back to my phone and setting things back up.
Did you have any issues with your upgrade or was it a seemless experience? I realize there is Netflix and google play (I do use Netflix but no Gpay).
If it worked good for you I may consider going to 10.0.3 from 9.0.17 in the next day or so. I realize the upgrading is all subjective, just curious
ozzmanj1 said:
May I ask, when you went from 9.0.17 to 10.3, did you use Oxygen updater? I have converted twice now from A9 to A10 and both times had to msmtool back to A9.17 due to various issues. I would like to update to A10, but don't want to have an issue and have to re-wipe everything and go through the ordeal of unlocking bootloader again as well as copying all my files back to my phone and setting things back up.
Did you have any issues with your upgrade or was it a seemless experience? I realize there is Netflix and google play (I do use Netflix but no Gpay).
If it worked good for you I may consider going to 10.0.3 from 9.0.17 in the next day or so. I realize the upgrading is all subjective, just curious
Click to expand...
Click to collapse
Worked well for me using oxygen updater and local upgrade option. No wipe or data loss for me. I am not root and my bootloader is locked. I did not see any issues with a10 apart Google certification that will be fixed when TMobile release a10 for this device
Sent from my [device_name] using XDA-Developers Legacy app
polzovotel said:
Worked well for me using oxygen updater and local upgrade option. No wipe or data loss for me. I am not root and my bootloader is locked. I did not see any issues with a10 apart Google certification that will be fixed when TMobile release a10 for this device
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Gotcha, perhaps I will wait then. I am unlocked bootloader with magisk and twrp. Thanks for the reply.
ozzmanj1 said:
May I ask, when you went from 9.0.17 to 10.3, did you use Oxygen updater? I have converted twice now from A9 to A10 and both times had to msmtool back to A9.17 due to various issues. I would like to update to A10, but don't want to have an issue and have to re-wipe everything and go through the ordeal of unlocking bootloader again as well as copying all my files back to my phone and setting things back up.
Did you have any issues with your upgrade or was it a seemless experience? I realize there is Netflix and google play (I do use Netflix but no Gpay).
If it worked good for you I may consider going to 10.0.3 from 9.0.17 in the next day or so. I realize the upgrading is all subjective, just curious
Click to expand...
Click to collapse
I just updated to the latest 10.0.3 last night. There were no major hiccups and I followed the ultimate guide method 2. There were some Magisk modules that were incompatible such as (OOS Doze) and my sms/MMS with Google messenger stopped working. The messagenr actually resolved itself and is now working and my Netflix works along with Disney plus. I am using the module safetypass to pass safetnet
LuCkyCn said:
I just updated to the latest 10.0.3 last night. There were no major hiccups and I followed the ultimate guide method 2. There were some Magisk modules that were incompatible such as (OOS Doze) and my sms/MMS with Google messenger stopped working. The messagenr actually resolved itself and is now working and my Netflix works along with Disney plus. I am using the module safetypass to pass safetnet
Click to expand...
Click to collapse
Oh, good to know. Thank you. I will look into that ultimate guide method 2. I appreciate the feedback.
Edit: Did you do local upgrade or upgrade from the oxygen update app directly?
ozzmanj1 said:
Oh, good to know. Thank you. I will look into that ultimate guide method 2. I appreciate the feedback.
Edit: Did you do local upgrade or upgrade from the oxygen update app directly?
Click to expand...
Click to collapse
Local update. I didn't lose any data or files. The process was pretty straight forward and i went straight to 10.0.3 too.
Did you root before installing 10.3?
jestyr8 said:
For those of us on converted TMO devices, you can only use full packages. The incremental will fail Everytime.
Click to expand...
Click to collapse
Not true I went from 9. 17 to 10.01 and Incremental to 10.3. With no issues. Your mileage may vary.
I'm on 9.0.17 converted TMobile to international, can I take the 10.3.0 update , I'm understanding I'll most likely lose Google pay which I don't use anything else?
I went from 9.17 converted to International to 10.3, then rooted.
Yes you will lose Google Pay and Play Store Certification.
Hey,
Long time. Rooter (since HTC desire HD) here.
I remember on my older Oneplus phones, installing an beta would stop you passing Safetynet, so banking apps wouldn't work etc. Is this still the case? Can anyone on the 11 betas see if it passes safetynet? I'm not rooted currently!
Anyone?
Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.
mapester said:
Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.
Click to expand...
Click to collapse
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!
manor7777 said:
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!
Click to expand...
Click to collapse
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.
efex said:
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.
Click to expand...
Click to collapse
Ah OK, that makes sense. Most of the OnePlus betas I've installed n the past have been after Google. Released the OS to pixels, and they still failed Safetynet, but I also know Google is constantly changing safetynet stuff so that's why I wondered. Thanks anyway!