yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
I'm sorry but I don't think I'm the person to help you with this. I don't do Samsung and the little I know is drawn from what I've seen in the threads here...

All I know is that if you're having issues with CTS failing because of your device using hardware backed key attestation you can use a different devices model prop value to force a basic attestation instead. And if you use a device model that is from the same OEM as your device (in your case Samsung) you'll still be able to use OEM specific features, like the Galaxy store. I've had several reports that this works (but can't test myself, since I don't have any such device).

It seems to me like you have more issues than what I've described above, and I suggest that you ask for further help in your device's forum here on XDA instead. It'll be much more likely that you can find useful help there.
[Magisk] Some_Random_Username:
OnePlus just released a few hours ago their first OxygenOS Open Beta based on Android 11 for 8-series, here are the new fingerprints (tested 8 Pro one on my 5T, I assume 8 one should pass as well).

OnePlus 8 IN2015 (11)=OnePlus/OnePlus8/OnePlus8:11/RP1A.201005.001/2009051300:user/release-keys__2020-09-01

OnePlus 8 Pro IN2025 (11)=OnePlus/OnePlus8Pro/OnePlus8Pro:11/RP1A.201005.001/2009051300:user/release-keys__2020-09-01
[Magisk] dr4go:
Ad 1) Thanks a lot for the detailed explanation. I agree that it's an edge case and for most devices totally irrelevant - Samsung's 2019 products are a complete mess in terms of rooting / modding.

Ad 2) I tried very hard to reproduce it on my device, but unfortunately I couldn't: I updated your module, resetted the settings and rebooted. As you've mentioned the modified fingerprint was still active, but not visible to the props script. Then I rebooted to safe mode, but the Android wheel saying "Optimizing apps..." was immediately there (with no module active). That's what I would expect, but of course... why would it behave like yesterday on my girlfriend's phone? [emoji849][emoji35]

What I meant with "didn't help" was, that strangely the Android wheel saying "Optimizing apps." didn't appear yesterday, although I definitely was using Safe Mode.

Ad 3) In case it helps... Magisk's 'reboot' does always the right thing... (After you update a module in Magisk for example.)
[Magisk] Sid220:
New fingerprint for Xiaomi Pocophone F1

MIUI Version 12 "pilot" kinda a pre-alpha stage,

Xiaomi/beryllium/beryllium:10/QKQ1.190828.002/V12.0.1.0.QEJMIXM:user/release-keys
[Magisk] Didgeridoohan:
[MENTION=3335621]dr4go[/MENTION] Thanks for letting me know about the Manager reboot working (I don't own any recovery device). I took a peek in the code and it should be a pretty straightforward fix.

If you'd like to help me test you could run this command in terminal and let me know if it reboots properly (same goes for anyone reading this that has a device where Magisk patches the recovery image rather than the boot image):

su -c /system/bin/svc power reboot recovery
[Magisk] dr4go:
[MENTION=4667597]Didgeridoohan[/MENTION] I thought that could / would be useful - how would you know if you don't have such a device... [emoji3]

Just tested the command: it works correctly and boots to the rooted os. [emoji1303]

Thanks a lot!
[Magisk] BlackVoltage:
DKB Tan2Go

Well some people say it works with the current canary release. But how do I install canary release? Within the app there are only "beta" and "stable" Update channels available.

While I find only the stable 20.4 version over here magisk[dot]me/blog/

whats microG?
[Magisk] zgfg:
Simply google to find about microG (open source alternative to GApps)

Also, by googling for: XDA Magisk Canary

find a thread about (now closed), in the OP post #1 there are still valid official links to GitHub lfor the latest (debug only now available) Canary Magisk Manager and Magisk
[Magisk] Didgeridoohan:
That's a bit off-topic in this thread, but you'll find everything you need on [MENTION=4470081]topjohnwu[/MENTION]'s GitHub. Never ever download from anywhere else! John's GitHub is the only official and safe place for Magisk downloads.
[Magisk] dyingearth:
Question. How do you install this module with the current canary build (298). John removed the direct module download section a while back, and I had to use canary build to get Android 11 rooted again.
[Magisk] zgfg:
You can't install a module if Magisk is not Installed.

But you can install Canary and modules before OTA ( if you don't go to Factory reset)

And what do you mean by direct install?

You can Download or Install a module from repo, and Install from storage (previously downloaded module - you can download also from browser) is still present - screenshots from Canary Manager attached
[Magisk] alex212020:
Redmi Note 9

Hello,

I am trying to update my device fingerprint on the Xiaomi Redmi Note 9 Global, however it does not appear to be in the list of available device fingerprints yet in this package. Can anyone describe where I can manually obtain and import the required fingerprint id for my device? Is it a file in the official ROM or something?

Thanks,

Alex.
[Magisk] ipdev:
Hi.

Yes it is in the official rom.

The MagiskHide Props Config documentation explains the process.

Finding a certified fingerprint GitHub - Link

How do I submit a fingerprint? GitHub - Link

New and updated prints are always welcome. :D

Keep in mind, you can normally use a different device if yours is not in the list.

Can I use any fingerprint? GitHub - Link

Cheers. :cowboy:
[Magisk] alex212020:
Cheers for the reply, I had a read through and found the following: Redmi/merlin_global/merlin:10/QP1A.190711.020/V12.0.3.0.QJOMIXM:user/release-keys

In the META-INF\com\google\android\updater-script file of the ROM I downloaded from the MI websitem however when looking at the example line to add to my custom import file I don't really understand how to format the above to match this format: Google Nexus 6 (7.1.1):Motorola:Nexus 6=google/shamu/shamu:7.1.1/N8I11B/4171878:user/release-keys

Thanks,

Alex.
[Magisk] Didgeridoohan:
If you want to make a custom prints list, all you really need is a device name (in the example "Google Nexus 6"), an equal sign and then your fingerprint. The ":Motorola:Nexus 6" part of the example is only used for the "Device simulation" feature of the module. You might also have to add the security patch date to the print, which you can either do by using the "Add/edit custom prop" feature of the module, or append it to the print with two underscores (__). You've probably already seen it, but the instructions are here: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf#custom-fingerprints-list

But, I'm probably gonna release a new update today or tomorrow, so if you give me the security patch date for that print I can add it to the module list.
[Magisk] kur41:
Sony Xperia 10 II Dual fingerprint

Sony Xperia 10 II Dual XQ-AU52 (10)

Sony/XQ-AU52_EEA/XQ-AU52:10/59.0.A.6.24/059000A006002402956232951:user/release-keys

2020-07-01
[Magisk] sak0071:
I can't hide root ?

Please Help
[Magisk] zgfg:
Does it fail on CTS Profile (due to Hardware attest finding that Bootloader is unlocked)?

Use the new option 2 (Force Basic attest) in the newer version(s) of MHCP

If not familiar with above terms, please search for in this thread, and/or read what was the hot topic here for the last month - you can also consult the MHCP docs on GitHub:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
[Magisk] Didgeridoohan:
Unless it's an issue with passing the CTS profile (as already covered by [MENTION=7786725]zgfg[/MENTION] above), that's quite outside the topic of this thread.

If it isn't CTS, take a look here: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

And if you still can't get things working after that post in the general support thread, but try to be more descriptive about your problem. The more details the better. :good:
[Magisk] dyingearth:
NVM, still not getting used to the canary manager UI. I completely didn't see the floating menu on the bottom of the screen.
[Magisk] zgfg:
NP. Anyway, long tap to the Manager icon and there will also be a shortcut to Modules
[Magisk] Didgeridoohan:
Module updated to v5.3.4, fingerprints list updated to v102

Another small update with bug fixes and a some additions. And of course some new and updated fingerprints.

Since Android 11 dropped the other day I took a quick look over at Android Dumps and looked up some brand new fingerprints for the Pixel devices. Unfortunately none of the threes had been uploaded, so I guess I'll just wait until they are or someone is kind enough to supply them.

Thank you to [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=4770208]Sid220[/MENTION], [MENTION=7141309]simonsmh[/MENTION] and [MENTION=4441458]kur41[/MENTION] for the prints this time around.

Changelog

v5.3.4

Release notes

Added a module update check option. See the documentation for details.

Added `system_ext` to the list of partitions used for certain props (thank you [MENTION=7141309]simonsmh[/MENTION]).

Fixed an edge case where changing settings after updating the module, but not having rebooted yet would cause issues with system.prop being kept from the previous version.

Fixed the -nw run option and made sure that some run options can't be picked together. See the documentation for details.

Cleaned up some unused variables.

Added print for Sony Xperia 10 II Dual XQ-AU52. Updated fingerprints for Google Pixel 2, 2 XL, 4, 4 XL and 4a, OnePlus 8 IN2015 and 8 Pro In2025 and Xiaomi Mi 10 Global, Mi 10 Pro and Pocophone F1. List updated to v102.
[Magisk] ipdev:
Looks like you got some. ;)

Pixel Android 11 from the September Google Factory Images.

Cheers. :cowboy:
[Magisk] Didgeridoohan:
Fingerprints list updated to v103

And there are the threes. Thank you [MENTION=7280276]ipdev[/MENTION].

Updated

Google Pixel 3

Google Pixel 3 XL

Google Pixel 3a

Google Pixel 3a XL
[Magisk] MaXAiRO:
Hello Didgeridoohan.

I would like to write my story concerning a bank app I had some trouble logging in because it was detecting root which I eventually managed to solve. I don't know if there's a dedicated general bank apps thread so excuse me if I'm totally off topic. I just wanted your opinion.

I'm currently using a Poco F2 Pro + Xiaomi EU 12.0.8 (MIUI 12 - Android 10) + Magisk 20.4 + EdXposed 0.5.0.6)

I couldn't log in even though I did all the following:

-SafetyNet pass (both basicintegrity and cts)

-Bank app was in MagiskHide

-Manager was repackaged

-Tried with no modules activated (Core Mode)

-Renamed TWRP and TitaniumBackup folders

-Added bank app in EdXposed black list

-Hid Titanium Backup and Edxposed Manager from the bank app using SudoHide

-Put some restrictions in the bank app using XprivacyLua (which just broke the app or still didn't log in)

-Tried some other fingerprints using MagiskHide Props Config

Then, I just remembered the xposed module RootCloak (latest beta update from July 2016) and that was the solution. It's impressive how powerful some xposed modules still are even after so many years.

I guess that latest Magisk Canary has better MagiskHide than stable 20.4 and maybe if I used canary right away I would be able to log in but it was easier at that point to test RootCloak first.

What's weird is that on my OnePlus 5 with the same setup (except for the rom of course), I managed to log in the bank app right away without using RootCloak.

In case you want to try with latest Canary MagiskHide it's this app. If you reach the log in screen you're good.
[Magisk] Didgeridoohan:
[MENTION=2725849]MaXAiRO[/MENTION] I don't have much to add really... There are ways of detecting Magisk that MagiskHide currently does not deal with, and there's not much to do about those (there are some unofficial Magisk releases floating around that has hacks put in place to circumvent some detection methods).

And of course it is very easy to detect other parts of your ROM or setup that MagiskHide can't help you with (which is why one device can sometimes hide things while another can't, they've got different ROMs/setups). More elaborate solutions like you've done with Xposed modules, isolation apps, etc is sometimes needed.

Pretty much everything I've got on this subject is collected here (you've probably seen it):

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

You've got things up and running. I'd consider that a win.
[Magisk] JasDevi:
I tried using the props but it says 4a inaccessible not found
[Magisk] Didgeridoohan:
Perhaps:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#props-not-found
[Magisk] kk9999gada:
Asus Zenfone Max Pro M1 (Pie) fingerprint:

ro.build.fingerprint = asus/WW_X00TD/ASUS_X00T_3:9/PKQ1/16.2017.2009.087-20200826:user/release-keys

Security Patch: 5 September 2020.
[Magisk] cd993:
Anyone please able to help me out by getting a working fingerprint solution for the Zenfone 7 Pro?

Many thanks!
[Magisk] Didgeridoohan:
If you haven't seen it already, there are quite a few tips on finding a certified fingerprint in the module docs:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] vMAC:
I currently am able to pass Safetynet on my Pixel 4XL with this module set to Basic.

This is great for passing Safetynet but not so good because some apps don't realize I have Face Unlock due to the Basic fingerprint.

I now see that you have Pixel 4XL fingerprints, but I don't understand if I can use these and still pass Safetynet. How is it that if I use this fingerprint it still won't use the hardware to verify and therefore break Safetynet/ctsProfile?

tl;dr - Can I use the Pixel 4XL fingerprint from this module to pass Safetynet on my Pixel 4XL?
[Magisk] smohanv:
If you use magisk canary to root your system and enable hide in settings you don't need any module to pass safety net and also Gpay works.

I used this prop module to pass root notification by banking app like Santander but no luck.
[Magisk] vMAC:
Not on my phone. With Canary and Magiskhide ctsProfile does not pass on stock ROM
[Magisk] zgfg:
Yeah, this is why that new option, Force Basic CTS attestation was added to MHPC
[Magisk] Didgeridoohan:
The Hardware vs Basic attestation doesn't have anything to do with the device fingerprint. It's changed to "basic" by altering the ro.product.model prop to match a device that isn't on Google's list of devices that should use the hardware check.

A drawback is that some device specific features may be disabled when the model is perceived as another device. You might be able to get around this by manually picking another device from the device list in the "Force BASIC attestation" menu. The Pixel 3a has at least previously not been on Google's list, as well as the Pixel 2s (IIRC). Try one of those.
[Magisk] GoldElocks:
I'm unable to pass SafetyNet, CTS profile stays false on my pixel 4a running DU 14.7. The dev for my device says that it is because his ROM is using September ARB and that Google hasn't released a fingerprint for Sep for any pixel devices for A 11 - Q

Would it be possible to just edit the fingerprint to use the Sep (2020-9-5) date in order to match the ROM in order to pass CTS profile? TIA
[Magisk] Didgeridoohan:
I've got the September August fingerprint for the Pixel 4a in my module (edit: I just realised you meant A10, not 11. In that case it's the August fingerprint since there never will be anything else for A10 anymore), you can just pick that from the list. But, the 4a uses hardware based key attestation for the bootloader state (IIRC), so you'll also have to enable the "Force BASIC attestation feature". It changes the model props to match a device that doesn't use hardware attestation, and by default it'll be the Nexus 5. If you want a newer device you can manually pick from the device list instead. I believe the Pixel 3a still doesn't use hardware attestation (unless that has changed with A11), and also the Pixel 2s.
[Magisk] GoldElocks:
That's strange, I have tried default Nexus 5, pixel 3a and pixel 4a fingerprints and they all fail CTS Profile. This was after you updated to 5.3.4 with a 2nd clean install, also checked for updates in the props config tool but says up-to-date. From everything I've read and understand about CTS profile it should be passing but we're unable to get it to pass on this ROM build for some reason.
[Magisk] Didgeridoohan:
If you are using a certified fingerprint (option 1 in the main menu)

and

forcing basic attestation (option 2), and you are still failing CTS it is likely that it is something about your setup that triggers it (EdXposed, etc) or possibly even the ROM itsefl (it's quite possible to create a ROM that simply can't pass SafetyNet).

Edit: I took a closer look at your ROM, and now I get what you were talking about initially. The ROM already has the August Android 10 certified fingerprint included, but since it has a security patch date of 2020-09-05 it'll not pass CTS. That'll be fixed by picking the 4a A10 fingerprint from the module list though. You could also just change the security patch date prop to 2020-08-05, if you'd like (but it's slightly more work, actually).
[Magisk] GoldElocks:
Picking the A10 fingerprint from the module list worked, thank you!!
[Magisk] ipdev:
I am using the Android 11 print on mine.

What happens if you reset MHPC and reboot.

r - Reset all options/settings

- SafetyNet should show Hardware type and fail.

Then run props and set just the fingerprint selecting the Pixel 4a Android 11 print and reboot.

1 - Edit device fingerprint

- SafetyNet should show Hardware type and Pass?

Has there been a change in Magisk that might explain why a device can pass showing Hardware Attest?

The devices show Certified in PlayStore so, they must actually pass or fool SafetyNet somehow?

I did not dawn on me until tonight.

I'm at a WTF moment here...

My Poco F2 uses Hardware Attest and passes SafetyNet.

Stock MIUI 12 (Android 10).

Unlocked bootloader and patched with Magisk canary.

MHPC is installed but, never used/configured.

Note:

Magisk Manager is always hidden (renamed).

MagiskHide is turned on.

The other Magisk settings should not matter?

Turn off Check for Updates, Systemless Hosts, No pop-up notification for root...

Will have time tomorrow night and/or this weekend to clean flash and test on factory roms for these devices.

They are the only two I have that force Hardware Attest.

Quick test trying to force hardware attest on my Pixel 3a xl, still used basic.

--

If anyone has an idea why these devices are passing, or can think of something to test, please let me know.

Cheers all. :cowboy:
[Magisk] Didgeridoohan:
[MENTION=7280276]ipdev[/MENTION] That's right, I forgot about that (my devices are just too ancient to be affected). It seems like Google changed something again a couple of weeks ago and even devices using hardware attestation pass CTS at the moment.

https://twitter.com/topjohnwu/status/1303845469798367233?s=20
[Magisk] zgfg:
Yes, interesting, I removed spoofing ro.product.model and SafetyNet is still passing, showing Hardware attest type (Xiaomi, Mi 9T, MIUI 12, A10)
[Magisk] jacxzs:
i started using this magisk module and i really like it, it really work perfectly, there is only one thing i need to ask, can you please add a device id for oppo A3S, i know you already included how to do it but im really a noob i tried but i cant follow the process, so could you pls add it . thank you very much i really appreciate it
[Magisk] Jindivikk2:
thanks, magiskhide props config helped hiding my hardware attestation on my Galaxy Note 10. I chose force Basic key attestation using Galaxy S4 fingerprints, and changed

ro.product.system.model=SM-N9005

ro.product.system.name=SM-N9005

cleared data , cache on play and google play services
[Magisk] Didgeridoohan:
Would love to help, but the device isn't available on Android Dumps or firmware.mobi, and I'm currently mobile and do not have enough storage space to download and check a stock ROM. You're either gonna have to give it a go yourself (I really recommend trying it, it's not that difficult once you've started) or hope that someone else has the time and means.
[Magisk] PoochyX:
Sorry for bringing this to your forum its just that your a very knowledgeable individual on android and you respond back to people helping with issues I am hoping you could help me with mines, I disabled the android system service camerastatsjobservice and did a backup without checking to see if it would boot cause I assumed it was just some logging service that could be safely disabled so I did a backup afterwards and the error is in the backup anyway to access adb via twrp and re-enable that service so the device will boot again sorry for the off topic I just don't want to bulid up my daily driver again...

([emoji88]Chaos GSI[emoji88])
[Magisk] Didgeridoohan:
[MENTION=7815789]PoochyX[/MENTION] You're right, the general Android Q&A forum would probably have been a better place. And then you could have just tagged those you wanted to ask for help instead of cross posting. For next time I guess...

You already have an answer to your other post, so maybe you have a solution already. To be honest I have absolutely no idea how to fix your issue, but if I had to make a wild guess and all you really need to do is to run an adb command to enable the service again: maybe you could run it during boot with adb wait-for-device.

Good luck.
[Magisk] ipdev:
You picked a difficult one to start with. :D

This one is going to have to come from you or another with the device.

You will need to be running the stock rom (regular or rooted).

Use adb shell or a terminal app and use the getprops command to dump the device props.

--

I looked into it last night.

After a bad connection to the OPPO download server.

40KB to 1900KB, Got above 4MB every now and then. Mostly staying around 40KB - 170KB.

The official download is an odd OTA package style.

The boot image is in an unknown format.

No recovery image or full directory. (Uses recovery-from-boot.p)

I did not find a fingerprint in any of the prop files, installer scripts or odd location they can be listed sometimes.

Long story short, there are multiply build prop files scattered though out the OTA.

There are eight build prop files under vendor alone, not including sub-directories.

When the update is run, the prop file(s) are combined, each one looks to import another one.

vendor/package/Default/system/build.prop look to import /persist/speccfg/vendor_ro.prop.

There is no persist in the OTA package, so that is a dead end.

Cheers. :cowboy:

PS.

It looks like there are two versions of the A3s

CPH1803 and CPH1853, both are on Google's certified list.

EDIT:

I was able to unpack the boot image once I noticed it was encrypted.

Was so excited last night when it finished downloading, I just unzip it.

Forgot about Oppo's ozip format.

Still did not make a difference.

The boot image does not contain a prop file in the ramdisk.
[Magisk] zgfg:
Please install termux from Playstore:

https://play.google.com/store/apps/details?id=com.termux

Run the following commands and copy back the responses:

getprop ro.product.manufacturer
getprop ro.product.model
getprop ro.build.fingerprint
getprop ro.build.version.security_patch

Assuming you didn't use MHPC (or anything similar) to change their values?
[Magisk] Some_Random_Username:
Hello, here's OnePlus 8 Visible fingerprint: OnePlus/OnePlus8Visible/OnePlus8Visible:10/QKQ1.191222.002/2007221621:user/release-keys__2020-06-01

Please note it's also an IN2015, somehow OnePlus decided to reuse the model number and FCC ID they had for the global variant. It also appears as a different model on Play Console (see attached).
[Magisk] DarkLordLP:
Please add surface duo to your list
[Magisk] Shuren666:
Samsung Galaxy Tab S4 SM-T835=samsung/gts4lltexx/gts4llte:10/QP1A.190711.020/T835XXU4CTF5:user/release-keys__2020-06-01

Android10
[Magisk] Displax:
Xiaomi Mi A2 Lite

xiaomi/daisy/daisy_sprout:10/QKQ1.191002.002/V11.0.11.0.QDLMIXM:user/release-keys__2020-09-01
[Magisk] Didgeridoohan:
Thank you. What is the security patch date for that build?
[Magisk] Shuren666:
2020-06-01