yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
According to those logs you've got several things going on.

The late_start service more crashes during boot, meaning no scripts are being executed during that boot stage. I've no idea why (some module or boot script possibly).

You've also got several modules that edit the device fingerprint installed, they'll clash (this module will deactivate the feature though, you don't have to worry about that).

And lastly, I don't think you've enabled MagiskHide. If it is enabled, try turning it off and on again. Check the docs for further reading:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Didgeridoohan:
I've finally had some time to do some testing and I'm preparing a small update to the module (and a large update to the fingerprints list).

This print did not pass CTS when I tested it... Have you tested it on your end?
[Magisk] Didgeridoohan:
Module update - v5.2.6-v92

The past couple of weeks there's been a ton of fingerprints submitted. I've finally had some spare time to properly test and add those to the list. Big thanks to [MENTION=4770208]Sid220[/MENTION], [MENTION=8234677]Some_Random_Username[/MENTION], [MENTION=4453960]swour[/MENTION], [MENTION=10811055]amipel[/MENTION], [MENTION=8483170]estofjlw[/MENTION], [MENTION=6345368]Displax[/MENTION], [MENTION=5380710]kontini[/MENTION], [MENTION=9317193]73sydney[/MENTION] and [MENTION=9098612]Filo1995[/MENTION] for keeping the list of certified fingerprints alive and well.

But, I also made a couple of small changes to the module. John's been working a lot on the Magisk internal Busybox lateley, and it's fully standalone during Magisk's boot process. So, with a little push by [MENTION=4049833]Juzman[/MENTION] I removed the prerequisite for using an externally installed Busybox. Seems to work alright. Full changelog below.

Changelog

v5.2.6

Fixed the supposedly "improved" verbose boot logging.

Change to using Magisk's internal Busybox for the `props` script (the boot scripts are already using it without issues and have for some time). Separately installed Busybox no longer needed. Thank you [MENTION=4049833]Juzman[/MENTION] for the push.

Added info about MagiskHide's status in the "Edit device fingeprint" menu.

Added fingerprint for Lenovo Tab 4 10 Plus TB-X704F and TB-X704L, Samsung Galaxy Note 4 SM-N910G and Xiaomi Redmi Note 8. Updated fingerprints for Google Pixel 2-4 XL, Motorola Moto G7 Power, OnePlus 5, 5T, 6, 6T, several variants of 7, 7 Pro, several variants of 7T and 7T Pro and several variants of 8 and 8 Pro, Poco X2, Redmi K30 Pro, Samsung Galaxy A5 2017 and Xiaomi Mi A2, Mi A2 Lite and PocoPhone F1. List updated to v92.
[Magisk] xdatin1:
Installed this update and work ok, tnx
[Magisk] mario0318:
It's a three year old mid-range phone that may not have been too popular, but here's the working fingerprint for my device:

LG K20 Plus (LGMP260)

MetroPCS/lv517_mpcs_us/lv517:7.0/NRD90U/1833409570571:user/release-keys

Somewhat interesting that for this device, the build brand name is set as the carrier, MetroPCS (now Tmobile), yet the Tmobile variant for this phone, LGTP260, has its fingerprint brand set as LGE as it should be:

LG K20 Plus (LGTP260)

lge/lv517_tmo_us/lv517:7.0/NRD90U/1809315248edb:user/release-keys

Anyway, I've used both and they seemed to work and pass Play Certification.
[Magisk] dmonium:
thanks, but it was changed to

ro.system.build.fingerprint=Redmi/begonia/begonia:10/QP1A.190711.020/20.6.11:user/release-keys

ro.build.version.security_patch=2020-06-01
[Magisk] Didgeridoohan:
Have you tested it (I will test it myself, but would still like to know)? The previously posted print didn't pass when tested, but not because a new release had been made. That's not how it works... Prints for old releases will still pass CTS, as long as they where certified in the first place.
[Magisk] keneankit01:
Can you add support for Nokia 6.1 (2018) (Plate2)
[Magisk] Didgeridoohan:
The module only helps with root detection if you fail CTS, nothing else (unless there's some random prop value that is detected which can be changed with the module).

Logs saved when you are failing CTS would be ideal.
[Magisk] crazyrexz:
thanks mate. nice to see my device get updated. will test later if going to face fail test
[Magisk] Some_Random_Username:
OnePlus being OnePlus decided to rollout a new "stable" update for OnePlus 5 and 5T without telling what has changed (and keeping same version number for no reason at all), here are updated fingerprints:

OnePlus5=OnePlus/OnePlus5/OnePlus5:10/QKQ1.191014.012/2006012143:user/release-keys__2020-04-05

OnePlus5T=OnePlus/OnePlus5T/OnePlus5T:10/QKQ1.191014.012/2006012146:user/release-keys__2020-04-05
[Magisk] MarkLev:
I successfully set my fingerprint to the supported device listed in MagiskHide Props but still was not able to make ctsProfile to true on Redmi Note 8 pro.

ROM: Android 9, xiaomi.eu_multi_HMNote8Pro_V11.0.2.0.PGGCNXM

Here is my log. Could you pls help?

http://www.mediafire.com/file/13tp99twysi56ca/propslogs.tar.gz/file

Edit: I am not able to upload the log directly due to some reason, so I upload it to mediafire.
[Magisk] Didgeridoohan:
From a quick look it does look like everything is set up as it should. And I double-checked right now and the fingerprint is passing CTS.

It is likely that you have some modification or other that Magisk cannot hide.
[Magisk] ps000000:
I am semi-noob for this.

How to use this module to disable Nav bar?

I ran the command

(there is the line qemu.hw.mainkeys=0 in the original build.prop)

props qemu.hw.mainkeys=1

and tried using both 2 boot stage but navbar still exist.

(My red magic 5g did not allow to save build.prop = error saving build.prop

by using build.prop editor apps, i think it caused by Android 10)

Thanks in advance.:fingers-crossed:
[Magisk] Didgeridoohan:
That's not how you use the props command. But I can't believe I haven't thought of that before. I'll definitely add that in the next module update! Thanks.

You run props, and then you pick the "Add/edit custom props" menu. From there you follow the on-screen instructions to set the prop to the value of your choice.
[Magisk] ps000000:
Oh just laugh. only props then other options came easy !!!

:fingers-crossed::laugh::laugh::laugh:
[Magisk] textbook:
I am having a really weird issue.

I was able to use this module before, but after updating to the latest version, termux is not recognizing props as an acceptable command.

OnePlus 7 Pro

OxygenOS 10.3.2

Magisk 20.4

I have uninstalled the module and termux, then reinstalled... There was no change. Can someone point me towards a solution?
[Magisk] Didgeridoohan:
And you're running su before props?
[Magisk] JasDevi:
Anyone June patch is having ctsprofile failing?
[Magisk] Ananaqil12:
Samsung Galaxy A50

(SM-A505F) Android 9

Security Patch : 2019-04-01

samsung/a50dd/a50:9/PPR1.180610.011/A505FDDU1ASD6:user/release-keys__2019-04-01
[Magisk] tysj:
Mine failed for the first few days since the patch. Then started suddenly passing for 2-3 days. Now it's failing again. No changes to any modules, MagiskHide, apps. Not sure what Google's doing in the background to trigger it so inconsistently.
[Magisk] DON2003:
tried this but it has no fingerprint for my device which is Lenovo K5 pro, so I use the one Lenovo with android 8, after reboot it stuck on boot logo, have to unroot via TWRP to make the phone boot, any fix or what I did wrong?
[Magisk] Didgeridoohan:
No need to unroot, there are other options:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

And if you need further help:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#logs
[Magisk] DON2003:
thanks, might start all over again, but may I ask if my device is not on the list, which will be the best to choose from the list? am using a Lenovo K5 pro with Lineage 16 and its Android Pie, thanks
[Magisk] Didgeridoohan:
I'm theory you should be able to use any fingerprint.

If your device isn't in the included list, pick whatever print is closest or see if you can find a print that matches your device.
[Magisk] thada2607:
A weird thing just happened, I updated my phone to OOS 10.0.9 (the latest for my codename) a couple of days ago and today I rooted it, ctsProfile was still 'fail', but the magisk hide option is available in settings now, which was not the case before, after enabling it, said option works fine. When I entered magisk again, it asked me to download the latest version and I let it do its things, I did a Safety Net check again and both are 'true'. There was a magisk module that helped to bypass the check in phone from the last OOS version, it didn't work in the last OOS version tho, to see if it somehow was compatible with the current OOS and helped me pass the check, I tried removing it, re-did the check and all are still true. Maybe it's just the OOS that caused this.
[Magisk] DON2003:
after I re-flash magisk, the phone stuck on boot screen again, then I followed your instruction rename a file in the module, and now it boot up, so its the module that cause the stuck in boot,

is this because i picked a wrong fingerprint? as I remember the fingerprint I picked is Android 8 and my rom is Android 9, will thi cause the problem?

my phone is Lenovo K5 pro with Lineage 16 which is Andorid 9, may I ask for suggestion which one to use? sorry am just a newbie on these tweaking thing, pls help
[Magisk] Didgeridoohan:
Usually there shouldn't be any issues with picking whatever fingerprint (as already stated). Might be something different about your device though...

But, I can't say anything without those logs.

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#logs
[Magisk] DON2003:
most probably, so wrong setting any fingerprint shouldnt be cause of stuck on boot. right?

I tried the module SafetyPatcher and it failed both basic integrity and cts but as I check playstore it doesnt shows the line that said uncertified, but nothing said device is certified either, also my banking app that was saying cant run on emulator now runs ok, very weird
[Magisk] Akilesh_15:
Updated fingerprint for Nokia 7 plus

Manufacturer: HMD Global

Model: Nokia 7 plus

Android Version: 10

Build Fingerprint: Nokia/Onyx_00WW/B2N_sprout:10/QKQ1.190828.002/00WW_4_15D:user/release-keys

Google Security Patch: 2020-05-01
[Magisk] CarbonGTR:
Nokia 6.1 Plus's latest build fingerprint. May 2020 patch -

Fingerprint:
Nokia/Dragon_00WW/DRG_sprout:10/QKQ1.190828.002/00WW_4_15C:user/release-keys
[Magisk] Didgeridoohan:
There's been a few reports of incompatibility between this module and GSIs, but so far I have no idea why (haven't been able to analyse any detailed logs on it). But that's currently there only issue with setting the fingerprint that I know of (but it's module specific).

Safetypatcher breaks SafetyNet unless you edit out a few lines in the module boot script (you can find what lines if you search through that thread).
[Magisk] DON2003:
will it be possible that my cts failed is not due to fingerprint but other cause?
[Magisk] :
Hi! May you add my device fingerprint to your module?

Samsung Galaxy J7 2016 Props:

ro.product.model=SM-J710FQ

ro.product.name=j7xeltetur

ro.product.device=j7xelte

ro.build.version.release=8.1.0

ro.build.version.security_patch=2019-07-01

ro.build.fingerprint=samsung/j7xeltetur/j7xelte:8.1.0/M1AJQ/J710FQXXU3CSG1:user/release-keys

Safetynet: Passes

Certificated: Yes
[Magisk] Didgeridoohan:
It's always possible.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] spicediablo:
Hi experts,

Thanks for providing this module. I am a user of poco f2 pro and after adding the fingerprint, I am still encountering cts profile:false in safety net. Anybody has this issue too? Appreciate the sharing.

Just tried to do again and found out that the fingerprint that was installed was for 11.0.6.0 and my original value was 11.0.2.0. Perhaps this was the problem? In this case, should I reset the fingerprint?
[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

Shouldn't be an issue:

https://github.com/Magisk-Modules-R...ob/master/README.md#can-i-use-any-fingerprint

But, that sounds to my like you are using the stock ROM, which would mean you don't really need this module and just haven't made sure that MagiskHide is enabled and working.
[Magisk] spicediablo:
Indeed I am using stock ROM and have magisk installed.I came upon this thread when I was looking for solution as my ctsprofile is false when safety net checking was done. My basic integrity is true though which means my magisk hide is working as per your guidelines. I have also tested by disabling magiskhide and launching banking app, which failed. When I added the banking app into magisk hide, it worked. So magisk hide is working

As of now, I have tried changing boot stages to default as well as post-fs-data but still no luck. When you said try a different fingerprint, I assume, you meant try a fingerprint for other models of phone from your list?

I have also collected the logs as per your guidelines.Much appreciated if you can take a look when you are free. Somehow, there is security token issue when i tried to upload to xda so I use google drive instead.

https://drive.google.com/file/d/1-5cImZ9l63WKZUKehUl3xxQ6hxOmFxxc/view?usp=sharing
[Magisk] Didgeridoohan:
Basic integrity can actually pass even with MagiskHide disabled in some circumstances.

If you want me to take a look at those logs you'll have to enable link sharing.
[Magisk] spicediablo:
Link sharing enabled. Heres the link.

https://drive.google.com/file/d/1-5cImZ9l63WKZUKehUl3xxQ6hxOmFxxc/view?usp=drivesdk

I hope I got the correct logs.. Thanks!

Sent from sagit
[Magisk] DON2003:
just curious why selecting a wrong fingerprint (in my case with my Lenovo K5 Pro on Lineage Pie which I select Lenovo forgot the model with Android 7) makes stuck on boot, I think it shouldnt happen, I want to try again, may you suggest me a fingerprint to pick for my device? thanks
[Magisk] Didgeridoohan:
Everything looks as it should. So, the fact that you fail CTS even on stock ROM and have confirmed that MagiskHide is otherwise working, it all points to something about your setup triggering the CTS check.
[Magisk] Didgeridoohan:
To have a chance of answering that I would need to see those logs I've been talking about since the beginning...
[Magisk] spicediablo:
Magisk hide confirmed to be working as all my banking apps are fine. Another thing to note is that I flashed magisk using unofficial twrp as there was no official one available yet. With cts check failure, what would be impacted in the root?

Sent from sagit
[Magisk] Didgeridoohan:
Everything I've got to offer can be found here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] DON2003:
where can I see the log? so I should set the fingerprint of the 1 not working like before so it will stuck on boot then save the log? where can I find it?
[Magisk] spicediablo:
Thanks! I understand better after reading the article. I would like to know if there is any risk in messing with the fingerprint value? I don't want to brick my brand new phone :)
[Magisk] Didgeridoohan:
That would be the preferred procedure. Logs:

https://github.com/Magisk-Modules-R...lob/master/README.md#collecting-logs-manually
[Magisk] Didgeridoohan:
There's always risks involved when modifying your device... Make sure to have a backup of any important data.

But, since this is a systemless modifications it's usually quite safe.

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] Didgeridoohan:
Start by updating the module. Report back if the issue persists after that.

MIUI is weird... Global ROM usually has better luck passing the ctsProfile check. I'm currently investigating.
[Magisk] Dil3mm4:
Hello [MENTION=4667597]Didgeridoohan[/MENTION],

on latest Magisk beta 16.6 the installation it's failing asking to install Magisk 15.0+

Please, tell me what you need to troubleshoot it.
[Magisk] Didgeridoohan:
Everything needed for troubleshooting is mentioned under "Issues" in the OP (and in extensions, the docs).

I can take a wild stab at guessing at your issue though. Broken Magisk installation. Possible solution - reinstall Magisk. If that doesn't work, logs please.
[Magisk] Justin Timberlake:
improved hiding (disabled)

ro.build.selinux: this props doesnt currently on your device

cant hiding magisk manager through magisk settings

this is the problem im facing yet cant open this Mandiri Online banking app while the others is accessible.
[Magisk] Didgeridoohan:
All that you're talking about is perfectly normal, and simply means you're using a stock (or near stock) ROM. It has nothing to do with being able to ride root fool an app. Except this:

What do you mean by this? It has nothing to do with this module, but would you care to elaborate?

A common detection method recently is apps checking for "Magisk" in the app name. This'll be circumvented in a future update of the Manager. You can test it right now though by uninstalling the Manager and try the banking app again.
[Magisk] Justin Timberlake:
[/COLOR]

yes im using debloated stock rom

i read on your web Hiding the Magisk Manager and Unhiding the Magisk Manager

already tried that with debloat systemlessly module to uninstall magisk manager but still there after reboot

maybe all of this because my rom came with pre-installed magisk, magisk manager and should go with clean install check non-root option?

tried clean install but no luck, but i can uninstall magisk manager at least.
[Magisk] Didgeridoohan:
The Manager does not disappear when you use the option to hide it. It simply randomises the package name. You can check this by going to "About" in the Magisk Manager and it'll either show com.topjohnwu.magisk if it's not hidden, or com followed by a random string if it is.

Having Magisk pre-installed on your ROM might cause issues with the hiding feature, but only if the ROM has the Manager installed as a system app, and even then the Manager won't disappear. There'll simply be two Managers since the system installed one can't be uninstalled.

So the banking app worked after you had uninstalled the Manager? :good:
[Magisk] chudy_85:
Work great on my p9 but I must added my own fingerprint to pass certificate and safety net
[Magisk] Didgeridoohan:
Care to share that fingerprint? It'd make a great addition to the list...
[Magisk] Justin Timberlake:
yeah its shows random package name after clean install

im eager to find more solution on this

im using 3 banking apps and only one that detects root? others is fine

still no luck on that
[Magisk] Didgeridoohan:
Last OT post on this in this thread...

Do you mean that it makes no difference when you uninstall the Manager? Or you can't uninstall it?

For further troubleshooting, take a look here and then ask any additional questions in the general support thread.
[Magisk] Justin Timberlake:
iight i'll give it a go, thanks for the feedback!

i can uninstall yet still no differences on that app don't know about others app though.
[Magisk] chudy_85:
Here you have

Huawei P9 (7.0)=HUAWEI/EVA-L09/HWEVA:7.0/HUAWEIEVA-L09/C432B502:user/release-keys
[Magisk] christian.arvin:
@OP

An updated fingerprint of Asus Zenfone 2 Laser MM

Asus Zenfone 2 Laser (6.0.1)

asus/WW_Z00L/ASUS_Z00L_63:6.0.1/MMB29P/WW_user_21.40.1220.2196_20180308:user/release-keys
[Magisk] skullkid383:
motorola/jeter_sprint/jeter:8.0.0/OCP27.91-23/23:user/release-keys

[MENTION=4667597]Didgeridoohan[/MENTION]

All credits go to [MENTION=5472845]fireball0093[/MENTION] for getting this stock fingerprint for the moto g6 play xt1922-7
[Magisk] boilerman92:
Work perfectly with magisk 16.6 mi5 miuipro and floppy kernel:svetius:
[Magisk] Didgeridoohan:
Update to v2.3.2-v21

My summer vacations are over and it's back to work. Have some time to properly work on my projects again.

A bit of a bug-fix release and here's the changelog:

Changelog

v2.3.2

Finally fixed installing with the configuration file on a clean Magisk installation.

Fixed updating placeholders if boot scripts gets restored at boot.

Updated the power requirements to 1.21 gigawatts.

Updated and added new fingerprints (Asus Zenfone 2 Laser, Huawei P9, LG G4, Motorola Moto C Plus and G6 Play, Samsung Galaxy J5 2015, Xiaomi Mi 4C and Mi Mix 2S), list v21. Thank you to [MENTION=8298415]xDoge[/MENTION], [MENTION=8340552]jenslody[/MENTION], [MENTION=2567034]slimdick[/MENTION], [MENTION=4190256]chudy_85[/MENTION], [MENTION=6642823]christian.arvin[/MENTION], [MENTION=8931427]skullkid383[/MENTION], [MENTION=5472845]fireball0093[/MENTION], [MENTION=5250567]ericlnu[/MENTION] and cnrd @ GitHub.

Miscellaneous fixes and updates.
[Magisk] Alejndrox097:
Huawei Honor 6X (8.0.0)

HONOR/BLN-AL10/HWBLN-H:8.0.0/HONORBLN-AL10/528(C00):user/release-keys

Magisk Hide
[Magisk] fmc000:
LOL
[Magisk] spicediablo:
I have reset the fingerprint bck to default without any issues.

Sent from sagit
[Magisk] transerrok:
Please add this device fingerprint for Redmi Note 8 Pro:

ro.build.fingerprint=Redmi/begonia_ru/begonia:10/QP1A.190711.020/V11.0.2.0.QGGRUXM:user/release-keys

ro.product.manufacturer=Xiaomi

ro.product.model=Redmi Note 8 Pro

ro.build.version.security_patch=2020-02-01
[Magisk] DON2003:
My phone Lenovo K5 Pro still got stuck on boot no matter which fingerprint I picked, even Treble mode same stuck on boot, why?

can I just edit my build.prop ro.fingerprint and pass cts? read my build.prop and the ro.fingerprint is something like treble thing,.

anyone?
[Magisk] Didgeridoohan:
You can edit build.prop manually and achieve the same result as this module (if the partition isn't permanently read-only).

It you want to get further help with this module (or other issues) you'll have to try to provide those logs I keep asking about...
[Magisk] DON2003:
thanks, but which fingerprint would you suggest me to try? also I have a thought that will I also be stuck on boot due to replacing the ro.fingerprint? I am afraid that the stuck on boot is caused by the module did rename the build prop? bec I might not as easy to get out with unroot or modifying the module via twrp, any idea? thanks again
[Magisk] Didgeridoohan:
If you're using a GSI, that's likely why you're experiencing issues with this module (I've already mentioned that there has been other similar reports). From what I've understood it's not the fingerprint that's the issue (but since I haven't been able to analyse any logs on the subject, hint hint, I have no idea what it could be).

Use whatever fingerprint you feel comfortable with, and make sure to match the security patch date (it's explained in the module docs). If you're worried about bootloop, start with making a backup of your original build.prop and restore that of necessary.

Lastly, the module does not touch the build.prop.
[Magisk] DON2003:
thanks, you are so helpful,

if wrong fingerprint is selected or used, or wrong or mismatch security patch date, isn't it will just still not pass the cts but wont stuck on boot, correct? so the stuck boot should be something with the magisk that not booting the module?