yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
That sounds like a bug with the automatic fingerprint update. I'm currently at work and have a bunch of schoolwork ahead, but I'll try to take a closer look in the next couple of days.
[Magisk] allrockedout:
Can you add redmi note 5 pie fingerprints please
[Magisk] Didgeridoohan:
The one you posted did not pass SafetyNet on my test device and I only add fingerprints that I can confirm are working.
[Magisk] NOS_bzone:
Hi dev, this module support Xiaomi Mi 9 (cepheus)?
[Magisk] garylawwd:
It supports any device running Magisk 19+

You don't have to use your own device fingerprint you can just use something close if you have to.

Read the module documentation everything you need to know is there
[Magisk] Didgeridoohan:
There's no fingerprint for that device included in the module, but otherwise it should work. If you have a working fingerprint you can enter it manually, either through terminal or with the configuration file.

If you do have a fingerprint for that device, please share it and I can add it to the module. Don't forget to also include the security patch date.

If you don't have a working fingerprint, here are some tips on how to find one:

https://github.com/Magisk-Modules-R...ter/README.md#finding-a-certified-fingerprint
[Magisk] loni90:
Tja!

Rootade nyligen min s8 med magisk - men får inte Samsung Pay att funka oavsett vad jag gör.

Klickar på Hide apps i magisk, och även testat installera din modul.

Inte testat Magisk V19 ännu då den är i beta, vågar man testa det?
[Magisk] jcmm11:
First of all as a senior member you should know this is a "must use English forum".If you use any other languages at least include a Google translate with it.

Second, you should also know that copying an entire OP like that is frowned upon. It wastes space and adds nothing to the discussion.

Yes I would recommend trying v19.I also recommend trying to hide Magisk Manager itself. Beyond that maybe somebody else with Samsung Pay experience can help you.

Först och främst som senior medlem borde du veta att detta är ett "måste använda engelska forum". Om du använder något annat språk åtminstone inkludera en Google-översätt med den.

För det andra borde du också veta att kopiering av en hel OP så är fryst på. Det slösar ut utrymme och lägger ingenting till diskussionen.

Ja, jag rekommenderar att du försöker v19. Jag rekommenderar också att du försöker dölja Magisk Manager själv. För det kan det hända att någon annan med Samsung Pay-upplevelse kan hjälpa dig.
[Magisk] loni90:
My bad, im not as active here anymore - and forgot about all the rules and stuff.

But thank you for taking time to answer my poorly executed question.

Keep up the good work!
[Magisk] SnowFuhrer:
If I assume your problem right, magiskhide won't help a thing in getting Samsung pay work. Samsung phones have Knox, which, when it detects unofficial software, blows a fuse on the motherboard, and then Samsung pay will never work without a specially modified kernel, even if you flash stock.
[Magisk] starcms:
Same issue here.
[Magisk] NOS_bzone:
Okey thank you, I'm using polaris (Mix 2S) device for fingerprint on my cepheus (Mi 9). And CTS Profile active now.
[Magisk] Kashamalaga:
For Mi9 isnt working. Here is the one valid :D

ro.product.brand=Xiaomi

ro.product.name=cepheus_eea

ro.product.device=cepheus

ro.build.version.release=9

ro.build.version.security_patch=2019-03-01

ro.build.version.incremental=V10.2.17.0.PFAEUXM

ro.build.version.sdk=28

ro.product.mod_device=cepheus_eea_global

ro.build.fingerprint=Xiaomi/cepheus_eea/cepheus:9/PKQ1.181121.001/V10.2.17.0.PFAEUXM:user/release-keys

ro.build.description=cepheus-user 9 PKQ1.181121.001 V10.2.17.0.PFAEUXM release-keys
[Magisk] Didgeridoohan:
Update to v4.0.1-v52

A small bug fix release. Thanks to [MENTION=4556013]iPusak Gaoq™[/MENTION] for finding it. Also thank you to [MENTION=4386816]Kashamalaga[/MENTION] and [MENTION=8972221]AnomSanjaya[/MENTION] for providing the fingerprints for this update.

As a side note, the module has just passed 50 000 downloads here in the XDA thread. No telling how many downloads from the Magisk repo, but I would expect the number to be significantly higher... That's kind of cool. Huge thanks to all of you!

Changelog

v4.0.1

Fixed a bug where the automatic fingerprints update function would always revert to the oldest print available for the set device.

Added two new devices to the fingerprints list, Oppo Neo 7 and Xiaomi Mi 9. List updated to v52.
[Magisk] Hedigehog:
Not work on BL9000 GSI RR_7.0.1
[Magisk] Didgeridoohan:
That's because Magisk isn't working properly on your device. It's not running things as it should during boot. I would first of all try to reinstalling Magisk (and save the installation log for possible analysis).
[Magisk] Hedigehog:
Any GSI android 9 and magisk 18.0+ don't work correctly, but all the modules I tried seemed to work, except for different Fix_cts:false

And what should be corrected for manual editing? In the vendor or in the system props (for android 9). And then all the pages only about 2 of these modules are repeated, and I can no longer find this manual method
[Magisk] Didgeridoohan:
It seems like files are magic mounted, yes, so that part is working. But boot scripts aren't being executed, and those are the heart of this module (and any other module that's based on changing props).

If you want to do manual editing of the required props, look in both /system/build.prop and /vendor/build.prop for these and change them to a certified fingerprint:

ro.build.fingerprint
ro.bootimage.build.fingerprint
ro.vendor.build.fingerprint

The vendor fingerprint is likely going to be set to a certified print already, so start by setting the other two to that same value. If you need to use a different fingerprint, don't forget to also set the security patch date to one that matches the fingerprint:

ro.build.version.security_patch
[Magisk] tuga_z:
What I can do more please?
[Magisk] Didgeridoohan:
Have you set the module up with a certified fingerprint? It's not a flash and forget kind of module, it needs some basic setup as well...

If you haven't already, take a look at the docs. Most things are covered there.
[Magisk] Estebanium:
Man I hate to mess around with stock ROM, but I hope I can make some people happy:

SAMSUNG GALAXY S7 Edge
2019-03-01
samsung/hero2ltexx/hero2lte:8.0.0/R16NW/G935FXXS4ESC3:user/release-keys

Good news: The S7 could still get Android Pie.

But now quickly back to LineageOS. Hopp hopp and flash! :silly:
[Magisk] madbat99:
[MENTION=4667597]Didgeridoohan[/MENTION]

I love how much you have put into this module. I follow the thread, but usually gloss over it quickly because I'm not worried about safety net (at least concerning device fingerprint) right now. Completely forgetting that it is an awesome custom props tool. I finally remembered that, and used it to set the prop to enable tethering. That was pretty much the last piece of the puzzle I need to pass safetynet whenever I want now.

Still on Oreo with a moto device that has no custom roms, so xposed with GravityBox is pretty much my custom ROM simulator. So now I switch off xposed and my banking app works my fingerprint reader.

So to you a very long-winded and, poorly voice type while driving,

Thank you
[Magisk] Paschfire:
So after thumbing through the entire thread, re-reading the OP section and the MagiskHide Props Config page section on Improve root hiding - Editing build.prop and default.prop, including the sections that follow it.

I for the life of me don't understand how to perform some simple build.prop editing.

On my 3T running stock OOS 5.0.8 ~ TWRP 3.2.3-10 ~ Magisk v19.0 Canary ~ BusyBox(osm0sis MM) ~ FKr46.

After reading about this module, I have 16 build.prop entries that previously I manually entered and would like to use this module to add them systemlessly.

I am confused on how to do so?

Within terminal prompt after running props, I selected option 5, then 'n' for new custom prop, typed 'build.prop' and get the following screen saying the prop doesn't exist.

Are there some detailed instructions, or guide to follow, on how to perform build.prop edits?

I'd greatly appreciated if someone could help guide me through the setup on how to use this module correctly. Or am I mistaken on the usages for it?
[Magisk] Estebanium:
You don't have to enter the name of the file (build.prop), you just need to enter the name of the entry and later the value to set. For instance you enter ro.product.manufacturer and hit enter, then it asks for a value e. g. samsung or htc
[Magisk] Didgeridoohan:
You're not quite getting the usage. When you're asked to enter a custom prop to set you're supposed to enter the actual prop, nothing else. "Build.prop" is the name of the file containing some of the props that are set by the system at boot and that you can then alter with modules like this.

Here's an example:

If you want to change the screen density, you would enter this prop when prompted:

ro.sf.lcd_density

Then you would be asked to enter the new value (and you'd be shown the current value if the prop exists on your device).

After the next reboot, the new value will be loaded instead of the one in build.prop (or whichever file the prop is stored in), but note that the actual file will not be altered, just the value loaded into memory.

But, since you have so many props that you want to set, let me suggest that you instead use the configuration file for the module instead of entering every single prop manually. That way you can easily alter many props at once and you can keep a copy of the file for future use. More details on that here:

https://github.com/Magisk-Modules-R...nfig/blob/master/README.md#configuration-file

Last note: The improved hiding (editing of build.prop and default.prop) has nothing to do with setting custom props. That function is used to systemlessly change build.prop and default.prop for the prop values that MagiskHide hides. Supposedly there are apps that can trigger by this (but I actually have my doubts about the usefullness of this feature)...

Hope that helps. :good:
[Magisk] Paschfire:
Seems I am confused then.

To explain in greater detail, all I was looking to do was simply to add the following additional lines to the build.prop, that don't exist within the original build.prop.

#

#GPU_Performance_Boost

#

com.qc.hardware=true

debug.qc.hardware=true

debug.qctwa.preservebuf=1

debug.qctwa.statusbar=1

debug.composition.type=gpu

debug.egl.profiler=1

debug.enabletr=true

debug.overlayui.enable=1

debug.performance.tuning=1

hw3d.force=1

hwui.disable_vsync=true

hwui.render_dirty_regions=false

ro.config.enable.hw_accel=true

ro.fb.mode=1

ro.product.gpu.driver=1

ro.sf.compbypass.enable=0

I've no issue with magisk hide or anything else Magisk related, I just thought it was better to add additional lines to the build.prop systemlessly as apposed to making edits to the original build.prop.

If this isn't part of the designed function/intension of this module, is there a better way of doing this? Or should I just continue using a modified build.prop for these types of build.prop modifications?
[Magisk] Didgeridoohan:
That is precisely what this module is for. I think what you've gotten hung up on is the altering of the actual prop file. With Magisk, that does not happen. Like I said previously, the new values are simply loaded to memory, nothing else.

Download the configuration file, add that list of props (just as it is, without the comment lines) to the CONFPROPS variable (see the file for more details and instructions), place it in /cache or /data and reboot.

Make sure to keep a backup of the configuration file and you can redo the process on any new ROM install or similar.
[Magisk] Paschfire:
No no, I understand that.

The original build.prop stays completely intact, unmodified, when using this module. (Eg.: Similar to the way setprop worked with ARISE sound system).

I just didn't understand how to proceed with setting it up properly.

I'll look into the configuration file setup and go from there. If I have any further questions I'll return here.

Thanks for all the help, greatly appreciate it. :highfive:
[Magisk] Paschfire:
K now I'm getting somewhere. :victory:

So simple I feel dumb asking for assistance in the first place.

Thanks again for all your help.
[Magisk] Didgeridoohan:
Asking for assistance when not getting something is never dumb. More people should practice that...

I'm glad things seems to be working as expected. :highfive:
[Magisk] HypoTurtle:
Do installed but not activated modules trip the system.prop check?
[Magisk] Didgeridoohan:
If you mean the checks for modules that do the same things as this module, then yes. I simply check for the presence of the module, nothing else.

Edit: that's something I could change for a future update though. Thanks for the idea...
[Magisk] HypoTurtle:
Yea meant in terms of the disabling, ill just uninstall in the meantime then, at times its a tad tricky to determine if a mod uses system.prop, but guess thats what the logs are for...
[Magisk] Didgeridoohan:
I don't do any checks for system.prop. I mainly check for known modules that also edit the device fingerprint, not the system.prop file per se...
[Magisk] Didgeridoohan:
It's not the module, but your Magisk installation that isn't working as it should.

The last part of the log shows that there was a magisk.log file generated at some point, so if you could upload that it would be good. I suspect that it'll be empty though (or not showing much), so you're probably going to have to look for help with getting Magisk up and running elsewhere... The ROM thread would be a good place to start, since GSI's are known to have compatibility issues with Magisk.
[Magisk] lunks:
I've switched to AOSP 8.1 and it's working fine with latest Magisk. Thanks for the plugin!
[Magisk] aydinbahadir88:
Installed the latest Magisk 19

Unfortunately it can not flash
[Magisk] Didgeridoohan:
Note to self: add this to the docs...

That means that you haven't done a proper update to v19 and core parts of Magisk is still on an older version. Reinstall Magisk from the Manager, direct install, and you should be good to go. If you can't do a direct reinstall you might have to uninstall Magisk first and start over.
[Magisk] hyborian:
[MENTION=4667597]Didgeridoohan[/MENTION], I am getting a "!File Not Downloaded" message when running props. It's ok on another phone of the same model though. Attached is the log, thanks.
[Magisk] Didgeridoohan:
Try updating/changing your Busybox.

Edit: is that the entire log? If so things aren't running as they should during boot...
[Magisk] hyborian:
[MENTION=4667597]Didgeridoohan[/MENTION], no, not the full log, I deleted the log just so I can capture only the error in a short log.

Thanks, it worked. Something was wrong with the Jrummy Busybox, it was so tough to remove from /system/xbin even after uninstalling JRummy app. Reinstalled Busybox by Osmosis and it's now in /system/xbin, now all ok.
[Magisk] x86cpu:
New fingerprints to add

I tried to format it for easy inclusion into the prints.sh. The H850 is an update. I have yet to get ahold of a ls997 oreo image, and LG has not released it for rs988 yet (if ever).

LG G6 H870 (8.0.0)=lge/lucye_global_com/lucye:8.0.0/OPR1.170623.032/183301757502c:user/release-keys__2018-11-01
LG G6 H872 (8.0.0)=lge/lucye_tmo_us/lucye:8.0.0/OPR1.170623.032/183621644ce05:user/release-keys__2019_01-01
LG G6 US997 (8.0.0)=lge/lucye_nao_us/lucye:8.0.0/OPR1.170623.032/181521705197f:user/release-keys__2018_06_01
LG G5 H850 (8.0.0)=lge/h1_global_com/h1:8.0.0/OPR1.170623.032/190380127377a:user/release-keys__2018-12-01
LG G5 H830 (8.0.0)=lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys__2018-08-01
LG G5 RS988 (7.0)=lge/h1_lra_us/h1:7.0/NRD90U/1707917149a1b:user/release-keys
LG V20 H918 (8.0.0)=lge/elsa_tmo_us/elsa:8.0.0/OPR1.170623.032/1831917495b33:user/release-keys__2018-11-01
LG V20 H910 (8.0.0)=lge/elsa_att_us/elsa:8.0.0/OPR1.170623.032/181871124f959:user/release-keys__2018-06-01
LG V20 VS995 (8.0.0)=lge/elsa_vzw/elsa:8.0.0/OPR1.170623.032/183141449275f:user/release-keys__2018-10-01
LG V20 US996 (8.0.0)=lge/elsa_nao_us/elsa:8.0.0/OPR1.170623.032/183241436cd40:user/release-keys__2018-11-01
LG V20 LS997 (7.0)=lge/elsa_spr_us/elsa:7.0/NRD90M/1626515087a95:user/release-keys
[Magisk] Redline:
I'm having a force reboot issue after installing this module on LineageOS 16.0 on my V30+

Installing the module through Magisk works fine, rebooting and then selecting the Fingerprint I want to use (in this case the 8.0 V30 Fingerprint) also works fine, but after rebooting to apply it, about a minute or two after reboot the screen brightness goes to max, and it does something of a SystemUI restart/system reboot, and I'm back to the lockscreen with everything starting up again as usual during a boot sequence.

This repeats until I go into Magisk, disable the module, and manually reboot during the 1-2 minutes before it does it itself.

Rebooting without disabling the module but AFTER applying the new fingerprint always loops on the boot logo for 3-4 minutes, and then reboots to recovery (TWRP in my case).

I thought it might be the Busybox I also installed at the same time, but I've narrowed it down to being able to reproduce it with 100% accuracy if only this module is enabled in Magisk.

Any ideas or logs you'd like me to get before/after the crash happens? The fingerprint is applied okay and now passes both Safetynet checks in Magisk (whereas before it would only pass the one) so the function the module set out to achieve works fine, but enabling it to use it for switching Fingerprints/updating it is a no-go.
[Magisk] Didgeridoohan:
[MENTION=5988026]Redline[/MENTION] The Magisk and module logs, as described here would be a good start, just to make sure things look alright. The /sys/fs/pstore/console-ramoops after a reboot would also be good. Grabbing a logcat during the event might of course also show something.

You could do some further troubleshooting by disabling the module and putting this in a script that you place in first /data/adb/service.d and then /data/adb/post-fs-data.d (don't forget execution permissions):

resetprop ro.build.fingerprint lge/joan_global_com/joan:8.0.0/OPR1.170623.026/181381736b4e9:user/release-keys
resetprop ro.build.version.security_patch 2018-11-05

If those work as they should it's definitely something with the module...

Edit: are you saying that it's enough to have the module installed, without applying a fingerprint for the issues to start?
[Magisk] Redline:
Logs from the module and SysLog (including Pstore but I believe this will be empty as it's bugged atm) are attached to my post.

Logs were taken within a minute after it did the SystemUI restart/reboot thing.

Having the module installed and enabled, AFTER applying a new fingerprint and rebooting, is what causes the issue. I'm able to have it installed and enabled without any issues BEFORE changing the fingerprint from the default but AFTER rebooting to enable the module after installation.

The issue occurs, but the fingerprint is changed to the new one I selected. I can then disable the module to prevent the issue from re-occuring while keeping the new fingerprint, and therefore passing SafetyNet.
[Magisk] Didgeridoohan:
What happens if you don't enable device simulation? It's not need for passing SafetyNet.
[Magisk] Redline:
It looks like everything is okay and working fine in that case.

I'd enabled it to access a specific LG app on the Play Store (funny you said that in your Readme.md for Device Simulation) but it looks like I can get an apk for the version I want online anyway.

Should've tried to disable that first, my bad :good:

Thanks for the module, I can actually use Google Pay now :D
[Magisk] wilsonhlacerda:
Hi [MENTION=4667597]Didgeridoohan[/MENTION] for you to know:

I have a device with LOS 14.1 (Galaxy S4 Active i9295) and have been upgrading both Magisk, Busybox and MagiskHide Props Config without problems, everything working fine as expected. Currently on my device I have v19.0 and newest modules. BUT..... yesterday I clean flashed my girlfriend's device that is exactly same of mine with exactly same LOS. Flashed Magisk v19, just like mine. Flashed same Busybox also. But MagiskHide Props Config refuses to flash: it asks for Magisk v19+. I've tried under TWRP, under install of Magisk Manager, under download plus add of Magisk Manager. Tried reboot and nothing. MagiskHide Props Config always refuses to install. What is curious is that this clean new device is just exactly like my one that have gotten everything working by incremental upgrades. Magisk itself seems to be working fine (partially pass SafetyNet, Busybox is installed fine, root apps get Magisk root,..).

Later today I'll try to reinstall Magisk v19 from Magisk Manager itself to see if I get different results, but anyway seems to me something may be broken on MagiskHide Props Config install.
[Magisk] Didgeridoohan:
Only way for me to know that is if you provide the module installation log (propsconf_install.log in /cache).
[Magisk] morganpl:
LineageOS 15.1 for Lenovo K6 Note (karatep)

I hope I can make some people happy :)
[Magisk] wilsonhlacerda:
Did it:

the log is not that informative: only has 3 lines, main and wrong info is that could not find Magisk 19+.

so as suggested I (re)Installed Magisk v19 again, under Magisk Manager (originally I did it under TWRP and was everything fine as I'd written), rebooted, and installed MagiskHide Props Config. Then module installation was successful. Problem solved.

Weird. But your suggestion did the trick. Thanks for this module and all Magisk support!
[Magisk] Didgeridoohan:
So, just to clarify:

You did a clean install of LOS on the device (did you wipe data?)?

You did a clean install of Magisk (which version/zip?) through TWRP?

In the log, what build version did it report that you had installed (and was that the version you had installed previously?)?

It would be good to narrow this down, since it's possible that there might be a bug in the Magisk update scripts.
[Magisk] h8isgr8:
This module is causing system apps, including the launcher, to crash shortly after booting. I have just enough time to open an app before the launcher crashes. It did this even before setting up the module. I managed to load a fingerprint, but stuff still crashes and ctsprofile is still false (I checked with getprop and fingerprint was applied). When I tried to run props in the terminal again it says permissions denied. Had to uninstall the module.
[Magisk] Didgeridoohan:
If you hadn't set anything up, the module does nothing...

Without any kinds of logs there's absolutely nothing that can be done about any possible issue.
[Magisk] h8isgr8:
Well, I wouldn't say it does nothing (sarcasm). If I install the module it causes system apps to crash even without running the setup. If I uncheck the module in Magisk the crashing stops. Magisk version is 19.0.

EDIT: What do I need to look for in the log? I see that all the apps that were crashing also show in the log "bind_mount" in front of them.
[Magisk] Didgeridoohan:
It's very possible that it's not the module per se, but some kind of synergy with other scripts/modules that's causing issues. That's happened before and hasn't been anything I have control over...

But, if you want me to take a proper look at this, you need to provide the Magisk Canary debug build log (details here) and the module logs (described here).
[Magisk] h8isgr8:
Not familiar with the Canary debug build, so I'll have to look in to that. I couldn't get the module to collect the logs so I had to collect them manually. The attached file contains magisk, propsconf, propsconf_install and propsconf_last logs.

Thanks
[Magisk] Didgeridoohan:
Your Magisk installation is broken and the boot stages are all messed up. You need to reinstall Magisk, preferably after uninstalling.
[Magisk] h8isgr8:
I'll give that a try. FWIW I've never been able to patch the boot image or direct install; I always have to install from recovery. I don't know if that points to some other issue my device might have.

Thanks for taking a look at the logs.