yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Sorry... I didn't think that question through. The v4.0.3 release of the module can't actually show colours on Magisk v20+, so it was kind of redundant.

On the affected device, what's the output of the following command (I'm expecting "screen"):

echo $TERM

And try changing the "Terminal type" in the app preferences to one that has "colour" in it's name (should be a "screen-256color" option). That might help.
[Magisk] OhioYJ:
screen-256color

Terminal type is set to screen, I checked my other devices they are set the same as well. Actually changing it to screen-256 doesn't change anything.
[Magisk] Didgeridoohan:
Weird... I'll see if I can find anything about it, but meanwhile you can do a couple of things. Try a different terminal emulator or simply disable script colours by running props with the -nc option or going to script settings and disable colours.
[Magisk] akhil17kr:
how do i reset fingerptint values to default ? i am using zenofone max pro m1 running on havoc pie, i used zenfone max pro m1 8.1.0 verified fingerpint to pass safetynet but it still didn't passed and now i am having error related to "your vendor image does not match" , i already uninstalled the module by going into terminal and input option to clear and reset all settings .

what are the correct steps to fix ?
[Magisk] Didgeridoohan:
If you've reset the module and rebooted there are no longer any modifications being done. If so you've got something else going on... You could upload the module and Magisk logs for me to look at.
[Magisk] jcmm11:
Your ROM should have a vendor image that goes along with it. Make sure that's the vendor you have installed
[Magisk] Didgeridoohan:
[MENTION=4288094]akhil17kr[/MENTION] and [MENTION=4487388]jcmm11[/MENTION]

That error will also arise if you only change ro.build.fingerprint and not ro.vendor.build.fingerprint. from v5.0.0 the module scripts won't edit a prop that doesn't already exist on the device. If that detection somehow failed on [MENTION=4288094]akhil17kr[/MENTION]'s device and the vendor print wasn't changed to match, we might have part of the answer.

Would have to see the logs to know more though...
[Magisk] bigjailerman:
So what commands are needed to change fingerprints in terminal..I have forgotten initial commands to bring up the choices.

Thank you
[Magisk] casouzaj:
Enter command props in any terminal emulator app. Then, select options 1 > f > maker > model > y > y. After your phone reboots, check if Saferynet's CTS profile test now passes.
[Magisk] ipdev:
I know some of these fingerprints have already been supplied by others.

Good work everyone. :D

Looks like Pixel and Pixel XL are officially done.

No more Sailfish and Marlin.

Guess we'll have to add flame and coral. :rolleyes:

Essential: PH1

OnePlus: 6, 6T, 7Pro, 7NR, 7T

Pixel(s): 2, 3, 3a, 4

Xiaomi: Mi 9 Lite, Poco F1

Note:

Fairphone FP2.

Passed on my Nexus 5 and 7.

Failed on my OnePlus 6T and Pixel 3aXL.

I give up for now.

Seems like it's a free-for-all right now, especially with SAR/Android 10.

Google, Magisk, ....

Cheers. :cowboy:
[Magisk] TrafalgarD:
Please add support for xperia Z5 premium single (E6853) satsuki
[Magisk] milan*SK:
Oneplus 3 anyone? 3T is not working for me
[Magisk] alponso:
Could you please share your cmd to change the permission. I also faced same problem after reset then reinstalling this module.
[Magisk] Didgeridoohan:
[MENTION=5628119]jbliz[/MENTION] [MENTION=3669620]alponso[/MENTION]

Could you guys share the exact steps you took for the issue to manifest? I'm out traveling for a few weeks and don't have much opportunity to troubleshoot and test. But, if I know what's wrong it might be an easy fix...

[MENTION=3669620]alponso[/MENTION] To fix the permissions, you can use a file explorer to navigate to /sbin/.core/img/MagiskHidePropsConf and change manually to permission 755 for the busybox binary there. Or, run this command as su in a terminal emulator:

chmod 755 /sbin/.core/img/MagiskHidePropsConf/busybox

[MENTION=4915180]Landrea[/MENTION] That's a typo in the code, I'll try to get things fixed as soon as possible. Meanwhile you can either uninstall and reinstall the module, or run this command as su in a terminal emulator and reboot:

chmod 755 /sbin/.core/img/.core/service.d/propsconf_late
[Magisk] Landrea:
[MENTION=4915180]Landrea[/MENTION] That's a typo in the code, I'll try to get things fixed as soon as possible. Meanwhile you can either uninstall and reinstall the module, or run this command as su in a terminal emulator and reboot:

chmod 755 /sbin/.core/img/.core/service.d/propsconf_late

[/QUOTE]

"no such file o directory"
[Magisk] Didgeridoohan:
In that case you probably either misspelled the path, or you really need to reinstall the module...
[Magisk] jbliz:
Here's my step to make it work :

1. Open Root Explorer.

2. Navigate to /sbin/.core/img/MagiskHidePropsConf.

3. Long press on busybox.

4. Select Permissions.

5. Set permission to 0755 rwxr-xr-x.

6. Switch back to Material Terminal.

7. Type command 'su' and 'props'.

8. Change fingerprint to ASUS Laser 2.

9. Reboot my phone.

10. And it's worked also SafetyNet is passed.
[Magisk] Didgeridoohan:
No... I meant the steps you took for the busybox permissions to be set to 644.
[Magisk] jbliz:
Oh I'm sorry, here my steps :

1. Install MagiskHide Props Config v2.3.0 module via TWRP.

When I was install this module, log show me some kind conflict with a module (safetynet fix). I don't remove safetynet fix module at that time.

2. Using Terminal Emulator with command 'su' and 'props'.

Module run normally without any errors occurs, but option 1 and 2 are disabled. Install and reinstall Magisk version from version 13, 14, 15 and 16, wipe cache, reinstall MIUI, update Rom what ever I do didn't make option 1 and 2 enable.

3. Pick option r - reset all options/settings and reboot.

I think this will fix everything but MagiskHide Props Config show error "The original prop value are not loaded, possibly due to a full reset of the module. Please reboot your device to reset.".
[Magisk] lazostat:
Can I use one of your fingerprints to pass safety test on LG g4 and Lenovo tab2 a10-70? If I install a fingerprint for other device, will it brick my phone?
[Magisk] fxstone:
No, it won't brick your phone. Only thing that could happen, is that you can no longer install some apps, which are device specific, as they check for the device's fingerprint.
[Magisk] lazostat:
So which fingerprint do you recommend me to install for lg g4 and lenovo tab2 a10-70?
[Magisk] abacate123:
Grab your stock rom fingerprint from its bruil.prop file. You can either send here, and Didgeridoohan should add it to the LG list there in the module so you can apply it through the terminal, or you simply apply this fingerprint prop manually.
[Magisk] lazostat:
My custom rom is android 6.0 but the only MM version is see in the list is the 6.0.1. Should I have any problem? Can I install a fingerprint with higher android version than my tablet's?

I don't know how to grab fingerprint from stock rom, and anyway the stock's android version of Lenovo tab2 is android 4.4.
[Magisk] fxstone:
Here you can find the instructions to get a devices fingerprint:

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

If you would have read the op carefully, you would have found it there aswell.

I dont use this module, so i don't know which fingerprints are available an thus i can't recommend one. Afaik picking a fingerprint for a newer android version shouldn't lead to any problems.
[Magisk] israfilkhan:
View attachment 4535772

Please help me.What can I do?
[Magisk] abacate123:
Did you reboot? If yes and it didn't solve, try to flash the module again, then try the terminal commands. Maybe it'll fix.

If not, then open magisk manager, open the side menu (from the left), open "Log", swipe to the right then save the "magisk" log in the floppy disk icon and send the file it generated here.
[Magisk] israfilkhan:
Yes reboot and flash module 2 times.but same result.

Here is the log.

View attachment 4535926
[Magisk] Didgeridoohan:
Holiday support post... :silly: Might not be able to troubleshoot much, but you could provide the logs that you'll find under /cache (just the Magisk log won't give the full answer). More details about logs are found in the documentation.
[Magisk] lazostat:
Ok i installed oneplus6 fingerprint and now i can pass safenynet! Thanks guys for this module!
[Magisk] Didgeridoohan:
Whenever I see that [MENTION=7280276]ipdev[/MENTION] has posted in the thread, I know it's gonna be a good day. Thank you my friend.

I got the Fairphone 2 print to pass on my Nexus 6 as well (completing the sequence, makes me all warm and fuzzy inside). Haven't tested on any other device, but 3 out of 5 is good enough... :D
[Magisk] Droid9684:
[MENTION=4667597]Didgeridoohan[/MENTION] I had passed the saftey check previously using both your module and a older one. I recently had to redo my phone and now it wont past safety check anymore. Can you help me out? Thanks!

Galaxy S5 G900V

AOSP Extended Rom 8.1.0

Custom boeffla 4.1 tuned

Rooted

Magisk 20

MagiskHide Props Config v65
[Magisk] Didgeridoohan:
Not without the almighty logs.
[Magisk] iruiz2:
Thank you very much for your module. CTS passed and GPlay showing certified on a Samsung Galaxy Tab S5e running RR Pie ROM.
[Magisk] twk99:
Hi!

In about a week Google Stadia, Googles game streaming service will be released. In the beginning the only phone it will work on are Pixel phones.

Will using this module to spoof a Pixel phone enable me to play Stadia on another android device?

Thanks in advance!
[Magisk] jenslody:
If it's not yet released, you might not get an answer, but it should be worth a try.

If it's not bound to some pixel specific stuff (hard- or software) it might work.
[Magisk] twk99:
Thanks for oyur reply!

I will give it a try when Stadia is released!
[Magisk] Droid9684:
Magisk Log

Here is the magisk log. So going back to my other backup previous to my phone restore from stock AOSP I did notice safteynet check didn't pass. But as I said in the past it has. I really want to avoid having to disable magisk modules using core if at all possible.
[Magisk] Didgeridoohan:
A couple of things:

First, this module won't do anything for passing SafetyNet with your current setup. Since you have Petnoire's Safetyspoofer installed, the device fingerprint feature of MagiskHide Props Config will be disabled (since they do the same thing).

Second, EdXposed now triggers SafetyNet but there are workarounds. Take a look in the EdXposed Github for details.
[Magisk] Droid9684:
Thanks it worked!!!

The EdXposed workaround worked thank you very much! :D
[Magisk] Arindam430:
Device- Redmi note 7 pro, codename- Violet

Fingerprint-

xiaomi/violet/violet:9/PKQ1.181203.001/V10.3.13.0.PFHINXM:user/release-keys

Security patch date is 01-10-2019

Please add this device in list
[Magisk] VizricK:
Quick question what happen to the 3rd option called "improved hiding" from 4.0.3 xx?

I update to 5.0.1 v65 latest and the option is missing. not letting me pass Safety Net on some apps like my Bank, PoGo, etc. Had to downgrade. Once I enable that option it's all good.

(Or what do I have to enable in order to pass besides the first option. Device simulation really does nothing for me since I don't know what custom values I need to place for my Exynos S8 running Hades ROM v11 pie)
[Magisk] Didgeridoohan:
Such info is usually found in the changelog or release notes.

Main reason is that the function wasn't compatible with SAR (would mount the system partition rw, not good) and that I'm still not fully convinced that it actually did any good.

Once I figure out how it should work for SAR it might make a comeback, but to put the effort in (I have extremely limited time to work on it) I would very much like to see someone proving that it actually worked. You seem to imply as much, but can you 100% replicate that the apps you're talking about will trigger their root detection if you don't have "Improved hiding" enabled? Logs (logcat) would of course also be appreciated...

All you need for SafetyNet is usually to edit the device fingerprint. Other root detection methods have nothing to do with SafetyNet...

I'm fairly sure that PoGo wouldn't benefit from "Improved hiding", but which is the banking app you're talking about?
[Magisk] bigjailerman:
Thank you very much
[Magisk] Didgeridoohan:
[MENTION=9427212]CleaveGodz[/MENTION] and [MENTION=7517292]ValeV008[/MENTION], if you've got the time I have another test zip for you. It probably won't fix all the issues you've seen though, and if it doesn't I would love a detailed description/screenshot and logs. [MENTION=8126387]martyfender[/MENTION] This version should also fix your issue by automatically detecting if the post-fs-data.sh script takes too long to start and then rebooting the device with the script running completely in the background from then on.

This zip has been fairly well tested, so barring any bugs you guys find I'd say it's pretty much release worthy (I hope).

Edit: slight update to the "well tested zip"... :D

Edit 2: A tip for those that feel inclined to help testing. Run the command with the -t option. That way any errors shown while running the ui will be much easier to see since the screen won't clear whenever the ui updates.

props -t
[Magisk] martyfender:
Thanks for this, I will test and report when I can. Like you, I have been busy dealing with real life issues, (a myocardial infarction and returning to work this week), no big deal, I problably would have been dead if I had not did so much running and cycling in my 20's-40's. I may not have survived a total blockage of a major artery. Heredity was the biggest factor. Sorry for the OT. I am off tomorrow,so will try your test.

Actually flashing now in the modules section.

I had the same error in the terminal so I said yes to rebooting to see what happens?

Still an error.
[Magisk] chooks06:
Take care mate! Wish you good health!
[Magisk] Didgeridoohan:
"A myocardial infarction ... no big deal" he says... :eek:

Thank you for helping out, but as I think you've told me earlier, real life and health comes first. Sounds like you're recovering well and I wish you all the best.

Your logs showed me that everything actually worked exactly as intended, and if it hadn't been for a small typo/though boo-boo on my part you likely wouldn't have seen any error at all after that reboot (the reboot is necessary).

I've updated the test zip in the post above, for anyone that wants to test for possible bugs.
[Magisk] ValeV008:
No problem, I will do it in the evening. (GMT+1 timezone)
[Magisk] sliding_billy:
A myocardial infarction is like a soft brick of the phone, right? ;) Seriously, take care.
[Magisk] martyfender:
I was being sarcastic when I stated that it was no big deal. I have been relatively healthy most of my 61 years so this was a major life changer.

I am flashing your latest test right now. Just testing with the -t option and rebooting, as there was an error again.

Still no go. The latest log with props -t in the terminal. I'm wondering if I should switch Apps2SD' script back to service.d and test it. That is where it was when we first started testing all of this.

However, Apps2SD is mounting the second partition just fine with it in post-fs-data.d.

Thanks
[Magisk] Didgeridoohan:
Thanks mate. Your device is quite the handful... In every single log up until now it's been showing a very consistent behaviour with the time it takes to start executing the post-fs-data.sh script. Between 400 and 550 ms. Suddenly it goes down to less than 200! Gorramit...

I'm just gonna go the manual route instead. If the issue arises, the user will have to enter the script settings (props -s) and activate the background execution. It seems rare enough to not bother with anything else. Stand by for further test zips... :silly:
[Magisk] martyfender:
Thanks for hanging in there. It seems my cheap devices in general are quite a handful. For example, my older, Nextbook Ares 8A, Android 6 tablets and now, my Onn 8 Android 9 tablets. There is a whole xda thread for this new device and many say it is close to AOSP. There are some user on that forum who have flashed many GSI treble roms on this device, so it seems to be very versatile. I have only used the stock with the latest Canary Magisk. Just last week a TWRP was released for it also.

I will test when I can, if you give me info about the manual method. By the way, your current released version appears to work well on my 4, still working, out of 5, Nextbook Ares 8A's, as far as I can tell.
[Magisk] kryshnakishore:
Oneplus 6, Android 10

1.I am getting screenshot error says "couldnt save screenshot Try taking screenshot again "...it is failing all the time Any suggestions.

2. I used to have single keyboard for personal & work profiles. Now that it is asking to install keyboard app in work profile. In Android 9 there was no such restriction, any suggestions.

3. When lock screen is set for personal profile it is asking to set lock screen for work profile also. In Android 9 there was no mandatory lock screen for work profile. Any suggestions.
[Magisk] Didgeridoohan:
I'm sorry, but I have no idea what that has to do with the MagiskHide Props Config module... Or did you just accidentally post in the wrong thread?
[Magisk] Didgeridoohan:
[MENTION=8126387]martyfender[/MENTION] Before I start doing to much crazy stuff, could you just try this zip? It's a POC and if it works I'll know I can keep on that same road. If it doesn't I'll just use a different approach... There's some air code in there, so it might not actually work at all, but I'm crossing my fingers (my devices are currently unavailable for testing).
[Magisk] hyborian:
I don't know, on my phone with SAR, I don't even need to set a fingerprint using MagiskHide, it just passes both Safety Net. All banking or apps that have any financial stuff work.

I had to change my Tasker scripts that mount "/system" to just "/", though. Like I have a Tasker menu to change boot animations which needs to mount /system before I can overwrite anything.
[Magisk] martyfender:
Logs
[Magisk] martyfender:
Log after changing Apps2SD settings to use service.d instead of post-fs-data.d.

Logs

Success!

This is the first time that MHPC has worked without error on this device in a while. I just changed the device fingerprint to the Pixel XL Android 9 and am rebooting.

Safety net pass in MM.

Reverting fingerprint changes and rebooting.
[Magisk] martyfender:
I also tested Test502-3.zip on one of my Android 6 tablets and it also appears to be working fine, although I didn't test any options. I will attach logs when back on that device.

Thanks
[Magisk] Didgeridoohan:
I wasn't talking about passing SafetyNet, but a now removed function of the module ("Improved hiding"). If you can pass SafetyNet it means that your device has a certified fingerprint (if it's stock that's not strange, if you have a custom ROM it means that the developer included one).

That's because Magisk now follows Google's standards and rules regarding SAR and mounts the system partition to "/" (System As Root).
[Magisk] hyborian:
Noted, just pointing out to the other guy that my SAR phone didn't need the removed module (which I never needed in the past and present anyway) ...

I use stock Roms on all my Xiaomis with Magisk, and really need to use MagiskHide fingerprint function to get them to pass Safety net, except this new Note 7 with SAR where I don't need MagiskHide. Wish all of the were like that, but anyway, we'll see what happens on my next Xiaomi phones (which I assume will all be SAR moving forward).
[Magisk] martyfender:
I just got home from work and was just curious what your thoughts were concerning my series of tests, unsuccessful to the latest, successful. Thanks for your input and I also hope it helps you out with improving this great module.
[Magisk] Didgeridoohan:
Well, I'm assuming you're mainly interested in the latest test zip, but I'm gonna give a bit more background and thoughts than that. Starting from your very first reports on this, they've given me a good reason to finally do something about the post-fs-data.sh boot script.

I've always been a bit hesitant on having too much going on there, since it's a blocking boot stage and things might go wrong if script execution takes too long (as you've noticed). But, since things seem to have been working for everyone up until now (or nobody's reported their issues), I've not bothered with it.

Your reports and tests have given me ideas for and the opportunity to refine how the scripts are handled. :good:

Going forward, almost the entire post-fs-data script will execute in the background. The only parts that won't is to start logging and saving of the device default values. The rest of what's left in the early boot stage (module settings file control and custom props that the user wants to be set here) is then executed in the background. Several things have been moved to the late_start service boot stage (like configuration file detection and setup).

Your latest series tests gave me what I needed to decide on how to handle running the entire post-fs-data script in the background. There'll be a setting to enable this (also accessible if all you get is the "boot script didn't run" screen that you should now be very familiar with), rather than the automatic approach I tried first (that was way too unreliable). At first I was contemplating a rather overcomplicated approach (I have a tendency to always end up there), but that would defeat the purpose of cleaning up the script in the first place. It was that approach you tested with the latest zip. It seemed to work, but not good enough... The final solution for the setting is much more simple (just a simple sed substitution on the script rather than having ways of executing different files).

Thanks for helping out and testing whatever I've thrown at you.
[Magisk] martyfender:
Maybe this is OT here, but you seem to be one of the only ones who may have a clue as to what is going on here, as it is very, very strange, to me:

I posted this bug to John, a few weeks back on github, but he said he could not reproduce it. So I did not post any further. But the same bug appears also on my New, Onn 8, Android 9 tablet, on several Android terminal emulators I tried, but causes no problems otherwise that I can see:

:/ $ su

: (unreachable) #

It started happening a few Magisk versions back, unofficial and Canary versions. As I stated I wasn't concerned until it appeared on the Android 9 device as well as all of my Android 6.0.1 devices. It is the (unreachable) part.

What is unreachable in Android that the terminal can't communicate with? I have no clue as to what commit this started at without going way back some time. It only appears to be cosmetic in nature.

thanks.
[Magisk] Didgeridoohan:
I have no idea, can't reproduce and my Google-Fu is failing me... Sorry.

I'm assuming there's nothing noteworthy in the Magisk log, but have you checked logcat?
[Magisk] ubercash:
Erorr in running MagiskHide Props

I did not install Edxposed on my device but I am getting an " service.sh not found" error while I run "props" in the terminal. I've tried rebooting several times but it still doesn't fix. Below is the propslogs.tar to download.

https:// drive.google. com /file/d/1B0LRZQTtQ6MT5qk7SZq30yh_SZjdH90n/ view?usp=sharing
[Magisk] Didgeridoohan:
From what I can see in your log, the late_start service boot stage (where the service.sh script is executed) doesn't even run on your device. Might not be module related at all...

I would try to do a complete reinstall of Magisk (uninstall and then install again) to see if that fixes things. First you could try the test module attached to this post though. It is used to test some fixes for the next release that might have something to do with your issue.
[Magisk] jcmm11:
Upload /system/etc/mkshrc

Whatever is causing (unreachable) is happening when trying to generate the prompt for root mode.
[Magisk] martyfender:
Here you go, from my Onn 8, Android 9 tablet:

Thanks

That file is also in /vendor/etc/mkshrc.