yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Update to v2.2.2-v18

Bugfix and maintenance update.

I also want to take the opportunity to push for the configuration file feature of the module. With that, it's very easy to set all your desired settings and custom props without having to run them through the terminal. Just create the file, place it in /cache and you're good to go on the next reboot. Keep the file handy if you ever need to reflash Magisk and/or the module for easy setup.

Changelog

v2.2.2

This is not the changelog you're looking for. You can go about your business. Move along.

Fixed a bug with setting custom props where the value contains spaces.

Added a couple of fingerprints (OnePlus 6 and Xiaomi Mi Note 2) and cleaned out a few old ones, list v 18. Thank you [MENTION=8787657]Nathan2004[/MENTION] and [MENTION=7166349]turbolukex5[/MENTION].

As usual, a whole bunch of script improvements that hopefully won't break anything.
[Magisk] abacate123:
First, thanks for this, very nice. I was actually waiting for it. But a question: Can I place the config file somewhere else (like internal storage, or external sd card for example)? Or is required to be there in /cache? I mean, when I do a full wipe (clean install), I don't wipe external nor internal storage, that'd be easier to place the files there, as I can do with other modules.
[Magisk] Didgeridoohan:
The configuration file is actually just a one shot thing to set the configuration you desire. It's deleted after the configuration values have been read from it and saved to the module.

Keep a copy on your internal storage and copy it to /cache whenever new configuration is needed.
[Magisk] Notonlyeyes:
Hi [MENTION=4667597]Didgeridoohan[/MENTION] ,thanks for all your work.

Updating list Fingerprint for Huawei P8 Lite 2017:

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/399(C432):user/release-keys

Security Patch Date: 2019-01-01

I tried the test it's working

Huawei P8 Lite 2017 (8.0.0)=HUAWEI/PRA-LX1/HWPRA-H:8.0.0/HUAWEIPRA-LX1/399(C432):user/release-keys__2019-01-01
[Magisk] rooban90:
My search for mi a2 lite doesn't bring up anything in this thread.

Hence posting here

ro.build.fingerprint=xiaomi/daisy/daisy_sprout:9/PKQ1.180917.001/V10.0.1.0.PDLMIFJ:user/release-keys

ro.build.version.security_patch=2018-11-05
[Magisk] skullkid383:
[MENTION=4667597]Didgeridoohan[/MENTION]

moto E5 play fingerprint:

motorola/james_sprint/james:8.0.0/OCPS27.91-140-1/1:user/release-keys

patch date:

oct 1,2018
[Magisk] winamp26:
Can I install on S7 edge?
[Magisk] Didgeridoohan:
Quick update, in case anyone is wondering what's going on.

I'm back from my winter wonderland and real life is gonna kick in hard tomorrow. There are a whole bunch of fingerprints that I need to go through, provided by a host of wonderful people, and there are also a few ideas for the next update for the module. Hoping to get some work done on both the fingerprints list and the module this week (the prints list should be done much sooner).
[Magisk] Didgeridoohan:
There are no device restrictions in this module. Go for it...
[Magisk] Didgeridoohan:
Fingerprints list updated to v41

New and updated fingerprints added to the list. Shoutout to (in no particular order) [MENTION=8122617]PHiDi[/MENTION], [MENTION=9637474]michaelmaverick[/MENTION], [MENTION=7280276]ipdev[/MENTION], [MENTION=4104899]z0mBy[/MENTION], [MENTION=5685876]pekkle_hksar[/MENTION], [MENTION=4553005]Notonlyeyes[/MENTION], [MENTION=7135952]l2o88j[/MENTION] and [MENTION=8931427]skullkid383[/MENTION]. Huge thanks for your contributions!

Added prints for:

Motorola Moto E5 Play

Samsung Galaxy A5 2017

Xiaomi Mi A2 Lite

Xiaomi Redmi Note 6 Pro

Updated prints for:

Huawei P8 Lite

Xiaomi Mi 8

Xiaomi Mi Mix 2S

Xiaomi Redmi Note 5 Pro
[Magisk] Didgeridoohan:
I tested all the fingerprints you mentioned and they all pass on my devices. No idea what that could be about... Sounds farfetched that it would be because of the processor architecture, but who knows? Have you tested again, just to make sure you didn't have a temporary case of the Magisk v18+ MagiskHide failure?
[Magisk] skullkid383:
he might need to wipe dalvik

---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------

i see how it is im last lol j/k
[Magisk] Didgeridoohan:
Last but not least, right? :p
[Magisk] nikal:
USB debugging issue

Hi,

I'm using Magisk for rooting my device (an old Vodafone Tab running android 5.1). The problem is that after patching the boot.img with magisk systemless rooting I noticed that USB debugging is turned OFF after each reboot. Searching for days in order to find a solution I ended to this thread and this specific module which can alter the prop values. I tried turning ro.debuggable to "1" but this didn't solve my problem. I suppose that I have to add custom prop values in order to keep USB debugging ON after each reboot. I found the following values to be related with USB debugging.

persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

Is this the solution or should I follow a different approach ?

Kind Regards
[Magisk] Didgeridoohan:
Start by disabling MagiskHide and rebooting. That will make sure that all the props that are changed by Magisk are set to their original values.

If that fixes it we know that it's caused by one of those props. Now you can use this module's function to set/reset the sensitive props changed by MagiskHide, one by one until you find the culprit.

If turning MagiskHide off doesn't fix it there's something else going on... Trying different props might not help, but it likely won't hurt either.
[Magisk] nikal:
Hi,

thanks for the reply. Many of these fixes I tried the last days without any result. I finally found a fix to my problem by adding a new custom prop with the following string.

persist.sys.usb.config=mtp,adb

actually the above string was already set in the props I just added the "adb".
[Magisk] Didgeridoohan:
Nice! Glad you got it working, but it's weird that Magisk should have an impact like that...

Thanks for sharing, I'll add that to my bag of tricks.
[Magisk] ipdev:
I guess I missed prints v41. You are just too quick to update sometimes. :D

Some more fingerprints for the next update.

January Pixel(s) and Essential.

It looks like the Nexus line is officially EOL.

Plus one or two other.

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

Well then... Just for you, here's fingerprints list v42. As usual the list will update when you run the props command, or by using the -f option or from the fingerprints menu if you've disabled automatic updates.

Added:

Samsung Galaxy J7 2017

Updated:

Essential PH-1

Google Pixel

Google Pixel XL

Google Pixel 2

Google Pixel 2 XL

Google Pixel 3

Google Pixel 3 XL

Google Pixel C

OnePlus 3T

OnePlus 5T
[Magisk] nikal:
Thanks for the reply,

it's weird given that I struggled to find other users having similar issues. One more issue I'm facing right now is that titanium backup doesn't detect root. I have tried almost every suggestion I found in forums and blogs but without any luck so far. Do you have any suggestion? Some way to get a log that may give me a clue of what's going wrong ?

thanks in advance!
[Magisk] Didgeridoohan:
As far as I can remember, I've seen one single mention of this behaviour and that was less than a week ago in a GitHub issue (was that you maybe?): https://github.com/topjohnwu/Magisk/issues/946

I don't really know about your TiBu issues... I've seen a few other reports of users having problem getting the app to work with Magisk, but I've never been one of them. Does other apps get root without issue?

You could grab a logcat while opening TiBu, that might show what's going on. You could also try enabling "Force system Busybox" (or something like that) in the TiBu troubleshooting settings (install Busybox first, I recommend [MENTION=4544860]osm0sis[/MENTION]' from the Magisk Manager Downloads).

We're getting a bit off topic for this thread though, so if you want to continue troubleshooting please post in the general support thread and tag me if you want my input.
[Magisk] nikal:
OK, I'm moving my request to the general support thread as per your suggestion (no it wasn't me with the post in GitHub).
[Magisk] oslo83:
Not a proper bug report, i know...

If you happen to hit '1' and not 'y' at the step screenshoted, I think it will broke script.View attachment 4683022
[Magisk] Didgeridoohan:
Good enough, I see what's wrong. Thanks for reporting.
[Magisk] fjuniper:
Sorry for the very basic question....

I have used Magisk for some time, but never used modules until I rooted my new S9 Plus - and got SafetyNet: CTS Profile fails and Basic Integrity passes. This module came recommended, so I have installed it. My problem is that I cannot get it to start!

In 2 different terminal emulators, I type props and just get:

/system/bin/sh: props: not found

Am I supposed to get to a particular directory? I think the instructions would have said if that were the case.

I have tried uninstalling and reinstalling the MagiskHide Props Config module.

I have the osm0sis busybox module installed, I have root, I have tried su in terminal - no difference.
[Magisk] Didgeridoohan:
First thing to check is if you've enabled Magisk Core Only Mode (it's in the Magisk Manager settings). If so, disable it or no modules will work.

If that's disabled already you'll have to post some logs for me to look at. Check the docs for what logs might be relevant: https://github.com/Magisk-Modules-R...lob/master/README.md#collecting-logs-manually

Edit: the error means that the module either isn't mounted by Magisk or hasn't been installed properly in the first place.
[Magisk] skullkid383:
is he typing su first might be issue there
[Magisk] Didgeridoohan:
Apparently:
[Magisk] skullkid383:
sry didnt read all i seen is where he put props cmd and issue
[Magisk] jenslody:
To nake it clear:

you tried it as root, after typing "su" and granting root access ?

And you rebooted after installation ?

I you type "su" what's the output of "whoami" in terminal ?
[Magisk] Jaymin.0.1910:
Typing "su" first with this module is not necessary as long as I see the code, the script will automatically detect root access and recall itself with root.
[Magisk] fjuniper:
Delete pls
[Magisk] fjuniper:
Thanks [MENTION=4667597]Didgeridoohan[/MENTION]

Magisk Core Only Mode is disabled i.e. grey, slid to the left.

propsconf_install.log attached

Thanks [MENTION=8340552]jenslody[/MENTION]

Yes, I have tried it with and without 'su' first. I didn't think I would need to, but was trying anything!

Yes, have rebooted many times and tried uninstall module / reinstall, reboot.

whoami gives "root"
[Magisk] Didgeridoohan:
With Termux it's generally necessary to run su first, but not on a regular terminal emulator.

You might want to try to attach that log file again, since I don't see anything. The Magisk log would also be useful and I'm assuming that there were no other propsconf files present in /cache, or?
[Magisk] fjuniper:
Sorry, propsconf_install.log attached now.

Also magisk.log attached.

Correct, no other propsconf files present.
[Magisk] Didgeridoohan:
Things look somewhat ok (the module seems to be installed alright), but you've added some weird apps to your Hide list, namely apps that actually need root. Titanium Backup, the TWRP app, and here's the kicker: Terminal Emulator. If you have that on your Hide list everything Magisk will be unmounted as soon as you start the app and for all intents and purposes the props script won't exist (hence the error).

The Hide list is for those apps that don't work when they detect Magisk, nothing else.
[Magisk] jenslody:
But in this case 'su' should not work at all and 'whoami' can not return 'root'.
[Magisk] atrix4nag:
sorry if its a nubie question.

I am having ctsprofile false in my magisk app. I am on android pie version on Oneplus 5. I installed the props config module from the magisk modules, downaloaded the file in OP, installed it from the app, from TWRP. none of the options updated ctsprofile to true. am I missing something. Please help me to make this working. I think I am missing some thing. .Please guide me through the steps.
[Magisk] fjuniper:
Thanks for the detailed reply. The reason I had been messing about hiding unusual apps (have not hidden them on my previous phone) was because I had been reading a piece about Banking Apps being sneaky and looking for apps that require root as a way of determining if you device is rooted. I bank with Barclays in the UK, and they are among the worst - it wont work on my S7 edge even if I unroot.

I have removed all hidden apps, uninstalled your module, rebooted, installed your module, rebooted, gone to Terminal, typed props, and I get...

No command 'props' found.
[Magisk] Didgeridoohan:
Very true. I missed the part about 'whoami' returning 'root'...

First of all, the apps you add to the Hide list aren't hidden for other apps. Magisk will be hidden for the app on the list. Just to clarify...

Second: The module seems to be installing correctly and the boot scripts looks like they're running, but if you don't have any other propsconf files (mainly propsconf.log) in /cache that means that no scripts ran. There's also no sign of the module actually being mounted by Magisk during boot. Could you please install the Magisk Canary debug build to get a better and more verbose Magisk log? The installation log from the Magisk Manager when you install the module would also be useful.

Third: "No command 'props' found" looks like what you'll get if you don't first call 'su' when using Termux.
[Magisk] Didgeridoohan:
The regular steps are:

Run 'props' in a terminal emulator.

Pick a fingerprint from the supplied list.

Reboot.

If it doesn't work there might be a number of reasons. Check the documentation for more info, start here: https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] atrix4nag:
thanks for the response.

how to run props in terminal emulator.. sorry for stupid question
[Magisk] Didgeridoohan:
No worries, everyone's a noob at some point. You'll actually find some info on that subject as well in the documentation (most things are covered there, so I suggest you take a look at that before continuing further).

I usually use Terminal Emulator, and then it's just a matter of typing in props, hitting enter and then follow the ui.
[Magisk] atrix4nag:
Thanks a lot.. it worked.
[Magisk] fjuniper:
1 - Thanks for the clarification.

3 - Quite right - but the message was effectively the same after running su.

2 - I have installed the Canary debug build - and I now see what props does :)

It all worked perfectly; I pass both SafetyNet checks.

Do you still want to see logs? Of course I now don't know whether it is a good idea to stick with the Canary debug version, given that it says "These builds are NOT for the faint of heart: professional users and developers only!", or to go back to standard Magisk...
[Magisk] Didgeridoohan:
So basically your Magisk installation was messed up and installing the Canary build fixed it.

If you want to stay on the Canary builds is up to you, of course. Just keep in mind that there might be bugs. But, you'll also get the latest features and improvements.
[Magisk] michaelmaverick:
Newest fingerprint for Xiaomi Mix 2S: Xiaomi/polaris/polaris:9/PKQ1.180729.001/V10.2.1.0.PDGMIXM:user/release-keys__2018-11-01
[Magisk] paolocorpo:
Dear [MENTION=4667597]Didgeridoohan[/MENTION],

I just installed your module on my LG GOOGLE NEXUS 5X

I am on custom PIE rom GZERO + Magisk beta 18.0

I have used the fingerprint recalled for N5X oreo with success !!

Thnaks

Paolo
[Magisk] Bogdans29:
What is unity ... Like In module s unity 3.0
[Magisk] Didgeridoohan:
This module doesn't use the Unity template, so I do believe you've ended up in the wrong place. Sounds more like a question suited for the Unity thread.
[Magisk] martyfender:
A funny thing happened today, on a Nextbook Ares 8A tablet that I had factory reset then tried to test other build fingerprints on. I tested a Google Pixel fingerprint and like I had found before, it did not pass safetynet.

However, within a minute or two of changing this fingerprint, I received an email message from Google congratulating me on purchasing a new Google Pixel device!

I wish I had the extra cash to purchase one! Right now I am perfectly happy with my Iphone 6, that my son so generously gave me when he upgraded to an Iphone 7. It just works with no problems and that is on IOS 12 betas.
[Magisk] Didgeridoohan:
Yeah, that sometimes happens when changing the fingerprint to a Google device.
[Magisk] martyfender:
As before, it looks like the only fingerprint that works is one where the device is also an x86 device: the Asus Zenpad S 8.0. I don't believe that any other fingerprint is from x86 devices, except my Nextbook Ares 8A fingerprint, but then, I did not try them all, or search to find out.
[Magisk] ToXiTe:
Will the x86 fingerprint work with x86-64 device?
[Magisk] ipdev:
The regular ZenFone 2 should be x86.

ZenFone 2 Laser is a Snapdragon 410

ZenPad S 8 failed for me.

ZenFone 2 failed also.

Edit 2: Nextbook Ares 8A failed also.

ZenFone 2 Laser, and every other arm fingerprint I have run across, seem to work fine.

Can you try ASUS ZenFone2 (ZE550ML)?

I do not have an x86 device, so I am curious if the regular ZenFone 2 fingerprint works?

I attached it below.

Download printslist.txt and copy it to the root of sdcard and remove the .txt

Then run props and select Custom under fingerprints. Select 1 or 5.

1. Has the security date.

5. Is just the fingerprint.

:confused:

Edit:

Attached file.
[Magisk] martyfender:
I don't see custom under fingerprints, I only see custom under Add/edit custom props.

I think it is because both total commander and mixplorer will not let me rename it. It would only open in a browser window in android so I had to create a text file and copy the text to it. and permissions can't be changed because it is on the internal SD card. They are 660. What am I doing wrong? Even copying it to root and changing the permisssions does not let me rename it in total commander.

I finally figured it out by opening it in Mixplorer text editor and resaving it with the name: Printlist.

This time, unlike other fingerprints, other than the Zenpad 8 s, cts profile is false, but basic integrity is true. So that is one step forward, I guess. I chose your option 1.

UPDATE: I set custom security patch level and it still does not pass the cts profile.

When I go to custom again, it only shows part of what I typed for the security patch level. That may be the reason.

This is what I thought I typed under custom properties:

I give up for now and reset to my devices working fingerprint. As I stated earlier, I am just testing all of this. My own device's fingerprint passes with Magisk Hide enabled.
[Magisk] bajie2009:
Hey [MENTION=4667597]Didgeridoohan[/MENTION], I have a Mix 2 china build MIUI V10.02 and none of the fingerprints seems to work. I tried changing boot stage with no result. ShellHide also doesn't seem to do anything. My phone pass basicIntegrity but fails ctsProfile. Can you please you can check out my logs. Thanks

Cant post link because im too new.. "/s/77mj7y0b7igncht/propslogs.tar.gz?dl=0" but the logs are here in my dropbox.
[Magisk] fjuniper:
Just wanted to come back and thank you for your help. My rooted S9+ is now working with the UK Barclays Bank app as well as the My EE app (mobile provider) and a couple of other banking apps. Unfortunately Halifax and Starling detect root, but I am not that bothered. The annoying one is Google Pay. I have this working with Monzo for contactless payments on my S7e, but when I added the card to the S9+, it says that I can use the card for web sites, but not for contactless in stores - a major step backwards....

<pause>

SafetyNet checks were successful on Friday, but I have just checked again and both fail!! Agghh - no wonder GPay won't work...
[Magisk] Didgeridoohan:
Been known to happen with the MIUI China builds since forever. And I've no idea why... Sorry.

To understand that issue, someone with an afflicted device would have to get their hands dirty and go digging for the cause.

I think I've seen reports that Halifax can be fooled by adding their domains to your hosts file. Check here, under "External connection": https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

There are a number of reports of MagiskHide intermittingly failing from time to time on Magisk v18. Toggling MagiskHide off and on in the Manager settings should be enough to make it work again. Why it's failing is under investigation.
[Magisk] tmptrsn:
Hi,

I used this to change my Xiaomi Mi 8 fingerprint, and I want to update with Xiaomi OTA, and so I reset the fingerprint. However, when I go into TWRP to flash the update, it gives an error saynig the ZIP expects the fingerprint to be X (my original fingerprint) but it's not it's fingerprint Y (the one I changed it to). I've tried restoring the fingerprint, manually changing it to the one it should be, unrooting, and removing the module, but nothing seems to work.

Any ideas?
[Magisk] Didgeridoohan:
This module does not make any permanent changes (it's a Magisk module after all), so there should be no trace of any used fingerprint when booted to TWRP.

Could you provide the recovery log showing the error?
[Magisk] bunchai16082014:
Hi, I want to ask some question about SafetyNet :confused:

1. Will my phone still pass SafetyNet test, if I remove some bloatware apps or system apps, using Magisk for root access ??

2. Since Xposed Installer is a Magisk Manager module. Then I still can install xposed module in Magisk Manager, right ? But, if I use some xposed module in Magisk, will it pass SafetyNet test ?

3. Can I use ZRAM or SWAP when I use systemless root like Magisk, and if so, will SafetyNet detect this ?

Thank You
[Magisk] rooban90:
It should if you have the fingerprint and patch date property set using this module with magisk root along with basicIntegrity as true
[Magisk] Didgeridoohan:
You're a bit off topic, since your queries doesn't really have anything to do with the module. But here's a quick overview of your three scenarios:

SafetyNet should pass just fine.

SafetyNet will trigger.

SafetyNet should pass just fine.
[Magisk] :
Hi,

First of all thank you for this module. It's very powerful and configuring the options is very easy via terminal. However I have an issue. I have searched the topic but haven't found a concrete answer.

Basically... Since encrypting my device, prop changes don't work. Before encryption I had Camera 2 API enabled. After encryption it stopped working (even though it was still set to 1 when I checked with your module before making changes). I tried your module and set it to 1. I tried both methods of loading the change and it didn't work. The only thing that works is either unencrypting (not desired due to weakend security) or changing the build.prop file in system partition.

I have attached a log generated by your module however if you need any more logs then please let me know. I would be very thankful to get this sorted as it would make updating the ROM very easy with no extra ZIPs required.
[Magisk] paolocorpo:
Dear developer,

I have a doubt

Is your module able to pass the Safety net check and the Certification issue into app Play Store or just the Safety net check ?

Thanks

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] madbat99:
This is designed to help pass cts profile, and only when failiure is due to custom, or uncertified rom. Also for making systemless prop changes.

It SHOULD help play store certification.
[Magisk] paolocorpo:
I have applied this module to my Mi A1 with Pie and Magisk

I used that one for OREO

Safety Net check is OK

And play store certification has been ... fixed just because I don't find into setting menu the relevant line ... Usually it is under that one of Play Store version ... ;)

View attachment 4687293

Inviato dal mio Mi A1 utilizzando Tapatalk