yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
There has been similar reports, yes, but I don't think I've seen anyone figure out why.

You could do some more in-depth logging by grabbing logcats while the issue manifests... I'm not very good at reading logcats, but we might be lucky.
[Magisk] Makishima:
Tried grabbing a log while trying to install an app/update from Play Store with it stopping completely at 100%. Hopefully there's something useful in there. I can try running it at boot to see what happens when it actually gets installed, but I have to remember how to do that.
[Magisk] Didgeridoohan:
You're trying to install HiCare, right? And you see the same with all apps? And only when you've used the module to change the fingerprint? Does picking a completely different print (say, a Pixel device) make any difference?

All your logging needs should be covered in the guide I linked you previously.
[Magisk] Makishima:
Yep, I was trying to update HiCare but this happens with any app. I haven't tried a different fingerprint... I've wiped the phone clean and reflashed everything about 20 times the last few days so I'm trying to relax a bit, I don't want any more problems this soon. :laugh:

I tried to see if a 'Disable Google Services' option enabled in my ROM's KangVIP settings caused this, but I think it's not really working... Tried un-checking that option and upon rebooting it's checked again. However, google services seem to work regardless and seeing as this was enabled by default it would have caused the same problem when I had SuperSU instead of Magisk; everything worked then. :rolleyes:
[Magisk] Didgeridoohan:
Well, from your description it isn't Magisk that is the problem, it's the changing of the fingerprint.
[Magisk] Makishima:
Well, I mentioned two problems, actually... The first one was the inability to uninstall or log into apps after changing the fingerprint and the other was simply installing/updating an app in one go without rebooting. The second problem happens regardless of whether I have changed the fingerprint and certified Play Store or not.
[Magisk] Didgeridoohan:
Ok, then I understand. That was not apparent from your original post...

Then I would prefer if you move the discussion about installing apps to the general support thread, or even a thread if it's own. It's a bit too off topic here...
[Magisk] Makishima:
Yes, of course, you're right! I just thought it was apparent when you said that other people seem to have the same problem and urged me to grab a logcat. Thank you for your help and quick replies!
[Magisk] dazza826:
V20 h990ds

lge/elsa_global_com/elsa:7.0/NRD90M/1801800193678:user/release-keys

Patch Level : 1st Jan 2018

Not in DB at the moment. Requesting to add if passes your testing
[Magisk] Didgeridoohan:
Fingerprints list updated to v63

Well... Managed to get a few more prints tested so here they are. Hopefully next update will have a long needed update to the module (a few minor bugs I've been keeping on my list for a while now).

Thanks to [MENTION=3396139]KromerX[/MENTION] and [MENTION=1517910]dazza826[/MENTION] for providing fingerprints.

The list will be updated when you run the props command, or (if you've disabled automatic updates) by using the -f option or from the Edit device fingerprint menu, and here's the update:

New

Asus ZenFone 5Z

LG V20 H990DS

OnePlus 7 (EU, India and US/Global variants)

OnePlus 7 Pro (EU variant)

Updated

OnePlus 3

OnePlus 3T

OnePlus 5

OnePlus 5T

OnePlus 6

OnePlus 6T
[Magisk] Nebrassy:
Mi A2 August patch

xiaomi/jasmine/jasmine_sprout:9/PKQ1.180904.001/V10.0.13.0.PDIMIXM:user/release-keys

2019-08-05
[Magisk] rybshik:
Moto G6 detected as Huawei P20 Pro by Google

I noticed that my Moto G6 plus is detected by Google as Huawei P20 Pro in

myaccount.google.com/device-activity

Is it something we should expect?

I have active MagiskHide Props Config and SafetyPatch modules
[Magisk] SnowFuhrer:
You obviously used that device's fingerprint.
[Magisk] rybshik:
How can I make it appear as Moto G6 plus?
[Magisk] SnowFuhrer:
Use the fingerprint of the device you want it to be seen as.
[Magisk] rybshik:
1 - Edit device fingerprint (disabled)

To enable, I had to deactivate SafetyPatch module. I will see if Google Pay will work
[Magisk] Didgeridoohan:
Just to clarify on your posts:

The Safetypatcher module changes your device fingerprint to a Huawei P20 Pro (to change that you'll have to manually edit the module files with your preferred fingerprint), and this module disables the fingerprint function if a known conflicting module is installed.

Now that you've disabled Safetypatcher you can pick a Moto G6 print from this module and SafetyNet should pass (if your issue only was your ROM not having a certified fingerprint). For GPay you might need more than that though: https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
[Magisk] rybshik:
Safetypatcher has been working well for me with GooglePay (except using fingerprint for not my device). So if am to keep using Safetypatcher and change fingerprint to Moto G6 plus, what exactly should I do?

I have to keep MagiskHide Props Config module as well for Mobile HotSpot Tethering.
[Magisk] Didgeridoohan:
Easiest thing would then be to just use this module to also change the fingerprint. There are several variants of Moto G6 available. Both modules do the same thing regarding fingerprints, that's why I disabled that option when a conflicting module is found.
[Magisk] rybshik:
sorry, it's not clear to me. When saying "this module", do you mean "SafetyPatch" or "MagiskHide Props Config"?
[Magisk] Didgeridoohan:
You're in the MagiskHide Props Config thread, so yes, "this module" means the one the thread is about...
[Magisk] rybshik:
and to disable "SafetyPatch" module as well?
[Magisk] Didgeridoohan:
Yes, like I said and as you've seen, the option to edit fingerprints in MHPC is disabled when you have it installed.
[Magisk] ripelag:
Can you please add fingerprint for Xiaomi Mi 9 Se Patch 2019-07-01
[Magisk] oslo83:
HUAWEI Mate 20 Pro

HUAWEI/LYA-L29/HWLYA:9/HUAWEILYA-L29/320C432:user/release-keys_2019-08-01
[Magisk] ashish1989:
Used this module, safety net pass is true for both, device is redmi note 5 pro, rooted with pie stock miui rom

PNB mPassbook app not working, magisk hide setting is also applied

Kindly suggest what to do now
[Magisk] boilerman92:
Redmi note 5 whyred

xiaomi/whyred/whyred:9/PKQ1.180904.001/V10.3.2.0.PEIMIXM:user/release-keys

security_patch

2019-08-05
[Magisk] Didgeridoohan:
That's off topic here... Take a look at these tips:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

If you can't get things working after that, post in the general support thread.
[Magisk] UnicFb910:
I installed the module and changed the fingerprint and now the phone keeps booting and dont turn on :(
[Magisk] Didgeridoohan:
Try the reset option:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module

If that doesn't work (there's a bug with it that I need to look at), remove the module manually, as described here (also delete /data/adb/mhpc/propsconf_late):

https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

Before resetting things though, please try grabbing the Magisk and Module logs, they could prove useful:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#logs
[Magisk] UnicFb910:
(I have a galaxy S6 with a custom rom and I changed the fingerprint to a s10plus android9)

I created a file using adb shell touch /cache/reset_mhpc and rebooted and don't works.

I removed the module, rebooted, and now the phone boots correctly.

I attached the logs, maybe there's a bug?
[Magisk] iPusak Gaoq™:
Xiaomi Mi A3

Xiaomi/laurel_sprout_eea/laurel_sprout:9/PKQ1.190416.001/V10.3.7.0.PFQEUXM:user/release-keys

Security Patch : 2019/08/05
[Magisk] Didgeridoohan:
Thank you. I'll make sure to add it to the list as soon as a small bug in resetprop is fixed.

For those interested: there is a limit on the number of characters a prop value may contain, of 92 characters (or at least there used to be, it may have been lifted for ro props). When Magisk sets a prop value from a modules system.prop file it uses the -n option of resetprop (without init triggers), something I also use in my scripts. Unfortunately there seems to be a off by one error when using -n, causing 92 character length props (like the Mi A3 fingerprint) to fail with a setprop error. Should be fixed in a future release...
[Magisk] Didgeridoohan:
You sure? From the logs it looks like you used a Pixel 3 XL print...

Anyway, there's a segfault when running resetprop on the fingerprint props, at least when checking them. It's possible that this is also the case when they're being set (which would explain your problem), but I can't tell from a stable release log. If you're so inclined you could install the Canary debug release and try again. That Magisk log would be much more verbose.

Why you're getting that segfault is another matter entirely, something that would take a little more testing since I have no idea what's causing it.
[Magisk] UnicFb910:
First I used a s10plus print, i formatted the phone, and retried using the pixel 3. With booth fails the boot

I'll try the canary debug release of magisk and i'll tell you thanks
[Magisk] UnicFb910:
Here you have. Log with Magisk canary channel debug installed.
[Magisk] Didgeridoohan:
Same issue there, but not much more info in the Magisk log... Something is going wrong when the prop gets set.

You could try moving the boot stage of the fingerprint props to late_start service. Might make a difference...

To test stuff, could you run these commands in terminal (with no fingerprint set in the module, of course):

resetprop -v ro.build.fingerprint google/crosshatch/crosshatch:9/PQ3A.190801.002/5670241:user/release-keys
resetprop ro.build.fingerprint
getprop ro.build.fingerprint

What's the output?

After that, could you reboot (to reset everything) and then run the same commands but change the -v option to -nv?
[Magisk] ToXiTe:
Viper4Android also breaks boot scripts. Any modules that make use of supolicy or magiskpolicy has a chance of breaking boot scripts
[Magisk] Didgeridoohan:
That might be true, but so far I've only seen reports of EdXposed causing issues with the Magisk boot process.

Not quite sure why you're posting this here though...
[Magisk] ToXiTe:
I spent over an hour trying to get MHPC module to work which ceased working after updating it few days ago. Finally, chose to disable Viper4Android, alongside EdXposed, which previously also had broken other modules. And the boot script ran.
[Magisk] Didgeridoohan:
And what about if you only disable EdXposed?
[Magisk] ToXiTe:
No change. post-fs-data script for MHPC doesn't run.
[Magisk] Didgeridoohan:
Could you provide the logs for that?
[Magisk] ToXiTe:
Attached
[Magisk] Didgeridoohan:
I notice you have riru-core still running. Could you also disable that along with EdXposed, but keep all other modules running? It would be interesting to see if it still fails after that.
[Magisk] jbarcus81:
Sorry if this has been covered.. But can this be used to get Netflix working? If your device is bootloader unlocked, especially the Pixel 3XL, you can't install or run Netflix even if you sideload. Is there a way to get this working using this script? If it matters, if you're unlocked, but running the Android Q betas, you can install and run Netflix perfectly fine.
[Magisk] Didgeridoohan:
Don't know... I haven't seen anyone report as to the actual details why that is an issue on some devices. If it was Magisk not being able to hide the bootloader state you wouldn't be able to pass CTS at all, so there's some other shenanigans involved (of course, it could still be connected to the bootloader).

If it's a matter of some prop or another being set to an offending value this module can help with that (the custom props function), but first someone would have to figure that out...
[Magisk] ToXiTe:
I did that too. Don't have the logs though. It still failed.
[Magisk] Didgeridoohan:
Ok. Thank you for the info.
[Magisk] jbarcus81:
I'll dig around and see what I can figure out. What I do know is that on Android P, if you're bootloader unlocked you cannot install Netflix. Even if you sideload, it will not run at all. The odd thing as I mentioned is if you're running Android 10, it works fine even with the bootloader unlocked. I'm not sure what it's checking or how. Somehow even with root being hidden and passing SafetyNet, and the Playstore stating device is certified, Netflix will not install or run. It's driving me insane.

Someone mentioned in another thread that;

I'm not sure what he means here.
[Magisk] Didgeridoohan:
If it's a matter of some system prop causing issues you could compare between Pie and Q. Run this in a terminal on each OS respectively, and then compare the outputs for any interesting differences:

getprop > /sdcard/props_<insert identifying name here>.txt

Running a logcat when trying to install/run the app might show something (don't know if anyone's done this yet).

Etc...

Spoofing the device fingerprint is the main purpose of MagiskHide Props Config... If that's the issue, picking a different device fingerprint might do the trick. Doesn't sound likely though, but worth a shot I guess.
[Magisk] jbarcus81:
I will get any and all information I can.. Amazing help so far!!

UPDATE: I'm working on getting the Props to compare, but here's a specific logcat of Netflix..

UPDATE 2: Prop Android P and Prop Android Q

I'm working on comparing the 2 now..

LogCat for Netflix on Q -- The attached image is the LogCat from Android P -- Added a second screenshot of the LogCat for Q and Netflix.
[Magisk] kurtextrem:
Hi [MENTION=4667597]Didgeridoohan[/MENTION], I hope it's ok to post this here and as you seem active, I hope we can find a solution.

Snapchat started a new ban wave 1 week ago and it now detects root, even with Magisk Hide and MagiskHide Props with Improved Hiding. What's especially curious is: It also detects root with Magisk Hide & Improved Hiding *inside* the app Island. Island creates a work profile and only apps you select will be in there. I did not install Magisk, thus root should not even be in there (root checkers don't detect root).

So somehow they are either escaping Island, Island is leaking root inside; or they found a way around Magisk Hide and the Improved Hiding. I use Snapchat to stay connected with friends abroad, but I'm also a dev, so I like to keep rooted. Do you have any ideas what the cause could be?

(magisk 19.4 latest canary, magisk hide props 4.0.3v57)
[Magisk] Didgeridoohan:
I have no idea what the cause could be... You'd have to use logcat, strace, or decompile the app to get a better idea about what's going on.

That's more than a bit off topic here though, so please use the dedicated Snapchat thread:

https://xdaforums.com/apps/magisk/discussion-snapchat-locked-accounts-t3922880

And don't put too much trust in the "Improved hiding" feature. It's a longshot at best and I only keep it in the module because there was once a single report of it actually being useful.
[Magisk] sliding_billy:
My wife's Pixel 3 (BL unlocked and rooted) never lost Netflix since it was still available. It just quit updating a few months ago. It never quit working all the way through 9. I updated her device to 10 yesterday using flash-all (minus -w) so Netflix remained. I didn't think to check it before changing the fingerprint to Pixel 3 Android 9 (to see if I can keep GPay working), but I did just check and Netflix is still working fine. My Pixel 3 XL did lose the original Netflix while on 9 since I was messing with some custom ROMs. At least one time, a TB restore of the Netflix backup from before updates quit continued to work without getting updates. The same TB Netflix restore failed to even open with or without data in the restore when I moved to HavocOS. I side loaded the last Netflix version on APK Mirror, and it worked fine and continues to on HavocOS (Android 9 of course). https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/ Play Store on PC shows both the P3 and Pixel 3 XL as not compatible with Netflix. I never had her phone on Beta 10, so I am not sure if it was any different.
[Magisk] Augustoandro:
Does this module prevent Xposed from detection from Safetynet as well?
[Magisk] Didgeridoohan:
No, it doesn't. Regular old Xposed cannot be hidden by Magisk in any way...

You could try EdXposed though since that apparently haven't shown up on Google's radar yet.
[Magisk] dyingearth:
Question, is terminal emulator necessary if I'm not going to be doing edit directly on the phone. I was able to use props while connecting to my computer via adb shell which brings me into the phone's shell session.
[Magisk] ipdev:
There was a surprise update for Pixel C last month.

Poco F1 was late to the update party, as normal.

Pixel phones and Essential PH-1 have been officially updated to Android 10.

I haven't been keeping up on all the changes lately.

Besides updated fingerprints, I also attached the (Pixel and PH1) prop.default and getprop from Pixel 3a XL.

Android 10 Pixel and PH1 boot images. (If anyone wants them.)

20190903-q-boot-images.zip GoogleDrive - Link

Cheers. :cowboy:
[Magisk] :
Can you add this to the official certified fingerprints list plox sar?

*From the stock ROM.

Cheers.
[Magisk] Didgeridoohan:
Running a Terminal emulator or ADB Shell is perfectly interchangeable. It's basically the same thing.
[Magisk] Didgeridoohan:
Thank you guys. I will make sure to include these in the next update.

But, I just wanted to let it be known that said update might be a bit delayed... I am currently quite busy with family, school and other matters. As soon as possible I'll make sure that both the fingerprints list as well as the module itself gets a long deserved update.
[Magisk] jcmm11:
Family? School? Other matters? Gasp! That sounds like, like - - - real life!!!

Just take the red pill ?
[Magisk] raiffeisen_hu:
I'm trying to bypass root check of my banking app (com.guidance.android.apps.raiffeisen.banklet) but since they've implemented a mobile token functionality I just can't get it to work. Other banking apps work fine.

I have frozen all root related apps (AdAway) except Titanium Backup, updated Magisk to the canary build, hid Magisk Manager, enabled MagiskHide, installed MagiskHide Props config, selected Xiaomi Mi A1 9.0.0 as my fingerprint, enabled advanced hide, implemented the UDS fix, removed Vanced and reinstalled YouTube (according to the logcat apparently there was a check for that) and I have even decompiled the apk to see what's going on. Between each step I've force stopped the app and deleted the data. When I disabled a module, I've restarted the whole system

During the check of the decompiled code I could determine that it uses Vasco's Digipass technology and logcat revealed that the app tries to access another Vasco product on the system. Also when there was no data connection, an error message popped up saying the service is not available. First I thought this was from the banking app's core but actually this was a Vasco error message. I have a feeling that maybe they have a list of banned devices, so if the root check fails once there is no way to be authenticated.

At this point I'm kind of out of options, so if there's anything I've missed, I'd be glad to try that.

I've collected and uploaded a bunch of logs here: ufile.io/zc22crpa

My phone is a Xiaomi Mi A1 with the latest LineageOS 16.0. RootbeerFresh returns all checks as passed.
[Magisk] Didgeridoohan:
[MENTION=10114432]raiffeisen_hu[/MENTION] Bypassing specific apps root detection is a bit too off-topic here, please use the general support thread or make a thread of your own (after first searching for any already applicable threads, that is).

Having said that, I tested the app and had no issues. With the app on the Hide list and the Manager repackaged it started without issue. If I removed it from the list it crashed at startup and opened a web page with this gem of text :D:

It is possible to hide from the app, but there might be something about your setup that simply can't be hidden. Could be your ROM.

If you haven't seen it already, this is a rather useful resource:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

But, you seem like you've done your research...

As already stated, please keep any further discussion in the general support thread or other more suiting threads.
[Magisk] raiffeisen_hu:
Yep, the app will startup normally, it does the check when you click on the first icon "Activate mobile token".

However you're right I'm gonna start a separate thread on this. Thanks anyway
[Magisk] MrBrady:
I'm getting the same issue on my Pixel 2 XL with Android 10, but not just with Netflix. Also with Moment Camera and Galaxy Wear. They don't appear at all when looking at the Play Store on the device. When looking at Play Store on a computer it says they're not compatible with my device.

The previous way to get around this on Our was to install this mod, clear data on Play Store and Play Services, then reboot. Doesn't seem to work anymore on Android 10.

Any suggestions?
[Magisk] sliding_billy:
In the case of Netflix, there is something going on with the Play Store being able to look beyond an otherwise masked BL unlock (custom kernel) and clear SafetyNet. In the case of the other apps, I don't know. I have been saying since the get go that there is an attestation failure being written like what happens with GPay. For now, that has been "fixed" with an SQL change to the db that holds the attestation codes, but nothing has popped up for the others. Have you tied spoofing your fingerprint back to Pixel 2 XL Pie and then checking? It also may just not be compatible with 10 yet and truly is not compatible with the device on 10 yet. Short of someone with a completely clean locked BL on the Pixel 2 XL and Android 10 checking the store, there is really no way of knowing that. Have you checked apkmirror?
[Magisk] MrBrady:
I haven't spoofed the fingerprint yet because Google Pay and Samsung Pay (for my Gear S3) work fine. Spoofing the fingerprint will at a minimum make Samsung Pay stop working.
[Magisk] sliding_billy:
I guess I am confused how spoofing back to 9 will caused either of them to fail unless 10 is what caused them to start working.
[Magisk] yxd0018:
installed busybox-ndk on magisk latest stable/debug version on AEX 6.6 rom.

Has error:

08-27 16:19:12.198 684 685 I Magisk : busybox-ndk: constructing magic mount structure

08-27 16:19:12.200 684 685 E Magisk : opendir: /sbin/.magisk/mirror/system/xbin failed with 2: No such file or directory

Root beer root check doesn't find busybox binary, so config module won't find props in sbin/.

Issue also filed at magisk source:

https://github.com/topjohnwu/Magisk/issues/1839

Anyone has any clue?
[Magisk] Didgeridoohan:
That unfortunately has nothing to do with either Busybox or this module. Magisk can't mount the system mirror, which means there's nothing to mount over when the modules are loaded. Could be a Magisk-ROM incompatibility or something else.

Can't quite remember at the moment if I've seen anyone being able to solve that particular problem. Search through the general support thread and the Magisk forum for similar issues and you might find something...
[Magisk] RokCruz:
Hey Man here again:

One Plus 7 Pro

OnePlus/OnePlus7Pro/OnePlus7Pro:10/QKQ1.190716.003/1909010630:user/release-keys

Security Patch: September 5, 2019
[Magisk] yxd0018:
Flashing older vendor and boot partition solved the issue. Don't know why.
[Magisk] Hyflex:
I can't seem to get SafetyNet to pass for Google Pay... my setup is:

Pixel 2 XL

Stock Android 9.0

Custom Kernel

Custom Recovery

Latest Magisk

MagiskHide enabled and Google Pay selected

MagiskHide Props Config set to Pixel 2 XL (Device Fingerprint)

What am I needing to try? I've gone through the main posts and I can't find anything that will help. Magisk itself shows a pass for both safetynet values.

I'd greatly appreciate some help!
[Magisk] CarbonGTR:
Have you tried clearing data and cache for Google Play Services and Google Play?