yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
Has anyone had their Mount Namespace Mode reset to Inherit Namespace Mode, when they had Global Namespace Mode set in settings, previously? That was on Canary 18007, that I first noticed it.

I use Global Namespace Mode because the author of Apps2SD in the past recommended using it with his app if one was using Magisk. On two of my devices, I am no longer using Apps2SD, so should I go back to Inherit Namespace Mode? I have not seen much info posted in the Magisk threads concerning what these different modes do. Does anyone have any better info on what the different Namespace Modes do?

Thanks
[Magisk] jcmm11:
Namespace modes have to do with the scope of changes that are applied when you mount/remount something. You basically have 2 namespaces, isolated and global. Inherited simply means that any su instance will inherit the namespace of it's parent process, with the default being isolated.

This means, for example, if you remount system as rw only the process that issued the remount (and any child processes it may spawn) will see it as rw. All other processes will still see it as ro. If you set the namespace to global (which you can do from a script or terminal emulator by using "su -mm -c <command that wants global namespace>") then the change will be seen by all processes.

https://su.chainfire.eu/#how-mount
[Magisk] Adithya88:
I have flashed this on stable 18.0 magisk and the cts profile is still false. Tried multiple times by installing and uninstalling module. Any other workarounds?

Device is Chiron having miui 10 beta.
[Magisk] Didgeridoohan:
Have you also chosen a certified fingerprint? Just making sure, it's relatively common that users expect a flash and forget experience...

Take a look in the docs: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md
[Magisk] martyfender:
[MENTION=4667597]Didgeridoohan[/MENTION] Were the logs I provided useful in any way?

Thanks
[Magisk] Didgeridoohan:
Yeah, they're confirming some of the issues that I've fixed for the next release. Just need time to test before throwing it out there.
[Magisk] viberiaz:
Samsung Galaxy J5 2016 (6.0.1) not availabe in the fingerprint list. Only (7.1.1) pls update
[Magisk] jenslody:
Please provide the fingerprint.
[Magisk] habylab:
Thanks so much for this. Fixed CtsProfile false on my OnePlus 6!
[Magisk] se7ensde:
I reset the module and not I keep getting a message about the props being wrong and to reboot to fix it but a reboot never fixes it. I've included a screenshot and logs.
[Magisk] viberiaz:
J5 2016 (6.0.1) pls add

samsung/j5xnltexx/j5xnlte:6.0.1/MMB29M/J510FNXXU2AQI6:user/release-keys
[Magisk] Didgeridoohan:
That's been covered a few times already over the past few days... The module doesn't work with Magisk Canary build 18006+. I'm testing some major new features for the next release, but have very limited time due to IRL stuff. Either downgrade Magisk or wait for a new release of the module (currently I have no idea when that will be, but I'm hoping within the next week).
[Magisk] blakegriplingph:
Anyone here tried this on the World Rally Championship app? It spazzes out on startup whenever it detects that it's running on a rooted device, and it appears to be using a method similar to this one.
[Magisk] Didgeridoohan:
This module doesn't have anything to do with any of the methods in the linked repository.

Every single one of those methods can be dealt with by using MagiskHide though, so just add the app to the Hide list and you're good to go. To be clear: I tested and it works just fine by just using MagiskHide (the Manager doesn't even need to be repackaged with a random name).
[Magisk] blakegriplingph:
Yeah I know that. What I meant was the app in question appears to be using the methods I linked earlier.

I tried MagiskHide on the WRC app myself and yet it's still being detected for some reason. Any clues as to why? I am currently running Magisk on atvXperience with Android 7.1 and Magisk 18.0. I've already set the tag from test-keys to user-keys to no avail. :/
[Magisk] Didgeridoohan:
And like I said, the linked methods are all taken care of by MagiskHide... For example, you don't need to change to user-keys manually, MagiskHide already does that for you (or should do it). Sounds to me like your MagiskHide isn't working as it should...

Take a look here and then continue this in the General support thread, please (it's a bit OT for this module):

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] blakegriplingph:
As what I was thinking. Upon trying the props util when I selected the option to manually set/reset MagiskHide sensitive props, the value for build tag is still set to test-keys prior to when I changed it.
[Magisk] karnan_bs:
Quick question. What should I do if my device fingerprint is not listed in this module? My device is Moto G5S plus. I tried chpoosing other devices' fingerprint and it made the basicintegrity as false too. So what should I do? Can you just tell me what should be next step? Whether it's to change build prop or to add custom fp. Can you just point me what should I do and I can go from there by reading the instructions. It's all a bit confusing as I'm fairly new. Thanks.
[Magisk] Didgeridoohan:
That's not normal behaviour... It is generally possible to use any certified fingerprint for your device.

Providing the logs might help in finding the issue.

You might also try to find the fingerprint in question and you could use that and I can add it to the list.
[Magisk] P-KAY 2323:
The original prop values are not loaded, oSs1bly due to full reset oft the module, or something has gone wrong.

I keep getting this error. Changed ROMs even. Worked before... Help me man.
[Magisk] Didgeridoohan:
This applies to unofficial builds as well:

https://xdaforums.com/showpost.php?p=78770143&postcount=1331
[Magisk] P-KAY 2323:
Oh. Thanks. I'll wait in that case. Or roll back.
[Magisk] bitye:
I installed latest with recommended BusyBox.

Terminal

Su

props

Selected my Poco

Used default

Boot loop

Uninstall magisk solved but removed my TWRP again and can't get a PC at night :(

But don't care just help me who can use with stock MIUI 9.1.24 and magisk 18
[Magisk] Greenchain:
???

who uses miui

sorry if you like it :D
[Magisk] bitye:
I tried almost all ROMs here and always MIUI was my favorite Android after Flyme so me ;)
[Magisk] DN38416:
I noticed there doesn't seem to be any for the Huawei Mate 20 Pro. So here's mine on 183 firmware:

HUAWEI/LYA-L29/HWLYA:9/HUAWEILYA-L29/183AUSC636R1:user/release-keys
[Magisk] oslo83:
I found another little bug and made it critical, props does not run anymore, tryed delete/reinstall...

I updated WHILE keeping root by flashing a patched boot at the right time.

After that, i was still rooted and :

-magiskhide showed correct actual signature but not correct stock signature ; It was now still the old one.

-magiskhide custom props were not applied anymore and default settings was not saved...

-after a fullreset option from Magiskhide ; props does not boot anymore, straight to your error for report screen...

Help!

Last log:

https://mega.nz/#!3dd2ESQB!SMeLKQbQpN1o_QyquZ5LR1A8DmSHd7bmoWyJRi2Smfs
[Magisk] Didgeridoohan:
https://xdaforums.com/showpost.php?p=78770143&postcount=1331

Current ETA for a fix (if everything works out smoothly): sometime this weekend.
[Magisk] oslo83:
Ooops sorry about that. :)
[Magisk] Didgeridoohan:
No worries... :D But, just to rub it in that little bit further, take a look under "Known issues" in the OP. :laugh:
[Magisk] bitye:
Am I understand correctly that latest version not working with Magisk V18?

If yes I understand the bootloop issue on my POCO F1.

I tried this too: Place a file named reset_mhpc in /cache (or /data/cache on A/B devices) and reboot.

But also not working at all. Need to remove magisk with uninstaller and reinstall everything related to that.
[Magisk] Didgeridoohan:
No, that's not at all what is happening. The module isn't compatible with the latest

Canary

builds (and any unofficial builds from the current code). And the issue has nothing to do with bootloops, but rather that the module won't do it's thing at all (since the boot scripts don't run properly)...

The only way for me to know what is going on is if you can provide logs related to the problem. If it's a proper bootloop that could be an issue, but if the device simply gets stuck at some point during boot you should be able to let it sit for a while and then boot to recovery and pull all the necessary logs from /cache.
[Magisk] bitye:
I need to go to a business trip so can't play with phone now. But will try to collect some asap.
[Magisk] madbat99:
You started modding your phone on your way to a business trip? LoL. Hope you have a backup phone. Hang in there dude.
[Magisk] oslo83:
Huawei P20

HUAWEI/EML-L29/HWEML:9/HUAWEIEML-L29/160C432R1:user/release-keys__2018-11-01
[Magisk] darkrevlis:
You have here my logs. I can't turn on and working your module with latest magisk canary build.
[Magisk] Didgeridoohan:
Update to v3.0.0/v3.0.1/v3.0.2-v42

Time for an update. Finally...

I've been extremely busy with life in the past few weeks and have only had a few minutes here and there to work on this update. And, since it's a pretty major update that means it's been taking a while to test everything out. Take a look at the changelog below and the updated documentation to get the details. The major thing for some users should be that the module works on the current Canary releases again.

I've been testing the update quite thoroughly, but I'm expecting a few (many?) bugs to pop up anyway. Please let me know if anything doesn't work as expected.

There have been a few fingerprints posted since list v42 was published, but I have not yet updated the list (it hasn't been a priority). I'll probably wait a few more days until the February updates start dropping in.

Edit: Found an issue with updating the module from v2.7.2 or earlier version. Quickfix v3.0.1 released...

Edit2: Another issue found... And fixed. Keep 'em coming. :D

Changelog

v3.0.2

Another quickfix, this time fixing editing already set custom props (a victim of slightly too heavy-handed optimisations of variable and settings retrieval in v3.0.0).

v3.0.1

Quickfix for updating the module from v2.7.2 or earlier.

v3.0.0

New function for device simulation. The module sets a number of device specifying props based on the used fingerprint. See the documentation for details.

New function for Treble GSI users that have a stock vendor partition: The module can use the certified vendor fingerprint found there. See the documentation for details. Thank you to [MENTION=7489364]oF2pks[/MENTION] for making me aware of this possibility.

New function where the currently used fingerprint automatically will be updated if there's a new fingerprint for that device added to the fingerprints list. See the documentation for details.

New function to set custom props in both post-fs-data and late_start service mode. See the documentation for details.

Updated the configuration file function so that the file will now be detected during installation or at boot. See the documentation for details.

Updated the locations for placing the configuration file when importing settings to the module. See the documentation for details.

Updated the configuration file to be version specific. Make sure you use the latest available configuration file.

Fixed compatibility with changed boot stages in Magisk v18.1-d73127b1(18006).

Fixed double download of fingerprints file if using the -f option and cleaned up the runtime options a bit.

Fixed module reset option.

Optimised variable and settings retrieval.

Optimised module boot scripts.

A whole bunch of minor fixes and cleanups.
[Magisk] Didgeridoohan:
In case somone tried updating to v3.0.0 and failed, try again with the v3.0.1 quickfix...
[Magisk] hyborian:
Fantastic ! Safety Net passes again for both under Magisk Canary release, thanks.

---------- Post added at 03:28 PM ---------- Previous post was at 03:11 PM ----------

I use a Pocophone too, no such bootloop. I also like MIUI and using the latest MIUI 10 developer ROM with Franco Kernel, I don't trust the other ROMs for a business phone - i.e. I only use custom roms for my "fooling-around" phones, YMMV.

The Magisk I use is the Canary release build. There must be something else wrong somewhere to give you a bootloop.
[Magisk] darkrevlis:
Yes is working well now with canary build. I'm using miui 10 on rn3 too.
[Magisk] Didgeridoohan:
If anyone's keeping score, quickfix number 2 (v3.0.2) was just released with a fix for broken editing of already set custom props.
[Magisk] JB v2:
I also can't get the Nvidia Shield fingerprint to pass the checks; I've confirmed that the module's working with some other certified fingerprints. Any ideas what could be going on?
[Magisk] Didgeridoohan:
I've tested and double-tested the Nvidia Shield fingerprints and they pass just fine on my test device. Do you have a Shield, otherwise I'm assuming it's just an academic interest... Your module logs with a Shield print active might show something (or not).
[Magisk] martyfender:
When I change a fingerprint and it asks if I want to enable device simulation. Upon reboot I see it is downloading instant apps in notifications and I do not have instant apps enabled in settings, Google, Google Play Instant. Is that normal with the device simulation? In my app list I also see Google Play Services for instant apps now installed.

You state to refer to the documentation but I could not find any info in there about the new simulation feature, or I just overlooked it, possibly?

The Asus Zenpad S 8.0 (6.0.1), is still the only fingerprint I have tried that passes SafetyNet on my x86 device with the exception of the device's original fingerprint.

Do you think it is because all of the other devices in your fingerprint list are ARM?
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#device-simulation
[Magisk] martyfender:
Thanks

Maybe it wasn't there yesterday because I had the tab already open in the browser and forgot to refresh the page?
[Magisk] martyfender:
In the process of testing fingerprints, I deleted app data of the play store and play services. I reset my fingerprint and the device passes safetynet. Now in the play store, it does not show certification information that the device is certified. that was several hours ago.

Does it take hours for this to show up again?

I solved it by going back to the original playstore version on the rom by uninstalling play store updates and then letting it update itself.
[Magisk] Didgeridoohan:
It's perfectly possible that it's a x86 - ARM thing, but I have no way of confirming or denying that...

The Play store certification can indeed take several hours to show up after a reset. It needs to do a check before it shows up, either by itself (at some kind of, long, interval) or you can force it like you did.
[Magisk] devloz:
[MENTION=4667597]Didgeridoohan[/MENTION] I have a fingerprint for LG G6, that is passing CTS check. For some reason, the 8.0.0 stock fingerprint is not passing, but the one from 7.0.0 works flawlessly. Tested on HavocOS 9.0.

LG G6 H870 (7.0.0)=lge/lucye_global_com/lucye:7.0/NRD90U/171732341982c:user/release-keys

Thank you so much for this module!
[Magisk] xTanker:
Can you add the fingerprint for 8.1 on Moto G5S?

8.1.0/OPP28.65-37/c13e:user/release-keys
[Magisk] ipdev:
[MENTION=4667597]Didgeridoohan[/MENTION]

Thank you for maintaining and updating this great module.

I've been hanging back on Debug 18005 till now. ;)

I haven't had a chance to try the vendor fingerprint option yet.

Question: How is the corresponding security date set, when the vendor security date does not correspond to the build fingerprint?

Example from vendor/build.prop

ro.vendor.build.fingerprint=OnePlus/OnePlus5T/OnePlus5T:9/PKQ1.180716.001/1901182129:user/release-keys
ro.vendor.build.security_patch=2018-06-05

ro.vendor.build.fingerprint=google/taimen/taimen:9/PQ1A.190105.004/5148680:user/release-keys
ro.vendor.build.security_patch=

Note:

I normally use propsconf_conf file for GSI. Device specific custom rom, I normally use the fingerprint(date) option.

Note 2:

Attached fingerprints.

- Nothing new, just updates. :rolleyes:

Cheers. :)
[Magisk] lakshya dahiya:
Hello, I have a problem, when I reboot with magisk hide and she'll hide, i pass safety net, but five minute later when I check again safety net never pass again. Can u help me, how do i give u log file

---------- Post added at 06:47 AM ---------- Previous post was at 06:44 AM ----------

Hello when I reboot with magisk hide and shell hide I pass safety net but if I check later I never pass safety net again my play store is certified. Can any one help which log file can i give u?
[Magisk] Didgeridoohan:
To be honest I'm basing this function purely on an idea by [MENTION=7489364]oF2pks[/MENTION] to just pull the vendor fingerprint as the print used by the module. Since I do not have a device that can run a GSI, I was kind of assuming that the security patch date wouldn't matter in this case... [MENTION=7489364]oF2pks[/MENTION] Could you help shed some light on this?

Thank you. I was actually hanging back a little and waiting for your awesome fingerprints updates before doing anything about the fingerprints list. I'll take a look at adding those to the list ASAP (which with my current life situation probably means sometime in the next 2-3 months... :laugh:).
[Magisk] Didgeridoohan:
I would love to, but that is unfortunately not a complete fingerprint... Take a look here on how to provide one:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint

Edit: and don't forget the security patch date...

That's got nothing to do with this module, and there's nothing I can do about it. You're likely experiencing a Magisk bug where MagiskHide will fail randomly. It's under investigation.
[Magisk] spida_singh:
Just dropped in to say thanks. Safety Net Playstore certification and UK banking app now working great on my OP6T using a custom ROM.

Great module and documentation!
[Magisk] oslo83:
Hi,

I'm maybe wrong, but it seems to me that latest magisk hide props does not support all the custom prop editing it used to...

The one beginning by ro. are still working fine ;

But not some other anymore, like:

IsShowNetworkType

hw_show_lte_lite

It's like props shown in Settings database editor's System tables tab were not working anymore with magisk hide props.

(But still do when edited in SetEdit.)
[Magisk] Didgeridoohan:
Hm... There has been no change to the actual function of the custom props option, so if it worked previously it should work now. Could you post the logs with those props active in the module?
[Magisk] oslo83:
So, it's possible that In fact I did previously

-edit these values via manually in right .xml or via Settings Editor android app.

-only then I must have add both 'invalids' and 'valids' custom props to magisk hide manager.

-then I forgot about previous editing via SetEdit of the so-called 'invalids' props and just wrongly assumed they were taken cared of.

I may remember that by that time, I may have gotten like now the prompt saying prop does not exist yet... (yes right spelled.)

Do you know the app i'm talking about:

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

I'll could still do it...
[Magisk] Didgeridoohan:
That app does something else, not covered by this module (although I have had an idea to implement that as well). What that app does is to change values in the settings database, not prop values. You can do the same in a terminal emulator by running the command "settings put" followed by what category (for example "global") followed by the setting and what value you want to assign to it. For example, if you want to enable tethering you can edit prop values, but you might also have to update the settings database, like this:

settings put global tether_dun_required 0
[Magisk] Bradco:
hello,

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

a lot lot of information at once :)

I have an elephone u pro who is certified by google I flash a custom rom (trebble) but I currently have another fingerprint and if I understand correctly I can recover the fingerprint of my device on the rom stock and injected.

three small questions:

1. how to open my rom file system.img easily to recover the fingerprint?

2. How do I inject the fingerprint with the module?

3. Is it possible to only have to do it just on time ?
[Magisk] oslo83:
Thank you very much for these precious infos.
[Magisk] oF2pks:
Just tried your latest MagiskHideProps on GSi: works fine & SafetyNet ok (ctsProfile ), [MENTION=7280276]ipdev[/MENTION] , with android 9, basically system GSi may be "recent or equal" than synced vendor/boot couple: https://source.android.com/setup/build/gsi#changes-to-keymaster-behavior

In oreo, phhusson introduced https://github.com/phhusson/device_phh_treble/commit/f1811092e681ae7b4091579adc8cf5a044077109 , which is still present in pie : https://github.com/phhusson/device_phh_treble/blob/android-9.0/rw-system.sh#L39
[Magisk] spida_singh:
Sorry for being bad news.

So, I thought everything was ok, I had enabled THE OP6T fingerprint and device emulation to achieve certification with Safety Net passing etc

But,it's stopped my Skype for business all from working, and also broke face unlock for me.

I'm using the sky dragon ROM

I'll try and grab logs and replicate later,but wanted to give a heads up.

Thanks again!
[Magisk] Didgeridoohan:
There is a method for that described in the documentation, under "Finding a certified fingerprint". If that doesn't work on your device your going to have to put your Google-Fu to the test...

Just run the props command, pick the "Edit device fingerprint" option and type in the fingerprint you want to use. Or, you can use a custom fingerprints list or a configuration file (both are covered in the documentation).

As long as you keep the module installed and active the device fingerprint will be replaced by the one you've set up at boot.

Is your ROM a GSI? In that case you can try using the new "Use vendor fingerprint" option for Treble GSI ROMs (under "Edit device fingerprint").
[Magisk] Bradco:
I will re-read the documentation several times to understand. for the rom I'm not sure , gsi I'm going to look were I find this information.

thank you for your answer I will come here to make a feedback.
[Magisk] russel5:
From latest firmwares

Sony XZ1 Compact -- Sony/G8441/G8441:8.0.0/47.1.A.12.179/1909673090:user/release-keys

Sony XZ1 Dual -- Sony/G8342/G8342:8.0.0/47.1.A.12.179/1909673090:user/release-keys
[Magisk] allrockedout:
I'm using xiaomi mi mix 2 I'm not seeing my device for certified fingerprints in terminal. I've tried mi 6 and tried other device fingerprints but not passing my play services is NOT saying uncertified and my magisk is saying ctsprofile not matching. What else should I try?

Xiaomi/chiron/chiron:8.0.0/OPR1.170623.027/8.6.4:user/release-keys
[Magisk] Didgeridoohan:
Mi, Redmi, Mix, Max... How many devices do those guys make? :laugh:

Anyway... Start by changing the boot stage to post-fs-data.

If it still doesn't work, provide the logs.
[Magisk] waylo:
Thank you [MENTION=4667597]Didgeridoohan[/MENTION] for everything you do for the Magisk community.

Just wondering, if BOTH CTSprofile and basic integrity are failing, is it likely this module could at least fix the CTSprofile? i.e. is it ever possible to have CTSprofile pass, but not basic integrity?

(Reason I'm asking is I'm trying to get Safetynet happy with my Galaxy Pro Tab running Lineage 14.1. All my searches, as well as my own attempts with this module and other variations, indicate it can't be done. But I'll be happy with an 'easy' fingerprint fix first.)
[Magisk] allrockedout:
Tried with changing boot stage still not working where is the best place to send you all my logs?