yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Update to v2.6.0-v33

New release pretty quickly following the last (school's picking up again next week, so likely the last for a while again). I actually completely botched the v2.5.0 release, but apparently nobody noticed. :laugh: Fixed all that now (I hope). Anyway...

Turns out that the new feature I put into the last release to automatically update the security patch date for Android Pie fingerprints isn't specific for Pie. It's likely got to do with the crackdown Google did where uncertified Android builds after March 16 2018 won't be able to use Gapps. So I spent some time going through the whole list of fingerprints and added security patch dates where needed. While doing that I also got sick and tired of how incredibly slow the fingerprints list has become to load (there are currently 124 fingerprints in the list), so I fixed that too.

The discovery of the need for a matching security patch date for a lot of prints probably means that a whole bunch of the fingerprints I've rejected over the last 6 months or so has actually been valid and where just missing the proper matching patch date. If you know that you had supplied me with a fingerprint that I rejected because it didn't pass CTS on my device, please repost it with a matching security patch date and it's very possible that I can add it to the list.

Changelog

v2.6.0

Updated the fingerprints list to load much, much faster.

Added and updated fingerprints for Huawei Mate 10, Nextbook Ares 8A, OnePlus 3, 3T, 5 and 5T, and ZTE Axon 7. List updated to v33.

The new and improved SafetyNet fix turns out to be not only for Android Pie. Gone through the entire list and added security patch dates where needed.

Fixed some seriously botched code in v2.5.0.

As usual, small bug fixes and improvemnts.

No Yoshis where harmed during the making of this release.
[Magisk] .\\D-ZFR:
Updated from 2.5.0 to 2.6.0, and safetynet not pass and fingerprint can't be change. But it works on 2.5.0. xiaomi mix 2s
[Magisk] Didgeridoohan:
As usual when reporting about issues, logs are mandatory.
[Magisk] .\\D-ZFR:
I reinstalled 2.5.0 it works normally. It's ok. I'm good with 2.5.0 for now
[Magisk] Didgeridoohan:
But if there is an issue with v2.6.0, I would very much like to know since I have not encountered any such issues when testing v2.6.0 prior to release. This is a community after all and I would very much appreciate your help.
[Magisk] .\\D-ZFR:
Ok. I'll update to 2.6.0. I'll post log later
[Magisk] .\\D-ZFR:
Here's the log
[Magisk] NPriyo:
Same issue with me. Module is showing that fingerprint is applied, but the device is recognising inbuilt fingerprint. The result is CTS profile check failure.

Device - Asus Zenfone Max Pro M1, Android 9.
[Magisk] 0n3-70uch:
Hi, I confirm this issue.

Bye the way [MENTION=510787]Developer[/MENTION]: Thanks for your work. Nice module.
[Magisk] kunaldas65:
Yup same issue
[Magisk] Didgeridoohan:
Update to v2.6.1-v33

Quick fix for the props not setting issue... Thank you all for reporting. Let's hope this one works. :good:

Changelog

v2.6.1

Small fix (revert really) for possible issue with setting prop values (including fingerprint).
[Magisk] 0n3-70uch:
Hi, very fast thanks. But still the same problem:

https://drive.google.com/file/d/1EMZfIk4i8yA10JupoChl-awWg7mRSStg/view?usp=drivesdk
[Magisk] PHiDi:
2.6.1 changing the fingerprint is working again. Thanks for the quick fix.
[Magisk] NPriyo:
Fingerprint is getting applied now, but CTS is still failing.
[Magisk] Didgeridoohan:
Update to v2.6.2-v33

Last one for today, even if it doesn't work. Let's hope it does this time...

Changelog

v2.6.2

Another quick fix. Keep 'em coming...
[Magisk] 0n3-70uch:
Yeah everything fine now. Thank you.
[Magisk] .\\D-ZFR:
it works with this version now. great job. thanks
[Magisk] Albon98:
Huawei P9 Plus, android 7, security patch: July 2018.

HUAWEI/VIE-L09/HWVIE:7.0/HUAWEIVIE-L09/C432B387:user/release-keys

Thank you for the great job that you are doing :good:
[Magisk] ansabhailte:
Still fails?

I followed the instructions but cts profile still fails. I have attached the logs.
[Magisk] Didgeridoohan:
Your log shows that everything is working as it should, so you have some other issue. Is Basic integrity passing?

Have you looked through the module documentation on what to do if things don't work as expected? This part is particular to your case:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] ansabhailte:
Yes, BasicIntegrity passes, and I went through the documentation. How can the logs say everything's good when MM shows a red X for cts profile? haha
[Magisk] Didgeridoohan:
Because the CTS Profile and Basic Integrity checks for different things. The ROM you're using might have some kind of other su integration that is interfering, there might be remnants on your device from previous modificatinos that are incompatible with SafetyNet, there might be an app on your device that triggers it. There are a whole number of reasons...

There's nothing in the logs suggesting that the module has failed. The fingerprint and security patch date are both set properly. Ergo, the most likely explanation is that there is something else going on. If you find out what, please report back. It would be interesting to know.
[Magisk] ansabhailte:
Is there a list somewhere of apps that trip SafetyNet? The only one I've seen mentioned is AdAway which I removed. I also flashed the su remover for lineageos before installing magisk. I have MicroG and DroidGuard Helper installed if that helps.

---------- Post added at 02:55 PM ---------- Previous post was at 02:40 PM ----------

Wait I have an unlocked bootloader, it gives that 5 second warning. Would that be the problem?
[Magisk] Didgeridoohan:
It's possible that the su remover could have left something behind. Ask in the ROM thread.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Magisk_can_hide
[Magisk] martyfender:
Do you mean the verification check or dm_verity check at boot? Normally Magisk patches your boot.img to remove encryption and dm_verity check at boot. In the advanced settings on the front page of Magisk Manager, are those those 2 boxes unchecked? If I am not mistaken, If Magisk detects that the data partition is still encrypted, it will not disable it, unless the data partition is erased. Please clarify if I have this wrong, some how.
[Magisk] JoeDoe0:
I have AdAway 3.3 and the latest stable Magisk 17.1 / Magisk Mgr. 6.0.1 installed. Both SafetyNet checks are passed OK. :)
[Magisk] martyfender:
[MENTION=3477625]ansabhailte[/MENTION] I have used AdAway for a long time and it has never caused any problems in passing SafetyNet. I am using it's systemless hosts option. Your problems are caused by something else, such as Remanents of the root provided in your rom or some other system modification. If I am not mistaken, flashing UnSu.zip can help with removing a rom included su, in some cases.
[Magisk] kgursu:
Hi everyone,

I cannot add the contents of my printslist file into the fingerprints list. How to troubleshoot this?

Previous ROM used similar file without a glitch. Now, I'm using Slimroms.

Thanks.
[Magisk] Didgeridoohan:
Providing more details, logs and the file would be a start.
[Magisk] Aelsherbiny56:
Hi... I have cts profile false and basic integrity true

But the dev of my custom rom said that safety net checks are paypassed by default and ignore the the test when it gives me fail in safety net checks

Will any thing get affected if i edited my fingerprint to the certified one which comes in my stock rom ( i know what the current fingerprint messing) ?

---------- Post added at 05:57 PM ---------- Previous post was at 05:53 PM ----------

And another question .. when I install the module it downloads the BusyBox ... And i have already installed it on my device also from the magisk repo.. is there a difference

Or any interfering?
[Magisk] Didgeridoohan:
If the SafetyNet check in the Manager returns false, the check isn't being bypassed... And there should be no drawbacks from using your device's stock fingerprint.
[Magisk] Didgeridoohan:
No interference. I was using an internal copy of Busybox to make sure things would work as intended. But, that's changed in the current release, so please update.
[Magisk] kgursu:
Here are my logs, sir!! :)

What details do you need?
[Magisk] Aelsherbiny56:
Ok thanks sir
[Magisk] kullurumanoj:
Heyy [MENTION=4667597]Didgeridoohan[/MENTION] , Any update on how to fix CTS profile match on miui china roms ?? I disabled magisk hide and installed shell hide and both basic integrity and CTS profile are failing now. Attached the logs Thanks in advance
[Magisk] Didgeridoohan:
Details about what you mean about not being able to "add contents". And don't forget to provide the printslist file.

No idea... That's not something I have time to investigate at the moment (or in the near foreseable future). Somone that has access to a device with the issue would have to do the dirty work.

It sounds though like ShellHide isn't working as it should (basicIntegrity failing). You might want to check with [MENTION=8570610]JayminSuthar[/MENTION] about that in his thread.
[Magisk] kgursu:
Ok, last time I use your module, I can see my custom added devices on fingerprints lists. Does this changed into anything new? Otherwise, on my device this printslist contents were not added to your list. I tried all three files, first one with .bak extension presents the one that stays on changing ROMs recently, which I used before. It indeed has a blank line at start. The one with .1 extension refers to the list of fingerprints of both of my devices. The one without any extension is the one I tried to use recently, which has a fingerprint for that particular device only.

Shall all of them work well?

Thank you.
[Magisk] Didgeridoohan:
Ha! Face, meet palm. I'm a little slow sometimes, but the penny finally dropped...

My recent improvement to loading the prints list broke the custom prints list function. I will try to get an update out sometime this week.

Many thanks for the report.
[Magisk] jcmm11:
If this module is deleted it leaves 2 orphan scripts, one in post-fs-data.d and one in service.d

This leads to a question. Why generate these scripts instead of just using common/post-fs-data.sh service.sh? Especially since you're already using post-fs-data.sh to generate the scripts?
[Magisk] Didgeridoohan:
If the module is deleted those scripts will self-destruct. And if the module is disabled they won't run.

The service.d script is where all the module specific settings are kept. Whenever a module is updated, the module folder in the Magisk image is cleared out, but the script in service.d is left untouched (unless it needs an update, in which case the settings are transferred to the new file). The post-fs-data.d script is used to run some things as early as possible. And lastly, the post-fs-data.sh script is only a backup in case the scripts in post-fs-data.d or service.d are deleted for whatever reason.

Some of the code I have in there doesn't always make sense, but the main reason for me to make modules like this is to test ideas (I have tons of modules that have never seen the light of day). Sometimes they work, sometimes they don't... If they work I usually leave them be, unless there are compelling reasons to do things differently.
[Magisk] Didgeridoohan:
Update to v2.6.3-v34

Bugfix release. Yay...

This one is for [MENTION=8600843]kgursu[/MENTION]. With v2.5.0 I greatly improved the loading speed of the fingerprints list, but I also happened to break the custom fingerprints list function. Fixed, changed and optimised it a bit. The custom fingerprints will now be loaded under the category "Custom" in the fingerprints menu.

Also added a couple of fingerprints to the list. Have been neglecting to thank the providers for a while. Sorry about that everyone... Today's fingerprints where supplied by [MENTION=9131926]Albon98[/MENTION] and [MENTION=453495]JEANRIVERA[/MENTION]. Thanks guys!

Edit: Did a small typo just prior to release. Fixed that now, but I won't make another release... Just redownload.

Changelog

v2.6.3

Fixed custom fingerprints list that broke with the fingerprints list optimisation in v2.5.0.

Added fingerprints for Huawei P9 Plus and HTC U12 Plus. List updated to v34.

Minor improvements.
[Magisk] kgursu:
Thank you. I'm not completely sure, that you include my custom fingerprints on your official list, because there are too many Asus Zenfone 2 Laser versions, mine was as mentioned ZE500KL or as another description: Asus Zenfone 2 Laser 5 (5 inch version), mentioned as Z00ED. Also, my other device has different variants, I have D6503 of Sony Xperia Z2, in short "sirius". You could add them too, if they are not there. As a side question: Why not adding these short names to your list, as a precaution? Thanks again... :o
[Magisk] EinderJam:
Hi, I noticed that I have a device which is not included in this module, so here's the fingerprint :

Device : Huawei P9 Lite VNS-L31 (3GB RAM version)

ROM from which the fingerprint is extracted : C432B414 , Android 7.0 (European ROM), android security patch level : June 1st 2018

Fingerprint : HUAWEI/VNS-L31/HWVNS-H:7.0/HUAWEIVNS-L31/C432B414:user/release-keys
[Magisk] Didgeridoohan:
Getting more variations of different devices on the fingerprints list is on the to-do list, but way, way down on the priority order. Some manufacturers have so many different variations of their devices that it just becomes ridicilous at some point. Keeping track of them all just takes too much time (time that I don't have). So far I just haven't bothered... That might change, or it might not (I haven't decided yet).

The above is one of the reasons I make it relatively easy to add your own fingerprints in the module with the custom prints list file. I hope it works for you now...
[Magisk] zaqm:
Hi, can you tell me which files should I modify to change the fingerprint version manually in Android Pie?
[Magisk] bhatianirudh2910:
Google pay is detecting root even after using magisk hide
[Magisk] skdubg:
Google pay doesnt see your root

you need it hided and SafetyNet passed in all options
[Magisk] cooltech786:
I just installed this - got the fingerprint installed for my Pixel XL and now Magisk is passing everything, but Google Pay is still detecting something odd and Chase Pay is detecting root. Is that because of an ongoing issue with the fingerprint or something else?
[Magisk] Didgeridoohan:
General root hiding tips:

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] kgursu:
This one fixed my issue, thanks a lot!!... :good:
[Magisk] hyborian:
Thank you very much, Didgeridoohan !

Worked perfectly on my 4 phones without a problem, pass both safetynet. I just selected a device model close to my model, with the right Android version, and voila, success.

Must have app.
[Magisk] Predatorhaze:
last build,fingerprint dont work on axon 7
[Magisk] skdubg:
it does work!
[Magisk] Predatorhaze:
on my device,google store still not certified.

with 7.1.1 fingerprint all fine
[Magisk] Didgeridoohan:
Play Store certification is irrelevant. Does the device pass the CTS profile check? If it does and the Play Store still is uncertified, all you need to do is to clear data for the Play Store and reboot.

Actually covered in the documentation (which no-one ever bothers to read):

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf#the-play-store-is-uncertified
[Magisk] jenslody:
I write documentations for my stuff at work and I always asked me, why I do that. Nearly no user reads it.
[Magisk] aouerfelli:
Just letting you know that I've read the wiki and it's answered all the questions I had, so at least your time spent writing it has not completely been in vain.
[Magisk] Didgeridoohan:
I've written so many unread texts over the years... But, somtimes it's worth it just to be able to say: RTFM! :laugh:
[Magisk] jenslody:
I dp it often, and last week I was able to help a user fix an error via phone by reading my own docu, so I could tell him where to look for possible errors.

So it is not completely useless, and I do it at work and get paid for it :laugh: .
[Magisk] HD_Lutze:
6.2.3 v34 _mi mix 2s with global beta 8.10.25 cts profile false ...

with 10.0.4.0 stable is working ...

//solved ... update fingerprint via emulator and now its fine ?!
[Magisk] jbardi:
I have finally found a combination of fingerprint and security patch date that match for the Xiaomi Pocophone F1 to pass ctsProfile:

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

Security Patch Date: 2018-08-01

Until this is added, create the printslist file in the root of Internal Storage with the following line in it:

Xiaomi Pocophone F1=Xiaomi/beryllium/beryllium:8.1.0/OPM1.171019.011/V9.6.22.0.OEJMIFD:user/release-keys__2018-08-01

Then you can find it under the "Custom" category in MagiskHide Props Config
[Magisk] cmstlist:
My Xperia X Compact with Magisk is passing SafetyNet fine, however the CTV GO app has started detecting root as of the latest update.

Logcat: D/BellMedia(16604): (ca.bellmedia.lib.shared.security.RootDetection:107) Found Dangerous Property: [persist.sys.root_access]: [3]

Can this module help me spoof that property so that apps like CTV GO won't see it?
[Magisk] jcmm11:
Possibly. The persist.sys.root_access is curious though. I don't know if that's what it's detecting or if it creates it to tell itself it found root. I would definitely delete that (you can find it in /data/property/) after applying any changes from this module and before trying your app again. (I'd also delete data and cache from the app)

Are you running a custom Rom? If yes then this module may help, if stock then it's probably something else.
[Magisk] Didgeridoohan:
Fingerprints list updated to v35

Added a few fingerprints. Thank you to [MENTION=8176862]EinderJam[/MENTION], [MENTION=624848]jbardi[/MENTION] and [MENTION=8350043]gloeyisk[/MENTION].

Huawei P9 Lite (7.0)

Xiaomi Pocophone F1 (8.1.0)

Xiaomi Redmi 3/3 Pro (5.1.1)

The list will automatically update when you run the props command, or (if you've disabled automatic updates) by using the -f option (run -h for details) or in the fingerprints menu.
[Magisk] cmstlist:
Thanks I didn't realize it was just a file in data. Deleted the file, rebooted, and now CTVGO isn't complaining anymore. Root still works and all.

I wonder if it's a temporary property that was needed as part of a rooting process. And yes I'm on stock aside from the fixes needed to kernel for root on this thing.
[Magisk] Notonlyeyes:
Update list

Hi [MENTION=4667597]Didgeridoohan[/MENTION] , thank you for your work...

Updating list Fingerprint for Huawei P8 Lite 2017:

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/386(C432):user/release-keys

Security Patch Date: 2018-09-01

I tried the test it's working

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/386(C432):user/release-keys__2018-09-01
[Magisk] jcmm11:
I have no clue where that property came from. Just for the record all persist. properties can be found in /data/property/ That's what makes them persist - you only need to run a setprop command once and the property persists through reboots. You can also directly edit values instead of using setprop command again.

Edit: it seems that property was created by phh's superuser. Haven't found anything else that uses it. How did you root this device?
[Magisk] Didgeridoohan:
That property can be traced all the way back to koush superuser, I believe.
[Magisk] cmstlist:
I rooted it using instructions specific to Xperia devices. A modded kernel was involved. The original instructions suggested using Superuser but I went with Magisk instead. It's possible that during one of my intermediate attempts I did use Superuser and that left a trace.
[Magisk] Firestone_cz:
Hello to the community. Is there any option how to install MagiskHidePropsConf module into beta of Magisk v17.3?
[Magisk] Didgeridoohan:
I'm not sure if I follow you...

The current release of MagiskHide Props Config is fully compatible for installation on all releases after Magisk v17.0. There's nothing special that needs to be done for the Magisk beta or Canary releases. Install from the Magisk Managers Downloads section.

If you're having some kind of issue you might want to provide more details, and possibly logs.
[Magisk] aouerfelli:
I don't know about you, but the first thing I do when I come to a thread is to read the original post.
[Magisk] Firestone_cz:
Here is the log. I try to install via TWRP or Magisk Manager but I'm failed.

I install Magisk v14.5 via TWRP without adding this module, install latest beta version of Magisk and after that install latest Magisk beta version.
[Magisk] Didgeridoohan:
Your Magisk installation seems broken. Reinstall Magisk...
[Magisk] Firestone_cz:
OK than. Uninstall Magisk and install latest beta Magisk with module at the very same time and looks fine :)

I guess that I have to solve fingerprint to my device (JiaYu S3 with custom ROM) to pass the ctsProfile? I try Improved hiding function but I'm failed.
[Magisk] Didgeridoohan:
Not necessarily:

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint

If you do find a fingerprint, please share it so I can add it to the module.
[Magisk] Firestone_cz:
So if I guess right I can use fingerprint from any other device to pass safetynet?

I will ask for proper fingerprint to my device at our device's forum. If I have a luck I will post it here.

Anyway can I change fingerprint from one to the other one when I find the right one to my device after a some days for example?

Many thanks for your time and useful helps to newbie.
[Magisk] Didgeridoohan:
Shouldn't be any worries...

I took a quick look in the JiaYu S3 forum and this would be a good candidate for extracting a fingerprint:

https://xdaforums.com/showpost.php?p=61387344&postcount=3358

Here are some instructions on how to go about it:

https://github.com/Magisk-Modules-R....md#the-stock-romfirmwarefactory-image-method
[Magisk] .\\D-ZFR:
Update latest pixel 3 fingerprint PQ1A please ?
[Magisk] ipdev:
I was downloading November factory images. (Nexus 5x and 6p)

I do not have a Pixel but I kinda use 2XL (taimen) image.

Was catching up in threads while doing it so, I grabbed blueline and crosshatch also.

Unpacked the boot.img (recovery.img incase of 5x and 6p) and here is what we get from prop.default

ro.bootimage.build.fingerprint=google/blueline/blueline:9/PQ1A.181105.017.A1/5081125:user/release-keys

ro.build.version.security_patch=2018-11-05
ro.product.model=Pixel 3
ro.product.brand=google
ro.product.name=blueline

ro.bootimage.build.fingerprint=google/crosshatch/crosshatch:9/PQ1A.181105.017.A1/5081125:user/release-keys

ro.build.version.security_patch=2018-11-05
ro.product.model=Pixel 3 XL
ro.product.brand=google
ro.product.name=crosshatch

ro.bootimage.build.fingerprint=google/taimen/taimen:9/PQ1A.181105.017.A1/5081125:user/release-keys

ro.build.version.security_patch=2018-11-05
ro.product.model=Pixel 2 XL
ro.product.brand=google
ro.product.name=taimen

ro.bootimage.build.fingerprint=google/bullhead/bullhead:8.1.0/OPM7.181105.004/5038062:user/release-keys

ro.build.version.security_patch=2018-11-05
ro.product.model=Nexus 5X
ro.product.brand=google
ro.product.name=bullhead

ro.bootimage.build.fingerprint=google/angler/angler:8.1.0/OPM7.181105.004/5038062:user/release-keys

ro.build.version.security_patch=2018-11-05
ro.product.model=Nexus 6P
ro.product.brand=google
ro.product.name=angler

ro.bootimage.build.fingerprint=essential/mata/mata:9/PPR1.181005.076/390:user/release-keys

ro.build.version.security_patch=2018-11-05
ro.product.model=PH-1
ro.product.brand=essential
ro.product.name=mata

Sorry this post got a little long. Added HIDE tag and PH-1 also.

Cheers. :)