yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Further to point 4 in my post above, those who have followed recent discussion here about problems hiding to root / modified environment from apps (bank etc) due to isolated processes may be interested in this article from Sihan Goi, "CSG — cyber lead for the Singapore Government sector ", a "reverse engineer and penetration tester" regarding:

- what rooting is

- the Android security model based on sandboxing

- how root compromises model (sandboxing)

- implication of this for ability to reverse engineer applications

- interest of attackers, security testers and power users ( 😛 ) in root access for exploitation etc.

- software developer interest in root detection

- MagiskHide use in analysing mount points

- timing of Magisk un-mounting paths

- root detection methods leveraging Magisks inability to hide the mount points from remoted services (before Magisk Hide started to hide the paths)

- race condition problem

MagiskHide rebuilds: monitor logcat, inotify & ptrace methods

- reasons Magisk v18 and below may be more resistant to certain forms of root detection than newer builds using zygote ptracing

- zygote ptrace problem detecting isolated processes

... and more.

https://medium.com/csg-govtech/diving-down-the-magisk-rabbit-hole-aaf88a8c2de0

Many thanks to @phrichuk99 for this link! 👍

https://xdaforums.com/t/skygo-app-detected-root.4128933/post-84826153

👀 PW
[Magisk] pierre 3175:
Hello all,

I have a real pb with this app and its modules.

I own a redmi note 10, MIUI global 12.0.4 and android 11. Xiaomi cut the possiblility to record call, a native option on my old asus zenfone 2, ideal to record conference by phone. I found an apk that has this option, but when micro is off, nothing is recorded, more precisely, a blank file is created. I also found that this apk got a magisk module which allow the apk to record from line, and not from hp.

So I dl the last version of magisk, 23.0, and here comes the problem.

I can't find how to install the module. Where should stands 3 lines, top left, I have the word acceuuil (home in english), and there's nothing in parameters.

Shall I install a previous version, and which one ? What can I do ?

Whatever help will be welcome,

Thanks

Pierre
[Magisk] zgfg:
Look at your screenshot - you have no Magisk installed, omly Magisk app installed.

Without having the Magisk installed, you can not manage modules

Maybe you just installed Magisk app but not Magisk?

Did you install Magisk by flashing though TWRP or by patching the img and flashing (or nothingh of that, in which case you obviously don't have Magisk imstalled)

Or, you maybe had on your phone an older version of Magisk App or Manager (that you possibly hided/renamed/repackaged in your past life) and it prevents now your new Magisk App v23 to connect to the Magisk, its db, etc (that can be also a reason for the new Magisk app to display that Magisk is not installed)
[Magisk] pierre 3175:
I'm confused : I thaught that with the V23, only the apk was needed. Maybe because english isn't my native language ^^

I'll try to find it...

PS : and till now, it seems TWRP is unavailable for my new phone

PPS : now, I have that, but the 3 lines are still not there
[Magisk] J.Michael:
The "only the apk is needed" of newer releases of Magisk is as opposed to downloading older-magisk.apk, older-magisk.zip, or uninstall.zip. Now, you download the apk, and if you want one of the zip files, you rename the apk to the desired zip name.

Start by answering @zgfg: did you already have Magisk on your phone?
[Magisk] 73sydney:
Congrats, you have magisk installed properly now, but i think your reference to the 3 lines is a reference to the old menu system, which is not longer there, but appears in earlier versions, and a lot of articles online, which leads to a lot of confusion...

The menu is now at the bottom of the screen in the form of a bar, to install modules, click on the little puzzle piece on the far right of the bottom floating menu bar
[Magisk] 73sydney:
He has resolved that issue, magisk is now installed (compare the Installe lines), and i think hes just looking for how to install modules...think he was looking for the old 3 line menu from previous versions...in many ways i wish the old menu would return...so many online articles use the old magisk ui for screenshots leading to exactly this confusion
[Magisk] zgfg:
Ok, now you have Magisk installed, ckick to the Modules tab as marked on your screenshot below

PS: Sorry, I was asleep, others already responded you :)
[Magisk] pierre 3175:
I only dowload the V23 apk, cause I couldn't well understand what to do with the other files..

Thanks :)

You're right, I notice that and tried in the intervall of our responses.

I then taught I need to reboot, and it seems rebooting make loose the installation of magisk. So I think I shall not reboot never ever, to have the modules to function, or I carry a PC with me to use fastboot each time needed... I'm right ?

PS : Soooo sad. I think I succes in installing the module, but now, in root, the apk,

True Phone Dialer & Contacts & Call Recorder, does not want to make a call, or to receive one.​

It's my chance.​

Thanks for your helps, guys. Must find an other solution​
[Magisk] zgfg:
Magisk survives the reboot, really no problem there.

Only if you did:

fastboot boot <patched-img>

instead of:

fastboot flash boot <patched-img>

in which case you didn't really flashed the Magisk but only temporarily booted to Magisk (until the next reboot)

Anyway, seems that the call-recording module you installed is not compatible with your ROM
[Magisk] pierre 3175:
That was happily the case, only temporatly booting to Magisk, cause if not I missed several incalls.

I'll check tomorrow if it is the module or the apk which have a problem with the root on my system, official ROM. I think on the second option because the bug came before I manage to install the module.

But Hope is still alive as I saw another module allowing to install manufacter's apks, maybe I can re-use the asus calling screen (not compatible without help on MIUIs ^^

I really thank you.
[Magisk] TrainedSheep:
How do I install Magisk canary build? I've searched forums and the github page, but I don't see a way to select it in the Magisk app or a current link to download 23001.
[Magisk] zgfg:
You have to download Magisk Canary apk from Magisk Github (install the apk then patch and flash the img or direct install, or rename to zip and flash through TWRP - suggesting you the first option). Link to Github is also visible from your Stable Magisk app:

Magisk/README.MD at master · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

However, Canary 23001 is leveled-up with Stable 23000 hence no diff here. And both are currently with unknown future who and when will release an(y )update

If you really want to go forward, consider switching to Magisk Alpha - search back in the thread where to download from, installation tip(s), etc
[Magisk] TrainedSheep:
Tried using https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk after it was already rooted with Magisk, but adb said [INSTALL_FAILED_VERSION_DOWNGRADE]

Well golly, the whole reason I was trying to use canary was to file a bug report, but if nobody is maintaining it, then there's no point. Thanks for letting me know!
[Magisk] 73sydney:
Youre probably better off as @zgfg suggested moving to Alpha

here: https://github.com/vvb2060/magisk_files/tree/alpha

Some of us have been running it for a while
[Magisk] pndwal:
Just use Magisk/Canary button on Magisk GitHub home page to get app. Opens

https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

This is latest 23001

Nb. Your link (where did you get that??) is to latest Canary in old archived magisk_files repo (note '_', not '-') so it's fetching 22003, ie. you would be trying to downgrade from 23000, and to downgrade you need to uninstall 23000 first, as with any app downgrade. 😜

Nb. Regular app installation from device should work fine, then Direct install to update (or downgrade) Magisk should be available / work.

Wouldn't say no point however.

Magisk contributors (there are 201) like @osmosis (especially) and @vvb2060 are still distilling / fixing issues, and responding to many issues, as are other informed / experienced users. Many workarounds / non-integrated solutions have been supplied.

Further, as has been noted, many fixes from topjohnwu Magisk Issues have been incorporated in vvb2060's Alpha builds (seems these go back at least to Dec 2018. Archived builds from Dec 2020 are available on his GitHub & Telegram) before merging in John Wu's.

I doubt this will change, and vvb2060 has produced several builds since John's last ones already! This is the beauty of such an open source project. Links, latest etc:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85226785

It would be a misunderstanding to say only John is supplying fixes for Magisk Issues, just as he is not (any longer at least) its sole developer!

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85127113

Nb. John already pretty much turned over current App design / fixes to @diareuse so he could concentrate on Magisk Mask itself:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-83637567

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-83771409

Clearly the issue of official builds continuing (in present form or other) is up-in-the-air atm, but a healthy / active / interested community still exists. 🙂 PW
[Magisk] 73sydney:
Is it too late to go back to SuperSU ? :)
[Magisk] 73sydney:
Hehe i was clearly joking, but its always good for the kids to get a history lesson!
[Magisk] ldeveraux:
maybe i missed the announcement, with TopJohnWu out of Magisk who took over?
[Magisk] pndwal:
No one has taken over, nothing anounced on that front.

Effectively, John is taking a break from maintaining Magisk... a break of unknown duration. 😉 PW
[Magisk] pndwal:
@Tabs78, please can you report if this

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85335989

solved your issue; it may help others.

I'm particularly interested to know which tv app you use, if it uses the VGDRM Helper service isolated process like SkyGo and others do, and if solutions to hide the isolated process or to block it, work. 👍 PW
[Magisk] complicazio:
Is it possible to flash other types of files (zip) besides the magisk modules through Magisk manager?
[Magisk] zgfg:
You can simply try.

But not, it looks for the module structure

PS: I think it was possible to flash Magisk zip (but if Magisk was already installed).

Not sure (does it still work)
[Magisk] complicazio:
I did not remember and I tried and the image files are able to flash without problems.
[Magisk] zgfg:
With Magisk Alpha 23001, I can only select Zip file (all the other types are grayed out).

What is exactly your Magisk app version and how do you flash that img file from Modules (Imstall from storage)? How would it know to which partition to flash the img file
[Magisk] complicazio:
I am probably confused, the image files (boot) can only be patched with magisk manager.
[Magisk] 73sydney:
You can only flash Magisk Modules through Magisk Manager, via the Plugin tab (puzzle piece icon on far right in the bottom toolbar), they must be zip files

You can only patch a ROM's boot image through Magisk Manager, on the home page via Install at the top, the boot image must be an img or tar (ODIN) file

You cannot flash kernels etc that you might have flashed via custom recovery in the past for various reasons through Magisk Manager if thats what youre asking

It only performs Magisk related tasks, the primary being the two above
[Magisk] pndwal:
That's not strictly true, as already mentioned above. 😉

Please see @Didgeridoohan's notes:

Unsupported Magisk version​

After updating the Magisk app you might get a message that the updated app doesn't support your installed version of Magisk. Here you have two options, both involving manually upgrading Magisk to a supported version. Download the Magisk zip and flash it from TWRP, or downgrade the app to a release that supports your current Magisk version and

flash the zip from the Modules section

of the app. This is done

exactly like when installing a Magisk Module

manually, by clicking the "Install from storage" button and selecting the zip.

I'm guessing there may be other non-module zips that are compatible if, like Magisk itself, they are designed to install systemlessly. May be way off here; NOT an educated guess. 😜

🤠 PW
[Magisk] 73sydney:
I respect and applaud your pedantry :) :)

As a fellow pedant, i say well done Sir! :)
[Magisk] pndwal:
It may be an academic / minor point, but feel the concern is not excessive given the original question as well as the fact this (useful) alternative usage had already been pointed out; just felt it shouldn't be dismissed / ruled out! 😬

In short, if I am really a pedant I feel this is scant proof... but I'll take it in the spirit intended, as a compliment... I think. 🤔

I do think anyone in these threads should be happy to learn, not least myself... and our experience does differ greatly.

I am conscious that much of what I know is academic for sure, having read much just for the sake of knowing. Others, yourself, @zgfg etc, already have more practical experience in real coding than I'll ever have... So I walk on eggshells if I contradict, but all of us can be edified here! 😜 PW
[Magisk] J.Michael:
Re: pedantry

I would like to see the word "flash" no longer used to refer to the installation of Magisk modules.

@pndwal, please add it to the agenda for the next meeting of the committee
[Magisk] dr4go:
Very minor addition: The same applies for patching an image file (*.tar.md5 in my case) - there you also see "flashing".
[Magisk] pndwal:
Haha... Perhaps we should chastise the original enquirer, but he's only learnt from the best! (Don't think I said 'flash'! 😉 )

I do take your point, but I'm not on the committee!...

And while it seems John often favours 'install' these days, even he still says flash! ... It seems @Didgeridoohan's use of 'flash' also is based on John's progressive, and even current documentation.

Eg:

https://xdaforums.com/t/magisk-the-magic-mask-for-android.3473445/post-69196610

And currently:

https://topjohnwu.github.io/Magisk/guides.html#magisk-modules

So a module is simply a folder... but how does it get there?...

https://topjohnwu.github.io/Magisk/guides.html#magisk-module-installer

... Who am I to argue? ... It does seem that the terms installer zip and flashable zip are somewhat interchangeable...

It ain't just the doc's either; App itself says 'flashing' while logging Installation, then 'done!'.

Also, I've found it quite difficult to get a clear definition of 'flashing' in this context too. (Perhaps the trouble you can get into here may explain your aversion to the term? 😬 )

I think I'll leave the language to the big boys myself... You could always submit an issue / pull request if it bothers you! 😜 PW
[Magisk] complicazio:
I can only flash magisk modules and nothing else.
[Magisk] pndwal:
Latest @vvb2060 Magisk Alpha build (July 18, 2021) changelog:​

Chinese Translated:

alpha update log​

Magisk (1eb83ad8-alpha-19)​

Based on 1eb83ad8, please refer to the upstream update log for related modifications

Properly process any data from magiskd

Support SharedUserId

Delete the backup file after restoring the boot image

Built-in current version update log

Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline

Support bootimg v4 format

Support bootconfig

Detect /data/adb/magisk/ not updated and prompt to repair

Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting

Fix that it cannot be flashed in some TWRP

Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy

Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide

Display a modal waiting pop-up window when hiding/restore the Magisk application

Edit: The following are new commits:

App adapted to Android 12

Android 12+ super user hides the screen overlay when the window pops up

https://github.com/vvb2060/Magisk/b...73bce50fe5e/app/src/main/res/raw/changelog.md

My earlier notes:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85098469

Current notes:

magisk_files repo is now updated! Check 'earlier notes' for installation method / details.

Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' version (1eb83ad8-alpha-19) now differs from 'Installed' (1eb83ad8-alpha).

Package is now also uploaded to Telegram group.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85229385

Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.

https://github.com/vvb2060/Magisk/tree/alpha/docs

😛 PW
[Magisk] DiamondJohn:
A zip can and many do, install more than folders. For starters there are the post-fs and service scripts. Fancy mounts and "stuff" can be done in these scripts (I think viper/vanced has some mounts in the boot scripts). Technically, I can imagine a installable/flashable Magisk script that can do its work without a corresponding folder. I don't know of any, but I don't see why not.
[Magisk] zgfg:
Vanced Manager takes root and installs their script to /data/adb/service.d/

On every boot, the script mounts modifed YouTube base.apk (split application) over the original YT base.apk

Formally, it's not a module and does not install through the ZIP module file, but one can easily make it to the module that will install the (same) script, just renamed to /data/adb/modules/<module-name>/service.sh
[Magisk] pndwal:
Sure, and thanks for the insight!

Still, aren't those scripts simply installed to the module folder? ... I think it's boot, not installation that activates them.

For the purpose of the discussion about whether 'flash' or 'install' or both are correct terms for loading modules, I cited John's (basic of course) definition for a(n installed) Magisk Module (a folder placed in /data/adb/modules) as opposed to a Magisk Module Installer (a Magisk Module packaged in a zip file that can be flashed).

I agree that initial installation may do more than populate a module folder in /data/adb/modules however; Viper also installs it's apk for example.

Again, my understanding is mostly academic; please let me know what I'm missing. 👍 PW
[Magisk] pndwal:
I just updated Alpha on RN8T.

Simply updated App from App home screen / App Install, then updated Magisk (mask) using Direct Install from App also.

Magisk App was hidden / renamed, and I didn't un-hide /restore it...

--> Seamless, issue-free installation. 👍 PW
[Magisk] starsfighter:
first i was using canaray version 20.4 now i come back tried to install the last stable version with no success the version doesn't appear with the latest manager but when install the canaray manager again it works but without ability to flash modules, so i tried to uninstall cannaray version but i found it's removed from github canaray uninstaller any one can provide me with a link to full uninstall magisk thanks.
[Magisk] 73sydney:
If you cant uninstall via Magisk Manager, you can try renaming the magisk apk you downloaded to uninstall.zip and flash through custom recovery (often TWRP)

Installation

The Magic Mask for Android

topjohnwu.github.io
[Magisk] starsfighter:
Edit,

give me error boot image backup unavailable. the magisk app will not be uninstalled uninstall it manually after reboot.

how can i uninstall it manually?
[Magisk] pndwal:
Did you UnHide manager first (if it was hidden)? That was a must for a number of builds, but especially coming from pre 22.0.

Next, update Manager to new Magisk App, then direct install?

If you did have hidden Manager, you'll likely have 2 conflicting Apps.

Unless you have other issues (model? ROM? etc), simply locating and removing hidden Manager (whatever you named it, 'Settings' etc) as well as new App, then reinstalling new app may be enough to fix issues.

Be sure to read updated instructions from GitHub 'OctoCat' symbol on Magisk App home screen.

Edit: I see that's been linked. 👍 PW
[Magisk] zgfg:
What is the point of going from Canary to Stable. If you are on v23, they are the same - Canary 23001 was leveled up to Stable v23000.

Besides, Stable has lower nomber (23000 is less than 23001), hence you probably need to go to Settings, Apps and Uninstall your Canary 23001 Magisk App (if you hided/repackaged) you have to know the mame you gave it.

Then download Stable apk 23000 and install, then e.g. patch with and flash - again, what is the use of that hassle

Finally, at the moment, you can not expect an updat, not for Stable, neither for Canary.

Hence, what's the point
[Magisk] zgfg:
For me the Alpha update from Jun23 1eb83ad8-alpha to yesterday's 1eb83ad8-alpha-19 was not fully seemless

I also took first to install the App (my App was not hiden/repackaged)

It asked me to download (supposidely the Stub), I accepted and it rebooted).

It repeated three times (asking to download and install, I accepted and after 5 seconds it rebooted

Finally I declined to download and I took Ditect install to update the Magisk - only then, after reboot it finally stopped asking me for download
[Magisk] J.Michael:
I think "uninstall it manually" is ininstall the app with standard Android interface: get to the app's info (find an icon, maybe in the apps drawer), lean on it, select app info; or go to Settings -> Apps, find Magisk Manager app (by whatever name), and tap on it.

From "app info", there is an "Uninstall" button.
[Magisk] pndwal:
That's interesting... I'm doubtful it was asking for stub, but maybe as now stores a local apk... Some issue causing reboot?

I recall you needed to uninstall John's build originally... That differed for me too; my initial Alpha App installed with no uninstall of Canary App... May be something different w/ your device? PW
[Magisk] DiamondJohn:
As for "scripts simply installed to the module itself". That would be my personal preferred method (and I have historically modifed some to act like that), and magisk explicitly has the feature to enable that (dont know if that is a more recent feature and hence less used). However in practice, that is not the case. For example Vanced installs a script to the shared post-fs

As to the "flash" - "install" discussion, I personally haven't confused a magisk flashable with a twrp flashable. And now, my device doesnt even have a TWRP for daily use, so either way doesn't bug me.

As for what Viper does, there are many different methods of installing Viper, each with their own techniques. The way I currently install Viper on A11 is 100% a magisk flash (or is that install ;) ). ie viper is not "installed", its mounted by magisk.

As for your understanding being academic, that puts you above me, as mine is mostly based on glimpses, projections and assumptions. ;)