yashsingh1/xdaforums huggingface dataset:
[Magisk] Prof_Shekhar:
Hi @pndwal

Thanks for your solution.

I went through the entire links but somehow I didn't understand the steps involved to fix my issues.

Request your guidance and assistance in this matter.

Thank you in advance for your time and patience.

Capt- Watson
[Magisk] DaOldMan:
I have read about your problems. All users telling you to stop looking for duplicate app are correct. All Magisk apps (no matter which name they have or their package name) are in the /data partition which is wiped completely when you do factory reset. Also all modules are in the same /data partition and yes, they are wiped too. So no need to hunt for any of those. Did you wipe your internal memory storage as well ?

Also all the root files in Magic are not in the /system partition but are added virtually by mounting. So no need to reinstall ROMS as your physical rom is just the same as before rooting. All Magisk rooting is virtual. That's the strength of Magisk, if you unroot and reboot all files will be unmounted and gone forever. No need to do any physical changes.

The fix must be in the other suggestions you got from users. I don't have currently a Samsung so I can't help. On OnePlus updating to the latest Magisk was totaly painless.

Good Luck !
[Magisk] pndwal:
Long and short:

Click Cannary in Magisk main page, downloads.

Try it.

Report.

👍 PW
[Magisk] xabu:
There is a setting where you can activate the on-screen navigation bar.

Might be very helpful for you ! Same as the restart options in Magisk under the

icon next to the settings-icon of Magisk.
[Magisk] xabu:
Ever thought of a total new approach by installing the lineageos for your note 8 ? LineageOS by @Ivan_Meler.

Then you' ll run Android 12 and together with Magisk a total new world will shine on your phone.

It's just an idea, no more ... no less.
[Magisk] zgfg:
I have a strange problem with patching.

First I thought I'm insane since I have two Xiaomi phones and I was updating through the Alpha versions, and I recall that patching sometimes worked and sometimes not

(if it didn't work I reluctantly updated Magisk by Direct method).

But yesterday evening I had the following situation:

1)

Mi 9T, MIUU 12.5.2, A11

latest Alpha f880b575(24101)

To my surprise, I was able to patch the stock boot.img, the already patched img and the boot.img from my other Xiaomi phone Mi 11 Lite 5g NE.

Tried several times and it worked without any problem

Later in the evening I rebooted Mi 9T (because of updating hosts file for AdAway), hence I did not change/update the ROM, Magisk, modules, settings, nothing

And then I came back to the situation that patching did no more work (like couple of days ago when I tried the last time):

- Copying image to cache

- (waiting)

- Process error

There is no problem with my boot images - they are always the same for whom the patching worked on the same phone an hour earlier

Screenshot and log is attached, log says nothing, the same error as above

The first time I observed this Copying img to cache error was in one of the last Alpha versions.

I always install/update Magisk by patching and flashing and I absolutely never had that error with any of 2301x Canary, Alpha or Magisk Custom versions (betas for Magisk v24) over the last months

2)

Mi 11 Lite 5G NE, MIUU 12.5.8, A11

Also the latest Alpha f880b575(24101)

Here, I always have the same (again, for various boot images, the same that I tested patching on the first phone Mi 9T)

- Copying image to cache

- (waiting)

- Process error

I'm no more 100% sure but I really think that once back in time I was able to patch also on this phone.

Hence I went through the last three Alpha apk versions (no need to go further since the phone is new and BL was unlocked 15 days ago, at which time I first installed Magisk), and I retested but patching now always fails as above (this phone is new and ROM was not updated since the BL was unlocked)

Is there anybody else, specially with MIUI 12.5+, A11, and with any Magisk v24 observing the same problem?

Im suspicious that something has changed how Magisk handles the Cache:

- On my Mi 9T, from time to time (but that was never the case with earlier versions of Magisk), Viper4Android app claims that drivers are not present and I have to accept installing drivers/rebooting, and then it works again

- On the new Mi 11 Lite 5g NE, I can endlesly go through: V4A app asks to install driver, reboot, again no drivers/install/reboot, etc

But I checked in /cache, it's linked to /data/cache and magisk folder was never created (on Mi 9T there is one, with the V4A subfolder and with V4A sepolicy.rule file).

Even if I manually create /cache/magisk/Viper4Android and put the sepolic.rule file, it doesn't help for V4A
[Magisk] Prof_Shekhar:
Aye aye captain 👍🏻👍🏻

Have downloaded app-debug.apk from Magisk GitHub topjohnwu page.

Will try n flash tomorrow and will let you know the outcome.

P.s. Which Magisk app version to use with this Canary version Magisk?

Hi @

Hi @xabu

Unfortunately, those buttons on my Magisk app 24.1 or 23 don't do anything. They are just there for namesake.

Anyway, I have completely uninstalled the Magisk 24.1 version completely from my device.

Will attempt to install Magisk Canary version (app-debug.apk) tomorrow as suggested by @pndwal . Let's see how it goes 🙂
[Magisk] Prof_Shekhar:
Thanks @xabu for your suggestion.

Will definitely try it out once I am out of this mess 🙂
[Magisk] pndwal:
🤔 Since the death of the Magisk Manager, dearly beloved and mercilessly killed of by a 22.0 slug at point blank range, we now have the Single-package-Magisk-App! This was announced in the local rag along with the death-notice... you may have missed it:

https://topjohnwu.github.io/Magisk/releases/22000.html

... So you simply install the app and it will automatically patch or directly install the included (matching version) Magisk mask/core! - Ie. App version should always match the Magisk (mask/core) version.

NB if you change the Update Channel to from Canary to Beta or Stable the app will still patch with Canary version (currently 22102) until you downgrade the app to Latest Beta or Stable version now showing on home screen (which will currently be 24.2 (24100)).

Special Reboot menu is a root feature; it will work once root is available to Magisk app.

... originally suggested to you 2 days ago by @yujincheng08 (LoveSy / Shana):

https://github.com/topjohnwu/Magisk/issues/5339#issuecomment-1030898268 😉 PW

PS If you or anyone else wants to catch up on major recent Magisk changes, may I suggest a little essential light reading; last half dozen or so Release Note pages from here:

https://topjohnwu.github.io/Magisk/releases/

That'll bring most pretty much up to speed quick-smart!
[Magisk] zgfg:
Like a sitcom (Professor's Magic Mask). The plot is hard to follow, ever changing😁
[Magisk] pndwal:
More like watching a combination of Startrek, Sherlock Holmes and Bollywood Pop Idol... with a bit of Nutty Professor for kicks... sitcoms are much more predictable... 😜

One for Trekkies:

"The needs of the few, or the one, outweigh the needs of the many"... hang on... did I muddle that? Oh well, works either way...

Blink and you'll miss this! PW
[Magisk] Spartacus500:
There are applications that after hiding Magisk etc. still do not want to work on my Samsung, after removing Magisk they work without a problem, which is 99% of the reason for these two reasons that I do not want to hide in any way 😔 I hope that the new stable version Magisk will solve the hiding of these detected files 🤔

1. SELinux rules are modified

2. init.rc is modified
[Magisk] zgfg:
You can use InitRcHider -sceenshot.

Expected that Shamiko will hide init.rc in the future
[Magisk] Spartacus500:
I checked what I already wrote about it. Active in Magisk, but it doesn't hide init.rc, I uploaded it, restarted it several times and nothing, init.rc modified.
[Magisk] zgfg:
For me InitRcHider hides both for Momo and the old Magisk Detector
[Magisk] m0han:
already does, i should think. https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86389145
[Magisk] Spartacus500:
I'm okay with your tests, except for SELinux modified and init.rc modified. Hiding these two points doesn't work for Samsung.
[Magisk] m0han:
also on custom roms for samsung?
[Magisk] m0han:
if you wanna try another applist detector, check hma channel on telegram
[Magisk] Spartacus500:
Such a test does nothing, I wrote that all tests pass except SELinux and init.rc 😔
[Magisk] zgfg:
Ok, made it, just needed a courage (Confirm this flash, that flash):

Xiaomi Mi 11 Lite 5G NE

MIUI 12.5.8, A11

A/B, Ramdisk Recovery in Boot (only Boot partition, no separate Boot and Recovery)

- I booted to TWRP (actually SHRP)

- Flashed TWRP img from TWRP

- Flashed Magisk apk (renamed to zip - probably renaming was not needed)

Now I have both Magisk (Alpha 24101 - latest Alpha) and permanent TWRP (SHRP)

Normal boot to System boots to Magisk,

Reboot to Recovery boots to SHRP

Like on the good old devices with separate Recovery (for TWRP) and Boot (for Magisk) - but here it's only Boot hence both fit into (frankly, boot.img 192 MB makes a lot of room🥸)
[Magisk] J.Michael:
Have you read the posts between @Prof_Shekhar and @pndwal? Your initial problem sounds similar to me.
[Magisk] Svan987:
Can you give the exact post number that shoud help for my case ? Thx.
[Magisk] szazs89:
@Svan987

I think you should uninstall Magisk (from TWRP with renamed the apk to uninstall.zip)

Then try to install it again, reboot. and reinstall the apk if it seems necessary.

But first check the installation instructions given in the first few posts.
[Magisk] pndwal:
Does it show in MOMO w/o fix? ... Doesn't show for me (A10 RN8T) w/ or w/o. PW
[Magisk] Barkuti:
Just dropped by. :unsure:

I see the MagiskHide duties have been transmuted into something more powerful called Zygisk.

So is John Wu still developing Magisk, but its new camouflage or invisibility system development Zygisk has been delegated to someone else?

By the way, and not that I am in a hurry to upgrade, but according to something I read somewhere in the Magisk General Support / Discussion thread, it is necessary to disable MagiskHide before upgrading to the new Magisk-Zygisk versions, doesn't it?

Cheers 😊
[Magisk] pndwal:
Seems you have this:

https://github.com/topjohnwu/Magisk/issues/5339

Same Fix as for

https://github.com/topjohnwu/Magisk/issues/4174

Ie:

Make sure busybox can be executed recursively...

Busybox will execute itself. On some older Samsung devices, when it is located in /data, it will not have rights to execute other programs including itself. We should also relocate busybox in this case to workaround Samsung bull****.

See topjohnwu/ndk-busybox@bdc8655

Fix the "app doesn't detect installed Magisk" issue in #4174

canyie authored and topjohnwu committed 10 days ago

This is working / built in latest Canary Magisk 24102.

Nb. Zygisk issues in Samsung devices fixed / built in 24102 (not in 24.1) include:

Invalidate Samsung's persist.sys.zygote.early …

Samsung FDE devices with the "persist.sys.zygote.early=true" property will cause Zygote to start before post-fs-data. According to Magisk's document, the post-fs-data phase should always happen before Zygote is started. Features assuming this behavior (like Zygisk and modules that need to control zygote) will not work. To avoid breaking existing modules, we simply invalidate this property to prevent this non-standard behavior from happening

Fix #5299, fix #5328, fix #5308

and

Refactor Zygisk loading …

yujincheng08 and topjohnwu committed 3 days ago

NB. If you have very old pre 3.19 Samsung kernel the latter issue may not be fixed. See:

[Wontfix] Zygisk cannot activate on some old Samsung devices with old kernel (3.19-) #5395

🤠 PW
[Magisk] J.Michael:
I don't remember reading that it was important to disable MagiskHide before upgrading.

I do remember reading that it is strongly advised to undo "rename/repackage the Magisk Manager app" before upgrading, because sometimes not doing so causes problems, and there has never been a report that doing it unnecessarily caused a problem.

The first few posts of this thread summarize current best practices.
[Magisk] pndwal:
In addition to info above, please read release notes for current Stable build:

https://topjohnwu.github.io/Magisk/releases/24100.html

Also, John linked his blog on current "State of Magisk" from release notes for first Canary builds introducing Zygisk. Please follow links:

https://github.com/topjohnwu/magisk-files/blob/9537c5d8cedfc09ca723ae0392b1219e75d9b636/notes.md

These documents will appraise you of new changes / direction for Magisk.

👀 PW
[Magisk] Prof_Shekhar:
Hi @pndwal

Finally at last, able to get the Magisk 24.1 (Canary version) alongwith its app running smoothly.

Activated Zygisk, congigured Deny list, installed universal SafetyNet.

However, when running app security check - Device compliance app (as suggested by one of the senior members), I get all test passed except root detection which is failing.

Request your guidance and expertise once again to get me out of this fix.

Watson
[Magisk] zgfg:
Well, some days ago, without InitRcHider, my Momo was showing the Init rc detection (I'm pretty sure about), and when I installed InitRcHider it stopped detecting it

Now, when some components were updated (at least Shamiko), I disabled InitRcHider, rebooted, and Momo now does not detect Init.rc (hence maybe I don't need InitRcHider anymore)
[Magisk] pndwal:
24.1 is a public Stable build! You mean 24102!?

Please explain Device compliance app...

Is SafetyNet passing in YASNAC?

What fix?

🔎 Holmes
[Magisk] Prof_Shekhar:
@pndwal

The app which is showing "Root Detection not passed" is called:

Security check - Device compliance for payments.

Yes, you are right.

I have installed Magisk 24102 (screenshot attached)

I have also installed Shamiko.

However, I am still not able to get any banking app to run due to root detection issues.
[Magisk] hungtinglung:
hide magisk app.

install universal safetynet fix 2.2.1.

put all banking app in denylist(magisk settings,configure denylist)

Release v2.2.1 (Zygisk) · kdrag0n/safetynet-fix

Changes Fixed under-display fingerprint sensor on Realme devices (thanks @osm0sis, @byxiaorun, @Jowat97) Clarified definition of "basic attestation" in readme Add check to prevent installation on ...

github.com
[Magisk] pndwal:
Subverting bank app detection is a whole other ballgame. Some just use Safety net API, more and more don't trust this (wonder why) and use more and more sophisticated customised detection methods.

To pass w/ more basic checking, have you put bank app in deny list, then cleared it's data?

Do same for 'Security check' app and see if results change...

Also, set Hide the Magisk app function. PW
[Magisk] zgfg:
Btw, don't you have Screenshots on Sammy - it's much, much easier than taking photos by another phone
[Magisk] Prof_Shekhar:
@hungtinglung

I have already put the banking apps in deny list. Still no difference.
[Magisk] szazs89:
What about Shamiko to hide Magisk itself? (see post #9)
[Magisk] Prof_Shekhar:
@zgfg

As my Sammy is still in barebone state, found it easier to take pictures using other device where I have my XDA app installed and directly upload it than taking pictures on the device which was being completely wiped out everyday.

Surely, I'll endeavour to take screenshots going forward.
[Magisk] Prof_Shekhar:
@szazs89

I tried that option without any difference in the outcome.
[Magisk] szazs89:
You may try to reinstall the banking app (or clear its data)... sometimes they remember their failed root checks.

EDIT: and don't forget to reboot...

(Sorry if it is trivial 🙂)
[Magisk] Prof_Shekhar:
@pndwal

I have put the security check app and bank app both in the deny list.

But somehow I am still not able to hide the root.

Would you suggest that I should install stub-release app from topjohnwu (I think) to enforce the root hide. Don't know how effective would this be.
[Magisk] Prof_Shekhar:
@szazs89

That is the first thing I did, to uninstall the banking app and reboot the device. Reinstalled the banking app but it is still detecting root.
[Magisk] pndwal:
Did you delete app data after?

Phone-shot shows you've already Hidden the Magisk app... That calls the stub.

You need other solution, eg. Hide My Applist LSPosed module etc... PW
[Magisk] hungtinglung:
this is example only.

slime can only run in non root phone.

slime can only run in whitelist samsung phone.

i try to tick slime app in denylist magisk 24.1 without reboot.

can run normal at LG phone.

i have change the fingerprint to samsung phone.

i have try a few banking app,run normally at my rooted phone.
[Magisk] szazs89:
Are you using stock or custom Rom?

In the latter case you need MHPC module, too (see #7). And fake a stock fingerprint for the custom ROM as @hungtinglung mentioned.
[Magisk] Prof_Shekhar:
I'm using stock rom.
[Magisk] Svan987:
I went back to Magisk 23.0.zip (flashed in twrp) and added custom channel for version 23.0.

https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c304e59f631280cc26ccc6d40a7cf04f7f37/stable.json

It's a tablet without using any sensitive app. I will wait the stable update.

Thanx @pndwal
[Magisk] Prof_Shekhar:
Can anyone suggest me ways to access module library which was earlier accessible from Magisk app prior to version 24.
[Magisk] Prof_Shekhar:
@pndwal

Finally mate, you made my day.

Installed LSPosed and Hide my applist. Configured the Hide my list.

Lo and behold, all banking and financial apps started to work without any issues.

I would like to express my sincere gratitude to all seniors (@pndwal , @xabu , @J.Michael , @zgfg and all others whose name I may have missed) in this forum for their unflinching support and guidance to a wanderer like me to hit a home run.

🙂🙂🙏🏻🙏🏻🙏🏻
[Magisk] m0han:
try Fox's Magisk Module Manager. https://github.com/Fox2Code/FoxMagiskModuleManager/releases/tag/0.3.1
[Magisk] Spartacus500:
Could you please throw in the test from the MOMO app 4.0.1 🤔
[Magisk] Prof_Shekhar:
@m0han

Thank you
[Magisk] beeshyams:
Can someone share the link of momo app? Strange that I can't find it and the Github link to it is broken

@Spartacus500 ? TIA

Edit

https://t.me/Magisk alpha found it here in case anybody else wants
[Magisk] Spartacus500:
Momo(io.github.vvb2060.mahoshojo) - 4.0.1 - 应用 - 酷安
[Magisk] pndwal:
Ah yes, I remember your RealMe passing...

Note to Me; Bin RedMi, get Real... 😳 PW
[Magisk] kramer04:
Hello

Maybe i'm the only one with this problem. I didn't found nothing.

Zygisk isn't active on magisk.

tried with magisk 24 beta and canary.
[Magisk] pndwal:
Did you try with no modules active? Could be Hex Installer or other module issue I'm guessing (if you tried clearing dalvik cache etc I mentioned). PW
[Magisk] kramer04:
yes i tried without modules

it's a fresh install of last samsung rom for Note9 Android 10
[Magisk] zgfg:
My new Lisa is still growing up and under age for unlocking Bootloader till Saturday but I'm preparing for the day

1) OTA zip does not contain boot.img but 13.2 GB payload.bin.

However, there is Payload Dumper:

https://xdaforums.com/t/how-to-extr...ot-image-and-apply-root-to-the-phone.4263811/

Found under OnePlus but it successfully unpacked my boot.img for MIUI

2) Now a newbie's question.

Since Lisa (Xiaomi 11 Lite 5g NE) is the a/b device:

getprop ro.build.ab_update
true

should I flash Magisk patched boot img to boot, or to boot_a, or both to boot_a and boot_b?

Per my understanding, boot will refer to the current slot (boot_a) while boot_b will be used for next OTA - hence even better not to patch boot_b

3) I'm confused that

getprop ro.build.system_root_image
false

but is this maybe 'normal' for a/b device or because of dynamic partitions?
[Magisk] Lughnasadh:
Can't speak to your specific device, but I have 3 a/b devices (all Pixels) and I just flash the Magisk patched boot image like...

fastboot flash boot <nameofpatchedbootimage>

It will patch your current slot, whichever slot that may be. And yes, no need to and not a good idea to patch your inactive slot.

Then if you update via OTA you can use the "install to inactive slot" method in Magisk.

Again, all this based on experience with Pixel a/b devices only.
[Magisk] zgfg:
Alpha 3c7e7921
[Magisk] Ghisy:
Hey, does anyone know how to go from Magisk v23 stable with Riru + LSposed to Magisk v24 with LSposed Zygisk on Android 11 (and 12)?
[Magisk] godenk789:
I also passed the S-pushtan root detection

with Zygisk enabled, and USNF + Shamiko module installed. The denylist option is unchecked to make sure that the Shamiko module is working fine...

I'm using a pixel-based custom ROM, with an "abnormal" environment status according to Momo apps.
[Magisk] zgfg:
Pls read OP posts.

Also, you can follow my post #14 from two days ago

In short:

- Uninstall all Riru modules, reboot

- If you had your Magisk app in Magisk v23, hidden, Restore Magisk app from its Settings.

Or uninstall that hidden Magisk app that you renamed/repackaged/hid

- Update from Magisk v23 to Canary v24 (read below about):

There are several possible paths. As it said in post #14, carefully read Magisk Documentation, Installation guide available from Magisk Github

E.g , I would prefer installing Magisk Canary v24 app, then patching the image, and flashing (details described in the mentioned guide)

But if you used to install your old Magisk v23 through TWRP, it should still work

You are talking about upgrading Msgisk but yoz also mention A12 - I doubt thar you had Magisk v23 on A12. In that case fully uninstall Magisk v23 and first upgrade your phone to A12.

Similarly if you need to update your A11

- then follow post #14

- after all that, install Zygisk-LSposed and your LSPosed modules, configure them
[Magisk] HUMENTH:
Why the Bold Circle flashing at launch of latest Magisk v24 beta?

Device: Redmi Note 8 Pro

OS: MIUI 12.5 (Android 11)
[Magisk] Stillhard:
So you can put your middle finger in the center of circle?
[Magisk] guhvanoh:
... and press play.
[Magisk] crypticc:
If it is relevant..

.when I briefly tried Shamiko it didn't work and lost Google certification. That was v23 too.

But I don't want to misdirect in case I missed a step and actually Shamiko v23 might be okay:.

I had downloaded and installed Shamiko then re-selected the 2 required GMS services into the deny list in Magisk that USNF disables, and then turned off the deny list in Magisk per Shamiko instructions. I turned off USNF. And then rebooted.

...I had lost CTS and Google certification in the Play Store realise not the same problem your trying to fix here but are the Shamiko alpha momentarily not working as intended? Or was removing USNF my error (you said earlier that it serves different purpose)

Chris
[Magisk] Zuikkis:
I see in the changelog of v24:

"[General] Support Android 12"

What does that mean?

I have been running v23 (stable channel) with Android 12 for some time now with no issues. It is not supposed to work? SafetyNet passes, Google Play is certified, banking apps work.
[Magisk] pndwal:
Yup, you need both; Shamiko initially only hid Zygisk (it's akin to RiruHide), then ability to hide Isolated process leaks etc were added... You may not even notice it's affect until you use bank apps etc that detect modified TEE by means other than relying on SafetyNet API.

USNF is pretty much the new MagiskHide - don't disable it! (allows SafetyNet to pass as long as your device used a certified fingerprint for CTS (Compatibility Test Suite) with matching security patch date... (MHPC can do the latter if using custom or China region stock ROM etc).

🤠 PW