yashsingh1/xdaforums huggingface dataset:
[Magisk] xynthesis:
https://www.dropbox.com/s/c7egnix3oltk7ew/propslogs.tar%5B1%5D.gz?dl=0

sir would u check my log please, i cant use the module after some update of which i dont know why that conflicted with this(vendo/rom/or somehing else?) cause before it worked like a charm, thanks
[Magisk] Didgeridoohan:
Everything looks fine, so my guess is that there's another module that has a service.sh script that is actually blocking other module scripts. If I remember correctly, that's been fixed in the current Magisk code, so you have a few options.

Disable whatever module is causing the issue (from the log it looks like it's Swap Torpedo).

Install a Magisk Canary build (currently on build 18111). Be warned that there might be bugs (although I've currently not had any issues and I use nothing else than the Canary debug builds).

Wait for a more stable Magisk release.
[Magisk] JarlPenguin:
I'm happy to report that certain device fingerprints work with both basicIntegrity and ctsProfile false.
[Magisk] Didgeridoohan:
Interesting... Could you provide more details on that (as much as possible, please).
[Magisk] JarlPenguin:
I'm using Pixel Experience 9.0, device is Moto G5S. Both basicIntegrity and ctsProfile is false without the module. Before, I used Migrate to migrate from AOSPExtended 6.3 (in which basicIntegrity was true), which migrated all of my Magisk modules as well. I was using the Pixel 2XL fingerprint which gave me ctsProfile true. I migrated to PE, SafetyNet still reported all true. Since migrating caused some problems I clean flashed, then re-applied the Pixel 2 XL fingerprint, and voila! SafetyNet still reported true! + I enabled device spoofing and improved hiding as well later on.
[Magisk] xynthesis:
Thank you for the answer, without ur module i can't use my mbanking apps :good:
[Magisk] Oni-X:
Hi everyone! Couple of days ago I got a problem with Google play app. The ctsProfile and basicIntegrity are shown as true, but Google Pay still doesn't work. All other apps and Pokemon go work just fine. Installed magiskhide props config, but nothing changed. Cleared data in Google pay - didn't help. Thanks.
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] bitye:
When I add correct security patch date with custom I loose cts on LOS official on my Poco
[Magisk] Didgeridoohan:
Do you mean that it passes before you add it? Then why add it?
[Magisk] ipdev:
I was hoping to add ZenFone 5Z fingerprint but, I could not get it to pass cts. :(

Attached fingerprints.

- Nothing new, just some updates.

Cheers. :)
[Magisk] ipdev:
I haven't had the time to give the official LineageOS a try but, someone asked about the fingerprints (in los16 thread) when I looked the official LineageOS seems to be using Poco F1 Oreo 8.1.0.

Xiaomi/beryllium/beryllium:8.1.0/OPM1.171019.011/V9.6.18.0.OEJMIFD:user/release-keys

I tested it on a different phone and it only passes when the corresponding date is added.

Unless you changed the fingerprint, the corresponding security date would be 2018-07-01.

Xiaomi/beryllium/beryllium:8.1.0/OPM1.171019.011/V9.6.18.0.OEJMIFD:user/release-keys__2018-07-01

I use the v10.2.2 fingerprint and security date for roms on my poco and it's been passing fine.

Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V10.2.2.0.PEJMIXM:user/release-keys__2018-12-01

Cheers. :cowboy:
[Magisk] sachin5555:
Hey i m using magisk latest version on my asus ZMPM1 and facing strange issue, i play MPL game and this game is not run on rooted devices so i hide this app using magisk hide feature, but still the show me that your device is rooted. Please help me how to hide this app completely from root access
[Magisk] Didgeridoohan:
Wrong thread. Read here, and if you can't get things working you can ask for help in the general support thread.
[Magisk] Didgeridoohan:
Fingerprints list updated to v47

Had a few update fingerprints that had been submitted over the past couple of weeks. Updated the list, currently at v47. Will update when you run the props command or, if you have disabled automatic updates, by using the -f option. Can also be updated from the "Edit fingerprints menu".

A huge thank you for the fingerprints go to [MENTION=3284980]dieterhaack[/MENTION], [MENTION=6948826]Nebrassy[/MENTION], [MENTION=1909994]Huexxx[/MENTION] and as always the amazing [MENTION=7280276]ipdev[/MENTION].

Updated fingerprints:

Essential PH-1

Google Pixel

Google Pixel XL

Google Pixel 2

Google Pixel 2 XL

Google Pixel 3

Google Pixel 3 XL

Google Pixel C

OnePlus 5T

OnePlus 6T

Xiaomi Mi A2

Xiaomi Mi Mix 2

Xiaomi Pocophone F1
[Magisk] Herox:
After I install the fix it works fine and then my profiles go back to false after the phone has been running a while. I have an S8 and im using Renovate ICE 8.0 and the latest 18.1.

Edit: If I toggle hide off, then on, it fixes it for a while.
[Magisk] Didgeridoohan:
That's a known bug with v18.0 and v18.1. MagiskHide is currently being rewritten from scratch, so the next release won't have this issue (but might have others, being brand spanking new and all).
[Magisk] yxd0018:
asking a dumb question here. I have magisk and all required modules. I grant permission to the terminal app. But I can't find command props in the terminal even though I can find magisk folder and getprop and resetprop. Any idea?
[Magisk] oslo83:
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#usage

" If you use Termux, you'll have to call su before running the command. "

[emoji14]
[Magisk] yxd0018:
I did. Except prompt changed, nothing changes.

:/ $ su

:/ # props

/system/bin/sh: props: not found

127|:/ #pwd

/
[Magisk] Didgeridoohan:
This means that the module hasn't mounted properly (what happens if you run the busybox command?). Could be caused by an error or by Core Only Mode being active.

If it's caused by an error I'll need the logs (see the module readme on how to find logs) if I'm going to be able to help.
[Magisk] yxd0018:
Figured out. I installed busybox module , but didn't install busybox app. After installed busybox app and grant permission, then reinstalling your module, props command works.
[Magisk] Didgeridoohan:
You don't need a Busybox app together with the Busybox module. And actually running the script has no dependencies on Busybox. It was the reinstall that fixed it...
[Magisk] mbc07:
Hey [MENTION=4667597]Didgeridoohan[/MENTION], could you update the fingerprints of Xperia X? The last released firmware was based on Android 8.0.0 with September 2018 security patches (build number 34.4.A.2.118 for both variants)...

For Xperia X

Sony/F5121/F5121:8.0.0/34.4.A.2.118/1631208121:user/release-keys

For Xperia X Dual SIM

Sony/F5122/F5122:8.0.0/34.4.A.2.118/1631208121:user/release-keys
[Magisk] CoreyVidal:
Are there any fingerprints for any Android Go devices? Oreo (Go Edition) or Pie (Go Edition)?
[Magisk] bitye:
Xiaomi Pocophone F1 latest stable fingerprint is:

Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/V10.2.3.0.PEJMIXM:user/release-keys
[Magisk] Didgeridoohan:
Not included in the module, but I'm sure you could find one if you searched. Here are some tips on finding fingerprints:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

And by latest you mean what security patch date exactly? I could if course experiment, but if you happen to have it (since you have the fingerprint) it would make my life much easier.
[Magisk] bitye:
Sorry my fault it's 2019-02 for me on LOS it says 2019-02-05 for that fingerprint when I use vendor 10.2.3.0 FP with your awesome module.
[Magisk] Didgeridoohan:
Fingerprints list updated to v48

A few fingerprints added today and I had a few minutes to spare for testing and updating the module. List updated to v48.

Thanks to [MENTION=5604590]mbc07[/MENTION] and [MENTION=3157580]bitye[/MENTION] for providing the prints.

Updated fingerprints

Sony Xperia X

Sony Xperia X Compact

Sony Xperia X Dual

Xiaomi Pocophone F1
[Magisk] .:B:.:
[MENTION=4667597]Didgeridoohan[/MENTION] Could you add an 8.0.0 fingerprint for the XZ1 Compact as well? I'm on a LineageOS 15.1 build and the ctsProfile check fails because there's only an Android 9.0 fingerprint in the list.

Sony/G8441/G8441:8.0.0/47.1.A.12.119/1601781803:user/release-keys

is what works for me.

Thanks a lot for your hard work.

Edit: The ROM version is 47.1.A.12.119 and it seems to come with the March 2018 ASB. I am running LOS 15.1 myself with the February 2019 ASB, but the SafetyNet test doesn't give any problems.
[Magisk] JarlPenguin:
motorola/montana/montana:8.1.0/OPP28.65-37-7/9bb9df:user/release-keys

Moto G5S fingerprint Oreo 8.1 stock

Everything passes
[Magisk] pafaf:
Magisk Root hide not hiding a portugueses bank APP,

Millennium moove.

Any Change of some kind of tricky to bypass this?
[Magisk] Didgeridoohan:
That's a query best suited for the general support thread. But, start here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] bsports666:
sorry to asking, but i have problem with one application on my android that dont want to start because i have root. so is with this module possible to make magisk root invisible for that application? i try with hidde root on magisk manager but not working... i have pptv king phone.... i try to run this app in terminal but there is so many options dont know what to choose? can anybody help me?

regards
[Magisk] Didgeridoohan:
Take a look at the post right before yours, it applies to you as well...
[Magisk] oslo83:
Huawei Honor 9
HONOR/STF-L09/HWSTF:9/HUAWEISTF-L09/157C432R1:user/release-keys__2019-02-01
[Magisk] martyfender:
On the latest Canary 18119, when I open in the terminal there is an error with Magisk Hide Props Config. Do you see this also? I just checked and Enable Doze for GMS module is broken, also. I haven't checked others, yet. Busybox, also, so my guess is all modules. Reinstalling the module didn't help.

I have to go to work, so I don't have time to get a log now.

Thanks
[Magisk] hyborian:
No errors in my phones, it instead updated the fingerprint list.

Furthermore, I discovered the build.prop customization, excellent.
[Magisk] Allstar007:
hello I have the Samsung Tab S3 LTE (T825) what do I have to do so ctsProfile: False jumps to True?

i have installed cr-Android 5.1 ROM from here.
[Magisk] Allstar007:
I have already entered in the terminal props and select another model for the fingerprint the S9 Plus. until then I understand that, then it will be hard because I come from Germany and my English is not so good. :(
[Magisk] Didgeridoohan:
If you've selected a fingerprint from the list, rebooted, and the CTS profile still reports as false, try a different fingerprint that more closely matches your device (Android version, etc).
[Magisk] Didgeridoohan:
Haven't seen any issues on my devices. Sounds like modules aren't mounting/running properly, but that log would be the best way to know. Have fun at work.
[Magisk] Allstar007:
thanks for the tip, which would most likely fit with my Samsung Tab S3 LTE (T825)?

I have installed cr-Anroid 5.1 Rom with Android 9
[Magisk] Didgeridoohan:
Ah... When you wrote cr-Android 5.1 I assumed that was the Android version, so what I meant was to use a fingerprint from an Android 5.1 device. If it's a device with Pie installed you should be good with any fingerprint (concerning the Android version at least).

If you can't get the CTS profile to pass, even with a certified fingerprint installed you likely have other issues. Is basic integrity passing (if not, there's a good chance that this module can't help)? Does MagiskHide work at all (try adding a root app to the list and see if it no longer can detect root)? If you can't get things working, providing the Magisk and module logs might help us help you.

More info is available in the module documentation and in my Magisk troubleshooting guide.
[Magisk] martyfender:
At dinner hour at work I updated 18120 and it was the same. Will get logs when I can.
[Magisk] martyfender:
Here are logs from the device with Canary 18119. The other device I already reverted to 18118 and it is once again working fine.

On another device with [MENTION=7187684]ianmacd[/MENTION] 's latest, which is at the same commit level as 18120., I uninstalled your module and reinstalled it and when I run your props command in a root prompt, I don't get any response just this: u0_a95@NX16A8116K:/ #.

I tried in TWRP, also and got the same result.

Thanks
[Magisk] Didgeridoohan:
Boot order seems to be completely out of whack. Module script execution and mounting is happening way too late, so nothing gets mounted properly.

If you can 100% reproduce it on a clean install of the official 18120 (or later if releases are made), a GitHub issue with details and installation/magisk logs might be in order.
[Magisk] timjosten:
[MENTION=4667597]Didgeridoohan[/MENTION]

Huawei Honor 8X (8.1.0)

HONOR/JSN-L21RU/HWJSN-H:8.1.0/HONORJSN-L21/101(C10):user/release-keys__2018-10-01

Asus Zenfone Max Pro M1 (8.1.0)

asus/RU_X00TD/ASUS_X00T_6:8.1.0/OPM1/15.2016.1902.340-20190216:user/release-keys__2019-02-01
[Magisk] martyfender:
I reverted both of my Canary devices to 18118 and everything is ok now.

On one device it was enough to simply flash the 18118 zip. On the other device I had to run the magisk uninstaller, flash magisk and all of my modules in TWRP.

That very thought crossed my mind about running the uninsaller and reflashing 18120 and the modules to see if it would make any difference. I will have to seriously have to think about that, considering the hoops I had to jump through to get back to normal.

I do have a boot script running on the devices since I still experience random bootloops, especially on first boot after update, updating lspeed, etc. It almost seems as if the bootloops have gotten worse after adding the boot script. And shutting down and cold booting appears to help in that regard. With those 2 builds, the bootloops appeared to be more frequent.

See my post on the Canary thread, because I experienced some strange things getting that one device back to normal.

Thanks for all of your input.
[Magisk] :
I got LG H815 with 7.0. I used always Magisk v18.1 with the fingerprint of H812 (always LG G4) with 6.0 of Android. But in this week new update of Google Pay doesn't make me pay with NFC. My ctsprofile stays always on True. What happened?
[Magisk] Didgeridoohan:
Wrong thread; go here:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] martyfender:
I was able to solve the issues with 18120 on one device by flashing the magisk uninstaller, reflash magisk and all of my modules in TWRP. Now all modules are working as expected including Magisk Hide Props Config.

On the second, more troublesome device, I had to factory reset in TWRP, flash 18120 and all of the modules. It was one of the older devices so it may have been a while since it was factory reset.

In recent builds I have had to use the uninstaller on several occasion, especially when reverting to the last version of Magisk. I rarely ever had to use the uninstaller in older versions, when reverting.

Everything seems to be ok on that second device now, with the exception of an intermmit bootloop spread through 5 devices. The other 3 devices are on [MENTION=7187684]ianmacd[/MENTION] 's builds.

I had the same problem on Ian's latest build and had to use the Magisk uninstaller with it to get back to normal.
[Magisk] Didgeridoohan:
Some of the internal changes lately are likely going to cause issues when going back and forth between versions. Good to hear you got it sorted.
[Magisk] dudeistpriest:
Thank you for this! It works great on my LG G6 (I have a custom Pie ROM which successfully appears as a spoofed Nougat now). My question is, when I simulate the device in my case it changes the props so it appears to be Android 7 instead of the actual 9 that it is. Will this cause any problems updating apps such as Google Apps? Will Play Store try to install a non-compatible version of the apps? Sorry for the newbie question! :D
[Magisk] Didgeridoohan:
If it seems to be causing any issues you can disable individual simulation props in the "Device simulation" menu.
[Magisk] dudeistpriest:
It didn't cause any issues, I was just wondering if it will in the future, if anyone knows. Just to be safe, I just turned off the build simulation (ro.build.*) and it still seems to pass the cts profile test.

I am wondering if apps check the android version number or the api level when they update.
[Magisk] Didgeridoohan:
Device simulation is not necessary for passing CTS, only the device fingerprint.
[Magisk] el_muerte:
first of all, thanks for this great module which also works fine for me.

Unforntunatly, I hoped to hide root for German PayBackPay app, which doesnt help.

What I did (also according to your FAQs)

- Adding app to magisk hide

- hiding magisk manager

- disabled USB debugging

- disabled developer options

- clearing app cache

- using props config module to change fingerprint and also enabled device sumulation (which as as said works fine - SafetyNet ist ok / CTS profile ok)

- rebooted device

- added some urls to adaway blacklist (taken from thread "santander bank app detects root")

Nothing helped - PayBack pay app still detects root....

Any advice, what else I can do?

What I still did not check is using an up to date canary build of magisk.... Might that help? At the moment I am still on the current stable 18100 version with Manager 7.0.0

Thanks for your support.
[Magisk] Didgeridoohan:
[MENTION=7283620]el_muerte[/MENTION] That's quite off topic for this thread, so please post in the general support thread instead (or better yet, wait for a reply to the post you already made in the Intune Hider thread not even 30 minutes ago, which also happens to be off topic).

You'll find the general support thread here:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

Make sure to try everything first though (like you said, you still have things to try).
[Magisk] Saison2018:
[MENTION=4667597]Didgeridoohan[/MENTION]

Huawei P20 Pro=HUAWEI/CLT-L09/HWCLT:9/HUAWEICLT-L09/203C432R1:user/release-keys__2019-02-01

This fingerprint is OK with cts (=green) and mark device compliant in Google Play Store

Tested on my P20 Pro (CLT-L09) with firmware 9.0.0.241 (241 was uncertified in Google Play Store and cts = red or false)
[Magisk] dra 99:
still not support on my cellphone miui magisk version 18.1
[Magisk] Didgeridoohan:
I don't know what that means... You're going to have to be more detailed, but if I had to guess I would think you need the info in one or the other of these links:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#logs
[Magisk] pekkle_hksar:
New fingerprint for mi8 global 10.2.3.0

ro.build.version.security_patch=2019-02-01

ro.build.description=dipper-user 9 PKQ1.180729.001 V10.2.3.0.PEAMIXM release-keys

ro.build.fingerprint=Xiaomi/dipper/dipper:9/PKQ1.180729.001/V10.2.3.0.PEAMIXM:user/release-keys
[Magisk] Kartik kurt:
I have flashed this module, but its not running when i try to run it in terminal emulator.

I get this error that "The service.sh module script does not appear to have run during boot"

Need a solution... I am adding screenshot and log files too.
[Magisk] Didgeridoohan:
There is someting wrong with your Magisk installation, causing the late_start service mode (when service.sh is supposed to run) to happen way too early. It doesn't quite seem to happen on the previous boot when you uninstalled the module though...

Could be that there are Magisk image related issues with your device, so if you could try with a Canary build installed (currently at build 18122) that would be a good way to find out. The current code base have gotten rid of the image approach altogheter, just because it is prone to bugs and problems.
[Magisk] Kartik kurt:
Tried it... still the same error with a bit of additional problems. Screenshot n log below.
[Magisk] Didgeridoohan:
There's something wrong somewhere, because the log tells me that you're still using stable Magisk v18.1. Please install the Canary debug build and save the prop logs after that.

Considering the additional issue, reinstall the module.
[Magisk] shloim1:
Hi, I'm trying to get this module working on my S6 running unofficial Lineage OS 16, but when trying to edit device fingerprint, it says 'ro.build.fingerprint doesn't seem to exist on your system'. I checked the logs, and there seems to be errors in the propsconf_last log, but it's behind my comprehension.

Here I attached a link to the files in my Google drive, because I don't see an option to upload the logs, and also a screenshot of the message

Thanks

https://drive.google.com/file/d/18FsM9djws3sr0FDyC4mZBMzKShWW7DMD/view?usp=sharing

https://drive.google.com/file/d/1bU731hnb1ZeKWyF2cE7q2N9n7EieOWpf/view?usp=sharing

Edit: I forgot to mention, that if I put in a new fingerprint, my phone goes into a boot loop.
[Magisk] Didgeridoohan:
What happens if you run the getprop command on ro.build.fingerprint? In a terminal, just type this:

getprop ro.build.fingerprint

Also try with resetprop, to see if there's any difference:

resetprop ro.build.fingerprint
[Magisk] shloim1:
Thank you so much for replying!

when i enter the getprop commend i get the fingerprint in the build.prop, however when i enter resetprop commant i get: 'stack corruption detected (-fstack-protector) aborted 134': confused:?
[Magisk] Didgeridoohan:
Interesting... Seems like the resetprop tool dies a horrible death when touching the fingerprint on your device. Just to make sure, could you install the latest Canary build (currently build 18122) and try again? That way we can see if the issue is version related. If it still fails I'll bring it to [MENTION=4470081]topjohnwu[/MENTION]'s attention to see if it can be fixed.
[Magisk] shloim1:
just to confirm, did you check the logs that i uploaded?
[Magisk] Didgeridoohan:
Yes, I did. They show serve issues with the resetprop tool and the device fingerprint on your device. Could be ROM related, but it's also possible you've found some obscure bug in Magisk.

Only way to know for sure if it's something that needs further attention is if you can replicate it on the latest Canary release.
[Magisk] shloim1:
doing it right now (btw i had the same issue with magisk v18.0)

---------- Post added at 06:44 PM ---------- Previous post was at 06:37 PM ----------

installed canary, and working beautifully!! thanks

logs=https://drive.google.com/file/d/12MW39bi3ZguB3v-qgmkJcyhPaXPfpPbP/view?usp=sharing

screenshot=https://drive.google.com/file/d/1twZ7VN7SkcRszDoAnsP4hkeYIk_a7dKD/view?usp=sharing
[Magisk] Didgeridoohan:
Glad to hear it. :good:
[Magisk] Didgeridoohan:
D'oh! You can boot to recovery and pull the Magisk log and propsconf log from /cache. Or if you manage to boot up you can run the props command and "collect logs", the last bootup's logs will be in there as well.
[Magisk] michaelmaverick:
Newest key for Xiaomi Mix 2S: Xiaomi/polaris/polaris:9/PKQ1.180729.001/V10.2.2.0.PDGMIXM:user/release-keys__2019-02-01
[Magisk] martyfender:
I would recommend running the latest Magisk uninstaller from the latest Canary build in TWRP, followed by flashing the latest Canary debug build in TWRP, also, all before rebooting.

Running the uninstaller has solved issues for me on my devices recently, with this module and others. Then after reboot, if the Magisk Manager is not installed by it, you can also install the MM debug.apk from the Canary thread. This will give you a clean start.

When flashing the uninstaller, confirm that it properly restores the backed up stock boot.img. If it does not, you may also need to flash the stock boot.img before flashing the Magisk.zip

Finally, you can then install your modules.
[Magisk] highdiver_2000:
Hi, I can pass Safetynet but I can't add any cards in Google Pay.

Mix2S with MIUI Global Beta, Magisk v18 with Magiskhide, Busybox and TWRP. All apps from the developers.

Installation of MagiskHide, I did the following:

1. Props

2. Restart

3. Change signature

4. Restart