yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Well done, and that explains it.

I'm not sure how YouTube streaming works, but It appears from this that some options offered (HD video, etc) depend on device capability (ie. CPU, GPU specs) which are determined using model prop(s).

[MENTION=7280276]ipdev[/MENTION]s recent discovery that it's not only models using Basic Attestation (usually older, with more limited functionality) that will cause a default to Basic, as we had assumed, may interest you. You can actually choose ANY value not matching actual model because, as is now clear, it's simply the mismatch that makes Force Basic function in MHPC work.

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/post83654739

What this means for you is that, if you wish (eg in the event you find other device specific functions broken), manually choosing a later device should 'Force Basic'. You could try Tab S7, and is should work (likely giving even better / more up-to-the-minute device specific functionality, apps etc) as even a later model won't match.

Hope it helps, PW
[Magisk] bartleby999:
I though it was blocking anything over 480p on some videos, some videos were showing up as 1080p - it turns out that it was actually blocking were all HDR videos. That was certainly the confusing aspect as I didn't know they were HDR, just that they should be 1080p.

So yeah I'm guessing at very least YouTube uses your props to check your model is capable of HDR.

Anyway, what you've added certainly does help, I'll keep that in mind for the future - So Thanks.
[Magisk] Displax:
Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.21.0.QFQMIXM:user/release-keys__2020-09-05
[Magisk] zgfg:
On Xiaomi Mi 9T, MIUI 12 eea, Android 10, even with a gibberish like ro.product.model = "undefined", YT Vanced root 15.38.35, playing 8K HDR 10+ videos, by default in 1060p
[Magisk] bartleby999:
I don't know what to say man. I'm running Vanced too, Android 9, TabS6 - Having the Props set to SM-A300FU meant no HDR. HDR was available without it and available with S5e. Come up with your own conclusion? :confused:
[Magisk] pndwal:
You are changing only that one prop only, right? Whereas MHPC Force Basic changes all model props.

This may be another way to get back HD YouTube, etc.

I think it doesn't work on all devices, but you could use MagiskHide Props Config to change just ro.product.model prop (to anything, "unidentified_flying_object if you like") instead of using Force Basic function (which changes several model props), to see if this is all you need to 'force' Basic Attestation.

If it does, likely you will also have HD in YouTube as this seems to be looking at a DIFFERENT model prop to determine device capability, and this being unchanged, YouTube will be seeing your actual model.

Also, if that works, I'd still be using a real model for the changed prop, not just 'unidentified' etc, and I'd now be making that a newer device from the same OEM and series (as discussed already) in order for apps that look at this prop to have the best chance to work. PW
[Magisk] Didgeridoohan:
[MENTION=6304759]bartleby999[/MENTION] If you're going to be testing this, I would also be curious what happens if you use the "Custom value" option for the "Force BASIC key attestation" feature and add a nonsense value.
[Magisk] Didgeridoohan:
[MENTION=11129403]Mirardt[/MENTION] It is perfectly possible that you can't pass CTS on that particular firmware, no matter what you do. Getting help from someone that has the device and know more about it would be ideal though...

If you really do need to pass CTS I guess you have nothing to loose by trying different ROMs (if available). If the ROM you've linked comes with EdXposed preinstalled that would be unfortunate (why would they do that?). You sure it is though, since in that translation I only see a (broken) download link to EdXposed.
[Magisk] zgfg:
Yes, only that one and from the beginning (from the time of the fist HardawareOff and experimenting with its system.prop file)

For my Mi 9T it was enough and before MHPC was extended with, couple of other Xiaomi stock firmware users confirmed for other Mi 9 line models that it was enough

However, since MHCP was extended, it was easier to advice people to read about and use there

Also, now when G relaxed with Hardware attest, it passes without forcing Basic on some phones, hence it's hard to make conclusions
[Magisk] Mirardt:
Oh ok ... I don't think there is anybody in the english speaking community that has the device and tried out a bunch of stuff with it.

I'm not sure. I think I'm just gonna try it out because their seems to not be another out.

Thanks!
[Magisk] zgfg:
VoWiFi is not related to SafetyNet.

You mean, like VoLTE, using your SIM operator's service but calling over WiFi, not over LTE?

It requires some settings for the operators, if this phone was released only for China, it might be missing.

There might be some props you need to add/redefine - you could use MHCP but you would need to find out which ones.

By Magisk overlay you could probably add whatever is missing for, but the hard part would be to find what ☹️
[Magisk] bartleby999:
Ok. So I used "Force BASIC key Attestation" and chose custom value and set to "Unidentied Flying Object" rebooted and YouTube still allowed 1080p at 60hz. And CTS still passed.

I also tried on the SM-T870 which is the TabS7, which also allowed YouTube 1080p at 60hz & CTS passed.

Here's where things got strange though. To ensure YouTube wasn't still loading data from the last device, I loaded the original value that gave me issues "A300FU" and YouTube only returned 480p options on the original video that I had noticed the problems on so I then loaded a video which only has HDR content and low and behold it returned all options from 360pHDR all the way to 2160pHDR. So, it wasn't blocking HDR as I originally thought, what it was actually blocking was 720p60 & 1080p60 (as you can see in the added pics) what this means, I've no idea - Other than you lose certain quality options by picking an older device.
[Magisk] bartleby999:
Ok. I was going to give this a try also out of curiosity but I don't seem to have that option.

For now, I've used Force Basic to change to SM-T870 (Tab S7) which is likely to be closest to my device (Tab S6) and everything is working fine. CTS is passed and YouTube is showing all available options.
[Magisk] zgfg:
Can you please give a YT link for a HDR video with 2160pHDR - I always see up to 1060pHDR (no matter how I experimented with ro.product.model)
[Magisk] bartleby999:
Sure. This is the video from the image I supplied. It only has HDR content and goes upto 2160p60HDR

https://youtu.be/LXb3EKWsInQ

Oh, also it may be worth mentioning that I'm using Vanced with Max Resolution toggles "On" and that's the only way 2160p will show up on that video.
[Magisk] Didgeridoohan:
That you would have to do with the "Add/edit custom props" option in the main menu.
[Magisk] Mirardt:
Oh man. Do you know anybody who would be able to find out or assist me in finding out?

I mean its nice to know that there is a way ^^
[Magisk] bartleby999:
Ok. I'm pretty new to all this, so maybe I shouldn't be adding custom props? I mean, are there any repercussions I should be aware of?

I have TWRP installed, so reinstalling a backup wouldn't be a problem in case of a bootloop - That's about the extent of my knowledge at present though.
[Magisk] Mirardt:
After hours of trying to handle Alipay and WeChat I finally managed to buy this ROM. Wish me luck, I'm gonna report if it helps with SafetyNet and other issues later!
[Magisk] zgfg:
Sorry, I can't find where should be the Max Resolution On - can you pls post a screenshot with the setting

For Costarica, I can see 2160p in browser (?) but 1080p60 HDR max in YT Vanced
[Magisk] bartleby999:
Setting/Vanced settings/Video Settings - Then just Toggle On.

Screenshot was on that last post.
[Magisk] bartleby999:
Ok decided to just go ahead and try. Because, what's the worst that can happen right. ?

So, I disabled Force Basic, rebooted and then added ro.product.model as custom prop & set it to SM-T870 - YouTube continues to show all available resolution options and SafetyNet passes using Basic.

::Edit:: Changed it again to SM-T970 (Tab S7+) or Netflix doesn't allow you to play HDR.
[Magisk] garylawwd:
Check your widevine level and make sure it is l1. If not then hd content from netflix, Disney+ etc won't be available
[Magisk] zgfg:
No Settings/Vanced Settings on my phone, and cannot find in Vanced Manager or YT Vanced such option, don't know where else could be, but never mind ?
[Magisk] bartleby999:
Yeah, I checked Widevine before changing again and it was L1 - HD content has no trouble, but Netflix doesn't recognise standard TabS7 as HDR compliant, it does however recognise the TABS7+ so switching to that enabled HDR again.

Not in your phone, in YouTube Vanced.

My bad though. I forgot you may need to enable "Vanced Hidden Menu Mode" by going to Vanced Settings and tapping on About ten times.
[Magisk] zgfg:
Ok, thans, got 2160p60HDR (within my screen resolution 1080x2340)
[Magisk] JaboJG:
Have you tried this module for Magisk? https://xdaforums.com/apps/magisk/module-social-media-cache-advanced-t3799155

It's called MultiFunctionPlus, it has the Device Spoofing Tool embedded in it which looks promising for fixing SafetyNet here.
[Magisk] Mirardt:
Hey Jabo, nope I haven't but I will, restoring the old ROM in twrp right now. Nice to have you here, because you actually have the device. BTW, does your voLTE and Wifi Calling work?

Oh man - the module you linked isn't compatible with Magisk since version 19 or so ... i was kinda hyped it might work. Hmm .....

Oh yeah I flashed the chinese custom ROM and there was no english language setting ... so translating was annoying. It allowed tons of functions and customization that is really cool, but couldn't help at all with Safety Net or Wifi Calling. Also I think it needs Magisk v. 21 and the Magisk Manager bugs out after installing it.

Jabo, are you planning on messing around with your phone and try to code your way out of it? Or will you wait for somebody to fix it?
[Magisk] ipdev:
--

First I thought it was a custom rom substituting a non-certified print with a certified one.

- Both are certified prints.

Then I thought maybe some sort of odd combined build?

- Checked LineageOS and the two devices do not appear to be combined builds.

ginkgo - begonia

I very well could have missed something when looking though. :o

Any roads...

--

Some updates.

Since I am running the Global version on Poco F2 Pro, I had to adjust the EEA print since I did not install it.

I pulled the system build.prop out of the update.

Redmi K30 Pro and Poco F2 Pro are shared/combined builds.

The update/install adjusts the values to the device used.

Poco F2 Pro EEA (European)

Redmi Note 8 Pro (Global)

Xiaomi Poco F1 (Global)

Xiaomi Redmi Note 8 (Global)

Cheers all. :cowboy:
[Magisk] sielhadi:
Hi I've galaxy s20 ultra and i edit the props to s20 ultra but i can't bypass cts
[Magisk] Didgeridoohan:
If your device is using hardware backed key attestation, and you're using the "Force BASIC key attestation" feature of the module to try to pass CTS you cannot pick the same device as the one you have. You need to use the default setting or pick a different device from your own (you should be able to pick a very similar device, as long as it's not the exact same model as your own).

For the device fingerprint you can pick your own device (that's even the recommended way to go).

If you're not using "Force BASIC key attestation", try enabling it...
[Magisk] pndwal:
Ok, so seems only changing this prop does achieve Basic Attestation and doesn't affect YouTube (Thanks [MENTION=7786725]zgfg[/MENTION]) as that's looking at alternative model prop(s).

However, other apps like Netflix, are clearly looking at this prop, so using a very late device model can fix this for you (Thanks [MENTION=7280276]ipdev[/MENTION]).

This may be the best solution for you, but not really much different to using Force Basic w/ Tab S7+ since you also need Netflix.

Many thanks for reporting / trialing that for us! PW
[Magisk] Didgeridoohan:
If you wanna try spoofing devices you can also use the "Device simulation" feature of this module. It's basically the same as the one linked (IIRC, haven't looked at that one in a while).
[Magisk] pndwal:
Bit OT here, but in case you're still searching, these are disabled by default on Xiaomi devices it seems, but can usually be enabled simply by running these codes in Phone dialer:

VoLTE *#*#86583#*#*

VoWiFi/WLAN *#*#869434#*#*

These disable 'carrier checks', and toggles should show in settings after that, as well as VoLTE symbol in header items. Simply running code again reverts.

Worked for me on Redmi 6, MiPad 4 LTE, Redmi Note 8T. :good: PW
[Magisk] Mirardt:
Oh interesting. Yeah I tried that one pretty early in the process, but unfortunately my phone bricked so I just didnt think about it anymore. I think in the manual you wrote something like "it wouldnt help passing Safety Net". Do you think in my case it could help?

Hey there, thank you very much for helping! Unfortunately, I did disable carrier check already and it didnt make it work. :/

zgfg suggested there might be just a few props that need to be changed but it wouldnt be easy to find them.
[Magisk] Didgeridoohan:
I doubt it, but since something similar was suggested I thought I'd mention it (and I have been known to be wrong more than once :D).
[Magisk] bartleby999:
Yeah, no problem - I'm glad to contribute.
[Magisk] zgfg:
Hope you all the best to put it back to work

If using MiFlash (PC), be careful, look to the bottom-right and make sure you switch from Clean all and lock to Clean all (something like that, writing from my heart) before you start flashing! Otherwise, if anything goes wrong, your Bootloader will be locked, you would not be able to boot to MIUI and you would need a paid assistance from somebody with the authorized EDL support
[Magisk] westeight:
Thank you - my S20 Ultra is now passing:
[Magisk] sielhadi:
What did you do please
[Magisk] westeight:
Just changed the basic key attestation to the Note 20 Ultra... :cowboy:
[Magisk] Mirardt:
[MENTION=7786725]zgfg[/MENTION]

Thanks, but that was like a week ago. I could just boot into twrp and restore a previous version.

Maybe thats not called "bricking a phone" though, idk. It just couldn't load the system.
[Magisk] sielhadi:
It works thanks

---------- Post added at 09:47 PM ---------- Previous post was at 09:46 PM ----------

Thaaaaak you
[Magisk] hoang_dang2809:
Please help me bypass CTS for Samsung A70 running stock with September patch rooted with Magisk. Thank you
[Magisk] Didgeridoohan:
Start by taking a look in the docs:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf#not-passing-safetynet

There's also a wealth of information on how to pass SafetyNet available here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

If you still can't get CTS to pass after reviewing all that information, come back and let us know what you've tried and what the results have been.
[Magisk] hoang_dang2809:
^

Okay, thank you. I read it but im not understand. I have just install MagiskHide Props and dont know what to do next :(
[Magisk] Didgeridoohan:
From the first link I posted you should have been able to surmise that you likely need to enable "Force BASIC key attestation". As long as you've also enabled MagiskHide and it's working, and don't have any modifications that MagiskHide cannot hide, you should hopefully pass CTS.

If you're wondering how to actually use and set up the module, that's also covered in the docs:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf#usage
[Magisk] Some_Random_Username:
Hello, here are latest OnePlus 8-series fingerprints extracted from "stable" OxygenOS 11 that started to roll out yesterday.

OnePlus 8 IN2011 OnePlus/OnePlus8_IND/OnePlus8:11/RP1A.201005.001/2009301800:user/release-keys__2020-09-01

OnePlus 8 IN2013 OnePlus/OnePlus8_EEA/OnePlus8:11/RP1A.201005.001/2009301800:user/release-keys__2020-09-01

OnePlus 8 IN2015 OnePlus/OnePlus8/OnePlus8:11/RP1A.201005.001/2010031600:user/release-keys__2020-09-01

OnePlus 8 Pro IN2021 OnePlus/OnePlus8Pro_IND/OnePlus8Pro:11/RP1A.201005.001/2009301800:user/release-keys__2020-09-01

OnePlus 8 Pro IN2023 OnePlus/OnePlus8Pro_EEA/OnePlus8Pro:11/RP1A.201005.001/2009301800:user/release-keys__2020-09-01

OnePlus 8 Pro IN2025 OnePlus/OnePlus8Pro/OnePlus8Pro:11/RP1A.201005.001/2010031600:user/release-keys__2020-09-01

Note that "stable" is between brackets, because there are already reports of several issues such as stock SMS app crashing when launched, popular third party applications (Snapchat, Messenger) not performing well and FPS drops in some games compared to OOS 10. That makes me believe that it is a release rushed for the sake of press, just like 7-series and Android 10 last year.
[Magisk] hotelmariofan:
Using the OnePlus 8 Pro on 10.5.13.

In order to get call screening via the Google Phone dialer, I must simulate a Pixel device with MagiskHide Props Config. So, in doing that, I simulate everything except "ro.build.display.id". Everything works, except for brightness. I cannot change it, and it is seemingly set to the absolute lowest setting.

Oddly, the brightness on the lock screen is normal, and responds appropriate to changes in the menu bar. It's only once I've unlocked the device that brightness is stuck at the lowest (though the menu bar allows me to change it as normal, it just doesn't actually do anything).

Any suggestions for what I might be able to do to maintain the simulated settings but maintain control of the brightness settings?
[Magisk] CookieRG:
Hello, can someone tell me if it works on mi 9t miui 12 now? I had root and installed magisk in July but I hadn't been able to remove the "cts false" so I came back in stock.

Is it working now? If yes, which method?

Thanks you
[Magisk] Didgeridoohan:
Don't know. Changing prop values can have all kinds of interesting effects... Do you need to simulate all those props to get the call screening working? Have you tried changing just one prop at a time to find if the issue is connected with a certain prop or combination of props?
[Magisk] Didgeridoohan:
Maybe it's the hardware backed key attestation that's causing you issues. Take a look in the docs for info on what features of the module might help: https://github.com/Magisk-Modules-R...f/blob/master/README.md#not-passing-safetynet
[Magisk] Spartacus500:
Hello, apparently this module can hide OEM unlock ? How to do it ?

My device : Samsung S7 9.0 Pie
[Magisk] Didgeridoohan:
It can? If so I'd guess you'd have to use "Add/edit custom props" to change the corresponding prop value.

Don't know which one... Maybe ro.oem_unlock_supported or sys.oem_unlock_allowed.

I seem to remember that might just be the same thing as flipping the switch in Developer options though, rather than "hiding it"... Please let us know what you find.
[Magisk] Mirardt:
Short Update: I tried again to simulate a device, this time the Google Pixel 4XL. It didn't brick but unfortunately it didn't solve the issue either.

One thing I noticed, though, is that the evalType is always "BASIC", even if I don't activate it in props settings. Does that maybe have any meaning?
[Magisk] Didgeridoohan:
You mean when you have the Pixel 4 XL simulation active? You'll get basic attestation if you simulate ro.product.model (which is what the "Force BASIC key attestation" option does), so that's likely why.
[Magisk] Mirardt:
Nope also when I have no simulation at all active.
[Magisk] Didgeridoohan:
That just means that you don't have to spoof the device model to pass CTS... Yay. If could pass CTS, that is... :(

Google likely tinkerers with this stuff all the time, so don't be surprised if things change from one day to the other.
[Magisk] Spartacus500:
ro.oem_unlock_supported = This entry shows a slider where you can enable or disable OEM unlock. 0 = hides OEM functions from the menu.

sys.oem_unlock_allowed = This function is responsible for OEM unlocked, which is 1 = OEM unlocked, 0 = OEM locked.

I found information in the link below that one user wrote that it is possible using the magisk hide profs module, but he did not give how to do it, I also have no idea how to do it :confused:

https://github.com/topjohnwu/Magisk/issues/1656
[Magisk] zgfg:
You start MHPC by props in Terminal.

Look into the options, you need the option for custom prop - I think it was 5.

So you type 5, etc, and you just follow the conversation with MHCP - when it asks you for the prop name you type that sys.oem_unlock_allowed, when it asks you for the value, you type in 0 or 1.

At the end you choose options to save and reboot - or you just play with but at the end choose to cancel, not to save

But I woild not change, specially sys.oem_unlock_allowed (the last post in your linked issue also says that user bricked his phone)
[Magisk] Mirardt:
There was a post of a guy about a ROM for the K30U, but the real interesting thing is that he said that his device passed SafetyNet when directly flashing GApps Pico and that it wouldn't pass with any installer.

But that would mean I need to resize and format the system partition, right, and as I read this is pretty dangerous and the device might brick.

With your experience of passing SafetyNet, would you say there might be a reasonable chance that it'll work and it's worth a try? (:

[MENTION=7786725]zgfg[/MENTION] would be glad to read you opinion, too <3
[Magisk] Didgeridoohan:
[MENTION=11129403]Mirardt[/MENTION] Looks like you have some kind of answer there. Pico GApps, and nothing else. Would explain your predicament. But if the system partition is full that would cause problems, yes.

Instead of reformatting to a new size (which probably could brick the device if you're unlucky/not careful), why not just remove some system apps that you don't need? That would free up space to install GApps (and Pico is quite small so you probably wouldn't need to free up too much extra space).
[Magisk] Spartacus500:
Yes, I read the last post on my link. There is also some risk ... :(
[Magisk] Some_Random_Username:
OnePlus 6-series updated fingerprints from OOS 10.3.6:

OnePlus/OnePlus6/OnePlus6:10/QKQ1.190716.003/2010042216:user/release-keys__2020-09-01

OnePlus/OnePlus6T/OnePlus6T:10/QKQ1.190716.003/2010042216:user/release-keys__2020-09-01
[Magisk] Mirardt:
NICE! I'm definitely gonna try it then! :D

Any app you can recommend to do that?
[Magisk] Mirardt:
IT WORKS!!!!!

Kinda ...

But i did FINALLY pass SafetyNet. I was also able to set up my Card in Google Pay, but the only problem is that it "doesn't meet security requirements". But I have a feeling that this is fixable, [MENTION=7786725]zgfg[/MENTION] postet a link to the fix at some point.

I'm gonna keep you up to date already a HUGE HUGE Thank You to all of you who helped! <3
[Magisk] zgfg:
Check if Playstore shows Device is certified. If not:

-Airplane on

-Settings/Apps, Show system apps

-Sarch for Google Play app, Google Play Services, Google Services Framework and Clean Data (for some only Clean cache is available)

- reboot, Airplane off and give a time to Playstore to sync

Probably you will further need OP instructions from GPay thread (I don't use GPay, hence never really tested)

Btw, I was just about to answer you to the previous posts (was busy last two days, experimenting with other things), but I'm glad that you made it with the help from [MENTION=4667597]Didgeridoohan[/MENTION]

If I recall, VoLTE/VoWiFi remained, or the secret code worked?

Unfortunately, there is no subforum for your device, but IMO you should later open a thread with all the mods you made, that others can find and get a help from - maybe you also describe then where did you order the phone (must be a good value for money - when things get fixed ?)