yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Fingerprints list updated to v123

I have a bunch of prints that's been updated in this update (mainly OnePlus, thank you @Some_Random_Username). And I also finally have a little bit of spare time... Had two large exams this week (one of which I'm pretty sure I flunked) and now I have a whole week until the next course starts. Yay.

This update is using prints provided by @Ema_Prowler, @DevRiturajKumar on GitHub, @Some_Random_Username, @a5782033 and @Displax. Thank you guys!

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

New

OnePlus N10 5G Metro

OnePlus N10 5G T-Mobile

OnePlus N100 Metro

OnePlus N100 T-Mobile

Redmi Note 9 Pro Max India

Samsung Galaxy Tab S7+ WiFi

Update

Motorola Moto G6

OnePlus 6 to Nord, Many different variants (32 prints)

Xiaomi Mi A2 and Mi A3
[Magisk] Some_Random_Username:
Sorry to annoy, but you made a small typo in README and fingerprint file: it's BE2015, not BE205. 😛

Hopefully you get the other one right 😛
[Magisk] Didgeridoohan:
Thanks for keeping an eye on things. Fixed (and since I copy paste that list it wasn't just the README).
[Magisk] OFShuvo:
Xiaomi Redmi 6 Pro

xiaomi/sakura/sakura:9/PKQ1.180917.001/V12.0.1.0.PDICNXM:user/release-keys
[Magisk] Didgeridoohan:
What's the corresponding security patch date?
[Magisk] Prit Kumar:
Plz add Lenovo K6 Power device fingerprint.
[Magisk] Didgeridoohan:
Would love to, but I need the data for it first:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] OFShuvo:
It's 05/07/2020
[Magisk] Didgeridoohan:
Thank you, but the print does not pass CTS. Either it's not certified, or that's the wrong security patch date for that print.
[Magisk] DjLeleX:
Please update/add fingerprint

Samsung Galaxy S10e - SM-G970F

samsung/beyond0ltexx/beyond0:11/RP1A.200720.012/G970FXXU9FUBD:user/release-keys_2021_03_01

Samsung Galaxy S10e - SM-G970N

samsung/beyond0lteks/beyond0:11/RP1A.200720.012/G970NKSU5FUBD:user/release-keys_2021_03_01

Samsung Galaxy S10 - SM-G973F

samsung/beyond1ltexx/beyond1:11/RP1A.200720.012/G973FXXU9FUBD:user/release-keys_2021_03_01

Samsung Galaxy S10 - SM-G973N

samsung/beyond1lteks/beyond1:11/RP1A.200720.012/G973NKSU5FUBD:user/release-keys_2021_03_01

Samsung Galaxy S10 Plus - SM-G975F

samsung/beyond2ltexx/beyond2:11/RP1A.200720.012/G975FXXU9FUBD:user/release-keys_2021_03_01

Samsung Galaxy S10 Plus - SM-G975N

samsung/beyond2lteks/beyond2:11/RP1A.200720.012/G975NKSU5FUBD:user/release-keys_2021_03_01

Samsung Galaxy S10 5G - SM-G977B

samsung/beyondxxx/beyondx:11/RP1A.200720.012/G977BXXU6FUBD:user/release-keys_2021_03_01

Samsung Galaxy S10 5G - SM-G977N

samsung/beyondxks/beyondx:11/RP1A.200720.012/G977NKSU4FUBD:user/release-keys_2021_03_01
[Magisk] 33seadog:
Mediapad T5

Ags2-l03 android 8, august 2020 security patch magisk 20.4

Is there a finger print that works?
[Magisk] Didgeridoohan:
There are some Huawei prints included in the list, so you could try one of those. Or try to find one that I could add to the list:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x

Although, prints for newer Huawei devices won't be Google certified since the "conflict"...
[Magisk] Didgeridoohan:
@DjLeleX I can't get any of those prints to pass CTS, so I'm guessing they're not from any officiall stable release... If they are, maybe the security patch date is wrong.
[Magisk] DjLeleX:
Sorry,

here's a partial list updated (the security patch date is the first of March 2021):

Samsung Galaxy S10e - SM-G970F

samsung/beyond0lteeea/beyond0:11/RP1A.200720.012/G970FXXU9FUBD:user/release-keys

Samsung Galaxy S10 - SM-G973F

samsung/beyond1lteeea/beyond1:11/RP1A.200720.012/G973FXXU9FUBD:user/release-keys

Samsung Galaxy S10 Plus - SM-G975F

samsung/beyond2lteeea/beyond2:11/RP1A.200720.012/G975FXXU9FUBD:user/release-keys

For others device (N versions and G977B), I won't be able to get my hands on them anymore, so I mistakenly thought that those fingerprint were right, I'm sorry.
[Magisk] OFShuvo:
Try 01/07/2020
[Magisk] XirXes:
I got it working on my T-Mobile Motorola Z2 Force running lineage 18.1 using the fingerprint from the latest T-Mobile stock rom.

motorola/nash_tmo_c/nash:8.0.0/OCXS27.109-51-14-7/12:user/release-keys

Security patch 2019-07-01
[Magisk] ipdev:
Have not tested..

Redmi 6 Pro India

Cheers. :cowboy:
[Magisk] RedTonight:
Hi all,

For ANDORID 11,

After installing Magisk , Universal Safetynet Fix , Magiskhide props config basicIntegrity was passed but ctsProfile was failed.

I updated my 'ro.build.fingerprint' (just this) with STOCK SW value. CtsProfule still Failed.

But Also updating 'ro.build.version.security_patch' from same STOCK SW value , ctsProfile was Passed.

So update both the property.

cheers.!!
[Magisk] Didgeridoohan:
Yes, that is known. On ROMs with a build date after march 2018 (so not A11 exclusive) you need to match the print with the correct security patch date:

https://github.com/Magisk-Modules-R...E.md#matching-the-android-security-patch-date

Was there some print included with the module that has the wrong date?
[Magisk] reintal:
Can u add fingerprint for Sony xperia 10 Plus (l4213)
[Magisk] itsnotAmit:
Hey, could you find any solution to that? Even I want to use Call Screening and "Faster Voice typing" but the brightness bug is the only thing bugging me right now.
[Magisk] Displax:
Look like it`s fixed now: https://github.com/topjohnwu/Magisk/commit/7da36079c1cd4c37cc8104afd540e0ee02cd0c08
[Magisk] Didgeridoohan:
I'm planning on testing that, but am currently pretty swamped. If anyone has the time to confirm whether the commit in question now allows long prop values, like the one below, that would be great.

Xiaomi Mi A3 Europe (11)=Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.3.0.RFQEUXM:user/release-keys__2021-01-05
[Magisk] Didgeridoohan:
There's a section of the docs dedicated to exactly that question:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x

Adding new prints relies almost exclusively on submissions from users...
[Magisk] Ota2501:
Anyone with galaxy a8 got trough csc on safety net? Tried many fingerprints, none worked, i am on Android 11 from the newest treeui rom
[Magisk] Didgeridoohan:
You already have the most likely solution in a reply to your other post (for future reference: don't double post)

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84745501

And if you want to dig further you've got lot's of info in the docs (for future reference, always check the manual first):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84745501
[Magisk] Ota2501:
Sorry wont happen again.
[Magisk] ineedroot69:
@Didgeridoohan how does reset all options/settings work? like for instance i modified some parameter on device simulation then decided to "reset all options/settings" does it restore the default parameter i modified on device simulation or no??
[Magisk] Didgeridoohan:
It restores everything to stock.
[Magisk] ineedroot69:
that's great to hear
[Magisk] juniordnz:
Sorry if here's not the place to post this, but I'm struggling with some banking apps from Brazil on my S6 (920I) with LOS17.1.

I've tried different fingerprints like S6 (920F), S10+, S10e. I'm enabling simulation on all props, everything works fine, props are correctly replaced on "about phone" but the banking apps keep saying my device is not using an original manufacturer ROM.

Simulating these fingerprints together with using magisk hide shouldn't make these apps "believe" the information I'm simulating? Am I missing something?
[Magisk] OFShuvo:
Brother can you tell me how to use this file?
[Magisk] Didgeridoohan:
Can confirm that the commit in question finally allows the above fingerprint to be set and it passes CTS perfectly. Should be a prints list update coming in the near future (today or tomorrow).
[Magisk] Didgeridoohan:
I'm planning on updating the list very soon, so the print will be included there. But, if you don't want to wait you can rename that file to "printslist" and place it in your internal storage, as described here:

https://github.com/Magisk-Modules-R...lob/master/README.md#custom-fingerprints-list
[Magisk] Didgeridoohan:
The device simulation is very basic and if the app in question is looking for other props you need to change those manually ("Add/edit custom props").

Maybe they're just doing a grep for props containing "lineage", or something like that (I'm just guessing, of course)... If so you'd have to change all those props as well.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Didgeridoohan:
Fingerprints list updated to v124

Finally got around to updating the prints list with all the new prints that have been submitted. Thank you @OFShuvo, @DjLeleX, @ineedroot69, @Howard20181 at Github, @XirXes, @ipdev and @firetablethelp for providing the prints. And @DjLeleX, I did manage to get every single S10 print you submitted to pass CTS eventually.

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

Special note: the Xiaomi Mi A3 Europe fingerprint is a print that will not be able to be set on any Magisk release prior to build 22007 (queue the Twilight theme).

New

BLU Vivo XI

Motorola Moto Z2 Force T-Mobile

Redmi 9T Global

Samsung Galaxy S10 (several different variants)

Xiaomi Mi 9 China

Xiaomi Mi A3 Europe

Xiaomi Redmi 6 Pro China & India

Updated

Samsung Galaxy S10 (several different variants)
[Magisk] 2B_4G10:
Hi ! Thank you for the great things you do!

This is my phone's Fing.Prt.:-

- Xiaomi Mi 10 Ultra, 128gb

- Securt. Patch date: 2021/03/01

$ su

etprop ro.build.fingerprint <

Xiaomi/cas/cas:11/RKQ1.200826.002/V12.5.1.0.RJJCNXM:user/release-keys

:/data/data/com.termux/files/home #
[Magisk] OFShuvo:
Thanks a lot brother. It's works perfectly in my Redmi 6 pro device.
[Magisk] itsmir:
Please bear with this idiot!

Installed via Magisk, rebooted and phone is virtually unusable. No wifi, and screen/icons all faded out. I can access a terminal but "props" command does nothing.

Attempted to uninstall the module via Magisk - same issue. Have reinstalled it now.

Phone - Mi9T on xiaomi.eu rom/Android10

Can anyone help!!
[Magisk] ineedroot69:
you need to type "su" before "props"
[Magisk] Didgeridoohan:
Only if using Termux (generally). But Termux is a bit of an overkill and I don't recommend if you don't need to do advanced stuff.
[Magisk] Didgeridoohan:
You need to provide a bit more info for me to help properly. For example: what do you mean when you say the the props command does nothing? What's the output?

And the all-important logs:

https://github.com/Magisk-Modules-R...lob/master/README.md#collecting-logs-manually
[Magisk] Sherbi:
Is this Mobile will be available soon ???

Xiaomi Mi 10T Global (11)=Xiaomi/apollo_global/apollo_global:11/RKQ1.200826.002/V12.1.1.0.RJDMIXM:user/release-keys

or is there any idea to make my custom ??
[Magisk] Didgeridoohan:
Making a custom list is very easy, so if you really want it now you should go ahead and make one of those.

I'll of course test that print and add it in the next update of the list, but I'll also need the corresponding security patch date for the print or I can't test/include it...
[Magisk] Sherbi:
Patch Data is 01-02-2021
[Magisk] itsmir:
There was no output at all when using the props command. Waited minutes.... no output at all.

After closing the terminal app, the phone froze & on rebooting only fastboot was accessible. So have flashed global fastboot rom, TWRP & magisk 22 - and will try again later. fingers crossed!!
[Magisk] DjLeleX:
Update S10 series to April security patch:

Samsung Galaxy S10e - SM-G970F

samsung/beyond0ltexx/beyond0:11/RP1A.200720.012/G970FXXU9FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10e - SM-G970N

samsung/beyond0lteks/beyond0:11/RP1A.200720.012/G970NKSU5FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10e - SM-G970F (Europe)

samsung/beyond0lteeea/beyond0:11/RP1A.200720.012/G970FXXU9FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 - SM-G973F

samsung/beyond1ltexx/beyond1:11/RP1A.200720.012/G973FXXU9FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 - SM-G973N

samsung/beyond1lteks/beyond1:11/RP1A.200720.012/G973NKSU5FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 - SM-G973F (Europe)

samsung/beyond1lteeea/beyond1:11/RP1A.200720.012/G973FXXU9FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 Plus - SM-G975F

samsung/beyond2ltexx/beyond2:11/RP1A.200720.012/G975FXXU9FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 Plus - SM-G975N

samsung/beyond2lteks/beyond2:11/RP1A.200720.012/G975NKSU5FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 Plus - SM-G975F (Europe)

samsung/beyond2lteeea/beyond2:11/RP1A.200720.012/G975FXXU9FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 5G - SM-G977B

samsung/beyondxxx/beyondx:11/RP1A.200720.012/G977BXXU6FUCD:user/release-keys_2021_04_01

Samsung Galaxy S10 5G - SM-G977N

samsung/beyondxks/beyondx:11/RP1A.200720.012/G977NKSU4FUCD:user/release-keys_2021_04_01
[Magisk] Didgeridoohan:
Sounds very strange. If all you did was to install the module, without setting it up in any way, you shouldn't see that kind of issues. And especially not if you uninstall the module...

Like I said, the only way for me to have any chance of figuring this one out you need to provide the module and Magisk logs. But, maybe it was some kind of fluke and your next attempt will be flawless.
[Magisk] itsmir:
It was indeed odd - was a little nervous of trying again so tried the SafteyNet-Fix v1.1.1 module from droidholic and all is now good. Fully rooted, safetynet passed and banking apps working again. This time I'm using an official fastboot rom & not the xiaomi.eu one. Thanks for your time!
[Magisk] R3dD3vil7:
Hi All,

I deployed LineageOS 18.1 on my Moto Z3 Play and realized I cannot use:

1. Biometry in some banking apps.

2. Google Pay.

I was not aware it may happen when I decided to flash my device. However, #1 has been solved with Magisk Hide option, unfortunately it did not work for #2. SafetyNet is failing for ctsProfile (it is OK for basicIntegrity, evalType BASIC). I read about the possibility to change device's fingerprint with Magisk props, however as my device was not listed there I chose to use Moto G7 with Android 10. Fingerprint change went OK but after reboot SafetyNet check is still failing and Google Pay does not allow me to add any card.

There is one more thing which makes me worried - I cannot run Magisk props anymore after fingerprint change. It is reporting:

props: inaccessible or not found 127

and because of that I cannot do another fingerprint changes.

I have already tried to find such a case but I did not find anything similar. Could you please help me with solving both cases? Of course the one with Google Pay is more important for me but I suppose to fix it I will also need to solve the one with props.
[Magisk] Didgeridoohan:
Since you're using a custom ROM it is very likely that you need to change the device fingerprint to pass CTS. But it is also possible that you need to use the new Universal SafetyNet Fix (the evalType field in the Magisk app's SafetyNet window isn't entirely reliable anymore).

https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation

Regarding props not found:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#props-not-found
[Magisk] R3dD3vil7:
Regarding props not found, I have seen that already and unfortunately neither of these options apply.

I have just reinstalled both props and BusyBox and that did the trick. Now I changed a fingerprint to Google Pixel 5 (Android 11). After restart props is still OK, SafetyNet check in Magisk pass fully (ctsProfile too) and Google Pay works fine as well.

Thanks for your reply, cheers.

Update:

I assumed it works as it was possible to add a card eventually. However it seems it will not work as I have got 'not configured' info above the card. I will check tomorrow the option you linked.

Update 2:

I checked Google Pay in a shop and it works fine even with this 'not configured' message, so on my site topic is closed and everything works correctly.
[Magisk] kamild_:
Fingerprint for POCO X3 Pro Global:

POCO/vayu_global/vayu:11/RKQ1.200826.002/V12.0.4.0.RJUMIXM:user/release-keys

ro.product.manufacturer: Xiaomi

ro.product.model: M2102J20SG

ro.vendor.build.securty_patch: 2021-03-01

ro.build.fingerprint was the only prop that needed to be changed to let a Xiaomi.eu ROM pass SafetyNet fully.
[Magisk] b0mb:
Fingerprint for Redmi Note 10 Pro - works fine using latest xiaomi.eu ROM ;)

Redmi/sweet_global/sweet:11/RKQ1.200826.002/V12.0.6.0.RKFMIXM:user/release-keys
[Magisk] Didgeridoohan:
Thank you. What's the security patch date for that print?
[Magisk] b0mb:
01.03.2021 😉
[Magisk] Evon88:
i want to cry 😭😭

this guy saved my life

finally after idk how much time trying everything

finally safetynet working good

bro whatever you are.. you are just a legend, i hope if i can donation for this dude someday, guys this dude doing the big work here

just thx from my deep heart
[Magisk] VPH20:
Samsung A5 2017 here, what to insert into terminal to hide rooted lineage os (latest)? I have Magisk and this module. Pls help.
[Magisk] Displax:
Pixel's update:

Pixel 3=google/blueline/blueline:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 3a=google/sargo/sargo:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 3a XL=google/bonito/bonito:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 4=google/flame/flame:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 4 XL=google/coral/coral:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 4a=google/sunfish/sunfish:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
Pixel 5=google/redfin/redfin:11/RQ2A.210405.005/7181113:user/release-keys__2021-04-05
[Magisk] Didgeridoohan:
Depends on that it is that you actually mean when you say "hide rooted lineage os"... If all you want to do is to pass CTS you likely need to change the device fingerprint. It is also possible that you need the new Universal SafetyNet Fix. It's all covered in the docs:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#usage

https://github.com/Magisk-Modules-R...b/master/README.md#what-option-should-i-use-1

If you want something else you need to be more detailed in your query...
[Magisk] liyiecho:
Hi ! Thank you for the great things you do!

This is my phone's Fing.Prt.:-

- Xiaomi Mi 10S

- Securt. Patch date: 2021/04/01

$ su

getprop ro.build.fingerprint <

Xiaomi/thyme/thyme:11/RKQ1.200826.002/21.4.8:user/release-keys
[Magisk] VPH20:
Some banking apps detect device rooted, so need to hide that. This all is just very new to me. Yes i need a fingerprint but the command line all what to enter to terminal ~
[Magisk] Didgeridoohan:
How to use the module is covered in the links I posted, but a tl;dr is that you enter the command props (depending on your terminal app, you might have to call su first) and then pick the options you need and follow the on-screen instructions.
[Magisk] Didgeridoohan:
Thank you, but unfortunately that print does not pass CTS. Either the print isn't certified or that's the wrong security patch date.
[Magisk] Didgeridoohan:
Fingerprints list updated to v125

Got a bunch of Pixel prints and Galaxy S10 prints for this month, together with a couple of others. Thank you @2B_4G10, @DjLeleX, @TheReduxPL, @b0mb and @Displax for keeping me busy.

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

New

POCO X3 Pro Global

Redmi Note 10 Pro Global

Updated

Google PIxel 3-5 (all variants)

Samsung Galaxy S10, S10 5G, S10 Plus and S10e (most variants)

Xiaomi Mi 10 Ultra China
[Magisk] liyiecho:
The data came from miui developer rom, it's my mistake. In the stable rom, the data is:

- Xiaomi Mi 10S

- Securt. Patch date: 2021/03/01

$ su

getprop ro.build.fingerprint <

Xiaomi/thyme/thyme:11/RKQ1.200826.002/V12.0.10.0.RGACNXM:user/release-keys
[Magisk] patp:
Cananyone help me pass CTS on a Xiaomi Mi Mix 3 (Perseus)? I had it working on crDroid 6(Q) but nothing works on v7.5 (R).

I've tried various fingerprints and it reports basic integrity passed, but not CTS. I've flashed the latest Safetynet fix 1.1.1, and cleared all data from Play Services and Play store. I have latest Magisk, hidden, and Magisk Hide applied to all the Play stuff.

What can I do?
[Magisk] Didgeridoohan:
And you've made sure that MagiskHide works otherwise?

Do you have any Magisk modules installed, or other mods? Modules doing bind mounting are known to sometimes break SafetyNet, as an example...

Could be a bunch of things really, but let's start there.
[Magisk] patp:
Thanks! Yes, Magisk Hide is working, I already used it to permit an app that detected root and refused to run until I hid it. Checked again with a root check app.

No other modules, just props config and safety net fix.
[Magisk] Didgeridoohan:
Have you tried the test version of USNF, to rule out that there's some incompatibility with the v1.1.1 method?
[Magisk] patp:
Just tried that, no luck. I cleared Play data before checking. Also tried another fingerprint, nope.

Is there anything else I can try?
[Magisk] Didgeridoohan:
Sounds like you've tested the regular stuff. Could be the ROM itself that's incompatible...

More (if you haven't seen it already):

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] patp:
Ugh, really need contactless payments. If is not compatible, is that game over for this ROM? Can the developer make it compatible in a future release?
[Magisk] Didgeridoohan:
If it is the ROM that's a possibility, sure... Checking with other users of the same ROM if they can pass CTS could be a start.
[Magisk] Farrukh2002:
Any fix for my device poco F1. Safetynet fails even when magisk is hidden.View attachment 5279547
[Magisk] Didgeridoohan:
That's not an issue with SafetyNet, but with the Magisk app. There's probably been some kind of update to the API that needs to be implemented... Try a different SafetyNet checker (and there might be that some of those are affected by the same kind of API update, so try several).
[Magisk] posteo:
To whom it may concern;-)

Everything worked well passing SN till updating Redminote8T Europe to New Firmware:

fw_willow_miui_WILLOWEEAGlobal_V12.0.3.0.QCXEUXM_07285b429f_10.0.zip.

Do i have to wait for New updated fingerprint list? Actual is v125.

Running LOS 17.1 rooted

Brgds
[Magisk] valunthar:
Any suggestions on fixing safetynet on a pixel 5? I've tried the latest version of universal safetynet fix and I've set the device fingerprint to pixel 3a, and I've cleared all play store storage with no luck. the device is running rooted lineage 18.1
[Magisk] okanorman:
Looking for Xiaomi Mi Max 3 Global,Android 10 certified fingerprint.
[Magisk] VPH20:
I need fingerprint.. to enter to console. Samsung Galaxy A5 2017 Lineage OS latest.. what to enter to console?
[Magisk] th3legend:
Just pushed a new canary build with SafetyNet checking functionality restored. Considering pushing a new early public release after a few more bug fixes.

Quote Tweet

John Wu

@topjohnwu

· Apr 14

Update: got a new API key working, will push a new update soon