yashsingh1/xdaforums huggingface dataset:
[Magisk] zy54917118:
thanks for your help,

I am using Xiaomi Redmi 4 Pro (6.0.1), and the pictures provided before have detailed system information.

There is no pre-installed Gapp in the system, I installed it by myself.

After your reply, I re-flashed the system, and after another attempt, the ctsProfile verification still failed. The relevant information of the Gapp used now is as follows:

Google Play services Version:15.0.90(040408-231259764)

Google Services Framework Version:5.0.1-1602158

Google Play services for Instant Apps Version:6.0.8-release-335882674

Google Play Store Version: 22.4.25-21[0][PR]337959405

I would like to ask me what setting information should be provided here, which can be helpful to solve the problem. Thank you again for your help.
[Magisk] Didgeridoohan:
That might be the cause of your problem? There's been discussions about this kind of stuff with Xiaomi devices before... A couple of weeks back there was a troubleshooting session for a K30 where it turned out it could only pass CTS of Pico GApps where installed by flashing then directly and not with any installer.

Best advice I can give at the moment is to try following that procedure, and maybe try different GApps packages.
[Magisk] zy54917118:
Thank you so much,I have read the link you sent me carefully,I know I should flash directly the pico GApps.

What do you mean by”flashing directly the pico Gapps”?could you please tell me the details like where I should start or the steps of ‘flashing’.Because I am not a pro and there is some language barriers here,I don’t understand what “flashing” means in this situation,and what pico GApps is .
[Magisk] Didgeridoohan:
Pico GApps is the smallest available package from https://opengapps.org/. It'll give you the base Google stuff.

By flashing directly I mean to use that zip and install it from TWRP, rather then using any other kind of GApps installer (I've no idea how you did it previously, of course). If you don't have TWRP, you can find it in your device's forum here on XDA, I'm sure.
[Magisk] zy54917118:
Thanks for your help.

In the open apps,there are three choices: Platform, Android, Variant but I don’t know which one I should choose.and I have already had TWRP and know how to use it.it’s so nice of you to answer so many questions.it’s very helpful.
[Magisk] Didgeridoohan:
No worries. We're all here to learn...

Platform and Android are usually preselected from your system. But if they're not, ARM (CPU architecture) and 6.0 (Android version) should be what you need. You could try different variants, but I'd start with the lightest - Pico.

Download the file and install it from TWRP.
[Magisk] zy54917118:
Thank you very much!I successfully passed the cts verification by installing the global V9.5.5.0 system, which pre-installed Gapps,thank you very much.
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RP1A.201105.002/6869500:user/release-keys__2020-11-05
Pixel 3 XL=google/crosshatch/crosshatch:11/RP1A.201105.002/6869500:user/release-keys__2020-11-05
Pixel 3a=google/sargo/sargo:11/RP1A.201105.002/6869500:user/release-keys__2020-11-05
Pixel 3a XL=google/bonito/bonito:11/RP1A.201105.002/6869500:user/release-keys__2020-11-05
Pixel 4=google/flame/flame:11/RP1A.201105.002/6869500:user/release-keys__2020-11-05
Pixel 4 XL=google/coral/coral:11/RP1A.201105.002/6869500:user/release-keys__2020-11-05
Pixel 4a=google/sunfish/sunfish:11/RP1A.201105.002/6869500:user/release-keys__2020-11-05
Pixel 4a (5G)=google/bramble/bramble:11/RD1A.201105.003.C1/6886399:user/release-keys__2020-11-05
Pixel 5=google/redfin/redfin:11/RD1A.201105.003.C1/6886399:user/release-keys__2020-11-05
[Magisk] purgy:
following the discussion from here https://xdaforums.com/showpost.php?p=83766789&postcount=4359 and the next few pages, I've managed to get my pixel 3a to use basic attestation, using pixel 4a as the device, but I'm now failing both basic integrity and cts profile.

Anyone have any suggestions as to where i should go from here?

on the 5th august patch for a10 if that helps / matters
[Magisk] pndwal:
basicIntegrity failing (as long as MagiskHide is on in Manager settings) is often caused by rogue Magisk Modules, EdXposed, Xposed etc.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82166469 PW
[Magisk] tennyleaz:
Cts profile failed for pixel 4a November update (RP1A.201105.002).

Previous version (RP1A.201005.006) props config on pixel 4a would pass both basic and cts profile check.
[Magisk] shm0:
Hi!

Is there are working S9+ (star2ltexx) Android 10 fingerprint?

firmware.mobi only has Android 9 fingerprints.

AndroidDumps has Android 10 fingerprints but no ro.build.version.security_patch info is provided.

I tried to unpack the vendor/stock firmware with mHideGP scripts (on windows and linux) but no luck.

Thanks.
[Magisk] Didgeridoohan:
As already stated, that's usually a sign of other stuff triggering SafetyNet. But, it might also be that you just need to toggle MagiskHide off an on. Give that a try too.

Have you made sure that hardware backed key attestation isn't being used for SafetyNet checking the bootloader state?

If it's on Android Dumps, the security patch date will be in there somewhere.
[Magisk] tennyleaz:
I see that hardware backed key attestation is used.

What others models should I choose to spoof for pixel 4a, to go back to basic?
[Magisk] Didgeridoohan:
As long as you pick something else than your own device you should get basic attestation. Picking another device as close to your own as possible is usually a good idea, so another Pixel device would probably be good for you.
[Magisk] chrcol:
Using custom props to modify a build.prop property.

I check after reboot with build props editor and it still shows stock value, but the props command in terminal shows my edited value.

Which is correct?
[Magisk] zgfg:
Build props editor maybe reads directly and bypasses systemless changes as done by MHCP module
[Magisk] Didgeridoohan:
[MENTION=7786725]zgfg[/MENTION] is correct: https://github.com/Magisk-Modules-R...uildprop-doesnt-change-after-using-the-module
[Magisk] purgy:
Yeah it turns out that along with changing to HW based attestation, whatever else was changed in safety net now detects my edexposed install, using the pixel 4a option in force basic attestation passes SN with edexposed disabled. My banking app still works however, so I'll just live with broken SN.

Thanks for the reply!

Edit - using edexposed v0.4.6.4 (4563) from here https://ci.appveyor.com/project/ElderDrivers/edxposed/builds/35441002/artifacts lets me pass SN.
[Magisk] rheznendra.p:
Samsung A50S (SM-A507FN) (Android 10)

samsung/a50sxx/a50s:10/QP1A.190711.020/A507FNXXS5BTI1:user/release-keys

Security Patch : 2020-09-01
[Magisk] swour:
Samsung Galaxy A5(2017) fingerprint update:

Security patch date: 2020-09-01
[Magisk] AL2009man:
I grabbed the firmware directly from Motorola Rescue and Smart Assistance Windows App. (I still need to figure out how to add Custom Fingerprint)

Phone: moto g(7) play - Metro by T-Mobile/METROPCS (XT1952-6)

Build id: QPYS30.85-18-3

System Version: 30.201.5.channel_t.t.en.US

Android Security Patch Level: August 2020 (most likely, based on Verizon Support for Moto G7 Play)

Build Fingerprint: motorola/channel_t/channel:10/QPYS30.85-18-3/60cdb:user/release-keys
[Magisk] transistor1224:
Bypass Safetynet

Help I try to bypass safetynet in s9 exynos but still ctsprofile condition is false how to I resolve that issue?
[Magisk] Aporzio:
Is there a possibility to add the fingerprint for the pixel 5 to the module?
[Magisk] acidspider:
If I had changed my props from.my pixel 3 to pixel 4 in order to.pass safety net, when I want to update to latest november update would I need to change it back first?
[Magisk] Didgeridoohan:
Start by taking a look in the docs:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Didgeridoohan:
It was submitted a couple of days ago, so as soon as I have some spare time I'll update the list.

But generally:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] Didgeridoohan:
Possibly... I've never tested, since I haven't actually taken an OTA update since before rooting my old Nexus 6. :laugh:

But yeah, changing props have the possibility of causing issues with device detection. To be safe I would disable those prop changes, but I would love to hear if someone performs some experiments with this (DISCLAIMER: don't, unless you know that you're doing).
[Magisk] zgfg:
You can just disable MHCP module and reboot - then props go to their original values.

Later, re-enable MHCP and you will again have fake values as they were previously set through MHCP
[Magisk] Aporzio:
Ok awesome thanks!
[Magisk] BlueMan_86:
Need MI 10T PRO on list... Thx
[Magisk] Didgeridoohan:
Take a look in the docs:

https://github.com/Magisk-Modules-R...ter/README.md#please-add-support-for-device-x
[Magisk] Zehlek:
Will next update include Pixel 5 Fingerprint? When selecting a certified one Pixel 5 is not on the list yet
[Magisk] Aporzio:
It's not going to matter anyways. You'll still have to select a different but close pixel device to your pixel 5 in order to force basic attestation. I have the pixel 5 myself. The reason safety net fails is hardware backed attestation. I asked about the pixel 5 fingerprint as well and upon further research it won't make a difference anyways. I'm waiting for the 4a 5g to be added since they'll always have the same features with being so close in hardware no device specific features should break by using it. Right now I'm using the regular 4a option for force attestation in hide props and it doesn't seem like anything is broken but I'd like to get close as possible which obviously would be the 5g variant.
[Magisk] bartleby999:
Have you tried to add a custom prop? If all you're trying to do is evade hardware backed attestation that worked for me. Just change ro.product.model - I actually changed my T860 (wifi) to T865 (LTE) so it's the exact same device and it passes Safety Net fine.
[Magisk] ai5g:
Hi!

I had Magisk Manager7.? and MagiskHide Props Config 5.3.6 installed. I couldn't start props ("props: inacccessible or not found") and the noticed that Core Only mode was on - when I switched it to off, it worked.

But...then I updated the Magisk Manager to 8.0.2 and got the same error when trying to start props config: "props: inacccessible or not found". However, in Magisk Manger 8.0.2 there is no "Core Only Mode" option anymore, nor is there a "Safe Mode" option.

Any ideas, how I could start the props config again? I have su in Termux.

Thank you!
[Magisk] zgfg:
Go to Modules tab and enable MHCP and other modules.

Also, in Settings, enable (if off) Magisk hide.

IMO, it should work to get you back fully to 'normal'
[Magisk] Aporzio:
Can you please explain how to do this?
[Magisk] zgfg:
Run props, read options as offered, one of them is to create or edit a custom prop. Just try and you will follow and see how to do

If you really need detailed instructions, please read the MHCP guide from GitHub - go to OP post #1 to find there a link to the Guide
[Magisk] bartleby999:
Yeah as zgfg said - Just run the props and look for Add/Edit Custom Props, it's pretty simple.
[Magisk] Didgeridoohan:
To add to the above, using "Add/edit custom props" to change ro.product.model will have the same effect as activating "Force BASIC key attestation" with the exception that with the latter it will also change any other model props that are on your device (ro.product.system.model, ro.product.vendor.model, etc). Most of the times it's enough with ro.product.model, but from reports it also seems like there are instances when one of the other props are necessary. I have an idea to allow tweaking which props will be changed, but for now you can easily use the "Add/edit custom props" feature to only add the ones you want so I'm in no hurry...
[Magisk] ai5g:
I have installed modules

- "Busybox for Android NDK"

- "MagiskHide Props Config"

- "Systemless Hosts"

They all are enabled. I have also tried reinstalling the "MagiskHide Props Config", but I still can't start props in Termux or Terminal Emulator. What Other Modules should I install?

Thanks!
[Magisk] Didgeridoohan:
Post the logs:

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs
[Magisk] MaximN97:
There are two common reasons why you would get an error saying "not found" when running the props command in a terminal emulator.

If you're using Termux you first have to run su, then it will work. If you're not using Termux it is likely that you have enabled the Magisk Core Only Mode in the Manager settings. Disable it, reboot and try again.

Gesendet von meinem MI 3W mit Tapatalk
[Magisk] zgfg:
Please follow his original post- he did have Core onlybefore he upgraded Manager, and in the new Manager there is no more Core only mode (to disable)'
[Magisk] rheznendra.p:
pls add support for samsung a50s
[Magisk] Didgeridoohan:
No need to bump, I've seen it... It'll be included in the next update. Until then you can just activate the print manually or use a custom prints list (it's described in the module docs).
[Magisk] BlueMan_86:
Device: Mi 10T / Mi 10T Pro EEA

Codename: apollo

Version: V12.0.10.0.QJDEUXM

Branch: Stable

Package Name: miui_APOLLOEEAGlobal_V12.0.10.0.QJDEUXM_ab1218565d_10.0.zip

Release Date: 2020-10-28

Android security patch: 2020-09-01 ( 1 September)

I uploaded attachment, because am not sure is that what u need... I read your github and everything, but just in case... am posting file so u can get fingerprint and implement in your magisk module..

This is of course from stock rom, clean... :)
[Magisk] pndwal:
Just took update! All good n very clear... but no more 'f' :crying: ;) ...not sure what 'Press "f" to pay respect' means...

... And just want to say MANY thanks for your clear, concise, up-to-date and relevant guides for both this Module, and for Magisk itself (endorsed by John Wu for good reason), and for your consistent efforts to keep them this way. Helped me and many other novice modders. :good: PW
[Magisk] Didgeridoohan:
There's also a description in there on how to collect the logs manually, in case the props script can't be run... I guess I'll have to make a clearer reference to that.

Here's my guess: Core Only Mode was active when you updated the Manager to v8.0.2. Magisk v20.4 still supports Core Only Mode, but since it's not one of the available options in Manager v8.0.2 you can't disable it. Navigate to /cache and see if there's a file named .disable_magisk. If so, delete it and after a reboot everything should be working again. If my guess is correct, that is. I haven't checked if [MENTION=4470081]topjohnwu[/MENTION] added any check for this when the Manager updated from 7.5.1 to 8+...
[Magisk] Didgeridoohan:
It's a gamer thing...

Thank you.
[Magisk] ai5g:
IT seems that your guess was right. The file was there and after deleting it, props worked again. Thank you very much, it really gave me a headache!
[Magisk] BlueMan_86:
man, sorry for spam... you did not answered, did I sent you a good file that you can use to make it work in your script?
[Magisk] Didgeridoohan:
No worries, the file is good. Instead of replying I thanked your post (so you'd know I had seen it) and would have for sure replied if there was something missing. Not easy for you to now though, so don't feel bad for wanting further confirmation... :D

I'll test the print and will probably push out an update to the list in the next day or so (if time permits).
[Magisk] BlueMan_86:
One question about busybox pro, I have it, so when we insrall BusyBox for Android NDK, do we need to remove busybox pro from playstore? does NDK is enough for everything, and maybe they somehow can be bad to have both... when you answer question, also make a column onyour github about that... So people know what to do... Thanks in advance....
[Magisk] Didgeridoohan:
There's no use to having two Busybox installations, they'll just clash. Pick one or the other... If you want to use the Magisk module Busybox you should probably uninstall Pro from within the app first.

But, for this module you do not need to install Busybox, so if that's why you're asking you're likely following old/wrong instructions (I removed the dependencies on a separate Busybox installation back in June).
[Magisk] zgfg:
Busybox as a module will be hidden by use of Magisk hide. Busybox app won't be, and you may end up having problems with banking apps, etc
[Magisk] pndwal:
Ah... Epic fail (on my part). It's amazing what can be learned here... I'm out of the loop w/ respect to games... let alone gamer memes!... Respect! (... I pressed f, but nothing happened.)

I'm off... to answer a call of duty... PW
[Magisk] zy54917118:
[MENTION=4667597]Didgeridoohan[/MENTION]

Hello, thank you very much for your previous help, my phone can now be fully verified by Google,

and the Magisk has checked the hidden function, and the Magisk has reinstalled other package names.

But when the app is running, it still prompts that the phone is rooted and that the mask software is running.

May I ask what the problem might be, is there any way to solve it?
[Magisk] Norup58:
Sorry if it has already been asked but need some help as I screwed up on my S10 by choosing the wrong fingerprint - was trying to correct the ctsProfile: false

The phone is now booting to the Initial Setup screen and not Hades Rom which I have installed.

I can access TWRP or Download mode, so is there any way I can edit Build.prop through these?
[Magisk] Didgeridoohan:
You can find everything I've got on hiding root from apps here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Didgeridoohan:
The module causing device issues:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] Norup58:
Thanks for your prompt reply.

Via TWRP I have tried to disable/remove module MagiskHidePropsConf by renaming file 'module.prop' inside the module folder to either 'disable' or 'remove' but still phone boots to Initial Setup screen.

Have moved the module to different directory but still I get Initial Setup screen after boot.

I have the HadesRom build.prop file, is there any way I can just transfer this to the phone and to where? (cant find build.prop via TWRP)
[Magisk] triggerlord:
Thanks for this great module! I'm passing safetynet on my Moto G7 Power with Lineage OS.
[Magisk] Didgeridoohan:
If disabling or removing (but it doesn't sound like the actually worked, so there might be something wrong with your Magisk setup) the module doesn't help then something else is up or got altered when you used that fingerprint. And using the build.prop file won't help since the original file never was altered in the first place (more on that here).

You could try grabbing logs, but that would likely only show what happened (if they show anything at all). I don't think there's much more I can contribute with unfortunately.
[Magisk] Nightf0x_007:
Op7t pro, magisk 21.0 edxpsoed 0.5, cant pass safetynet from a while ago, before it was working normally

Is there anything happened or something, and i dont know about it ?
[Magisk] Didgeridoohan:
EdXposed always has the potential of triggering SafetyNet... And once found you'll have to clear cache for Google Play Services before SN will pass. It might also be hardware backed key attestation detecting the unlocked bootloader. Or something else...

More details here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] pndwal:
Just started playing with EdXposed, so I'm a real noob here (and I know nothing about recent changes, but do know that EdXposed's relationship with SafetyNet is an off and on affair), but v0.4.6.4 (4563) (YAHFA) stable (from Magisk repo) is passing for me! Considerations here:

https://xdaforums.com/xposed/development/official-edxposed-successor-xposed-t4070199/post83894657

Only tried v0.5.0.6 (4564) (SandHook) (guess you're talking about this version), and couldn't make it pass. Neither would v0.4.6.4 (4563) (SandHook) stable (from Magisk repo) pass for me, so I'm guessing only YAHFA builds are passing at present.

Sorry for OT, but may be useful / good news for some here... PW
[Magisk] Nightf0x_007:
Safetynet was passing but from sometime ago it wasnt passimy anymore and yes i have 0.5 yahfa will install 0.4.6.4 and see, in the past whenever it wasnt passing i just open edxposed app and close it then safetynet will pass

---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------

I just install magiskhide props module i never triggered anything or played with any settings or something, thanks, will take a look at the doc and see what will happen

---------- Post added at 01:47 PM ---------- Previous post was at 01:30 PM ----------

I just install magiskhide props module i never triggered anything or played with any settings or something, thanks, will take a look at the doc and see what will happen
[Magisk] pndwal:
Sorry, I was assuming you knew it was an EdXposed issue; if it is, generally basicIntegrity will be failing in Magisk Manager Check SafetyNet, and removing / disabling problem EdXposed build and clearing cache in Google Play Services will fix it as well as accompanied ctsProfile failure.

If it's ctsProfile alone failing, it's probably not an EdXposed issue at all, and this module will most likely fix the problem, but only if configured.

As long as basicIntegrity passes, check evalType in Magisk Manager Check SafetyNet. If it says HARDWARE, you'll need MHPC option to Force BASIC Key Attestation for example. PW
[Magisk] zgfg:
Xiaomi Mi 9T, stock China, MIUI 12, Android 10, (currently) passing SN (CTS attesting Basic) with stock ro.product.model=Mi 9T

ro.build.fingerprint=Xiaomi/davinci/davinci:10/QKQ1.190825.002/V12.0.6.0.QFJCNXM:user/release-keys

ro.build.version.security_patch=2020-10-01
[Magisk] Tuckerr200:
Fingerprint for SM-N986B not in the list

Would it be possible to add the Fingerprint for SM-N986B it's not in the list?:)
[Magisk] zgfg:
It must be submitted by somebody who owns the phone with that firmware or who can extract it from the OTA

See MHPC Guide on Githb, see also a post right before yours

Hence, if you have it, you could submit
[Magisk] gecowa6967:
Hey, thanks for this great module.

I can pass SafetyNet with this custom fingerprint

google/redfin/redfin:11/RD1A.201105.003/6886588:user/release-keys__2020-11-05

on my Pixel 5, but when I take a picture the Camera Name in the EXIF data says "Google google/redfin/redfin:11/RD1A.201105.003/6886588:user/release-keys__2020-11-05" instead of "Google Pixel 5". Do I have to change the device name somewhere else?
[Magisk] Didgeridoohan:
That does not sound like you changed the device fingerprint... Did you use that fingerprint string with the "Force BASIC key attestation" feature? Because that will change the model name to whatever you decide to use. You might want to start by reading up on what that particular feature actually does: https://github.com/Magisk-Modules-R.../master/README.md#force-basic-key-attestation

TL;DR: To force SafetyNet to use basic attestation you have to change your device model name. Pick the closest available device from the included list, but NOT your own device.
[Magisk] Didgeridoohan:
Just a small update on this...

The fingerprint in the file did not pass CTS when I tested, unfortunately. But, I decided to spend some quality time during a lecture and dig through Android Dumps for it. Found both the 10T, 10T Pro and Redmi K30S Ultra, so that's a win. :good: