yashsingh1/xdaforums huggingface dataset:
[Magisk] jaroulz:
Thanks for trying to help mate, pretty new here so not sure what you guys need in order to move forward ^^

Using the default Terminal app that comes with LOS 17.1 (installed BusyBox tho, didn't change anything).

Regarding the logs, there is nothing in Magisk coz I've installed the .zip via TWRP. But when I go to Modules in Magisk, it shows MagiskHide Props Config module is installed. Version 5.1.2-v76.

Core Only Mode was enabled... Trying again now, will update.

---------- Post added at 03:38 PM ---------- Previous post was at 03:38 PM ----------

Still not working, same message from the Terminal.
[Magisk] Didgeridoohan:
Did you reboot after disabling Core Only Mode (it's necessary)?
[Magisk] jaroulz:
Just rebooted my phone, working now ! Thanks you're the man (and I'm the noob lol)
[Magisk] Some_Random_Username:
OnePlus 7 (GM1903) updated fingerprint: OnePlus/OnePlus7_EEA/OnePlus7:10/QKQ1.190716.003/2002021900:user/release-keys__2020-01-01

OnePlus 7 Pro(GM1913) updated fingerprint: OnePlus/OnePlus7Pro_EEA/OnePlus7Pro:10/QKQ1.190716.003/2002021900:user/release-keys__2020-01-01
[Magisk] jaroulz:
For those who were trying to get this mod working in order to be able to use Samsung Wearable app, here is a link to what to do next (post from EvilWayz) :

https://xdaforums.com/galaxy-s9/help/galaxy-wearable-app-rooted-phone-help-t3838503/page5

Hope this helps coz it took me 48hrs to get this thing done (a lot of research).
[Magisk] ncc1977d:
Solved the problem with IanMacs magisk 19.1 and PetNoire Safety Spoofer. No magiskhide props config needed !
[Magisk] doonoo:
Is there a way to make OnePlus 5t Android 10 key?
[Magisk] martyfender:
Maybe if someone provides it.
[Magisk] ipdev:
A little OT for this thread but..

A great example of how to use this module. ;)

You might want to to point to the original post earlier in the thread by [MENTION=9328513]To_O[/MENTION]

Galaxy Wearable App on Rooted Phone Help xdaThread - Post 7

The one with the screenshots.

For a lot of prop changes/device spoofing using this module, you might be better off using a config file.

Configuration file GitHub - Link

Not until 5t is officially updated to 10.

If you are looking to use a 10 fingerprint, I would suggest Pixel 2xl (taimen).

Although any 10 print will do. (If you want to stay with OnePlus, use the 6t print.)

Cheers. :cowboy:
[Magisk] dgl6y7:
So I used this to enable Wi-Fi tethering on my Pixel 3 XL. It works perfect! Thank you so much this is an awesome module.

I had a question though. As I understand it in my simplistic non-tech mind, this creates a boot script that changes the build.prop settings on boot rather than permanently changing them in the file.

Will this script continue to work if I unroot? With Android 10 root doesn't really give me a lot of access anyway. I would like to unroot so I can use Google Pay.
[Magisk] Didgeridoohan:
The script completely relies on Magisk, so it won't work if you unroot.

For Google Pay, see these threads/posts:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

https://xdaforums.com/apps/magisk/m...7-1-22-pie-t3929950/post79643248#post79643248
[Magisk] Syoenth:
I'm using CrDroid in Xiaomi Redmi Note 7 and the module install correctly, but once I apply a fingerprint and reboot it bootloops so I have to delte the module via Magisk Manager on Orangefox, why is this happening?
[Magisk] Didgeridoohan:
Did you only apply a fingerprint and nothing else? Default settings otherwise? Logs?
[Magisk] Syoenth:
yes, only apply a fingerprint, reboot and I got bootloop
[Magisk] Didgeridoohan:
I'll need those logs to have any chance of helping.
[Magisk] Syoenth:
these are the logs
[Magisk] Didgeridoohan:
You're getting a segmentation fault when resetprop is run to change the fingerprint. I have no idea why...

Could you post the rest of the files in /data/adb/mhpc as well, and the Magisk logs?
[Magisk] Syoenth:
ok
[Magisk] CarbonGTR:
Removed post.
[Magisk] Sid127:
[MENTION=4667597]Didgeridoohan[/MENTION] I have just been informed that this fingerprint doesn't pass cts. However the fingerprint below does

Nokia/Dragon_00WW/DRG_sprout:10/QKQ1.190828.002/00WW_4_10C:user/release-keys

Security Patch Date - December 1, 2019
[Magisk] Didgeridoohan:
I tested that first print last night and it worked fine... And I checked it again right now and had no issues.
[Magisk] Didgeridoohan:
[MENTION=6673539]Syoenth[/MENTION] There's not much I can do about your issue right now. I've seen this before on rare occasions but don't know what is causing it. Could be a bug with resetprop, but that would need the attention of [MENTION=4470081]topjohnwu[/MENTION] and he has a lot on his plate (it's on the bug investigation list though).

There's one more thing we can test and later I'll prepare a file for you to see if a previous workaround for this issue works for you as well.
[Magisk] Some_Random_Username:
OnePlus 7T HD1903 updated fingerprint: OnePlus/OnePlus7T_EEA/OnePlus7T:10/QKQ1.190716.003/2002022021:user/release-keys__2020-01-01

OnePlus 7T HD1901/1905 updated fingerprint: OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/2002022020:user/release-keys__2020-01-01
[Magisk] Didgeridoohan:
[MENTION=6673539]Syoenth[/MENTION] Try putting this in a file in /data/adb/post-fs-data.d, give it execution permission and reboot. See if that works...

#!/system/bin/sh

resetprop ro.build.fingerprint "xiaomi/lavender/lavender:9/PKQ1.180904.001/V10.3.12.0.PFGMIXM:user/release-keys"
resetprop ro.bootimage.build.fingerprint "xiaomi/lavender/lavender:9/PKQ1.180904.001/V10.3.12.0.PFGMIXM:user/release-keys"
resetprop ro.system.build.fingerprint "xiaomi/lavender/lavender:9/PKQ1.180904.001/V10.3.12.0.PFGMIXM:user/release-keys"
resetprop ro.vendor.build.fingerprint "xiaomi/lavender/lavender:9/PKQ1.180904.001/V10.3.12.0.PFGMIXM:user/release-keys"
resetprop ro.odm.build.fingerprint "xiaomi/lavender/lavender:9/PKQ1.180904.001/V10.3.12.0.PFGMIXM:user/release-keys"
resetprop ro.build.description "lavender-user 9 PKQ1.180904.001 V10.3.12.0.PFGMIXM release-keys"
resetprop ro.build.version.security_patch "2019-08-05"
[Magisk] jman0:
Confirmed working on a ZTE Nubia Z17S (NX595J) using the built-in fingerprint from the Nubia Z17 (NX563J). I can now use Google Pay again. Thanks.
[Magisk] Syoenth:
Thanks
[Magisk] Senliast:
Just want to say, that i also have the problem, that one user had a few sites back. After selecting prop, entering value and answering yes, the terminal just hangs. Tried with Termix, Android Terminal emulator, Material Terminal, all the same. Device - LG G3 with Fulmics ROM. Magisk 23. Xposed (classic). Have a Galaxy S7 and Xiaomi Mi9T Pro - here it works just normally.
[Magisk] Sid127:
Well, we were unable to pass cts on our devices on the Stock build itself, that's why I thought I'd let you know
[Magisk] Didgeridoohan:
We never did figure that one out. I'll see if I can figure out a better troubleshooting method. Not sure when I'll have time though. If I don't get back to you anytime soon, it'll either be because I'm crazy busy or that I've completely forgotten (got a bad case of Teflon memory these days). :D
[Magisk] Didgeridoohan:
Interesting. And I assume that fingerprint is from that build. Like I said, I can pass CTS just fine with the January fingerprint you provided (haven't tested the other one yet), so there might be something else going on with that stock build.
[Magisk] breakdowns:
Please add Redmi Note 8 (ginkgo)
[Magisk] Didgeridoohan:
I would need your help with that:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] breakdowns:
This fingerprint Redmi Note 8 (ginkgo):

Xiaomi/ginkgo/ginkgo:9/PKQ1.190616.001/V11.0.6.0.PCOMIXM:user/release-keys

Security patch data : 01-01-2020
[Magisk] Didgeridoohan:
Thank you, but I just tested that print and it does not pass the CTS profile test.
[Magisk] crok.bic:
Settings export?

Hi [MENTION=4667597]Didgeridoohan[/MENTION], a quick question:

I'm not sure whether it is already implemented (and I missed it) or not (yet..) but is there any possibility built into the module's logic to somehow export it's settings? During a move from one ROM to another or when sharing my setting with people it would be really helpful to me, I slowly added lots of props one by one and now it is around two dozen :D Moving the whole module directory or just recreate the same config with the propsconf_conf is feasible will more than likely will work just fine, but I thought about an "elegant" method where I can use the already set up module somehow (:

Thank you!
[Magisk] Didgeridoohan:
The configuration file is the working way of saving your settings. I currently don't have any plans for other features. Do you have any particular way to implement such a feature in mind?

Thinking about it, I could possibly add a feature to export the current settings to a propsconf_conf file.

Man... This thing is getting complicated. I probably should start learning to code an app for this, but I really don't have the time for that.
[Magisk] seniug:
Can I uninstall magiskhide props after changing fingerprint and having my playstore certified?
[Magisk] Didgeridoohan:
No. It's a systemless modification, so if you uninstall the module the scripts won't run and the fingerprint will return to the original one.
[Magisk] seniug:
Ok i understand. Thanks for the quick answer!:)
[Magisk] crok.bic:
No need for an app, really. I would just do the same as you came up with: recreate the propsconf_conf with the current settings, probably without the whole documentation in the original file, purely including the variables' values only. Since the module's scripts are going through these anyway I suppose this is an easy, effective and professional way - or isn't it?
[Magisk] Didgeridoohan:
I have already implemented this feature and just need to give it a test run (it's all air code at the moment). I should have some time in the coming days to do some polishing of the module and get a new version out there.

About an app: I have been toying with the idea to learn how to code Android apps, just to make the UI/UX a bit friendlier. That's something I currently (and for the foreseeable future) do not have time for though...
[Magisk] aerodown:
Add support for Xiaomi Mi Box S

Hi, please add Xiaomi Mi Box S fingerprint, thanks.

ro.build.fingerprint=Xiaomi/oneday/oneday:9/PI/2231:user/release-keys
ro.build.version.security_patch=2019-11-05
[Magisk] aerodown:
Add support for Samsung Galaxy Note 9

Hi, please add Samsung Galaxy Note 9 fingerprint, thanks.

ro.build.fingerprint=samsung/crownltexx/crownlte:10/QP1A.190711.020/N960FXXS4DTA5:user/release-keys
ro.build.version.security_patch=2020-02-01
[Magisk] SH1M4BD3:
Can you add mi 8 se 9,10??
[Magisk] Didgeridoohan:
Not without your help:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] babaren:
Vernee Mars Pro Fingerprint

Hi Can You add Vernee Mars pro fingerprint ?, thanks :)

ro.build.fingerprint= vernee/Mars_pro/Mars_pro:7.0/NRD90M/1506326000:user/release-keys
ro.build.version.security_patch= 2017-08-05

Thanks in advance :)
[Magisk] Didgeridoohan:
Thanks, but unfortunately that print does not pass the CTS profile test.
[Magisk] babaren:
what should i do ? , or did i gave a wrong one ? :confused:
[Magisk] Didgeridoohan:
I'm not sure there's much you can do. I took a quick look at Google's list of supported devices and the Mars Pro isn't even on the list (there are other Vernee devices though).

If the device hasn't been certified by Google, no fingerprints from that device will pass CTS.

If you get ahold of another print I can test that, but considering the above I wouldn't hold out much hope...
[Magisk] babaren:
you mean another device ? , or get my print again on my device ? :confused:
[Magisk] Didgeridoohan:
I meant a different print from the same device, if there are any other firmware release available.
[Magisk] babaren:
is there a way to get it without installing the rom ? , because vernee only released 2 roms :crying:
[Magisk] Didgeridoohan:
There are some tips in the module docs:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] babaren:
thanks ill to find it :)
[Magisk] crok.bic:
Thank you for implementing this feature! (: However, I updated the module on my phone (running Magisk v20.3 if it's important) and tried the config export function and it - indeed - created a propsconf_conf file on the [internal storage]/mhpc dir but it's size is 0byte. How can I troubleshoot this behavior?
[Magisk] Didgeridoohan:
Yup... Confirmed. For some strange reason it worked on my test device, when really it shouldn't have.

I'll fix shortly.
[Magisk] crok.bic:
Thanks for the prompt answer, I'm waiting patiently (:
[Magisk] Didgeridoohan:
I did a quick fix, so if you could reinstall v5.2.0 (I'll probably just make it a silent update) and see if it works now I'd be grateful.
[Magisk] crok.bic:
Yeah, sure I updated it (increased only the versionCode but not the version variable, tricky)

and it looks to work perfectly fine! :good: :highfive:
[Magisk] Didgeridoohan:
Excellent. Now I just need to figure out another quickly reported bug (a whole bunch of devices will show the wrong device when trying to pick a fingerprint), but I'll leave that for tomorrow. Now I need to sleep...
[Magisk] Didgeridoohan:
Who needs sleep anyway? Quick fix pushed...
[Magisk] Didgeridoohan:
Quick fix v5.2.2

Soo... I found what must be some kind of weird copy-pasta error that broke manufacturer and model simulation last minute. That is now fixed and released as v5.2.2. Original release notes still apply.

Bloody hell... I wonder what else I broke.
[Magisk] Sid127:
No big deal, buddy. Feel free to mention me anytime you need more prop values from Nokia 6.1 Plus :)
[Magisk] crok.bic:
Far as I can tell it works perfectly fine!
[Magisk] Didgeridoohan:
Well, I know of at least one bug, but it's likely been around for a while, so I didn't break that with this release (probably). It only affects installation though, so not that big a worry for now.

And I've got another thing that needs fixing that's not really a bug with the module but that I can do something about, so...

Expect a new release fairly soon. :D
[Magisk] Some_Random_Username:
OnePlus 6T updated fingerprint: OnePlus/OnePlus6T/OnePlus6T:10/QKQ1.190716.003/2002220019:user/release-keys__2020-02-01

OnePlus 6 updated fingerprint:

OnePlus/OnePlus6/OnePlus6:10/QKQ1.190716.003/2002220019:user/release-keys__2020-02-01
[Magisk] loco1911:
Redmi 7 Onc Fingerprint

Fingerprint

xiaomi/onc/onc:9/PKQ1.181021.001/V11.0.3.0.PFLMIXM:user/release-keys

ro.product.manufacturer

Xiaomi

ro.product.model

Redmi 7

Miui 11.3.0

Android 9 Pie

Enviado desde mi Redmi 7 mediante Tapatalk
[Magisk] Didgeridoohan:
Thank you very much for including the manufacturer and model, but unfortunately I also need the security patch date. I could of course guess and figure it out by trial and error, but takes way more time than I have.
[Magisk] Instinct_82:
Hello today i tried to install this module but after installing and rebooting my device it says (custom binary blocked by frp) and i can't access twrp to disable that magisk module. Is there any way to recover without losing my data?
[Magisk] Didgeridoohan:
Did you only install the module and nothing else? You didn't enable any settings, fingerprint, custom props, etc?

If you did enable anything, using the rest file after having disabled Magisk might help. Details on that in the docs, here:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

If all you did was install the module and nothing else I'm not sure how to help... Can't see how you'd get that result just by that. What device and Android version are we talking about? You'll somehow have to disable/uninstall the module, but if you can't boot or enter TWRP that can be hard.

One thing you can try is the Magisk built-in adb command for dealing with these kind of situations, alternatively the custom Magisk route:

https://didgeridoohan.com/magisk/Magisk#hn_No_custom_recovery
[Magisk] Some_Random_Username:
Edited previous post to add OP6 fingerprint.

OnePlus 7T Pro NR HD1925 updated fingerprint: OnePlus/OnePlus7TProNR/OnePlus7TProNR:10/QKQ1.190716.003/2002150222:user/release-keys__2020-02-01
[Magisk] Instinct_82:
[Device- galaxy s7 edge dual sim (Indian)

OS- oreo 8.0]

Hey today i was trying to solve (textnow app) root detection problem and afaik i did these steps :-

1. Repacked magisk manager

2. Flashed magiskhide prop module (it was successful)

3. Turned off OEM Unlocking in usb debugging

4. Reboot

After researching i find that i was stupid to turn of oem unlocking (i thought maybe coz of setting textnow app was detecting root)
[Magisk] Didgeridoohan:
Yes, that's very likely your issue. If there's any way of saving your data you're better off asking for help in your device's forum.
[Magisk] Mr_Happy:
A couple of days ago I installed this and I could change the device fingerprint with it.

Yesterday I installed the latest rom update and now it says in the menu 'edit device fingerprint (disabled)".

I searched, but could not find how to enable it...

What am I missing and how can I enable this again?
[Magisk] Didgeridoohan:
That usually means that you have another module installed that alters the device fingerprint:

https://github.com/Magisk-Modules-R...ter/README.md#an-option-is-marked-as-disabled
[Magisk] satnavpt:
[MENTION=4667597]Didgeridoohan[/MENTION] I followed steps to edit the fingerprint for my device in order to fix the cts profile fail. However, it is stuck on booting after the terminal asks to reboot. What do I do?

(BTW This is on an A5 2017 using CRDroid 10.0)
[Magisk] Didgeridoohan:
Take a look here:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] Mr_Happy:
Somehow I missed that... :(

Weird that it worked before, but disabled some modules and now it works.
[Magisk] Didgeridoohan:
Update to v5.2.3-v79

I'm on a roll (and playing with this is such a great way to procrastinate with real work), so here's another update. While fixing stuff that I broke with the v5.2.0 update I found an issue with transferring settings during a module update. Nothing major, but annoying so here's the fix.

There has also been a couple of reports where there are issues with resetprop retrieving prop values. Could be a bug with resetprop or a device/ROM issue, but until more is known I've chosen to use resetprop only to set prop values and good old getprop to retrieve them. Might make the module work on those few devices that are affected.

Lastly, a big ol' thank you to [MENTION=8234677]Some_Random_Username[/MENTION] for providing the OnePlus prints for this update.

Changelog

v5.2.3

Fixed issue with settings transferring between module updates.

Use resetprop only to set values and retrieve values with getprop. For whatever reason some devices have issues with resetprop and this might make the module work on those.

Updated fingerprints for OnePlus 6, 6T and 7T Pro NR. Fingerprints list updated to v79.
[Magisk] swour:
Samsung Galaxy A5(2017) fingerprint update:

Security patch date: 2020-01-01
[Magisk] :
So, magiskhide works but running props in the terminal says that the service sh script did not run. Ive tried every 6 configurations (3*2 = boot stage settings * background script). Ive had edxposed before and now i only have osmisis busybox and magiskhide enabled in magisk. Reinstalled the system even, and magiskhide multiple times.

The link below should provide the logs

http://www.mediafire.com/file/gox3ze35u1x7s7u/propslogs.tar.gz/file
[Magisk] Didgeridoohan:
For some reason, that I unfortunately have no way of knowing what that is, the late_star service stage doesn't run properly on your device. Even looks like it is failing as MagiskHide starts.

Reinstalling system or MagiskHide Props Config doesn't help in this case. You could try deleting the Magisk database (/data/adb/magisk.db) in case it's something wrong with a table or such (just make sure to unhide the Manager first), or try reinstalling Magisk.
[Magisk] :
Deleting magisk.db worked. Thanks so much
[Magisk] Some_Random_Username:
Android 10 fingerprint for OnePlus 7 Pro NR GM1920: OnePlus/OnePlus7ProNR_EEA/OnePlus7ProNR:10/QKQ1.190716.003/2002141334:user/release-keys__2020-01-01
[Magisk] Bskendkk:
can't pass cts even after changing to an in-module fingerprint

hey!

Total noob here, trying to pass cts

So I have installed the module, ran terminal, picked a certified fingerprint (tried redmi note 8 pro and mi mix 3)...

Upon reboot, I still can't pass cts, even though terminal shows that the new fingerprint is applied..

What am i doing wrong?

For the record, I'm on Redmi Note 8 Pro, running 20.2.27 beta ROM.

Please help! :)
[Magisk] loco1911:
Redmi 7 Fingerprint

No problem bro :D

The security patch is from 2019-12-01 (December)

Thank you for this amazing module!
[Magisk] Didgeridoohan:
Take a look in the docs for some tips on how to troubleshoot:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Bskendkk:
Hello! Thanks for replying :)

I read the doc thoroughly, tried everything...

Nothing worked :(

I am now trying to collect logs. It says "the file will be placed in your root folder".

The problem is, there are 10-15 files there in the root directory and i dont know which is the log file (none of the names make it clear). Could you please assist me?
[Magisk] Cryceratops:
This is what I get.

https://imgur.com/a/xzUeCvB

Is there any way to do it manually perhaps? I'm not too concerned with how I arrive there, just that it passes
[Magisk] Didgeridoohan:
You need to fake the device fingerprint, and with Magisk that is done with the resetprop tool... You could of course manually edit your build.prop file with the new fingerprint, but if you want to keep your /system untouched that's not an option.

I have no idea why you can't run resetprop though. I'll investigate a bit...
[Magisk] Cryceratops:
What are the consequences of doing that? And how would I go about doing so
[Magisk] Didgeridoohan:
[MENTION=5401246]Cryceratops[/MENTION] Just to be sure, could you run the commands in Terminal Emulator instead of Termux?
[Magisk] Cryceratops:
Sure, this is the result.

https://imgur.com/a/10LYPA8
[Magisk] Didgeridoohan:
Same thing...

So, the issue is that the resetprop tool doesn't seem to get symlinked properly. Why?

Does your ROM by any chance come with Magisk pre-installed?
[Magisk] Cryceratops:
Yes it's this ROM right here: https://xdaforums.com/galaxy-s7/help/qa-superman-rom-t3472202

It comes with the AROMA option.. but the strange thing is I had this same ROM installed a few months ago, and to pass the ctsProfile I read somewhere that I needed to paste a stock build.prop overtop the existing one, and that seemed to do it. When I tried it again this time (after a clean format), it still seemed to fail. So I re-pasted the original again. Is there something I can modify to pass the check?
[Magisk] Didgeridoohan:
If you're passing basicIntegrity but not ctsProfile it's usually enough to change the device fingerprint (ro.build.fingerprint) to a certified fingerprint. You can do it systemlessly with Magisk (resetprop), or manually by editing build.prop. Doesn't really matter unless you really want to keep /system untouched (usually only important if you want an OTA on a stock ROM).
[Magisk] Cryceratops:
Right. I'm not concerned with OTAs. In this case resetprop doesn't seem to be working... do you know what value(s) I need to change manually in order for it to pass?
[Magisk] Didgeridoohan:
Like I already said, ro.build.fingerprint needs to be set to a certified value. Usually found from a stock ROM. Looking at your build.prop though, it kind of looks like that's already the case (I'll test it when I get an opportunity, gonna spend the next 36 hours or so traveling)... If so, you might have other issues that this method can't fix.

I can't help you with that, more than linking to my troubleshooting guide, where you'll find plenty of tips on how to make sure that everything is working as it should.