yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
The app is just a GUI ('dashboard') for actual Magisk mask. Magisk data - database, config files, overlays, modules etc are stored in /data/adb (for its favourable permissions, availability etc), and configured Magisk will function fine without the app. So Magisk App contains very little app data compared to most apps. If you clear data the only difference you'll notice is that the 'Download Magisk only from the official GitHub page...' warning returns if it was previously hidden. PW
[Magisk] pndwal:
As I made some effort with this information to counter common erroneous notions still circulating about Google's stance on root, the 'Magisk community' etc, as well as Johns position and loyalty (or lack thereof) to the same, I saved this yesterday when it become apparent (by OP tone) that a purging was likely. My bad of course for posting such an OT reply in the thread for Alpha...

For anyone interested and since it was purged there, I'm reposting here, with the original spoiler:

Warning:

The following is more General Information re. the custom modder, root and Google relationship. Please Don't read further if you're not interested in gaining a fair / balanced view. 😝 You've been warned...

Spoiler content hidden.

🤠 PW
[Magisk] HippoMan:
I have now created a cat-and-mouse-game discussion thread:

https://xdaforums.com/t/...ng-and-mod-hiding-cat-and-mouse-game.4425939/
[Magisk] zgfg:
I wonder, how many philosophers we have around 😄
[Magisk] QuietMountains:
I have everything checked for Gpay
[Magisk] m0han:
Applist Detector does not find TWRP (Custom Recovery) issues, but Oprek Detector does. I am running the latest LSPosed-v1.8.0-6488-zygisk-release. The module folder does not have system.prop anymore. Is it just me? Now Momo does not report 'ART parameters are abnormal'.
[Magisk] zzz2002:
OK, dumb question of the ... What is HMA & where can I find it.
[Magisk] pndwal:
Hide My Applist module for LSPosed. GitHub. PW
[Magisk] pndwal:
Just moved up to that from stable, and can confirm 'ART parameters are abnormal' is no longer detected. 👍

PW
[Magisk] pndwal:
What is selected by default? PW
[Magisk] QuietMountains:
For Gpay?
[Magisk] m0han:
do you have system.prop?
[Magisk] pndwal:
Yes, if you check box with processes showing all are selected... Try selecting with processes hidden, then check... I get:

It works fine with just that process selected. Also, seems your ('Asia' region?) GPay app is different from mine...

I know that while most no longer need SQLite fix (it was needed for all in addition to SafetyNet pass to use GPay w/ Magisk root until Google changed something a year or so ago), some report still needing that. My guess is that it may be per region/GPay variant.

If resetting denied processes to default doesn't fix it, you may want to try that. See OP here for details:

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/

You can use method in OP, but most preferred the Magisk module from @73sydney which makes a technical and challenging process dead-easy / entirely systemless:

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/post79643248

You'll need both this and SQLite Binary module. This worked for G Pay and reportedly helped for some other banking apps.

Check recent posts there as well as OP / recents here:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/

@73sydney may be of more help to you on this. Don't forget to clear Google Pay data before any new test to clear any cached detection flags.

🤠 PW
[Magisk] pndwal:
Here?:

...no. PW
[Magisk] Prof_Shekhar:
@kamathanmol

Magisk hide has been removed by its creator. It's no longer available in any Magisk version 23 onwards.

You may use Denylist in combination with Shamiko and HideMyAppList with LSPosed to hide your desired banking and financial apps.
[Magisk] zzz2002:
Thank you
[Magisk] crazychris69:
Trouble finding this out;

Does the latest canary build support the Pixel 6 pro properly? Or should I opt for the March update? Running just fine on Jan 2022 version. Fully rooted and zygisk working great! Love the work John does.
[Magisk] Lughnasadh:
Pixel 6 Pro is working fine with the latest Canary (24305) on today's April build.
[Magisk] kykkus:
Hello, I have a problem with magisk and ROG PHONE 5, after the update to Android 12, I patched the boot image with magisk app (24300) as usual, I entered fastboot, flashed the image but the phone remains in bootloop. only with version 2300 it creates a boot image that starts the phone. But with the 2300 the magisk app tells me that I don't have root. Before the update to android 12 I was rooted. how can I do? I try also the last canary (24305) same problem.
[Magisk] zgfg:
Bootloop: You might have left the modules that are not compatible with A12. Before upgrading, you had to disable (those) modules.

You can still do it through Android Safe mode, adb or TWRP (hopefully one of the methods will apply to your phone) - go to Magisk GitHub and read the Wiki.

Btw, even if Magisk v23 app does not recognize that Magisk is installed, you may still have root. In that case you can use a root explorer like MiXplorer, go to /data/adb/modules - each subfolder corresponds to one Module (you can recognize which module from the folder name or by opening the text file module.prop)

Put an (empty) file named exactly as: disable

into the subfolder whose module you want to disable

"Root not recognized': Most likely classical issue that you have two Magisk apps, one old renamed/repackaged when you previously did "Hide Magisk app" and now the newly installed Magisk app

You have to find (Settings, Apps or through the drawer) that old renamed/repackaged Magisk app/mngr and UNINSTALL that one.

Magisk app/mngr is just a UI interface between the modules, DenyList, Magisk db - uninstalling the app/mngr does not affect the Magisk itself.

But the old app/mngr still holds the grip with your Magisk db etc, hence the new Magisk app cannot find that Magisk is installed

That issue has been discussed here hundred of times, hence you could find more in the older posts
[Magisk] kykkus:
Thanks for the reply.

TWRP is not bootable (black screen when I try to issue the command:

fastboot boot twrp.img)

If I open MiXplorer or Fx Explorer tells me that I don't have the permissions and if I give in ADB Shell the command su it tells me "su: inaccessible or not found".

I don't have a other magisk app I also tried to uninstall the magisk app but it always can't find me the root.

Any other ideas?

thank you.

Magiks log output is:

Output file is written to
/storage/emulated/0/Download/magisk_patched-24300_YsiPT.img
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!
[Magisk] zgfg:
I didn't say to use adb su but to read Wiki from Magisk GitHub how to disable modules b using Android safe mode or adb (adb wait-for-device shell magisk --remove-modules)

See the screenshot. Please find yourself the Wiki and about disabling/uninstalling the modules manually (they had to be before upgrading to A12)

Regarding root explorer - the root permission must have been given when Magisk app worked (finding Magisk)

And TWRP does not work for A12

That's why I point you to read about Safe mode and about that adb command while booting...
[Magisk] AbdRiz:
I've been trying to install magisk on my Oneplus 8 running android 11 but it just throws my phone into a bootloop, I've tried installing through twrp and also through patch image method but the same thing happens, if I use an older version of magisk, it straight up doesn't work, can someone please help?
[Magisk] pndwal:
Stable Magisk?; Quite a few fixes incl. for regressions since... Likely this one fixed it:

https://github.com/topjohnwu/Magisk/commit/b1faa5eed4f5c52cc60a90ca74744a77fde07575

Issue with Bionic updating realpath?

https://github.com/topjohnwu/Magisk/pull/5620#issuecomment-1075050952

I notice @osm0sis helped alot with this fix despite:

https://github.com/topjohnwu/Magisk/pull/5620#issuecomment-1073054955 ! 🙉🥳

https://twitter.com/i/web/status/1494714771270250502

👍

I'd be trying latest Canary... 😛 PW
[Magisk] pndwal:
Re. cat and mouse game (c/o Mishaal 😜):

https://twitter.com/i/web/status/1508480359868076035

👀 PW
[Magisk] pndwal:
Trying not to stir this pot now. I put something about original(?) 'policy' here:

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

My Edit ref there is to this later 'policy' by @Didgeridoohan:

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

particularly:

So linking social media is apparently fine now...

Sadly, linking Telegram in particular as a source for downloading mods / files still appears to be a no-no, even when that's the main / official source. 🙁 :

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

Hope it's now clear... It is to me... clear as mud. PW

PS. Mishaal is probably John's favourite (former) XDA staffer! 😉 (...xXDA?) PW
[Magisk] pndwal:
MagiPipe 'One-Click Root' w/ rainbow Magikarp icon...

More love for Mishaal... And Google 'DirtyPipe'?... Dreams are free John... 😁

https://twitter.com/i/web/status/1511107456566390785

🙄 PW
[Magisk] Koffietijd:
I have a very strange issue. Not sure if this is a bug.

I installed Lineageos 18.1 on Samsung A5 (a5y17lte). With nano open-gapps and Magisk 24.3.

I can install dutch banking app ABN Amro from google play store and I'm able to run that app. But since last update of that app, earlier this week, I can not enable Zygisk in Magisk. If I enable Zygisk, this ABN app won't start anymore. Not even when I hide it.

As soon as I disable zygisk, ABN Amro app is able to start. Is there a work arround for this? What happens when I enable Zygisk? Please some advise!
[Magisk] zgfg:
Make sure your banking app is in DenyList, restart, test again.

If still not working try with Shamiko module (it hides Zygisk)
[Magisk] Koffietijd:
As soon as I enable Zygisk in Magisk, put ABN in the denylist, reboot, ABN does not start.

If I then install LSPosed-v1.8.0-6482-zygisk-release.zip and install Shamiko-v0.4.4-106-release.zip

in Magisk as modules, and then reboot, and check denylist. ABN does not start. It crashes immidiatly.

When I disable Zygisk. Then the ABN app starts again.

But I need Zygisk, denylist for other apps.
[Magisk] knojap:
I've got a question.

I've got an S5 and a S7.

Both with crdroid 7.13 (Android 11).

Installed Magisk / Zygisk enabled. Without safetynetfix or something else.

Playstore say's it's certified and my banking app is working! Great

But when using lineage 18.1 on my S7 with magisk and zygisk, the playstore is not certified and my banking app is not working:

I have to install Safetynetfixx (zygisk) and the playstore ist certified. But my banking app still is not working and detects root.

Can you tell me what could be the difference?

Thanks
[Magisk] jons99:
well crdroid has the safetynet fix baked in to their rom and lineage don't
[Magisk] BostonDan:
Also, magisk cannot hide everything about root from banking apps. One of the reasons why topjohnwu originally stopped supporting/developing magiskhide. I have learned to live with reduced functionality on my banking app (can still use parts of it, but not one or two features).

Cheers,

B.D.
[Magisk] pndwal:
Latest Official TJW debug Canary Magisk:

Magisk (63a89d9f) (24306)​

[App] Fix incorrect superuser snackbar text

[MagiskInit] Improvements to sepolicy hijack

[MagiskInit] Use LD_PRELOAD on 2SI init to assist hijack

[MagiskInit] Support Oculus Go

[MagiskSU] Fix a possible crash in magiskd

Diffs to v24.3​

[MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)

[MagiskInit] Introduce new sepolicy injection mechanism

[MagiskInit] Support Oculus Go

[App] [MagiskSU] Properly support apps using shared UID

[MagiskSU] Fix a possible crash in magiskd

[Zygisk] Fix function hooking on devices running Android 12 with old kernels

[BusyBox] Add workaround for devices running old kernels

https://github.com/topjohnwu/magisk-files/blob/016444fb3c6fbd363c11046f56460dc75bf643eb/notes.md

👍 PW
[Magisk] knojap:
But with crdroid the banking app is fully working. So there must be a way to implement safetynet in LOS as like in Crdroid. Or am i wrong?
[Magisk] casouzaj:
Install MHPC module and reboot. Then, in a terminal emulator, enter:

su

props

Select option 1 and follow the prompts.
[Magisk] m0han:
fyi: don't know how, but 'xposed hooks' is now not being flagged by applist detector and momo (were earlier). strangely, oprek detector still flags 'custom recovery files' although no twrp folder/file exists on my device. safetynet passes fine.
[Magisk] pndwal:
Many custom ROMs, including some unofficial LOS forks, are now integrating passing (spoofed) fingerprint (w/ date matching security patch) as well as @kdrag0n's Universal SafetyNet Fix based on his implementation for his Proton ROMs.

Official LOS will never do this due to policy... Just like Magisk itself...

Magisk gives you the framework to implement hiding modules for these same functions however, notably MagiskHide Props Config for passing fingerprint, USNF to cause attestation evaluation type to fall back to basic and other hiding - changes to sensitive prop values etc - (allowing CTS Profile match to pass), and Shamiko for hiding Zygisk hooking and other traces of root / modified (broken) TEE. PW
[Magisk] knojap:
Just working with riru. And zygisk don't like riru. But now i have found a way to make it work.

Thanks
[Magisk] pndwal:
Root for VR goggles! ... Any takers? 😛 PW
[Magisk] pndwal:
My Momo hasn't changed w/ Magisk update:

- RN8T. PW
[Magisk] kramer04:
just tried it and again ans always bootloop

android 10

samsung note9
[Magisk] Mord0rr:
One Plus 6, unlocked, root, xXx rom + Pie 9.0.9 officially rom.

Last Magisk......faill al tests.

I just full format phone last week. If i know, i wouldn't format it, since Magisk was working.....

From comments here, seems that its more difficult to make it pass, than install a rom (no ofense to the developers).

Any suggestion? Format and install before enter system?
[Magisk] squirtle27:
I downloaded the oneplus 10.44? boot.img and patched it using Magisk. I then proceeded to flash it to my device using adb/fastboot.

I installed lsposed and some modules, root was working fine. The only thing I was worried about was the constant bootloops anytime I would restart my phone.

Yesterday, my phone's audio stopped working altogether. It seems like my device is stuck in vibration mode? Anyways, at the same time, I started getting this message: "the version of the google play services installed on this device is not authentic". I checked my root again and as it turns out I have no root access even though everything worked fine just as few hours earlier. Any ideas what might have happened?

I reflashed the patch and after 20 minutes of bootlooping my device is on again. SU works perfectly fine, passes basic safetynet check, still no audio, 3.5mm doesn't register anything, mic picks up no sound, background image doesn't wanna stay on.

Youtube videos play but don't have sound, all other videos behave as shown below:

https://xdaforums.com/data/video/4069/4069067-9ba9492bcae11434616e4e6e67aab4a6.mp4
[Magisk] pndwal:
@Displax identified this issue affecting many devices: Root accidentally disappears (daemon crash) in some cases #5681

Fixed by Canyie's Guard su request IPC #5682

Merged in Magisk master:

Guard su request IPC …

Previously `read_string()` calls `std::string.resize()` with a int read from remote process. When I/O error occurs, -1 will be used for resizing the string, `std::bad_alloc` is thrown and since magisk is compiled with `-fno-exceptions`, it will crash the whole daemon process.

May fix #5681

canyie authored and topjohnwu committed 2 days ago

Built in Canary now -

Canary Changelog:

[MagiskSU] Fix a possible crash in magiskd

Looks like this to me. May want to try latest debug Canary. Not sure of your audio issues w/o root; perhaps you use mods affecting audio? PW
[Magisk] WalterAH:
OnePlus 6T, OxygenOS 11.1.2.2, Magisk 23.0

I am trying to open an app which normally requires superuser rights but when I try to open said app it just automatically opens up Magisk,

I tried uninstalling and flashing the magisk.img but when i re-install it and hide it it just keeps popping up the magisk app itself.

Normally the app (HAL - pokemon go spoofing app) would request to access superuser rights but no dice.

Ive tried deleting and re-installing the APK for the app but when i try to open it it just popups the Magisk.

Is there a way to fix this issue to get the prompt to show up and grant superuser rights to the apps i wish to use?
[Magisk] squirtle27:
This doesn't seem to be the case, most of my sensors don't return any values for some unknown reason, along with not being able to record videos, play most videos, use speakers, microphone or headphone jack at all.

Other than that everything seems normal :p

Currently trying to remove all modules and see what happens (if i could get my device on >:( ).
[Magisk] pndwal:
These symptoms actually look like mismatched / incompatible kernel. (Issue fix I linked just addressed your apparent loss of root since you mentioned:

but it seems you have a different issue...)

Going back to this comment:

- Mismatched kernel (it's in boot image) seems highly likely, especially as you seem unsure what you downloaded, but you've given very few details.

Please say exact current ROM in use and how you "downloaded the oneplus 10.44? boot.img"...

Did you actually download complete ROM per official instructions, or boot image separately somewhere? PW
[Magisk] pndwal:
Do you mean Magisk-patched boot image here?:

... And what do you mean by "hide it"??

I have no experience w/ Pokemon or associated mods, but after trying this app, can you see it / manually select Superuser privileges from Magisk App Superuser list? PW
[Magisk] pndwal:
What tests??

Pass what??

There are some essential steps to take if you mean "pass SafetyNet", but this is no longer a function associated with Magisk itself so I won't elaborate unless you clarify / confirm. PW
[Magisk] pndwal:
Using Direct Install? ... What options do you get / have selected? PW
[Magisk] Mord0rr:
I mean pass pass SafetyNet. It fails completly.

Im old school flash on TWRP, but frm what i read herem things became super complicated now...

Even it seems we have to patch bootloadr.img using ADB, what wasnt necessary on past.....

Strange because im on PIE and not the 10 or 11,,,,so it should be more easy...

Is it Google Play? Maybe i patch some old hacked Google Play.....

Well,,,,tests apart everything seems to work, and i have root, thats ok.
[Magisk] pndwal:
Patch/flash method is really the only universally working method now.

It is actually essential for many devices from 2018 (ie. A-only SAR which lack ramdisk in boot.img; zip installer cannot work for Magisk in recovery ramdisk), it also eliminates issues using incompatible or semi-compatible custom recoveries, and it allows Magisk installation where custom recoveries are simply unavailable (many devices lacking custom development support as well as those running Android 12 & 13).

Nb. these changes were really necessitated by Google changes to Android boot methods and initialisation. See this:

https://topjohnwu.github.io/Magisk/boot.html

Why? - SafetyNet API functions the same way for most devices. Pre Oreo (8) devices will generally not need forced fallback to Basic attestation evaluation type however, and may be able to continue to pass SafetyNet after full HKA deployment (when 8+ devices won't be able to any longer).

No!...

But you may (in some rare circumstances) need to clear Google Play Services data to get SafetyNet pass. Also, you may need to clear Google Play Store data to get Play Protect 'Device is certified' result.

Passing SafetyNet is not really complex, but John isn't playing the cat & mouse game-that-has-become-a-war-to-him anymore! - Insight / his thoughts here:

www.twitter.com/topjohnwu/status/1445598597521633285

Basic Hiding modules for 'root' (really modified / broken TEE) currently available for Magisk:

Magisk still gives you the framework to implement hiding modules however, notably: 1) MagiskHide Props Config for passing fingerprint (needed for custom ROMs where a passing device 'fingerprint is not spoofed/integrated),

2) Universal SafetyNet Fix to cause attestation evaluation type to fall back to basic (due to recent Google server-end changes) and other hiding - changes to sensitive prop values etc - (allowing CTS Profile match to pass; where this solution is not integrated in a custom ROM), and

3) Shamiko for hiding Zygisk hooking and additional (other) traces of root / modified (broken) TEE.

These basics are covered in more detail in OP (first 9 posts) in the new thread:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

Hope this helps! 😛 PW
[Magisk] ale5000:
@topjohnwu: Hi, inserting some additional lines at the start of module.prop can cause issues?

Something like this:

# SPDX-FileCopyrightText: none
# SPDX-License-Identifier: CC0-1.0
[Magisk] zgfg:
TJW does not participate here, he will not read and never answer you here - his last post was Oct 1, 2020

For the module.prop format, check Magisk GitHub, Documentation - or open various modules files and compare (like for the built-in Systemless hosts, on the screenshot)

Anyway, you can easily test yourself. Use a root explorer (like MiXPlorer) go to /data/adb/modules, take a module/folder, add your stuff to its module.prop file and then open in Magisk app, Modules tab to see that your lines were ignored (it will still show the proper info about the module name, developer, version, etc)

For the experiment, edit the existing lines like name= or version= etc, then reopen Magisk app, Modules tab and see the differences you can make
[Magisk] Mord0rr:
Thank you very much for hard, long detailed explanations...

Very apreciate!
[Magisk] squirtle27:
I think you're right, my stock oxygenos was I think 3 versions behind (probably 10.4.4 or however the formats are) and I flashed with the 10.99 boot.img file which I extracted from the full rom of it.

I have the stock of 10.99 (or whichever version it is that I flashed to my device), so what should I do at this point? Is it going to be normal if I use a stock 10.99? and after that can I properly root my device with the patched 10.99?
[Magisk] J.Michael:
If you want to stay with the old version, locate the full ROM of the old version, extract the boot image, patch with Magisk, and flash.

If you are worried about whether you can use the nww ROM, or about whether it will be harder to install Magisk, you should check threads devoted to your device, and threads devoted to that OS.

I would think that you would always have the option of going back to the old ROM if things go badly, assuming you have the full ROM -- how did you install it in the first place? -- but I've read enough in these threads to know it's always possible for something to be irreversible. Maybe that's only with updates from sources like Samsung, and never with OxygenOS, but noone can say without actually doing it.