yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
This is not the module you are looking for. :cool:

If you can pass both SafetyNet checks and only want to change SELinux to permissive, there's nothing this module can do for you.

Create a file in /data/adb/service.d, name it selinux.sh and put this inside it:

#!/system/bin/sh
setenforce 0

Lastly give it execution permission (chmod 755) and reboot.
[Magisk] martyfender:
Or you could do as I do on one of my 4 devices and use the App, SeLinux Switch and check it apply on boot setting. I don't really need an Selinux device that is permissive, but I have several reasons why I test it on this one device only, which I won't get into, since it is off topic in this thread so sorry to further the OT, D.
[Magisk] JarlPenguin:
Another update for Moto G5S build fingerprint:

motorola/montana/montana:8.1.0/OPPS28.65-37-7-11/7f8a6:user/release-keys

Security patch: 2019-08-01
[Magisk] MartinRK:
Hello! I got an installation error, and no reason shows. Could you please help me figure it out? Just updated to magisk 20 and flashed props config.
[Magisk] Didgeridoohan:
The reason is likely shown if you save the log (top right corner). If you post that I can help you.
[Magisk] DjDiabolik:
Lol wait.. There's a misunderstanding ;)

My problems / little issue it's not related the SafetyNet check. I know i need to change the selinux mode to pass the both check.

My current problems it's about the installation of last version of google chrome browser. On my current tugapowers playstore say to me my device it's not compatible and someone as suggest to me i need to change my fingerprint and cited this module... It's correct?

Sorry for my bad English.. It's probably this the cause of this misunderstanding....
[Magisk] Didgeridoohan:
I actually have no idea if changing the device fingerprint will help with that... But worth a shot I guess.

After you've run the props command you pick the "Edit device fingerprint" and then pick a print of your choice from the included list of certified prints.

If that doesn't work you might have luck with the "Device simulation" feature, but be warned that it is known to cause all kinds of issues on some devices.
[Magisk] MartinRK:
This is the log file.
[Magisk] Didgeridoohan:
Thanks. That's a known issue related to SAR rather than Magisk. I'm hoping to have an update out soon, since more and more users are reporting about this.
[Magisk] sidagg:
Not able to activate Google device app permission to appon this screen. Activate this device admin app button not able to select.
[Magisk] jenslody:
I had the same issue with another app.

After a long time of searching, I found the cause: the app was installed in external/adoptable storage, after moving it to internal, I could use it as admin app.

In short: checking whether it's installed in internal storage is worth a try.
[Magisk] kaisar11:
safetynet passes via magisk manager but another app fails

my safetynet passes via magisk and another app fails

play store is certified but still tez app does not pass

i hide root for tez also

but still not passing tez security

i don't know what could be the possible cause for that

please help
[Magisk] Didgeridoohan:
I'm currently at a loss as to what could be the issue with the China beta. If you could get me the same logs from a Global ROM, I might be able to make some comparisons...

There seems to be something wrong with the SafteyNet checker from Free Android Tools. All other SafetyNet apps report a passed SN...

With Tez, they've found that you'll need to revoke phone permissions from Google Play Services when you want to use the app.

https://xdaforums.com/apps/magisk/tez-app-custom-rom-root-device-t3722018
[Magisk] slimdick:
del
[Magisk] Didgeridoohan:
Ha ha... I was just gonna drop in and ask if you had actually tested that fingerprint, because I could not get my device to pass the CTS check with it. I guess you had come to the same conclusion. :D
[Magisk] slimdick:
I have just checked and it does not work, there must be a Stable Global version, the one from the CN does not work. :o
[Magisk] Adamask:
Someone can explain to me the difference between this two fingerprints?

Thanks

MagiskHide Props Config v2.3.0

by Didgeridoohan @ XDA Developers

=====================================

Edit fingerprint

=====================================

Currently set to:

motorola/montana/montana:7.1.1/NPPS26.102-49-8/6:user/release-keys

The original value is:

motorola/montana_retail/montana:7.1.1/NPPS26.102-49-8/6:user/release-keys

Enter the new fingerprint or

pick from the options below.

f - Pick a certified fingerprint

b - Go back.

See the module readme or the

support thread @ XDA for details.

Enter 'e' to exit:
[Magisk] Didgeridoohan:
motorola/montana_retail/montana:7.1.1/NPPS26.102-49-8/6:user/release-keys
[Magisk] Adamask:
Thanks. OP can update Moto G5S fingerprint with this information?
[Magisk] kullurumanoj:
Heyy man [MENTION=4667597]Didgeridoohan[/MENTION]

It took almost 3-4hrs to take backup,install and again restore and finally got logs for you attached both global and china logs...hope you could find something

Thanks

Manoj
[Magisk] Didgeridoohan:
Oh man... With that kind of effort I really hope I can find something in there. You'll have to wait a bit though, since I'm flying to the other side of the world in 6 hours (which reminds me, I need to get some sleep), and won't be back home for another 3 weeks, at least. I'll take a look as soon as possible.
[Magisk] allrockedout:
The same thing happened to me on miui 10 China rom. Once I switched to miui 10 global it's working fine. Does your device have global rom yet?
[Magisk] Didgeridoohan:
It is very possible that Google is looking at something extra in the Chinese ROMs, so that they won't pass the certification check.

[MENTION=5984070]kullurumanoj[/MENTION] You can actually take a look at the files yourself (like I said, I won't have much time or opportunity in the next few weeks), and try to compare the different props between the global and Chinese ROMs. If they're looking at some extra prop besides the fingerprint, you can start experimenting with different props from the global ROM on the Chinese one. Use the custom prop function of the module to set new props.
[Magisk] kullurumanoj:
[MENTION=4667597]Didgeridoohan[/MENTION] Yahh sure man...have a great journey, indeed you have done a great job in creating this module..will wait for your help..if we can't figure it ourselves

Thanks

Manoj

---------- Post added at 06:38 AM ---------- Previous post was at 06:29 AM ----------

Noo I have moved to chinese rom again..just for testing I have installed global rom
[Magisk] jbliz:
Unable to use MagiskHide

I accidentally reset the setting, it was first time use this tools. Uninstall Magisk, Magisk Manager and MagiskHide Prop Config then re-install them all this problem still occurs.

Please help me to solve this.

Edit :

I found the solution. I just change busybox permission.
[Magisk] lazostat:
When do you say fingerprint what do you mean and where do i find it? I try to pass the test on lg g4 and lenovo tab2 a10-70 but i cant.. I install this modue still i get a false status.
[Magisk] FPRSergio:
Samsung Galaxy J3 (2016)

ro.build.fingerprint=samsung/j3xnltexx/j3xnlte:5.1.1/LMY47V/J320FNXXU0ARB1:user/release-keys
[Magisk] Fahrilubis:
[MENTION=4667597]Didgeridoohan[/MENTION] already instal ur module but stil cantl see netflix then uncertified status?
[Magisk] Didgeridoohan:
Ok... Small support post. Don't have much time while out traveling...

Do you mean that the internal busybox hadn't been given execution permissions (755)? That's not good... Could you provide the logs (run the "Collect logs" option and post the resulting file)?

The devices fingerprint is a prop value that is used to identify it. If you're having issues, check out the documentation for tips on what to do.

Clear data for the Play Store. More here:

https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up
[Magisk] jbliz:
busybox permission

No, I believe reset all options/settings on my phone somehow change busybox permission to 644. Reboot not solved and almost whole day I google it for solutions.

After post in here I take a look on screenshot again. Luckly Material Terminal app show information about busybox can't get permission to execute command. So I had change permission to 755 by manually and it worked.
[Magisk] Landrea:
[MENTION=4667597]Didgeridoohan[/MENTION] thank you for your hard work!

Sorry to bother you but I have a small issue: I'm on a Honor 6x, with custom rom "crdroid", so my phone says "Huawei P9 Lite" in infos...

Btw, I pass "basicintegrity: true" but not "ctsProfile: false", so i looked around and found your module.

I wanted to play "Pokemon go" (no shame here)......

I run your script and set fingerprint for Huawei P9 (i don't know why), somehow ctsProfile was true, Pokemon go worked for some minutes but then stopped again.

So i run the "r" command, to reset everything and start from the beginning (I was going to look for a better fingerprint). It gave me some error (couldn't read). Now the ctsProfile is false, but your script doesn't run anymore. I even tried to uninstall your module, then Magisk with Magisk uninstaller and reinstall, but still says the module is not running.

On the bright side, Pokemon go is now working, eith ctsProfile: false.

But I'm afraid I might have done some damages with installing/uninstalling your script, that at the moment I can't run.

I looked for logs (cache, data...) but I didn't find them and i can't "collect logs" because I can't run the script....

thank you all!
[Magisk] Didgeridoohan:
I actually can't reproduce any of those... I'm going to need more details.
[Magisk] DaveX2012:
What about v20 will this work?
[Magisk] Didgeridoohan:
Magisk v20 shouldn't be an issue. But some SAR devices might have problems with installing the current module release (/cache isn't write-able)... I'm in the middle of polishing and testing the next release though, where that will be fixed.
[Magisk] ipdev:
The world of Xiaomi is a little odd. ;)

If the device is unlocked, you can flash the Official Global version.

Along as it's an official build, it would be genuine.

The Mi 9 Lite fingerprint and date you posted are correct.

I pulled the recovery/prop.default from the official global to compare.

SafetyNet passed on the two devices I tried it on.

Sorry to add to the todo list. :o

Some current fingerprint(s) for the list.

Essential PH-1, OnePlus 6T, Pixel(s), Poco F1 and Mi 9 Lite.

Cheers all. :cowboy:
[Magisk] martyfender:
I just purchased an Onn 8 tablet from Walmart. I used mtk-su temp root to backup the stock boot and patched it with the latest Magisk Canary build. It has Android 9 on it. I installed MagiskHide Props Config.

I get: The service.sh module script does not appear to have run during boot.

The only modules I have installed are the busybox ndk, App Systemizer (terminal Emulator) the systemless hosts.

The only reason I installed the module was because I was passing safetynet in MM, but failing playstore certification. I have since fixed that by deleting data in the playstore. I can remove it, but I am just curious why it is not working. Is it the bug you will be fixing in the next release?

And, of course, I almost knew for certain how to fix the playstore certification issue, but I can't resist testing your great module.

Attached are the logs.

Thanks
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] The late_start service boot is running too early. Could be because of the module, or something about your Magisk installation. Seeing a Magisk log without the module installed might shed some light on which it is...
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] The late_start service boot stage is running too early. Could be because of the module, or something about your Magisk installation. Seeing a Magisk log without the module installed might shed some light on which it is...
[Magisk] martyfender:
Attached log is after uninstalling the module and rebooting.

Thanks
[Magisk] Didgeridoohan:
The same... Here's from the log:

The late_start service mode should run just before boot is completed, not this early. Your Magisk install seems to be broken so a reinstall might be in order...
[Magisk] martyfender:
I installed Magisk on the new device by patching the dumped stock boot.img with the latest Magisk Canary Magisk Manager. I flashed that patched img in fastboot. Upon rebooting and opening MM, I got the message that additional setup is needed. I approved that and it succeeded, as far as I know. I got no failed message like I got with the stable v20. [MENTION=4470081]topjohnwu[/MENTION] did a WIP in MM on Canary for Android 9 for this problem. But, as he stated, it is a WIP.

How should reinstall Magisk this time?. Also I believe I did one Canary update using the direct install method, but can't remember for sure.

Thanks
[Magisk] Didgeridoohan:
Don't know... All I know, from the log, is that the Magisk boot process is broken on your device. And similar reports have been fixed by reinstalling.
[Magisk] martyfender:
I tried patching a stock boot.img again in MM and flashing it again in fastboot and that still did not solve the problem. I haven't yet tried to totally uninstall Magisk and starting over. Will using the uninstall in MM be enough and maybe reflashing the stock boot.img. Since I don't have twrp for this device, I don't want to mess it up. Especially since I don't have a system backup. backing up system on this device is difficult.

Thanks
[Magisk] aseferfan:
So, are the fingerprints added? I wanted to select the mi 9 lite fingerprint, but couldn't find it in certified fingerprints list
[Magisk] @rafaelreis:
Fingerprint certifield moto z play?

[MENTION=4667597]Didgeridoohan[/MENTION] is it possible to include moto z play XT-1635-02 stable ROM 8.0 certified fingerprint?

motorola/addison/addison:8.0.0/OPNS27.76-12-22-9/10:user/release-keys

Excuse me if I put something wrong.
[Magisk] ipdev:
When [MENTION=4667597]Didgeridoohan[/MENTION] can find the time, the updated/new fingerprints will be checked and added to the official list.

In the meantime, you can use a custom finger print instead. There are a few ways to do it.

Magisk Hide Props Config ReadMe/Instructions

- Please Update Fingerprint Link

- Custom Fingerprint List Link

- Configuration File Link

The list I attached is in the custom fingerprint list format. If you wan to use it, read the custom fingerprint list link above for instructions.

Cheers. :)
[Magisk] ipdev:
Just need the corresponding security date to test/use it. ;)

If you are running the rom, you can grab it with adb shell or a terminal app.

getprop ro.build.version.security_patch

or

getprop | grep ro.build

(This will display all ro.build.** values.)

Otherwise, you can find it in the one of the prop files.

(system/vendor)build.prop, default.prop, prop.default or the updater scripts.

Cheers.:cowboy:
[Magisk] jenslody:
The second issue might be related to the used terminal (-emulator).

Which one do you use, or if you do it via adb shell, which os/terminal-emulator do you use to run the command?

And which locale/language is used?
[Magisk] martyfender:
Should I try backing up /data/adb, deleting it and reboot, since repatching and reflashing the patched Magisk boot.img didn't solve it? Or could this really mess up the device? I did dd backups of system, boot and recovery, but certainly not all of the many Android partitions of this device, since it has no stock img or twrp.

I have already returned one device I bricked, by trying to flash the onn 8 thread creator's backup images. I suspect his backups were from an older rom revision, since with his magisk patched boot.img, I lost wifi and other. this same issue was present on my 5 Nextbook devices with different rom revisions. the boot.imgs had to be paired with the same rom version or one would loose wifi, bluetooth, etc. And this was on 5 devices with the same Android version, same processor and same kernel version. A user on my thread indicated that there may have been minor hardware changes also between versions to account for this. Intel firmware was different between versions, also, or IFWI (Intel Firmware Interface).

When I backed up and patched the new tablet images, they worked fine as far as I know except for this late start problem.
[Magisk] Didgeridoohan:
[MENTION=5263982]aseferfan[/MENTION] and [MENTION=9785665]@rafaelreis[/MENTION], you already have your answers from the always helpful [MENTION=7280276]ipdev[/MENTION]. I'm pretty far along the way to pushing the new update out there, but school and life in general outside of XDA is breaking my back right now. Got two exams coming up in the next couple of weeks, but after that things will lighten up a bit. If nothing else I might try to at least get a new fingerprint list out there before that.

[MENTION=8126387]martyfender[/MENTION] Deleting the Magisk files could work. Other than that, a full uninstall and reinstall might be the only way to fix things.
[Magisk] martyfender:
Yes, I backed up and deleted /data/adb and I was afraid I really messed up the device, because when I launched MM, additional setup failed. Uninstalling MM only and reinstalling it, only fixed that. unfortunately, reinstalling the module after that did not fix the problem. The only way I know how to unistall Magisk is to delete the data and reflash the stock boot.img I had not deleted the other data files that Magisk and Magisk Manager created. before trying to redo this, just /data/adb. I'm just not sure that the other data files would have caused this issue. Does this issue also effect post-fs-data.d scripts or service.d scripts, if you have any idea, are they at a different stage than that late start service? I guess I really need to re-read topjohn and your documentation.
[Magisk] Didgeridoohan:
If the late_start service mode runs to early it will affect all service.d and module service.sh scripts.

About uninstalling, have you tried running the complete uninstall options from the Manager? If I remember correctly, even when you use the patch boot image option when installing a copy of the stock boot image should be saved in /data.

You probably have to start competely from scratch, patch the boot image again and everything.
[Magisk] jahidinbedod:
[MENTION=4667597]Didgeridoohan[/MENTION]

bro please update fp oneplus 5 from OOS 9.0.9

ro.system.build.fingerprint=OnePlus/OnePlus5/OnePlus5:9/PKQ1.180716.001/1910081949:user/release-keys
[Magisk] chooks06:
Stay focused mate!

All the best for the exams!
[Magisk] martyfender:
I have yet to try the MM full uninstall option and restoring the stock boot.img to see if that help with the previously mentioned problem. I'm a little afraid to go back to stock boot, even though I although the encrypted device booted fine after unlocking, before flashing the Magisk patched boot.img.

Last night before I removed MHPC, I installed one of my favorite apps, Apps2SD.

upon rebooting received the message that the 2nd, ext partition could not be mounted In the app settings, Set su.d/post-fs-data.d/service.d path to:

/data/adb/service.d.

The second partition was not being mounted because that script was not being run at boot. I placed another known good script in that folder, also to test and neither of them ran at boot.

I had a hunch so I uninstalled MHPC every subsequent reboots, the scripts in that service.d folder run, as usual, same at my old devices. At least on that broken Magisk install, if it is, MHPC blocks those scripts from running

I guess I need to take the plunge and totally remove Magisk, as you suggested and test again. I hope that doen't require a full factory reset, though. If needed, though, I am willing to give it a try. I just wish this device had twrp.

I do not like mtk spflashtool as I had many issues with it in the past with an older device.

Thanks and good luck on your exams!
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] Thanks.

It would be interesting to see the Magisk log with and without MHPC.... And the module log from the boot when it is active.
[Magisk] martyfender:
Where is the module log? is that not taken with the zip logs I provided? I can certainly provide the magisk.logs.

The first magisk.log I am attaching is without your module. The second is with your module. And again Apps2SD's 2nd ext2 partition was not mounted.

I realize that on Android 9 I don't need the udsbypass script, but it was the only script I had available on my old devices to test at this time. I will be removing it. It certainly is useful on my older, Android 6.0.1 tablets, though. With it, Rootbeer Fresh passed all checks, without it does not.

I will keep your module installed until I here from you about the module log from the boot. I am assuming that it is not in the propslogs.tar.gz I already provided you. A few hours ago I was re-reading your documentation, especially concerning boot stages. but it still leaves me uncertain what the difference is between late start service.sh vs post-fs-data.d and service.d

Thank You for all of your great contributions on xda!
[Magisk] Didgeridoohan:
Thanks [MENTION=8126387]martyfender[/MENTION]. No need to keep the module installed, since it really does look like the module post-fs-data.sh script is causing your issue (but not the last time you had disabled the module, weird). Anyway, I have some data to look at and can at least make an attempt to figure it out (when there's time).

The late_start service mode is when the service.d (general boot scripts) and service.sh (module specific) scripts run. The general scripts run first and then all the module scripts, and it's the same for the post-fs-data mode.

[MENTION=4470081]topjohnwu[/MENTION] has a quick summary of the boot process here:

https://topjohnwu.github.io/Magisk/details.html#magisk-booting-process
[Magisk] martyfender:
When I removed your module last night and rebooted, the Apps2SD script in /data/adb/service.d once again, apparently did not run, because I got the popup on reboot that the 2nd partition was not mounted. After posting my initial magisk.logs to you, I added your logcat boot script to /data/adb/post-fs-data.d. In addition, I still had the udsbypass script in /data/adb/service.d.

I removed both of them and rebooted, and all was well again. I suspect the logcat boot script was blocking the running of the Apps2SD script, for some reason. Is that possible? I could change the path the Apps2SD script to /data/adb/post-fs-data.d. That I believe was the original location, but some users on the Apps2SD xda forum recommended changing it to /data/adb/service.d to solve the issue of the second partition not being mounted message. That seemed to work for me on my older device. The other thing I forgot to mention is that I have both Kernel Adiutor and Lspeed apply on boot settings that run at boot, but don't create Magisk scripts. They however have never caused problems in the past that I am aware of. Also, see my latest post in the Magisk Canary thread of a potential issue. Sorry, I guess it is now getting off topic here.

Thanks
[Magisk] chooks06:
I feel that's the way this forum is supposed to be so I'd say you're still on topic.

Though the technical details is way beyond what I can understand, I see a detailed "fault finding" procedure, trying to establish/eliminate possible cause of the symptom.

And you've been a great help to many in this forum. I've learnt some things and more just reading.. Thanks mate!

Have a great weekend!

Cheers!
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] The logcat boot script from my guide runs in a subshell, so it shouldn't (in theory) affect much at all.

What it seems like is that post-fs-data boot scripts can somehow "overwhelm" the boot process (if that's possible)...

I'm really not sure. I'd still like to see if a clean install of Magisk, completely from scratch would make any difference. But, I know how daunting such a task can be, so don't sweat it if you're not up to it.