yashsingh1/xdaforums huggingface dataset:
[Magisk] 73sydney:
*Shameless Plug*

You dont need to lose your MagiskHide or Deny Lists, between ROM flashes, or swapping Magisk forks, if only there was an easy way to backup and restore those precious entries.....

GitHub - stylemessiah/MagiskHideDenyBackup: A simple magisk module to backup any apps you have in your MagiskHide or Deny lists for easy restore on new ROM flash

A simple magisk module to backup any apps you have in your MagiskHide or Deny lists for easy restore on new ROM flash - GitHub - stylemessiah/MagiskHideDenyBackup: A simple magisk module to backup ...

github.com

GitHub - stylemessiah/MagiskHideDenyRestore: A simple magisk module to restore any apps you backed up, using the partner MagiskHideDenyBackup module, on new ROM flash

A simple magisk module to restore any apps you backed up, using the partner MagiskHideDenyBackup module, on new ROM flash - GitHub - stylemessiah/MagiskHideDenyRestore: A simple magisk module to re...

github.com

:)
[Magisk] gorkemoji:
Hello,

I was trying to install Magish, it succeed, but whenever I enable Zygisk, Magisk says magisk doesn't installed on the device.

Anyone knows a fix for this?

Thanks in advance
[Magisk] J.Michael:
Forget about Zygisk, do you have Magisk installed?
[Magisk] gorkemoji:
Yes, I do.
[Magisk] bege10:
Thank you very much! I did not mess around with Magisk at all, just upgraded from Android 10 to 11.

I had uninstalled Magisk before I read your answer. Even uninstalling Magisk, flashing the standard boot.img and installing TWRP and Magisk again (this time by patching the boot.img instead of flashing the zip in TWRP) did not solve the problem.

Then I saw that the adb folder had not been purged completely when I had uninstalled Magisk. Is that normal? If it can create such issues it should be purged completely.

Deleting that folder did it! 👍
[Magisk] pndwal:
If you take Uninstall Magisk, Complete Uninstall from the App I believe everything should be removed from data/adb/. By "not purged completely" do you mean some files were removed?...

If you take Uninstall Magisk, Restore Images, Magisk (Mask/core) will be removed but config files (everything in data/adb/) will remain so you can take an OTA update and original config is preserved for when you reinstall Magisk... The App remains too.

Of course uninstalling the Magisk App is not uninstalling Magisk and won't affect conig in data/adb/...

If you did do complete Magisk uninstall, you'd also need to do initial Magisk install (fastboot flash patched boot image) again to reinstall... The delete-/data/adb-contents approach effectively gives you a clean Magisk installation w/o reinstalling...

So did you really uninstall Magisk (ie. take Uninstall Magisk, Complete Uninstall from the App) and find it failed to clean /data/adb?... Perhaps you just uninstalled the Magisk App (manager/dashboard)(?)...

🤠 PW
[Magisk] pndwal:
So to be clear, if you toggle on Zygisk in settings and reboot, you see 'Magisk Installed - N/A' in Magish App?... But you do have SU (Magisk root)/Magisk installed?

Maybe Magish is the issue... Where'd ya get that? 😜 PW
[Magisk] gorkemoji:
Yeah, exactly. I am 100% sure that Magisk root is installed and I am using a patched kernel.

I got it from GitHub, isn't it the correct place to get?
[Magisk] bege10:
After the system upgrade TWRP and root was lost because the system boot image had been installed. I installed TWRP and flashed the same Magisk version as before (25.2) from there as I always did before. Everything was in place as before the upgrade but the issue with Zygisk was there. And I guess the /data/adb folder was still there from before the upgrade.

I uninstalled Magisk completely, rebooted and then did the whole procedure as mentioned above. (Flash standard boot.img, then install TWRP, then patch this boot.img with Magisk and flash that. And the issue with Zygisk was still there.

It was then when I looked at the adb folder and at that point it was not empty any more, of course. And to my surprise the bootloop saver was still there - but that is installed in /data/unencrypted.

If you are right the folder had been removed through that procedure, but the issue with Zygisk was still there. And deleting the folder then finally solved the issue. So I have no clue what the reason was.

My conclusion: I will uninstall Magisk completely and have a look at the adb folder before the next Android upgrade.
[Magisk] zgfg:
Magisk Stable 24.2, from TJW GitHub?

Any particular reason why didn't you update to the newer Stable 25.2, or maybe even (as most of us), Canary 25205?

First versions with Zygisk (v24) did have some childhood illnesses, that were later constantly improved
[Magisk] bege10:
Sorry, a typo. 25.2 (I corrected the above post)

Do you recommend the Canary build? I thought the stable build is more of what its name says: stable.
[Magisk] zgfg:
Many run Canary here, incl. me

Canary may come with some new bugs (along with other fixes and improvements, but then they are quickly fixed with the new Canary release.

This 25203 was released like a month ago, I don't recall some regression reports

But probably there is no big difference to 25.2 Stable (equivalent to Canary 25201).

I thought you were really on the older 24.2
[Magisk] zgfg:
Attached the Changelog diff
[Magisk] bege10:
That's interesting, thank you! In my case removing the adb folder helped, but who knows whether the Zygisk fixes in the Canary would have prevented the issue.
[Magisk] pndwal:
Of course!... But for delta (stock incremental) OTA updates you'd need to take Uninstall Magisk, Restore Images (as minimum) as all images must be stock or AVB/update engine will prevent the update... Full OTA images or fastboot ROMs will work fine as whole images are just overwritten, but of course Magisk is lost...

No need to guess... You didn't take Uninstall Magisk, Complete Uninstall option!...

But apparently you didn't!... Please read what I said!

That's expected... If you thought you'd purged Magisk's config files and fixes an existing issue that way, you hadn't... Unless you did actually take Uninstall Magisk, Complete Uninstall option... But you've never indicated you did!...

... But I don't think you ever did 'empty it'!

🤔 What procedure?... You have apparently not done any procedure that empties /data/adb (only taking 'Uninstall Magisk, Complete Uninstall' option in App (generally reliable) or renaming magisk.apk to uninstall.zip and flashing in custom recovery (fraught)) until you manually emptied it!...

Nb mods like @huskydg bootloop saver can do more than systemless changes... That one patches boot image and adds files in /data locations other than /data/adb... Uninstalling should be done through proper module 'remove' options to call proper uninstall script... even then these don't always work properly... I've had issues removing bootloop saver in particular...

... That's why I suggested it! 😝

Conclusion is (and I did state it plainly in previous post if you read carefully):

• if you want to fully uninstall Magisk (ie both Magisk root (core/mask) and it's data confog files, take the in-App Uninstall Magisk, Complete Uninstall option... That's why it's there!!! (In BIG RED letters.) - Uninstalling Magisk App (only a 'dashboard'/UI app) or overwriting boot image won't cut it! 😝...

• If you want to clean Magisk configuration (effectively get clean Magisk installation but without losing root), just manually delete all files in /data/ADB and reboot... 😜

Please read this carefully!... Hope it's a bit clearer now! 😛 PW
[Magisk] Clandaries:
Wow,

when i read this, i can be really happy, that everything ist working on my Xiaomi MI 11 Ultra.

It is rooted with Magisk, even after OTA i have no problems to root it again.

I can use Wallet, my banking app, Netflix and so on.

I just will say thank you for this.

I wish you all a Merry Christmas an a happy new year :)
[Magisk] bege10:
Thank you for your detailed helpful answers. 👍

Obviously I was not able to explain what I did when. And it is not necessary to try it again because it is clear now what to do.
[Magisk] borisSweden:
How does the bounty system work?
[Magisk] pndwal:
Well in NSW Australia it doesn't any more; it was deprecated in 1841. See:

https://www.familysearch.org/en/wik..._Immigrants_-_FamilySearch_Historical_Records

Of course, you may be eligible to migrate to other (less?) desirable climes/lands of opportunity under a similar bounty scheme, but I don't know which (or which climes/lands either)... You'd need to consult with your local Migration Department, and it's often hard to determine if a government even has one (Migration Department I mean; bounty schemes may also be indeterminate)... 🙂

Spoiler content hidden.

😜 PW
[Magisk] philetus:
I have a Yoga Tab 3 Plus I have Lineage 18.1 on. I read that 18.1 is done and I need to install Lineage 19 so I wanted to update my TWRP to the latest and The TWRP app said I had to be rooted. I used Magisk before, but uninstalled it after a while so I downloaded the latest Magisk Manager and flashed it. The Manager then wanted to install the latest Magisk and sais my tab wouldn't let me so I looked for the Unknown sources button and could not find it where it was supposed to be. I ran the download anyway and Manager popped up the Unknown sources button for me. Anyway, I have latest Magisk and TWRP now and every thing works great.

What I need to know now is if there is a way for Manager to pop up the unknown sources button when I need it.

Thanks for any help.
[Magisk] vulcanrvn:
Hello,

Does anyone know if there is a way to stop magisk modules from creating folders at the root of internal storage?

If not then I guess it would come down to editing the modules myself to point them to create the folders in a different location right?

Thanks
[Magisk] 73sydney:
Which module is doing this, because magisk modules dont generally create folders there....
[Magisk] pndwal:
Does sound unique... I've noticed some XPosed modules put folders in /data/system that may be detected (eg Ruru detector does this). Eg HideMyApplist, XPrivacyLua... PW.
[Magisk] pndwal:
Yoga Tab 3 Plus LTE or Yoga Tab 3 Plus Wifi?

I never install that app... Nb. If you do, you'll need to hide it (using Hide My Applist LSPosed module etc) from some bank apps that detect this... (Many more also detect the TWRP folder)...

Also, you don't need root to install TWRP from PC using fastboot... But why not have Magisk!... You'll find plenty of uses for it...

Little confused by this...

Magisk Manager is very old... Last version was 8.0.7, provided for use with Magisk 21.4... Hope you have current App version 25.2...

(Current Magisk is provided w/ Magisk binaries and UI packaged together in a single package .apk. This installs UI simply as 'Magisk' app since John announced the death of Magisk Manager 2 years ago. - See Magisk v22.0 Release Notes.)

It's not Magisk doing that; Android System warns you about unknown sources etc, and lets you know if you need to alow installation from device or non-Play Store sources... The 'popups'/interface may well be tailored in OS skins provided by Lenovo/other OEMs also, and work slightly differently depending on device... You should get whatever options you need when trying run .apk packages from device however...

👍 PW
[Magisk] borisSweden:
Not like that, I mean getting something working on Android.
[Magisk] pndwal:
So "How does the bounty system work for getting something working on Android?"? 🥴

... I think you mean Google's bounty scheme for security bugs / vulns... Did you read the comments in my spoiler above? 🙂 PW
[Magisk] borisSweden:
Not bug related. I thought asking this on a MODDING thread would send the message right but I was wrong. But instead of spamming requests and pLsSiRjIoVoLtEnEeDnOwSiR, Im asking a open ended question. Its nothing to ask custom roms or OEM for.
[Magisk] xShx72:
Hello, could someone tell me if it's possible to pass safety net test using an older version of Magisk, namely v21? Or really any way of passing while having Magisk v21. The reason I'm asking is this temp root method only works for that version.

https://xdaforums.com/t/amazing-tem...rmv8-2020-08-24.3922213/page-50#post-82081703
[Magisk] pndwal:
Oh... Well beats me then...

But that's the point; perhaps if you could elucidate this 'bounty system' just slightly, someone may come up with an answer re. how it works!... (I may be a simpleton, but so far all I've read is spam... Just hadn't said so...) PW
[Magisk] 73sydney:
Its okay, i found the bounty hes looking for

Bounty (chocolate bar) - Wikipedia

en.wikipedia.org
[Magisk] pndwal:
Sure!...

Just enable MagiskHide if device launched with Android 7 or earlier... If a more modern device, use Riru + Ri-USNF...

You will probably want to pass Play Integrity deviceIntegrity now however since SafetyNet is depreciated... You may need a USNF fork modded to use Riru and to cause prop mismatches needed to trigger hardware verdict enforcement bypasses in PI API... @huskydg has such a fork...

I'm not sure what parts of MagiskHide or USNF will actually be needed for passing S/N or PI deviceIntegrity in you case, but it should certainly be easier for you with a locked bootloader than for most Magisk users...

Do you know the reason you cannot springboard to permanent root or use late Magisk by means of this exploit? PW
[Magisk] xShx72:
Hey, thanks so much for your fast reply. Unfortunately I have three old phones laying around the house and none seem to work except for an old LG M250N, which I can't unlock the bootloader on. I've tried MTK client to unlock the bootloader so I can perma-root it, however booting into brom is a whole different issue I can't figure out. It's running Android 7, and from what I've understood in your reply, it's less of a hassle to keep it at that, than it is to upgrade to Android 8 and root it with the said method?
[Magisk] pndwal:
I meant you may be able to permanent root from your temp root (see OP in your thread; it indicates 'some devices' can with this MTek exploit)... I know that's often what temp root exploits are used for, but I've no experience with this...

... Just meant you won't need to bypass HKA (hardware keystone based attestation) on devices w/ A7 LV (launch version)... nothing to do with RV (running version)... RV won't affect lack of hardware / keymaster version required for HKA! 🤪...

And knowing it's A7 LV, you shouldn't need USNF either as it only adds trigger for fallback to basic attestation evaluation type and trigger for bypassing hardware evaluation type enforcement w/ pre 24.0 Magisk... Your device will always use basic attestation by default... So simply enable MagiskHide...

Nb. If able to use Magisk 24.0+, you'll need to manually add gms attestation (droidguard) process to denylist and (likely need to) use MHPC or other solution to adjust sensitive props formerly handled by MagiskHide, or simply install USNF to handle these functions only...

👀 PW
[Magisk] pndwal:
FWIW, seeing some movement in Magisk again... 😃

@osm0sis has now fixed FlashAfterUpdate addon.d-v2 script (Magisk Survival Script for custom ROMs with addon.d support) issue (Magisk side) breaking A/B device w/ late Android Magisk survival 👏👍😋, now merged, Installation Instruction page is updated for P7 series and future A13 launch version devices (ie. w/ GKI related removal of genetic ramdisk from boot.img) and more commits merged... 👍 👀 PW
[Magisk] vulcanrvn:
Energized Protection and Font Manager both do this for me. I mean it makes sense because both modules use the folders as working directories for downloading and whatnot. I was just curious to see if there was a way to stop that and instead move those folders to the /data/adb/magisk/module folder instead.

Perhaps that wouldn't be wise?

If it's just me this happens too I csn figure it out if not then I'll message the module creators.

Thanks
[Magisk] pndwal:
Very sorry I missed this reply... Yes, GitHub, but my question was just a joke relating to your spelling (Magish)... Please disregard that...

You didn't give many details... Is device Galaxy S6 Edge or other?... Stock ROM or other?... Custom kernel? Versions? PW
[Magisk] gorkemoji:
It's okay man. I got you.

Yeah, it is with stock ROM (7.0)
[Magisk] zgfg:
You could inspect the module's scripts and change the paths

You can then redefine that temporary/working folders go to /data/local or /data/local/tmp, as some modules use

However, if a certain module is of Zygisk type (coming with the pre-compiled native code binaries), then (without recompiling those source) you cannot change its paths - check in /data/adb/modules/<it's subfolder> does it contain a bin or zygisk subfolders

Also, some modules may come with the accompanying applications (like LSposed, Viper4Android), hence again you can't change the paths that are hard-coded into those apps
[Magisk] pndwal:
S8 and older kernel issue... So you'll need custom, ported, fixed or newer Kernel; please check kernel version in use and read pinned issue linked from here:

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

... Could be time to use root on your Xiaomi devices... 😜 PW
[Magisk] zgfg:
Btw, official TWRP 3.7.0 for Android 12 is out, but still for a limited number of devices:

TWRP 3.7.0 Released

TWRP 3.7.0 is out now for most currently supported devices.

twrp.me
[Magisk] m0han:
Happens to me with HMA and Xposed Edge, which is probably why I can't get rid of the related detections in Ruru app.
[Magisk] zgfg:
I don't have XEdge but my Ruru does not report anything, specially it doesn't find HMA

Make sure that you hide HMA from Ruru (and other checkers looking for) by the HMA itself. Similarly, hide XEdge from Ruru and other checkers by use of HMA
[Magisk] ipdev:
Same as zgfg, I do not use Edge and I include HMA in my root blacklist. 🙃

Pixel 6 (Android 12L) and Pixel 7 (Current Android 13).

Note:

Momo show 'Found Magisk' on P6 due to iYT module. :unsure:

Edit:The iYT module does not trigger 'Found Magisk' on P7.

After clearing Momo, now it show 'Found Magisk' on P7 also. ¯\_(ツ)_/¯

Second half of my reply in the iYT - [xdaThread] - Post # 8​

Cheers. :cowboy:

PS.

I forgot to add Ruru to my Denylist on P7.

So I initally failed 'Abnormal Enviroment' test(s).

Added Ruru to Denylist, stoped and cleard cache of Ruru and rebooted.

Now P7 is the same results as P6.
[Magisk] m0han:
I've had as in the screenshot for a long time. Anything else to be done?

BTW, Where do you guys have HMA folder - /data/system or /data/adb/modules or.... ?
[Magisk] ipdev:
I am a bit confused by the combined screen shot. 🙃

Is the left half all that you include in your HMA root hiding blacklist?

What is the right half?

Looks like you are running HuskyDG's Magisk.

I have never tried his Magisk builds so, I am not sure what differences there are in setup. :unsure:

Spoiler content hidden.

As for HMA..

I have two blacklists.

- Magisk

The missing third app is the regular Magisk apk.

Since I repackage (hide) Magisk, only 'Settings' is found.​

- PlayStore

---

panther:/ # ls -la /data/system/hide_my_applist_qmkinlvpuvaffpxi/
total 18
drwx------ 3 system system 3452 2022-12-18 20:40 .
drwxrwxr-x 28 system system 8192 2022-12-24 15:21 ..
-rw------- 1 system system 694 2022-12-24 15:24 config.json
-rw------- 1 system system 3 2022-12-24 13:32 filter_count
drwx------ 2 system system 3452 2022-12-24 13:32 log
panther:/ #

---

Hope it helps more than confuse. 🙃

Cheers. :cowboy:
[Magisk] pndwal:
Seems to vary (wildly?) per device / ROM...

Not as simple as correct configuration in HMA for some of us...

Funny how the detections show up in different places; Nb. Yours (Xiaomi Poco X3 NFC, A 13 crDroid v9.0 I assume?) are quite different from mine (Xiaomi RN8T, A10 stock MIUI):

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

🙃 PW
[Magisk] zgfg:
Please excuse me but I'm absolutely not able to understand why do you list Magisk Delta and Viper4Android as Effective Apps in HMA

What would you hide from them - Delta and V4A are not banking apps, they are not checkers like Ruru, Oprek or TB-Checker

Effective apps list should not contain the apps you are hiding (Delta, HMA, XEdge), but the apps that try to detect them (hence banking apps and checkers like Ruru, Oprek, TB-Checker, etc)

I said that you have to hide HMA (and XEdge) from Ruru

Therefore, Ruru must be in the Effective apps list (not Delta or V4A) and Ruru must be linked to the Blacklist template listing Delta, HMA, XEdge and other apps you may want to hide from Ruru

Ad the same for real banking apps and other checkers like TB-Checker or S-Check - enable each of them in the Effective apps list and link each of them to the same Blacklist template listing Delta, HMA and other apps you want to hide

Please carefully read several times every bit in the OP post #1 by @73sydney, his excellent guide how to use HMA:

https://xdaforums.com/t/hide-my-applist-a-brief-guide.4519731/

Concentrate to the part from paragraph "Configure HMA" till the end of his post

Everything is described there, and no need to repeat the same here

NB, I have two phones, one with Magisk Delta, the other with official Magisk Canary.

And I have HMA configured the same way on both my phones, and my Ruru (S-Check and TB-Checker as well) is completely green on both, not detecting anything (specially, not detecting HMA)

And yeah, on both phones I use V4A, and I have absolutely nothing related to V4A in my HMA config on either of my phones
[Magisk] pndwal:
... And now my long-standing issue:

Magisk cannot detect key events correctly #4624

is finally closed with a fix:

Support detecting safemode by ro.sys.safemode... Thanks Shana!

if (getprop("persist.sys.safemode", true) == "1" || check_key_combo()) {

becomes

if (getprop("persist.sys.safemode", true) == "1" ||
getprop("ro.sys.safemode") == "1" || check_key_combo()) {
...

... I'm looking forward to testing new improved safe mode key-combo detection for reliable module disabling (when modules cause bootloops etc) on MIUI and some other devices that could enter Android Safe Mode but still fail to disable modules...

😛 PW
[Magisk] ipdev:
The commits since the last release have not had a negative impact for me.

Hope John releases a new canary or release build soon. 👍

I have been running personal (snapshot) builds for a little while. 🙃

Cheers. :cowboy:
[Magisk] m0han:
Yes. Left is 'Manage Templates', right is 'Select Effective Apps' as indicated in the screenshot (attached afresh). Yes, Magisk Delta Canary latest (almost always).
[Magisk] m0han:
Xiaomi Poco X3 Karna (non-NFC), A12.1, AICP rom of 23.Dec.2022
[Magisk] m0han:
Magisk App gets flagged if I 'take it out of HMA'. Please check the screenshot attached.
[Magisk] pndwal:
I think John'll drop one on us soon...

But is there a difference between building personal snapshots and trying topjohnwu CI builds from official actions?... I know other builds there are from forked commits and often represent changes not merged in official (and I've tried these too sometimes), but John's (at least generally) seem to be merged as soon as they're built and combine all earlier TJW commits also... PW
[Magisk] pndwal:
...if you 'take it out' of 'Apps Invisible' to hide from Ruru etc?... sure...

But I think he's asking 'Why have Magisk in 'Apps applied to' (apps you're hiding applist items from), formerly (pre 3.0) known as 'Effective Apps'... PW
[Magisk] zgfg:
Can you shortly describe how your problem Magisk not detecting key combo for Safe mode on MIUI will be resolved by Magisk checking ro.sys.safemode

Does it mean that you actually did enter Safe Mode but on your Xiaomi Magisk did not detect Safe Mode because Magisk was looking for persist.sys.safemode while on Xiaomi Safe Model is flagged by ro.sys.safemode or how

Ie, the problem was not in the key combo but in different prop flagging the Safe Mode?