yashsingh1/xdaforums huggingface dataset:
[Magisk] Yeshu_bablu:
I guess this won't work on my Moto G5 plus. Will it? I am very new to these stuff. I'm right now on V16.3. Can you give clear step by step process for creating the fingerprint for my device?
[Magisk] atarek:
Samsung Note 3 Fingerprint

Hello,

Thanks for your great effort :)

Samsung Note 3 (n9005) running MM 6.0.1:

samsung/greatltexx/greatlte:7.1.1/NMF26X/N950FXXU1AQHA:user/release-keys

regards,

Ahmed
[Magisk] Didgeridoohan:
You can actually use whatever fingerprint that is certified, it doesn't have to be for your device. I do have the G5 Plus available though, and it will be in the next update. I'm not finished with testing all the new features yet though...

Meanwhile, here's the fingerprint. Select the "Device fingerprint" (1) when you've run the props command and then enter this:

motorola/potter_n/potter_n:7.0/NPNS25.137-33-11/11:user/release-keys
[Magisk] orjanraberg:
I am quite sure this is the fingerprint for Sony Xperia Z5 Dual:

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

I own the phone myself but it is running Lineage OS now so I cannot check myself. Maybe someone can confirm?
[Magisk] Yeshu_bablu:
I'll wait for the update. I'm using a custom ROM. So..should I reflash my stock NPN 7.0 and flash this...then upgrade to my custom ROM? As you said...you have to finish testing it, I'll wait. I'll subscribe to this thread and wait for the new update. Thank you so much for your hardwork.
[Magisk] Didgeridoohan:
I tested that fingerprint on my Nexus 6 and it does not work there (I only add fingerprints that can work on any device).

Edit: I'm curious about the "dev-keys"... That doesn't sound like a stock, certified, ROM.
[Magisk] musiXelect:
Samsung Galaxy Note 5 SM-N920C

samsung/nobleltejv/noblelte:7.0/NRD90M/N920CXXU3CQH6:user/release-keys
[Magisk] orjanraberg:
Yes that is strange. Does the following work for you:

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

Someone posted that in this thread as being the fingerprint for Xperia Z5 (non-dual I presume).
[Magisk] Didgeridoohan:
Yeah, I test all prints posted. That one did not work either.
[Magisk] orjanraberg:
Bummer. I need a working fingerprint for Z5 as that is my only phone that doesn't pass the CTS profile test.

I will see if I can find one in the Z5 sections.
[Magisk] jhobc:
Zuk Z2 Pro

ZUK/z2_row/z2_row:7.0/NRD90M/2.5.435_170525:user/release-keys
[Magisk] borito215:
Does anyone have fingerprint for Xiaomi Redmi Note 4x?

Maybe silly question, can I use certified fingerprint for Xiaomi Redmi 5 for the 4x?
[Magisk] Didgeridoohan:
You should be able to use any of the included fingerprints, if you can't get a hold of your device's specific one.
[Magisk] borito215:
You are correct. I just used the Xiaomi Mi 5 on my Xiaomi Note 4.

SafetyNet Test previously failed on CTS profile match but now showing as success so status is Passed.

Thank you to all :good::good::good:
[Magisk] Felix Siahaan:
[MENTION=4667597]Didgeridoohan[/MENTION],

Could you help to add Redmi Note 4/4X fingerprint in the next release?

Here's the fingerprint:

xiaomi/mido/mido:7.0/NRD90M/V9.2.1.0.NCFMIEK:user/release-keys

Thanks...
[Magisk] Shriac:
I want to edit my build. Prop for ro.config.tima=0 to get Shealth working. how do I get it done.
[Magisk] Didgeridoohan:
I actually have a new feature for that in the next version of this module. You can add whatever props you like... I'm waiting for some time to test one last thing and should hopefully (time permitting) have a new release ready later today (think: sometime in the next 10-12 hours).

If you can't wait, put this in a file and place it in /sbin/.core/img/.core/service.d (or if that doesn't work, place it in /sbin/.core/img/.core/post-fs-data.d instead):

resetprop ro.config.tima 0

Lastly, give the file permission 755.
[Magisk] Shriac:
Well that did the trick. Thanks. Waiting for the new features. Is it possible to also edit csc files systemlessly?
[Magisk] Didgeridoohan:
CSC files are a Samsung thing, right? I wouldn't know, I have a slight enmity towards Samsung devices... :laugh: If they're located in /system or /vendor, then yes, it's possible with a Magisk module. That's outside the scope of this module though...
[Magisk] Shriac:
Yes I have samsung galaxy note 5. The csc is located in system folder.
[Magisk] Didgeridoohan:
Cool. But like I said, that's outside the scope of this module (read: off-topic :p), so if you want to accomplish that your best bet would be taking a look at the link I posted and make a Magisk moduler yourself. Or, ask for advice in a Samsung specific forum, or the Magisk general support thread.
[Magisk] Didgeridoohan:
Update

Ok. Finally had some time to properly sit down and test a couple of new features.

The big ones in this release are the ability to set custom props and a function to apply settings with a configuration file. The second one could have an impact if you want to use Magisk to make a custom ROM pass Play Store certification out of the box.

The fingerprints list has also grown quite a lot. Currently there are 37 certified fingerprints on there, and they've all been tested to work on at least one device. Therefore I've also changed the fingerprints list so that they're all grouped by manufacturer for easier access.

Make sure to read through the documentation if you have any questions.

Changelog

v2.0.0

Added a function for setting your own custom prop values.

Added a function for setting values by configuration file. Useful if you want to make a ROM pass the ctsProfile check out of the box.

Added a function for resetting the module by placing a specific file in /cache. Useful if a custom prop is causing issues.

Added a function to set options for the props script. See the documentation for details.

Added command option to not check online for new fingerprints list at start. Run `props` with the -h option for details.

Restructured the fingerprints list menu. Sorted by manufacturer for easier access.

New and updated fingerprints (lots), list v6. Thank you [MENTION=5007648]uodii[/MENTION], [MENTION=6421927]jackebuehner[/MENTION], [MENTION=1861039]lvbaal[/MENTION], [MENTION=8237713]thorin0815[/MENTION], [MENTION=2585605]shaDNfro[/MENTION], [MENTION=5237901]Wolfcity[/MENTION], [MENTION=6247359]atarek[/MENTION], [MENTION=9085111]musiXelect[/MENTION], [MENTION=5021307]Zincoshine[/MENTION], [MENTION=7166349]turbolukex5[/MENTION], [MENTION=322811]orjanraberg[/MENTION], [MENTION=6254472]NIKKISLAYER7[/MENTION], [MENTION=9054448]rufk[/MENTION], [MENTION=9068776]nalajcie[/MENTION], [MENTION=7180732]spoof123[/MENTION], [MENTION=8754178]MeNoNoob[/MENTION], [MENTION=8452055]Felix Siahaan[/MENTION], [MENTION=4660349]jhobc[/MENTION]

Minor fixes and improvements.
[Magisk] orjanraberg:
Good work! Will try it out soon.

I still haven't been able to find a working fingerprint for Xperia Z5 but I have managed to find one for Xperia Z5 Compact now:

Sony/E5823/E5823:7.1.1/32.4.A.1.54/3761073091:user/release-keys

---------- Post added at 03:09 PM ---------- Previous post was at 02:45 PM ----------

Now I actually got someone to check the fingerprint for me on Sony Xperia Z5.

Sony Xperia Z5:

Sony/E6633/E6633:7.1.1/32.4.A.1.54/3761073091:user/release-keys

No "dev-keys" on this phone.

Update: E6633 is the model number for Sony Xperia Z5 Dual but the key would probably be identical on the the non-dual version.

---------- Post added at 03:42 PM ---------- Previous post was at 03:09 PM ----------

I have tested the new version on my Xperia Z5 with the key I just posted and it now passes the CTS profile match test! :)

Thanks a lot Didgeridoohan!
[Magisk] Didgeridoohan:
Updated fingerprints list to v7.

Added Sony Xperia Z5, Sony Xperia Z5 Compact and Sony Xperia Z5 Dual.

Thank you [MENTION=322811]orjanraberg[/MENTION].

The list will update automatically when you run the props command, or you can do it manually in the Fingerprints menu if you've disabled automatic updates.
[Magisk] ashwa18:
Coolpad !!

:( can anyone give me a fingerprint for coolpad note 3

Iam not getting it from anywhere even my official forum has been closed
[Magisk] traketto:
While I am reading the new fingerprints list, I saw that the "Sony Xperia Z3 Tablet Compact" that I have posted here.

I have extracted the fingerprint from the original ROM downloaded fron Sony repository.

I have not tested the submitted fingerprint because now I have installed a custom AICP Oreo 8.1 rom, and this rom is not able, in any way, to pass the ctsProfile with any of your fingerprints.

Do you have tested the fingerpint with a bad result or you just missed it?

Thank you.

PS: This is the fingerprint (successfully tested by me) of my glorious Samsung Galaxy S4 International Version (jfltexx)

Fingerprint: samsung/jfltexx/jflte:5.0.1/LRX22C/I9505XXUHPF4:user/release-keys
[Magisk] Didgeridoohan:
Thank you for pointing that out. I had indeed missed testing and adding the Z3 Tablet print to the list. And the S4 print works as well. I'll make sure to include them both in the next update.
[Magisk] iBART:
Hi!

I have los15.1+magisk. I have installed this module and changed the fingerprint (moto g 5 plus) but saftynet is still false. I skimmed documenation but I didn't get what I have to change. MagiskHide prop or Custom?

Thanks
[Magisk] Didgeridoohan:
Are you passing basic integrity? And please provide the logs as described under "Issues" in the OP?
[Magisk] Didgeridoohan:
This conversation is better suited here than the Magisk support thread.

Use the "Custom props" option and just follow the instructions.
[Magisk] Didgeridoohan:
Hello again.

This made me curious and the urge to problem solve is too big... :laugh:

Could you run this in a terminal emulator and then send me the resulting file?

su -c getprop > /sdcard/props.txt
[Magisk] traketto:
Ok thanks for your interest.

I have installed the 2018/02/05 build.

I have installed magisk 16 and Magisk Hide props config module.

In Magisk Hide I have selected the following apps:

- Google Play Store

- Google Service Frameworks

- SafetyNet Test

Using your fingerprints there is no way to pass ctsProfile check inside Magisk app or in SafetyNet Test.

If you need more info ask me.

Thank you.
[Magisk] UMU24013:
Thanks. It works perfectly for properties like ro.product.model and many others. But I was unable to get it to work with gsm.sim.operator.iso-country . What can I do to permanently override this property value?
[Magisk] Didgeridoohan:
Are you sure it's supposed to be "gsm.

sim

.operator.iso-country"? I believe the correct prop is "gsm.operator.iso-country", without "sim".

Edit: and when things aren't working as expected, please provide the logs mentioned under "Issues" in the OP.
[Magisk] orjanraberg:
That is very interesting since my Sony Xperia Z3 Tablet Compact with the same ROM passes all SafetyNet tests without having to change the fingerprint.
[Magisk] traketto:
I have made a full wipe and flashed the march build, magisk 16 and open gapps nano and now the device can pass all SafetyNet checks, included ctsProfile.

Maybe I have left some junk during a month of tests, a clean filesystem helped a lot.

I have also noticed that the device fingerprint now is the original one provided by Sony, surely the rom developer has fixed something.

Thank you very much for the help.
[Magisk] kullurumanoj:
[MENTION=4667597]Didgeridoohan[/MENTION]

Hey bro,

I was using Universal safety net fix previously and it's not working now.

So thought of using this now and it worked on my device Redmi Note-4X stock rom (Global) and recently I installed stock rom (China) but still CTS profile is not matching, I tried installing and uninstalling magisk tried different finger prints but still no luck, Can you please help me with this

Just a suggestion : I think it would be good if you can can create telegram group for discussions on this and you may even get help from others in doing so.

Thanks in advance.
[Magisk] kaiiori:
Sony Xperia X (8.0.0)=Sony/F5121/F5121:8.0.0/34.4.A.2.32/1455699507:user/release-keys
[Magisk] Didgeridoohan:
So it works on the Global ROM, but not the China one? Refresh my memory please, but isn't it the Xiaomi China ROM's that are supposed to be certified out of the box? Or I might be confusing it with something else...

Anyway...

Your logs look good (apart from the excessive amount of apps/services on your Hide list, there's no need to hide that much :eek:), so I can't say what it could be. Could you run this command (with the module fingerprint option disabled) and send me the resulting file:

su -c getprop > /sdcard/props.txt

About Telegram, I really don't feel I have any need (or desire) for that at the moment. Would just be one more thing to keep track of. Thanks for the suggestion though.
[Magisk] Didgeridoohan:
Maintenance update

Pushed a small update a few hours ago, with a couple of new fingerprints, bug fixes and new features.

Having issues updating the OP at the moment, so no changelog or zip file available there. Best to download from the Magisk Manager anyway. OP will be updated when the technical issues have been solved.

Changelog:

v2.1.0

"Improved hiding" will now also mask the device fingerprint in build.prop. Please reapply the option to set.

Fixed colour code issues if running the script with ADB Shell. Huge shout-out to [MENTION=7296895]veez21[/MENTION].

Fixed typo in A/B device detection. Thank you to [MENTION=8570610]JayminSuthar[/MENTION].

New fingerprints (Samsung Galaxy S4 and Sony Xperia Z3 Tablet Compact), list v8. Thank you [MENTION=5169008]traketto[/MENTION].

Minor fixes and improvements.
[Magisk] kullurumanoj:
But my version is not stable china rom..mine is beta..so maybe I'm facing this issue..even the global one which passes CTS is beta..so I thought of posting here.. I have attached the latest log and screenshot along with the file you asked for.
[Magisk] 0ther:
device:

Xiaomi Mi 5 / Mi 5 Pro

rom:

MIUI Global Stable V9.5.2.0.NAAMIFA

fingerprint:

ro.build.fingerprint=Xiaomi/gemini/gemini:7.0/NRD90M/V9.5.2.0.NAAMIFA:user/release-keys
[Magisk] Didgeridoohan:
Fingerprints list updated to v9

Added and updated a whole bunch of the latest Google fingerprints, together with the Sony Xperia X (thank you [MENTION=5205014]kaiiori[/MENTION]).

The list will update automatically when you run the props command, or you can do it manually in the Fingerprints menu if you've disabled automatic updates.
[Magisk] Didgeridoohan:
Quick bug fix

Dammit... There's always that little thing you forget.

v2.1.1

Fixed transferring custom props between module updates.
[Magisk] Yeshu_bablu:
[MENTION=4667597]Didgeridoohan[/MENTION] I reflashed my ROM and Magisk 16.3. I flashed your Magisk module and it seems, its not working even though there are no Magisk modules installed. So please help me in creating a custom fingerprint. Noob here. The process you gave is too complex for a beginner like me.
[Magisk] Didgeridoohan:
Do you mean that you want to use the configuration file to set a certified fingerprint out of the box on a fresh install?

Download and place this file in /cache, find a suitable fingerprint here and paste that into the CONFFINGERPRINT variable of the configuration file. And of course, reboot.

Example if I wanted to use the Google Nexus 6P fingerprint:

CONFFINGERPRINT="google/angler/angler:8.1.0/OPM5.171019.019/4619337:user/release-keys"

Is that what you're looking for? If not, please specify a bit clearer...
[Magisk] papuruth:
Yureka Black 5040

Can anybody provide Yu-5040 black fingerprint.
[Magisk] JohnFawkes:
[MENTION=4667597]Didgeridoohan[/MENTION] not sure if its been mentioned here yet but seems your module is blocking apps from showing in app drawer. like i have zackptg5 viper and the Greenify4Magisk module and after installing magiskhide props viper and Greenify disappear. it's not limited to those apps either. seems to be any module which puts apks into app or priv-app are affected by this bug
[Magisk] Didgeridoohan:
Had not heard that reported before, and have not experienced it myself. That's usually caused by an issue with a module post-fs-data.sh script interfering with Magisk.

Hm... Could you post a magisk_debug.log and the module logs (check the OP)?
[Magisk] JohnFawkes:
here you go

forgot im on magisk 16 because i thought this might if been an issue with magisk before i figured out its this module by process of uninstalling modules one by one until apps came back. give me a few and ill install 16.3 to get more logging
[Magisk] Didgeridoohan:
The post-fs-data.sh script runs just fine, and I don't see anything obvious in the Magisk log. Would it be possible for you to grab a Magisk log (but preferably the debug log) when only MagiskHide Props Config is active and no other modules?

The resetprop log isn't mine... That looks like something from your ROM.
[Magisk] JohnFawkes:
heres debug log
[Magisk] JohnFawkes:
yea ill disable everything but viper and magiskhide props
[Magisk] JohnFawkes:
only viper, fbind (so i dont lose my files that are being symlinked to sdcard), init.d Injector (bootloop if disabled and not installed), and magiskhide props config
[Magisk] Didgeridoohan:
Thank you. I'll take a good look at those a little later.

But I've been planning to move things away from post-fs-data as much as possible anyway, so this is might be a good excuse to get off my butt... :laugh:

I'll get back to you shortly.
[Magisk] skullkid383:
Moto e4 perry stock fingerprint

motorola/sperry_sprint/sperry:7.1.1/NCQ26.69-64/68:user/release-keys
[Magisk] x11term:
Xiaomi Redmi 2 TD Pro

latest MIUI 9 Stable V9.2.3.0.LHJCNEK

Xiaomi/wt86047/wt86047:5.1.1/LMY47V/V9.2.3.0.LHJCNEK:user/release-keys
[Magisk] Didgeridoohan:
Just wanted to let you know I haven't forgotten about you. :)

I've done some optimisation (need to check for regressions before releasing), but the post-fs-data.sh file still has to run some code to gather the necessary data. And, I still don't know why it causes issues for you in the first place..

If possible, could you test the module again, but comment out line 66 in post-fs-data.sh:

# Get the default prop values
#curr_values

If that does nothing, could you just delete the post-fs-data.sh script and see if that works. Just to confirm it is the script causing it...
[Magisk] nijihana:
Is there a way you could make this work with xposed framework installed?
[Magisk] Didgeridoohan:
Read the OP.
[Magisk] giociampa:
Google thinks I have a Pixel 2 (instead of a Moto G5+)

I assume that it's due to this:

shell@android:/ $ getprop | grep finger
[ro.bootimage.build.fingerprint]: [motorola/potter_n/potter_n:7.0/NPNS25.137-33-11/11:user/release-keys]
[ro.build.fingerprint]: [motorola/potter_n/potter_n:7.0/NPNS25.137-33-11/11:user/release-keys]
[ro.vendor.build.fingerprint]: [google/walleye/walleye:8.1.0/OPM1.171019.011/4448085:user/release-keys]

The first two were set using props to override the (USNF-generated) Xiaomi fingerprint - but the third seems to be the one Google uses for the "Device activity & security events" page.

I'll look at creating a script to (hopefully) correct this - but was wondering whether props would be updated to check for (and amend) this value also...?

Thanks in advance,

[Additional]

I tried using the custom edit ... but got an error at the last stage:

This will set ro.vendor.build.fingerprint to:
motorola/potter_n/potter_n:7.0/NPNS25.137-33-11/11:user/release-keys

Do you want to continue?

Enter y(es), n(o) or e(xit): y
sed: bad option in substitution expression
[Magisk] Didgeridoohan:
Thanks for reporting. I'll add the vendor prop to the next update, and the error you're experiencing is a bug I have already fixed for the next release. Should be up shortly...
[Magisk] giociampa:
No problem - and thanks again!
[Magisk] JohnFawkes:
no worries man. anyway commenting out line 66 and rebooting didn't work but deleting post-fs-data script and rebooting did work. made apps reappear in app drawer
[Magisk] terrorgen:
Hello, I am running CypherOS Oreo on my LG G4 H811 with Magisk. I found out that whenever I installed MagiskHide from the Magisk app and restart immediately, I get into a boot loop. I cannot get out of the boot loop by disabling MagiskHide or uninstalling Magisk.

Attached is my log.
[Magisk] Didgeridoohan:
Strange... Are you saying that even if you disable the module or uninstall Magisk your device won't boot? Could you install the Magisk v16.3 beta and see if there's a magisk_debug.log available in /data/adb after getting stuck on boot? If so, post that log please.
[Magisk] terrorgen:
I 'touched' .disable_magisk, it doesn't let me out of the bootloop, next I just pushed the uninstall Magisk zip to TWRP and flashed it. Although the flash looks successful, bootloop didn't stop.

Bootloop meaning it tried to load system for a while then gave up and reboot into recovery. For lack of a good terminology I called it bootloop.

How do I get 16.3? The official thread still has 16.0 up although there is a mention of 16.3.
[Magisk] Didgeridoohan:
If the flashing of the Magisk uninstall zip was successful, the bootloop should stop. Unless you're now experiencing another issue that some users have reported that they can't boot after flashing the uninstall zip... :laugh: Try installing Magisk again. If you want to use the v16.3 beta, you'll find that zip in the beta thread.

Try following the advice from here if you get into further issues with the module: https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
[Magisk] madbat99:
You get 16.3 by changing update channel from stable, to beta in magisk manager settings.
[Magisk] Didgeridoohan:
Update

New version available in the Magisk repo. As usual the current zip is also attached to the OP. Here's what's new:

v2.1.2

Detects and edits only existing device fingerprint props.

Slightly optimised the boot scripts.

New fingerprint (Motorola Moto E4), list v10. Thank you [MENTION=8931427]skullkid383[/MENTION].

Minor updates and improvements.

[MENTION=6815443]JohnFawkes[/MENTION] and [MENTION=5363065]terrorgen[/MENTION]. Please feel free to test this new version against your issues. I doubt it'll be fixed, since I have no idea what's actually causing it in the first place, but it'd be nice to have confirmation.
[Magisk] JohnFawkes:
unfortunately updating did not fix the apps disappearing issue. once I get off work ill look at the post-fs-data and the service script and comment stuff out and reboot until apps come back so i can figure out whats causing it. btw this is happening by just installing it. default settings. i havent even ran props in terminal.
[Magisk] Zep0th:
Update via Magisk v2.1.2-v10

This update made it stop working, it was working fine on v2.1.1-v9,

After changing fingerprint, it says it has changed but after rebooting it stays the same.

Screenshot of both version's.
[Magisk] kaiiori:
Xperia X Oreo confirm
[Magisk] Didgeridoohan:
Please provide the logs as described in the OP.
[Magisk] Zep0th:
I have no PC to provide logs unless there's a way to do so without PC.
[Magisk] Didgeridoohan:
If you read the OP (Original Post), under "Issues", you'll see that the logs I asked for are already on your device.
[Magisk] Zep0th:
Ahh my bad, I didn't actually read all of it, my fault.

here ya go.
[Magisk] Didgeridoohan:
No worries.

I think I see what's happening and if so it's a purely cosmetical bug. Just to make sure though, could you run this command in terminal and get back with the output:

getprop | grep fingerprint

Edit: Nevermind... I've realised there are some issues with the new implementation and I'm reverting it somewhat. Expect another update shortly. :good:
[Magisk] Didgeridoohan:
Bux fix and optimisations

Small bugfix reverting a "good" idea I had yesterday. :p I also took the opportunity to streamline another couple of functions as well.

v2.1.3

Reverted the function to only editing existing fingerprint props.

Optimised setting the different props.

Minor updates and improvements.

Install from the Magisk Manager Downloads or get the zip from the OP.