yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
If the module installed properly, and you are getting this error.

MagiskHide Props Config v5.2.4

by Didgeridoohan @ XDA Developers

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

The service.sh module script does not

appear to have run during boot.

This means the module won't work.

You are on Magisk canary 20409.

Something else is keeping the script from running on boot.

Your Magisk install is borked.

If you are on Magisk canary 20409. Revert to an earlier canary version, switch to the stable/beta version or wait for the next canary.

Magisk issue # 2781 GitHub - Link

Note.

If you run an older Magisk or the stable/beta and run "props"

Make your changes and reboot and then update to canary 20409.

No service.sh/service.d scripts will run so "props" will be broken but, post-fs still works so the changes made should still run on boot.

Without some kind of log, it just a guess in the dark. ;)

The Magisk log file should show scripts and modules starting up on boot.

There is always adb logcat or apps like SysLog and MattLog (Both from PlayStore) that you can use to get a log file.

The module log files are saved on the device, you will need root access to get them.

/data/adb/mhpc/

As always, take a look here for answers.

Scripts Did Not Run GitHub - Link

Get Logs GitHub - Link

Cheers. :cowboy;
[Magisk] ipdev:
[MENTION=4667597]Didgeridoohan[/MENTION]

Due to my prior post.

I do not have to check my mhpc logs that often, so I'm not sure when this started.

When I checked my log files, propsconf_boot_verbose.log is 0 bytes.

Figured it was because I was also running canary 20409 on that device.

Pixel 3aXL abc rom

When I checked another device (canary 20405) it also had a 0 byte boot_verbose.log

Renamed both verbose.log and verbose_last.log (also 0 bytes) and rebooted. A new propsconf_boot_verbose.log was generated but still 0 bytes.

The other logs are generating on both devices, just not the boot log.

Attached a screenshot Nexus 7 (2013) unofficial AospEXtended (Android 10).

Daily use, not a flash and fix device so, it gets rebooted and updated slowly. ;)

Completely different [rom builds, partition setup, armv7/v8, ..] devices have the same problem(symptom?) for me.

Can you check if the boot log is currently being generated correctly for you?

Cheers. :cowboy:
[Magisk] Didgeridoohan:
[MENTION=7372255]Kennytriplex[/MENTION] as [MENTION=7280276]ipdev[/MENTION] already has posted, of you're on Canary 20409 that's due to a bug in that release. Otherwise, logs will be needed...

[MENTION=7280276]ipdev[/MENTION] That's expected. The verbose boot logs haven't been generated properly since Canary 20307 when John introduced the standalone Busybox mode. It just haven't been a priority for me to find a different solution...
[Magisk] Kennytriplex:
Thanks to you both for your quick response. I failed to mention that I’m installing these on a Samsung galaxy s5 running on stock android 6 marshmallow. I was previously running magisk 20400 and magisk manager (267) and everything was running smoothly except for the issue I outlined above about the service.sh startup not working.

I have updated to magisk 20408 and magisk manager 248. Now a few functions such as all the reboot options are not working. Modules are not showing. Attempting to download and install any module whatsoever results in “zip is not a magisk module. Install failed”.

Installing a module through recovery and rebooting, the modules don’t appear or load up. No module shows in the app. Upgrading to 20409 is exact same thing. And service.sh still not working in props

Thanks again for your anticipated assistance
[Magisk] Didgeridoohan:
If you where using stable Magisk v20.4 when you where getting the "service.sh script did not run" error you are going to have to provide the logs that [MENTION=7280276]ipdev[/MENTION] was talking about, otherwise it's going to be hard to help. Did you take a look at the links he provided and the tips for your issue that can be found there?

It sounds like your Magisk installation is quite borked though, so I suggest that you uninstall and do a clean reinstall. Since there are service.sh script issues with Canary 20409 it might be a good idea to stay on the stable release for now though.
[Magisk] Kennytriplex:
I’ll take a look at those links now. And probably do a complete uninstall and/or maybe RE flash my stock rom. Then install twrp, magisk manager, and magisk in that order. I’ll update after that.
[Magisk] TheUndertaker21:
[MENTION=4667597]Didgeridoohan[/MENTION]

any update for me ? LOL

went back to stock for a bit
[Magisk] Didgeridoohan:
Sorry, with your last post I kind of figured that you considered the case kind of closed. I don't see what could be the cause in any of the info you've provided, and since it's only those ROMs that are affected it does sound like it's a ROM thing. There's at least not much more I can do at this point...

I guess I should have replied about the boot log script not running. It might be that the post-fs-data scripts simply doesn't run during the bootloop, so not much to do there. It was running fine otherwise, so you've set it up properly.

It was a good run and we did our best to figure it out I guess...
[Magisk] iamMG:
I want to use the SoundAssistant app by Samsung on my OnePlus 7 Pro. I tried using Samsung S10 Plus fingerprint but the app still doesn't work. Any help regarding this is appreciated.
[Magisk] Kennytriplex:
Ok. So after trying different options and settings, I decided to downgrade magisk to 20300. Making use of latest magisk manager 7.5.1. Everything worked perfectly. Seems there is a issue with magisk 20400 that makes it unable to run service.sh in marshmallow Samsung s5. Won’t be upgrading for now

On the side, how do I enable device simulation in props? It’s currently set at disabled right now
[Magisk] Didgeridoohan:
If it is possible you'd very likely need more than just changning the device fingerprint. Try using the Device simulation feature of the module, but it is so basic that it is far from certain to work for this purpose. Fooling the Play Store involves more than that... Have you tried APKMirror?
[Magisk] Didgeridoohan:
I would very much have appreciated if you had posted the logs, to see if there are any possible issue with the module...

Are you talking about this: https://github.com/Magisk-Modules-R...ter/README.md#an-option-is-marked-as-disabled

You need to set a fingerprint before using that function.
[Magisk] Kennytriplex:
Ok. I’ll give it a shot. Previous logs had zero bytes and couldn’t be opened. But I’ll try and see if I can get the logs
[Magisk] iamMG:
Yes, I sideloaded it from APK mirror. The app checks more than that. It is made for Samsung devices only (a summary of it: basically allows setting different volume levels for different media volume sources/apps). I have been looking for alternatives but there are literally none. I don't get how is this not a native android feature. Anyway, I tried your instructions and set Device Simulation with options (1,2,3) but still It force closes instantly.

Edit: Thanks for the quick reply.
[Magisk] Didgeridoohan:
Ok. I thought you were having problems installing it from Play store.

You could grab a logcat when the app crashes. That might give a hint as to what's going on.
[Magisk] iamMG:
I saved a logcat. I hope this helps.
[Magisk] hamsteyr:
Getting a strange issue where I cannot run props in termux, it says command not found.

Thing is that when I used to use crdroid on my Poco it worked fine, but doing the exact thing in Lineage 17.1 give me a command not found.

Have got busybox (osmosis) installed, 5.2.4 of the script installed and tried rebooting multiple times to try and figure it out to no avail. Made sure I'm not on core only mode as well.

Anyone can shed some light on this?

Edit: disregard. Silly me forgot to SU. ?
[Magisk] Didgeridoohan:
And you've run su before the props command?

Personally I don't like using Termux for this simple stuff, since it sometimes seems to display these kind of quirks. On the other hand, plain old Terminal Emulator always seems to work...

Edit: Ah... Just noticed your edit. :good:
[Magisk] hamsteyr:
Yeah sorry bout that, I derped. I always used Terminal Emulator, and so I didn't realise that you needed to Su before until I scrounged the documentation.

It works fine now! Thanks!
[Magisk] TheJoker71:
How did you manage to pass cts in pocof1 with android 10?... Previously i sont hve issue with cts... But now when i upgraded to android 10 i cannot pass cts with pocof1...
[Magisk] Didgeridoohan:
You're going to have to be a bit more detailed... Are you saying that CTS fails even if you set the device fingerprint to a Poco F1 Android 10 print, or that you generally can't pass CTS on a Poco F1 with Android 10?

If it's the former:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check

And if it's the latter:

https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet

But first of all, have you made sure that MagiskHide is enabled (and toggled it off and on again if it is)?
[Magisk] TheJoker71:
Hi... Thanks for reply... very sorry... I manage to pass cts now in pocof1... But i need to use magisk20.3... the 20.4 latest version cannot pass cts... Thank so much for this wonderful module of yours...
[Magisk] Didgeridoohan:
That was your first post, so you can't... I think it's a 10 post minimum before you can post links or attach files.

You could upload it somewhere (cloud or sharing service) and point us to the location.
[Magisk] Didgeridoohan:
[MENTION=5984070]kullurumanoj[/MENTION] Ok. Here's the last attempt to see if the issue can be fixed by changing prop values. A couple of them might be relevant, and a couple of them are just in there because you never know... Put the configuration file in /cache, remove the .txt extension, reboot and it'll change the fingerprint and some more props. I've also set it to run in post-fs-data by default, for the best chance of success. Let's cross our fingers and see how it goes. I'm more and more leaning towards it being something that can be improved upon on the Magisk side though. I'll see if I can sit down and analyse that later...
[Magisk] Seagold:
Please add Samsung Galaxy J200H 3G DUAL SIM, Stock ROM 5.1.1

J200HXXU0AQK2
[Magisk] Didgeridoohan:
I'm going to need someone to provide a working fingerprint before I can do that.
[Magisk] Seagold:
How do i resolve this...
[Magisk] kullurumanoj:
Still no luck man...you have done everything what can you do..I have attached the logs..Thanks a ton..I will find something better for you
[Magisk] a tiny ant:
Hello, first of all thanks for your work.

The module doesn't work at all for me. After installing it and opening a terminal followed by "su" and "props" I get the following message:

"The service.d boot script did not run during boot".

This error message appears on all variations of the props command, like props -h or props -s. It doesn't seem to recognize any modifiers.

Edit: removed the logs
[Magisk] Didgeridoohan:
https://github.com/Magisk-Modules-R...EADME.md#i-cant-pass-the-basicintegrity-check

Something's wrong, obviously... That log package seems broken, so if you could collect the logs manually and post them here I can take a look at what the issue is. XDA attachments seems to be broken, that's why... I'll take a look at the logs when that's been fixed...
[Magisk] a tiny ant:
Post no longer necessary.
[Magisk] Nathan2004:
Hello this is the newest fingerprint from MIUI 9.6.1.0 for scorpio

The fingerprint :

BUILD_FINGERPRINT :=

Xiaomi/scorpio/scorpio:8.0.0/OPR1.170623.032/V9.6.1.0.OADCNFD:user/release-keys
[Magisk] Seagold:
- Copying zip to temp directory

- Installing universal-safetynet-fix-v2-beta-5.zip

update-binary: line 148: /sepolicy-inject: not found

Archive: /data/data/com.topjohnwu.magisk/cache/install.zip

inflating: config.sh

update-binary: source: line 170: config.sh: not found

Failed!

! Installation failed

Added: OP asked me to share this.

Thanks.
[Magisk] jenslody:
You are in the wrong thread: "Universal SafetynetFix" != "MagiskHide Props Config".
[Magisk] j1gga84:
Is the module also for setting basicIntegrity from false to true?

ctsProfile shows true on my side, only basicIntegrity is false :confused:

regards
[Magisk] a tiny ant:
I found the reason! I have my phone encrypted along with requiring pattern for startup. Disabling the secure boot option fixed the issue and allowed the script to run properly. I didn't have to decrypt it.
[Magisk] Didgeridoohan:
If you have ctsProfile = true and basicIntegrity = false, that means you're using Xposed and the "No Device Check" Xposed module.

Xposed cannot be hidden.

That's great, that you got it figured out. But I would have liked to see those logs, to see if there was anything I could have done about it for future versions.

I have both an encrypted device and a pattern set for startup and have zero such issues...
[Magisk] a tiny ant:
Right, here you are then. Thought I'd remove unnecessary things from the thread.
[Magisk] Didgeridoohan:
Thank you. It wasn't a module issue, but rather a Magisk issue. The late_start service was trying to run before anything else, and that's not going to work... I'm assuming you reinstalled Magisk as a part of removing encryption. If so, that probably fixed it..
[Magisk] mayanxoni:
My device was failing the ctsProfile check but passing the basicIntegrity check. It finally solved the problem and worked on my Redmi 5(Rosy) after changing the device fingerprint to Redmi Note 5(5 Plus).

Thanks for an amazing hack!
[Magisk] anaandshailu:
I can't run the props command
[Magisk] begin_android:
thanks to developer

i tried this module on device Mi Max 2/Oxygen. based on MIUI 10 V8.7.12

but nothing change. based on this module, ro.build.fingerprint based on miui 9 global v9.5.4.0

thanks
[Magisk] Didgeridoohan:
Did you make sure to enable MagiskHide on v20.4? From that release Hide is disabled by default, so if you did a clean install it wouldn't be active. Once you installed Magisk v20.3 MagiskHide would activate again.
[Magisk] TheJoker71:
Yes... It was enabled... There were a check mark both the busybox and magiskhide under settings/module... Any other sign it was disabled?
[Magisk] clonechill:
Will the fix stick, even if magisk is uninstalled?
[Magisk] Didgeridoohan:
Busybox? That has nothing to do with MagiskHide. Are you talking about this module being enabled? I mean the MagiskHide toggle in the Manager settings.
[Magisk] Didgeridoohan:
No. You would have to do old-fashioned direct edits of build.prop for things to stick without Magisk installed.
[Magisk] clonechill:
Thank you. Yes I want to do that. Is there a tutorial for the old way?
[Magisk] ipdev:
Quick update for Pocophone F1.

Cheers. :cowboy:
[Magisk] ipdev:
You could check in your device forum if there is a guide specifically for the device.

Otherwise read though this one, little old but still active.

[Guide]ChangeDeviceModelExtraStepxdaThread - Link

It should give you a good idea of what needs to be done.

Keep in mind, you might end up breaking permissions and/or securities.

The reason to see if there is a guide related to the device.

Hope it helps.

Cheers. :cowboy:
[Magisk] BeeJ1109:
Why default disable in v20.4 and not v20.3

Would it be better to default enable in v20.5 If it causes issues. Switch off easy to toggle .

I'm Still having issues to save the setting, when toggle off to on. Then restart again, setting still is again off. So any toggle only lasts, while active. Therefore useless option.

A reboot is used to restore any faults. Power OFF and then ON, is A Master Reset to fix loops and other effects.

Common fix for ALL Bug Riddled Software. Gets things back to a common start point and work on to analyse the fault.

"Technician's Fault Finding Technique 101".
[Magisk] Didgeridoohan:
MagiskHide is disabled by default from Magisk v20.4 because John decided that's the way he wants it to be (and it's unlikely to change). Mainly got to do with Google's soon™ to be activated (probably, but of course nobody really knows when and even if) key attestation check that will make it impossible to pass SafetyNet on many devices. The feature is disabled by default to possibly reduce the expectations of it being a magical fix for passing CTS (once Google flicks the switch it won't be).

Regarding the other part of your post, that sounds like you are describing a bug that some users experience, where MagiskHide has to be toggled after a reboot to start working. As far as I know no-one has been able to show why it actually happens, or provide any useful information to troubleshoot. If I had to guess I would say it's probably caused by buggy implementations by OEMs not following Android standards...

If you don't feel like helping in trying to figure it out, you can easily work around this bug by using a boot script or automation app to run this at boot:

magiskhide disable
magiskhide enable

If you'd like to follow up on this conversation I would like to ask you to continue it in the general Magisk support thread (just tag me), since it doesn't really have anything do to with this thread.
[Magisk] th3legend:
Stuck on boot with lineage

Found some logs...looks like it crashess which causes the phone to stuck on boot looping the logo

Samsung galaxy a20 on lineageos android 9

Happens when I enter the finger print and the security patch of my device.... It worked before the magiskpropsconfig was upgraded last month.

I'm gonna try tweaking things but already tried different start options

Edit

So I tried late service late service and at least it doesn't boot loop logo ...still have fail though for safetynet check....attached config screencap

Will see what else I can try...
[Magisk] Didgeridoohan:
There's been a couple of reports about this on GSIs recently, but I still haven't managed to figure out what it could be (I don't have any devices that can run a GSI).

Could you run a test for me? Disable the module and put the attached file in /data/adb/post-fs-data.d (and don't forget to give it execution permissions). That way we can at least determine if it's the module or the act of setting the fingerprint that messes things up...
[Magisk] th3legend:
For sure...I don't know the service that well...I assume it reads that that text file in...attached screenshot of permissions and Dir and catted it....I disabled props module and rebooted...no boot logo loop there....I assume it read the mhpc.txt properly and has the appropriate fingerprint

Thanks!
[Magisk] Didgeridoohan:
Thank you. That's quite helpful. I'm assuming that SafetyNet now passes, or?

Before I start working on things, could you remove the boot script and enable the module again. Set a fingerprint again with all other settings to the default, but before that change one script setting (option 6 in the main menu). Enable the "Background boot script" option and see if that makes things work.
[Magisk] HannibalLecter:
HDFC PAYZAPP suddenly stopped working today. It says cant work on this device because of an error.

Safety net is passing and device is certified. still not working.

It worked just a week or so before when i paid a bill.

Tried today and suddenly poof.

Anybody can try using Payzapp and confirm?
[Magisk] Didgeridoohan:
You are in the wrong thread... Take a look here and then post in there Magisk General support thread if you need further help:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] th3legend:
Actually it doesn't pass, but pogo works....I tried the basic stuff that might help like clear cache and storage on play store and services and deleted things in sdcard that might flag something like folder called twrp and stuff called magisk....also pogo with the late late service enabled and that txt file removed as well works too...even though safteynet shows still false. I'll continue to work on that though....and I will get back to you soon on that background script settings and see if I can get it to boot without hanging with defaults.

Thanks again!
[Magisk] Didgeridoohan:
Thanks for testing stuff.

Meanwhile, I tested the print you've used, as well as the one from the ROM and neither of them pass CTS.

I took this from AndroidDumps though, and it passes:

samsung/a20cs/a20:9/PPR1.180610.011/A205WVLU3ASK2:user/release-keys

Patch: 2019-11-01

I'll add that to the next prints list update.
[Magisk] th3legend:
Strange the print I grabbed was from stock at the time I think there was an update since then to the stock firmware.maybe that has something to do with it....I tried that new one in late /late service modes and it still shows ctsfalse...I'll reset play and stuff again though to see if that helps...

Before that I reset to defaults and tried to enable background bootscripts and then set the fingerprint previously and I got a boot logo loop again.
[Magisk] TheJoker71:
What.?... So it means i dont need to install busybox? So why ur installer reminds me to install busybox and even suggest which one to download and install? Ever since i use ur magiskhide always reminds to install busybox... So i can uninstall busybox now?
[Magisk] Didgeridoohan:
This module (MagiskHide Props Config) needs Busybox, yes. Magiskhide, the internal function of Magisk that hides Magisk and it's modules from apps and services does not. You need to keep the two separate.

When I asked you to check if MagiskHide is enabled I was talking about the Magisk function, not the module.
[Magisk] petyauser99:
Could you please update props for redmi note 7?

It's out of date and not passes cts
[Magisk] Didgeridoohan:
I just tested and can confirm that the fingerprint for the Xiaomi Redmi Note 7 passes SafetyNet perfectly fine.

Certified fingerprints do not go out of date (but in extreme cases, Google can of course change that certified state). If you can't pass CTS you probably have something else going on, it's unlikely to be the fingerprint (considering that confirmed it works).

Edit: Oh yeah... There's also this:

https://github.com/Magisk-Modules-R.../master/README.md#please-update-fingerprint-x
[Magisk] Reznor7:
GSI Bootloop

Just wanted to let you know that with today's update, I still get a bootloop on Havoc 3.5 GSI after enabling a fingerprint. Please let me know if there's anything I can do to help.
[Magisk] Didgeridoohan:
Update? To Havoc? Cause there's been no update to the module. I've tweaked the docs a bit, so GitHub would show that there has been changes made. But unless the version number changes, there's nothing new to the actual module.

So far I have no idea what's going on with the GSIs. To have the least chance of figuring things out I would need more detailed information and logs (but even that's no guarantee since it's not my area of knowledge). Between other real life obligations I've worked a bit on a module update with better logging, but it'll be a few days yet (at least) until I have time to finish that.

If you've got the inclination, grabbing module logs and a boot log from when the module causes the bootloop using the current Canary release (20411+) would be helpful.
[Magisk] TheUndertaker21:
I did something today

I manually changed build props and it boots up fine

But would bootloop if we change anything with magisk props

Others should provide logs since I was unable to