yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Hiding the bootloader is Magisk's job, and as far as I know the type of masking that Safetypatcher does isn't actually doing anything since no apps or services have direct access to /proc/cmdline (the same goes for detecting the written value in build.prop). I'm no Android developer, so I could of course be wrong.

If you want to use Safetypatcher you can just edit the post-fs-data.sh script and replace the Huawei print with your own in the resetprop commands (remember to uncomment the vendor print command). You can also use MagiskHide Props Config by just entering the fingerprint into the module terminal ui or by using the configuration file (https://github.com/Magisk-Modules-R...nfig/blob/master/README.md#configuration-file).

You will also have to add a prop change for the security patch date though, either with resetprop in the script or with MagiskHide Props Config (take a look here for details: https://github.com/Magisk-Modules-R...E.md#matching-the-android-security-patch-date).

I'm going to try to update the fingerprints list in the next couple of days, so I'll make sure to add the Moto G7 Power to it. Thanks
[Magisk] mn1968:
I am interested in changing the volume steps for my alarm, ringtone, and notifications. Using your module I successfully changed my media from 25 to 15 steps. Unfortuanately, there is no prop already entered for me to modify and what I've tried to add doesn't work. I've tried:

ro.config.ringtone_vol_steps=15

ro.config.ring_vol_steps=15

ro.config.notification_vol_steps=15, etc.....

I am hopeful this will work if only I could find the right syntax. I've searched the forums and Google and don't know what else to search for.

Any suggestions?

Thanks!
[Magisk] acras1:
Please, need help. I'm aex maintainer for mi A2 lite. If i use this module with given mi a2 lite build fp, all work fine. But when i want to use that fp compiled in rom - it doesn't work.

Rom is using that code to set fp

# Device identifier. This must come after all inclusions
PRODUCT_DEVICE := daisy
PRODUCT_NAME := aosp_daisy
BOARD_VENDOR := Xiaomi
PRODUCT_BRAND := Xiaomi
PRODUCT_MODEL := Mi A2 Lite
PRODUCT_MANUFACTURER := Xiaomi
TARGET_VENDOR := Xiaomi

PRODUCT_GMS_CLIENTID_BASE := android-xiaomi

PRODUCT_BUILD_PROP_OVERRIDES += \
TARGET_DEVICE="daisy" \
PRODUCT_NAME="daisy_sprout" \
PRIVATE_BUILD_DESC="daisy-user 9 PKQ1.180917.001 V10.0.1.0.PDLMIFJ release-keys"

# Set BUILD_FINGERPRINT variable to be picked up by both system and vendor build.prop
BUILD_FINGERPRINT := "xiaomi/daisy/daisy_sprout:9/PKQ1.180917.001/V10.0.1.0.PDLMIFJ:user/release-keys"

Ain't it enough? Module does somthing else?
[Magisk] Didgeridoohan:
The only prop values for changing volume steps that I know of are these:

ro.config.vc_call_vol_steps
ro.config.media_vol_steps

If you need other modifications you might have more luck with Xposed (or EdXposed) and the Gravitybox module (or other applicable Xposed modules, I don't use it so I'm not very well versed in what is available).

Edit: I did some quick digging and found these two as well:

ro.config.alarm_vol_steps
ro.config.system_vol_steps

No idea if they'll actually do anything for you.
[Magisk] Didgeridoohan:
You'll also have to match the security patch date (ro.build.version.security_patch). For that particular fingerprint that would be 2018-11-05.
[Magisk] acras1:
I have this in boardconfig

VENDOR_SECURITY_PATCH := 2019-11-05

I should change it to 2018-11-05?
[Magisk] Didgeridoohan:
I don't know how building a ROM works, so I can't answer that partiular question. But the ro.build.version.security_patch prop needs to be set to the date that matches the used fingerprint (regardless of the actual patch).
[Magisk] acras1:
But when i use in rom fp from Pixel (google/walleye/walleye:8.1.0/OPM1.171019.011/4448085:user/release-keys) - it works without module. Strange
[Magisk] Didgeridoohan:
Not strange at all. That fingerprint is old enough to not need to match the security patch date.

Edit: if you take a look in the module fingerprints list you'll see that some prints have the date appended to them and some don't (that's how I keep track of the dates in the module):

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh
[Magisk] acras1:
So I need stock for before May 2018?
[Magisk] Didgeridoohan:
From what I've gathered it actually needs to be a build before March 16th 2018. A fingerprint from a build after that would have to match the patch date as well.
[Magisk] mn1968:
These worked! Thanks. It's just a matter of playing around and finding the right syntax for the ringtones & notifications now. Any idea where I might even begin to look for this?

Also, can this module be used to make volume buttons skip media tracks? Or unlink ringtone & notification like gravity box? Or is that beyond the scope of this module?
[Magisk] Didgeridoohan:
That's great to hear. I got those two extra ones from the Android source code (https://android.googlesource.com/pl...om/android/server/audio/AudioService.java#624), and there where no other props mentioned...

This module only works on prop values, so anything that can be altered through props can be modified, but that's it. If you need more than that you'll need to edit the system somehow, either directly or through tools like Xposed.
[Magisk] Didgeridoohan:
Update to v5.1.1-v72

Small update, mainly to conform with the new module installation setup and to add/update device fingerprints.

As always, the module wouldn't be the same without the prints submitted to you guys, and this time around I'm sending a huge thank you to [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=8961188]Micdu70[/MENTION], [MENTION=5886033]robi10101298[/MENTION], [MENTION=4111660]dlhxr[/MENTION] and [MENTION=6827524]amit.tiger12[/MENTION]. :good:

Changelog

v5.1.1

Updated the module to conform with the current module installation setup.

Minor updates.

Added fingerprint for Samsung Galaxy Note 10 Plus and Xiaomi Mi 9T (Global version). Updated fingerprints for Essential PH-1, Google Pixel 2-4 (all variants), Oneplus 5, 5T and 6T, Xiaomi Mi 9T (European version), Mi Mix 2 and Redmi Note 4/4x. Fingerprints list updated to v72.
[Magisk] estofjlw:
None of it worked

Updated Magisk, Magisk manager and MagiskHide Props Config

None of it worked. I went from two green checks and a pass to "cts Profile false" Tried both fingerprints - and the security patch date was already correct according to MagiskHide Props Config.

Editing fingerprint into SafetyPatch Module - same

Removing SafetyPatch Module - same

Editing fingerprint into Magiskhide Props Confg - same

Removing Magiskhide Props Confg with edited SafetyPatch module still installed - same

Reinstalling Magiskhide Props Confg alone - same

Resetting to default values or replacing Magiskhide Props Config - same

Reinstalling SafetyPatch Module - FIXED

Removing both MODULES gives the 134-7 fingerprint shown in build.prop via BuildProp editor

Is the HUAWEI fingerprint so old it does not actually have a cts profile pass check ??

Any ideas what is causing this ??
[Magisk] Didgeridoohan:
The Huawei fingerprint used in Safetypatcher is old enough to not need the matching security patch date to pass CTS, that's why it passes without any further action.

I tested the 134-7 fingerprint you posted with 2019-12-05 as the set date for the security patch, and it did not pass CTS. That can mean a couple of things... Either that's the wrong date or the fingerprint isn't certified in the first place.

Double-check the date (use getprop to read the ro.build.version.security_patch prop), and if that is correct it likely means the print isn't actually certified by Google.
[Magisk] kullurumanoj:
[MENTION=4667597]Didgeridoohan[/MENTION]

I have checked the logs..there isn't difference in both.. please look during your free time once ur back
[Magisk] Didgeridoohan:
Thanks. I will as soon as I can.
[Magisk] steven360:
Does this work on ROMs that have cts failing and basicinegrity failing too?

My device is in serious need of passing safetynet, and I am using treble gsi ROM of bootleggersrom.
[Magisk] waylo:
It will not do anything for Basic Integrity. It might not even do anything for CTSProfile, if the basicintegrity is failing to begin with.
[Magisk] pandavova:
Hey, I got a error that the settings boot script does not appear to have run during boot.

Im using a S5 Neo, Magisk 16.4, with this 8.1 Custom Rom: https://xdaforums.com/galaxy-s5-neo/development/rom-lineageos-14-1-t3612300

Here is the log archive: https://puu.sh/AO887/32ff47fdfa.gz
[Magisk] Didgeridoohan:
Likely caused by a known bug with the reset function (typo on my part), that I'll fix as soon as I can. Out traveling for another week or so, so likely not before then... Uninstalling and reinstalling should fix it for now.
[Magisk] pandavova:
Thats the problem for me, it doesnt seem to help.
[Magisk] Didgeridoohan:
Ah... No, it wouldn't actually. Didn't think of that. That's another bug I'm gonna fix in the next release.

You have two options, and they both involve this file: /sbin/.core/img/.core/service.d/propsconf_late

Either change that files permissions to 755, or delete it, and reboot.
[Magisk] Cyga:
Thank you it really helped me. Now mi5 works on MIUI 10 Global Beta 8.6.21
[Magisk] Didgeridoohan:
Had a few moments to put together a bugfix release. Managed to patch up a couple of things... Let's hope I didn't break something else in the process.

Changelog

v2.3.1

Fixed permissions for the settings boot script when using the reset option.

Fixed log collecting.

Added automatic log collecting when there's an issue with the boot scripts.

Some updates to the documentation, mainly regarding troubleshooting issues.

Miscellaneous improvements and fixes.
[Magisk] Cryceratops:
Can anyone help? I'm running a custom 7.0 TW-ROM on my G930W8, but when running the props command, I get "The original prop values are not loaded, possibly due to a full reset of the module, or something has gone wrong. Please reboot your device to reset"

Resetting seems to yield the same message, any ideas?
[Magisk] Didgeridoohan:
What about the rest of what that message tells you about?

Hint: logs... Provide them.
[Magisk] Cryceratops:
Seems to occur even when running the "collect logs" command. This is what appears:

https://imgur.com/a/3opMKlj
[Magisk] Didgeridoohan:
You can also manually collect the logs (it's described in the documentation), or you can update to v2.3.1 and it'll automatically collect the logs for you if the issue persists.

But if you update, I'm guessing that the issue won't persist since I've fixed that bug in v2.3.1...
[Magisk] Cryceratops:
Here is the log file, collected using the latest version.
[Magisk] Didgeridoohan:
That is interesting. The resetprop tool doesn't seem to be working during boot on your device, hence it can't load the original prop values. It does work for collecting prop value when you're booted though (for the log).

There's also an error related to resetprop in your Magisk log.

Could you try a couple of things? Run this command in a terminal emulator and report back with the results:

su -c resetprop -v ro.build.fingerprint

Second thing you can try is to uninstall Magisk and install it clean. If the issue still persists, installing the v16.4 beta and providing the magisk_debug.log might show more about what's up (if it doesn't work there either).
[Magisk] Cryceratops:
Thanks for the reply. The first command you had me run yields this message: sh: resetprop: not found

I'll see about uninstalling Magisk, odd though, never seen this happen to anyone else

---------- Post added at 05:42 PM ---------- Previous post was at 05:09 PM ----------

So I tried downloading the uninstall and install packages for Magisk, flashed the uninstaller, re-booted back to recovery, flashed the installer, installed your module again but the same message pops up when I run the props command. Is there any other way of spoofing the fingerprint and passing ctsProfile?
[Magisk] Didgeridoohan:
Are you by any chance using Termux? If so you'll need this command:

su -c /sbin/resetprop -v ro.build.fingerprint

And I haven't seen this for anyone else either...
[Magisk] Cryceratops:
Interesting.. I am indeed using Termux... tried with the new command and I now get:

can't execute: Permission denied
[Magisk] Didgeridoohan:
What about this (-l is a small L):

su -c ls -l /sbin/resetprop

And what about only:

su -c /sbin/resetprop
[Magisk] JarlPenguin:
Device: Moto G7 (river)

Fingerprint: motorola/river_retru_n/river_n:9/PPOS29.114-134-7/b6963:user/release-keys

Vendor security patch: 2018-11-05

Security patch: 2019-12-05

Device: Moto G5S (Montana)

Fingerprint: motorola/montana/montana:8.1.0/OPPS28.65-37-7-12/073f74:user/release-keys

Security patch: 2019-08-01
[Magisk] angellusmortis:
I am trying to get Props Config to work on my device (Razer Phone 2 global, running Unofficial Havoc OS 3.0 GSI). I have the latest stable of everything (Magisk 20.3 and Props Config 5.11/v72).

I do not even need Props Config on the official Havoc OS 2.9 GSI running Pie, but on the 3.0 it does not seem to be able to set the fingerprint prop correctly. The only error I get is when the custom fingerprint is set to the default stage, I get

stack corruption detected (-fstack-protector)
Aborted

I am using a custom fingerprint based on my devices original settings. Here is my printlist:

Razer Phone 2 (9)=razer/cheryl2/aura:9/P-MR2-RC001-RZR-190914/3123:user/release-keys__2019-09-05

Any ideas how to fix this or to still manually set the props I need to so ctsProfile passes? I would like to use Havoc 3.0 so I can keep Android Q. I have the logs, but I am not 100% sure where/how to upload them to share them as I do not see an upload option in the form.
[Magisk] Didgeridoohan:
Have a couple of followup questions:

Exactly where and when do you see this error?

Have you tried using the fingerprint feature that's specific for GSIs?

For logs you could always use a filesharing service and post the link here or directly to me through PM.
[Magisk] estofjlw:
It was the date . . .

[MENTION=4667597]Didgeridoohan[/MENTION]

It was the date which should be 2019-12-01 for the 134-7 fingerprint.

The ROM device - Moto G7 Power (Ocean) is certified See https://xdaforums.com/showpost.php?p=81388415&postcount=148 and 149

The Custom ROM phone had the bad date and it had OTA updated itself to 134-7 firmware - so I assumed it was the good date.

The Stock phone which I let do the OTA update to 134-7 when I checked it there - had the 2019-12-01 security_patch date.

I removed the SecurityPatch module and changed the security_patch date through MagiskHide Props Config and on reboot two green checks without the SecurityPatch Module

Through BuildProp Editor - it still showed the bad date but in test of the MagiskHide module I left it and rebooted - and it passed CTS - then I changed the date there also by BuildProp Editor.

You can fix the date and put it in the list now.
[Magisk] Didgeridoohan:
Thanks, I'll take a look at adding the print for the next list update.

But... If you're going to edit the build.prop file manually there's absolutely no point to using a Magisk module to change the fingerprint. You might as well do it all directly in the file...

It does not matter what it says in the file, all that matters is what's loaded to memory. And that's where Magisk comes in with it's systemless modifications.

https://github.com/Magisk-Modules-R...rop-doesnt-change-after-setting-a-custom-prop
[Magisk] estofjlw:
Yes . . . I know

Yes I know . . . it was a piece of mind thing . . . which is why I re-booted and left it there at first to be sure MagishHide Prop Config was working
[Magisk] NOS_bzone:
Hi dev, can i request for Grus (Mi 9 SE)

Fingerprint: Xiaomi/grus/grus:9/PKQ1.181121.001/V11.0.4.0.PFBMIXM:user/release-keys

Or

Xiaomi/grus/grus:9/PKQ1.181121.001/V10.3.4.0.PFBMIXM:user/release-keys

Thank you.
[Magisk] gvv2012:
Use module on Android x86

Can I use this module on Android x86 9 Pie. This OS emulated on qemu/kvm.
[Magisk] Didgeridoohan:
The answer to that would be a definitive maybe... I have zero knowledge or experience with emulating Android so you'd have to try to find out. Please report back when you've done so.
[Magisk] Cedoresti:
if i have edxposed this module dont work ?
[Magisk] Didgeridoohan:
Maybe... As far as I know EdXposed hasn't been updated to use the new pre-init sepolicy patching and is still using live patching in post-fs-data, something that can lead to a number of issues.

One issue that has been reported is that it has the possibility of breaking Magisk's boot process and causing the boot scripts to fail to run. Which would lead to issues for this module... But, it doesn't happen on all devices, so you might be lucky.
[Magisk] Didgeridoohan:
Hi there.

I just realised you did not include the matching security patch dates for those fingerprints. I'm going to need those too...
[Magisk] NOS_bzone:
Hi dev,

Oh I'm sorry, you need security patch dates for those fingerprint.

- Security Patch (2019-08-01): Xiaomi/grus/grus:9/PKQ1.181121.001/V10.3.4.0.PFBMIXM:user/release-keys

- Security Patch (2019-10-01): Xiaomi/grus/grus:9/PKQ1.181121.001/V11.0.4.0.PFBMIXM:user/release-keys

Source:

https://github.com/TeamHorizon/andr...mmit/ac6acccaa0675d05ef0a844302db928aa7436eaa

Thank you dev ?
[Magisk] Cedoresti:
thank you. if all people answer same you ..... nice.

thank again.
[Magisk] zbysogi:
Im having similar issue. I cant pass cts profile and in emulator while running props the option "edit fingerprint" is disabled. The modules i have installed are:

BusyBox

liboemcrypto disabler

MagiskHide props config

SafetyPatch

Systemless hosts

When I uninstall the SafetyPatch i cant even run the props in emulator :/ vicious circle.
[Magisk] Didgeridoohan:
If you can't pass CTS with Safetypatch installed you likely won't have any success with this module either (do you pass basic integrity?). They basically do the same thing (which is why I disable that option when other similar modules are installed, to avoid conflict), but this module has some more customisation options.

What do you mean "can't even run the props"? What happens, is there an error, what about logs, etc? The more details you can provide, the easier it gets for me to provide help.
[Magisk] Pojinko:
Busybox not found

Hello,

When I open the Terminal Emulator app and type in the command "props" this message appears: "No Busybox found"

I have downloaded and installed the Busybox module from osm0sis. But still for some reason the props module does not see it. What can I do? I need to chenge the fingerprint of my device.
[Magisk] casouzaj:
Have you rebooted after after iyou nstalled the busybox module?
[Magisk] Pojinko:
Yes I did.
[Magisk] Didgeridoohan:
[MENTION=346743]casouzaj[/MENTION] has a very good starting point there... If that's not your issue I'm going to have to see some logs to be able to help.
[Magisk] Some_Random_Username:
[MENTION=4667597]Didgeridoohan[/MENTION]

OnePlus 7Pro NR GM1920 updated fingerprint:

OnePlus/OnePlus7ProNR_EEA/OnePlus7ProNR:9/PKQ1.190223.001/1912171007:user/release-keys (Android Pie, security patch level 2019/12/01)

Additionally, a new fingerprint:

Samsung Galaxy Core Prime (SM-G361F) (Lollipop 5.1.1, security patch level 2016/02/01): samsung/coreprimeveltexx/coreprimevelte:5.1.1/LMY48B/G361FXXU1APB1:user/release-keys
[Magisk] Pojinko:
I dont know how to get logs because I can't use the terminal as it says there's no Busybox (but there is) to collect logs. Also the manual way I don't have the folders listed in the documentation (/data/adb/mhpc - I don't have the /adb folder).

The only thing I can provide is the Magisk log attached.
[Magisk] joluke:
Install "syslog" from play google and run it and it will do the job for ya. Untick modem logs and grab all the others. That's it :)
[Magisk] Pojinko:
Please see attached.
[Magisk] Pojinko:
Please see attached
[Magisk] Didgeridoohan:
If you don't have the /data/adb folder there's something very, very wrong with your Magisk installation (that's where all Magisk's internal files are kept)... But since Magisk seems to work just fine I'm going to assume that's not the case.

And your Magisk log shows that you do not have any Busybox Magisk module installed. That doesn't mean that you don't have Busybox installed, of course, just that it's not a Magisk module. What happens if you execute the busybox command in terminal?

Edit: unfortunately those other logs are of no use to me...
[Magisk] Pojinko:
I fixed it by uninstalling magisk and flashing it again. Then I installed Busybox first, rebooted, installed props modules and reboot. Now it works. Thanks!
[Magisk] joluke:
I'm not a developer. Just gave ya syslog to collect logs.
[Magisk] xunholyx:
syslog is not bad, but personally I use Logcat Extreme. You should give it a try. Just an FYI
[Magisk] joluke:
Thanks for your help! I will try it for sure! :D
[Magisk] NOS_bzone:
Hi dev, for grus (Xiaomi Mi 9 SE) on new update module magiskhide not yet available..
[Magisk] Didgeridoohan:
There hasn't been an update to either the module or the fingerprints list since you posted those prints. So no, it's not in the list yet...
[Magisk] Some_Random_Username:
New fingerprint for Huawei P20 EML-L09 (Android Pie, security patch level 2019/10/06)

HUAWEI/EML-L09/HWEML:9/HUAWEIEML-L09/9.1.0.345C109:user/release-keys

An additional difference with current P20 fingerprint is that EML-L09 is a single SIM model while EML-L29 is a dual SIM one
[Magisk] Didgeridoohan:
Updated to v5.1.1-v73

Noticed a couple of issues right after publishing the last release, so here's another.

There are currently 283(!) Google certified fingerprints included in the module fingerprints list. Huge thank you to everyone who keeps sending in new and updated prints. This time around I want to especially thank [MENTION=5126235]angellusmortis[/MENTION], [MENTION=8483170]estofjlw[/MENTION], [MENTION=4488852]NOS_bzone[/MENTION] and [MENTION=8234677]Some_Random_Username[/MENTION] for providing the prints for this update.

Changelog

v5.1.2

Reset current fingerprint if disabling fingerprint modification because of a conflicting module.

Fixed using the configuration file in /sdcard during boot on FBE encrypted devices.

Added fingerprint for Huawei P20 (L09 single SIM), Motorola Moto G7 Power, Samsung Galaxy Core Prime and Xiaomi Mi 9 SE. Updated fingerprint for OnePlus 7 Pro NR and Razer Phone 2. List updated to v73.
[Magisk] Cedoresti:
this is really great app! big thank and many thanks for dev!
[Magisk] pilger:
Hey there!

First of all, thanks for the module. Great stuff!

I'm trying to set a custom value to a prop, though, and the command hangs right after I send the "y" for continue. I have to abort it with ctrl+c. Is there a fix for that?

I'm on Termux, using Magisk 20.1 on a Z00A device.
[Magisk] Didgeridoohan:
I can't replicate... Could you provide the logs?
[Magisk] pilger:
Of course. It's attached.

Thanks!
[Magisk] Didgeridoohan:
Hm... I can see that it does fail, but not why. Which reminds me that I've been meaning to implement more verbose logging and keep forgetting about it. Doesn't help you right now though, does it?

Until I do implement it (I won't forget this time), could you try a simpler terminal emulator. Termux sometimes actually creates more issues than it's worth...
[Magisk] pilger:
Aw. :(

I've tried Terminal Emulator just now and got the same result. Would you care to suggest a simpler one, maybe?
[Magisk] Didgeridoohan:
Doesn't get simpler than that... Hold on a couple of minutes and I'll get you a test version of the module with some verbose logging hacked in.

Edit: [MENTION=5942084]pilger[/MENTION] Here, I've attached a test zip for you. Install that (it's the same as the current version in the Magisk repo with some added logging), run the props command and replicate the issue, then go back in and save the logs again. Hopefully that should show me more... It's a bit of an air code hack (as in I haven't tested it), so I hope it runs for you.
[Magisk] pilger:
There you go.

I really appreciate you taking the time to do all this, man.