yashsingh1/xdaforums huggingface dataset:
[Magisk] danrm619:
Can I pass CTS Profile & BasicIntegrity with this module in a Moto G4/G4 Plus?
[Magisk] skullkid383:
Yes that's what this module is meant for
[Magisk] Didgeridoohan:
Well... If you're not passing Basic Integrity, you've got other issues that this module can't solve. This module will only help you if your CTS Profile check returns false as a result of your device's fingerprint being uncertified (custom ROM).

Take a look in the Magisk Guide for more on also passing Basic Integrity.
[Magisk] terrorgen:
ah shucks... the reason of the bootloop, I found, is not the module, but the well known battery drain or the old battery itself that is not delivering. One of the two.
[Magisk] christian.arvin:
Z00l fingerprint

Thanks for this module it passed my device. :o:good:

DEVICE: Z00LD - (ZE550KL) 2GB Variant ASUS ZENFONE 2 LASER
ROM : Resurrection Remix N (7.1.2)

FINGERPRINT: Android Marshmallow (6.0.1)
Zenfone 2 Laser=asus/WW_Z00L/ASUS_Z00L_63:6.0.1/MMB29P/WW_user_21.40.1220.2179_20170803:user/release-keys
[Magisk] xhide:
Can i use any fingerprint for my device? Sorry if this is included in the op
[Magisk] abacate123:
I think so. But it's better to use your own stock build fingerprint.
[Magisk] spawnlives:
Hi

Since updating magisk from 16.3 to 16.4 cannot run module. Have tried uninstalling and re-installing but still the same. Have also tried an earlier version.
[Magisk] spawnlives:
Sorry sent without finishing will repost
[Magisk] spawnlives:
Hi

Since updating magisk from 16.3 to 16.4 cannot run module. Have tried rebooting, uninstalling and re-installing but still the same. Have also tried an earlier version. Module did work on 16.3. Magisk is workimg ok without any issues. This is the only magisk module installed.

My phone is a samsung s8 stock rom nougat 7.0 arm64

Canmot upload magisk debug log at the moment for some reason but if needed will try again as a seperate post.
[Magisk] Didgeridoohan:
It's likely caused by an issue with Magisk v16.4 I've seen reported elsewhere, also on a Samsung running Nougat. The late_start service doesn't run, and since this module relies on it quite heavily, that's an issue...

It's possible it's caused by the sepolicy changes in v16.4.

That other user updated to Oreo and things started working, so you can try to update or go back to Magisk v16.0 or v16.3.
[Magisk] Didgeridoohan:
Update to v2.1.5-v13

I dropped a small update a few hours ago. Finally had some time to also post about it...

Mainly it was an update to the fingerprints list, which I also just happened to find a small typo in, so that got updated again between the module updated and this release note... The current fingerprints list is v13 and if you've already updated the module to v2.1.5, the fingerprints list will update when you run the props command (or you can do it manually if you've disabled automatic updates). The other stuff is purely cosmetics and small improvements. It's likely it'll still break something though... :silly:

Edit: Oh yeah... I'm also currently investigating why some users have success with the USNF module, but not this one, and if I can do anything about it.

Changelog

v2.1.5

Show what device the currently set fingerprint is from.

Show what device the fingerprint you're about to set is from.

Fixed, updated and added a bunch of fingerprints, list v13. Thank you [MENTION=9129635]0LDST4R[/MENTION], [MENTION=6642823]christian.arvin[/MENTION] and [MENTION=7166349]turbolukex5[/MENTION].

Minor updates and improvements.
[Magisk] Goutham Ganesh:
there is an UPI app by Google in India, called Tez, it is not working lately even if safetynet is passed, has anyone managed to run Tez?
[Magisk] Didgeridoohan:
It's been discussed a lot, here's a link (and in many other threads, but best to keep it in one place. Read: it's OT, don't discuss it here please. :p):

https://xdaforums.com/apps/magisk/tez-app-custom-rom-root-device-t3722018

Summary of that thread: SafetyNet has to pass, but it also depends on the ROM.

I've been wondering if anyone has tested it with the "Improved hiding" feature from this module, and I've yet to see anyone figuring out what it actually detects.
[Magisk] ANDROID O:
Thanks dev

Working super fine , thanks dev
[Magisk] Didgeridoohan:
Fingerprints list updated to v14

Updated and added a few new prints to the list.

Added:

Google Pixel 2 (8.1.0).

Samsung Galaxy A8 Plus (7.1.1). Thank you [MENTION=7862303]zahidul.sifat[/MENTION].

Samsung Galaxy S3 Neo (4.4.4).

Samsung Galaxy S7 (8.0.0). Thank you [MENTION=7166349]turbolukex5[/MENTION].

Updated:

Google Pixel 2 XL.

As usual, the list will update when you run the props command, or manually update in the fingerprint menu if you've disable automatic updates.
[Magisk] tolis72:
Hi any solution for Xiaomi Redmi 5 plus (vince)?
[Magisk] Didgeridoohan:
I've started perfecting tracking down device fingerprints. Planning on updating the documentation about that at some point...

Spent a total of about 5 minutes tracking this one down and testing it:

xiaomi/vince/vince:7.1.2/N2G47H/V9.5.4.0.NEGMIFA:user/release-keys
[Magisk] 0LDST4R:
Here we go again,

Sony Xperia Z C6603 (5.1.1)

Sony/C6603/C6603:5.1.1/10.7.A.0.228/58103698:user/release-keys

Sony Xperia Z1 C6903 (5.1.1)

Sony/C6903/C6903:5.1.1/14.6.A.1.236/2031203603:user/release-keys
[Magisk] tolis72:
Thank you very much!
[Magisk] AhmadNaimHebat:
Hi, which is more important in selecting a fingerprint, same device or same android version?
[Magisk] Didgeridoohan:
You can use any fingerprint for any device really...

But if you have an Android 8.0 ROM, but there's only an Android 7.1.1 fingerprint available for the same device, there's no issue using the 7.1.1 fingerprint.

Using a different devices fingerprint will cause your device to seem like that device, which might have side effects. Couldn't tell you for certain though... Haven't really experimented with it.
[Magisk] Defforest:
Really interested with this module, so this should work like other Universal Safety Net Fix right?

Bypass safetynet to green result, does it support Redmi 4 Prime / Snapdragon 625 for now?

Because I saw you need specified fingerprint from some device
[Magisk] Didgeridoohan:
It's somewhat similar to USNF, since it also changes the device fingerprint. That module does a few more things though, and I'm currently looking into why that module works on some device/ROM combinations when this one doesn't (but there's so few hours in the day :eek:).

You can actually use any fingerprint that's supplied with the module, they've all been tested to be certified and should help pass SafetyNet on custom ROMs that doesn't pass the ctsProfile test.

Here's a fingerprint from the Redmi 4 Prime global stable ROM though. I haven't tested it yet, but if it does work I will add it to the current fingerprints list:

Xiaomi/markw/markw:6.0.1/MMB29M/V9.5.3.0.MBEMIFA:user/release-keys

You can test it yourself by entering it manually in the module settings.
[Magisk] Didgeridoohan:
Because of some issue with XDA, it's getting impossible for me to update the OP of this thread. Spent an hour refreshing the page just to edit it to the current info about moving the support thread...

New support thread can be found here:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

Locking down this thread... See you in the new one. :good:
[Magisk] Mezabaru:
I see Samsung S8 on the prop list but no S7, is there anything I can provide to help get support added?
[Magisk] Didgeridoohan:
You sure about that fingerprint? It does not work when I tested...

You can provide the stock fingerprint and I can then add that to the list:

getprop ro.build.fingerprint
[Magisk] moonranger98:
Thanks !!
[Magisk] Didgeridoohan:
The module can now be found in the Magisk repo and here's an update to celebrate.

v1.2.0

Now in the Magisk repo. Updated to match.

New fingerprint for Pixel 2, list v3. Thank you [MENTION=3694505]Telperion[/MENTION].

Show info when checking for fingerprint updates.

Minor changes and improvements.

All previous releases are now found on GitHub and only the current release is attached to the OP.
[Magisk] Mezabaru:
herolte:/ # getprop ro.build.fingerprint

samsung/heroltexx/herolte:7.0/NRD90M/G930W8XXS2DRA9:user/release-keys

There you go!
[Magisk] 0ther:
device:

Xiaomi Mi 5 / Mi 5 Pro

rom:

MIUI 9 Global Stable V9.2.1.0.NAAMIEK

fingerprint:

ro.build.fingerprint=Xiaomi/gemini/gemini:7.0/NRD90M/V9.2.1.0.NAAMIEK:user/release-keys
[Magisk] OldSilverFox:
herolte:/# getprop ro.build.fingerprint

samsung/heroltexx/herolte:7.0/NRD90M/G930FXXU2DRB6:user/release-keys

ctsProfile: true

basicIntegrity: false

SM-G930F
[Magisk] moonranger98:
Lenovo k6 power 7.0 stock rom. Is this the right. I haven't tried it through terminal commands.

ro.build.fingerprint=Lenovo/karate/K33:7.0/NRD90N/K33_S231_171114_ROW:user/release-keys

I have a query that I edited ro.build.fingerprint using kernel adiutor app and magisk is still showing CTS profile false. Is that a right way or am i doing something wrong

Also that ro.build.fingerprint of stock is applicable for custom roms with higher version or not.

Currently I am on 7.1.2 resurrection remix.
[Magisk] bonz_zzz:
Xiaomi Redmi 4 pro

ro.build.fingerprint=Xiaomi/markw/markw:6.0.1/MMB29M/V8.2.4.0.MBEMIDL:user/release-keys

ctsProfile : false

basicintegrity : false

i've tried to reset my fingerprint to xiaomi mi6 but no good, still false.

please help

magisk 16.
[Magisk] abacate123:
Try another fingerprint or another rom, also make sure to not use Xposed since it won't let you pass both checks.
[Magisk] Didgeridoohan:
Apart from what's stated above about Xposed, this module only has a chance of working if basic integrity reports true (read the OP/documentation).

For other MagiskHide/SafetyNet issues, take a look here (like it says in the OP/documentation):

https://www.didgeridoohan.com/magisk
[Magisk] Didgeridoohan:
Let me guess: you have Xposed and the No Device Check module installed.

This module should be unnecessary in such a case.
[Magisk] 0ther:
device:

Xiaomi Mi 5 / Mi 5 Pro

rom:

MIUI 9 China Stable ROM V9.5.1.0.NAACNFA

fingerprint:

ro.build.fingerprint=Xiaomi/gemini/gemini:7.0/NRD90M/V9.5.1.0.NAACNFA:user/release-keys

I just extract (both: Global Stable and China Stable) fingerprint line from build.prop in recovery .zip

Sorry but I don't know which one is certified... probably only the China fingerprint
[Magisk] Didgeridoohan:
From my quick test earlier it seems like the global print works fine.
[Magisk] Didgeridoohan:
Maintenance update.

v1.2.1

Fixed logic for checking the original prop values. Thank you [MENTION=6439974]abacate123[/MENTION].

New fingerprints (Xiaomi Mi 5, ZTE Axon 7), list v4. Thank you [MENTION=7787494]0ther[/MENTION] and [MENTION=4492889]-Duir-[/MENTION].

Minor fixes.

Install from the Manager or download from the OP.
[Magisk] Jaymin.0.1910:
[MENTION=4667597]Didgeridoohan[/MENTION],

I don't know if now been removed, but previously I read in the Magisk Modules documentation that the description of a module must match its id for Magisk Manager to recognize it as a module, which is missing in your GitHub repo, forgive me if been changed.:)
[Magisk] Didgeridoohan:
I must confess that I don't know what you mean. Could you clarify? Maybe link to the part of the documentation you're talking about...
[Magisk] Jaymin.0.1910:
It was in the Submit modules to the official Repo section in the older documentation, it's removed now, but all the modules still follow the standards, so I told you about this.
[Magisk] Didgeridoohan:
I'd still like a clarification though, since I still don't follow what description you're talking about. :p

I'm using the module template almost without modifications, so there shouldn't be any worries.
[Magisk] nos1609:
Xoaomi Mi 5S lastest global fingerprint

Xiaomi/capricorn/capricorn:7.0/NRD90M/V9.2.1.0.NAGMIEK:user/release-keys
[Magisk] traketto:
Sony Xperia XZ1 Compact G8441

Stock Rom Oreo 8.0.0 version: 47.1.A.12.119

Fingerprint:

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

---------- Post added at 06:08 PM ---------- Previous post was at 05:53 PM ----------

Samsung Galaxy S8+ SM-G955F

Stock firmware Oreo 8.0.0 version: XXU1CRC7

Fingerprint:

samsung/dream2ltexx/dream2lte:8.0.0/R16NW/G955FXXU1CRC7:user/release-keys
[Magisk] Jaymin.0.1910:
I meant the GitHub repository description
[Magisk] MoHuToP:
N910F

samsung/trltexx/trlte:6.0.1/MMB29M/N910FXXS1DQH9:user/release-keys
[Magisk] Didgeridoohan:
Ah yes. Now I see what you mean... I do enjoy when things are properly labeled and described, so I was a little triggered when I saw that the repo description hadn't transferred over. :laugh:

I had not seen that mentioned anywhere in the current docs though (but like you say, it was written in the old docs), and the module is available for download so I don't think it's an issue. Just in case, I'm changing it back though. :good:
[Magisk] 4Strings:
My contribution. Xperia Z5 7.1.1/2:

Sony Xperia Z5 (7.1.x)=Sony/sumire/sumire:7.1.1/N-MR1-KITAKAMI-170920-0229/1:user/dev-keys
[Magisk] ramabg:
This is the fingerprint of Xiaomi 5S Plus:

Hopefully my Banking app will finally be able to work again.
[Magisk] Toni Moon:
Works perfect in Leeco le pro 3 with the OnePlus 3T profile
[Magisk] Didgeridoohan:
Fingerprints list update to v5.

Added Samsung Galaxy Note 4. Thank you [MENTION=1946644]MoHuToP[/MENTION].

Added Samsung Galaxy S7. Thank you [MENTION=5146463]Mezabaru[/MENTION] and [MENTION=5469194]OldSilverFox[/MENTION].

Updated Samsung Galaxy S8 Plus. Thank you [MENTION=5169008]traketto[/MENTION].

Added Sony Xperia XZ1 Compact. Thank you [MENTION=5169008]traketto[/MENTION].

Added Xiaomi Mi 5S. Thank you [MENTION=1575315]nos1609[/MENTION]. Here you go [MENTION=7805160]FSLenviant[/MENTION].

Added Xiaomi Mi 5S Plus. Thank you [MENTION=4226577]ramabg[/MENTION].

Please note that there are way too many variants of all the different Samsung models... I will only add one working fingerprint for a module. If you want one for your specific variant, use the custom fingerprints list function.

The list updates when you run the props command.
[Magisk] Mahmoudinos:
That's work with both? Can fix this too?
[Magisk] Mahmoudinos:
Failed
[Magisk] Didgeridoohan:
Like it says in the OP, this module can help you if you fail ctsProfile but pass basic integrity. That's clearly not the case for you and you won't be helped by this module.

Like it's also stated in the OP, you can find further help with MagiskHide issues here:

https://www.didgeridoohan.com/magisk

If you have Magisk v15+ already installed, I suspect you simply have a broken Magisk installation. Likely the same reason MagiskHide isn't working. I'd try doing a reinstallation of the latest Magisk release (try the beta, currently v16.3). If that still doesn't work, go to the general support thread and provide lots of details and logs.
[Magisk] abacate123:
If you have xposed installed and activated, disable it or uninstall it. This module will fix the ctsProfile check, and has nothing to do with the basicIntegrity check, afaik.

Read the log written on your own screenshot, it says to use a magisk higher than v15, it literally explain itself.

Although if you're already using an updated magisk version already (which is the v16 nowadays) and you're still getting this error (which would be weird), then try to flash this module through TWRP.
[Magisk] thorin0815:
Because my Moto G4 failed SafetyNet CTS Profile with NPJS25.93-14-15 firmware I tried the fingerprint of the version right before and it worked.

motorola/athene/athene:7.0/NPJS25.93-14-13/3:user/release-keys
[Magisk] NIKKISLAYER7:
Stock nvidia Shield K1 (7.0) fingerprint:

nvidia/sb_na_wf/shieldtablet:7.0/NRD90M/1928188_1065.2559:user/release-keys
[Magisk] FSLenviant:
Never knew it's coming this fast !!

You're a lifesaver man, seriously [MENTION=4667597]Didgeridoohan[/MENTION] :))

Thank you so much for Capricorn Fingerprint ..

:D

God bless you in your lifes .. :)
[Magisk] Didgeridoohan:
Hi there.

I think you placed this post in the wrong thread. This one is more suited for it...

It's likely that you can fix your issue by using the fingerprint feature of this module.

Install the module, run the props command and pick one of the included fingerprints. Usually it doesn't matter if it doesn't match your device...

If you really want a different that match your device, there are instructions on how to find one in the docs.
[Magisk] rufk:
.

Hey thanks for that!

I restored my stock ROM, saved my fingerprint and am now heading back to Lineage and will modify my fingerprint to the stock one when I get there. Hopefully I can then pass SafetyNet!

Thanks :)
[Magisk] yoav1990:
Thanks a lot! The S7 fingerprint worked for my S7 Edge.
[Magisk] rufk:
PASSED! Sort of...

[MENTION=4667597]Didgeridoohan[/MENTION]

Thank you so much!

After following your instructions i now pass both sections of the SafetyNet test!

However, Netflix doesn't show up in the play store and says 'not compatible with your device' and blocks me when I open it.

I checked and play store confirms my device is 'certified'

Do you know what a solution to this is?

(I have edited most of the prop files, and masked the appropriate apps)

Thanks again!
[Magisk] Didgeridoohan:
That's not a root hiding or SafetyNet thing (so far, Netflix only uses the certification status of the Play Store for installation). There's likely something missing in your ROM. Try an older version of Netflix or ask for advice in your ROM thread.

By the way: Mind posting that fingerprint? I could add it to the fingerprints list in the next update...
[Magisk] rufk:
Fingerprint

Sure, I'll ask in my ROM thread.

Here's the fingerprint

(For Vodafone Smart Ultra 6)

Vodafone/P839V55/P839V55:5.1.1/LMY47V/20161227.134319.15534:user/release-keys

Thanks for the help!
[Magisk] lvbaal:
Fingerprint of my device with Safetynet passed on both checks:

DEVICE INFORMATION

NAME: Mate 10 Pro

MODEL: BLA-L29

CODENAME: HWBLA

MANUFACTURER: Huawei

────────────────

GOOGLE SAFETY NET REPORT

STATUS: PASSED

────────────────

BUSYBOX REPORT

STATUS: INSTALLED

VERSION: 1.28.2

PATH: /system/bin/busybox

PERMISSIONS: -rwxr-xr-x (755)

UID: root

GID: root

SIZE: 1.39MB

LAST MODIFIED: Apr 1, 2018, 9:09:32 PM

MD5: 738551AFDF67AB36A08A285051946BD4

SHA-1: 5B7C8649A98F0F38C495320E7A9FE807BB45CC56

────────────────

BUILD PROPERTIES

BOARD: BLA

BRAND: HUAWEI

CPU ABI: arm64-v8a

DISPLAY: BLA-L29(C432)

FINGERPRINT: HUAWEI/BLA-L29/HWBLA:8.0.0/HUAWEIBLA-L29S/137(C432):user/release-keys

HARDWARE: kirin970

HIDE PRODUCT INFO: false

ID: HUAWEIBLA-L29S

IS CONTAINER: false

IS EMULATOR: false

IS ENG: false

IS TREBLE ENABLED: true

IS USER: true

IS USERDEBUG: false

NO HOTA: false

PERMISSIONS REVIEW REQUIRED: false

PRODUCT: BLA-L29

SERIAL: AQH0217B23001461

SUPPORTED 32 BIT ABIS: armeabi-v7a, armeabi

SUPPORTED 64 BIT ABIS: arm64-v8a

SUPPORTED ABIS: arm64-v8a, armeabi-v7a, armeabi

TIME: 1520406423000

TYPE: user

Report generated using SafetyNet Checker on Google Play
[Magisk] Tecalote:
[MENTION=1861039]lvbaal[/MENTION]

Your information doesn't include the fingerprint (example see post: #61 - one before yours) - to find it out you can run in Terminal Emulator:

getprop ro.build.fingerprint

(see documentation which is linked in post #1)
[Magisk] OldSilverFox:
Deleted.
[Magisk] lvbaal:
Like I've noticed before, the XD app is cutting off pasted text after certain characters. Now it was the text after ¨(¨ behind ¨DISPLAY: BLA-L29 8.0.0.137¨ that was not pasted and why the info was incomplete. I have added the missing part on PC.
[Magisk] MeNoNoob:
Xiaomi Redmi Note 3 pro

Xiaomi/kenzo/kenzo:6.0.1/MMB29M/V8.2.1.0.MHOCNDL:user/release-keys
[Magisk] traketto:
Sony Xperia Z3 Tablet Compact SGP621

Stock Marshmallow 6.0.1 version: 23.5.A.1.291

Fingerprint:

Sony/SGP621/SGP621:6.0.1/23.5.A.1.291/3706784398:user/release-keys
[Magisk] andrasandhi:
Moto G5S Plus 7.1.1 (sanders)

ro.build.id=NPSS26.116-26-4 , security_patch=2017-10-01

ro.build.thumbprint=7.1.1/NPSS26.116-26-4/4:user/release-keys
[Magisk] nalajcie:
Xiaomi Mi6 (sagit) - Android 8.0.0

Fingerprint from MIUI GLOBAL ROM V9.2.3.0.OCAMIEK

(works with current MIUI DEV builds based on Android 8.0.0, fingerprint from Android 7.1.1 made ctsProfile failure)

Xiaomi/sagit/sagit:8.0.0/OPR1.170623.027/V9.2.3.0.OCAMIEK:user/release-keys
[Magisk] orjanraberg:
I cannot get value I set with the MagiskHide Props Config command to stick on my Xperia Z5 running LineageOS 7.1.2

The original fingerprint of my device is the following:

Sony/lineage_sumire/sumire:7.1.2/NJH47F/c0c2dacae4:userdebug/release-keys

I have tried to set the fingerprint to the following (Xperia Z5, found in the thread):

Sony/sumire/sumire:7.1.1/N-MR1-KITAKAMI-170920-0229/1:user/dev-keys

And the following (for Xperia Z5 Dual, my actual device):

Sony/sumire_dsds/sumire_dsds:7.1.1/N-MR1-KITAKAMI-170609-1025/1:user/dev-keys

But the setting doesn't take effect. Instead props reports that the fingerprint is set to the original value (by this module). It doesn't help to reboot or use the other settings in the props command

What I doing wrong?

Log files (attached) don't give any clues to me, it all looks fine there.
[Magisk] Didgeridoohan:
Thanks for reporting. That's likely caused by a bug I've already homed in on for the next release. I'm also working on a couple of new features, but hoping to have a new release in the next few days.
[Magisk] orjanraberg:
OK, thanks for the reply, I will wait for the new release then!
[Magisk] spoof123:
santoni:/ $ getprop ro.build.fingerprint

Xiaomi/santoni/santoni:6.0.1/MMB29M/V8.5.4.0.MAMCNED:user/release-keys.

Xiaomi redmi 4x
[Magisk] Zincoshine:
I have a retired Samsung galaxy S6 and would like to donate its fingerprint. How do I do this?
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

Don't worry, your device doesn't become unusable... The fingerprint is ROM specific, not for each individual device.
[Magisk] orjanraberg:
Sony Xperia XZ=Sony/F8331/F8331:8.0.0/41.3.A.2.99/1455830589:user/release-keys

Sony Xperia XZ on stock Android 8.0.0
[Magisk] Zincoshine:
Samsung Galaxy s6 international fingerprint:

samsung/zerofltexx/zeroflte:5.0.2/LRX22G/G920FXXU1AOD4:user/release-keys
[Magisk] jackebuehner:
htc/HTCOneM10vzw/htc_pmewl:6.0.1/MMB29M/774095.8:user/release-keys

HTC 10 running AOSiP 8.1 Oreo
[Magisk] uodii:
Sailfish April 2018 build

google/sailfish/sailfish:8.1.0/OPM2.171019.029/4657601:user/release-keys

Also, terminal reports the spoofed fingerprint, but Samsung pay is still able to detect directly from the buildprop. Any way to figure out how they are circumventing this?
[Magisk] Didgeridoohan:
Detecting the fingerprint from build.prop? Hm... I haven't included the fingerprint in the prop file modification function, but I'll look into adding it.
[Magisk] jasonkx:
Can you add the OnePlus 5 Oreo?
[Magisk] Didgeridoohan:
It'll be in the next update. I'm still testing some new sweet features and waiting for that to also update the fingerprints list. Meanwhile, here you go (OOS 5.0.4):

OnePlus/OnePlus5T/OnePlus5T:8.0.0/OPR1.170623.032/02040656:user/release-keys
[Magisk] orjanraberg:
Sony Xperia X Performance:

Sony/F8131/F8131:8.0.0/41.3.A.2.99/1455830589:user/release-keys
[Magisk] Didgeridoohan:
That's the exact same fingerprint you provided for the Xperia XZ earlier: https://xdaforums.com/showpost.php?p=76176179&postcount=76

:confused:
[Magisk] orjanraberg:
Sorry, managed to paste the wrong fingerprint. Updated the post now. It seems the fingerprint is almost identical though. The two phones do have the same software version so I guess that is how it is supposed to be.
[Magisk] kaiiori:
support for my Xperia X device

Xperia X

F5121

8.0.0

34.4.A.2.32

Sony/F5121/F5121:8.0.0/34.4.A.2.32/1455699507:user/release-keys
[Magisk] Didgeridoohan:
[MENTION=7919143]Yeshu_bablu[/MENTION] You're posting in the completely wrong thread for your query...

But, give this module a go. It might help.
[Magisk] Yeshu_bablu:
I'm sorry. My condition right now is that I am on V16.3 and I cannot solve the CTS issue. Sorry for the trouble caused.
[Magisk] Didgeridoohan:
I know... This module was created to deal with that kind of issue.