yashsingh1/xdaforums huggingface dataset:
[Magisk] ~clumsy~:
Already tried "setenforce permissive" same result.

Do you think this dead end ? Or is there some options I can try after you've reviewed the log.

I will look into the kernel sources and try and build my own, even if that's possible, not sure what the current state is on the sources for my device.
[Magisk] Didgeridoohan:
I'm really not sure...

There's another thing you could try. Let's see if it's the module or the props that are causing the issue. Disable the module, put this in a boot script and test it, first in service.d and then post-fs-data.d.

#!/system/bin/sh
resetprop ro.build.version.security_patch 2019-06-05
resetprop ro.debuggable 1
resetprop ro.build.fingerprint google/blueline/blueline:9/PQ3A.190605.003/5524043:user/release-keys
resetprop ro.bootimage.build.fingerprint google/blueline/blueline:9/PQ3A.190605.003/5524043:user/release-keys
resetprop ro.vendor.build.fingerprint google/blueline/blueline:9/PQ3A.190605.003/5524043:user/release-keys
resetprop ro.build.description "blueline-user 9 PQ3A.190605.003 5524043 release-keys"

That will do the same prop modifications that you had in the first log you posted. If that works we know it's going to be something to do with the module rather than the props. If it still doesn't work you could comment out one prop at a time to see if it's a specific prop causing the issue.
[Magisk] ~clumsy~:
With your module disabled they both booted but the servic.d didn't result in a ctsProfile pass but post-fs-data did. I have attached both logs below:

bootlog_service.d.log

bootlog_post-fs-data.d.log
[Magisk] Didgeridoohan:
Hm... Thank you. That confirms that it's something about the module setup and the scripts that I run at boot. It doesn't look like it's got something to do with the denials I mentioned earlier, since they are present in these logs as well. You have no segfaults this time around though...

One more thing to try before I can start digging through my code:

Enable the module again, but before rebooting go to /data/adb/module/MagiskHidePropsConf and rename post-fs-data.sh and service.sh to something else, so that they do not run at boot. This way only system.prop will be loaded and the fingerprint you've set will be loaded from there. If that works, please rename service.sh back to it's original and try again. If that still works restore post-fs-data.sh and this time things will likely fail again. This'll hopefully give me a hint as to where the issue is.
[Magisk] ~clumsy~:
I re-enabled the module, renamed post-fs-data.sh and service.sh then rebooted, all was fine. I restored service.sh and rebooted, I got stuck on boot just before the boot animation, I renamed service.sh using adb shell and rebooted, the phone failed to boot again. So I had to manually remove the module using adb shell to reboot.

[MENTION=4667597]Didgeridoohan[/MENTION] Thanks for you help, you gave me a work around, if there anything you want me to test feel free to PM me.
[Magisk] DerNetzreporter:
Hi, I am using a Xiaomi A1 with Android version 8.0 and Magisk and Moun_Kernel.

The ryanair app crashes and isnt present in playstore for this phone/verison.

every try to change/renew the fingerprint (this should be the reason why the app crashes) fails.

Using this modul or Kernel Adiutor cant change the fingerprint.

after rebooting the phone it is always the old version at the ro....fingerprint line.

changing security level date works. Android system info shows the new date
[Magisk] pmatj:
Hi,

I'm using a GSI Treble ROM "Descendant" on a P20 Lite and I want to set a device fingerprint for it. However, when I apply any patches, the system does not start, except for when I set everyhting to post-fs (set in Script Settings and also when appling fingerprint and date). In that case, however the fingerprint is not changed...

I've installed magisk into recovery_ramdisk and so I currently have no real recovery to change data on the device.... In order to get back into busienss I need to flash original recover_ramdisk, boot into erecovery and wipe data which boots the normal recovery.

After that, I can start over again (flash magisk into recovery_ramdisk and so on....)

my problem is, that I currently cannot supply any logs nor deactivate the module (although I can boot "normally" and circumvent magsik - in that case I do not have any root-rights ...) it's crazy :)

Any ideas?

Thanks in advance,

Peter
[Magisk] Didgeridoohan:
I need logs to even have a chance to see what that's about.
[Magisk] Didgeridoohan:
Are you using the feature to use the vendor fingerprint, or picking one from the list? If not, try using the vendor print.

Other than that I need logs, so set the print for post-fs-data and grab those logs...
[Magisk] DerNetzreporter:
Log file, problem see above
[Magisk] Didgeridoohan:
There was an error in the fingerprints list for that particular print. I've fixed that now... There's also an error when the fingerprint gets set, but I'm not quite sure about that one...

Update the fingerprints list, reapply the print and try again. If it still fails, please try changing back to the default boot stage and also use the Magisk Canary debug build. That will give more comprehensive logs. Post the new logs and we'll continue troubleshooting from there.
[Magisk] DerNetzreporter:
Fingerprint is now updated but still no luck with Ryanair app. So it seems I need to search other people with my problem.

EDIT: Changed fingerprint also to Google pixel 3a v9. ctsProfile now fails, cleared data and cache in playstore, still no success.
[Magisk] manjaroid:
Working Oreo fingerprint for Moto G4/G4 Plus athene

Here's a working fingerprint for Moto G4/G4 Plus with 8.1.0 build OPJ28.111-22 (released November 2018) that fixes a false ctsProfile (and 'Device not certified' by Google Play Store) after updating to build OPJ28.111-22-1 (released May 2019). Both builds have December 1, 2018 security patch.

This line came from build.prop while running OPJ28.111-22:

ro.build.thumbprint=8.1.0/OPJ28.111-22/532da:user/release-keys

And getprop reported:

motorola/athene/athene:8.1.0/OPJ28.111-22/532da:user/release-keys

After updating to the newer OPJ28.111-22-1 the fingerprint was saved in /sdcard/printslist as:

Motorola Moto G4 (8.1.0)=motorola/athene/athene:8.1.0/OPJ28.111-22/532da:user/release-keys

[MENTION=4667597]Didgeridoohan[/MENTION] -- Perhaps this 8.1.0 fingerprint for Moto G4 could replace 7.0 Nougat in your pre-configured prints.sh script. Thanks for an important module and its excellent documentation!
[Magisk] Didgeridoohan:
If the app depends on Play Store certification, then it doesn't matter if you clear data for it if SafetyNet isn't passing. It'll report uncertified unless you pass CTS.
[Magisk] DerNetzreporter:
Sorry, my fault.

With xiaomi a1 v9 fingerprint saftynet works. And Pokemon go starts. But no Ryanair.

After that I tried the pixel fingerprint. With this cts fails.
[Magisk] Didgeridoohan:
Just stick with the Tissot print...
[Magisk] pmatj:
OK, I tried a couple of different thinks but now I'm back at this point. I'll send some logs concerning the issue with post-fs and not booting, but just for now, the fingerprints for

Huawei P20 Lite

EMUI 8.0.0

.\adb shell getprop ro.build.fingerprint

HUAWEI/ANE-LX1/HWANE:8.0.0/HUAWEIANE-LX1/180(C432):user/release-keys

.\adb shell getprop ro.build.version.security_patch

2019-04-05

EMUI 9.1.0

.\adb shell getprop ro.build.fingerprint

HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L21/132C432R1:user/release-keys

.\adb shell getprop ro.build.version.security_patch

2019-05-05

Best regards,

Peter

UPDATE: I've attached my log
[Magisk] JhinCuatro:
Any clue the best way to avoid detection of apps? Sudohide and minminhide do this- but are [ed]xposed modules, and rather unstable sometimes..

It's weird when using "advanced root detection" that with zero permissions granted, it picks up on magisk..
[Magisk] Didgeridoohan:
Thank you. I see that there are a few things I need to fix for the boot stage settings, but meanwhile you can try resetting the module and trying again (with the default boot stages). This time though, skip the device simulation. It is a speciality feature that you shouldn't really enable unless you really need it since it has the potential to cause quite a few issues...

If you want to really hide certain apps from other apps that would be the way to go. I guess you could try using something like Island, but I can't advice you there since I've never used it.
[Magisk] jenslody:
Or if you prefer opensource software (as I do, especially for security related software) , I suggest using Shelter.
[Magisk] Didgeridoohan:
Thank you. Hadn't seen that one before.
[Magisk] tuvok1981de:
Helly Guys,

i have make something and have add the Modules but i have no idea what i must do on my GT-I9506 S4 to fix my Problems with the SafetyNet Check

https://prntscr.com/o7onem

https://prntscr.com/o7oneu

https://prntscr.com/o7oner

can anybody help me?
[Magisk] Didgeridoohan:
Since you're failing both CTS and basic integrity there's a good chance that this module can't help you at all... MagiskHide might simply not work on your device.

With this module, what you would do is to go to the "Edit device fingerprint" menu and pick the S4 from the list of included fingerprints and after a reboot SafetyNet should pass (if everything else is working as it should).

For tips on getting MagiskHide to work, here's some reading:

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

If you can't get things working, make sure to include logs with your next post:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#logs

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] tuvok1981de:
thank you for your help .. hm i have do this 1F1919 and 1F1920 but it will not work with this options

Is this possible, that the Magisk will general not run on the device or not on this ROM what i have?

I have also read, that Magisk will not work with older Kernel as 3.8 i think my LineageOS have 3.4 on the System
[Magisk] Didgeridoohan:
That's what I was suspecting... You should be able to see a message in your Magisk log along the lines of "mount namespace isn't supported on your device" if that is the case. MagiskHide simply can't work if the proper patches aren't added to your kernel (you can find the relevant information from my guide)...
[Magisk] tuvok1981de:
hm on the "Log" "Magisk" i can not found this Message

here is a Log File from the Manager

https://prnt.sc/o7rvoq

https://prnt.sc/o7rvz5

https://prnt.sc/o7rw74

https://prnt.sc/o7rwe5

https://prnt.sc/o7rwmo

https://prnt.sc/o7rwt6

https://prnt.sc/o7rx75

https://prnt.sc/o7rxci
[Magisk] Didgeridoohan:
All the help I can give you is already written in the guide I linked you previously. You need to troubleshoot and figure out why SafetyNet isn't passing on your device (or why MagiskHide isn't working, if that's the case). It can be triggered by many things (there's a list of examples in the guide).

This is now getting a bit off topic for this thread, so please continue in the general support thread.
[Magisk] JaNoxGER:
No updates

Hi, i tried this because my banking app stoped working for me.

After the Installation im not able to install new Lineageos Updates on my oneplus3 because its labeled with oxygen again.

Uninstalling the plugin didnt fix it for me.
[Magisk] Didgeridoohan:
More details needed... What is the actual failure, what's the error message, etc? Logs are also a great tool to include in any report about issues, so please do.
[Magisk] JaNoxGER:
It just says:"This rom is not compatible with oxygenos"

twrp thinks that i have oxygen installed but its lineageos.

All since ive tried this toll
[Magisk] Didgeridoohan:
The module is not active in TWRP, so it would have nothing to do with that.
[Magisk] JaNoxGER:
But the tool changes system parameter?

Maybe it changed back my info to oxygen what it should be from factory
[Magisk] Didgeridoohan:
Completely systemlessly, that's the point of doing this with Magisk. And when you boot into TWRP Magisk isn't loaded at all, so neither are any of its modules.

If you want I could take a look at the recovery log for you, to see if there's any hint as to why it happens.
[Magisk] JaNoxGER:
I uploaded it.

Thx
[Magisk] Didgeridoohan:
I believe you've misread the error message. This is what it states:

You simply need to first flash an up-to-date modem firmware. You'll find it in your device's forum.
[Magisk] JaNoxGER:
OMG. Thank you!

I totally misunderstood that, will try the update with your tip!
[Magisk] ipdev:
Just some updates.

Looks like 8.1.0 is actually dead.

R.I.P. Pixel C. - Google can now finally deny your existence. ;)

Note to those without a Pixel C.

Google has pretty much removed Pixel C from almost every one of their sites. It's not even on the EOL page, even the original Google Nexus is.

Pixel(s)

No more Pixel C.

Essential PH-1.

OnePlus 5T and 7 Pro.

Did not get a chance to test 7 Pro.

Xiaomi Pocophone F1.

Cheers.
[Magisk] Didgeridoohan:
Awesome! Got a whole bunch of prints submitted by friendly users, waiting to be put on the list. Gonna try to get them all checked out and added in the next couple of days.

:good:
[Magisk] x86cpu:
ASUS Zenfone 6 latest update.

Asus Zenfone 6 (9.0)=asus/WW_I01WD/ASUS_I01WD:9/PPR2.181005.003/16.1210.1906.156-0:user/release-keys__2019-06-01
[Magisk] RokCruz:
Hey, thanks for your hard work!

Can you add this fingerprint from Moto G6+ ? I'll really appreciate it!

motorola/evert_amx_n/evert_n:9/PPWS29.116-16-6/5cbfe:user/release-keys
[Magisk] Didgeridoohan:
Thank you, but I also need the security patch date that corresponds to that print.
[Magisk] RokCruz:
Sorry o completely forgot about that

This is the date: May 1 2019
[Magisk] JERRYZKT:
You can use the fingerprint of samsung s10 plus (9) to pass the cts and playstore verification, I have succeeded. Better backup the original fingerprint in advance in case of any issue.
[Magisk] Lalit@1999:
Can you add Moto g5 finger print released on February 8.1.0 Oreo ? Thanks in Advance
[Magisk] Didgeridoohan:
And for reference:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] cuongnguyenadt:
I have exactly the same problem. Could you pls help. I installed Magisk and Magiskhide props v3.5.2 in secondary rom dual boot but it sound like the module doesn't works due to of mouting problem. If you could provide a script to resolve it. I would much appreciated.
[Magisk] Didgeridoohan:
First of all, update to the latest version of the module please. It's always harder to provide support on old releases, so I really don't want to...

Second, I need info or I can't help at all. Logs.
[Magisk] cuongnguyenadt:
https://drive.google.com/open?id=1Uo6uA-nCIveee9lL9wdKxTFDtCIuJKj0

https://drive.google.com/open?id=1--HI-Uu6ID1s-TlLaC0dNBQnMm26JNIb

Thanks for your prompt response. The reason is that i got bootloop everytime after upgrading to Magisk 19. So i will keep using Magisk 18.1. And the old version 3.5.2 is the latest version for Magisk 18. At this stage i can't find a way to flash patched zip file (such as Magisk modules or Magisk 19.3 zip due to error 1 - mouting problem in TWRP). It is not the case if the rom is primary as my currently rom is non primary (dual boot patcher with Magisk 18.1 installed but i'm assume all magisk modules don't work). I installed MagiskHide props 3.5.2 successfully but everytime go to Terminal it keeping say that props not found as a thread in page 4-5. I'm trying to provide some screenshots...

Please note that. i was tried some methods to fix error 1 in TWRP for flashing zip files for Secondary rom but it doesn't work (patch boot.img). If you still need the logs i will try to grab them. Also trying to upload some screenshots. I'm looking a way such as a script that can be fix this can be mount system to bin/xbin folder.
[Magisk] Didgeridoohan:
[MENTION=7506794]cuongnguyenadt[/MENTION] Yes, I need logs or I wouldn't have asked for them...
[Magisk] cuongnguyenadt:
Magisk install log: sry i have no idea to attach the log as attachment

https://drive.google.com/open?id=1-NewzgJ-K8dOcJFk0UBDWNiwxce3GHHr

Could you please let me know how to get propsconf_install log, propsconf log and propsconf_last log?

Thanks again bro
[Magisk] Didgeridoohan:
They're stored in /cache (like it says in the docs I linked you earlier).
[Magisk] cuongnguyenadt:
propsconf_install.log:

https://drive.google.com/open?id=1-R9w8gu_dG9iypV0RhtebbPH_ZzbGnbm

i only found this log: propsconf_install.log which path i should try for others?
[Magisk] Didgeridoohan:
Everything looks fine, but the module isn't using xbin, as in the posts you were quoting earlier, it's using /system/bin. Doesn't tell us why it's not working though. Could simply be an incompatibility with the setup you have...

The fact that you're not seeing any other logs means the module isn't working as it should since you should get those of the boot scripts run. What about your Magisk log?
[Magisk] cuongnguyenadt:
Hi bro. Nothing in magisk log. What should i do now for further troubleshooting?

---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------

Yes. The screenshot i send earlier saying that it using system/bin. My mistake
[Magisk] Didgeridoohan:
How do you know what I'm looking for? I need to see it...
[Magisk] cuongnguyenadt:
Magisk log:

https://drive.google.com/file/d/1-8vdOGB0OF2YKIWu14Qe1Va578QJno-a/view?usp=drivesdk

It just showing nothing.
[Magisk] Didgeridoohan:
So you mean that it is completely empty? I can't check myself, since you haven't shared the file.
[Magisk] cuongnguyenadt:
Yes. It complely empty from my view either. I'm using log viewer from play store. May i know where the module was installed/stored? Can we call it via terminal?

Thanks for your help so far.
[Magisk] jcmm11:
/cache/magisk.log

Edit: you can also save it from the log viewer in Magisk Manager and it'll get saved to /Download/
[Magisk] cuongnguyenadt:
There is no magisk.log in that directory in my phone.

Screenshot:

https://drive.google.com/file/d/1-TdZPkNpHJwwo5p-yUIMij6JS5i-rEPj/view?usp=drivesdk
[Magisk] Didgeridoohan:
Sounds like Magisk isn't working well with your dual boot setup... I have no idea how that works so there's no way for me to troubleshoot that part.

All the module files are stored in the Magisk image (since you're on Magisk v18.1), which is mounted to /sbin/.core/img, and there's also a boot script in /data/adb/service.d. But from the sound of it neither the file mounting or the boot scripts are running. Without the boot script, the module is useless...

Without more to go on there's absolutely nothing I can do. Good luck.
[Magisk] cuongnguyenadt:
All good. I will try to reflash the rom.

Many thanks for your help.
[Magisk] Didgeridoohan:
Fingerprints list updated to v60

Finally had time to sit down and test all the fingerprints submitted recently. It was a bunch... :good:

The list is now updated to v60 and will be updated on your device when you run the props script, or by using the -f option or from the "Edit device fingerprint" menu if you've disabled automatic updates.

Shoutout and thanks to all the people that provided the prints in this update. In no particular order: [MENTION=6169969]RokCruz[/MENTION], [MENTION=2881807]x86cpu[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=9861591]pmatj[/MENTION], [MENTION=10002204]manjaroid[/MENTION], [MENTION=8403246]DessertArbiter[/MENTION] and pablomh over at GitHub.

Here are the new and updated prints:

New

Huawei P20 Lite

Motorola Moto G6

Motorola Moto G6 Plus

Sony Xperia XA2 Dual

Updated

Asus Zenfone 6

Essential PH-1

Google Pixel 1-3a, both variants

Motorola Moto G4

OnePlus 5T and 7 Pro

Xiaomi Pocophone F1
[Magisk] raystef66:
[MENTION=4667597]Didgeridoohan[/MENTION]

already another one updated for MI9 ;)

ro.build.fingerprint=Xiaomi/cepheus_eea/cepheus:9/PKQ1.181121.001/V10.2.27.0.PFAEUXM:user/release-keys

ro.build.version.security_patch=2019-06-01
[Magisk] Abaddon:
[MENTION=4667597]Didgeridoohan[/MENTION] I got one from Xiaomi Redmi K20 Pro

raphael:/ # getprop ro.build.fingerprint

Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.14.0.PFKCNXM:user/release-keys

raphael:/ # getprop ro.build.version.security_patch

2019-06-01
[Magisk] Didgeridoohan:
Fingerprints list updated to v61

Quick update with two fingerprints. The list will update when you run the props script, or by using the -f option or from the "Edit device fingerprint" menu if you've disabled automatic updates.

Thank you to [MENTION=5334294]raystef66[/MENTION] and [MENTION=3815496]Abaddon[/MENTION] for the provided prints.

New

Xiaomi Redmi K20 Pro

Updated

Xiaomi Mi 9
[Magisk] JarlPenguin:
New build fingerprint for Moto G5S (montana):

motorola/montana/montana:8.1.0/OPPS28.65-37-7-4/1dd5:user/release-keys

Description:

montana-user 8.1.0 OPPS28.65-37-7-4 1dd5 release-keys

Security Patch:

2019-02-01

or

motorola/montana_retru/montana:8.1.0/OPPS28.65-37-7-4/1dd5:user/release-keys

Description:

montana_retru-user 8.1.0 OPPS28.65-37-7-4 1dd5 release-keys

Security Patch:

2019-02-01
[Magisk] G U C C I:
[MENTION=4667597]Didgeridoohan[/MENTION], first of all. Thank you for this module! It seems like it'll help me get passed the Safetynet check. I pass the basicintegrity check but fail the ctsProfile one, so I would imagine that this will work for me. I have an LG V20 (H910) running LineageOS 16. When I run "props" in terminal emulator, it tells me that "The post-fs-data.sh module script does not appear to have run during boot" and I've tried completely uninstalling Magisk and all the modules (0smosis busybox included) and I'm still getting this message. I'll attach my log it generated. Any idea? I'd be grateful for the help! :)
[Magisk] Didgeridoohan:
Judging by your log, this applies:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#known-issues
[Magisk] G U C C I:
Ahhh I see, that's unfortunate. Thank you for your prompt response. Would I be able to disable it, run props, set it up, and then re-enable EdXposed?

Edit: I just tried it and it worked. Passing Safetynet completely now. Will try re-enabling EdXposed now and see if it stays that way. Fingers crossed!

Edit 2: It's working with EdXposed enabled! So I guess it's just a workaround to disable EdXposed when using "props" and then re-enable it right after you confirm you can pass Safetynet! Again, thank you so much for this module!
[Magisk] Didgeridoohan:
Yup, that's a viable workaround as long as you keep the default boot stage (don't switch to post-fs-data or late_start service since those are the scripts the get interrupted by EdXposed). Hadn't thought of that, actually (I don't use EdXposed). Thank you.

For anyone else reading, it should also be possible to use the configuration file during installation of the module. That way you don't even have to disable anything and everything will be set up right after the first reboot.
[Magisk] G U C C I:
I'm glad it worked! :) Happy that I can use the configuration file rather than having to do multiple reboots!
[Magisk] oslo83:
Huawei Mate 20 Pro

HUAWEI/LYA-L29/HWLYA:9/HUAWEILYA-L29/301C432:user/release-keys__2019-06-05
[Magisk] oslo83:
Here is maybe a bug in MagiskHide Props Config's custom props ;

These :

ro.huawei.cust.oma_drm

&

ro.huawei.cust.oma

can't both be set at the same time as module is seeing them as the same prop telling prop has already been set.
[Magisk] Didgeridoohan:
That is indeed a bug. I'll investigate and fix at the first opportunity. Currently on my summer break, but that might be a good project for rainy days...
[Magisk] Didgeridoohan:
Was a quick investigation, and honestly I don't know why I didn't foresee that issue while creating that part of the module...

Meanwhile there's an easy workaround for you, until I can fix it. Set the props in the other order, ro.huawei.cust.oma before ro.huawei.cust.oma_drm and it will work.
[Magisk] oslo83:
Enjoy !

Thanks for the tips, always happy to debug :D
[Magisk] bformz:
Hi, do I submit logs here?
[Magisk] Didgeridoohan:
If they have anything to do with the MagiskHide Props Config module, then yes.
[Magisk] bformz:
service.sh module scrip is not running

I have restarted a few times