yashsingh1/xdaforums huggingface dataset:
[Magisk] Alekim91:
View attachment 4878801Hi everyone I have a problem, there are some apps that have a system of recognition of root as a example apps mobile banking, than the app cant be open...

I have hidden magisk root with hide magisk function but problem persist....

Now I have installed this extended rom (that is very good) and I ask to you if there is a way to force the hidden or a different method to hidden root.

Thanks to everyone
[Magisk] Didgeridoohan:
From what I can see there's nothing wrong with that (exactly the same as on my OP3T). [MENTION=4487388]jcmm11[/MENTION] will likey be able to say more though...
[Magisk] Didgeridoohan:
You're a bit off topic, but we're always happy to help here... :D If you're not passing the CTS profile when you check SafetyNet this module can help you, but otherwise you're going to have to go through some other loops.

If you've added the app in question to the Hide list and repackaged the Manager with a random name (in the Manager settings), and the app still is triggering it could be a whole number of things.

Take a look in the Magisk guide here:

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

If you can't get things working post in the General support thread with details about your device and the app.
[Magisk] martyfender:
Added logcat.
[Magisk] Didgeridoohan:
I only took a quick look on my way home and nothing really stood out (to me at least).

But, just to remove some variables: does it make any difference if you don't link the app to your sd card?
[Magisk] jcmm11:
Hmm. What's the output (as root) of each of:

echo ${PWD:-?}

echo $HOSTNAME

More to follow, that'll do for starters.
[Magisk] martyfender:
Screenshot attached, if I did those commands correctly?

I tried to copy and paste, but it would not paste into the terminal.
[Magisk] Lw00d:
\

pixel 3xl

rooted magisk 7.4.0, magisk 20.1.

did you ever get this to work. i am on the same boat. just updated to A10. if anyone knows how to get this to work. let me know .please.
[Magisk] martyfender:
I unlinked and moved the only app I have moved to external, GT Racing 2, back to internal and in Apps2SD settings, deleted the mount script for the second, EXT2 partition and rebooted. I had an error on reboot, of course that the second partition was not mounted.

The strange thing is that when I then entered props in the root terminal, I got the same old error in your last test module. I then recreated Apps2SD mount script, rebooted and your test module seemed to work again, just fine, without even moving the game back to external. very strange, indeed.

If I get a bigger MicroSD card, I may convert to adopted storage on this device instead. I just have never used it before so I am hesitant to do that. I do know that MM can't be on external, I'm not sure about the other negative of using it?

Thanks
[Magisk] jcmm11:
Ok. Now I'd like to see the output of the following. 2 sets of results. Rooted and unrooted. Just to make things a bit more obvious switch to a directory other than /. /sdcard should work just fine.

set|grep PWD

pwd
[Magisk] kamikaze702k:
Use to work but not sure what happened. Maybe the constant magisk updates broke something.

Same rom and kernel and device

Oneplus 7 pro

Aosip / Smurf

Tried activating the fingerprint as prior but no change in status of safety net

Not sure what how or when it occurred only just noticed I couldn't update an app then thought I check safety net and bang.

Tried the test3 zip too but no luck.

Any suggestions or help would be appreciated
[Magisk] martyfender:
sorry, I don't understand do I need to cd to that dir? even though I have been using Linux Mint Mate a couple of years, I am still not fluent in the terminal. Do you mean su in the terminal vs no su?

Not in order. Sorry, too tired.

thanks

Here you go.
[Magisk] jcmm11:
I can tell you what's happening. I can't tell you why. Logcat may have an answer.

We can also get rid of 'unreachable', but you'll no longer get your current directory as part of your prompt. We can also make this change only when running as root. Your choice.

What appears to be happening is that, only when running as root, it can't correctly read your current working directory. To be more precise it gets the current directory but precedes it with (unreachable). At a guess, and it's very much a total guess, it has something to do with the way Magisk is mounting system as root on your device (s). Is this happening on all devices? Are they all x86?

Like I said answers may be found in a logcat. You may need someone better than me to read it though, although I'll be happy to take a look.

The command "pwd" should just return the current working directory (p rint w orking d irectory)

PWD is a system variable that contains the same.

Let me know if you want to modify things to remove the error, and if so which way you want to approach it.
[Magisk] martyfender:
This happens on my New, Onn 8 Android 9, 64-bit ARMv8-A tablet and all of my Nextbook Ares 8A, Intel x86, Android 6.0.1 8" tablets. The output I gave you was from the Onn 8.

I did post a logcat a few posts back from it.

Is it only a cosmetic error? It doesn't appear to cause any known problems, unless that is what is causing problems with MHPC.

3 things all of these devices have in common is several apps that have apply on boot settings: Kernel Aduitor, L Speed, Apps2SD and Greenifys boot service.

And of course, the latest Magisk Canary and the modules, Busybox NDK, App Systemizer(Terminal Emulator), MagiskHide Props Config and Systemless Host for use with Adaway. The only app systemized is Greenify.

So I am not sure what to do, leave it or?
[Magisk] Didgeridoohan:
Let's address this before it's lost in this (rather interesting) terminal troubleshooting session.

Failing both checks means that there's a complete failure of MagiskHide (if it was the module you'd still pass basic integrity). First thing to try is to toggle MagiskHide off and on again (sometimes necessary after a Magisk update). Further troubleshooting:

https://didgeridoohan.com/magisk/MagiskHide#hn_MagiskHide_Issues
[Magisk] martyfender:
attached is the same file from one of my Nextbook Ares 8A, Intel x86, Android 6.0.1 tablets.

I use jackpal terminal, incorporated int Apps2SD and also the stand alone version. What about the settings in the terminal app: vt100, screen, linux, screen-256color and xterm?

it is set to the default, screen and, of course, there are other settings, the only of which I have changed, is font size.

Sorry for getting off topic here. If you know of a better place to move it, let us know? Or should we keep it here since it is of interest to you and others, especially since your module does use the terminal?

Thanks
[Magisk] kamikaze702k:
Tried this but no luck. Really unsure what's caused this. Maybe I should fully uninstall magisk and install again?

Edit

Tried uninstalling completely and reinstalled, still no luck, just a bit annoying, sorry I know it's not a module issue but possibly a magisk issue, will attempt to get this solved
[Magisk] jcmm11:
I think it's only cosmetic, although I can't be sure. We can try and track this down. To start try turning off the apply on boot stuff and see what happens. My guess for the most likely culprit is Speed Apps2SD.
[Magisk] kamikaze702k:
Managed to get both safety net passes but still can't get to install/update apps like Netflix, any suggestions?

Edit

Fixed it via edexposed
[Magisk] martyfender:
So I left a comma out, lspeed, Apps2SD are two separate apps. I already tried disabling them, will have to uninstall them and will test after work.
[Magisk] martyfender:
I have uninstalled all three apps, rebooted to twrp and deleted cache and dalvik cache and then rebooted. It was what I knew and suspected all along, the unreachable still happened and it was something that topjohnwu changed in Magisk some time back that caused this to happen, but I am not sure when and where it happened. This is in jackpal terminal emulator that is still installed.

How should I proceed now? I have thought about installing a very old version of Magisk to see if this disappears.

Thanks
[Magisk] jcmm11:
For tonight the only thing I can suggest is try core-only mode and see if that makes a difference. Based on what you mentioned is installed I'll be surprised if it does, but can't hurt to try.

If you want to try old versions try 19.1 ? If it works you can work forward from there to see where it stops working.

Beyond that I can still make it not show up (as mentioned previously).
[Magisk] Didgeridoohan:
Do you mean that you fixed the Netflix issue with EdXposed, or that SafetyNet was failing because of it?

If Netflix is still not cooperating, make sure that the Play Store is reporting certified.
[Magisk] kamikaze702k:
I fixed the safety net with your module, basic integrity was failing because of edexposed so I blacklisted the play store and Google services and Google framework now everything is fine, device certified, both checks pass, able to update Netflix

Initially I think it was the magisk updates and having edexposed installed broke both.
[Magisk] martyfender:
Uninstalling those apps and core-only mode did not help. The worse part of core-only mode is that the busybox ndk module is disabled, so get errors attempting to run root a terminal and MagiskHide Props Config test will not then run at all.

Since I have a twrp backup I could try what you suggest to not make it show up, if you don't think it will have negative consequences.

Screenshot attached.

Thanks
[Magisk] jcmm11:
Here you go. This Magisk module should eliminate the visual problem. Whether there's any real impact behind the scenes I don't know, but if there is this will NOT fix that.
[Magisk] martyfender:
That fixed it. I am at work so I have only tested during my lunch. In laymans terms, can hou tell me what changes you made in the file. Of course I can read it, but won't understand all of tbe command changes.

Thanks.
[Magisk] Didgeridoohan:
Google started detecting EdXposed recently, so that would be why SafetyNet suddenly started failing without the blacklisting workaround.
[Magisk] jcmm11:
There really aren't that many changes. I reordered a few things and made one small change. Here's the original code

if (( USER_ID )); then PS1='$'; else PS1='#'; fi
PS4='[$EPOCHREALTIME] '; PS1='${|
local e=$?

(( e )) && REPLY+="$e|"

return $e
}$HOSTNAME:${PWD:-?} '"$PS1 "

I rearranged the if statement like so, just splitting it out to individual lines. Easier to read.

if (( USER_ID ))
then
PS1='$'
else
PS1='#'
fi

Since things work correctly if you're not running as root I decided to just modify the root prompt code. So the code for a regular user simply got copied into that part of the if statement. For the root user I removed ${PWD:-?}, which prints the current working directory.

I removed $HOSTNAME for both since it's just blank on phones - actually it's not even defined (this file is basically a generic file copied from a Linux distro)

Finally I stuck the PS4 definition up front to keep things cleaner. So the final code is

PS4='[$EPOCHREALTIME] '
if (( USER_ID ))
then
PS1='$'
PS1='${|
local e=$?
(( e )) && REPLY+="$e|"
return $e
}${PWD:-?} '"$PS1 "
else
PS1='#'
PS1='${|
local e=$?
(( e )) && REPLY+="$e|"
return $e
} '"$PS1 "
fi

just FYI $e is simply the return code from the previous command. It'll appear blank if 0
[Magisk] VizricK:
Bank of America some how trips on this device only. (I can skip the dev warning, but it won't let me sign in. Unless I run your props values)

Pokemon Go is really sensitive with its constant updates I usually have to reactivate hiding and props.

(Currently during my lunch) unless I activate the 3rd option (don't know if you really designed it to do something ) but if I don't activate I get PoGo saying my device is incompatible. (Even while hiding Magisk from the game.)
[Magisk] martyfender:
I do not understand most of this brilliant work, but I will eventually try it also on my Nextbooks, as it has worked very well.Something in Magisk that topjohchanged recently in Magisk caused this. He said he could not reproduce.

Should I give him this again in a bug report or not? Is it an isolated case that just coincidentally happens on 2 of my devices? I am the only one who has reported this , so I may be the only one with this issue.

Thanks for all of your time spent on this, it is much appreciated.
[Magisk] flyingdavy:
Props not found

hello everyone,i use xiaomi 6 with A9 miui11 9.11.14

Because of failing to pass the SafetyNet CTS Profile check .I have installed Busybox and MagiskHide Props Config. But whether I install through the Modules, or from recovery,it doesn't seem to work.

When I called su with Termux and tap props It always show me not found. like

$ su

:/data/data/com.termux/files/home # props

/system/bin/sh: props: not found

127|:/data/data/com.termux/files/home #

props

/system/bin/sh: props: not found

127|:/data/data/com.termux/files/home #

and I cant uninstall or switch model through magisk by rebooting.

It seems like the magisk doesnt work. who can tell me what happened?
[Magisk] Didgeridoohan:
[MENTION=10321635]flyingdavy[/MENTION] Sounds like you have Core Only Mode enabled in the Manager settings. Other than that I would need to see the module and Magisk logs to say more.
[Magisk] flyingdavy:
thanks， you are right. I have core only mode enabled?
[Magisk] flyingdavy:
sorry I have closed core only mode enabled and used Termux edit xiaomi6 fingerprint. but still cant pass the cts:(

If i need to matching the Android security patch date.

I cant upload log . Always get bad request.I will try to upload it.
[Magisk] Didgeridoohan:
Questions:

Did you pick a fingerprint from the module? If so, the security patch date is included and automatically set. If you didn't, that's likely your issue.

Do you pass basic integrity? If not, you've got other issues than just a not certified fingerprint. Take a look here:

https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] flyingdavy:
Thanks again ,Yes I have passed the basic integrity but cant pass cts.

And I have two system in my phone with system separation.it can be the reason that i cant pass cts?
[Magisk] pmsoft:
I'm new to this module and my purpose of using it is to get my NVidia Shield games I bought on the play store. I own a Xiaomi Mipad which has the same K1 plattform as the shield and played these games before. There is Lineage OS 7.1.2 running on my tablet and I can pass basic integrity and cts. But in playstore I still cannot download Half Life. Could the reason be that the fingerprint is from 7.0 and I have 7.1.2? Thanks for the help.
[Magisk] Didgeridoohan:
You mean multi-ROM? I'm not familiar with that... Sorry. You might have to make sure that you set both systems up properly.
[Magisk] Didgeridoohan:
That kind of thing rarely relies on the device fingerprint. You might get lucky with the device simulation feature.
[Magisk] flyingdavy:
Ok, thank you any way.I will try to del one .
[Magisk] Avarast:
Mi 9T Pro (10)

Yet another Mi 9T print, this time the international Pro version. Essentially the same device as the K20 Pro, but it identifies as the international variant.

$ getprop ro.build.fingerprint

Xiaomi/raphael/raphael:10/QKQ1.190825.002/V11.0.1.0.QFKMIXM:user/release-keys

$ getprop ro.build.version.security_patch

2019-10-01
[Magisk] swour:
Samsung Galaxy A5(2017) fingerprint update:

Security patch date: 2019-11-01
[Magisk] Didgeridoohan:
Update to v5.1.0-v66

Bit of an update, fixing a few bugs and other fun stuff... Take a look at the changelog below.

A bunch of fingerprints have also been added and updated, so a huge thanks to the contributors for this update:
[MENTION=1682119]cortomalese[/MENTION]
[MENTION=5234347]Leonidas87[/MENTION]
[MENTION=7280276]ipdev[/MENTION]
[MENTION=9867603]Avarast[/MENTION]
[MENTION=4453960]swour[/MENTION]

Changelog

v5.1.0

Fixed issue caused by some devices toybox commands not working as expected.

Cleaned up the post-fs-data script to remove unnecessary strain from the boot process. Moved as much as possible to the late_start service boot script instead. Among other things, this means that there will be a reboot late in the boot process when using the configuration file during boot (see the documentation for details).

Added new script setting to execute the post-fs-data module boot script completely in the background (see the documentation for details).

Fixed some typos.

Various minor fixes and optimisations (which just means I can't remember exactly what I did and can't be bothered to look it up).

Added fingerprints for the Fairphone 2, Google Pixel 4 and 4 XL, OnePlus 7T and Samsung Galaxt Tab A WiFi. Updated fingerprints for the Essential PH-1, Google Pixel 2-3a (both regular and XL), OnePlus 6, 6T, 7 Pro and 7 Pro NR, Samsung Galaxy A5 2017 and Xiaomi Mi 9 Lite and Redmi K20 Pro/Mi 9T Pro. List updated to v66.
[Magisk] MrHomebrew:
Ill be uploading a few other device fingerprints. They are essential for a major release for a new device with twrp and custom rom.

Also fixes the Nintendo switch, etc.

I'll have them up asap and hope you can add the minor changes to a quick release.

Appreciate you taking the time with the last updated and the many changes, fixes and additional fingerprints
[Magisk] MrHomebrew:
Here are the working and tested device fingerprints I needed added the the module for a planned twrp and custom rom release. There are also 2 more but i wont have those just yet. The sooner these can be added in to the module the better. Thanks again for your great work.

Galaxy S10 Plus (10)=samsung/beyond2qltesq/beyond2q:10/QP1A.190711.020/G975USQU2ZSJF:user/release-keys__2019-11-01

(I will update the S10 Plus key as the beta continues and especially on the final release)

Nvidia Shield TV (2017) (9)=NVIDIA/darcy/darcy:9/PPR1.180610.011/4086636_1604.6430:userdebug/test-keys__2019-07-05

Nvidia Shield TV (2017) (8)=NVIDIA/darcy/darcy:8.0.0/OPR6.170623.010/3507953_1441.7411:user/release-keys__2018-12-05

Nvidia Shield TV (Pro) (9)=NVIDIA/foster_e_hdd/foster:9/PPR1.180610.011/4086636_1604.6430:userdebug/test-keys__2019-07-05

Nvidia Shield TV (Pro) (8)=NVIDIA/foster_e_hdd/foster:8.0.0/OPR6.170623.010/3507953_1441.7411:user/release-keys__2018-12-05
[Magisk] martyfender:
Does this have the fixes incorporated in the test502-3 that I am using now successfully? I am currently using service.d for bootscripts.

Thanks
[Magisk] Didgeridoohan:
There's a setting you can toggle so that the post-fs-data.sh boot script runs completely in the background. That was the only thing that seemed to work reliably in the multiple tests we did.
[Magisk] Didgeridoohan:
[MENTION=5234347]Leonidas87[/MENTION] Thanks. Fingerprints are h relatively easy to get updated, it just takes a bit of time to test (I test every single one). I'll take a look at those tonight.
[Magisk] CarbonGTR:
[MENTION=4667597]Didgeridoohan[/MENTION] Is a build fingerprint from an unreleased build that passes both CtsProfile/BasicIntegrity fine?

Im running the Android 10 Leaked build with Google Play certification. (Can install Netflix from google play) on my Nokia 6.1 Plus.
[Magisk] martyfender:
How can I do that since I can't get it to load without the error and log collection? I am reflashing test502-3.

Thanks
[Magisk] Scripted27:
Can you please update Whyred's fingerprint with the latest V11.0.3.0.PEIMIXM ?
[Magisk] Didgeridoohan:
Because you can now reach the script settings even with that error. That's also explained in the new error text:

https://github.com/Magisk-Modules-R...536d0609c4efdca12d/system/binpath/props#L2657
[Magisk] Didgeridoohan:
It's very rare that I go hunting for prints myself, they're almost all user provided. So:

https://github.com/Magisk-Modules-R.../master/README.md#please-update-fingerprint-x
[Magisk] Scripted27:
Si basically, what files do you need or props lines to update fingerprint ? I can install the latest global rom and extract what you need
[Magisk] Didgeridoohan:
It's all explained further up in the docs I linked you.
[Magisk] Scripted27:
Here the latest fingerprint for Xiaomi Redmi Note 5 Pro (Whyred) on Android 9 with November 5 security patch

ro.system.build.fingerprint=xiaomi/whyred/whyred:9/PKQ1.180904.001/V11.0.3.0.PEIMIXM:user/release-keys
[Magisk] Didgeridoohan:
If it's certified, sure. Post it and I'll test it out.
[Magisk] Didgeridoohan:
I just finished testing these and there'll be a quick fingerprints list update shortly. But, the S10 and the Shield TV Pie prints did not pass CTS when I tested. My one rule for prints on the list is that they need to pass CTS when

I

test on my devices...

You can still use them with the module though, by using a custom fingerprints list or a configuration file.
[Magisk] MrHomebrew:
I have been using a custom fingerprint list to test on my end. Ill keep in mind the 2 you mentioned that had issues. The S10+ is still in beta and only just lost netflix in the store. As soon as the S10+ hits official ill get the fingerprint for you. Ill double check the shield tv pie one.

Appreciate the time and work put in. This is by far one of the most essential modules for magisk and rooting/custom roms ;)
[Magisk] Didgeridoohan:
Fingerprints list updated to v67

Quick update with a couple of fingerprints. Thanks to [MENTION=5234347]Leonidas87[/MENTION] and [MENTION=9395209]Scripted27[/MENTION].

New

Nvidia Shield TV 2017

Nvidia Shield TV Pro

Updated

Xiaomi Redmi Note 5 Pro
[Magisk] Didgeridoohan:
Thanks. It was actually both the Shield Pie prints.

Beta releases rarely have proper certification, and the Shield TV Pie prints you supplied both had userdebug and test-keys. That's also usually a sure way of knowing that they're not certified (I guess the OEMs don't want to go through the CTS verification process just for a test build).
[Magisk] CarbonGTR:
[MENTION=4667597]Didgeridoohan[/MENTION] Here you go. Nokia 6.1 Plus's Android 10 Build Fingerprint.

Nokia/Dragon_00WW/DRG_sprout:10/QKQ1.190828.002/00WW_4_070:user/release-keys
[Magisk] Didgeridoohan:
I can of course try to find it though trial and error, but it would be a lot easier for me if you could also post the security patch date for that print. Thanks.

Edit: Nevermind... I found the relevant forum thread. It's October 1st.
[Magisk] Didgeridoohan:
Fingerprints list updated to v68

Thanks to [MENTION=10122765]CarbonGTR[/MENTION] I could do a quick update of the fingerprints list and add the Nokia 6.1 Plus Android 10 print. List at v68.

Updated

Nokia 6.1 Plus
[Magisk] CarbonGTR:
Oops sorry. Next time I update the fingerprint I'll mention the security patch date:p

It's November 2019. Not October 2019.
[Magisk] Didgeridoohan:
Ok, thanks. If it's November I'll update the list. But, interestingly, for this particular print it doesn't seem to matter... Tried several different dates and they all pass.
[Magisk] Didgeridoohan:
I doubt you'll have any luck just changing the fingerprint. There'll be other signs of a "Custom OS". If you pass SafetyNet, you've added the necessary apps and services to the Hide list and also hidden the Magisk Manager and you still can't get things working, there might be some prop values you can change to pass detection. That you can do with the "custom props" function of the module.

But, I have no idea what those props could be, so the best place for you to keep discussing this would be threads like Microsoft Intune Company Portal or your ROM's thread (in case there's something specific about the ROM that's being detected).
[Magisk] margalvezsimarro:
Issues at boot stage

Hello, I'm using device HUAWEI P9 Lite (7.0) with custom ROM RR 6.2. ctsProfile isn't being passed since magisk v19.1 so I tried this module. It installs correctly but can't use it. Here goes some screenshots. Tried enabling background boot script, changing both boot stages... Nothing is working. Log is attached. Thank you in advance. I'm NOT using Xposed btw
[Magisk] Didgeridoohan:
As far as I can see the late_start service mode doesn't execute at all on your device. That's not an issue with the module, but your Magisk installation. Try reinstalling Magisk and see if things start working.