yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
The first time around, it was yesterdays build: 2018080910. I may have put that in that older post. The martyfender-test.zip was on today's build: 2018081011.

What I just posted was on todays build: 2018081011.

If you need more info, let me know.

Here is my full disclosure, I don't even need this module with Magisk Hide enabled in Magisk, to pass safety net and play store certification. I only added the module to test if module installs were working in unofficial builds and out of curiosity about this great module you have created. I've even thought about testing other build fingerprints to see if they work on my device. I could give you the Nextbook fingerprints, but I'm not sure how useful they would be, since it is somewhat of a unique device created by Yifang Digital, in ShenZhen,China.

OT here (I thought about posting this in the general thread): I wish I could buy more of them, but Nextbook silently changed the hardware to ARM, a much smaller battery, with Android 7.01, so I have no custom recovery to be able to root them, like [MENTION=2472806]vampirefo[/MENTION] 's. recovery for the 6.0.1 x86.

The manufacturer apparently purposely disabled fastboot/bootloader mode. The option exists in the stock recovery menu, but it then boots to a black screen and the command, fastboot devices, shows no devices attached. ADB shows the devices when booted normally, though.

I also got a Smartab at Walmart's black friday sale, cheap, $28, with Android 7.0.2 and fastboot is apparently disabled in it also. Have you ever encountered or heard of such a thing? I would like to be able to root but without a stock rom, I'm not sure how, especially without fastboot.

Thanks
[Magisk] martyfender:
Should I replace this also on my other tablets? I am now on [MENTION=3306843]kantjer[/MENTION] 2018081113. Also does doing this replace the one installed by Osmosis's busybox for Android NDK module? Or will osmosis be updating his module, also?
[Magisk] kantjer:
My 2018081113 build already has the FrankeNDK build Busybox
[Magisk] Didgeridoohan:
That replaced [MENTION=4544860]osm0sis[/MENTION] Busybox on that device, yes. There's no need to replace anything else, since I'm pretty sure he's gonna look into the stuff we found here and bring out an update (no ETA).
[Magisk] martyfender:
Isn't that only Magisk internal busybox, though? If I run the first command mentioned previously on one of the tablets updated to todays build, without his test busybox he provided, I get the monotonic error and the 0 byte busybox file on the sdcard.
[Magisk] Didgeridoohan:
That's correct. Although it seems like the Magisk internal busybox might have been fixed by a commit before FrankeNDK, but that's a different story... :laugh:

OT: About your question for advice about tablets, I'm not the guy to ask. I recently bought a Huawei Mediapad M5, because I need some kind of tablet for when I'm starting my studies in three weeks. It wasn't cheap, and with Huawei's bootloader fiasco it doesn't seem like it's gonna be easy to root (but I'm hoping [MENTION=7050182]MishaalRahman[/MENTION]'s hint about XDA changing Huawei's mind pays off). It was simply the only tablet I could get my hands on that ticked most of the boxes. Fortunately I only need it for easy access to my literature and some media consumption...

And I almost forgot: I find that RoyalBlue is a nice text colour that works with both black and white themes.
[Magisk] Didgeridoohan:
If you pass the CTS profile you can get your Play Store to be certified (might have to clear data for it first though).

If you're using a custom ROM you need to use a certified fingerprint (there are loads of them included in the module, and in the docs you can find info on how to get one if there isn't one for your particular device). And, if your device uses hardware backed key attestation you need the new Universal SafetyNet Fix.

Some reading about that:

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

And some further reading on what's needed to pass SafetyNet:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] ineedroot69:
holy fvk ahaha let's go would recommend this module 10/10 (y) :love:
[Magisk] FivEawE:
Xiaomi Redmi Note 8 Pro (begonia) Europe A10 - Update

[ro.product.manufacturer]: [Xiaomi]
[ro.product.model]: [Redmi Note 8 Pro]
[ro.build.fingerprint]: [Redmi/begonia_eea/begonia:10/QP1A.190711.020/V12.0.4.0.QGGEUXM:user/release-keys]
[ro.build.version.security_patch]: [2021-02-01]
[Magisk] Didgeridoohan:
Fingerprints list updated to v119

Another batch of prints submitted, tested and added to the list. Thank you @Displax, @marat2509 and @FivEawE.

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

Xiaomi Redmi 9

Updated

Nvidia Shield TV 2015

Nvidia Shield TV 2015 Pro

Nvidia Shield TV 2017

Nvidia Shield TV 2019

Nvidia Shield TV 2019 Pro

Redmi Note 8 Pro Europe
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 3a=google/sargo/sargo:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 3a XL=google/bonito/bonito:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4=google/flame/flame:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4 XL=google/coral/coral:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4a=google/sunfish/sunfish:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 4a (5G)=google/bramble/bramble:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
Pixel 5=google/redfin/redfin:11/RQ2A.210305.006/7119741:user/release-keys__2021-03-05
[Magisk] Didgeridoohan:
Fingerprints list updated to v120

@Displax is back with this month's Pixel prints. Yay!

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.

Updated

Google Pixel 3 - 5, all variants
[Magisk] 73sydney:
At least you didnt Squee.... :)
[Magisk] Displax:
Razer Phone 2

razer/cheryl2/aura:9/P-SMR6-RC001-RZR-201022/3201:user/release-keys_2020-11-05
[Magisk] Displax:
Fixes:

Rename: "Xiaomi MI 10 Europe" >>> "Xiaomi Mi 10 Europe"

Rename: "Nvidia Shield K1" >>> "Nvidia Shield Tablet K1"

Rename: "Nvidia Shield Tablet" >>> "Nvidia Shield Tablet WiFi"

Add:

Nvidia Shield Tablet LTE (7.0):NVIDIA:SHIELD Tablet=nvidia/wx_un_do/shieldtablet:7.0/NRD90M/1928188_1065.2559:user/release-keys

Update:

Nvidia Shield Tablet WiFi (7.0):NVIDIA:SHIELD Tablet=nvidia/wx_na_wf/shieldtablet:7.0/NRD90M/1928188_1065.2559:user/release-keys
[Magisk] glothatik:
Hi all,

That device had not fingerprint yet:

Samsung [SM-A510F] (7.0):samsung:SM-A510F=samsung/a5xeltexx/a5xelte:7.0/NRD90M/A510FXXS8CSF3:user/release-keys__2019-07-01

# Samsung SM-A510F [Build Date - Jun 26 2019]
# ro.bootimage.build.fingerprint=samsung/a5xeltexx/a5xelte:7.0/NRD90M/A510FXXS8CSF3:user/release-keys
# ro.build.version.security_patch=2019-07-01
#
# ro.build.version.release=7.0
# ro.build.version.sdk=24
# ro.product.device=a5xelte
# ro.product.brand=samsung
# ro.product.manufacturer=samsung
# ro.product.model=SM-A510F
# ro.product.name=a5xeltexx
# ro.build.product=a5xelte
[Magisk] Didgeridoohan:
Quick heads-up on this one. I had a couple of minutes to test the last few submitted prints and they all passed except for this one. I even checked against Android Dumps and it matches the data there so I guess it isn't certified...
[Magisk] Displax:
Strange. Because it's official ROM. Maybe certification recall.

Can you, please, test this one?

razer/cheryl2/aura:9/P-SMR7-RC003-RZR-210107/3225:user/release-keys__2021-02-05
[Magisk] Didgeridoohan:
Yup, that one works.
[Magisk] T1tino:
Please add

LG k20 Plus

MP260

lv517

MetroPCS/lv517_mpcs_us/lv517:7.0/NRD90U/1833409570571:user/release-keys__2018-12-01
[Magisk] johnyu2003:
Please add, thanks

Xiaomi Mi 11(11.0)

Xiaomi/venus/venus:11/RKQ1.200928.002/21.3.1:user/release-keys
[Magisk] Didgeridoohan:
Securiy patch date?
[Magisk] johnyu2003:
2021-02-01
[Magisk] Sofiyan42:
كيف تحمل
[Magisk] Didgeridoohan:
Hi and welcome to XDA. If you are asking for help with something you're going to have up be a lot more detailed than that. Google translate gave me "how to carry", and that is difficult to interpret...

XDA also requires you to use English when posting (you are free to use translator software if you want). See the forum rules, rule #4 for details.
[Magisk] johnyu2003:
The fingerprint will be update in the next version?
[Magisk] Didgeridoohan:
Yes it will.
[Magisk] johnyu2003:
It's good to hear that, can't wait anymore:love:
[Magisk] :
Samsung Galaxy A7 2018 (SM-A750GN) - Android 10: samsung/a7y18ltedx/a7y18lte:10/QP1A.190711.020/A750GNDXU6CUA1:user/release-keys

Patch day: 2021-01-01
[Magisk] Didgeridoohan:
Turns out I misjudged something somewhere (when I replied with an affirmative previously I thought I had already tested it)... This print does not pass CTS, and I even took a peek over at Android Dumps and tried a few more versions and none pass. So I will not be including the Mi 11 in the next print update...
[Magisk] Didgeridoohan:
Fingerprints list updated to v121

A few new fingerprints, a few updated fingerprints and a couple of small name corrections. Thank you @Displax, @glothatik, @T1tino and @K-218 for your contributions.

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

New

LG K20 Plus LGMP260

Nvidia Shield Tablet LTE

Samsung Galaxy A5 2016

Updated

Nvidia Shield Tablet WiFi

Razer Phone 2

Samsung Galaxy A7 2018
[Magisk] johnyu2003:
Got it! Hope can have a solution to pass Google Pay. Thanks for your help
[Magisk] Didgeridoohan:
Use a Mi 10 print... And you'll likely also need the new Universal SafetyNet Fix to circumvent hardware backed key attestation. And then use the GPay db trick to actually make GPay work.
[Magisk] johnyu2003:
I find a solution to pass CTS, CN forum have made a magisk module to fix the print on Mi 11, you can try this versions.

ro.build.fingerprint=Xiaomi/venus/venus:11/RKQ1.200928.002/V12.0.22.0.RKBCNXM:user/release-keys

ro.build.description=venus-user 11 RKQ1.200928.002 V12.0.22.0.RKBCNXM release-keys

ro.build.version.security_patch=2021-01-01
[Magisk] Didgeridoohan:
Fingerprints list updated to v122

Quick update, thank you @johnyu2003

New

Xiaomi Mi 11
[Magisk] johnyu2003:
You are welcome ☺️
[Magisk] Spartacus500:
@Didgeridoohan

Another question, is it possible to change the OEM unlock option on Samsung devices to disabled by resetprop? Normal disabling of OEM on root with twrp is the system will not wake up, so I'm curious if resetprop can trick the system that OEM unlock is disabled.
[Magisk] Didgeridoohan:
If I remember correctly changing that prop value can change the option for real, not just make it look like it is. Be careful when experimenting...
[Magisk] Spartacus500:
You did not console me, maybe someone will check on Samsung with android 9.0 or higher whether the system will get up after such a procedure. Overall, when is this entry loaded? Immediately after booting the boot system or a little later? And do these entries work in TWRP?
[Magisk] pndwal:
FWIW, I don't think SQLite Fix is needed for working G Pay now; works for me and others with basic hiding...

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-84625277 PW
[Magisk] Ema_Prowler:
It does not work with the fingerprint that is currently listed on the moto g6 in your module

pleas add

MOTO G6 XT1925-1

motorola/ali/ali:9/PPSS29.55-37-7-6/16c5a7:user/release-keys

ro.build.description=ali-user 9 PPSS29.55-37-7-6 16c5a7 release-keys

ro.build.version.security_patch=2020-02-01

View attachment 5245173
[Magisk] mario0318:
So I'm not sure what changed exactly if it was a change in busybox module, or a package install thru Termux or an update to this MHPC module, but running props on Termux now displays a few "invalid alias name" warnings before loading the script. The module still works fine and so far it seems to just be warning messages.

But regardless of having reinstalled busybox-ndk thru magisk repo, or FeraVolts busybox charged module, or neither, the messages persist which makes me think it was after a particular module update some months back, it had been a while since I've updated this module. Here's a screenshot:

View attachment 5245223

Kind of leads me to another minor issue regarding updates because for some reason new updates do not appear on Magisk as new or available when the update button is refreshed, it simply never shows up. I would have to scroll down past my installed modules list and then some to find MHPC, compare my current installed version to the latest module version or release date and install. I know the module has an update mechanism within the scripts and that more often than not they are simply fingerprint list updates, but I still like to deploy new module versions when available via the Magisk interface.

Are either of these an issue for anyone else?
[Magisk] ipdev:
Not sure why the Moto G6 in the current list did not work for you. :unsure:

I just tested and both fingerprints passed for me.

Motorola Moto G6 (9):Motorola:moto g(6)=motorola/ali/ali:9/PPS29.55-34/0c5d:user/release-keys__2019-02-01
Motorola Moto G6 XT1925-10 (9):Motorola:moto g(6)=motorola/ali/ali:9/PPSS29.55-37-7-6/16c5a7:user/release-keys__2020-02-01

Only tested on Nexus 7 (2013) - Lineage 18.1

I am not sure what the exact difference between them but, there are three Motorola ali devices on Google's certified list.

Motorola moto g(6) ali XT1925-10
Motorola moto g(6) ali moto g(6)
Motorola moto g(6) ali moto g(6) (XT1925DL)

You noted XT1925-1, I assume that is the XT1925-10 that is on the certified list. :unsure:

Cheers all. :cowboy:
[Magisk] Ema_Prowler:
@ipdev

in my list of devices in hidden prop the second you listed the Motorola Moto G6 XT1925-10 does not appear.

And I do not know what the 1 with 10 will have to do with the model on the box says MOTO G6 XT1925-1.

The number zero I don't know where it comes from.

I tell you what I did with my device before the safetynet went off.

At first root the phone with one of the tutorials here XDA.

this one precisely (https://xdaforums.com/t/dont-using-newest-magisk-and-disabler-for-moto-g6.4006983/).

I followed the steps and safetynet all ok.

Now a day ago I updated the magisk because I found out that in magisk you can add modules. but it asked me to update.

then as I saw that the safetynet did not work, download the new version of the dm_verity that is in that post and apply it with twrp, but it did not work then install the hidden prop and apply the fingerprint and it did not work either.

Note that I have the phone updates blocked, that is, (the update app has been released). I have noticed that when applying a fingerprint after restarting a system update notification comes out which ends normally, this is just an observation that I comment on nothing else and also say that I have disabled and that I do not.

well and nothing more to say if you have any questions about the status of any part of my device I will gladly let you know here are some photos.View attachment 5245277View attachment 5245279
[Magisk] Didgeridoohan:
@Ema_Prowler The print in the module works just fine for passing the CTS profile check, you've got something else going on.

First thing to check whenever MagiskHide fails after an update is the MagiskHide toggle in the app settings. If it's off, turn it on. If it's on toggle it off and on again and then reboot and make sure that it's still active.

There's a small checklist in the module documentation you can check as well:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check

The update notification that pops up when you've changed the fingerprint is perfectly normal since Android thinks you've updated when the print changes.
[Magisk] Didgeridoohan:
@mario0318 I don't see that behaviour with Termux (although I get another little error message that I'm gonna investigate). I'm assuming you do not see this with any other terminal apps? It doesn't look like anything to worry about though, just a small quirk with busybox preparation at start. Talking of which, the module should first and foremost use the Magisk internal busybox, but here it does look like one of your other installations is being used. I'd love to see your module logs.

And regarding updates:

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

You're seeing a changed date in the module list because of the fingerprint list updates, nothing else. And as you say, that has an internal update mechanism so I don't push a module update for a simple prints list change. What you're describing is perfectly normal and expected.
[Magisk] mario0318:
Got it. Now it makes sense. I missed that portion of your documentation. So if I ever see the update shown as new/available on the Magisk repo then it's a certainty there's updated module logic, else it is minor list updates.

Regarding the script warning messages, it also occurs with Terminal Emulator so it seems it's beyond Termux's config. I attached the log archive as requested.
[Magisk] Didgeridoohan:
My best guess is that the alias command on your device can't handle dots. Shouldn't have any effect on how the module functions.
[Magisk] Ema_Prowler:
I already tried everything, I don't know what else, but at least I know that it's the magisk hidde that doesn't work.

then I leave an image of the magisk detector.

What's wrong with this image other than the magisk hidde not working?

View attachment 5245973
[Magisk] Didgeridoohan:
Looks pretty normal, apart from the "Magisk Hide not working". Why it's not working I have no idea... Did you test it on a root app?
[Magisk] Ema_Prowler:
root working
[Magisk] Didgeridoohan:
No, I meant if you have tested MagiskHide on a root app to see if it doesn't see root anymore. Just like described under "Make sure that MagiskHide is enabled and working" in the checklist I linked earlier...
[Magisk] Ema_Prowler:
If I did what you said and it works now, I flashed again in twrp magisk and it no longer exists, install the app on the cell phone, ramdisk appears: ok and it says that it is not installed and it does not give me the option to install in direct mode.

Now how is it installed with an img because it is the only option it gives me, the image would be the twrp?
[Magisk] Didgeridoohan:
Not quite sure what you mean... What did you do exactly, and what works? Did you uninstall Magisk? If you need to reinstall you can either use the patch image option or flash the installer from a custom recovery. It's all well documented here: https://topjohnwu.github.io/Magisk/install.html

Or did Magisk all of a sudden stop working?

Anyway, it sounds like we've moved outside the scope of this thread so it's probably better if you continue posting in the General support thread instead.
[Magisk] Ema_Prowler:
I give up I will do a wipe since I tried everything and everything and nothing works, there is something that I cannot see and I do not want to continue denying but I prefer to do a wipe of everything and start from scratch, also thank you all.
[Magisk] Some_Random_Username:
Hi folks, below are latest fingerprints currently available for OnePlus devices.

As always, OnePlus/OnePlus7/ fingerprint is for GM1901 and GM1905 / OnePlus/OnePlus7Pro/ fingerprint is for GM1911 and GM1917 / OnePlus/OnePlus7T/ fingerprint is for HD1901 and HD1905 / OnePlus/OnePlus7TPro/ fingerprint is for HD1911 and HD1917. Note I did not bother extracting A11 open beta fingerprints for 7/7T series as a build is supposed to land in stable channel by the end of the month .

Regarding the new Nord N10/Nord N100 T-Mobile and Metro by T-Mobile, I uploaded the full props at https://github.com/oxygen-updater/b...nord-n10/metro-by-t-mobile/10.5.8.BE88CF.prop , https://github.com/oxygen-updater/build-props/blob/master/opnord-n10/t-mobile/10.5.8.BE88CB.prop , https://github.com/oxygen-updater/b...ord-n100/metro-by-t-mobile/10.5.8.BE82CF.prop and https://github.com/oxygen-updater/build-props/blob/master/opnord-n100/t-mobile/10.5.8.BE82CB.prop . From their ro.product.system.model property, I gather that OnePlusN10TMO is BE2028, OnePlusN10METRO is BE2025, OnePlusN100TMO is BE2012 and OnePlusN100METRO is BE2015. Furthermore, the N10 5G global is BE2026, see attached for reference. View attachment 5248367

Spoiler content hidden.
[Magisk] Didgeridoohan:
I always get slightly nervous when I see that @Some_Random_Username has posted in the thread. Usually that means that there are a gazillion new/updated prints to test... :p
[Magisk] brhoomy101:
Is there a solution for the device?

-Samsung Galaxy S9+ / star2lte

-Android 10
[Magisk] rudix78:
Do you konw how to solve conflict between magisk hide and microG core services. Magisk hide has script that automatically hides microG core services and this results in CRASH. I need to manually remove microG from magisk hide list, then service starts working ... till next reboot. After reboot magisk again adds microG to hide list and service crash. Do you know how to remove microG permanently from magisk hide list?
[Magisk] Didgeridoohan:
That's way off-topic for this thread, but there's an open Github issue for that:

https://github.com/topjohnwu/Magisk/issues/3559

A couple of possible solutions: wait for John to deal with it one way or another, or edit the referenced (in the issue ticket) code and build yourself.
[Magisk] rudix78:
Thank you, I read that ticket (it's from last year), I was thinking about editing code (hide_utils.cpp:197) but I don't know where to find it in MagiskHide Props Config, that's why I thought this thread may help to guide me how to edit magiskhide config.
[Magisk] Didgeridoohan:
It's from December last year. Just a few months old... As long as it's kept open it's on John's radar.

And I think you've misunderstood what this module is for. It's used to change prop values using the Magisk resetprop tool, not to edit the source code and build a custom Magisk... If you want to edit and build yourself you've got John's instructions on how to build Magisk here: https://github.com/topjohnwu/Magisk#building-and-development
[Magisk] ineedroot69:
about device simulation what the data it pushes?? when I enable all I can't open any apps but not bootloop they just keep crashing
[Magisk] Didgeridoohan:
It just changes a few props (you can see which ones in the menu or the docs), but they've got lots of potential for causing issues, especially if you enable them all (as you've already seen). Hence the warnings in both menu and docs... My best guess is that there are conflicts between different props that is causing the problems.
[Magisk] ineedroot69:
I thought it would ask for which device model it would simulate but apparently you're the one who supposed to feed it with data
[Magisk] Didgeridoohan:
It will stimulate whatever device you've picked under the "Edit device fingerprint" menu.
[Magisk] Rafiul119:
Can i unlock all games max graphics by changing fingerprints?
[Magisk] Didgeridoohan:
I think you need to change the model for that, but you can easily enable that from the "Device simulation" menu once you've picked a fingerprint. Or you could just use the "Add/edit custom prop" to change only the model props, but you'd have to find the model value yourself.

I've never played with this stuff though, so please try it out and let us know.
[Magisk] Displax:
Xiaomi Mi A3

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.7.0.RFQMIXM:user/release-keys__2021-03-05

Xiaomi Mi A2

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