yashsingh1/xdaforums huggingface dataset:
[Magisk] mickeychan1:
Hi! I'm also having problem with touch n go. I'm on magisk 25.2, universal safety net by kdragon v2.4... all other banking apps pass ...

Please help.... I'm not sure what you mean to install magisk v23?... Does that mean I need uninstall magisk v25 first, then install v23?

Or do I just install magisk delta directly from magisk v25, and if so, is there any guide how to do it?

Many thanks from a fellow Malaysian to another 😊 as only Malaysians uses touch n go app....
[Magisk] J.Michael:
Read the last hundred posts in the main Magisk thread.

The safest way to change Magisk versions is to uninstall Magisk, uninstall the Magisk manager app, reboot, and start over with a different Magisk APK.

There have been recent posts about other procedures.

In this post @Fry-kun described a very simple process that I didn't believe. You can waste five minutes watching the video, or you can read the follow-up posts.
[Magisk] roslanhashim:
yes... you need to install magisk v25 and reinstall magisk v23.

or

you can directly install MagiskDelta.apk, open it and grant root excess. reboot into recovery and install magiskdelta.zip.

reboot into system - open magisk delta apps. go to settings - switch on MagiakHide - configure MagiskHide by adding all banking apps & tng ewallet. click on 3 dot - show system apps - search google - click to hide Google Play Service, Google Play Service for AR, Google Play Store. if you install Vanced MicroG, make sure you hide it also.

long press Magisk - uninstall.

this method work for me even i have to learn it by hard way
[Magisk] superbarney:
I just tried out Magisk Delta. Using that seemed to have allowed the TnG app to run again. Other bank apps and Grab are working fine still too. Hopefully the changes that is in Magisk Delta can be integrated into the original Magisk in the near future.
[Magisk] wyt18:
What about lsposed/zygisk? Would that work with Delta?
[Magisk] mickeychan1:
thanks! I will try it!
[Magisk] koberulz:
I don't really keep up with Android stuff, just pop in periodically when I get a new phone.

I remember seeing that topjohnwu got hired at Google, and as part of that they insisted he remove Magisk Hide functionality. Not sure what happened after that, but I just avoided any Android and Magisk updates and I've been fine. Unfortunately, I accidentally clicked on a Magisk update the other day and now it doesn't work, I get periodic "Magisk has stopped" messages and trying to click on it in the app drawer does nothing.

So...what exactly is its status? It seems to still be going, contrary to the dev-hired-at-Google-and-app-nerfed narrative I was aware of. Not sure how to go about resolving my problem. I guess updating to Android 12 might be back on the table?

Pixel 3.
[Magisk] zgfg:
There is a lot to read in the OP posts right in this thread - for the beginning

And then some newer stuff, ongoing in the later posts in this thread, Magisk general, Google Pay thread (if you use it)

Btw, you could search for PixelFlasher XDA thread, a tool for OTA updating Pixel phones and (re)installing/updating Magisk
[Magisk] koberulz:
I'm not going to read an entire 150-page thread, though, and what I've found seems conflicting. Magisk Hide is dead, but there's a Deny list, but apps can still detect root now because Magisk can't do anything to prevent that...

I need Hide, because my banking and streaming apps won't work otherwise.
[Magisk] zgfg:
I said to read OP = Original Poster posts in this thread to see what's different in the new Magisk and how to configure and use - eg, Zygisk and DenyList instead of the old MagiskHide, about hiding (not only Magisk but the whole 'root') by Shamiko, USNF, the things you're asking for

You don't have time to read 150 pages - I think nobody has hours (if not more - accounting for answering additional questions when you open Pandora box, like where the Module repo is 'gone', etc) to write several pages now exclusively for you about the 'status' of the new Magisk, or do you really expect that?

That's exactly why this thread was opened at the beginning and a lot of patience spent by the OP poster to give the newcomers to the new Magisk v24 (now v25) a quick start

But if it's still too much to concentrate and to read, then better give up and go back to Magisk v23

There is also a fork Magisk Delta - it's based on the new Magisk but with MagiskHide instead of DenyList (it can be used with this new Zygisk or without).

To make hiding easier, Delta also provides Whitelist mode named SuList (in MagiskHide you list those apps you want to hide from, in SuList you list the opposite - those apps you don't want to hide, hence when you install new 'banking' app you don't need to add to MagiskHide and reboot).

Delta has its own thread on XDA (search can find it)
[Magisk] koberulz:
I've read it, and I'm confused.

It implies DenyList replaces Hide, but then the Magisk FAQs say Magisk has no features to prevent apps seeing root. Those seem contradictory to me.

I'm sure there's nowhere near 150 pages of information I actually need, so reading the entire thread would largely be a waste of time.
[Magisk] zgfg:
DenyList is not exactly for hiding but it partially helps for that

Zygisk provides the mechanism for additional modules to help for hiding - like the Shamiko module

To pass Play Integrity API (no intention now here to describe what it is and how it supersedes the deprecated SafetyNet), you will need the latest USNF

(I think all that above was shortly addressed in the OP posts)

Some 'banking' apps search deeper for 'root' and you may additionally need Hide My Apps (HMA) - btw, that would apply also to the users of the old, pre-Zygisk Magisk (but would require to search for Riru based LSPosed instead of the new, Zygisk-LSPosed)

And again, there is a Delta fork that includes Zygisk but also the old MagiskHide (in the whitelist SuList mode or classical blacklist MagiskHide list) instead of DenyList - exactly because the developer wants to help himself and his users to easier hide

All these are just bullets for further (re)search

Edit:

There is also a MagiskHide module (from the developer of Magisk Delta) for the official Magisk, that gives you back the MagiskHide to the new Magisk v25xxx
[Magisk] koberulz:
Looking at PixelFlasher, it requires I give the shell root access in Magisk, but I can't do that, because Magisk won't open.
[Magisk] zgfg:
Better ask in the Pixel Flasher thread

Btw, if you just 'blindly' updated from Magisk v23 to the new Magisk v25 (being new with what it brings), there are might be various reasons why "Magisk does not open"

Btw, who does not open: Magisk app or it opens but does not recognize Magisk installed (due to remaining your old 'Hide Magisk' app/manager on the phone), or you go to ADB or Terminal emulator and you cannot grant root access, etc

It would probably be better to uninstall Magisk (by flashing uninstall.zip through TWRP, as described on the official Magisk GitHub page - btw, another guide, official, for the new Magisk) and then to install from scratch (as described in the guide on GitHub or probably by use of Pixel Flasher)
[Magisk] koberulz:
If I click on Magisk in my app drawer, nothing happens.
[Magisk] zgfg:
Then follow the second part of my post you quoted, fully uninstall Magisk (not just the app) and clean install the new v25 - see the Magisk official installation (and uninstallation😁) guide and possibly (I don't have Pixel) the PixelFlasher guide

Sorry, that's it. Not easy now to jump now (or advise about - for someone's else phone) from Magisk v23 to v25, with the number of unknown variables - his phone and ROM, installed modules and their (in) compatibilities, did he do Hide Magisk app and how he renamed Magisk app or he does not remember that, etc)
[Magisk] koberulz:
How do I uninstall? I can't access the app to uninstall it, and the uninstallation instructions just say that if you can't do that, "flash it like any flashable zip", and I have no idea how to do that. I know TWRP stopped working, is that back? The TWRP thread in the Pixel 3 forum hasn't been updated in years. Or can I just flash it with fastboot?
[Magisk] Umbardacil:
I set up Magisk to automatically grant su to any app requiring it. And I'm talking about Google pay not banking apps. Those do not detect root
[Magisk] mahaseno:
Hello all

I have a problem and I don't know how to solve it

Yesterday I installed a new firmware for my phone

I used the previous version 23

But now I fail to hide magisk manager

After renaming, two icons appear

The original icon of magisk manager and a new icon with the name I chose

But it is disabled and not working

What is the solution to this problem, brothers?
[Magisk] jhedfors:
Did you follow all the steps to install Magisk v24 posted at the beginning of this thread? This thread was created specifically for Zygisk (v24).
[Magisk] toejam119:
Since you've setup everything accordingly with Magisk 24.1 have you deleted cache & data from Google Pay? Here (https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-83998107) is someone seemingly with the same problem and that was the solution. I had a similiar problem with my banking ID app a year ago, even if I did setup everything correctly it would still say "your phone is rooted/jailbroken" (since I started the app once when I wasn't hiding all root from it), the solution was to delete cache and data so the app would reset itself back to 0, start fresh. You have to setup the card(s) again but it might be worth a try. Maybe even reboot after deleting cache and data from the app before starting it.

However, that "Apps with root/xposed access" failing in Oprek Detector worries me. If you have an app requiring root, Google Pay might detect this app as a banned app and refuse to work (not sure how their detections work exactly).
[Magisk] J.Michael:
It sounds like you have two versions of Magisk Manager app installed. Uninstall both of them: On each icon, press and hold until you get a tool-tip, select "App info", select "Uninstall". Reboot. See if Magisk installs a Magisk Manager app stub. If there is a Magisk Manager app after the reboot, run it and let it finish setting up. If there is no Magisk Manager app after the reboot, install the Magisk Manager app apk.
[Magisk] _mysiak_:
I have exactly the same issue with Magisk 24.1 on Xiaomi phone, in the past I managed to hide Magisk manager after enabling "allow installing apps via USB" in developer settings, but it doesn't do the trick anymore. At the end I just installed LSposed module "Hide My Applist" and prevented Banking apps from seeing Magisk manager (+LSposed etc.). It works in the same way and actually even better as I can hide more apps than just Magisk manager. 🙂
[Magisk] mahaseno:
Thanks for your replay

In fact, after updating to 24, I could not hide the magisk manager completely, as it was before

Although the safetynet test was successful

but my bank app can still detect magisk manager

Plus I heard I can't use riru with Zygisk

It seems frustrating to me
[Magisk] mahaseno:
Great

does Hide My Applist work with you to hide magisl from app bank !!

any tutorial please

cause i tried it before but i failed to hide any app
[Magisk] _mysiak_:
1. install zygisk-lsposed (pick one from https://github.com/LSPosed/LSPosed/actions, I am using this one at the moment https://cdn.jsdelivr.net/gh/LSPosed...17f357/LSPosed-v1.6.5-6341-zygisk-release.zip)

2. install Hide My Applist and activate LSposed module

3. in HMA - manage templates -> create blacklist template -> edit list of apps -> add all root apps (Magisk manager, LSposed, ...), go back, SAVE (click on save icon on the top right)

4. in HMA - select effective apps -> choose your Banking app -> enable hide + enable all hide methods + apply template from previous step, SAVE (click on save icon on the top right)

5. force close Banking app, start it again and it should work + you will see info about number of blocked requests in the main screen of HMA
[Magisk] mahaseno:
THANK YOU BRO

Now i can say goodbye magisk hide
[Magisk] mahaseno:
But unfortunately

after reboot

My bank app stops

Magisk manager must be renamed to any other name in order for the application to work
[Magisk] mahaseno:
any fix?
[Magisk] Spartacus500:
Hello, I have a Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE, the newest Magisk zygisk, I need to hide everything I marked in Magisk Detector 🤔
[Magisk] Lord Sithek:
First, repackage Magisk App, only after that find the repackaged app in HMA and add it to your template. Data of bank app may need to be cleared as well
[Magisk] mahaseno:
I've already done that

But the bank app stops after rebooting

But the question is:

Do I have to activate HMA in LSPOSED MANAGER on FRAMEWORK ONLY?

Or does it have to be activated on all applications that will be dealt with?
[Magisk] Lord Sithek:
Should be System Framework only. Well, or your bank app is very very smart, or it looks for something else than Magisk app which you haven't considered yet. Like debugging mode enabled or TWRP folder on the internal storage
[Magisk] mahaseno:
I do not think so

Because after renaming MAGISK MANAGER

The bank application works directly and without restart

This means that the matter is not related to activating the developer options because I have not activate it until this moment
[Magisk] Umbardacil:
I've cleared Google pay cache and rebooted several times already. Besides gpay-should i clear other Google app's cache? Banking soda are working life a charm. Only this stupid gpay won't... Deleting all cars is last thing I'd like to do...
[Magisk] Spartacus500:
And how to fix this also 🤔
[Magisk] zgfg:
Screenshots tell more than words

Also, AdAway and Vanced YT (root versions)

Still, couple of things are bothering me:

1) Patching boot.img always fails with Copying to cache / Process error.

Initially I patched boot img on the other phone (good, old Mi 9T), later I made Direct update to the latest Alpha

2) Cannot make Viper4Android to work. V4A app reports there is no driver, it goes to 'install driver' and to reboot, but then again it reports no driver, and the cycle repeats

3) Tried couple of mods from CustoMIUIzer but they didnt work (GravityBox and HMA do work)
[Magisk] zgfg:
Sorry, I do not know the situation with TWRP for your Pixel device. But check to TWRP.me (official TWRP site), do they have TWRP for your model and your Android version

In the worst case (no TWRP or other custom Recovery) and you cannot open Magisk app, you can always (I know, it's pain in the ass) reinstall your ROM with Factory resetting. That would also fully uninstall Magisk by also deleting all its stuff (modules, database, etc)

---

If you are good with using the Terminal emulator and shell commands, you can avoid Factory resetting

To see if that apply, open your Terminal emulator and execute:

su

magisk -c

If it prints your version of Magisk installed, we can go for

But if it cannot find su, whatever - then sorry, I will not second in that direction further (even if it is 'just' about which Terminal emulator to use or how)
[Magisk] J.Michael:
You have to have some idea of what you have done, and how you did it.

For these mysterious Magisk manager apps you cannot run: long press on whatever you are tapping to try to run it, Android should provide a context menu including an item "App info". Choose that, then "Force stop" and "Uninstall". Go through your app drawer carefully, looking for other, renamed, instances of Magisk manager app.

From a command prompt (on the phone; open a terminal window; if you don't have a terminal emulator app, download one) try typing "magisk --help" -- that might give you an indication of whether you have Magisk installed.

You have to know whether you installed Magisk by patching the boot partition or by patching the recovery partition. Whichever, if you have a working fastboot, you should be able to restore the patched partition (by which I mean restore it to its unpatched state) by using fastboot.

Did you ever have TWRP? What do you mean "TWRP stopped working"? Just because someone stopped producing new versions of TWRP, that would have no effect on your device having TWRP.

I have lost track, did you ever try PixelFlasher? It still requires that you have adb and fastboot, but the interface might be more to your liking.
[Magisk] koberulz:
PixelFlasher requires Magisk, which brings us back to square one.

I think TWRP was incompatible with an Android update for, like, a year at least? Or maybe it just couldn't be installed, could only be booted? Not sure.

Anyway, booted into TWRP, ran the Magisk uninstaller, ran the most recent Magisk installer, and we have working Magisk! Don't have root, though, so that's the next step. Will give PixelFlasher a go.

EDIT: Now I can't boot at all, it just goes to fastboot after the Google logo. Balls.
[Magisk] Lughnasadh:
Pixel Flasher doesn't require Magisk.
[Magisk] koberulz:
The guide says it does, although it also says shell has to be granted root permissions but it isn't necessary for the phone to be rooted, so I'm confused.

Either way, I ran PixelFlasher and now can't boot the phone. Which is hardly an improvement.
[Magisk] Lughnasadh:
I guess you mean to find Magisk Tools. To use Pixel Flasher itself you don't need to be rooted.
[Magisk] koberulz:
Not sure what you mean.

But right now my phone won't even boot, which is a more pressing issue. Are there alternatives to a factory reset?
[Magisk] jons99:
in pixel flasher flash the unpatched boot img
[Magisk] koberulz:
No dice.
[Magisk] Lughnasadh:
I would just wait to see what badabing has to say after reviewing your support.zip that you submitted in his thread.
[Magisk] jons99:
yeah no dude you have a bigger problem I just looked at the support thing you submitted in the pixel flasher page it sims you tried to flash your rom using the latest platform tools which has a problem with fastbootd so you need to use an older platform tools to flash your rom again
[Magisk] koberulz:
Well as I said in that thread, I don't know where to get the older versions.
[Magisk] J.Michael:
Can you explain "have working Magisk" at the same time as "Don't have root"?

Do you understand the two parts of "Magisk"? The part that gets injected; i.e., the part that requires that you patch an image. And the part that is just an Android app, formerly officially known as Magisk Manager.
[Magisk] Lughnasadh:
For those that don't know, Platform Tools versions 34.0.0 & 34.0.1 have a problem booting into fastbootd. There have been several users who have ended up with unresponsive phones while flashing factory images on Pixels. Version 33.0.3 is the last correctly working version. Google is aware of this and is working on a fix.

Here is a link to a link to 33.0.3.
[Magisk] koberulz:
When I click on "Magisk" in the app drawer, it opens the app. As opposed to previously, where it did nothing, or threw a "this app keeps stopping" error.
[Magisk] jons99:
use this
[Magisk] pndwal:
So guessing Magisk Installed = N/A still...

To be clear, that's not working Magisk! 😉 PW
[Magisk] koberulz:
Okay, so I've booted, and I have root, and I can open the Magisk app, but I don't have Zygisk.
[Magisk] J.Michael:
Why do you want Zygisk?

Did you look in the working Magisk manager app to see if there is a setting "enable Zygisk"?
[Magisk] koberulz:
It's working more than it was before. Although the hidden app icon is still there and clicking on it still gets me a "this app has stopped working" error. Ugh.
[Magisk] koberulz:
I don't know what Zygisk is.

Okay, seems it's a setting, and I need it for the new Magisk Hide equivalent, so...I need it.

Now...there was another thing to do with SafetyNet, right? I HAVE TOO MANY OPEN TABS, ugh. And I need to hide Magisk again, right?
[Magisk] pndwal:
Yup... My remark was just for clarity; App is only a Magisk UI / 'dashboard', not Magisk... Magisk itself still isn't working... PW
[Magisk] koberulz:
In what way is it not working? I have root, and everything seems as it should:
[Magisk] pndwal:
Zygisk is extra (hooking) functionality for Magisk... You'll only have it once Magisk is actually installed and recognised by the Magisk App (please don't confuse the two)...

In App you need to see a version under Magisk Installed, not N/A, first... PW

Edit: Yes! Magisk is good now!
[Magisk] koberulz:
Well my first takeaway is that Android 12 was clearly designed for blind people, JFC. Is there any way to shrink the UI down? I have basically nothing in my quick settings now, the pad to enter my PIN on is bloody huge, the clock occupies the entire lock screen...
[Magisk] zgfg:
To enable Zygisk, go to the Settings and enable - eg, you will need for USNF

About the Zygisk is covered in the OP posts
[Magisk] J.Michael:
Check Android settings -> Accessibility -- maybe there's a "zoom" option.

Failing that, take things one at a time. Look at the clock on the lock screen, maybe there were several widgets to choose from and you chose (or had chosen for you) a really, really, big one.
[Magisk] J.Michael:
I would suggest *not* hiding Magisk until you need to. Never mind whether you used to. Try the suggestions about USNF and HMA. Which really means, until there is an app that refuses to run, don't bother with anything.
[Magisk] exis_tenz:
For that I use AOSP Mods, which is a combined Magisk/LSPosed module. It gives you at least the option to have a row of 4 shortcuts in your panel instead of 2. Still not perfect, because 6 or 7 is way better. I totally do not understand why anyone in Silicon Valley thought this was an update. To make QUICK TILES harder to reach. At least they could scratch the word QUICK now. TILES it is. Large tiles. Huge tiles. Ugly tiles. But tiles.

There IS also a forked and non-offical version of GravityBox for A12. Many things do not work though! And before playing around install a bootloop-protector in Magisk! I use GravityBox PURELY to re-map my onscreen buttons (double tap to sleep, for example).
[Magisk] Fishawy:
Does this GravityBox fork provide an option for more than 4 tiles in QS? And do they work on A13?
[Magisk] exis_tenz:
Nope, it's in there, but malfunctions (does nothing). What DOES work is "AOSP Mods", which can show up to 4 columns, but you can set the first swipe down to show 2 rows. That makes 8 in total. By pulling down, you can adjust another 8.
[Magisk] Fishawy:
Thanks, I'm already using AOSP Mods with the 8 tiles in QQS, but I was hoping for something that gives more than 8 (coming from OnePlus).
[Magisk] M3m3nt01:
Have you come accross a solution or a fix for this problem?
[Magisk] JAIMASS:
Hello Bro Am Having Mi 11x momo is detecting bootloader unlocked. Could you please elaborate the steps clearly. My device is snapdragon. How to backup the partition seccfg. Please tell the methods bro 🥺. As am I new to this
[Magisk] JAIMASS:
Bro also am having OnePlus 9R is this possible in OnePlus 9R. Because in momo it detects TEE broken. But I can bypass bootloader unlocked by safety net fix. How to bypass TEE broken. Is your method works for OnePlus snapdragon device. Could tell the method
[Magisk] zgfg:
He said that the method works for Mediatek - if you have Snapdragon, it's not Mediatek...
[Magisk] joegreat:
On my OnePlus 7T the manual downloaded Magisk 26.0 app installation/opening fails with "...was denied Superuser rights" - installed app version stays on version 25.2 (with recently updated SafteyNet Fix).

Any idea what the version 26.0 app needs/changed to be installed?
[Magisk] Homeboy76:
I don't have a OnePlus T7, but if you have Magisk 25.2 installed on it. Open the Magisk Manager. Tap the settings Icon and set the channel to Canary if you want to install Magisk 26001 or set it to Beta if you want to install Magisk 26 Beta. When the update arrived Tap Update then Direct install.
[Magisk] pndwal:
Very likely you still have a previous hidden Magisk App (stub app) installed... Uninstall the older App and conflict with 26.0 should be gone...

This can occur as hidden stub has different signing keys etc but dual apps will still compete for superuser control of Magisk... The App (UI) shouldn't ask for superuser permission anyway; it's usually a sign you have competing app iterations. PW
[Magisk] ashish1989:
I accidentally installed v26 beta, how can I roll back to v25.2 stable?