yashsingh1/xdaforums huggingface dataset:
[Magisk] meric57:
Hello, ask for advice or help here I rooted with those tutorial https://xdaforums.com/t/recovery-un...-s10-exynos-g970f-g973f- g975f-g977b.3924856/

As you can see, I asked for help on the last page on this topic.

I restored magisk apk hidden for update, I have to do it directly magisk or redo with the tutorial a month ago, I just flashed magisk 25.0.APK in the TRWP zip, when I did, no way to start the block on the Samsung logo and start Android.

I had to start in TRWP recovery mode every time and save the restore, the best thing to do is to know how to update it.

Thank you

​

Do you have to uninstall magisk already installed to install magisk25.0. modify official AP Firmware again with magisk. extracted boot.img from AP patch_magisk and flashed with magisk25.0. see screenshot application installer 25.0 above updated. How to update, I tried with TRWP not its plant and with magisk the same.
[Magisk] Timmmmaaahh!:
┤Maintenance├┤Moved all new itsme related posts to its dedicated thread: Itsme not working, this thread is busy enough as it is :)├
[Magisk] J.Michael:
@pndwal I blame you. I admit that I contributed.

No more references to Hoagie mode.
[Magisk] zzz2002:
I did this after I dropped my S7Edge into my Koi pond, about 18 months ago. It sank into about .75 metres of water.

I heated the device in order to remove the back, to try and dry it, however I did not expect it to be salvageable. After several hours of blowing heated air over it I was surprised to find the S7edge was working well.
[Magisk] Zaxx32:
I'm baffled atm although I'm still a novice...go figure.

Everything was fine...until I decided to update to 25.0 using Magisk manager. I enabled the beta channel then updated. It flashed and asked for reboot...after reboot the magisk manager is nowhere to be found...not in the app drawer and not thru settings > apps. Tried another reboot, still no magisk. Tried a reinstall...about 2-3 sec. after opening it just returns to my file mgr. At first I just assumed I'd just lost root...but when I launched an app with su privs...it said su privs granted! After a brief look around, I realize I'm still rooted but unable to find MM. Migiskd shows in app mgr. Dunno why I can't find MM...but Fox's magisk manager loads fine, shows all my module details.

I'm hoping there's an easy fix without having to reroot (my P4a is an A/B slot dev. so no twrp!)...and I don't I wanna lose my /data.

Please gimme a clue cuz I'm stuck and do not wanna wipe...😣
[Magisk] zgfg:
Describe:

1) What was your previous version of Magisk you updated from?

2) Did you have your previous Magisk app/mngr hidden/renamed?

You had to unhide before updating (well, well known issue, tons of times suggested here and elsewhere).

Find your old hidden/renamed Magisk app/manager and uninstall it

3) How did you install Magisk v25 - you 'flashed' - what does it mean?

You downloaded and renamed the Magisk apk to zip and flashed through TWRP?

Did you install Magisk application v25 at all?

Recommended way for installing is: update to the new version of Magisk app, then use that updated Magisk app to patch the img and flash the patched img through Fastboot!
[Magisk] Zaxx32:
I've never hidden or renamed magisk ever...never needed to pas safety net.

Updated from 24.3 to 25.0.

Updated via MM as mentioned...

No, 'I' never flashed the update...MM did...as mentioned

Didn't flash the boot'ing or anything else. Was just a simple, basic, plain update using Magisk itself.

TWRP is not supported for the Pixel 4a...also mentioned.

After I updated, like I have done every time b4, by clicking update IN MM...after which it asks for reboot. After reboot, no sign of MM but I still have root...I do not need to make a new image to flash.

Plz maybe review my post.

After googling I maybe found the answer...clear the dalvik cache.

Need a second opinion if anyone knows...🤔
[Magisk] zgfg:
Still I don't understand what exactly and how did you update. Can you describe it step b step, what did you clicked, or downloaded, etc

Magisk app only flashes the update if you use Direct install. Otherwise you only update app/mngr, but not Magisk

There are two 'things', Magisk itself and Magisk app. Updating only the app does not mean that Magisk was also updated

Also, use Terminal and type in:

magisk -c

to see which version of Magisk (not Magisk app) does it report
[Magisk] ipdev:
What version of the Magisk app did you try to install?

I assume it did not install since you said if failed out after 2-3 secs.

What is Migiskd in your app manager?

There was an odd issue with the app on the canary 25000 release,.

Fixed a day or two later.

Some could not hide (rename) the app.

I had two hidden (renamed) apps installed.

One was current and correct.

The other was a version or two older than the version I updated from. 🙃

I just eventually uninstalled the older one.

Canary/Debug 25001 included a few more commits and was released.

Magisk beta 25000 was released with canary 25001 so, it should have the same commits as canary 25001.​

If Migiskd is the Magisk app (and it does not open) you can try clearing the cache and data of the app.

--

The app is separate from the Magisk installation.

You can clear the cache and data of the app or even force stop and uninstall it.

You might need to reconfigure settings of the app (depending on what you did).

Update channel and other preferences like Notifications for example.

Magisk's setup/configuration is stored in Magisk's database file and will not be affected.

Superuser list, Denylist, Zygisk for example.

Cheers. :cowboy:
[Magisk] gd48202:
I updated from 24.3 to 25 by flashing the magisk 25 zip in recovery. The installation went fine, but I am encountering a problem where the app is constantly asking if I want to grant Superuser Access to an app. When I check Magisk in the Superuser tab, it states that no application has requested access. Magisk is no longer keeping track of the apps that require su access.

Any help is appreciated.

GD
[Magisk] Zaxx32:
MM = Magisk apk (aka Magisk Manager)

Edit: mk... 'magisk -c' returns '25.0.0''
[Magisk] ipdev:
So you only updated/install the App and did not updated/install Magisk in the Magisk app? :unsure:

Open the Magisk app.

Update (install) App.

Update (Install) Magisk.

Direct install (Recommended).

Reboot.

The prompt to reboot, should only only show after Magisk finished patching and replacing the boot image.

Cheers. :cowboy:
[Magisk] Radulescubg:
Hello all.

I just updated from 24.x to 25.. And now, even with zygisk enabled, momk detects su

I tried to uninstall magisk completely, rebooted, restated in recovery, flashed the latest alpha apk in twrp, restarted to system, opened alpha, downloaded the full app, enabled zygisk again, restarted, and added momo to the deny list.. Still sees the su.

Also, some other random errors that were not there until I tried to upgrade ( apart from selinux one)

Am I doing something wrong or..?
[Magisk] heinhuiz:
I 'clean flashed' 25 and encountered the same behaviour, but after a few reboots the Superuser tab started displaying the apps and their status was retained.
[Magisk] pndwal:
Just an observation re. late Magisk changes (may affect ItsMe users and other bank apps):

Since some are stating ItsMe (and other) are now detecting Zygisk I made the following test (and I still cannot narrow down what is actually detected / am not sure we can say definitively what is detected):

With latest Momo detector, USNF, hidden Magisk App, Shamiko and Magisk 25001, Momo shows:

- Latest ItsMe ID app is detected. (HideMyApplist is also properly configured for this app.)

Wanted to see how latest Momo & ItsMe ID apps responded to (older) Stable Magisk 24.3 (with latest USNF, hidden Magisk App and Shamiko also), so I downgraded and get:

- Latest ItsMe ID app is detected also, whereas previous versions passed with this setup.

So, while something in Magisk 2500x is clearly breaking Zygisk hiding in Shamiko (I suspect this is due to changes brought with Johns new 25.x security enhanced linux policy (read sepolicy rules) injection), I cannot conclude from this that this/other apps are now detecting Zygisk hooking since it still detects 'root' where latest Momo is not detecting Zygisk...

Of course these app devs could quite conceivably have found ways to detect other traces of Zygisk (not yet implemented in Momo by vv and Rikka), but since we can still bypass root detection by new ItsMe in Alpha Magisk with traditional MagiskHide but not in 24xxx (where Shamiko is still successfully hiding Zygisk from latest Momo), my guess is that late ItsMe security is likely detecting something different...

@Stillhard, @Eng.Raman

I've posted this here since I've seen assertions that apps like this are now detecting Zygisk, but no concrete evidence... 😬😜 PW
[Magisk] zgfg:
You tested now with 24300 Stable?

Bcs my Momo 4.2.0 (and 4.1.1 I think) started to report Zygisk found with Canary 24314 or so (definitely, Momo 4.2.0 with Magisk 24316)
[Magisk] pndwal:
Yup, 100% as stated... PW
[Magisk] Radulescubg:
Welp. I uninstalled magisk 25, installed again 24.3, enabled zygisk, installed back the modules, Shamiko and USNF...

Time to clean flash the rom again. Fml.

Or if anybody know how I can do a proper "clean-up" of any magisk remnants, so can give a another try to reinstalling 24.3.. I'm open to any ideas
[Magisk] pndwal:
I believe this problem (a bug) occurs when Magisk app was hidden or you take Hide the Magisk app option and the routine fails to remove the full app which seems to be detecting the call for superuser permission from the stub (and I'm guessing this should be properly handled by the Magisk daemon).

Please see my post following the next for a simple fix. 🙂 PW
[Magisk] pndwal:
Yup... Just delete all contents of /data/adb using root explorer if root isn't lost, custom recovery or ADB... After that, ensure only one Magisk app, the full version (not stub) is installed, reboot, and Magisk daemon should rebuild database and other Magisk config files.

Nb. You can leave module directories intact if you understand their setup structure, or just install the again later... All best, PW
[Magisk] pndwal:
Simple Fix

There are clearly still issues in current builds with the way a hidden Magisk App (stub apk) updates, and even with initial hiding.

A simple fix in (probably) every case where things go wrong (and this can be done at any point in the. process also) is to 'clean' install app as follows:

- Simply uninstall all Magisk Apps*, go to Magisk GitHub main page, select the Magisk build you want from Downloads, install that and then take Hide the Magisk app option if you wish.

*Nb. If you cannot locate, go through list in Device settings, Apps, and find Magisk App(s) named 'Magisk', 'Settings', or 'yourcustomname'.

Nb. 2. Even this 'clean' installation method may fail with message

and/or one requesting superuser permission for Magisk app.

In this case I found that the unbidden app is actually still present, and a second attempt succeeds. So just close and ignore the messages (don't continue, don't grant), remove only the partly set up stub app ('Settings', or 'yourcustomname'), open Magisk App and take Hide the Magisk app option again --> profit (hopefully!).

Hope it helps. 😊 PW
[Magisk] zgfg:
Ok, you do have Magisk v25 installed.

Seems something went wrong with just the Magisk app - see the post right before mine:

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

To reinstall just your Magisk app Beta v25, go to Magisk GitHub, click to Download / Magisk Beta v25, and install the downloaded apk (as any otherapplication, not by flashing):

https://github.com/topjohnwu/Magisk/releases/tag/v25.0
[Magisk] Zaxx32:
k...headed to bed... thought I'd post the cliff notes

1 - 'magisk -c' returns '25.0.0''

I see my apps being granted su privs...and they work

So I AM rooted with v.25...

2. Magisk Manager v25 APK app shortcut is not where to be found...

Not in app drawer, not in Settings>Apps nor Storage>Apps....

Not in root section either.

3. I installed an .apk that reqs root, as a test. After installing it boot then req. root privs AND my fingerprint for validation...so MM v25 actually works.

4. Opened Fox's Magisk Mgr...it showed all my modules working fine even updated one.

So...what I had done: In magisk mgr. v24.3, I went to prefs and selected BETA as my update channel. Back on the main page it notified me of the avail. v25 beta update of course....I clicked the update option...it did its usual update stuf then, ofc, asked me to reboot. I did so and after bootup...I realized I couldn't find the new v25 anywhere...yet I'm rooted...obviously, w/ v25 as stated.

What I've tried...Checked everywhere even swapped to Pixel Launcher with no luck. I use Nova fwiw...and I checked the hide app list too...nothing, cuz I've NEVER hidden any apps EVER on any phone of mine. Never used magisk hide or anything...never had to pass saftey net...Keep my financial on my very solid and never rooted, bone stock Moto G7 fliw. Also looked in root directory folders...nothing. Lastly I tried flashing the Magisk Man. v25.ZIP file using FKM...after the reboot...STILL no luv.

My only sighting is a 'magiskd' process in my app mgr.

Lastley a few ss of the magiskd process.

It's now 7am here by New York. I've been beating on this all morning...I GOTs ta sleep. Sorry I did not have time to read the new posts first...getting back up at noon. Will read every post I see and try all suggestions.

THANX A LOT GOOGLE! for this A/B slot, dynamic updates scheme and no recovery options for ur biggest fans...those who root! smdh... /endofrant

😒
[Magisk] mingkee:
Is there any solution of Netflix error -93 on rooted A12 (Moto Edge 2021)?

I have to cancel root and lock the bootloader to make it work again

This gives me a concern: does A12 successfully nuked root for good?
[Magisk] martyfender:
You don't, by chance have a hidden magisk app named settings, do you? One clue is 2 settings apps. If you renamed it, it could be something else.
[Magisk] Zaxx32:
I've never hidden or renamed magisk cuz I've never needed to pass safety net or dodge detection...as mentioned...
[Magisk] Zaxx32:
Already tried that. Also tried flashing the v25 zip. Was the first thing I tried, I think...no luck.

"You can clear the cache and data of the app or even force stop and uninstall it."

I can't find any trace of the apk...no 'way' to uninstall/reinstall. That is my problem! 😖
[Magisk] heinhuiz:
I didn't read all posts about your problems, but if I were you I would flash the original boot.img of your ROM, boot with it, try again to find a Magisk app and if I did, delete it, and finally install the Magisk 25 zip again through recovery. Did you try that?
[Magisk] Zaxx32:
I might try this soon. But I have a Pixel 4a with A/B slot bs...no (official) twrp support. I'm to the point where I may just wipe and reroot and reinstall everything when A13 comes out of beta. 🤔🤔
[Magisk] ipdev:
Zygisk has not been detected for me recently.

There was something I did (or did not do) that allowed Zygisk to be found before.​

I do not remember what it was. 🙃​

For me, Momo just shows Debugging mode and Bootloader unlocked.

I had time to try the DenylistUnmount module today and got the same results. 🙃​

---

Do you notice any difference if you remove this process from the denylist?

isolated|io.github.vvb2060.mahoshojo:io.github.vvb2060.mahoshojo.maho.MahoService2

It made a difference for me before but, not any more.​

Cheers. :cowboy:
[Magisk] heinhuiz:
I love A/B, it saved me several times from problems like you experience by just booting from the other slot.

If you have an unofficial TWRP that is working, you can use that to dirty flash your ROM and if it doesn't boot change back to the other slot. If it does boot and, you install magisk.zip with TWRP, it will be installed to the other slot, so you can revert to the previous slot again in case of trouble.

Let's say you're on slot A now.

Dirty flashing your ROM will put it in slot B. If it does not work you can revert to slot A again with TWRP and you're back where you started.

If it does work, and next you flash Magisk through recovery, it will be installed in slot A. Like before, if that gives you problems, you can go back to the previous dirty flashed install in slot B with TWRP.

I think it's brilliant.
[Magisk] laur89:
What's the deal with vbmeta.img patching? Magisk wiki isn't too clear about it.

I'm on Mi 9T Pro, and adb shell ls -l /dev/block/by-name returns an instance of vbmeta, hence my phone has a separate partition for it.

This means in Magisk Manager app -> Install -> I untick both the

Patch vbmeta in boot image

&

Recovery Mode

options. Then successfully patched boot.img. But when I selected vbmeta.img for patching (ie same procedure as used for boot.img beforehand), then Magisk console errors out:

- Device platform: arm64-v8a
- Installing: 25.0 (25000)
- Copying image to cache
! Unsupported/Unknown image format
! Installation failed

From the wiki linked above I can't figure out how one is supposed to produce a patched vbmeta.img. Any ideas?
[Magisk] martyfender:
If you still have root, as you state, open a root file explorer and go to /data/data/. If the magisk app is not hidden as you state, you should find a folder named: com.topjohnwu.magisk, unless the app was somehow uninstalled in the process of updating. If it was some how mistakenly hidden, it will have some random package name.

If none of this helps, wiping your device may be the best option.
[Magisk] heinhuiz:
The wiki states:

Did you do that?
[Magisk] laur89:
Doesn't the last argument to the command - vbmeta.img - need to be the patched vbmeta.img? Based on the recovery/boot image patching instructions in the wiki I assumed vbmeta needs to be patched by Magisk app as well.

Or is fastboot the one doing the actual patching? If so, should I just extract the vbmeta.img from my ROM zip and pass it to the fastboot command? Or where should one acquire the vbmeta.img that's passed to fastboot command?
[Magisk] pndwal:
So not w/ 25001?

Just tested several builds to narrow it down w/ latest Momo...

For me (using RN8T w/ stock MIUI Android 10), 24315 breaks Zygisk hiding. In 24314 and earlier, Momo doesn't detect w/ latest Shamiko... So it may be this commit:

Fix zygisk code unloading or one of several others.

If you mean when Magisk (24315+) Zygisk is detected, then no... just tried.

Thanks for your info. PW
[Magisk] pndwal:
I don't think you answered this yet... I'm curious too... PW
[Magisk] zgfg:
Why do you need vbmeta?

I have Mi 9T for three years, went through MIUI 10 till MIUI 12.5 (A9 - A11) and some custon ROMs, all Magisk versions that were available in the meantime (incl unofficial Magisk versions like Alpha and Custom) and never, ever needed to bother with even v from vbmeta

Also, you have subforum here on XDA for Mi 9T Pro, guides and posts about installing Magisk, they don't mention vbmeta.

Did you successfully install Magisk without vbmeta - if so, then why vbmeta?

If you "need'' vbmeta for some custom ROM (?), then better ask for instructions directly where the corresponding guide was posted
[Magisk] J.Michael:
It looks like it is not so much that Magisk needs to patch vbmeta (the way it needs to patch boot or recovery), as you need to change some flags in vbmeta, and the fastboot flash command will change those flags.

So, here's another vote for "try the fastboot flash vbmeta" commands with the extra options. From somebody who has nothing to lose if your device melts.
[Magisk] zgfg:
From what you have previously posted, you do have Magisk Beta v25 already installed, hence do not attempt to flash Magisk zip again or so (if you did, and reflashed now something different from Beta v25, your ground had already changed)

You have the problem with Magisk APP - it is called APP not Manager anymore, hence please be precise and do not use the term MM. Unless you really tried to install some ancient version of Magisk Manager?! Then who knows what's happening to you...

Btw, you mentioned magiskd in your MM - and couple of others already asked you about, what do you mean by that? I also don't understand what is magiskd for you in Magisk app (or Magisk mngr by its old name)?!

You also say that you never used Hide Magisk App. In that case your Magisk app (or even the old Magisk mngr) must have its original package name: com.topjohnwu.magisk

Hence, use ADB and execute:

adb shell pm list packages -f | grep topjohn

It should return something like:

package:/data/app/~~zzAk3kGwba_zaqNBLB_roQ==/com.topjohnwu.magisk-bK0p7-IYI3W2guIzkD4Cgg==/base.apk=com.topjohnwu.magisk

From that you can read the path where your Magisk app is installed. In my case as above (your 'scrambled' folder name will be different), it means:

/data/app/~~zzAk3kGwba_zaqNBLB_roQ==/com.topjohnwu.magisk-bK0p7-IYI3W2guIzkD4Cgg==/

Use root explorer like MiXPlorer (if I understood correctly, you do have Magisk/root), go into that folder and you will see there like on my attached screenshot (observe the Magisk app icon)

Delete that folder from /data/app, in my case (your 'scrambled' folder name will be different but similar) the folder:

~~zzAk3kGwba_zaqNBLB_roQ==/com.topjohnwu.magisk-bK0p7-IYI3W2guIzkD4Cgg==/

And then install Magisk Beta v25 app (NOT any ZIP and not any other version of Magisk app or the old Magisk Manager) from the Magisk official GitHub, exactly the link I gave you in my previous answer to you

When you download that Magisk app it shall be the file name:

Magisk-v25.0.apk

with MD5 checksum:

eeb3f44c82ffac76944a5f82d24b76f1

Install that apk and confirm all permissions it might ask you for
[Magisk] pndwal:
But I'd be very surprised if this is needed at all as @zgfg pointed out... except on some obscure devices, or some just getting Android 12 / 13 / 14* support... Always best to try following official Instructions first...

John has been doing his best to make Magisk installation seamless and prevent device specific options like this from even showing where not needed / likely not to work as they potentially allow users to break / brick their devices... If they can be safely used they should show in app, and be set without resorting to manually adding switches in fastboot as I understand things...

Of course, John still has to play catch-up for newest devices and OS's, eg recently for Pixel 6 running Android 13 Beta 2:

www.twitter.com/topjohnwu/status/1525034917670756353

*BTW, since you recently introduced a food theme to Android 'modes', can I use that as a segue to mention ǝʞɐƆ uʍop ǝpᴉsd∩ in relation to Android 14?... I Just learned this from John... (If there's trouble I'm gonna blame you...):

www.twitter.com/topjohnwu/status/1534576024494538752 🙃 🎂

🤠 PW
[Magisk] zgfg:
User asked for Xiaomi Mi 9T Pro - that device originally shipped with A9 and later was officially upgraded only till A11
[Magisk] heinhuiz:
Your question has been answered thoroughly above. If you follow the wiki correctly, you can see that you don't patch the vbmeta.img file itself, but - like @J.Michael says - the partition, by changing some settings:
[Magisk] razrielsch:
I tried to install newest magisk 25.0 on a lineageOs 18.1 on a Sony X Compact.

But it always fails from trwp. cant mount folder rca.

So whats my fault here ? Do magisk expect a specific folder which should be part of the lineageos ?
[Magisk] laur89:
The fact that users have been flashing 9T Pros in previous years without modifying vbmeta goes against the official Magisk install instruction which explicitly says to patch the vbmeta partition if your phone has one.

Who am I to tell if this is something that has been made necessary as of late, or it's always been optional? Or perhaps it's needed with a12.1 that wasn't out 2 years ago? Rather would follow Magisk guidelines than andecdotes.

Ah you're right, the wiki does make a distinction there. Thanks, all clear now.