yashsingh1/xdaforums huggingface dataset:
[Magisk] salmanghiyas:
thanks bro, it worked, just one last thing, now that I have created one another user there is an option that says "Allow phone calls and sms" which is disabled and I cannot enable it, I doubt there should be another prop for that, can u help in this ?
[Magisk] Didgeridoohan:
Great!

But, I have no idea about that option... Check your device's forum, or search the web/XDA.
[Magisk] zgfg:
Simply test and you'll see yourself.

If not working, you can easily disable the changes you made by MHPC, and everything will be again like before you installed the MHPC module

Please read the OP post #1 and MHPC Guide from Github for how to use the MHPC module (everything is well documented)
[Magisk] FivEawE:
Xiaomi Redmi Note 8 Pro (begonia) Europe A10

[ro.product.manufacturer]: [Xiaomi]
[ro.product.model]: [Redmi Note 8 Pro]
[ro.build.fingerprint]: [Redmi/begonia_eea/begonia:10/QP1A.190711.020/V12.0.3.0.QGGEUXM:user/release-keys]
[ro.build.version.security_patch]: [2020-11-01]
[Magisk] Drahy:
Hello I changed some props and it worked but now ir seems to stopped working. I tried to change the props closer to my model number (Samsung A600FN) but i lost all props now and anything I do has no effect. Apps are not "updated" during boot up like before. Can I force the update during startup somehow? Thank you.
[Magisk] Didgeridoohan:
I'm going to need more details than that... What do you mean "it seem to stopped working"? Likewise with "lost all props" and "apps are not updated during boot". None of that describe normal situations, so you need to help me help you...

And to do that it's always a good idea to include the module logs when reporting about problems:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com
[Magisk] Drahy:
Hello,

Everytime i changed some props the phone updated all apps in my phone like "updating 23 from 300 apps" during startup. It was ok, cts profile passed but galaxy apps offered strange apps for different model and generated errors. I tried to reverse it all and start over with more closer model for fingerprints and it went ok... All was put to default. But now when I change anything or even previous settings I had befire, it doesnt do anything, no cts passing... Nothing... device just rrestartingwith no updates of the apps at the startup of the device. In the props menu it looks ok and green but the props didnt really changed it seems. Do I have to do something different to make the changes really apply? Is there such option?

Thank you.
[Magisk] Didgeridoohan:
@Drahy Like I said, it's always a good idea to include logs. I'm not gonna be able to figure out anything without those.
[Magisk] Drahy:
Here it is.
[Magisk] Didgeridoohan:
You might want to try attaching that again...
[Magisk] Drahy:
Ok next try...
[Magisk] Didgeridoohan:
Seems like the new forum doesn't like files with the gz extension...

Anyway, I do not see anything wrong in the logs. You've set the Samsung Galaxy A7 2018, both for the fingerprint and for forcing basic attestation. And the corresponding props are set accordingly.

If you've got issues, it doesn't seem like they're from the module.

You could always try resetting everything (for the module). There's an option for that in the main menu when running the props command.
[Magisk] Drahy:
Yes it seems add on Ainur Narsil from Magisk somehow disabled functionality of this mod. When removed all was applied correctly during startup. Anyway there should be some kind of additional check if all was really applied correctly during reboot?
[Magisk] Didgeridoohan:
There are several checks in place to make sure everything is running as it should. In this case though, everything did run as expected and all props you had configured in the module had in fact been applied correctly.

Glad to hear you figured it out. (y)
[Magisk] Drahy:
The problem is that the settings were NOT applied correctly even though the module said they were. After removal of another modul the changes were applied correctly. That was the additional check I was writing about...
[Magisk] Didgeridoohan:
Then, for my understanding and for further troubleshooting, I would appreciate if you let me know more about how the props weren't applied and how you checked/confirmed this.

Because, when saving the logs the module checks and saves all the current props, and they all corresponded to the values you had set in the module.
[Magisk] oursgentil:
It is possible to create a fingerprint with these informations ?

ro.system.build.date=Fri Nov 13 12:11:53 KST 2020

ro.system.build.date.utc=1605237113

ro.system.build.fingerprint=samsung/beyond0ltexx/beyond0:10/QP1A.190711.020/G970FXXS9DTK9:user/release-keys

ro.system.build.id=QP1A.190711.020

ro.system.build.tags=release-keys

ro.system.build.type=user

ro.system.build.version.incremental=G970FXXS9DTK9

ro.system.build.version.release=10

ro.system.build.version.sdk=29

ro.product.system.brand=samsung

ro.product.system.manufacturer=samsung

ro.product.system.model=SM-G970F

ro.product.system.name=beyond0ltexx

ro.product.system.device=beyond0

ro.build.id=QP1A.190711.020

ro.build.display.id=QP1A.190711.020.G970FXXS9DTK9

ro.build.keys=test-keys

ro.build.display_build_number=true

ro.build.version.incremental=G970FXXS9DTK9

ro.build.version.sdk=29

ro.build.version.preview_sdk=0

ro.build.version.preview_sdk_fingerprint=REL

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=10

ro.build.version.security_patch=2020-12-01

ro.build.version.base_os=samsung/beyond0ltexx/beyond0:10/QP1A.190711.020/G970FXXU9DTJA:user/release-keys

ro.build.version.security_index=1

ro.build.version.min_supported_target_sdk=23

ro.build.date=Fri Nov 13 12:11:53 KST 2020

ro.build.date.utc=1605237113

ro.build.type=user

ro.build.user=dpi

ro.build.host=SWDH7005

ro.build.tags=release-keys

ro.build.flavor=beyond0ltexx-user
[Magisk] zgfg:
If you need to change more props than just those that bare the name fingerprint (or if you have new fingerprints not yet updated to MHPC) you can always use Add/Edit Custom prop and Delete prop options (5 and 6) in MHPC and freely add/delete/edit any prop you want
[Magisk] Didgeridoohan:
@oursgentil Yes, that's more than what I need to add the device to the fingerprints list. I'll test it and if it passes CTS I'll add it in the next list update.
[Magisk] GtrCraft:
Update for POCO X3:

(Europe):

fingerprint: POCO/surya_eea/surya:10/QKQ1.200512.002/V12.0.7.0.QJGEUXM:user/release-keys

security patch: 2020-11-01

(Global):

fingerprint: POCO/surya_global/surya:10/QKQ1.200512.002/V12.0.7.0.QJGMIXM:user/release-keys

security patch: 2020-11-01
[Magisk] dingolino:
Hi, just started to read the documentation about the tool. What I was wondering is whether there is the option to safe/restore the fingerprint of the device before using one from the list ...

Best regards,

dingolino
[Magisk] Didgeridoohan:
Nothing is overwritten when using the module, the prop change is completely systemless. To go back to the original fingerprint you just use the reset option under the "Edit device fingerprint" menu or from the main menu.
[Magisk] user00123:
Hello, thanks for creating the tool! I have my device rooted, and I changed the fingerprint to OnePlus 6 Android version 10. The reason is because I want to use a specific feature in Gboard which is only available in select flagship phones. I know for sure that the feature is available in OnePlus 6, since I have tested it with an actual device. My understanding is that by changing the device fingerprint Gboard should see the device as oneplus 6 and enable the feature.

But it isn't working. The safety net check is passed.

Any ideas how I can fix this? Thank you!
[Magisk] Didgeridoohan:
It's very likely that more is needed than just changing the fingerprint. My first guess it's that you'd need to change the model rather then the fingerprint. You could activate "Deceive simulation" and try enabling the model prop there. If that still doesn't work you can keep trying with different props.
[Magisk] AyHenry:
Please where is this file located? Because am facing the same issue. Thanks
[Magisk] user00123:
Just tried it out. It's working now!

Many thanks :)
[Magisk] Didgeridoohan:
If you have the same issue, it's in /cache (or possibly /data/cache). But note the leading dot in the file name. That means it's a hidden file and depending on your file explorer you might have to enable an option to view hidden files.
[Magisk] Didgeridoohan:
Which prop was it that made it work? If it was the model, you could try resetting the fingerprint to your original and instead use "Force BASIC key attestation" and pick the device you want from the list. That will only change the model props and nothing else.
[Magisk] user00123:
I got lazy and enabled all the props. Not sure if it can cause any harm.

I will try to do the props one by one later, and get back.
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ1A.210105.003/7005429:user/release-keys__2021-01-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ1A.210105.003/7005429:user/release-keys__2021-01-05
Pixel 3a=google/sargo/sargo:11/RQ1A.210105.002/6985033:user/release-keys__2021-01-05
Pixel 3a XL=google/bonito/bonito:11/RQ1A.210105.002/6985033:user/release-keys__2021-01-05
Pixel 4=google/flame/flame:11/RQ1A.210105.003/7005429:user/release-keys__2021-01-05
Pixel 4 XL=google/coral/coral:11/RQ1A.210105.003/7005429:user/release-keys__2021-01-05
Pixel 4a=google/sunfish/sunfish:11/RQ1A.210105.002/6985033:user/release-keys__2021-01-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ1A.210105.003/7005429:user/release-keys__2021-01-05
Pixel 5=google/redfin/redfin:11/RQ1A.210105.003/7005429:user/release-keys__2021-01-05

Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.19.0.QDIMIXM:user/release-keys__2020-12-01

Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.16.0.QDLMIXM:user/release-keys__2020-12-01
[Magisk] Displax:
Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:10/QKQ1.190910.002/V11.0.26.0.QFQMIXM:user/release-keys__2020-12-05
[Magisk] Max128:
Hello can you please add the Samsung tab s6 lite ( SM-P610 model ) because i can not pass the ctsprofile with magisk. Thanks
[Magisk] Didgeridoohan:
I'd love to:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] Max128:
This is correct? will it help you add it?

samsung/gta4xlwifixx/gta4xlwifi:10/QP1A.190711.020/P610XXU2BTK2:user/release-keys
[Magisk] Didgeridoohan:
Looks ok, but I would have to test it to make sure (happens whenever I have the time for it). But before I can do anything I need the security patch date as well.
[Magisk] Max128:
1 december 2020
[Magisk] Some_Random_Username:
Hi folks, below are latest fingerprints currently available for OnePlus devices.

As always, OnePlus/OnePlus7/ fingerprint is for GM1901 and GM1905 / OnePlus/OnePlus7Pro/ fingerprint is for GM1911 and GM1917 / OnePlus/OnePlus7T/ fingerprint is for HD1901 and HD1905 / OnePlus/OnePlus7TPro/ fingerprint is for HD1911 and HD1917.

Also note the following: the new OnePlus/OnePlusN10/ fingerprint is for global software. I however don't know for sure model number it is for since device is not officially live yet in USA. Regarding the new OnePlus/OnePlusN100/ fingerprint (also for global software), I tend to believe it is for BE2011 by looking at ro.product.system.model prop (I uploaded full prop at https://github.com/oxygen-updater/build-props/blob/master/opnord-n100/intl/10.5.4.BE81AA.prop ) and as FCC fillings hint at it.

Spoiler content hidden.

Additionally here's an Android 11 fingerprint (extracted from a OnePlus 7T closed beta dump I've been sent) which I haven't tested: OnePlus/OnePlus7T/OnePlus7T:11/RKQ1.201022.002/2012201945:user/release-keys__2020-11-01.

I tend to believe it should pass SafetyNet since device is listed as running Android 11 on Google Play Console.
[Magisk] M1ster1:
First of all, thank you Didgeridoohan for this module that is great and working fine! (y)

I got a Xiaomi note 10 on MIUI 12.

Orangefox as recovery.

Magisk Manager 8.0.4 and Magisk 20.4 are working fine.

The Magisk Manager safety net check shows the basicIntegrity OK but fails CTS and shows "evalType HARDWARE".

So I read the Github tutorial from the first page and I used

"Force BASIC key attestation"

.

It's written : " Do NOT pick your own device, instead try a device that is as close to your actual device as possible. The closer it is to your actual device the less is the likelyhood that things will stop working as a result of the model prop change. "

By default the MagiskHide props advise me to use Mi - 3W, a device from 2013 from the same brand, and with this key attestation, safety net check is a success.

I think that 2 devices from the list given by MagiskHide props are probably closer to mine :

- Xiaomi Mi note 3, a device from 2017 but from the exact same "branch" or "range" because it's a "Note"

- Xiaomi Mi 10, a device from 2020 a bit stronger but pretty close

These two options are good and succeed with a safety net check.

Does it make really a difference here, maybe it doesn't... any hint on that?

Thanks!
[Magisk] Didgeridoohan:
Sounds like you're on top of things and have found options that work for you.

Regarding changing fingerprint vs forcing basic attestation I've tried to cover the different use cases here:

https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1
[Magisk] zgfg:
First hand experience from Mi 9T. I really played a lot here since the beginning of that CTS Hardware eval issue (last year), with MIUI 11 and 12

- You don't even need to use Force BASIC option (that will change you three or so model prop values), you can simply use another MHPC option Edit custom prop, to change only this one:

ro.product.model

- For ro.oroduct.model you can take anything, it will just show you then a different model name under the Settings About and/or All Spec.

E.g. I used davinci (but also 'names' like myModel, unknown or undefined) instead of my proper model name Mi 9T and didn't have any problem

If you are taking a real product name of another model from the same manufacturer, you must make sure that it would be an older model where Google does not enforce Hardware CTS eval

It's not recommend to use model names from another manufacturer (you would then also need to change the prop with manufacturer name)

Better change less number of props, since different software reads different props (if you have stock, certified firmware, you don't need to change device fingerprint). Change only what you need for CTS (ro.product.model should be enough)

PS: I think that GCam apps also read ro.product.model, hence you may affect Google Camera if you use.

But otherwise it should not affect like Netflix (your L1 cert), etc

Not sure if ro.product model is maybe used by YT for the max resolution, but if you use YT Vanced (root) you can enforce the highest resolution anyway

You would even properly receive OTA notifications (for OTA, you must anyway go back to stock boot.img, that would disable Magisk and therefore also all the systemless changes like these props via the MHPC module)
[Magisk] M1ster1:
Sorry, I may have incorrectly ask my question.

I think I understood the difference fingerprint / basic attestation.

To write it simply: as it is not related to fingerprint, in my case choosing the basic attestation from "Xiaomi Mi note 3" or "Xiaomi 10" makes a big difference or not?

The only thing about that that I've read is "Using an actual model value from an old device may also help with keeping OEM specific features working (like the Samsung Galaxy Store). "

And as my device is pretty new, I guess I'm not concerned.
[Magisk] zgfg:
See my answer, given you specifically for MIUI, post #4780 (one before this your last question)
[Magisk] Didgeridoohan:
That was in the early days. Now you just have to pick a model different from your own device, doesn't matter which one...

Unless Google changed something again, of course.
[Magisk] Didgeridoohan:
Yes, just like @zgfg says, the "Force BASIC key attestation" feature changes the ro.product.model prop and the corresponding partition props. Depending on which device you pick, it'll make your device seem to be that model.
[Magisk] M1ster1:
Awesome !

Thank you for your help and your very precise explanation :geek:

Okay, I disabled the Force BASIC option.

I only added the custom prop "ro.product.model" and I put "Mi Note 3" (as it is an older model as you advise). and it's still passing safetynet ! (y)

And in Settings/About/All Specs the name appears as you said : Model : "Mi Note 3".

Not using GCam but I note it just in case I would.

Of course I'll use Vanced, I am rooting for few reasons and Vanced is one of them :)

If i still receive OTA notifications that's good!

In case I don't I guess I can reset my ro.product.model to stock, make the update, and set it back after, right?

About the OTA, I was considering the option given by Orangefox to setup incremental MIUI OTA in OrangeFox Recovery : https://wiki.orangefox.tech/en/guides/ota
[Magisk] bartleby999:
I don't think that is true. I'm using a custom prop set to the Tab S6 LTE version of my device (Tab S6 WIFI) and CTS still passes.

My device : SM-T860

Custom Prop : SM-T865

SafetyNet ✅

From my experimenting, It does. I'd lose all HDR support if I picked a device without HDR capabilities and Vanced wouldn't override that. So, you should pick the device closest to your own.
[Magisk] zgfg:
Good, glad it all worked to you as expected

You can revert MHPC changes through MHPC, or you can simply disable MHPC module in Magisk Manager (when you later re-enable, all previous props changes will be again in effect).

Don't forget to reboot

For OTA I didn't try that option from OF, but I do OTA:

- reflash stock boot and recovery (with stock Boot all systemless changes are disabled, incl. the MHPC module and its props), do OTA and reboot, patch my new boot.img, flash the new patched.img, flash TWRP again (optionally)

When I reboot I have the old modules, props, Vanced YT, AdAway, everything

Alternatively, you can revert stock boot.img but keep TWRP (OF) and flash recovery/zip firmware for OTA, then

the rest as above.

I did that couple of times but once flashing OTA through TWRP trigerred Factory Reset and since then I don't want to give it a try again (to waste time for reinstalling things).

However, it is also possible to install downloaded OTA update through Settings, System update (you must have stock boot and recovery like commented above, and better download full OTA, not the smaller "update from..." zip firmware) - in that case you don't need to wait for OTA notification

OTA COMMENTS FOR MIUI ONLY, for other devices milleage can vary - follow OTA procedures for your phone
[Magisk] zgfg:
The whole purpose of changing product model is to trick Google to not use their list of devices where they force CTS Hardware (that's why you fake it from your original one).

E.g., if I change my Mi 9T to Mi 9T Pro I don't gain anything

I'm not familiar with e.g. Samsung models, for which of them Google will force Hardware or not - if you do have CTS Basic for your choice of product name, then keep with that.

Btw, for Samsung you maybe must really change more than ro.product.model, so use Force Basic option (or experiment yourself with changing props one by one).

It's also Samsung specifics if changing of particular props (therefore Force Basic) may affect (or not) OTA notifications, updates of system apps or similar - it all depends which prop they read for which purpose (hence the changed one can mislead)

For YT, use Vanced YT root (you have Magisk) and you can enforce HDR with the highest resolution, no matter of props
[Magisk] rishnu:
Safety net fails, why? Device Huawei honor 4x, running on custom rom, lineage os
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...nfig/blob/master/README.md#issues-support-etc
[Magisk] crataclysme:
It worked ! Thanks a lot ! I passed the SafetyNet Test :)

I think I know why BusyBox download failed... I've installed your module on an unstable 4G ? That would be good to add a check, for idiots like me ?

Thanks for your awesome work !
[Magisk] Didgeridoohan:
Thank you for the confirmation. I've seen that issue before, but hadn't connected it with a failed Busybox download until I saw your installation log. Currently restructuring a bit and adding a md5 checksum check, so that it won't happen again.
[Magisk] Zep0th:
Previous version was working flawlessly, update stopped working ):

Logs will come when I have time
[Magisk] Didgeridoohan:
Update to v2.3.6

Another bugfix release. Added a md5 checksum check to the download of the internal Busybox. Now there won't have to be any issues from a failed Busybox download...

I also changed the default boot stage for setting the different props (build fingerprint and custom props) to post-fs-data. This change comes from the fact that it takes just a tiny delay in the execution of the boot scripts for the change of the build fingerprint to have no effect. It's simply more reliable in the earlier boot stage. If there are any kind of issues during boot, try changing the boot stage to late_start service instead. Just keep in mind that this might cause setting the build fingerprint to fail.

Changelog

v2.3.6

Added md5 checksum when downloading the internal Busybox.

Changed the default boot stage from late_start service to post-fs-data.

Various fixes and improvements, as usual.
[Magisk] martyfender:
I updated to your latest on one device and had no problems, but on the second Nextbook Ares 8A it has an error downloading the busybox with a supposed good connection.

attached is your module created logs.

--- google.com ping statistics ---

1 packets transmitted, 1 received, 0% packet loss, time 0ms

rtt min/avg/max/mdev = 26.632/26.632/26.632/0.000 ms

08-09-2018 01:00:41 - - Downloading busybox

Connecting to raw.githubusercontent.com (151.101.184.133:443)

wget: note: TLS certificate validation not implemented

wget: clock_gettime(MONOTONIC) failed

08-09-2018 01:00:42 - ! Busybox md5 mismatch!

08-09-2018 01:00:42 - ! No busybox downloaded!

When entering props in the terminal I get: module internal busybox not found

Then despite this the settings load.

EDIT: I copied the busybox binary from the /sbin/.core/img/MagiskHidePropsConfig directory from one tablet to the problem one, changed permissions to 755 and now it launches in the terminal without the busybox missing error.

I did a reinstall over the existing and the install log made no mention of downloading busybox again, I assume, because it was there, this time.
[Magisk] Didgeridoohan:
Hm... The issue isn't the connection, but wget is failing (for some reason).

wget: clock_gettime(MONOTONIC) failed

And that's both with the Magisk internal Busybox (used during module installation in the Manager) and with [MENTION=4544860]osm0sis[/MENTION]' Busybox (that I see you have installed, so the module will use it until the internal Busybox is downloaded).

I took a quick look around, but only found one other report of that particular error (also with [MENTION=4544860]osm0sis[/MENTION]' Busybox).

I have no idea what that could be about. [MENTION=4544860]osm0sis[/MENTION] Need some help here... :D
[Magisk] jenslody:
This looks like a device or wget error.

Do you use syste wget (toybox/toolbox) or do you have a busybox installed ?
[Magisk] osm0sis:
Hmm, that's a new one. Did that start in busybox 1.29.x and/or is it only with certain Android OS version, and/or wget arguments?

Edit: For example, on my OP5T on Oreo 8.1 the following worked fine:

busybox wget -S -T 4 -O /sdcard/hosts https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts