yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
So latest 'N/A' still appears? Only greyed out Hide App option fixed? Or other??? PW
[Magisk] zgfg:
That's probably the cause of your troubles.

You need to understand that changing Update channel does not immeditely switch from Stable to Canary. or vice versa.

After changing the Update channel in settings, you have to install the corresponding new apk, and then the Magisk itself.

Update channel setting should actually just help you, pointing to the right channel for the installation from Magisk app.

And to have a notification when an update comes to your 'new' Update channel

But I think there is something messed up in v22+ with Canary json file, and if you only swich the Update channel from one to another, I'm not really sure where from would it really look for the stub to start hiding the Magisk app

Anyway, now it works for you, good

Btw, I didn't play with Hide Magisk app for long time, but I tested now with Wb2060 Alpha, and his default name for the hidden app is Settings - IMO, one more way to ensure hiding the Magisk from banking apps and so
[Magisk] koberulz:
Oh, yeah, sorry. That section updated. Don't have the phone on me right now.
[Magisk] pndwal:
But the only way I can reproduce his 'Latest App N/A' issue is to select Custom channel (with no working json url, of course)! And I'm guessing Hide App option will be greyed out in John's builds in this case too (- my current @vvb2060 Alpha has update for offline stub, and still works as mentioned)... Otherwise, one or other app should appear.

Settings has been default name in John's builds for a while now too. Not a @vvb2060 exclusive. PW
[Magisk] pndwal:
Oh, I just realised he just said he DID have Custom channel set!!?

He'd replied to me earlier:

Still scratching head at this point...

...Now, re home screenshot request:

Aha! ...Now it's all clear. 🙃

@koberulz, App Install and Hide App require channel set to point to correct App or stub apk in John's Magisk builds.

Custom channel (if set) must also have Custom URL set, pointing to a properly configured json file containing file links. Selecting Custom channel w/o valid URL for json breaks App / stub (for hiding App) Installation.

Nb. w/ @vvb2060's builds, hiding App still works as these now use a local (offline) stub apk.

I'm guessing home screen is NOT actually the same now either...

I'm betting 'Latest App - N/A' has actually gone and App / stub versions show now, at least with internet connection. 😜

Wily fox caught... User was throwing his own red herrings! 😉 PW
[Magisk] HippoMan:
Thank you. I now have a clearer understanding of this issue. And I won't try to install the vbb2060 version via the Custom Channel, but rather, by uninstalling the current Magisk and then installing the vbb2060 apk.
[Magisk] pndwal:
Fun facts re. @vvb2060:

Regularly contributes to

- LSPosed Framework. (Interestingly, John Wu cut his teeth on / pioneered XPosed).

- LSposed AndroidHiddenApiBypass

- topjohnwu Magisk

- vvb2060 magisk_files

Created his own repo fork of topjohnwu/libsu on May 12.

PW
[Magisk] J.Michael:
Does vvb2060 / vvb20260 / Wb2060 / vbb2060 have a presence on XDA? Any chance these names will converge to a consensus?
[Magisk] zgfg:
He is wb2060 on Github:

vvb2060 - Overview

vvb2060 has 20 repositories available. Follow their code on GitHub.

github.com

XDA does not find under "@wb2060"
[Magisk] pndwal:
Thanks! ... May be too late now! 😜

So that'd be vvb2060!

Fixed my lazy copy-pastes. 😬

No XDA presence AFAICS. PW
[Magisk] HippoMan:
Regarding the vvb2060 alpha Magisk release (or however the characters "v", "w", "b", "0", "2", and "6" might be used and arranged): I downloaded the following and tried to install after uninstalling the v23 stable Magisk:

https://github.com/vvb2060/magisk_files/blob/alpha/app-release.apk

However, the install fails with this error:

% adb install app-release.apk
adb: failed to install app-release.apk: Failure [INSTALL_PARSE_FAILED_NOT_APK: Failed to parse /data/app/vmdl1485714559.tmp/base.apk]

If I "adb push" it to my device and try to install that way, it also fails.

Is there another location for obtaining this vvb2060 alpha version for download?
[Magisk] Homeboy76:
Can vvb2060 be used to patch the Google stock boot.img?
[Magisk] zgfg:
I don't know for Pixel (or what) but I patched with no problem my boot.img for Xiaoimi with A11.

Generally, it should work. His Alpha is about 15 commits upstream the latest official v23
[Magisk] zgfg:
I had errors before I uninstalled the Canary. Btw, I had also an error because of wrong downloading.

For your reference, attached the Alpha app-release.apk (just renamed).

Install the apk, switch Channel to Alpha, download additional resources if it asks and patch the image.
[Magisk] Wesley_NL:
i use old android 9 still, see image

ctsprofile failed ,

i know i probaly should update , but to redo all app settings exc.. is just quite alot ,and i domt know if i can root android 10, without problems ,
[Magisk] HippoMan:
This one worked. Thank you very much.

Apparently, the one from the github site that I referenced above is faulty. Where did you find this one?

I'm still on A10, and so I am able to run TWRP, and I therefore was able to use the direct install option. No manual patching was necessary.

So far, so good on this version.

PS: The one from the github site is microscopic compared to this one ("app-release.apk" is the one I downloaded from that site):

% wc -c app-release.apk Magisk-Alpha-1eb83ad8-23001.apk
120959 app-release.apk
10353541 Magisk-Alpha-1eb83ad8-23001.apk
[I]10474500 total[/I]

PPS: Never mind. I didn't download it correctly. I have to click on the "app-release.apk" link and then click on the "Download" button on the page that shows up. I originally just downloaded directly from that "app-release.apk" link, and I just got HTML.
[Magisk] HippoMan:
I ended up with the same result as one or more other people: using vvb2060 alpha Magisk with "Riru - Enhanced mode for Magisk Hide" did not make any difference with my banking app. It still detects root.

However, I have an idea that I will try when I get some extra time:

There is fork of TWRP called "OrangeFox" which allows dual boot to be set up on certain A/B devices. My OnePlus 7 Pro is one such device. I can install two instances of my OS on my device: one with the standard rooted Magisk v23.0, and the other with the vvb2060 "Magisk Lite", which might successfully be able to hide root for my banking app. I'll only run my banking app in the "Magisk Lite" partition.

The OrangeFox Dual Boot thing needs both partitions to be rooted in order to work. So Magisk Lite would still be needed in the banking partition, and maybe this will work.

By the way, I'm running this under Android 10. Not sure if that Dual Boot Orange Fox recovery will work on my device under A11. However, I don't care, because I have little or no desire to move to A11 for the time being.

Once I have time to test this, I'll report my findings.
[Magisk] zgfg:
More about the Lite experiment tomorrow
[Magisk] pndwal:
Answered, but nb. Alpha still has channels for stable, beta, canary synced with John's builds, so switching back should be easy. PW
[Magisk] pndwal:
Mmm. You still didn't say which Magisk; Public Stable / Beta or Canary build? Or What does evalType say?

However, I'll assume you're on a public build (stable/beta) as canary was already fixed at time of posting.

If N/A shows for evalType when check SafetyNet, you simply don't know if ctsProfile fails using Magisk test. You don't see basicIntegrity or ctsProfile pass because API for TEST was revoked. You can use 3rd party checker to be sure.

Fix for SafetyNet check is now merged in public builds also, so simple direct update from App (on Stable Channel) should resolve this.

In event of problems, if you have ADB Fastboot on PC working, or TWRP, you can simply flash unpatched boot image for your current ROM to fix bootloop, or a saved patched image for current Installation to restore current working Magisk root.

This invariably fixes 'your system has been Destroyed' / bootloop issues in connection with Magisk Installation, and user data remains intact. 🤠 PW
[Magisk] pndwal:
Just to check on basics (before assuming app detects isolated process mount, etc):

- Have PlayProtect Device is certified in PlayStore?

- Bank app in MagiskHide list, reboot, wipe app data (this order!). 😜 PW
[Magisk] m0han:
good info about dual boot set up on certain A/B devices. thanks. would you happen to know where i can see a list of such 'certain A/B devices'?
[Magisk] pndwal:
This:

https://xdaforums.com/t/recovery-du...ified-reborn-21-03-2021.4177865/post-83730471

Original Devs projects (MANY useful root associated utilities).

https://zackptg5.com/android.php

See notes here under DISCONTINUED OR HANDED OFF MODS:

Old thread:

https://xdaforums.com/t/recovery-du...official-twrp-for-oneplus-7-7-pro-5g.4066851/

Old GitHub:

https://github.com/Zackptg5/TWRP-DualBoot-Guac-Unified

🤠 PW
[Magisk] zgfg:
Hence I dared to test Wb2060 Lite 7717f0a6 (23001)

and installed its app-release.apk. It has 'all' Update Channels + Lite, but no more Alpha channel (?).

Patched my boot.img, flashed and rebooted.

Root and SafetyNet were ok

- I 'lost' all my modules, incl. Systemless hosts.

But Lite still has the Modules tab and for testing I successfully installed SSH from Repo - Lite installs to its own /data/adb/lite_modules folder

- Indeed, MagiskHide tab was 'inverted', all my apps that were previously granted root with the 'regular' Magisk (Stable, Canary, Alpha), now were ticked in here.

- Besides that Lite has its own modules folder, it also creates its own lite_magisk.db database

I was playing about an hour with Lite. Once I suddenly lost root (and Lite apk started to show Magisk as not installed), but after simple reboot, Magisk Lite was again up and running

At the end I installed back my Magisk Alpha apk and flashed my boot img previously patched by Alpha - since Lite had its own database and modules folder, when I rebooted, Magisk Alpha was properly back and running, not affected (modules, 'regular' MagiskHide apps) with my previous Lite experimenting (the same should also apply to Stable or Canary)

Edit:

@HippoMan, if you install dual-boot with one 'regular' Magisk and another Lite, they should not mess up between them.

However, dual-boot is maybe not-needed since Lite has its own modules, too
[Magisk] pndwal:
Good on you Maverick, for leading the squadron!

Interesting that modules can be installed in light of this:

https://github.com/topjohnwu/Magisk/issues/2406#issuecomment-634585257

Don't know if adding modules would break intended use to hide isolated processes (I understand it's the mountpoints of the modules themselves that 'leak', and allow su detection), or if that ability is there for experimental purposes.

I'd be interested to know results of @vvb2060's MagiskDetector app with this, and result differences for standard Canary, Lite w/ and w/o modules installed, w/ and w/o riru-unshare module (enable enhanced mode for Magisk Hide), especially on Xiaomi, which apparently cause problems for MagiskHide hiding Isolated processes where Pixels don't.

Guess sooner or later, someone here with a difficult Bank app case will test Lite / report.

Goose.
[Magisk] HippoMan:
Device is certified. Banking app in Magisk Hide. Numerous reboots and wipes.

Banking app itself (Chase) is known to be able to detect root, no matter what.

https://xdaforums.com/t/chase-app-always-detects-root.4099627
[Magisk] pndwal:
Interesting.

Can you run / check with @vvb2060's MagiskDetector app? - should at least narrow it down.

My bank app is not detecting root, but items 1 and 5 could be issues exploited for detection by other apps on my device / setup (MagiskHide is working fine, but not hiding these):

PW
[Magisk] zgfg:
Have you enabled MagiskHide for Magisk Detector?

I have the same results except that MagiskHide works for me (tested with Magisk Alpha)

Edit: With Magisk Lite: su no more found in the path, but checking MagiskHide option has dissapeared from Magisk Detector (?!)
[Magisk] Stillhard:
Try to use this Riru-MomoHider
[Magisk] centodue:
How can I check? Can I try to rename it? Or what other....

Using command said to me by J.Michael I found this:

find / -name su

/system/xbin/su

/sbin/su

/sbin/.magisk/mirror/system/xbin/su
[Magisk] HippoMan:
Mine has the same results as yours, except for item number 2. My second item says this:

"Test results: Magisk module modified at least one system file."

In any case, I have the workaroud that I mentioned a few pages back: to run the web-based version of my banking app on my device. With my bank, the web UI is almost exactly the same as that of the Android app, and no functionality is blocked. As I mentioned before, this renders the so-called "security" of the banking app to be totally useless.
[Magisk] HippoMan:
I just now tried that (installed via Magisk and rebooted). This had no effect on my MagiskDetector results.
[Magisk] Stillhard:
Make sure you've follow the guide there to set it up first

Such as adding the config(s) like:

su -c touch /data/adb/modules/riru_momohider/config/isolated
su -c touch /data/adb/modules/riru_momohider/config/setns

etc
[Magisk] pndwal:
Good point, slipped my mind. 😉

w/ MagiskDetector in MagiskHide list: other results same, 'Magisk Hide works fine' like you, on Alpha.

Good to know this can be hidden... May help some!

Could be a good sign.

Guessing it's likely su file in PATH is needed for this test. PW
[Magisk] 73sydney:
fwiw my time with successful new magisk + Ritu and a happy bank app was over early this morning, after about 3 days of no drama. Suddenly root started being detected again. From a little playing it was detecting via /proc/mount

After what root detection by my bank app did to my Google pay account last week, I unrooted early this morning until I can try something else

note: shelter did not work at all for my banking app.

This whole change is quite sudden, two weeks ago everything just worked...
[Magisk] HippoMan:
There's no mention on that site about doing this configuration by means of creating empty files which are named after the configuration properties. All it says (after describing those properties) is this:

"Note: Since 0.0.3, all features are disabled by default, you need to create a file named /data/adb/modules/(lite_)modules/riru_momohider/config/ to enable it."

I guess this actually means to create those files inside of that named directory.

Furthermore, the directory /data/adb/modules/riru_momohider/config exists on my device, but not the documented pathnames /data/adb/modules/modules/riru_momohider/config nor /data/adb/modules/lite_modules/riru_momohider/config.

I'm guessing that "modules/(lite_)modules" in that documentation actually means "modules OR lite_modules", even though that forward slash before the open parenthesis is the same character as the other pathname separators in that string.

Anyway, after creating "isolated", "setns", "app-zygote_magisk", and "initrc" files under /data/adb/modules/riru_momohider/config, MagicDetector now says that "su" does not exist in PATH, but it stll states that a Magisk module modified at least one system file, and that init.rc has been modified by Magisk.

And my banking app still says that it detects root.
[Magisk] HippoMan:
Shelter has never worked for my banking app, either.
[Magisk] J.Michael:
My idea of a "check" is "ls -dl filepath" in a terminal window (terminal emulator; command prompt). You can see from @DiamondJohn's screen shots that Mixplorer also shows enough detail.

Can you restore the original firmware and check to see if it was already rooted?
[Magisk] pndwal:
Interesting, you seem to have an extra 'leak'.

Could benefit from saving / checking MagiskDetector Log. It's fairly verbose... PW
[Magisk] HippoMan:
It contains a few dozen lines line this:

svc name init.svc.NAME-OF-SVC

... followed by ...

[ 06-02 18:54:29.341 13070:13070 V/ViewRootImpl ]
The specified message queue synchronization barrier token has not been posted or has already been removed

[ 06-02 18:54:29.342 13070:13111 W/.magiskdetecto ]
Reducing the number of considered missed Gc histogram windows from 409 to 100

[ 06-02 18:54:29.349 13070:18366 D/DecorView ]
onWindowFocusChangedFromViewRoot hasFocus: true, DecorView@5df1ac0[MainActivity]

[ 06-02 18:54:29.383 5705: 5705 W/detector_zygote ]
type=1400 audit(0.0:58253): avc: denied { getattr } for path="/data/data/io.github.vvb2060.magiskdetector" dev="dm-2" ino=10945386 scontext=u:r:app_zygote:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c164,c257,c512,c768 tclass=dir permissive=0

[ 06-02 18:54:29.383 5705: 5705 W/detector_zygote ]
type=1400 audit(0.0:58254): avc: denied { getattr } for path="/data/data/io.github.vvb2060.magiskdetector" dev="dm-2" ino=10945386 scontext=u:r:app_zygote:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c164,c257,c512,c768 tclass=dir permissive=0

[ 06-02 18:54:29.392 5705: 5705 I/AppZygoteInit ]
Beginning application preload for io.github.vvb2060.magiskdetector

[ 06-02 18:54:29.402 5705: 5705 I/AppZygoteInit ]
Application preload done

[ 06-02 18:54:29.405 5705: 5725 W/detector_zygot ]
Reducing the number of considered missed Gc histogram windows from 140 to 100

[ 06-02 18:54:29.418 5705: 5705 D/Zygote ]
Forked child process 5737

[ 06-02 18:54:30.871 13070:13070 V/ViewRootImpl ]
The specified message queue synchronization barrier token has not been posted or has already been removed

[ 06-02 18:54:30.888 13070:13070 W/Choreographer ]
Already have a pending vsync event. There should only be one at a time.

[ 06-02 18:54:31.798 13070:30052 D/DecorView ]
onWindowFocusChangedFromViewRoot hasFocus: true, DecorView@5df1ac0[MainActivity]

[ 06-02 18:54:37.161 5705: 5705 I/Zygote ]
Process 5737 exited due to signal 9 (Killed)
[Magisk] J.Michael:
I had guessed that the string "(lite_)modules" meant "modules" OR "lite_modules".

So I thought you needed another level of directories:

"/data/adb/modules/modules/riru_momohider/config/" OR

"/data/adb/modules/lite_modules/riru_momohider/config/"
[Magisk] Stillhard:
You have to clear the app's (MagiskDetector) data cache first and reboot.

MagiskDetector use a mechanism to keep the detection in data cache on boot
[Magisk] zgfg:
modules/modules must be a mistake but:

/data/adb/lite_modules

is a valid path where Magisk Lite installs the modules (see my post a day or two ago about shortly testing the Magisk Lite also from wb2060)

Btw, to pass Magisk Hide in Magisk Detector, you must (obviously) check-in/enable Magisk Detector app in your Magisk Hide list (see also my post about and the last night answer by @pndwal) - riru not needed here.

Probably, wipe the Cache/Data for Magisk Detector before retesting

Also, with Magisk Lite, Magisk Detector does no more find su in the path
[Magisk] Stillhard:
Just to point out a typo here:

"app-zygote_magisk" should be "app_zygote_magic"
[Magisk] pndwal:
Thanks for that.

I'd considered this, but had assumed detection app wouldn't do that to ensure realtime results, (unlike aim of bank apps), but no!

I can confirm at least results for init.rc are cached. 👍 PW
[Magisk] Mikoros:
hello, I wanted to report a root app that worked fine on 20.3 but no longer works since 20.4 and higher :

Téléchargez ES File Explorer / Manager PRO Apk 1.1.4.1 pour Android

ES File Explorer / Manager PRO - Gestionnaire de fichiers multifonctionnel prenant en charge tous les formats de fichiers. Avec ce programme, vous pouvez copier des données stockées dans .zip et .rar et travailler.Il existe de nombreux gestionnaires de fichiers dans chaque marché Android,

apktry.com
[Magisk] zgfg:
You may ask on its thread/site. Nevertheless, MiXplorer is a way ahead (and works fine with all Magisk versions)
[Magisk] DiamondJohn:
Should all this discussion about the beta/alpha of the new magisk lite (or whatever iots called) be moved to different thread?
[Magisk] wangdaning:
I would say given that John is gone and this whole sub-forum is his, everything new should be moved to a different development sub-forum.
[Magisk] zgfg:
This thread was General, and it included Stable, Beta and Canary versions - all three were maintained by TJW.

Now, when he started to work for Google, it is unclear when and from whom can we expect the new release(s)

If, then maybe from wb2060, and based on his Alpha version (upstream commits to Canary) - in the past he also provided certain important fixes and some of them were also available for pre-testing from his Github (I think, it was also his Alpha), before they would be incorporated to TJW"s Canary

Maybe this thread becomes obsolete in the future, frozen for TJW Magisk up to v23, who knows...

Magisk Detector discussion is about the general issues, certain banking apps that detect the Magisk. Magisk Lite is maybe in that direction (if wb2060 ever decides to release some kind of 'official' release)

Unfortunately, TJW long ago distracted himself from XDA and wb2060 was never a member here
[Magisk] pndwal:
And many thanks for suggesting this module!

I think MagiskHide is sorted, at least for my Xiaomi device (Stock RN8T, Alpha Magisk) 😛 :

A bit regarding configuration seems to be lost in translation on its GitHub, so did a little googling.

My setup:

- Install riru_momohider module

- Disable 'Riru - Enhanced mode for Magisk Hide', riru-unhide module (if have it)

- create an empty file named for each option used (I have all enabled), and place these in existing

/data/adb/modules/riru_momohider/config folder (no extension, mine have rw-rw-rw- permission)

[Options: isolated, setns, app_zygote_magic, initrc]

- MagiskDetector in MagiskHide list

- Clear MagiskDetector data

- Reboot

Nb. Only MagiskDetector items 1 & 5 (as per SS above) were being detected before this.

@HippoMan, I'm interested if this solution will solve item 2 detection for you, but guessing you may need to resolve this separately.

Also interested to hear if, with each MagiskDetector item undetected, anyone with Bank App detecting root has success with these... or it there are unlisted methods extant.

Hope it helps! 🎉 PW
[Magisk] pndwal:
Yes, many tested fixes for MTK in Alpha etc, before these were merged to John's Canary and public builds.

Agreed; this is probably the best place for now, especially given @vvb2060 doesn't seem to be active here, as well the fact that most of his working notes appear to be in Chinese.

Please note that his handle on GitHub and Twitter (although that account is fairly stagnant) is @vvb2060 (v v b 2 0 6 0), as has been noted recently. 😬 🤪 PW
[Magisk] pndwal:
🤔

Not sure what you mean here. PW
[Magisk] zgfg:
Ok, maybe there is no forum or something to report issues in ES File Explorer. But I thought, the problem is not on Magisk side (even if something changed on Magisk side - ES should keep up with), and that MiX is much, much better (at least, it already was couple of years ago when I switched from ES to MiX)
[Magisk] 73sydney:
Let me see if im reading you...

I am completely unrooted, so im trying:

flash magisk

flash riru

flash riru_momohider

reboot

create (touch):

/data/adb/modules/riru_momohider/config/isolated

/data/adb/modules/riru_momohider/config/setns

/data/adb/modules/riru_momohider/config/app_zygote_magic

/data/adb/modules/riru_momohider/config/initrc

MagiskHide MagiskDetector app

clear data for MagiskDetector app

reboot

So its not necessary to enable MagiskHide for banking apps etc? Or rename Magisk app?

I tried no hiding and hiding my bank app...didnt make any difference, utter failure

Also appears you cannot rename Magisk app name ?
[Magisk] zgfg:
Magisk Hide must be always enabled if you want to hide Magisk from an app seeking for the root. But that might be just the beginning (for some apps could be enough) - as you already listed the other possible steps