yashsingh1/xdaforums huggingface dataset:
[Magisk] h8isgr8:
Just wanted to update and say I got everything working. Re-installing Magisk fixed the crashing problem. CtsProfile remained false at my first attempt of using a fingerprint. I picked another one with my exact Android version and it passed. :good:

Thanks again for the help.
[Magisk] Tahsin Can:
Xiaomi Redmi Note 6 Pro ctsProfile: false. Help me please?

İ using pixel experience 9.0 rom
[Magisk] garylawwd:
Read the op properly!

This is not flash and forget and your CTS magically passes, there is a setup process through a terminal emulator (I use termux, you can get it on playstore or fdroid)

And type these commands

su
props

Then choose a new certified device fingerprint just follow the on screen instructions.

And on a side note do a bit of research before flashing anything its not wise to just blindly flash anything without reading the appropriate information because you could easily end up bricking your device
[Magisk] JarlPenguin:
If this didn't work try:

motorola/montana_retru_n/montana_n:8.1.0/OPPS28.65-37-7-2/d0526:user/release-keys

Security patch is 2019-02-01.

motorola/montana/montana:8.1.0/OPPS28.65-37-2-2/22d20:user/release-keys

montana-user 8.1.0 OPPS28.65-37-2-2 22d20 release-keys

Security patch is 2018-10-01.

Should I use montana_n or montana_retru_n for the device description?
[Magisk] Tahsin Can:
Ohh! Thank you very much. İ am sorry. İ read now. Fixed. Thanks.
[Magisk] Didgeridoohan:
Not needed... The module creates the proper ro.build.description value based on the fingerprint used. But for any future reference, it should be montana_retru_n.

Thanks for the prints, I'll take a look at them shortly.
[Magisk] steve51184:
What advantages does this have over SafetyPatch? With that you just install and reboot and it works fine no need to mess with selecting prop files etc

Didn't mean this to come over rude at all just wondering what this doesn't that SafetyPatch doesn't?
[Magisk] rinado:
sorry. didn't see that it was already in the list. Thank you all for your support :)
[Magisk] JarlPenguin:
1. Device simulation is possible

2. Wide variety of fingerprints

3. Doesn't give internal error upon boot
[Magisk] MonteXMat:
Still missing Mix 3 :c
[Magisk] Didgeridoohan:
Safetypatcher and this module both change the device fingerprint to a certified one. Difference is that with this module you can (more easily) pick what device fingerprint you want to use whereas with Safetypatcher you get a Huawei 20 Pro no matter what (unless you manually go in and edit the scripts). With this module you also get a few more options of what boot stage to use for setting the fingerprint, the prop file you mention can be very useful when flashing new ROMs, you can also set custom props, etc.

It all comes down to personal preference which module you want to use...

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

I have a small problem, I have set up some custom props, all ok, except one:

persist.radio.multisim.config=ss

ro.fast.dormancy=0

ro.mtk_perfservice_support=0

ro.ril.fast.dormancy.rule=0

wifi.supplicant_scan_interval=3000

This wifi.supplicant_scan_interval=3000 does not seem to stick, even if props did not complain when I set it up.

See screenshots, these are after adding/setting up wifi.supplicant_scan_interval and after rebooting. All the custom props are shown. Then I select wifi.supplicant_scan_interval to check.

Props says it is not yet set (but it did set up with no error messages before reboot), and returns the value as 180, but I have it in build.prop as 3000. Where is props getting the value ? Even the props log shows 3000. There is only one line in build.prop.

Not a major issue, but I am just wondering. Thanks for any ideas ...
[Magisk] Didgeridoohan:
[MENTION=8671532]hyborian[/MENTION] My first guess would be that the prop in question gets set late during boot. Try changing the boot stage for it to late_start service.
[Magisk] hyborian:
Thanks, I'll try that. I cannot edit it as screenshot no.2 will show. I tried to delete it using props delete, it said deleted, even props log says deleted after reboot. When I go back to props, it's still there, very persistent. Looks like I have to reinstall props to try what you suggested.
[Magisk] Didgeridoohan:
Hm... That's a bug. I'm planning on a new release today or tomorrow, so I'll take a look at that.

Look at your first screenshot though, there's a reset option for all custom props there, no need for complete uninstall.
[Magisk] hyborian:
Thanks, I used the reset option. And for that particular custom prop, I selected late stage, and it works now ! Props recognizes it as changed.

I still don't know where props gets the value of 180 from, though, as I have it as 3000 in /system/build.prop itself. I added it, it wasn't there in the 1st place when I searched for it.

Maybe there is another build.prop somewhere ?
[Magisk] jcmm11:
Depending on your phone look in /product/ and /vendor/
[Magisk] Didgeridoohan:
Since it's being set that late in the boot process, I believe you won't find it in any build.prop file but rather some other prop settings file. Which one, no idea... Build.prop, no matter from what partition, is loaded really early in the boot process. That's why your build.prop edit also got overridden.
[Magisk] hyborian:
Great, thanks for your help !
[Magisk] Estebanium:
How can it be that even after using MagiskHide and MagiskHide Props an App detects my device is rooted? I also used Magisk option to rename the manager to something random
[Magisk] garylawwd:
Clear data and cache for the app and try again. What app exactly are you trying to hide?
[Magisk] Didgeridoohan:
The app might be using the silly UDS and stat detection method that's floating around (will be taken care of in a future Magisk release). It might be detecting other apps on your device that it has blacklisted, there might be things about the ROM you're using that triggers it, etc, etc...

This module will only help you pass SafetyNet, so if the app uses other detection methods it's not strange the module has no effect.
[Magisk] Estebanium:
Thank you for the quick response. After scrolling through the logs with MatLog it turned out that the App noticed /sbin/busybox and so assumed that my device is rooted. I use busybox via Magisk Manager and I assumed that it is installed systemlessly. I wrote a post at their thread.

I use the German App Finanzguru. I activated MagiskHide and improved hiding in MagiskHide Props, but I guess that the existence of busybox can not be hidden by Magisk?
[Magisk] jenslody:
Which busybox do you use ?

The module from osm0sis should be in '/system/xbin/busybox' and gets hidden normally.

Does your rom ship busybox probably ?
[Magisk] jcmm11:
Busybox is hidden just fine. I have osm0sis' busybox installed on here and it's not detected (see attached screenshot). However there's also no /sbin/busybox on my system and if you have that on yours it's a question of where it came from - it's not from osm0sis' busybox which, systemlessly, places its binary in either bin or xbin.

Might want to move further discussion to the Magisk general thread instead of cluttering up this one.
[Magisk] Estebanium:
I already posted in the Magisk thread. I use Busybox from Magisk Manager. Don't know if there are different versions. I thought this would be a flash and forget thing..

Sure, don't want to be too off topic but what App is that in the Screenshots?
[Magisk] jcmm11:
Rootbeer Fresh. It's an updated version of Rootbeer, and I do have it hidden in Magisk Hide.

https://play.google.com/store/apps/details?id=com.kimchangyoun.rootbeerFresh.sample
[Magisk] Cassious:
Hey everyone, just a quick question..I was getting the ctsprofile false, and I installed the hide prop config. I have a Moto G6 (Ali) but the only fingerprint available is the G6 plus (Evert?). Can I use that fingerprint, or should I just try to do a custom one? Sorry if it's a simple question, I'm on Pie and been out the game for a while. Thanks.
[Magisk] wilsonhlacerda:
Nice tool. Do you know why you (and me!) get the Magisk UDS and Stat flagged?

By the way, I'm getting also Root Cloak Apps flagged. Weird is that when I enable Xposed systemless module I don't get it (and I'm not hiding any app to Rootbeer using Xposed). EDIT: rebooted with Xposed on and tried Rootbeer some more times and it is always getting red flagged now.

I'll try to understand that with Rootbeer itself, but if you can help I thank you. Can be via PM not to spam this thread here (although I do think the subject is closer to the one of MagiskHide Props Config and may help others reading).
[Magisk] martyfender:
Do you know why you (and me!) get the Magisk UDS and Stat flagged?

I get that result also, because Magisk is not able to hide that root detection method yet, but as I understand it, that may change in future versions. I think [MENTION=4667597]Didgeridoohan[/MENTION] made mention of that a few posts back, if I am not mistaken.
[Magisk] Didgeridoohan:
Actually, no... What you're talking about has to do with general root hiding and that's more of a subject for the general support thread or one of the many "my banking app is detecting root"-threads. I don't mind it being discussed here though, as long as the subject doesn't take over.

For more on what RootBeer is doing, everything is detailed on GitHub. There you'll be able to see exactly what the app is looking for: https://github.com/kimchangyoun/rootbeerFresh If I remember correctly, RootBeer also prints very detailed information about what it finds to logcat, so you could also use that to find out what's going on.
[Magisk] pkn267:
Hello everyone , I flashed magisk v 19.1 and it is not passing safetyNet . I tried flashing v 18.1 after that which never got installed as it always showed magisk is not installed. What can be the issue?
[Magisk] Didgeridoohan:
Wrong thread (this isn't a general MagiskHide support thread), but try toggling MagiskHide off and on again in the Manager settings.
[Magisk] pkn267:
I did it and it showed that my device needs some additional files for it to work. Now there is no option to unhide magisk .
[Magisk] pkn267:
Now it is showing magisk not installed.
[Magisk] Didgeridoohan:
Now you've really moved out of the scope of this thread...

When you downgraded, did you also downgrade the Manager? If not, that's probably your issue. Do a fresh install if Magisk and Manager and continue any further posting about this in the general support thread.
[Magisk] D@rekills4:
Hello,

Thank you for this amazing module for the extra steps to prevent root detection.

I enabled improved hide and rebooted the device.

However, my banking app still detects that the device is rooted.

Is there any way to diagnose this further?
[Magisk] Didgeridoohan:
The "improved hiding" feature is a longshot at best. Take a look here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] pkn267:
I know it's not related to this thread but in the general thread no one is replying . What additional settings does it need???
[Magisk] Estebanium:
If you are sure that you setup Magisk Hide correctly, you could try out the App RootBeer Sample that provides a good overview of the detection possibilities for finding out that your device is rooted. If you use MagiskHide on that App and RootBeer still detects your root, you will be informed why.
[Magisk] Didgeridoohan:
I'm going to quote my last reply to you (where I actually gave you a possible solution):

And please do keep things in the correct threads, even if it means waiting for an answer...
[Magisk] pkn267:
Did as u told me , I installed it manually and now it passes safety Net thanks .
[Magisk] D@rekills4:
I am not rooted according to that app.

But my banking app detects that I am rooted.

Any way to know what kind of detection my banking app is using?
[Magisk] Estebanium:
If RootBeer tells you that you are not rooted, this should tell you that you either have no root or that you activated MagiskHide for that app. So if you also do that for the banking app, it should hide your root from that app. If that is not the case and so the app is detecting root, delete cache and memory of that app and try it again. If it still fails, download MatLog or any other logging utility, because it is very likely that the app logs it detection or tells you what the app is doing. So open any app to see you current logging output and start your banking app and proceed to the message of root detection. Switch to the log and search for any message related to root detection.

Please have a look at Magisk thread for more support, because this is pretty off topic here. Unfortunately their thread is flooded with update issues to 19.2.

Good luck.
[Magisk] aiseno:
Do you hide magisk package to different apk? Last option in general setting? After hiding this magisk will call manager in app drawer.View attachment 4752713
[Magisk] atifaslam7:
Hi, sorry if I'm disturbing you, is there currently support for the Pixel 2 android Q beta 2 ? or am I allowed to use the previous versions in the terminal? when using the props config?

Edit: nevermind used the props for 9.0 which works and was succesfully able to pass ctsprofile as well. But banking app still not working, so it's definitely a new detection they have :(
[Magisk] Didgeridoohan:
As far as I know there should be no problem using the current version on Q.
[Magisk] wilsonhlacerda:
Have you tried the app with clean ROM? No root or whatever? Q is very new.....you're on the bleeding edge, some apps are not ready to it yet. Maybe the price for early adopters.
[Magisk] Didgeridoohan:
There's a good chance it's simply because you're using Q. I've seen some reports along those lines...
[Magisk] atifaslam7:
I meant the android version of my phone in the list when you go into props via terminal, not the actual version of the MagiskHide Props. Anyways I read on your github that we can use older versions of the phone and it should work the same, which it probably did since the cts profile was successful this time.

Might be that Q is not supported by the app you're right. Guess I'll just revert back to android P in that case. I've checked it on another rooted phone( samsung s10 on official builds), if it's rooted, the banking app clearly says it "does not supported rooted phone". But here on my phone it opens normally, and just says can't connect to network.

I guess it's not a problem based on root detection, rather a problem based on android build compatibility as you mentionned.
[Magisk] TerrorToetje:
I'm sorry for not including them at the first place, here we go!

Edit: Added Debug Log
[Magisk] Didgeridoohan:
Thanks, I'll take a look soon. Meanwhile, have you tried toggling MagiskHide off and on in the Manager settings?
[Magisk] TerrorToetje:
Yhea a few times, doesn't seem to make a difference sadly.

Edit: Added a debug while it works once I disable the module

Edit 2: Device seems to be encrypted
[Magisk] kaisar11:
not working for lenovo k6 power custom rom
[Magisk] Didgeridoohan:
I'm going to assume you're talking about the fingerprint, right?

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check (start by changing the boot stage).

If it still doesn't work: https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#logs-etc
[Magisk] kaisar11:
changing fingerprint id cause issue with vendor image

it shows vendor image mismatch

how can i solve that issue
[Magisk] Didgeridoohan:
That should be completely harmless, but could you post the logs mentioned in the second link I gave you, together with the file generated by running this command in a terminal emulator:

su -c getprop > /sdcard/props.txt
[Magisk] Jemec26:
Wow.

I am just passing by to say thank you!! On my redmi 5 plus (vince) I was having this problem with dev rom and this module fixed it!!! Excellent job sir!
[Magisk] Didgeridoohan:
There's an error in your debug log that seems to be related to the MagiskHide process monitor:

E Magisk : open: /proc/1689/cmdline failed with 2: No such file or directory

I need to do some hard thinking to figure out what that could have to do with this module though... I'll be back, don't have much time to troubleshoot at the moment.

You could test a few things meanwhile. Does the issue occur if you don't set a fingerprint? Does the module itself, without anything set, cause it? Does setting custom props make a difference or not? Does it make any difference if you change the module boot stage (on the script settings)? Etc...
[Magisk] TerrorToetje:
I can install the module and enable it, all is good then but once I add a fingerprint and reboot then it seems to happen, I will try to move the boot stage!
[Magisk] Rom:
@Didgeridoohan

Hello, just for info, you module works on the LG G6 (EU-H870) with an custom ROM that is, by default, not recognized as a "good" device. After installing the module and reboot, the selinux check in-build in Magisk Manager show me a good SN result.

And the second info that confirm the first one: i was able to login to my snapchat account (last apk version), so according to last Snapchat SN/root checks, i can confirm that your module works fine.

Thank you for your work :):good:
[Magisk] grossvs:
Not working for me on mate 10 pro b145 :(
[Magisk] TerrorToetje:
I managed to find the issue, I just used the Asus Zenfone fingerprint to test cts, and once I use that one I fail both test but once I use this one:

asus/WW_P01M/P01M_3:6.0.1/MMB29P/WW_P01M-V5.6.0-20170608:user/release-keys

I Pass both checks, and the best thing is default mine should be:

asus/WW_P01M/P01M_4:6.0.1/MMB29P/WW_P01M-V5.6.0-20170608:user/release-keys

It seems that the USA version of this device is certified (3) and the Eu version is not (4)

Best Regards,
[Magisk] Didgeridoohan:
That's a good find. Thank you. What device is that fingerprint from? A quick search suggests it's the ZenPad S 8.0. Is that correct? I'll add it to the list of fingerprints in the next update (hopefully within the next few days).
[Magisk] TerrorToetje:
Yes this the Zenpad S8 Z580CA:)
[Magisk] allrockedout:
Hey finally have official play store on my phone. CTS wasn't passing but changed fingerprint and boot process and working now. Thanks a million man
[Magisk] grossvs:
Mate 10 Pro b145 now working fine ?
[Magisk] esgie:
Ok so how can I now set an empty value for a prop? It's impossible after some recent update.

Popular example from samsung devices

ro.config.timaversion=

Or stuff lke ro.config.ringtone etc
[Magisk] Didgeridoohan:
Interesting... I did not envision that someone would use the custom props feature in such a manner. I'll whip something up for you in the next update.
[Magisk] Didgeridoohan:
Update to v4.0.2-v53

Had planned to get this update out over a week ago, but life happens... I was mainly gonna update the fingerprints list, but figured I would get a few tweaks to the module out there as well. Had time to finalise things tonight and here it is. Expecting to have a few May fingerprints dropping in soon and I'll add those in a separate fingerprints list update.

Thank you to [MENTION=6867525]Estebanium[/MENTION], [MENTION=2881807]x86cpu[/MENTION], [MENTION=5526254]morganpl[/MENTION], [MENTION=8972221]AnomSanjaya[/MENTION] and [MENTION=9506129]JarlPenguin[/MENTION] for providing the fingerprints for this update.

Changelog

v4.0.2

Removed prompt to enable device simulation after changing device fingerprint. It has too much of a chance of causing issues and is not necessary for passing the CTS profile check.

The check for conflicting modules that do similar edits to MagiskHide Props Config now takes into account if the conflicting module is disabled.

Made sure that custom props can be edited for boot stage or reset, even when not set by the module yet.

I was gonna add a chemistry joke, but all the good ones Argon.

Various small fixes and optimisations.

New fingerprints for LG V20 (several variants) and Lenovo K6 Note, and updated for LG G5 and G6 (several variants), Motorola Moto G5S, Oppo Neo7 (several variants) and Samsung Galaxy S7 Edge. Fingerprints list updated to v53.
[Magisk] loni90:
Hi, yeah i guess so.

Might also be that i got both Magisk and Xposed - and Magisk cant hide Xposed?

I need Xposed to enable Call recorder - otherwise it might have worked?
[Magisk] trohn_javolta:
Hi, I pass safetynet checks, just want to use this module for adding custom lines in build.prop file.

I'm unsure if I understood variable PROPOPTION:

What custom prob list will be replaced if I use option replace? You mean if I used the config file before to set custom prob values and now I use it again, the values from first config file will be replaced?

..Just wanna make sure nothing from build.prop gets deleted if I use this module and I don't mess up safetynet status.

My goal is to get auto rotation in all directions of lockscreen, homescreen and in all apps. Can't understand why this isn't a default option in android settings...
[Magisk] Didgeridoohan:
Correct. If you've set any custom props previously, the replace option would remove those and only add the new ones from the configuration file.

The build.prop file won't ever be touched (that's how Magisk works) and going back to the stock values is just a matter of disabling or resetting the module.
[Magisk] ipdev:
A few updates and additions.

Newer Pixel, Essential and OnePlus 5T fingerprints.

Found Xiaomi Mi Max 3, Mi Mix 3 and Samsung S10 Plus fingerprints.

Cheers. :)
[Magisk] Didgeridoohan:
Fingerprints list updated to v54

Like clockwork [MENTION=7280276]ipdev[/MENTION] is here with the May updates, plus a few others. Awesome! :good:

Updated the fingeprints list to v54.

New prints:

Samsung Galaxy S10 Plus

Xiaomi Mi Max 3

Xiaomi Mi Mix 3

Updated prints:

Essential PH-1

Google Pixel 1-3, regular and XL, and Pixel C

OnePlus 5T
[Magisk] hyborian:
* deleted
[Magisk] Didgeridoohan:
Update to v4.0.3-v55

Nothing really to write about. Small bug fix (thank you [MENTION=6815443]JohnFawkes[/MENTION] for the code review) and an updated fingerprint (thank you [MENTION=8970704]Fangshing87[/MENTION]).

Changelog

v4.0.3

Tiny bugfix release. A couple of messed up variables restored to their full glory.

Updated fingerprint for the Xiaomi Redmi Note 5/5 Plus. List at v55.
[Magisk] dimon222:
Thanks for another bugfix release. Only begging for one random change, pls switch the changelog to top of package description, since it's very long and too much of scroll for release notes on phone :)
[Magisk] Didgeridoohan:
Hm... I have tested different layouts, and having the changelog on top simply doesn't look good (to me). I'll think about it.
[Magisk] dimon222:
How about simply adding one link on top that would direct to latest post with change log? :)
[Magisk] Didgeridoohan:
That's why I have the index at the beginning of the readme, for easy access to whatever part you need. But, with your post I realised I could add a link at the top of the OP of this thread as well. So, that's done... :good:
[Magisk] littlepandemonium:
Anybody has the fingerprint of a certified Android Go device?
[Magisk] HonorCode:
I had a SafteyNet check failure on an LG H918 running Lineage OS 16 unofficial. I used magisk 19 to install busybox and props. I tried to change the fingerprint using props, and now my system won't boot. I wish I would've taken a backup beforehand.
[Magisk] HonorCode:
Thanks,

From the github page:

I'm assuming reset_mhpc just needs to be an empty file to flag a reset. I used the terminal in twrp to touch /cache/reset_mhpc , but system still won't boot.

I'll try magisk tools to remove props later.
[Magisk] Didgeridoohan:
It's of course possible that the reset failed somehow. But, you don't need any tools to uninstall the module. Simply navigate to /data/adb/modules and delete the module directory.
[Magisk] hyborian:
Try this, something new in Magisk 19.

https://xdaforums.com/showpost.php?p=79527991&postcount=33424
[Magisk] HonorCode:
Well, I deleted this module folder in

/data/adb/modules/

and I also tried

touch /cache/.disable_magisk

No luck. My system still won't boot.