yashsingh1/xdaforums huggingface dataset:
[Magisk] VVAREZ:
Yes my bad, the core only mode was active. Now I have a list to select but which one do I select to fix the "ctsProfile reporting false" ?
[Magisk] Didgeridoohan:
Whichever fingerprint you want. They're all certified and tested.

There's a lot of info in the documentation as well:

https://github.com/Magisk-Modules-R...ices-fingerprint-to-pass-the-ctsprofile-check
[Magisk] VVAREZ:
Every thing is green now! thanks!!!
[Magisk] whenitapproaches1:
Hi, I've got "The original props values are not loaded... " error asking me to reboot when attempting to run "props" command.

I did reboot many times but can't figure out.

Logs file: drive.google(.)com/file/d/1C1e2v7YXkow81tWsN4R0L8WkCCUceHd2/view?usp=sharing

I am unable to post link yet, you may remove parentheses from the link

Btw, I'm on custom ROM (Lineage 8.1) J7 Prime and custom kernel Oxygen with Lucky Patcher.

I did uninstall Xposed Framework both from Magisk and also in TWRP Recovery.
[Magisk] martyfender:
I've seen that error on my devices before when the module was not properly installed. I can't remember, but, I may have used the direct download install and had to try the download and install through TWRP to get it to work, on occasion. That was, of, course with older versions. Recent versions have worked flawlessly with the direct download and install method in Magisk Manager.

An uninstall and reinstall of the module may also fix it.

Mention of Lucky Patcher is ban on xda, as it is considered warez and the moderators often delete the post. It can make you system also unstable.

I am unsure, but I believe it is similar to xposed, in that a device with it will not pass SafetyNet, as it modifies the system, even with this module.

I'm sure, [MENTION=4667597]Didgeridoohan[/MENTION] will know, for sure.
[Magisk] Didgeridoohan:
[MENTION=9635323]whenitapproaches1[/MENTION] Looks like the Magisk image doesn't seem to have had time to properly mount before the boot script runs, resulting in the script not doing it's thing since it seems like the module isn't actually installed. Hm... I'll think about that one.

And as [MENTION=8126387]martyfender[/MENTION] says, please don't use Lucky Patcher... It is not welcome on XDA.
[Magisk] whenitapproaches1:
Thanks for your reply, I tried installing another version of the module. Now the props command seems working but safetynet still not getting bypassed.
[Magisk] Didgeridoohan:
If you need further help, you're going to have to give more info than just "it's not working"...

But, start by reading the docs, since most questions are answered there.
[Magisk] Didgeridoohan:
Update to v2.7.2-v40

Was going to just do a quick fingerprints list update with some of the prints all you guys have been posting lately. Thank you very much! But, I also found a couple of possible improvements so a proper update was in order.

Thank you to [MENTION=6948826]Nebrassy[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=7528084]compgamer89[/MENTION] and [MENTION=5685876]pekkle_hksar[/MENTION] for your contributions to the fingerprints list. There where a couple of other prints posted since the last update, but unfortunately I could not get those to pass the CTS profile check. [MENTION=8122617]PHiDi[/MENTION], I had not seen your amendment to your post, with the added date, until just now. I did test the print though and it passes so I'll add it in the next update, now I'm off on a winter vacation.

If you have any kind of holiday coming up, may it be a happy one!

Changelog

v2.7.2

Re-run the post-fs-data script if the Magisk image wasn't mounted yet or if the script has been reset.

Added fingeprints for Razer Phone 1 & 2 and Xiaomi Mi Pad 4, and updated fingerprints for Xiaomi Mi 8, Mi A2 & Pocophone F1. List v40.

Mostly harmless.

Small fixes, as usual.
[Magisk] SnowFuhrer:
If anyone here has an Galaxy A5 2017 running 8.0, could you upload the fingerprint? TY
[Magisk] michaelmaverick:
I got the newest fingerprint for Mi Mix 2S, it is Xiaomi/polaris/polaris:9/PKQ1.180729.001/V10.0.9.0.PDGMIFH:user/release-keys__2018-11-01
[Magisk] ipdev:
This was a little more difficult than it should have been. ;)

Samsung A5 (SMA520F)=samsung/a5y17ltexx/a5y17lte:8.0.0/R16NW/A520FXXU4CRE8:user/release-keys__2018-05-01

I hope this is the one you were looking for. If not, I can try again when I have some more time but, I would need a specific Samsung firmware file name or preferably a fast download link to the stock firmware or at least the fota.zip from it.

Cheers. :)

Edit:

Sorry, forgot to add a Thank you to [MENTION=1642356]Rick#2[/MENTION] your post Here helped me and saved me some time. :good: :D
[Magisk] Exodusnick:
Go to data/data/com.android.vending/shared_prefs/finsky.xml

Open with code editor

Search for:

<boolean name="device-google-certified"value="false"/>

false to true and Save and reboot The device

And then look in play store settings

Device is certified ;)
[Magisk] Nebrassy:
Have you considered changing some of the other props such as ro.product.device so you could access apps/games that have a whitelist of supported devices?
[Magisk] Exodusnick:
No, have no problems with applications and games
[Magisk] Nebrassy:
Was asking the OP
[Magisk] SnowFuhrer:
Could anyone tell me how to use replace the fingerprint in my phone with the custom one? I know the op said how to do it, but I keep getting the original fingerprint when I pull it with the getprop command. (Probably doing something wrong) :D
[Magisk] Didgeridoohan:
That's exactly what the Custom Props function of the module is for.

I have had plans for using the fingerprint to set a whole host of other props (for proper device emulation), but since you can set whatever custom props you want with the module already it's not a priority.

You'd need to provide all the logs for me to know for sure what's going on.
[Magisk] jenslody:
Do you reboot after setting it ?
[Magisk] SnowFuhrer:
I will try tomorrow and take logs.

Yes. :)
[Magisk] Nebrassy:
Yeah, of course it can be done with custom props, but the idea of having all proper props in the list is pretty appealing
[Magisk] Didgeridoohan:
I've actually had that kind of feature on my mind for quite some time... It's actually relatively trivial. Just need to split up the used fingerprint in its parts and apply to the relevant props. I'll take a look at adding an option for that after the holidays.
[Magisk] SnowFuhrer:
[MENTION=4667597]Didgeridoohan[/MENTION] here are the logs.
[Magisk] Didgeridoohan:
From your logs it looks like you haven't applied any fingerprint at all... I'm assuming you wanted to use the one [MENTION=7280276]ipdev[/MENTION] supplied, so since that one isn't included in the module you have two options. Either pick option 1 from the main menu of the props script (Edit device fingerprint) and then just manually enter the fingerprint and follow the instructions. Or use a module Configuration file to set the print. You can use this file, just place it in /cache and reboot.
[Magisk] SnowFuhrer:
Thanks, that did the trick!
[Magisk] z0mBy:
Hey here's the Fingerprint for the Xiaomi Redmi Note 6 Pro (8.1.0)

xiaomi/tulip/tulip:8.1.0/OPM1.171019.011/V10.0.5.0.OEKMIFH:user/release-keys

Thanks for adding :)
[Magisk] Didgeridoohan:
Thank you, no worries. But, I'll also need the security patch date that corresponds to that fingerprint.
[Magisk] droncheg:
Hi. I'm on Xperia X Compact (kugo,F5321) with this rom.

MagiskHide Props Config v2.7.2

Magisk v18.0

Command 'props' in rootshell fails with 'The original prop values are not loaded...'

Here's a propslogs.tar.gz if it helps to fix this issue =)
[Magisk] Didgeridoohan:
I have absolutely no idea why, but the late_start service settings script (the heart of the module) is completely empty on your device (note to self: add a check for that). That's why things aren't working...

If you uninstall and install the module again you should be fine.
[Magisk] droncheg:
Thank you, module reinstall solve problem.
[Magisk] sikiro:
can i request the addition of the xiaomi mi mix 3?
[Magisk] Didgeridoohan:
You can, but:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] Gemini-Zepeto:
I'm using Mi 5 with stock ROM and Floppy Kernel, after upgrading Magisk to v18 (or changing the kernel, I don't know the culprit) I lose both SafetyNet check. This module solves both and my banking app is up and running.

If anyone got problem with SN check, just try to flash this godsend module.
[Magisk] sikiro:
here is what i gathered sir.

Xiaomi/perseus/perseus:9/PKQ1.180729.001/8.12.7:user/release-keys

ro.build.version.security_patch=2018-11-01
[Magisk] Soumy1234:
I installed this module after flashing a custom room, but after setting the fingerprint and rebooting it says the "late start service boot script does not appear to have run during boot". Here is the log
[Magisk] Didgeridoohan:
Thank you very much. That looks good and I'll make sure to test it out and add it to the module fingerprint list as soon as I'm back from my winter holidays (it'll be a couple of weeks).

Meanwhile you can test out the print yourself by entering it manually (don't forget to also set the custom prop for the patch date), or you can make a custom fingerprints list, or you can use a configuration file to set both the print and the patch date.

Looking at your log I can see that there are things that aren't right with your Magisk installation.

For some reason the late_start service boot mode is happening before the post-fs-data boot mode (it's supposed to be the other way around) and even before the Magisk image is mounted, causing the late_start service settings script to percieve that the module isn't installed triggering a cleanup of the scripts. At a later stage things start kicking in as they should and the scripts are restored, but since it happens so late and that the boot modes are messed up, the script doesn't run as it should.

Solution: re-install Magisk and hope it works this time...
[Magisk] sikiro:
this print is from a china-dev rom for this device although both print and date match when i added it manually it still failed cs check. unfortinately. i will wait for your return and see if we can figure something else out. thank you so much for the response.
[Magisk] Didgeridoohan:
Being a dev ROM likely means that it won't be certified. The best bet for a certified fingerprint is from a stable release.
[Magisk] Soumy1234:
Alright, I'll try it out
[Magisk] z0mBy:
Whhops, sorry.... the corresponding security patch date is 1st of October 2018 :)
[Magisk] Soumy1234:
It worked, thank you so much!
[Magisk] martyfender:
I have seen so many post on the Magisk General forum where I have wondered if just installing Magisk 18 again, would solve the problem?

It is strange that a second install would fix this? What could be going on here?

On my 5 devices, recent Magisk Canary and unofficial builds have had very few problems, but I see so many users having problems with 18, that they never had before.

For me, on my 5, Nextbook Ares 8 devices, I have had no problems with your recent updates.
[Magisk] sikiro:
alright I tested a couple diferent combinations using some stock roms and here is the one that worked for perseus from the global rom. this makes google pay work and for some reason it also has better magisk hide compatability !

ro.build.fingerprint=Xiaomi/perseus/perseus:9/PKQ1.180729.001/V10.0.11.0.PEEMIFH:user/release-keys
ro.build.version.security_patch=2018-11-01

Thank you for this.
[Magisk] Soumy1234:
I got the same error again about late start service script not running during boot. I forgot to mention that just like last time, my phone shows a "glitchy screen" on boot and some of my other modules like iOS emojis and Dolby digital plus don't work.
[Magisk] Didgeridoohan:
And just like last time it's caused by the late_start service boot mode running way, way too early.

There's a common denominator between your two cases though. It looks like you've systemised some apps with App Systemizer right when the issue manifests. There could be some issue with systemising large apps (the merge image was 640 mb). Does the issue persist after another reboot?

If there is some kind of issue with the image merging, there likely won't be anything done about it at the moment. I happen to know that there are plans to change how that works in the near future....

If you're trying to systemise several apps, try doing one at a time and see if that makes a difference.

In conclusion, it's not an issue with this module. The issue could be with App Systemize, with Magisk or maybe both, I don't know which. It'd take some more testing to determine what, but as hinted above it might not be worth the effort.
[Magisk] Soumy1234:
I think you're right about the app systemizer. I did systemize a bunch of apps together

Now everything is ok. Thank you for your time.
[Magisk] littlepandemonium:
Any way of using this module without Magisk? Been trying to manually change build.prop values with no success.
[Magisk] jenslody:
Nope.
[Magisk] jcmm11:
What device and how have you been trying to change it?
[Magisk] littlepandemonium:
LeEco Le 2.

I tried to edit the two build.props in /system/ and I

changed the ro.device.fingerprint line to the preset LeEco fingerprint in the module. The device isn't the exact same but it works...
[Magisk] Didgeridoohan:
Well, if you're not using Magisk you'll have other issues passing SafetyNet that cannot be fixed by changing the device fingerprint. Whatever root solution you're using, an unlocked bootloader, etc, will all trigger SafetyNet, things that MagiskHide normally takes care of so that this module can do it's thing.
[Magisk] velfere:
Sakura

Hi this is Fingerprint for Xiaomi Redmi 6 Pro (Sakura) on miui chinese version

sakura:/ # getprop ro.build.fingerprint xiaomi/sakura/sakura:8.1.0/OPM1.171019.019/8.12.6:user/release-keys

sakura:/ # getprop ro.build.version.security_patch 2018-12-01
[Magisk] Dexer125:
Hello, could someone share fingerprint description for this fingerprint? We need it for custom ROM.

Xiaomi/dipper/dipper:9/PKQ1.180729.001/V10.1.1.0.PEAMIFI:user/release-keys

Thanks
[Magisk] Didgeridoohan:
You mean ro.build.description?

You can usually construct the description prop from the info in the device fingerprint. For that particular print it should be:

dipper-user 9 PKQ1.180729.001 V10.1.1.0.PEAMIFI release-keys

After I'm back home after the holidays, the next release of the module will actually do this for you (together with another few props).
[Magisk] makination:
Fingerprint for Galaxy J7 2017 8.1.0 needed (SM-J730F), I don't know if J7 2017 Prime 6.0.1 from the list will work.

If somebody knows I'll be much appreciated.

Enviado desde mi SM-J730F mediante Tapatalk
[Magisk] martyfender:
I would suggest trying the fingerprint from the J7 2017 Prime 6.0.1.

It is easy to revert if it does not work for you.
[Magisk] Didgeridoohan:
Apart from the above:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] makination:
It worked! Thanks a lot [emoji3526]

Enviado desde mi SM-J730F mediante Tapatalk
[Magisk] Snake186:
hi, my safety net check is ok, after the magisk flash has disabled me fingerprints as the original settings of the system, and in the settings of magisk does not let me enable anything. I have a Huawei nova CAN-L01, I can not install magisk modules, error "merge.img failed", the unofficial twrp does not flash zip file. how can I do?
[Magisk] Didgeridoohan:
Seems like you're experiencing some issues...

Instead of trying to figure everything out, I'm simply going to link you to my troubleshooting guide for everything Magisk and MagiskHide:

https://www.didgeridoohan.com/magisk

In there you'll find a lot of information on what you can do to fix some of the most common issues.

If you can't figure things out after that, pay close attention to the part about reporting bugs and issues:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] martyfender:
I was testing if changing the build fingerprint will pass safetynet. I tried different ones and they do not pass.

With magisk hide and my default nextbook fingerprint, I do not need to do this to pass, but I like to test with new versions of your module and new unofficial builds.

Some time back, with an older version of this module, with a different fingerprint, was passing on my device, with an older, unofficial version of magisk. I don't remember in which versions it was passing. Is it because the device is x86?

I wish I had noted the previous build that worked.

Could you please diagnose?

Thanks

Attached is the log.

Thanks
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] I'll test it out when I get an opportunity.
[Magisk] martyfender:
UPDATE:

I chose the Asus Zenpad S 8 fingerprint and my device is passing both basic and cts profiles, now.

Others I remember trying that failed were the Asus Zenphone 2, Google Pixel XL and Nvidia Shield, Samsung Note 4, Samsung Galaxy Prime, LG G4, Essential PH-1 and Oneplus 2.

Maybe because the Asus Zenpad S 8 may be the only x86 device on your fingerprint list?
[Magisk] kryshnakishore:
Intially safety net passed, after 3hrs Safety net failed & I toggled magisk hide & safety net passed. Here's the complete log pls do check anyone. I tired all workarounds but same issue
[Magisk] martyfender:
I don't believe I even see Magisk Hide Props Config Module installed in your log?
[Magisk] pekkle_hksar:
New fingerprint for mi8 global 10.1.2.0

ro.build.version.security_patch=2018-11-01

ro.build.description=dipper-user 9 PKQ1.180729.001 V10.1.2.0.PEAMIFI release-keys

ro.build.fingerprint=Xiaomi/dipper/dipper:9/PKQ1.180729.001/V10.1.2.0.PEAMIFI:user/release-keys
[Magisk] kryshnakishore:
Intially I flashed it but the same issue is happening so I removed it.. With/without mogisk hide the issue is same

I fact I did not understand what to do after flashing mogisk hide zip.. For op6 stable 9.0.3 ,what are steps needs to do after flashing magisk hide zip

Pls help me out on this
[Magisk] Didgeridoohan:
[MENTION=6892058]kryshnakishore[/MENTION] This module has no bearing on your issue, so please keep the discussion in the general support thread. Also, your issue is a known bug with Magisk v18 (but without a current solution), so unless you have detailed knowledge on why it happens there's nothing to discuss really...
[Magisk] Didgeridoohan:
Funny... That's practically identical to the one I already have in the module. Only difference is 10.1.10 -> 10.1.2.0.
[Magisk] skullkid383:
Hey so even tho I passed safety net can't find Netflix on play store any solution

---------- Post added at 01:59 AM ---------- Previous post was at 01:53 AM ----------

Nvm showed up after a cple reboots
[Magisk] BruceElliott:
Ok, thanks. Not sure that I saw the message as I was fumbling with understanding the entire interface after installing. That said, it appears that the "tap to start safetynet check" function fails with my installation. (See screenshots below.) Maybe because I installed v16.4? I did that because of developer comments to the effect that one of the versions post-16.0 fixed compatibility with some Samsung phones. From extensive forum reading, apparently earlier versions had compatibility problems with some Samsung models, at least with Galaxy S5. (Mine is SM-G900T on Android 6.0.1) I was able to confirm SafetyNet with "SafetyNet Test" app, however. And indeed the Play Store changed my device status to "Certified." So it appears that all is well for the moment at least.

As to the operation of the MagiskHide Props Config module, could you please take a look at the last three screen shots below? I found my device fingerprint and stored it in the printslist text file on root of internal SDCard and entered module terminal command as instructed:

Samsung Galaxy S5=samsung/kltetmo/kltetmo:6.0.1/MMB29M/G900TUVU1GQC2:user/release-keys

The module provides little feedback, so difficult to say if its working or whether Play Store recognizes device's fingerprint natively. Curiously, though, Magisk settings indicate "no fingerprints were set or no device support." In light of SafetyNet Test app's indication of "CTS profile match: success," is the take-away that Play Store is recognizing device fingerprint without the aid of the plug-in module?

Thank you for your work!
[Magisk] abacate123:
I'm using the same magisk version and it's fine. Did you use the "Hide Magisk Manager" option in settings? It's below the "Clear repo cache". As the second screenshot says. That option will repack your manager apk with another package name (to avoid other apps detecting the manager). If yes, that should be the reason. If not, then I don't know, but does that really matter? I mean, you're already passing it and if you see Netflix, Pokemon Go and so in the play store and it's certified within PS settings, then you're good to go. Nothing to worry.
[Magisk] Didgeridoohan:
[MENTION=2903832]BruceElliott[/MENTION] The massage you get when trying to check SafetyNet from the Manager is caused by having the Manager hidden. It's not possible to check SafetyNet in that case. There's nothing wrong, just the way it is... You've already found another app to check.

The fingerprint option you're seeing in the Manager (screenshot 4) is your fingerprint, the one on your finger. It can be used to grant superuser access and has nothing to do with this module.

If you want to check your currently set device fingerprint you can run the prop script again and open the fingerprint menu. You'll see if your fingerprint has been set. Since your last screenshot is showing that you pass SafetyNet, I'm going to assume that everything is working as it should. If you want reassurance you can post the logs. You'll find them in /cache, and they all start with "propsconf".
[Magisk] BruceElliott:
Super; thank you sir!
[Magisk] Bharath Lr:
Device is not certified by google.. any way to fix this, i cannot check safetynet it says unknown issue with google play services
[Magisk] Didgeridoohan:
Issue 1:

https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up

Issue 2:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Cannot_check_SafetyNet
[Magisk] Didgeridoohan:
[MENTION=2903832]BruceElliott[/MENTION] I think you're over-complicating things...

If you want to mod your device and still keep using Google's services, you will put it in a state that will make it uncertified. With Google's new policy of blocking Gapps for these devices, you have two options.

Whitelist your device, as in the link you posted. Your device will still be uncertified though, and certain apps won't show up in the Play Store, or won't install.

Install Magisk and use MagiskHide to keep your device certified. If it ever reports as uncertified, you can simply clear data for the Play Store and you're good to go again (as long as you pass SafetyNet).

Doesn't have to be more complicated than that. Personally I prefer option two...
[Magisk] BruceElliott:
Yes, I agree completely. Option 2 is what I did (with your kind help and that of others on these threads). I was just trying to help the guy get back into the Play Store, based upon what appeared to be a similarity between what he experienced and what I've been through over the past few weeks. My problem (and apparently his) went beyond simply being uncertified. My phone was in a state of Play Services data being corrupted. When that happens Play Store does not even open.
[Magisk] Didgeridoohan:
That's interesting. I might play around a bit with that later.
[Magisk] MBechirM:
Can I edit custom props without using terminal ?

If yes, how ?

The reason is I want to change "ro.product.model" from J500F to Pixel 2 XL

But when I use the terminal the value changes to just "Pixel" and the "2" and the "XL" are created in separate lines as you can see in the screenshot
[Magisk] Didgeridoohan:
Oh... Buggrit. That's a bug. I'll fix... Not until tomorrow though. Thanks for reporting.
[Magisk] MBechirM:
Thank you :)
[Magisk] Didgeridoohan:
No worries. And when I've got it sorted you can actually use the configuration file to set whatever option you want, including the custom props.