yashsingh1/xdaforums huggingface dataset:
[Magisk] chooks06:
Apologies that I can't offer a solution but I'm curious. The K20 should be running Android 9 if I remember correctly. Even with Android 8 there were issues with Xposed, but mainly could be resolved or had workarounds.

With Android 9 (pie) most users would be running riru, Ed Xposed (yahfa or {can't remember the other variant}).

I don't use Xiaomi but EM11 would be based on Android 10?

Best regards.
[Magisk] cohenelad:
Hi [MENTION=6323980]chooks06[/MENTION]

Yes, 11.2 is based on Android 10.

Also, I have update my post as I was able to find solution and managed to run my banking app once more
[Magisk] zgfg:
There was a month ago or so a post where user had to remove Titanium, because his banking app concluded that phone was rooted because it found Titanium app installed.

And I think once it was that presence of Quarantine app yielded another app to conclude that phone was rooted

So Magisk does not hide particular apps from the list of installed apps - btw, it would be a question which apps to hide, expanding the list based on new apps on the market, user reports of which apps are causing troubles to their banking apps, etc.

Magisk only hides the Magisk itself (by ignoring root requested from the apps you want to hide the Magisk from) and its own Magisk Manager (by repacking it and changing its name)

Maybe there is a Magisk module where you can see all installed apps and check which of them have to be hidden (not sure would it be possible and how - definitely such a module could not repack and rename each such app to hide it the same way as MM hides itself through repacking and renaming)

Hence it remains to users to find out if presence of certain apps raises a red flag to their various banking and similar apps, and to remove them - just like it is described in the Magisk troubleshooting guide
[Magisk] JudgeDread11:
If using edxposed you can use sudohide to hide apps from other apps. (Including magisk manager without repacking).
[Magisk] PoochyX:
For some reason I can't get Sudo hide to work for me, with edxposed manager with sandhook or yahfa on android 9 moto G7 play (which version are you using)

/09/[emoji645]/[emoji725]/
[Magisk] chooks06:
Happy to hear you got it working! Cheers!
[Magisk] lorsch:
Hello. I encoutered an issue with the Magisk Manager that I couldn't find any information about.

I don't have the option "Tap here to check SafetyNet" showing. I should be interjacent the two checkmarks confirming that the latest versions for Magisk and Magisk Manager are installed and the advanced options, but there is no option available. I flashed Magisk on my S4 mini using TWRP, one time with AOKP (nougat), one time with AOKP (pie). In both cases the result is the same. What could possibly the reason for this? I would appreciate some help.
[Magisk] Didgeridoohan:
Have you installed Gapps? Google Services are necessary for SafetyNet...
[Magisk] lorsch:
No, and I don't plan to. But I realized now that I need MicroG.
[Magisk] cognitivedissonance:
Any other Schwab Bank users get the app working again? All my other CC and banking apps still work properly, but Schwab constantly throws me an error and won't let me log in. I assume they've found a way to detect root that the others haven't yet adopted. Been like this for a few months now.
[Magisk] BostonDan:
No problem here with Schwab. I have a problem with Fidelity though. I keep getting a "network" error, but it doesn't say it detected root...

Cheers,

B.D.
[Magisk] ktmom:
Do either of you have an ad blocking ap installed?
[Magisk] cognitivedissonance:
Interesting. That's similar to the behavior I experience with Schwab. Just tells me I have the wrong ID or password.

I do have AdAway, but I've tested Schwab when AdAway is disabled. Same result. Is it possible Schwab is looking for and detecting that AdAway is installed, even if it's not blocking ads?
[Magisk] ktmom:
You disabled ad blocking from within Adaway then rebooted? Also clear cache/data from Scwab app after rebooting.

Yes, it's quite possible an app is looking for other known root apps, Adaway, Titanium Backup, ect. Also other frameworks like (Ed)Xposed.
[Magisk] BostonDan:
I also have AdAway, but no problem with Schwab. I'm also using Google pay rooted and have BusyBox installed.

Cheers,

B.D.
[Magisk] cognitivedissonance:
Yep, disabled adblocking in AdAway then rebooted, force stopped Schwab, cleared its data, even uninstalled, rebooted, reinstalled.

I have OEM Unlocking disabled too, Magisk manager is hidden (named Management) and I have Schwab selected in Magisk hide. Only Magisk modules I have are Systemless Hosts and BusyBox for Android NDK.

My root apps include LP, titanium backup, EX Kernel Manager, MiXplorer, AdAway and Simple Reboot. Is there a good way I can hide these other apps from Schwab?
[Magisk] ktmom:
There is a write up on hiding root from apps here.
[Magisk] ipdev:
Like others have mentioned, the best would be to use customization via magisk.

Between modules and/or script files, you can do almost anything systemless.

It takes some reading and learning but, eventually you can figure out how to make something work for you.

[MENTION=4667597]Didgeridoohan[/MENTION] 's guide Link is a great source of knowledge, tips and tricks.

The Magisk Documentation Link will come in handy if/when you try to make your own modules and scripts.

OT - Non Magisk way.

If TWRP can mount (decrypt if your encrypted) system then you can simply mount system and make the changes when booted in recovery.

TWRP includes vi editor and [MENTION=4544860]osm0sis[/MENTION] has a nano editor Link that I've used a few times in recovery. Normally I just mount system(or the partition I need to mount) then use adb to pull/push a file or adb shell to remove/rename files.

I'm not a Sammy guy so, I do not know if it will cause problems with knox or something else by editing system files in recovery. Best to check in your device thread about it first.

It defiantly breaks the OTA compatibility on (Nexus) Pixel devices.

Cheers. :cowboy:

PS.

Sorry all for the OT bit. :o
[Magisk] sq_dev:
There is some rework from android 9 to android 10. I see the rework on S9 G960F A10 and Note 10 N976U.

This two devices are not system_root devices and take not the same bootup steps as S10 exynos devices.

Thats the problem: https://source.android.com/devices/...uage#implement-dynamic-partitions-new-devices

I hope the MAGISK peoples find a way to rework the init part. The new thing is the dynamic mounting.
[Magisk] Didgeridoohan:
John's aware of this, but if you look at more of the Google documentation there's stuff showing that they are not...

If you look around you can find both of these statements:

Can't say anything so far about how John will deal with this, but like I said he's aware (I only know about the above quotes because of an internal discussion about this).
[Magisk] DaveX2012:
Hide Magisk Manager

Does anyone know why i can't hide magisk manager? After trying to hide magisk manager. After "Hide Magisk Manager", app keeps prompting to upgrade to full Magisk Manager.

logs.
[Magisk] ktmom:
Are you using manager 7.5.1?

Could you try with the Canary release?

There was a issue that was closed:

https://github.com/topjohnwu/Magisk/issues/2211
[Magisk] The War Profiteer:
How can I revert this ugly design without losing any new features? :/
[Magisk] ipdev:
I wasn't aware that the s9+ was updated to dynamic partitioning.

When I did a quick check last night, it looked like the s9+ was originally released with 8 (SDK26).

SAR was only mandatory for devices that shipped with 9 (SDK28), so I assumed the update to 9 and 10 used the easier path of updating.

Plus I couldn't find a factory 10 rom to download, so I couldn't pull the prop files to have a good look.

All Android 10 roms are system-as-root. The reason older device are being brought up to SAR mostly 2SI (two-stage-init).

Partition Layout source.android - Link

I'll have to look again but, I do not remember Dynamic Partitioning being set as mandatory yet or if it will be.

Android 10 Release Notes source.android - Link

There would have to be a way to modify the super partition since the DPU(OTA) would be able to trash and resize the groups of the super partition.

I haven't been following along too closely on it.

Thanks for letting me know about Samsung. :)

Cheers. :cowboy:

PS.

If you have a link (that will not take hours or require a login) for an s9+ 10 rom, please let me know.
[Magisk] seemebreakthis:
Seems like this "UBS Access" was successfully detecting the presence of Magisk Manager even with "hide Magisk Manager" enabled thereby randomizing the package name.

Reason I found out, I decided to try the app again after noticing the latest canary build of Magisk Manager has undergone a major revamp. Lo and behold I could use "UBS App" once again.
[Magisk] marquelito:
How? I download it to test, and can open no problem. The app starts a pop up message? Or just dont start? Before i hide in magisk it fc , then hide and got ok
[Magisk] DaveX2012:
yes manager 7.5.1 i did try canary also same results.
[Magisk] dcarvil:
To switch to canary, download Magisk Manager from https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

Nevermind, I misread your message.
[Magisk] Conan851:
I have a problem, bank application, root detected, how to solve it?
[Magisk] ktmom:
https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] Conan851:
I have hidden it, but suddenly it was discovered. Maybe something is wrong? What should I do?
[Magisk] ktmom:
All the troubleshooting information available is linked in the document I sent you to.
[Magisk] BeansBeanson:
Missing the option to verify safetynet in MagiskManager now??

I was stuck on this yesterday, but today after successfully patching a recent LOS16 nightly so I can set up micgroG, I no longer see the option in MagiskManager. I don't remember what I had done in the first place to get it to show.

I do have Nanodroid setup, and MicroG is giving me all green checks. What am I missing?

Thanks!
[Magisk] RandomPooka:
Bottom center button that looks like a shield. SafetyNet is the top right option.
[Magisk] iwanova:
Provide log and more detail, please.

Also, I have a same problem. There's one of a banking app that now can detect magisk, even with magiskhide and safetynet enabled.

So, here's the app: https://play.google.com/store/apps/details?id=src.com.bni

And I've provided the log. I hope it helps: https://drive.google.com/file/d/1-39QctEhPm1UK2cGWwt03sxLTwwWSDpJ/view?usp=drivesdk
[Magisk] Didgeridoohan:
Every single one of those posts went through... :D

Anyway, I tested that app with the current Canary debug build (hidden Manager) and had no issues hiding root from it.

First thing: have you repackaged the Manager with a random package name and a custom label? If not, try that. If you still can't get things working take a look here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] BeansBeanson:
I know the buttons you mean, I think I had them on a previous install, but I don't have them now.

Turns out I had wifi off and Magisk wont show the "Tap to verify SafetyNet check" when wifi is off.

Still gives me the "SafetyNet API Error" though.

I'm concerned that I don't actually have root. This is what my logcat shows regarding Magisk

$ adb logcat | grep "Magisk"
02-02 02:25:01.468 613 2601 I Magisk : ** boot_complete triggered
02-02 02:25:03.454 613 3021 W Magisk : su: request rejected (10111)

Is there a separate step to gain root with Magisk??

My setup is:

OnePLus 6t

lineage-16.0-20200123-nightly-fajita-signed.zip

Magisk-v20.3.zip

NanoDroid-22.5.1.20200102.zip

twrp-3.3.1-1-fajita.img

MagiskManager-v7.5.1.apk (flashed this over the installed version to try and fix)
[Magisk] iwanova:
Deleted
[Magisk] Didgeridoohan:
As far as I know, MicroG doesn't work with SafetyNet (but I don't keep up to date with the development of MicroG, so that might have changed).

That rejected message just means that an app was rejected superuser access. You can see which one in the su logs.
[Magisk] iwanova:
Just realized this feature exist lmao. I changed my package name and it works. Thank you.
[Magisk] jenslody:
You are right, microG still does not pass safetynet, but NanoDroid does not necessary mean the user uses microG.
[Magisk] BeansBeanson:
I am looking to use MicroG to have a google free environment. Should I not expect to pass SafetyNet with MicroG installed?

---------- Post added at 07:22 PM ---------- Previous post was at 07:18 PM ----------

Should I read that as MicroG is likely to be causing the SafetyNet API error, or that MicroG has nothing to do with SafetyNet?
[Magisk] jenslody:
Google changed the way safetynet works, and as it is not documented (obviously) it's not easy to fix:

https://github.com/microg/android_packages_apps_RemoteDroidGuard/issues/24
[Magisk] GG67:
Hello,

I tried to root my new Galaxy A71 using the method described here: h t t p s: //androidleaker.com/how-to-root-samsung-galaxy-a71-with-magisk-method-no-twrp (sorry not allowed to post links yet)

The key combination to boot not root at the end (power + volume-up) does not seem to work for me. And some video on youtube seem to confirm. So I used volume-down and power to start reboot and the volume-up alone during boot. But this results in my phone entering a boot loop, and I don't know any way for diagnosing the reason for this. When letting bot it without keys it actually boots but with magisk being disabled.

The description on the page does not exactly matching my phone in other areas as well, as for example I need to push volume-up shortly for download mode, and not several seconds as described which actually triggers another behavior.

But maybe just Magisk is just not supporting the A71 yet (I know this has nothing to do with the example of the download mode above ;) ), as it was released very recently ?

Any help would be largely appreciated

P.S.: I rooted a Note 10+ 2 weeks ago with a similar procedure (also with some minor flaws) with no problem.
[Magisk] ktmom:
I did a quick search but since this device is so new, there's not a lot of information out there. Are you sure this is an A-only system-as-root device? That would be the reason to install Magisk to the recovery partition. If it has A/B slots, then it would install to the boot.img.

If you're not sure, instructions are here.

If the device is a A-only system-as-root, then you might want to try the Canary release.
[Magisk] BeansBeanson:
deleted

---------- Post added at 02:18 AM ---------- Previous post was at 01:58 AM ----------

Thanks for linking to that. Super helpful actually. My interpretation is that there is nothing I can do to fix it and I should just wait until the fix comes out then right? Does that mean no one running microg can pass safetynet??

How important is it for safetynet to pass in order to run microg? Is it an app by app basis, like most apps will work but some higher security apps, like a banking app will not?

I haven't fully set up this phone yet and switched over to it as my daily since I've been unclear on how important all this is for day to day use
[Magisk] guest4711:
All my devices don't pass safety net because I don't install g-apps nor microg. (I'm using unified nlp only.) But all banking apps I need work flawlessly. Google pay would not work but I don't care about it - I don't like to tell BigBrother where and when I'm paying...
[Magisk] vikd007:
Solved now, it was edxposed causing the issue & sometime cts fail too, but found solution in xposed thread
[Magisk] sq_dev:
Links:

https://samsung-firmware.org/

https://www.sammobile.com/firmwares/

Cheers
[Magisk] GG67:
Thank you very much for your reply. I checked with ADB and it looks like an A-only system as "getprop ro.build.ab_update" returns "false". But "getprop ro.build.system_root_image" returns nothing.

Also, but I may be wrong, I would expect magisk to be installed into the A-partition on a A/B system just to have no effect, not causing any boot loop due to that, right?

I will now give the canary release a try

---------- Post added at 07:57 AM ---------- Previous post was at 07:42 AM ----------

Short update, I just installed the canary release manager and it reports the system as being nor A/B System nor SAR. I assume this is inline to my outputs in adb shell where getprop ab_update returning false and system_root_image returning nothing, i.e. not true. But I'll give it a try anyway
[Magisk] 骆家峻a:
I ask my magisk is refreshing, how to solve it, my Android is 10
[Magisk] GG67:
Unfortunately same result, except that with the canary release it enters boot loop all the time even if booting from power-off with no key combination. I tried several times making sure I followed the instructions correctly.
[Magisk] Didgeridoohan:
I wouldn't be surprised if you're seeing the same issue that Samsung A51 users are experiencing (and most likely future Sammy devices as well). Take a look here for some details into what they're discussing in the A51 forums: https://xdaforums.com/galaxy-a51/how-to/guide-how-to-root-samsung-a51-sm-a515f-t4032389

Basically you can't boot the device without having it being properly AVBv2 signed, and that causes issues when you try to install Magisk...

No idea if this is something that [MENTION=4470081]topjohnwu[/MENTION] will even try to address (it might not be possible to create any kind of general solution), so for now you might have to try to get the ball rolling yourself in the A71 forums (that at the moment are very quiet unfortunately).

I'm no dev, so please don't ask any technical followup questions. :D
[Magisk] ktmom:
Hi, there is not enough information to help you in this statement. Please provide information as to what device and additional description about what is not working.

My guess is you have a boot loop. That is when the device stays on the boot logo and will not fully boot up.

There is lots of information here.

I am gathering that English is difficult for you. Feel free to use an online translator.
[Magisk] GG67:
Thanks for this information. Loks like you are right as the A71 image also comes with vbmeta_samsung.img which cannot be patched. So I guess I will have to wait for TWRP for the A71
[Magisk] kamikaze702k:
New ui also doesn't show modules that need to be updated, you need to manually check the modules from the list and find the updates then install then, plus the screen flickers when attempting to update modules too.
[Magisk] nonsub:
WIFI unusable with Magisk :(

Hi. Using Samsung A320F (DS.)

Issue seems to be reported by others as well. I've tried Lineage and stock ROMS as well as trying 19.x versions. WIFI get's switched off and cannot be turned back on.

Are there any solutions to this?

Thanks!
[Magisk] bagarwa:
adb access to /data/ blocked in Feb patch of Android 10?

I typically adb push the magisk zip to /data/ and then flash that zip in twrp.

But today, after flashing the Android 10 February patch, the adb push to the /data/ folder kept failing, with "permission denied" error. I cleared the adb debug permission from developer options and granted the permission again; and still the same error.

I did a local patch of the stock boot.img to create the magisk_patched.img and flashed that from bootloader and that worked.

So, this post is more to do with my curiosity - did Google block adb access to /data/?
[Magisk] kamikaze702k:
Anybody know what version of magisk manager was before the new ui interface one, I can't take this new ui anymore it's getting on my nerves massively. Thanks
[Magisk] BillGoss:
7.5.1
[Magisk] kamikaze702k:
Thanks man, gone back to that, what a relief
[Magisk] BeansBeanson:
Should magisk be flashed on both A and B slots?
[Magisk] thaiminhai:
HI all

Please guide me to root S9+(SM-G965F) with android 10 room G965FXXU7DTAA
[Magisk] amg314:
https://xdaforums.com/galaxy-s9/how-to/root-galaxy-s9-s9-official-stock-8-0-t3843098
[Magisk] side:
Good evening [MENTION=4470081]topjohnwu[/MENTION]

i am side, the official maintainer of jfltexx (samsung s4). The ROM has got the SAR philosophy enabled, android 10 rom boots fine but i have issues with magisk.

TWRP flashes the flashable magisk zip

zip recognizes the SAR

but when i be back to runtime, magisk manager says that magisk is not installed.

i talked with dees_troy for a while and we finally said that its not TWRP issue but magisk.

What can i do for u in order to debug that thing ?

Thanks
[Magisk] ktmom:
It looks like you opened an issue on the Magisk GitHub. I'm sure it would help to attach logs from installing and booting using the Canary debug build of Magisk.
[Magisk] side:
yes i also opened an issue to github. i can delete this post or github issue if u want.

ok i will try the canary build.

PS

Using the latest stable flashable, log is clean saying that magisk flashed successfully
[Magisk] ktmom:
No worries. I was going to suggest you open a GitHub issue and you had beat me to it [emoji106]
[Magisk] side:
updated my github issue with recovery log.

i wont attach logcat since there is no app crash on runtime. (or u can ask for it if u want)
[Magisk] thaiminhai:
It not working in android 10.
[Magisk] hinxnz:
NVM
[Magisk] tempe222:
Is there a way to hide Magisk from the Citrix Secure Hub app? I need it for work. In Magisk hide, the app doesn't appear (any more, it used to appear in older Magisk versions 18.X last year).
[Magisk] wilsonhlacerda:
Hi Side, I'm running S4 Active I9295 with LOS16 Android 9.

I've already experimented similar problems with Magisk 20.x

I remember to see another Magisk users with other devices facing the same problem (here in this thread, some time ago)

The solution to me and them was to first flash Magisk 19.3 (or 19.2, 19.1, I'm not sure). It installs fine. And then self upgrade it to Magisk 20.x. This way everything goes fine.

Maybe this information can help you/ [MENTION=4470081]topjohnwu[/MENTION] to debug and easily solve the problem.

Just to let you know, [MENTION=4470081]topjohnwu[/MENTION] typically do not check this thread here. Sometimes he pings on the Canary one. Better report and keep in contact with him on Github.

Besides that he has some requirements for bug report: to try with the canary debug version, that is on the development edge and gives additional log info. Check its Github.

Thanks for S4 LOS and good work.
[Magisk] angelalex1924:
Hi I want to ask if i can play pc games in nvidia shield(ex call of duty modern warfare, gta v, pubg etc) without having my pc open or have nvidia gpu.
[Magisk] garylawwd:
Completely off topic this is a magisk thread why are you posting that here?
[Magisk] angelalex1924:
Sorry I realized it.. I searched for nvidia shield topics and it show that. I am really sorry
[Magisk] AmbientChaos:
Is Magisk boot image patching different from TWRP installing

I have a noobish question. But I'll try to be clear and concise. Basically, I would prefer to have root. In the past I just flashed Magisk systemlessly using TWRP. However, currently my device has no TWRP yet. It's an Android 10 device, also it was recently released.

What is the difference between

A) using TWRP to flash Magisk systemlessly

B) using Magisk manager to patch the boot image, then flashing with fastboot.

If both are the same, i.e. both are systemless, have the same features, that's great, then I have no problems.

But if boot image patching is not as good as flashing systemlessly using TWRP, I would like to know. I don't want to flash the boot image, then *if* TWRP is ever released, have issues in the future. For example needing to manually patch the boot image every time to update Magisk, or not being able to take OTA's, or not being able to remove Magisk because it's not systemless (I don't know, just an example)

Basically, I want to know if boot imaging patching is a stopgap measure and not as good as TWRP flashing. Should I patch my boot image now or wait until TWRP is released (if ever) to root.
[Magisk] Didgeridoohan:
[MENTION=5502678]AmbientChaos[/MENTION] It's the same.