yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-1.3789228/post-85851553
[Magisk] Techguy777:
Yes I tried to do device simulation and change all props and bootloop. I can't win I have a Poco F3 with EU Android 11 and it's been a pain since I got it. Twrp doesn't work worth a crap either with it. I love the phone great performance for the money but tweaking with custom roms or anything is hard.
[Magisk] Didgeridoohan:
Activating all props in "Device simulation" often causes a bootloop, that's not specific to your device.
[Magisk] Philnicolls89:
I have a Samsung s10+ and have to use a shim mod of USNF to pass safety net, which changes my model number to 'pixel' meaning I can't use the galaxy store.

I've tried editing my device fingerprint to my correct model and then using device simulation to edit props but for some reason it doesn't do anything. Model number is still seen as pixel and I still can't use the galaxy store.

Does anyone have tips on where I am going wrong or what I need to do?

*edit*

This is moot now as I didn't realise the latest release of USNF has added support for oneUI (Samsung). So no need for a shim mod anymore. I'm still curious as why changing the props didn't work though?!
[Magisk] Some_Random_Username:
OnePlus 9RT Chinese model MT2110 fingerprint: OnePlus/MT2110_CH/OP5154L1:11/RKQ1.210614.002/1635776772321:user/release-keys__2021-09-05

Extracted it from default.build.prop in /odm/etc/20820 (20820 is 9RT project ID)
[Magisk] Dante63:
URGENT HELP NEEDED, PLEASE:

I need help and I have a feeling this issue is related to this thread, all of a sudden this is happening:

View attachment 5453301

WhatsApp has gone crazy & I can't open it at all...

I have Samsung galaxy note 20 ultra & using the latest hideprops with kdragon 1.2.0

View attachment 5453305View attachment 5453307

Please help me through this problem because I need my WhatsApp urgently, I have work to do and I'm at working unable to see messages or receive calls...

UPDATE:

I have changed things back to default and disabled both modules and still no luck, I am no attempting to backup my WhatsApp folder and reinstall WhatsApp, hopefully it would fix things for me
[Magisk] Didgeridoohan:
I don't think that this module would cause that... If you'd been doing more extensive prop changes maybe, but since you're just using the two basic SafetyNet passing options I wouldn't expect issues (unless you've set them to something really strange).
[Magisk] Didgeridoohan:
Since you've already got things up and running I'll just address the issue you had changing the prop manually.

IIRC, the USNF version you were using changed the model props in the late_start service boot stage, in the service.sh file of the module. By default, this module set props much earlier than that so any changes the module did would have been overwritten once the USNF service.sh file was executed. This could have been circumvented by making sure the prop you wanted to change would be set during the late_start service stage and possibly even with a delay, but you would then have had to set the props manually with "Add/edit custom props".
[Magisk] Dante63:
It just happened like that, after WhatsApp update, WhatsApp stopped working, constantly crashing and this is the thrown error from the logs, I have done a backup for the media files and moved everything out of Android folder to reinstall WhatsApp application and restore it from the backup, upon reinstalling WhatsApp, the app functioned without crashing (while modules are disabled and props are back to default, basically my SafetyNet is broken, so I will fix my SafetyNet, then restore WhatsApp backup) and see what happens...

UPDATE: it's working now but I have no clue why this happened, I don't touch build.prop or modify it at all, it's just pass SafetyNet and even that was done months ago...
[Magisk] Didgeridoohan:
Module updated to v6.1.2 and fingerprints list updated to v137

A small update to the module and since @Some_Random_Username has visited there's a huge update to the fingerprints list. There are also a few prints provided by @Simon1511, @Filo1995 and @TPelangi. As always, a huge thanks to you guys that continue helping keeping this module somewhat relevant.

Changelog

v6.1.2

Added rudimentary tampering check.

Added fingerprints for OnePlus 9RT, Samsung Galaxy A52 4G and Xiaomi Mi 6X and Redmi K30 Pro. Updated fingerprints for OnePlus 6 to Nord CE, many variants. List updated to v137.
[Magisk] ajsmsg78:
When installing the module on a Pixel 6 Pro to hide the navbar (custom prop, qemu.hw.mainkeys 1) it works fine to hide the navbar but then the Google Camera app takes about 4-5 seconds to switch between modes and has random freezes. Uninstalling the module fixes the issue. I'm not sure how the two ended up connected but the glitch is there somehow. I did a factory reset and set everything back up just to double check and it's the same issue.
[Magisk] Didgeridoohan:
Is it the module or the prop change causing this? Logs?
[Magisk] Displax:
Pixel`s update

Pixel 3a=google/sargo/sargo:12/SP1A.211105.002/7743617:user/release-keys__2021-11-05
Pixel 3a XL=google/bonito/bonito:12/SP1A.211105.002/7743617:user/release-keys__2021-11-05
Pixel 4=google/flame/flame:12/SP1A.211105.002/7743617:user/release-keys__2021-11-05
Pixel 4 XL=google/coral/coral:12/SP1A.211105.002/7743617:user/release-keys__2021-11-05
Pixel 4a=google/sunfish/sunfish:12/SP1A.211105.002/7743617:user/release-keys__2021-11-05
Pixel 4a (5G)=google/bramble/bramble:12/SP1A.211105.003/7757856:user/release-keys__2021-11-05
Pixel 5=google/redfin/redfin:12/SP1A.211105.003/7757856:user/release-keys__2021-11-05
Pixel 5a=google/barbet/barbet:12/SP1A.211105.003/7757856:user/release-keys__2021-11-05
Pixel 6=google/oriole/oriole:12/SD1A.210817.036/7805805:user/release-keys__2021-11-05
Pixel 6 Pro=google/raven/raven:12/SD1A.210817.036/7805805:user/release-keys__2021-11-05

Xiaomi Mi A3 EU

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

Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.15.0.RFQMIXM:user/release-keys__2021-10-05
[Magisk] eg1122:
This is a known issue on pixels when hiding the navbar. There is a workaround in the pixel 6 pro section. Its the thread dealing with mods for unrooted folks. There are also mods in the themes section that accomplish this without the delay.

Edit*

https://xdaforums.com/t/remove-navb...-non-rooted-pixel-6-pro.4357937/post-85933081
[Magisk] ajsmsg78:
I saw that and that's what I have been using for the last few days. Thanks for the info.
[Magisk] optimus207:
i need help with fingerprints of lg v50 v500, any one have an ideal? :(
[Magisk] ipdev:
@optimus207

The best option is to pull it straight from the device running stock. ;)

Sometimes the only option.

Most options are described in the documentation.

MHPC Documentation - Finding a certified fingerprint - GitHub - Link

Cheers. :cowboy:
[Magisk] mrspeccy:
Can you please update the following fingerprint:

Oneplus 8T Europe (KB 2003): OnePlus/OnePlus8T_EEA/OnePlus8T:11/RP1A.201005.001/2110091916:user/release-keys

Android 11, security patch October 2021
[Magisk] DarkImperator:
Realme X2 Pro (RMX1931)​

Could you add the newest version of Realme X2 Pro to your fingerprint list?

Build Prop:

ro.product.manufacturer: realme

ro.product.model: RMX1931

ro.build.fingerprint: realme/RMX1931EEA/RMX1931L1:11/RKQ1.200928.002/1634728216537:user/release-keys

ro.build.version.security_patch: 2021-11-05

Android 11, November 2021 security patch
[Magisk] Didgeridoohan:
Once school starts going into a slower Christmas mode I'll start looking into an update to both the module and the fingerprints list. Right now I've just got to much else on my plate...
[Magisk] Verifyatna:
Can you add asus zenfone zoom s fingeprint please. I can't pass safety net in my phone. Because when i want edit device fingerprint, my phone not listed in there

Here is

ro.product.manufacturer=asus

ro.product.model=ASUS_Z01HD

ro.build.fingerprint=asus/WW_Z01H/ASUS_Z01H_1:8.0.0/OPR1.170623.026/WW_80.30.76.74_20190319:user/release-keys

ro.build.version.security_patch=2019-03-05

Android 8.0.0

Please... I want using mbanking in my phone root
[Magisk] ipdev:
@Verifyatna

There are a few ways you can use/test the fingerprint.

From MHPC Documentation - Please update fingerprint X - GitHub - Link

You can enter the fingerprint manually in the Edit device fingerprint menu in the module, you can use the configuration file, or you can make a custom fingerprints list.​

You can generally use any one of the certified prints in the list.

It is normally recommended to be as close as possible to your device but, not always necessary.

MHPC Documentation - Can I use any fingerprint? - GitHub - Link

Cheers. :cowboy:
[Magisk] Verifyatna:
thanks. but my english is bad. any tutorial on video?
[Magisk] NOS_bzone:
Hi, please add device Xiaomi 11T Pro (Vili)

Indonesia ROM (Latest)

Fingerprint: Xiaomi/vili_id/vili:11/RKQ1.210503.001/V12.5.2.0.RKDIDXM:user/release-keys

Security Patch:

2021-10-01

Thank you.
[Magisk] Verifyatna:
thanks you, i tried it. but still can't pass safety net. what's wrong with my phone? it's because SAR : NO in my phone?
[Magisk] Filo1995:
Xiaomi Redmi K30Pro (Android 11) Update

ro.build.fingerprint

Redmi/lmi/lmi:11/RKQ1.200826.002/V12.5.7.0.RJKCNXM:user/release-keys

ro.product.manufacturer

Xiaomi

ro.product.model

Redmi K30 Pro

ro.build.version.security_patch

2021-10-01

--------------------------------------------------------------------------------

The Android 10 version K30 Pro's fingerprint is here:

25 - Redmi > 2 - Redmi K30 Pro China (10)

But, the Android 11 version one is here:

30 - Xiaomi > 77 - Xiaomi Redmi K30 Pro China (11)

They are the same device, the ro.product.manufacturer and ro.product.model should be the same, maybe put them together is better. There are too much Xiaomi and Redmi devices, put all the Redmi devices under the Redmi menu may be better.
[Magisk] Displax:
Pixel`s update

Pixel 3a=google/sargo/sargo:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05
Pixel 3a XL=google/bonito/bonito:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05
Pixel 4=google/flame/flame:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05
Pixel 4 XL=google/coral/coral:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05
Pixel 4a=google/sunfish/sunfish:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05
Pixel 4a (5G)=google/bramble/bramble:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05
Pixel 5=google/redfin/redfin:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05
Pixel 5a=google/barbet/barbet:12/SQ1A.211205.008/7888514:user/release-keys__2021-12-05

Xiaomi Mi A3 EU

Xiaomi/laurel_sprout_eea/laurel_sprout:11/RKQ1.200903.002/V12.0.14.0.RFQEUXM:user/release-keys__2021-11-01

Xiaomi Mi A3 GL

Xiaomi/laurel_sprout/laurel_sprout:11/RKQ1.200903.002/V12.0.16.0.RFQMIXM:user/release-keys__2021-11-01
[Magisk] JacobBoi_:
Hello,

I think i have a pretty simple issue:

Info:

Realme 7 Pro,

Android 10,

Rooted thru Magisk,

No custom Rom,

This is my Only Installed module,

Using Terminal Emulator from F-Droid,

I did repeat the instructions from documentation 3 times,

No, not writing "su" does not change anything.

The problem:

When running "props" in terminal I get an Access denied response. (check screenshot) .
[Magisk] vandyman:
It almost sound like your terminal emulator does not have super user rights from Magisk. Wild guess..

Try using the app called " termux" as your emulator.
[Magisk] JacobBoi_:
Hello,

Sadly, nothing changed and i doubble checked in magisk app does it have the Super User Rights in the magisk app.

My magisk, root and stuff is also working properly. (i can run apps that require a root)
[Magisk] vandyman:
1 - Uninstall the module.

2 - re download the module and install.

3 - go through the setup again.

4 - do not multi post the same questions in other threads, that is a big no no..
[Magisk] Didgeridoohan:
@JacobBoi_ You need to post logs for me to be able to tell anything. Look here: https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] Fif_:
This looks like /system/bin/sh is missing or unaccessible. It could be SELinux.
[Magisk] F308:
With /system/bin/sh missing none command could be executed, at least I think it would be this way.

Magisk, in second tab from left at the bottom, (of four in total), shows who has root privileges.

As well who has not because was rejected earlier.

That may be changed.

If an app wants run as root pop-up window will/should come up asking for permission.
[Magisk] Auuuuu:
BlackShark 3S​

Could you add blackshark3s to your fingerprint list?

Build Prop:

ro.product.manufacturer: blackshark

ro.product.model: SHARK KLE-A0

ro.build.fingerprint: blackshark/KLE-A0/klein:10/KLEN2011100CN00MQ3/V11.0.4.0.JOYUI:user/release-keys

ro.build.version.security_patch: 2020-09-01

Android 10
[Magisk] andrew2432:
Hey can I use magisk to safeguard myself from this log4shell vulnerability? Easily yes? @Didgeridoohan

@ipdev ???
[Magisk] Fif_:
In theory, yes.

In practice, it's unlikely to happen as you'd need to use Magisk to patch every single instance of the log4j library, in every app and in the system as well.

I'd venture we may see something akin to smali patcher for some old stock Roms, and we'll have to rely on the devs to update their apps.
[Magisk] andrew2432:
I guess then my question is then can't I edit my .props and block this ability completely over the entire device? I thought I read there's an easy fix within lib4j you can add a string of text that strictly disallows executable code added and its patched? Couldn't I do this with .props somehow?
[Magisk] Didgeridoohan:
@andrew2432 That's not how what props editing does...

You're way of topic for this thread. Generally what you need to do in cases like this is to make sure that all your apps are updated and that you've got all the latest security patches. This one is a server thing, so not much us end users can do (at least that's what I can tell from the little I've read about it).
[Magisk] sardelisp:
can someone help me please to see why i cannot pasa cts profile check on my Mi10 lite using custom rom?

i have tired everything

i have taken logs
[Magisk] Didgeridoohan:
What exactly does "tried everything" mean?

Two things I can think of from the top of my head:

Use the Universal SafetyNet Fix

Apply a certified fingerprint from this module

Take a look in the docs for more details:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] sardelisp:
everything means that i pick a verified fingerprint (mi 10 lite 5g global android 11) having already installed universal safetynetfix 2..1.2 for stable magisk 23.0

what else i can do? by the way rom is LOS
[Magisk] Didgeridoohan:
The logs you posted show nothing about having either a fingerprint applied or Universal SafetyNet Fix installed...

Fix that and try again (as in: apply a print, install USNF and post new logs if things still don't work).
[Magisk] sardelisp:
uh i forgot, you are right i upload wrong files, but tell you that i have done those things. i ll take new logs
[Magisk] sardelisp:
the correct logs
[Magisk] Didgeridoohan:
Everything looks fine there and you seem to have the right setup for passing CTS.

It might be the ROM you're using that is causing the issue, in which case it could be a lot harder to fix (check with other users/the developers if passing CTS is even possible on that ROM).

Or, it might be one of your other modules that's the culprit. I didn't see anything suspicious, but try disabling all other modules than Riru, USNF and this module to see if things start working.

Other than that there's not much I can help with. MagiskHide Props Config did it's thing as expected...
[Magisk] sardelisp:
wipe data and cache from google play services and play store is crucial??
[Magisk] Didgeridoohan:
Generally no (only to get the Play Store certified), but it has been known to fix things so go ahead.

You've got more tips like that here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] sardelisp:
i think its because lineage roms dont allow spoofing

but what i can do about it?
[Magisk] Didgeridoohan:
I believe I covered that already:
[Magisk] sardelisp:
thanks for your time sir, much appreciated
[Magisk] F308:
You simply may get cached results.
[Magisk] pr3dicament:
Alright.. I have a weird issue. I completely reflashed everything, similar to MSM download tool but not quite; let's call it the Linux version of this (fastbootd) -- So, i've had this issue for some time now, and i noticed KB2005 working when I installed it on slot B. I remember switching to slot A for one reason or another, it was odd. My custom recovery can't install OOS so I can only do fastboot or MSM if it wants to be detected via VM (passthrough). Sometimes even before rooting or anything, ctsProfile fails, but right now I'm spoofing KB2007 since they're just about the same damn phone. One's Global (KB2005) and the other is T-Mobile (KB2007). Can someone test KB2005 for me? I have been spending too much time trying to make sure crap works. USNF caused hell on OOS and eventually i got bootloops and then suddenly no access and i couldn't do anything. I've cleared data on all google play services, store, apps, everything. Believe me, this thing got wiped out completely. Anyway, this was just recently. It's either a mismatch with this firmware specifically (11.0.11.11 KB05AA -- it happened when i updated.) I never ran into this issue when updating before.. and I did both a full download with Oxygen updater and an OTA.. so I got the whole thing.. hence fastboot saving this after using the payload dumper:

You can do this on Windows as well. Click here :)

Click here for the Linux Version!

Now, back to what I was saying.. Once using LSPosed this first time around and magiskhide (and repackaging magisk to be hidden) and props, and my KB2005 passed before just fine. Now I don't know what's going on here. If someone could just tell me if the fingerprint works for them? They all pass except my actual device and it wasn't doing that before... heh. It'd be awesome to be able to use my exact device and get rid of this OCD lol. Hope to hear from you guys. Thanks a million.
[Magisk] Some_Random_Username:
Hi folks, below are newer fingerprints for OnePlus devices, hopefully I got everything right.

Updated fingerprints:

Spoiler content hidden.

New fingerprints for devices already in list:

Spoiler content hidden.

New fingerprints for devices not already in list:

Spoiler content hidden.

Below are a few words which I wanted to share about some fingerprints:

9/9 Pro A12 fingerprints come from the "stable" OxygenOS 12 update, which has been pulled. Well, it looks like in addition to rolling out a flawed build, OnePlus in its infinite wisdom decided EU users should get a newer build than users in other regions (C.38 vs C.36), and not only decided to not mention it on its own forum post, but also decided it should feature December 5th SPL, thus leaving other users behind on November 5th SPL.

Nord N10 and N100 are also sold via Mexican carrier Telcel, but they still run Android 10 in spite of their unlocked variants counterparts having received Android 11 update back in July 2021. Furthermore, in spite of both featuring local update ability they are not listed on Mexican support website; which by the way displays "Sorry, this page is not available in this region at this time." on every phone page (8 Visible is listed on US support page, although displayed build is severely outdated). No one knew about them until few days ago, since they feature the same build tag as global unlocked units (BE86AA and BE81AA).
[Magisk] LEENO:
G975F

selected forced G975f europe

than phone bootloop

How to revert changes?
[Magisk] LEENO:
for fast fix, module deleted by twrp - > deleted module folder, still bootloop, restored system, still bootloop, fixed writing firmware with home_csc, anyway data loosed... Next time i try your solution thanks
[Magisk] Kurt Krummbein:
The quickest solution is not always the best solution ... should have better read what Didgeridoohan said ;-)

Gtz

Kurt
[Magisk] Didgeridoohan:
@Anonymous11289 It looks like the system.prop file has been created as it should, but it seems like the print still gets set to the Pixel 2... Hard to say why without the rest of the files from the log zip (better to upload the whole zip), but it could be that the system.prop file isn't executed as it should our you have another mod that's setting a walleye print after this module has done it's thing.
[Magisk] Flamefire:
Got a question for the XZ1 Compact fingerprint: This module lists: "Sony/G8441/G8441:8.0.0/47.1.A.12.179/1909673090:user/release-keys;Sony/G8441/G8441:9/47.2.A.11.228/3311891731:user/release-keys__2019-09-01"

While this looks correct I can't find those in any of the (Euro) stock ROMs: which all have "Sony/lilac/lilac:9/YOSHINO-2.2.0-190903-1904/1:user/dev-keys" in their build.prop, e.g. G8441_Customized CE1_47.2.A.11.228-R1C and G8441_Customized DE_47.2.A.11.228-R3C

So a) where did the MagiskHide FP came from? and b) WTF? The stock ROM lists "dev-keys"? O.o

Note: I tested the stock-build.prop FPs and they don't pass CTS. That is surprising IMO. (Yes changed ro.build.version.security_patch, ro.build.description, ro.build.fingerprint and even kept ro.build.tags=dev-keys but also tried with release-keys)

Not really an issue but I'm curious...
[Magisk] Didgeridoohan:
Got the A9 here:

https://xdaforums.com/t/module-magi...p-edits-and-more-v6-1-2.3789228/post-82455475

You'd have too ask @russel5 where they got it...
[Magisk] Anonymous11289:
Attached, appreciate your assistance.
[Magisk] Didgeridoohan:
It's AR Core.
[Magisk] pepote666:
Mi 10 lite 5G

Xiaomi/monet_global/monet:11/RKQ1.200826.002/V12.5.6.0.RJITWXM:user/release-keys

security_patch 2021-12-01

thanks
[Magisk] GohanBurner:
Is there any way to change the device name back to original even when hiding? Like I'm using the "force basic attestation" which utilizes a Nexus 5 but I would like my actual phone to show up as a descriptor when using chromecase or something. Is that possible? If I connect to my chromecast it shows Nexus 5, is it possible to make it show Pixel 4a 5G (or anything I want basically?).
[Magisk] ghsch:
Hey. I've recently installed an Android 12 ROM on my Redmi Note 6 Pro - tulip. When installed this module, system boots normally, and I can use the phone for about a minute, then it freezes and reboots. Tried uninstalling the module, but the problem persists. What can I do?

Edit: I did uninstall Magisk, but it didn't fix the issue. Then, I wiped Dalvik and Cache. It fixed the freezing/restart loop. Any ideas why?
[Magisk] handy77:
My s9 plus cts has failed was working before. Not sure why it has stopped working
[Magisk] handy77:
My s9 plus cts has failed.
[Magisk] Philnicolls89:
Something has either changed on your side or server side with Google. I don't think there have been any major changes server side recently so I suspect it's got to do with your phone set up.

A detailed explanation of your set-up might help to diagnose the problem, particularly any changes eg magisk versions or mods or firmware changes etc.
[Magisk] Applebox:
Xiaomi Redmi 9T Taiwan

Could you add Xiaomi Redmi 9T to your fingerprint list?

Build Prop:

ro.product.manufacturer=Xiaomi

ro.build.fingerprint: Redmi/lime/lime:11/RKQ1.201004.002/V12.5.2.0.RJQTWXM:user/release-keys

ro.build.version.security_patch: 2021-10-01

Android 11
[Magisk] anuraag.neo:
Build Prop:

ro.product.model = Redmi Note 9 Pro Max

ro.product.manufacturer = Xiaomi

ro.build.fingerprint = Redmi/excalibur_in/excalibur:11/RKQ1.200826.002/V12.5.3.0.RJXINXM:user/release-keys

ro.build.version.security_patch = 2021-10-01

Android 11
[Magisk] void0error:
@Didgeridoohan Particular Banking app (IndOASIS) is not working:

More info, Check this post: https://xdaforums.com/t/indoasis-in...agisk-hide-not-working.4385261/#post-86221107