yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Please say what you are doing... Is that output from Magisk App or did you change .apk to .zip and use old flash from recovery?...

Guessing the former... If so we generally patch extracted boot images these days although Magisk can handle archive formats so .tar, and now even payload.bin archives can be handled...

Anyway, seems you may be trying to patch a .zip archive... Why?... And have you read the Installation Instruction page?... Click the GitHub OctoCat next to @topjohnwuin App for main page and scroll down...

🤠 PW
[Magisk] kaodd:
ok what i did - installed magisk.apk, flashed boot.img, flashed patched boot.img with flashboot and restart = devices flashed! fixed safetynet = ok!

tried to flash v4a.zip = got the message, sh*t
[Magisk] HippoMan:
I've been using Magisk Delta in whitelist mode, and my whitelist contains literally dozens of references to rootable apps.

If I switch to Magisk Stable or even (gasp!) Magisk Alpha, is there any way to transfer this "whitelist of rootable apps" knowledge from Delta?

Or will I simply be stuck with having to manually set up the equivalent of this knowledge in blacklist mode?
[Magisk] pndwal:
Well you may have been blasting past too fast, but got it passed at last... Heck, take your time to check... Well done... PW
[Magisk] kaodd:
i'm kinda old and running out of time soon;) so that means i cannot flash zip files?
[Magisk] HippoMan:
I'm aghast at how vast we'd have to cast for a rhyme written as well as thou hast. Let's run the victory flag up the mast.

PS: I hope you're not offended at being sassed.
[Magisk] zgfg:
We'll see do we get exciting new(regression) bugs 🤪

Hopefully, it won't be first Stable or Canary, followed by fixes in Alpha (still waiting for Stable and Canary fixes for broken things in v26.4) - many users reverted back to v26.3
[Magisk] J.Michael:
How did you "flash v4a.zip"?

You do not use fastboot to flash zip files.

If v4a.zip is a Magisk module, I think you use the Magisk manager app: one of the icons on the first page takes you to "Modules", from there you should be able to wander to "Install Module".
[Magisk] pndwal:
Probably stuck...

Shamiko has whitelist mode... Don't know how you'd transfer configuration though... 🙃 PW
[Magisk] pndwal:
Very likely I'd say...

I'm guessing Canary or Beta... Doubt first will be stable for same reasons...

Small fixes with come directly from TJW master... Experimental fixes will likely come from LSPosed/Metagisk, LSPosed/magisk (private), a @canyie fork, Alpha or other as always... 😜 PW
[Magisk] pndwal:
What you tried was to patch a .zip, not flash... That method could be used to Magisk-patch a complete ROM think...

As above you can flash module .zips, even Magisk builds, from Modules tab, Install from storage...

Wishing you much time and many Magisk updates... 🤠PW
[Magisk] HippoMan:
Yeah, and it's described in the Shamiko docs as being slow and not suited for non-testing use.

Oh well ...
[Magisk] HippoMan:
I understand that Magisk Stable and Magisk Alpha don't have a whitelist mode.

However, I'm wondering if there is some command-line-based way to tell either of them to mark a given app as being rootable?

... perhaps some usage of the "magisk" command-line program, or perhaps some "pm" command, or perhaps by creating files or database entries, or perhaps some other way?

The reason I'm asking is that I can do an sqlite3 query to get a list of the apps that are set up in Magisk Delta's whitelist. Since such a list is available, I'm wondering whether after switching to either Magisk Stable or Magisk Alpha I could run some sort of command(s) to flag each of those listed apps to be enabled for root.
[Magisk] J.Michael:
I don't remember seeing an official declaration that this is possible, or supported.

But, since you say you can query the apps in Delta's whitelist, you can certainly modify the database to make the same kinds of "marks" -- maybe adding records, maybe modifying existing records.

I think the first step would be to check Magisks Stable and Alpha to make sure they have the same kind of markings in their databases.

Good luck.
[Magisk] HippoMan:
Thank you. And this means I'd have to install either Stable or Delta Alpha and then dig though its files and databases.

The problem is that I don't have a lot of spare time for this kind of investigation, which is why I was asking here whether anyone has any knowledge of this, before I go jumping in and installing either Stable or Alpha.

I'll wait here for a while longer (maybe until Monday or so) to see if anyone might be able to shed any light on this. If not, then I'll figure out when I have enough time in the future to do this investigation myself.
[Magisk] pndwal:
Extract and read readme.md from Shamiko .zip... See Usage...

Edit: See next posts...

😉 PW
[Magisk] HippoMan:
If this is the same as the README.md file on the Shamiko github site which I have already read before, then I won't find any information that addresses my question.

But when I have some time, I'll download the Shamiko zip file and check out its contained README.md, in case it's different from what's shown on github.

PS: My current meeting was just unexpectedly canceled, so I do have time for this now. The contained README.md file indeed is the same as what's already shown on line.

It just says that Shamiko whitelist mode can be turned on or off based upon the existence or non-existence of an **empty** file named /data/adb/shamiko/whitelist . This is what I already learned before. No docs are given about how to pre-seed the app whitelist information itself, or even if such pre-seeding is possible in the first place.
[Magisk] matfcb:
26.3 works fine on Xiaomi Mi 9 Pro 5G Android 11. 26.4, 26.4.1 (Canary) doesn't work. I turned all modules off but 26.4 does not work. 26.3 works fine. Any solutions?
[Magisk] pndwal:
Sorry guys, didn't check properly... Thought @J.Michael simply wasn't sure if whitelist mode was available, but see you had asked about CLI options:

... This may not be supported by native magisk binary commands but likely is via SQL database commands per:

https://topjohnwu.github.io/Magisk/tools.html#magisk

For Denylist (in Tools doc under magisk binary), under Usage: magisk --denylist [action [arguments...] ] are several options for
and I've tried some, but for Superuser access there are apparently no such options and it seems the app is generally enrolled for this... SU applet of magisk binary doesn't seem to help either...

However it seems likely that --sqlite SQL exec SQL commands to Magisk database might help (I don't know about available commands), or simply save list in an SQLite editor and restore since Magisk just stores Superuser list of policy settings in 'policies' in .db file with app identified by uid like:

... Maybe you didn't know. 🙃 ...

If Delta uses an entry comparable to 'policies' with same uid identifiers for apps, guess you could simply save em and wack entries like 1xxxx, 2, 0, 1, 1 into 'policy' (Superuser app) list...

... FWIW I don't think CLI options in Alpha etc differ at all... For Alpha:

(I think --preinit-device has been added since last doc update.)

😋

🤷‍♂️

Maybe you'll just take the plunge now...

... Hope you report successes...

Any coders here who can list relevant commands for --sqlite SQL exec SQL commands to Magisk database?

🤠 PW
[Magisk] pndwal:
This:

should fix issues described here:

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

... Wait for next release or try a late CI build from Magisk GitHub if you can't... 😜 PW
[Magisk] HippoMan:
Being a coder, I had discovered a week or two ago that the relevant table in the Delta /data/adb/magisk.db is named "hidelist". It contains one row for each checked item in the "Configure mount" list.

The command would be ...

select * from hidelist

However, simply changing this table's entries doesn't seem to properly propagate those changes to the "Configure mount" list in a way that causes them to be recognized by Magisk Delta when determining which apps will run as root. I already tried that a while ago under Delta 26301.

There is probably other information (such as that which is contained in that "policies" table, perhaps, and maybe other tables) which somehow has to be joined properly with the contents of the "hidelist" table.

And anyway, I have no idea whether or not the /data/adb/magisk.db database is used identically in Stable and Alpha to how it's used in Delta. Given that there is no concept of "Configure mount" in Stable or Alpha, I don't even know whether a "hidelist" table exists in those non-Delta Magisk versions.
[Magisk] pndwal:
I read that recent Alpha builds can be swapped with TJW builds at will without issues with config data etc, so I'm guessing that the .db format is identical... I'll check once the next build appears and I'm back on official Magisk...

I can confirm that for Alpha an SQLiite viewer shows only the four tables I posted above... There's no 'hidelist', only 'denylist', and this is true despite Alpha retaining a HideList mode...

Alpha HideList is only available when Zygisk is disabled, so I've just disabled it, engaged HideList, rebooted and checked magisk.db again... I can confirm that the table name doesn't change... Seems in Alpha and TJW Magisk it is always 'denylist' while SuperSU settings reside in 'policy'...

As Custom Magisk (@TheHitMan) and other forks implemented Magisk configuration very differently, they stipulated that a full uninstallation (especially/data/adb contents) should be performed when migrating... I don't know what @huskydg says about that, but I imagine that fork will be incompatible with the Canary builds it's synced with also... Current Alpha is different/compatible... PW
[Magisk] Utini:
Any ideas on this? Log file included.
[Magisk] kaodd:
finally i fixed it. thx for all help.

c u with my next problem, it will come i'm sure.
[Magisk] BROKEN1981:
When will Magisk get the Google monett theme? Adguard and swift backup has it. Few other apps are getting it too such as SDmaid.
[Magisk] Nergal di Cuthah:
Meh, just would be added bloat to an app that is rarely opened except for updates and the rare new module.
[Magisk] pndwal:
Bit further in a "blast from the past" for many here...

@73sydney

Saw your post here: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-89154853

and thought id point out my Superuserlist backup and restore modules already fiddle with SQL commands and the policy table, you can see the commands in the /common/install.sh files

https://github.com/adrianmmiller/SuperuserListBackup

https://github.com/adrianmmiller/SuperuserListRestore

So the logic/code to manipulate the db is already done and im happy for anyone (other than Androidacy) to use it and expand on it if they find it useful

Maybe this will help?

p.s. all the cut tricks you can put down to the influence and tutelage of Didge in getting me started when doing the GPay module, the rest, the SQL stuff was just fiddling and reading the magisk code

Me

Yeah... thanks!

I vaguely remembered you'd done this but didn't check back... Can I reproduce post above in a reply?... @HippoMan may appreciate it...

Any more cats / cat antics/love? 😛

@73sydney

yeah i was hoping you would want to share with him

no cat, 2nd time in a row the breeder changed their story last minute - was supposed to arrive today. 4 months of being invested in 2 cats form 2 different breeders, working like a slave to finish my build on THEIR schedule, and both turned out to be timewasters.

Me

Ta.. will pass all that on for old times sake...

Sorry about cats... Looking forward to more pics...

Bit worried about the doc... Remember Where's Wally?... Well where/hows the doc??

@73sydney

Cheers, hope its useful to him

All good re cats, theres plenty and the right one will turn up. Should have final cat prison pics at end of week, made ramp up last week, assembly of that final piece and odd jobs this week

Hope B is well and just busy

------​

... There you go!... Hope it helps... 👍 PW
[Magisk] zgfg:
Yeah. Btw I posted long ago. I simply use MiXPlorer to edit the magisk.db
[Magisk] pndwal:
Is it TJW (official) Magisk? PW
[Magisk] Utini:
It is the official magisk app. But what do you mean with TJW or PW?
[Magisk] zgfg:
TJW = Top John Wu, PW = PndWal
[Magisk] HippoMan:
Wow! Many, many, *many* thanks indeed for this blast from the past! I'm aghast! (in a very positive way!)

And huge amounts of thanks to @73sydney, which I hope will get passed fast to him! Indeed this info that you supplied, @73sydney, provides a lot of what I've been looking for. In my far from ample spare time, I'll dig into this and hopefully then be able to try to achieve my desired Delta-whitelist-to-equivalent-Stable/Alpha-configuration conversion. I'll then report back here with my findings.

To @73sydney: without having had any news about you, I've been worried about you. I'm glad to now know that you are alive and seemingly well!

Not sure what a "cat prison" is. Being a cat owner and cat lover myself, I have serious doubts that any kind of feline incarceration could ever be effective at rehabilitating any kind of behavior preferences among these intrinsically stubborn creatures. :):)

I therefore assume that the "cat prison" is something else and for a totally different purpose.

In any case, thank you again, very much, to both of you!
[Magisk] Utini:
Oh okay. Well its the official TJW from github.

Attached is the .apk that I downloaded and the one that got downloaded through the managers update.
[Magisk] zgfg:
Cannot be sure from the names. Generally, version number like 26.3 should mean Stable 26.3

26400 should be Beta 26400.

Or 26401 should be Canary 26401

It depends how you setup Updated Channel in the Magisk app settings - if you chose Stable, it will point and install the latest Stable, etc

Also, if you download from the official GitHub page, Stable would be latest Stable (26.4 now), Beta latest Beta (26400), Canary and Debug (26401)

Also, all official (TJW) apps (Stable, Beta, Canary and Debug) install with com.topjohnwu.magisk package name. Forks Alpha or Delta have different package names
[Magisk] Utini:
I just compared the md5 checksum of the .apk from github and from my downloads folder. They are identical.

So I am using the original TJW magisk.

I also can't fins any app/process with the UID that was blocked root by magisk. Really weird.
[Magisk] BROKEN1981:
Not sure how anybody in their right mind would consider that "bloat". It's actually consistency.
[Magisk] J.Michael:
It is "bloat" in that it involves adding code to a program. If the code is not useful to a particular user, but it increases the size of the program, then that user will regard it as "bloat".

Perhaps more useful to you: Nothing in this thread will influence future development of Magisk or its manager app. To have any hope of the real developers seeing a feature request, you would have to post on Github, Telegram, or the service formerly known as Twitter. Even then, I do not believe that casual posts get much attention. You will have to track down the requirements and submit a full, formal, request.
[Magisk] woozie.2007:
Sorry for asking, but is it working now magisk 26.4? I don't want to loose again my banking apps, thanks
[Magisk] HippoMan:
Agreed. And I believe that such features should be optional with the default being opted out, with any users who want the feature to be able to opt in.
[Magisk] Nergal di Cuthah:
Sooo much extraneous code ;-) lol

I'd rather it stay as skinny as possible
[Magisk] ayambakargoreng:
Hi, I need help to root my device using Magisk. I am currently installing Magisk v25.2 (installed using APK from github). When I open Magisk app and press Install there's only option for select and Patch a file. I am assuming I need to select AP file like stated in https://topjohnwu.github.io/Magisk/install.html. But currently, I am using LineageOS 18.1 on Samsung Galaxy Note 3 [HA3G]. I don't know where to get the files to patch.

Any tutorials or anybody list out the steps need to be done would be great. Most of the tutorials I found are either using old version of Magisk or don't really tell the steps need to be done to root custom OS.
[Magisk] J.Michael:
It is not a matter of how old the version of Magisk is.

How did you install LineageOS? What kind of files did you use? What mechanism did you use to install those files?

You have a Samsung device. I assume you have to use Odin to flash anything. You have to give Odin tar files. John Wu advises that you always use the complete set of four tar files every time you run Odin.

Did you get one or more tar files when you downloaded LineageOS?

Have you found a thread for any Samsung device in which anyone claims to have installed Magisk into LineageOS?
[Magisk] ayambakargoreng:
How did you install LineageOS? -> I've used another custom rom before (resurrection remix), successfully rooted it. Now I just flashed lineage OS by flashing using TWRP.

What kind of files did you use? -> The file format is zip

What mechanism did you use to install those files? -> Flash using TWRP

You have a Samsung device. I assume you have to use Odin to flash anything. You have to give Odin tar files. John Wu advises that you always use the complete set of four tar files every time you run Odin.

Did you get one or more tar files when you downloaded LineageOS?

-> nope. only 1 zip file

Have you found a thread for any Samsung device in which anyone claims to have installed Magisk into LineageOS?

-> I've not found it yet
[Magisk] pndwal:
Wow... Very old device!... The caveats for Samsung Devices in Important Notes in Installation instruction page probably don't apply to your device, but I'd back up everything first just in case of problems requiring data wipe...

In your current LineageOS .zip archive you should find boot.img... for you installing Magisk should be as simple as using Magisk app to patch that, then flash it using TWRP... Alternatively, just renaming magisk.apk to magisk.zip and flashing that in TWRP should work fine too; will give you partial root, then follow instructions on booting/opening Magisk App to complete Magisk installation (fully root by setting up selinux/module rule directory with device booted)...

Nb. Your device may suffer from this issue: Zygisk cannot activate on some old Samsung devices with old kernel (3.19-) #5395 by yujincheng08 ATM... If so Zygisk won't work on your device... However despite this being marked "Wontfix", the fix was expected and is already merged upstream (ie Refactor zygisk to use native bridge to inject #6659)... You may or may not need to wait for next Magisk release to use Zygisk; you can't know without trying!

🤠 PW
[Magisk] Wolfcity:
Xiaomi mi 9t (Redmi K20) running xiaomi.eu 12.5.2 (Android 11) working good with PIP 1.2 3. and magisk stable 26.3. No problems with Banking apps like S-push-TAN.

But as posted by other users before: Magisk 26.4 let's the UI and several things go crazy.

Just information.
[Magisk] ayambakargoreng:
Thanks. Got it working using this method : Alternatively, just renaming magisk.apk to magisk.zip and flashing that in TWRP should work fine too; will give you partial root, then follow instructions on booting/opening Magisk App to complete Magisk installation

My kernel version is 3.4.113 so I don’t have any issues enabling Zygisk
[Magisk] zgfg:
Btw, this might be interesting for some, maybe eg @HippoMan:

[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Disable Force Encryption Native Early Override (DFE NEO v2) | Disable encryption /data | userdata

Brief description: Disabling encryption without direct modification of system files. Mount method, i.e., RW not required. Supports EXT4(RO/RW), EROFS, F2FS(RO/RW). Description: DFE-NEO v2 is a script designed to disable forced encryption of the...

xdaforums.com

(Disclaimer: Not using)
[Magisk] HippoMan:
If this actually works, would it be something which might facilitate some sort of dd-based backup-restore for devices for which there is no TWRP or OrangeFox for performing nandroid operations?
[Magisk] danweber:
I have an app that is trying to detect Magisk. I've enabled Magisk hide, but one thing the app does is check the process table, and right there there's a process called `magiskd`.

I tried the crude solution of killing the process, renaming the file, and relaunching it with its new name, but this broke most of magisk and I needed a reinstall.

Is there a way to have magisk rename its daemon?
[Magisk] zgfg:
You must try, if you are interested in

I'm not - I want to keep Encrypted Data for security purposes and I have no plans to think about unencrypting

With TWRP (as I have) and with unencrypted Data, a thief or anybody who would find my lost phone (if that happens) would be able to copy (TWRP supports MTP) all my files to his PC. Pictures, documents, etc
[Magisk] J.Michael:
Would you share the name of this app?

Have you granted this app elevated privilege?

When I run "pa -A" from a terminal, there is no mention of magisk. Only when I run with "root" privilege do I see this "magiskd" you mention.
[Magisk] zgfg:
What do you mean by "Magisk hide"

There is only "Hide Magisk app" option, and as it's name says, it hides (renames/repackages) Magisk APPLICATION, not the Magisk (demon)

You should use DenyList - assuming you're running official Magisk

Only in the ancient versions of Magisk there was "Magisk hide" (together with "Hide Magisk APP", where the second was only hiding the app, only the first was hiding Magisk itself)

There was also "Magisk hide" in the unofficial Magisk Delta, but not the latest Delta versions

So, be precise, what is your exact version of Magisk and do you really mean "Magisk hide" or" Hide Magisk app".

And for hiding Magisk you must use DenyList, plus Shaniko to hide Zygisk
[Magisk] dcarvil:
Did you mean "ps -A"? I have no pa command.
[Magisk] pndwal:
I wondered if that's possible too... Just checked in AM debug app and it showed a list including:

However after revoking superuser rights it can only find its own processes...

Tried ps -A in a TE too and can confirm su is needed to see the processes:

Are you certain that the app can actually do this, and without su privilege?...

Conceivably a bank may ask for su privilege despite root being properly hidden... I can only surmise that this would be an opportunistic trick, and if you actually allowed (accepted) it, it would be a mistake...

I'm also skeptical about the source of such an app... The implications for a genuine financial institution doing this are very concerning at best... Worse, it would smack of a rogue (phishing) app masquerading as a genuine bank app which does occur even in official app stores...

If apps can source running processes w/o root or other special privileges however, or if some innocuous looking permission can allow this without root, this would be a concern in itself... 😬 PW
[Magisk] J.Michael:
Yes, it should have been "ps".
[Magisk] xcl1pse:
There's no way to rename magiskd. Like for what?

If the app/process inherit its own mount namespace, it will see only its own package name and the app/process package name which started the daemon IF App/process requests root permissions

If the banks use this method to detecting magisk, must question their security system
[Magisk] HippoMan:
In my opinion, many banks indeed make use of questionable security systems, so I wouldn't put it past some of them to try to detect Magisk in this manner.
[Magisk] pndwal:
Latest @vvb2060 / @RikkaW KeyAttestation app update:

v1.6.0

- support app generated attestation keys

- support show certificate chain

- support provisioning info extension

- save as p7b for Windows friendly

- rewrite parse certificate chain

- fix activity config change

👍 PW
[Magisk] rodken:
As well as some hotel chains [I'm looking at you Marriot].
[Magisk] knigge111:
Hello! I use the deny list from the Magisk App options menu. Then activate the toggle for force deny list. I use 3 different bank apps and with this method the apps working without a problem.
[Magisk] xcl1pse:
Yes because you preventing magisk and modules mounting into the app..