yashsingh1/xdaforums huggingface dataset:
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 3a=google/sargo/sargo:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 3a XL=google/bonito/bonito:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 4=google/flame/flame:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 4 XL=google/coral/coral:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 4a=google/sunfish/sunfish:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05
Pixel 5=google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys__2021-08-05

Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.12.0.RFQMIXM:user/release-keys__2021-07-05

Xiaomi Mi A3 EU

Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.10.0.RFQEUXM:user/release-keys__2021-07-05

Xiaomi Mi A2

xiaomi/jasmine/jasmine_sprout:10/QKQ1.190910.002/V11.0.28.0.QDIMIXM:user/release-keys__2021-07-01

Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.21.0.QDLMIXM:user/release-keys__2021-07-01
[Magisk] akshay.ku:
Hey,

Thank you so much.

Yes it's July 1st security patch
[Magisk] Didgeridoohan:
Fingerprints list updated to v130

Massive prints list update! I haven't been able to do any testing of prints all summer, so the backlog got pretty big... Now they're all tested and all the prints that passed CTS (only 6 prints failed) have been added to the list.

Huge shout-out to all the wonderful (and patient) people who contributed. In no particular order:

@Some_Random_Username, @Dhaval Bhramkhatri, @Last_SiN, @Displax, @GtrCraft, @BlackSoulxxx, @rdis, @yazakachka, @tepsys, @DjLeleX, @ipdev, @xuxu1, @spacedingo (Github), @Howard20181 (Github), @SyberHexen, @CHT45, @akshay.ku

The prints list will update when you run the props command, or if you have disabled automatic updates by using the -f flag or from the "Edit device fingerprint" menu.

New

Asus Zenfone 8 Mini Europe & Global

Motorola Moto Edge

Motorola Moto G 5g

Motorola Moto G 5g Plus

Motorola Moto G Pro

Motorola Moto Razr 2020

OnePlus 7T T-Mobile

OnePlus 9 (All variants)

OnePlus 9 Pro (All variants)

OnePlus 9R

OnePlus Nord CE (All variants)

POCO M3 Pro 5G Indonesia

Realme XT RMX1921

Samsung Galaxy S10 Lite SM-G770F

Samsung Galaxy Tab S4 SM-T837A

Xiaomi Mi 8 Explorer

Updated

Google Pixel 3-5 (All variants)

Nvidia Shield TV 2015

Nvidia Shield TV 2015 Pro

Nvidia Shield TV 2017

Nvidia Shield TV 2019 Pro

OnePlus 6 (Several variants)

OnePlus 6T (Several variants)

OnePlus 7 (Several variants)

OnePlus 7 Pro (Several variants)

OnePlus 7T (Several variants)

OnePlus 7T Pro (Several variants)

OnePlus 8 (Several variants)

OnePlus 8 Pro (Several variants)

OnePlus 8T (Several variants)

OnePlus N10 (Several variants)

OnePlus N100 (Several variants)

OnePlus Nord (All variants)

POCO F2 Pro Global

POCO X3 NFC Global

Redmi Note 8 Pro Europe

Redmi Note 9S Global

Samsung Galaxy S10 (All variants)

Samsung Galaxy S10 Plus (Several variants)

Samsung Galaxy S10 5G (All variants)

Samsung Galaxy S10e (All variants)

Xiaomi Mi 9 China

Xiaomi Mi A2

Xiaomi Mi A2 Lite

Xiaomi Mi A3 Europe

Xiaomi Mi A3 Global
[Magisk] GtrCraft:
Thanks for the update, but I don't see the POCO F3 fingerprint? Was it not working?
[Magisk] Didgeridoohan:
That doesn't matter. If the module Busybox can't be downloaded, the module will look for [MENTION=4544860]osm0sis[/MENTION] Busybox, and if you don't have that installed it will fall back to using Magisk's internal Busybox as a last resort until the module Busybox can be installed.

If you need help with passing SafetyNet, start by taking a look at the issues and support part of the documentation. If you still can't get things working make sure to provide lots of details and logs.
[Magisk] osm0sis:
Well, I can't say for sure about FrankeNDK then, since us believing it worked was based on your testing, [MENTION=8126387]martyfender[/MENTION]... so if it doesn't work now then there must have been something flawed about your tests. :eek:

That said, I looked into it today and found that disabling the busybox feature CONFIG_ENABLE_MONOTONIC_SYSCALL should avoid the troublesome piece of code, and I just pushed an NDK busybox module update compiled with that and [MENTION=4470081]topjohnwu[/MENTION]'s Android Pie changes, so give that a spin. :good:
[Magisk] martyfender:
With the above, the latest module from the repository doesn't download the busybox and when typing props in the terminal it fails.

The test module he provided still works though and downloads the busybox for the module. What was stated earlier about falling back to your busybox module and as a last resort, the one in Magisk is not true in my case unless neither of them work when I type props in the terminal.

I have, of course went through at least 2 newer unofficial Magisk versions since I did the original tests.

How do you think the test were flawed? I followed the instructions exactly as far as I can tell. It appears to me that the frankenndk that was provided to you was some how changed once it was commited and built in the builds
[Magisk] osm0sis:
Flash my lastest Busybox module update, go to a command prompt and type `wget --help` to make sure you've got my 2018-08-13 build.

Once you've established that, try `wget -O /sdcard/hosts https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts`
[Magisk] martyfender:
I had thought I had updated and the module show as 1.29.2 aug 13, 2018 5:40:14 PM, but when I type wget --help it shows:

u0_a84@NX16A8116K:/ $ su

u0_a84@NX16A8116K:/ # wget --help

BusyBox v1.29.2-osm0sis (2018-08-02 17:32:12 ADT) multi-call binary.

Usage: wget [-c|--continue] [--spider] [-q|--quiet] [-O|--output-document FILE]

[--header 'header: value'] [-Y|--proxy on/off] [-P DIR]

[-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL...

Retrieve files via HTTP or FTP

--spider Only check URL existence: $? is 0 if exists

-c Continue retrieval of aborted transfer

-q Quiet

-P DIR Save to DIR (default .)

-S Show server response

-T SEC Network read timeout is SEC seconds

-O FILE Save to FILE ('-' for stdout)

-U STR Use STR for User-Agent header

-Y on/off Use proxy

u0_a84@NX16A8116K:/ #

I have had some issues with module installs, but in most cases I see errors in the install when it happens. Do you have any Ideas?

Thanks
[Magisk] osm0sis:
Alright, so update again with my module, and if you don't end up with 2018-08-13 then, like I said, there's definitely something fishy going on with your setup.. maybe a conflict with another module? The update worked fine on my Galaxy Nexus, OnePlus 5T and OnePlus 6. Try installing from recovery maybe, and/or uninstalling anything that might be conflicting.
[Magisk] martyfender:
I un-installed the module, rebooted, then rebooted to TWRP and installed it successfully. The command successfully downloaded the hosts file.

I have the following modules installed: your busybox, greenify4magisk, sysconfig patcher and magisk hide props config. test build provided in this post. I had to install the last one through add modules, because when trying it through TWRP, it failed with an error 1. With your updated module it was successful only when done in TWRP. Go figure?

I just tested the Magisk Hide Props Config test build: martyfender-test.zip through TWRP again to confirm it was error 1 failure.

After that I downloaded the Magisk Hide Props Config from the offical repository and successfully installed it with the add module function in MM. it show busybox being successfully downloaded, also, unlike the previous results with the official module. Therefore, thing are looking good with your new busybox.

Thank You for your patience with me in doing all of these tests.

I will try flashing your new module on a second or more tablet to confirm, then post the results.
[Magisk] osm0sis:
Not sure what to tell you about the rest of that, maybe something for [MENTION=4667597]Didgeridoohan[/MENTION] to look into.. can you verify your wget --help shows 2018-08-13 and try the wget command from my previous post?
[Magisk] martyfender:
I'm sorry if it wasn't clear in my post, I said that it shows 2018-08-13 and the wget command was successful.

On the second tablet that I had replaced your busybox with the frankendk version posted previously, it failed and still showed topjohnwu's version with the download install of your module, but succeeded once again with TWRP, this time without removal and a reboot, first. And by the way, I have always determined the version installed just by typing busybox which that has alway given me the version and that is much simpler.

The wget command also was a success on this second tablet. I think we have a winner!

Thanks for all of your great contributions!

If I discover any more issues, I will let you know.

---------- Post added at 12:56 AM ---------- Previous post was at 12:43 AM ----------

@Didgeridoohan with [MENTION=4544860]osm0sis[/MENTION] updated busybox on 2 tablets, so far I have flashed your latest module from the repository and in each case it successfully downloads busybox. On the second tablet, it did not, so I knew it was already there, so I deleted it and ran the module install again with the add module mode in MM and this time, as I thought, it downloaded the busybox.
[Magisk] Seagold:
Invalid response from... No error but yet to pass SafetyNet
[Magisk] Seagold:
This is my build.prop file.... Check.

https://drive.google.com/file/d/1BredksHcWuph9Z9-Ga5fDcbR1JLbH42m/view?usp=drivesdk
[Magisk] Didgeridoohan:
Neither of those screenshots have anything to do with the function of this module. Even if the Busybox you have on your device would have a broken wget, backup functions would take over and everything would work as it should. Otherwise you would get an error message when running the props script (with clear instructions on how to proceed with the logs provided).

And SafetyNet can no longer be checked through the Manager or even most other SafetyNet check apps. Google updated the SafetyNet API some time ago, but have now started enforcing it, so most apps that have been able to test SafetyNet are no longer working.
[Magisk] martyfender:
See my post here for an app that is working if you enroll in the beta:

https://xdaforums.com/showpost.php?p=77333365&postcount=2150
[Magisk] AndrewKvas:
Added fingerprint for Xiaomi Mi5S Plus (Mi5s plus miui 10 Android Xiaomi/natrium/natrium:7.0/NRD90M/8.7.26:user/release-keys https://xdaforums.com/showpost.php?p=77225933&postcount=434) is fingerprint of development version of MIUI.

Device can't pass SafetyNet.

Stable version of MIUI 10 for Mi5S Plus is unavailable.

Please replace on GitHub fingerprint for Mi5S Plus with stable MIUI 9 version: Xiaomi/natrium/natrium:7.0/NRD90M/V9.6.2.0.NBGMIFD:user/release-keys
[Magisk] Didgeridoohan:
Indeed, you are correct. The current fingerprint for the Mi 5S Plus does not pass. I must have messed up my testing of the print somehow... I'll replace it with the one you've supplied shortly. Thank you very much. :highfive:
[Magisk] Didgeridoohan:
Fingerprints list updated to v28

Updated Xiaomi Mi 5S Plus (thank you [MENTION=377855]AndrewKvas[/MENTION]) and also added a print for Motorola Moto Z2 Play (thank you [MENTION=4570328]TpmKranz[/MENTION]).

The list will update when you run the props script or with the -f option if automatic updates are disabled.
[Magisk] martyfender:
I updated today to your new build and had an md5 error on install when downloading busybox for the mod. I used the MM download install. When launched in the terminal it had a busybox error and it was downloaded, then all was good.

EDIT:Confirmed on 3 devices
[Magisk] DE SEXIEST:
Can I use this to edit build prop files?
[Magisk] Didgeridoohan:
You can use the custom prop function of this module to edit prop values systemlessly. You won't be editing the actual build.prop file, but you'll instead load your own custom values into the system.

Any prop you like, so it's quite powerful...

Edit: Either use the props command and enter your new props and values manually, or use the configuration file to set many props at once.
[Magisk] DE SEXIEST:
Thanks

Thanks man
[Magisk] Didgeridoohan:
That is correct. I tested several times and got attestation failed (both basic integrity and CTS failed). Didn't have time to dig deeper at the moment, but I have another couple of prints collected that did the same thing and will take a closer look at those when time permits.
[Magisk] GtrCraft:
Well it's probably because there was a new update since then, I will get the new fingerprint
[Magisk] akshay.ku:
Hey bro,

Thank you so much for updating the list.

for some strange reason, still not able to pass the CTS.

here is what i have tried.

Device: Samsung S10 lite G770F

Rom: Stock Rom

Android:11

Recovery:TWRP 3.5.0_10-2

Magiskk: installed version:23

Magisk modules:

MagiskHide Props Config : V5.4.0-V130

Universal safety fix V1.2.0 (Gives a boot loop), i had to disable the V1.2.0 and add the version 1.1.0

Energized protection, busy box, substratum

in the magisk hide props config its configured as

1. Reset all settings

2. added the fingerprint with the new one (updated one for G770F)

3. Turned on Device simulation all

I rebooted the device and checked CTS (eval Type Hardware) now it says BASIC and still not passing

Did i miss any step or made a wrong config? need a help

Regards,

Chandan
[Magisk] Didgeridoohan:
There are a couple it things you could try...

Try the v2 test version of USNF:

https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635

Try without any other modules then MHPC and USNF, to make sure it's not a module causing issues.

Edit: By the way, device simulation is not at all necessary to pass SafetyNet...
[Magisk] akshay.ku:
WOW!!

Thank you so much bro

All good now, the safetynet fix V2 works.

Now able to pass the CTS profile

Thank you bro!!!
[Magisk] sjgoel:
Hi, did you find any solution? I have same problem.
[Magisk] Didgeridoohan:
I'd be interested in hearing about that too...

I replied to them here, but never got an answer.
[Magisk] Last_SiN:
Mi8 Explorer Edition, updated fingerprint, manualy tested and working props.

Xiaomi Mi 8 Explorer (10):Xiaomi:Mi 8 Explorer=Xiaomi/ursa/ursa:10/QKQ1.190828.002/V12.5.1.0.QEHCNXM:user/release-keys__2021-06-07
[Magisk] hotelmariofan:
I was never able to find a workable solution unfortunately. I eventually just went back to the default phone app, receiving plenty more spam calls. I'll eventually just go for the Pixel 6 for that reason and others. Sorry I couldn't be of any help.
[Magisk] sjgoel:
Thanks, me same. Back to default app.
[Magisk] NOS_bzone:
I hope Poco F3 aka Alioth on the list soon 😁
[Magisk] TheKerevas:
Wooow, thx for updated F2 Pro 🥳
[Magisk] Didgeridoohan:
I can't get this to pass on my device. Are there any typos in there? I even tested different security patch dates (2021-06-01, 2021-06-05, 2021-07-01, 2021-07-05).
[Magisk] Last_SiN:
All the info is from here

Edit: Yup, looks like I've messed a bit.

2020.12.01 for a security patch.

View attachment 5384585
[Magisk] NOS_bzone:
Hi dev, please add Poco F3

POCO/alioth_id/alioth:11/RKQ1.200826.002/V12.5.2.0.RKHIDXM:user/release-keys 2021-06-01

Thank you 🙏
[Magisk] Didgeridoohan:
@Last_SiN Thank you. That works indeed.

@NOS_bzone Thank you, I'm currently testing some POCO F3 prints and that one does indeed pass CTS. (y)
[Magisk] Didgeridoohan:
Module updated to v5.4.1, fingerprints list updated to v131

Here's a small bug fix and another fingerprints list update. There's been a couple of bugs reported during the summer that I now finally had the time and piece of mind to take care of, and I also did something I rarely do: hunted down the fabled POCO F3 prints.

Not much more to say than thank you to those who contributed with prints for the list: @NOS_bzone, @Last_SiN and @ysc3839.

Changelog

Changed internet connection test to use Github rather than Google, for users that do not have access to Google in their countries.

Fixed a bug where prop values containing equal signs would be truncated.

Fix error message in log regarding copying system.prop during module installation.

Added fingerprints for the POCO F3 (Europe, Global, Indonesia, Russia, Taiwan and Turkey) and Redmi K40 China and updated the fingerprint for the Xiaomi Mi 8 Explorer. Fingerprints list updated to v131.
[Magisk] ugurkrdmr:
My phone (Huawei Mate 10 Lite[RNE-L01] is not on the list. Can you add it or help me with another way to prop fingerprint fix my device.
[Magisk] Didgeridoohan:
No, it's not. And when a device is missing from the list that's generally because noone has submitted it...

If you can find a print I'd be happy to add it to the list. Here are some tips on how to find a print:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

And here are the details on what's needed when submitting a print:

https://github.com/Magisk-Modules-R...aster/README.md#how-do-i-submit-a-fingerprint

I'm not sure what you mean by "another way to prop fingerprint fix my device", but it's perfectly possible to use another device's print to pass CTS:

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

If you've got further questions you can probably find them in the docs, but I'm always here to help.
[Magisk] Xoby:
Hello, dear developer. Thank you for the work done, I have a question for you, is it possible to achieve Google certification on ported rom? I have a POCO F3 device and installed the Android 12 Beta 4 port yesterday and it is not certified. I tried to change the fingerprint from another certified device, but it was always not certified. Is there a chance to fix it in some other way or is it a feature of the rom (port)?
[Magisk] Didgeridoohan:
Most likely you'll also need to force basic key attestation:

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
[Magisk] Xoby:
it seems that it is not supported on the 4th beta. I also tested safetynet-fix-2.0.0, but it didn't work with MHPC. Anyway, thank you for the answer, so it's not possible to solve it yet
[Magisk] Chicada:
Hey, Please add fingerprint for Samsung J6 (2018),

Thanks!
[Magisk] Didgeridoohan:
Similar questions get asked all the time, so I'll just link you the post I made yesterday:

https://xdaforums.com/t/module-magi...p-edits-and-more-v5-4-1.3789228/post-85488245
[Magisk] Chicada:
Ohh, sorry, I'll flash stock rom, and get fingerprint,

Sorry for the inconvenience!
[Magisk] ugurkrdmr:
I did like you said, used any of fingerprints. Phone passes CTS test successfully but... Play store certificate is seems valid but i can't find Netflix, DSTV Now etc. on store.
[Magisk] Didgeridoohan:
If you pass CTS and the Play Store now reports certified and Netflix doesn't show up, start by waiting. Could be that some time is needed for everything to register properly.

Could be that there's something else though. I've seen similar things when playing around with one of my test devices, but I never did dig any deeper into that so I don't know that it could be.

You could just get the apk from apkmirror and install manually. After that you should be able to find it in the Play Store.
[Magisk] ugurkrdmr:
I waited more than 20 hours, Netflix is not showing up :/
[Magisk] Didgeridoohan:
I'm that case you have my second suggestion...
[Magisk] ugurkrdmr:
I already did it last night, Netflix is installed on my device but i just wanna get updates from play store, so despite of i installed APK from apkmirror, Netflix didn't show up...
[Magisk] Didgeridoohan:
Interesting... In that case I can't help you, since that solution worked fine for me and I don't know that the underlying issue is.
[Magisk] ugurkrdmr:
Sad :( anyway, thx mate, have a good day.
[Magisk] poloPonyo:
Hello dev. First of all thank you for all the amazing work you're doing.

Im trying to pass CTS but I just can't

I tried changing my fingerprint to another random one (Similar to my device since my devices fingerprint is not on the list) but it didn't work and evalType stayed HARDWARE. Tried another one and I got into a bootloop. Fixed the bootloop and that's why I'm scared to try more fingerprings since this is my main device and not a testing device. Installed EdXposed with Riru and HiddenCore module to pass CTS, still didn't work. Not only that it didn't work, even basicingegrity started to fail. I tried to find my devices fingerprint and I only found a different model, same device. So I guess no luck. I have run out of ideas lol. Any help would be appreciated guys. Ty.
[Magisk] Didgeridoohan:
If you want to use Xposed-like mods and pass SafetyNet you're probably better off using LSPosed. It has a better success at staying off Google's radar.

What you probably need is to force the key attestation to not use the hardware check (and if you're using a custom ROM a certified device fingerprint):

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation
[Magisk] poloPonyo:
Thank you for the reply. No I'm on stock rom.

And I've tried installing kdrag0n's SafetyNetFix but it doesn't support armeabi-v7a.
[Magisk] Didgeridoohan:
If you're on a stock ROM you do not need to tinker with device fingerprints (unless it's a weird device that doesn't get certified by Google), and since it's aarmeabi-v7a device it's also unlikely you'll need the SafetyNet Fix.

If you can't pass SafetyNet you've probably got other issues... If you could upload the logs from this module (there's an option for saving them in the main menu) I could take a look and see if anything stands out
[Magisk] poloPonyo:
Also wanted to point out that whenever i restart my phone it says Not running Samsung Official software. Im 100% sure im on stock Rom but I rooted my phone through a youtube tutorial and the file that I downloaded (the firmware file) was already rooted so I just had to flash it with TWRP. Maybe my phone thinks its a custom rom. Also these are the only logs i could find on the magisk menu. Not that experienced. Sorry.
[Magisk] Didgeridoohan:
There are no logs attached (maybe you need to upload them somewhere and send the link), and I meant the module's main menu (currently option 7 - Collect logs).
[Magisk] poloPonyo:
I think I got them. Had to get them manually. Hope these are the right ones.

logs.zip - AnonFiles

anonfiles.com
[Magisk] ppr01:
*disregard*
[Magisk] Didgeridoohan:
Not seeing anything that pops out... Possibly one of your modules might be causing issues, so it's worth a shot disabling them all and trying again.
[Magisk] poloPonyo:
Just tried it. Disabled all of my modules and rebooted. Still the same.

basicintegrity: passes

ctsProfile: fails

evalType: HARDWARE
[Magisk] Didgeridoohan:
Well, if it's actually using hardware attestation I suggest you head over to the SafetyNet fix thread and ask for help there:

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/

You'll need to give all possible details regarding your device and problem, or the chances of actually getting any help decreases greatly. I don't think there's anything I can help with here...
[Magisk] nikhilmanudhane:
I flashed a fingerprint for my device using termux, however after rebooting, it has gone into fastboot loop.

flashing dtbo and twrp not helping.

Please help.
[Magisk] Didgeridoohan:
If it's caused by this module you can easily revert those changes by disabling or resetting the module, either from TWRP or with the inbuilt feature described here:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

(I suggest trying the reset option)
[Magisk] nikhilmanudhane:
phone not going into recovery mode, how can I use TWRP?

Is there any other way?