yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
I always manually download (and install) from their TG channel. Hence I control do I use Zygisk or Riru, Release or Debug (they deploy four versions per release)

And for quite some time I'm exlusively on Zygisk (Relese) zips.

And with their previous versions I never had that issue. When I downloaded and installed the latest from TG, it did not complain that there was a 'newer' one.

It just started about ten days ago with one of the versions from TG at that time. And still remains with the latest

Hence I'm not talking about installing LSPosed from PlayStore, but the versions they update/post few times a week to TG (or you can manually choose and download from their Github)

Besides, it's been long ago I switched from Custom Magisk and Riru to Alpha and Zygisk (when I uninstalled Magisk with all modules, particularly Riru modules). And I never had that issue during that time - and over that time I completely wiped Cache, Dalwik, etc.

But it suddenly started now with their recent releses

It's not a big deal, I know if/that I have the latest (Zygisk) LSPosed hence I don't need to pay attention what it complains ifI open the LSPosed manager.

I was just saying that it's strange (and some kind of regression bug, because it worked fine with their previous builds)
[Magisk] Nathan combrink:
Look I've got ramdisk and everything but I can't get in majestic installed
[Magisk] zzz2002:
Sorry to ask here but searching this thread/forum/... is like pulling teeth

Device hero2lte - lineage 19 by Ivan Meler.

1. where can i find FoxMmmm

2. what is Shamiko - i can't find it or a description of it.

3 ditto for magisk - my current version is "app-debug" 2022-01-03

thanks
[Magisk] Lord Sithek:
1. https://github.com/Fox2Code/FoxMagiskModuleManager/releases

2. Tool for hiding Zygisk. To be downloaded from Telegram
[Magisk] vandyman:
You need to install the ramrod app.

And use it with the mojo hider module.
[Magisk] Palazzo_K:
On my Samsung S7 Flat, I have Magisk apk installed in its latest stable version, however I need to install the alpha version. When I install alpha version, the application doesn't recognize the magisk(as you can see in the image). This only happens on the S7, as I did the same on a Moto G2 and recognized it normally. Does anyone have any idea what I can do?
[Magisk] J.Michael:
Uninstall the app before installing a different version of the app.
[Magisk] Palazzo_K:
Done, but still the same. As I said, it worked well on the Moto G2, only my S7 can't do it. First, I installed Magisk via TWRP on both, but since I had this problem on S7, I reinstalled the firmware and rooted it via flash boot.img in the Magisk app just to see if it would make any difference on it, but it stays the same.
[Magisk] pndwal:
Sorry, I'm a little confused; are you saying 23.0 worked fine? And what is the need for Alpha?

And please say if you OS is Marshmallow Nugat, Oreo or other... PW
[Magisk] Palazzo_K:
Yeah, 23.0 stable is fine. Alpha is fine too when installed in my Moto G2, but when I install it in my S7, it doesn't recognize Magisk installed and I can't install modules and stuff. Need alpha for Zygisk. Only way I can make an specific app run at my S7.
[Magisk] pndwal:
What Android version? -updated to Oreo? Or Custom rom?... Also, have you tried canary 23016 (for Zygisk)? PW

Edit: Does sound like dual conflicting app issue (hidden app not detected / removed by new one) as mentioned by others... Check for it in device settings, app info... default hidden app name is 'settings', or find what you chose...
[Magisk] zgfg:
Are you ABSOLUTELY sure that you don't have the old Magisk APK from v23 still on the phone, as repackaged/renmed (if you did in the past: Hide Magisk app)?

If you did so and if you still have that repackged Magisk app, that is then the reason that your new Magisk Alpha app cannot 'find' Magisk

You had to: Restore Magisk app (before updating!) or find it in the Settings/Apps (or Apps drawer) and delete that repackged/renamed Magisk app (you can still find and delete it now)
[Magisk] martyfender:
The hidden app is by default named settings unless you renamed it. You will see two settings apps in the app tray, one the hidden app and one actually Android settings.
[Magisk] Palazzo_K:
Samsung S7 Flat SM-GF930F Stock Rom 8.0.0. Is not conflicting app issue. I'm aware of that and restored Magisk before uninstalling the app, then runned uninstall.zip(both alpha, beta and canary) with TWRP to make sure everything is uninstalled properly. Then I installed alpha with TWRP and Magisk continue not being recognized. Uninstalled using TWRP(uninstall.zip) and done the same process with canary. Still, no sucess. Uninstalled everything again and tried to root with patched boot.img using Odin. I've done with boot alpha and canary patched images, one at the time, uninstalling the previous one, and still, no sucess.

When I rooted my Moto G2 was fairly simple, I uninstalled the app, used uninstall.zip(TWRP) and then rooted using the .zip alpha + TWRP. Everything is fine in this Moto G2. I just don't know what the hell is wrong with this Samsung S7.

Anyway, I appreciate the tips. If anyone has any more suggestions, feel free to speak and thank you in advance.
[Magisk] zzz2002:
s

thanks
[Magisk] pndwal:
I initially thought you likely have the longstanding issue here for Samsung Note 4 and other armeabi-v7a devices running stock Android 6, 7 (have root / display Installed - N/A):

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

There's been great recent progress with this issue and some test builds already work - scroll down to where Canyie gets involved - but I think so far devices reported affected are on A6, 7 - You're on 8 Oreo, and also reported 23.0 works; those guys can't use post 22.0 builds... however does seem you have armeabi-v7a...

You could test su from ADB shell to test if you have root as suggested;

- https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-1001114393

- https://github.com/topjohnwu/Magisk/issues/4174#issuecomment-1001133055

I mentioned a major fix for later Sammy devices here (already merged downstream, will be in next release):

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

but those guys got bootloops...

You could try the test builds in corresponding actions... Could be a new non-reported issue; if not a duplicate, please consider making a new issue ticket... PW
[Magisk] Tirofog:
I installed a PE GSI on my SM-T500 A7 then magisk. I then changed to a LOS GSI after a TWRP data format and fastboot system erase. I don't want to run magisk now, but the stub keeps showing in the app drawer and even after uninstalling it's back after a reboot. I've deleted everything magisk from storage and flashed the uninstaller but no luck..
[Magisk] J.Michael:
Could Magisk be installed in recovery, as part of your TWRP?

Does LOS come with Magisk installed?

Have you tried restoring the stock firmware?
[Magisk] cognitivedissonance:
Out of curiosity, did you ever get the Chase app to stop finding root? Mine allows me to login, but detects root when I click "Rewards" -- the popup verbiage is the same as you've listed.
[Magisk] HippoMan:
I can't find "Rewards" in the Chase app. How can I get to it, in order to test this for you.

Oh, I found "Rewards", and now it even works for me in the regular Chase app on my device!

One thing I did on my device a while ago was to hide the "TWRP" directory. I renamed /sdcard/TWRP to /sdcard/prwt . I'm guessing (and hoping!) that this might have fooled the Chase app into thinking that I'm not rooted.

After renaming, the TWRP recovery seems to use the "prwt" directory for backups. It somehow found it without my having to change anything in TWRP recovery.
[Magisk] Tirofog:
I've installed a few ROMs without this issue, so it's not TWRP.

This LOS has phh's Superuser which, when toggled on, should appear in the drawer, but it's not. Stock is a last resort, having just set the entire tablet up from scratch, leaving root last! Plus no google restore option.

Wiping/formatting data and erasing system? I don't get it :unsure:

Thinking about it, magisk wasn't installed on the PE I just came from. Could be the stub was there but went unnoticed as the ROM was short-lived. The last install was on the PE+ prior to that, when it was hidden.. hmm, I'm wondering if this would happen offline...

Thanks 👍
[Magisk] pndwal:
A few guesses here; quick check indicates device seems to be A only, ramdisk in boot, so seems issue is not Magisk in recovery partition.

From your description it seems Magisk is still installed / daemon still running which installs stub apk on boot when no app is detected.

Uninstall options (zip or uninstall in app) will not succeed when backup un-patched boot.img is not found in /data (magisk_backup_xxxx), so won't work after data format. You could manually flash un-patched boot.img if available to uninstall Magisk core on most devices, but on Samsung A9+ this will break boot as official Installation Instruction for Sammy devices on Android 9+ states:

Important Notes​

Never, ever try to restore either boot or recovery partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.

The only supported way to install Magisk on these devices is to flash the whole (patched) firmware file as AP, together with BL, CP, and CSC for full data wipe:

Installing Magisk for the first time REQUIRES a full data wipe (this is NOT counting the data wipe when unlocking bootloader). Backup your data before continue...

Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.

It follows that the safe (only?) method for fully uninstalling Magisk (restoring stock images) is: Flash the whole (original) firmware .tar file as AP, together with BL, CP, and CSC for full data wipe.

At the very least you'll need to flash the whole (original) firmware .tar file, together with BL, CP, and HOME_CSC. (I'm not a Sammy user, and have no idea if this opinion works without issues, ie whether full Magisk uninstall can be done safely without full data wipe.)

🤠 PW
[Magisk] pndwal:
Stub is installed at boot by Magisk daemon (see post above). Magisk has not been uninstalled (from boot image) for reasons I've noted. This is likely why phh Superuser isn't showing also.

You need a safe method for restoring un-patched boot image, and options are limited for newer Sammy devices... 😬 PW
[Magisk] Tirofog:
😭

I'm curious if this might have anything to do with the last install being hidden :unsure:

Appreciate @pndwal @J.Michael

Edit: back in business after flashing stock firmware, thanks again..
[Magisk] HippoMan:
I have been fervently and happily avoiding upgrading my reliably running-with-Magisk-23.0 and SafetyNet-passing OnePlus 7Pro (GM1917) device from A10 to A11, due to all of the headaches and complexity that I have witnessed here concerning the use Magisk for A11 and higher.

However, I have an older identical device with a broken screen and a badly hosed OS (EDL problems and a totally inaccessible /data partition) which was sitting in my junk drawer for the past year or so, and I recently decided to see if I could get it running to use as a test device for Magisk under A11 and above, because I need my other device to be reliably running and can't afford boot loops.

It took a lot of my not-very-ample spare time for me to un-hose the /data partition of that older device without the use of the EDL-requiring MsmDownloadTool, but I finally got that done via some of the partition tools offered by OrangeFox.

Then, after doing some investigation, I chose to try the A11 crDroid ROM. After installation, it came up fine with TWRP, Magisk 23.0, and LSPosed. This involved none of the painful headaches that I have witnessed here concerning other devices, OS's, and ROM's. I simply had to flash the OS, a proper version of TWRP, the recommended GAPPS, Magisk, and LSPosed. Everything is working fine, and the device passes SafetyNet.

In case anyone wants their A10 OnePlus 7Pro to have a mostly headache-free Magisk-enabled upgrade to A11 which passes SafetyNet -- and which also involves TWRP and LSPosed -- here is what I installed:

crDroidAndroid-11.0-20211217-guacamole-v7.13.zip

twrp-3.6.0_11-0-guacamole.img

FlameGApps-11.0-basic-arm64-20211218.zip

Magisk-v23.0.zip

Magisk install: Riru v26.1.4.r522.8b379cedb5

Magisk install: Riru - LSposed v1.6.5 (6272)

So far (after several hours of testing), this configuration is working fine.

Excelsior!
[Magisk] pndwal:
It's not; stub is installed whenever daemon can't find Magisk App installed on boot, whether hidden or not. This is different from app calling stub for hiding process. PW
[Magisk] J.Michael:
@HippoMan What do you do about the broken screen?
[Magisk] HippoMan:
Nothing. As I mentioned, I am only using this as a test device.
[Magisk] midgo12:
So I installed the latest Derp 12 and patched the boot image in magisk.

Before flashing the patched image I am not rooted and Magisk app shows Ramdisk Yes.

When Magisk creates the patched image it locates the Ramdisk and says it is being patched.

After flashing patched boot image I am rooted but Ramdisk shows no.

I have tried several versions of Magisk and it is the same.

I stay rooted until I reboot then root is lost.

Also I am using Magisk 23 and Magisk hide button does not stay on.

Can any one suggest a solution please...
[Magisk] zgfg:
You didn't say what is your device (that's important) but for some phones (Xiaomi, particularly), Magisk will always claim Ramdisk No although when patching, it will report that Ramdisk was found (just as you described)

However, depending on your phone (and what was its stock Android version?), you maybe have A/B SAR - you e.g. flashed the patched boot img to A, hence when it reboots to B you have no more Magisk

With root, from Terminal, execute:

getprop ro.build.ab_update

True will mean that your system is A/B
[Magisk] midgo12:
Phone is a Oneplus 7 pro...

Went from 11.0.3.1 to Derp 11 then to Derp 12...
[Magisk] zgfg:
I'm not a OnePlus user no familiar with its firmwre versions But gave you hint how to check is your device is A/B
[Magisk] pndwal:
You have this known issue:

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

It's already fixed by LoveSy in LSPosed test fork. Pull request here:

https://github.com/topjohnwu/Magisk/pull/5070

Fix has not yet been merged in Magisk master downstream, but working test build is in artifacts here:

https://github.com/topjohnwu/Magisk/actions/runs/1582452741

👀 PW
[Magisk] zgfg:
Btw, just tried the 'artefact'. You can open Configure DenyList when Enforce DenyList is disabled (it was an issue reported, because of Shamiko), but it opens empty DenyList.

Only when Enforce DenyList is is enabled, then Configure DenyList properly shows all apps confugured for DenyList

(Since I have Shamiko, my Enforce Denylist is disabled while Enforce DenyList was populated)
[Magisk] pndwal:
What did you try it on?

I haven't spotted that issue / fix; guess it's merged in Alpha only? .. But I'm on Alpha w/ Shamiko also... Is it in last canary also?

Nb. That test build for OnePlus / Android 12 is only one commit ahead of last canary; next canary will include 14+ merged commits, and hopefully this one... PW
[Magisk] zgfg:
On Alpha, when Enforce DL is disabled, Configure DL is greyed out (cannot be opened)

Don't know how it works on Canary

In that artefact build, Configure DL can be opened when Enforce DL is disbled, but DL list shows empty

Case: For Shamiko, Enforce DL must be enabled. But DL list must be configured. If you want to add an additional app to DL, you must temporarily enable Enforce DL, make change to Configure DL, then again disable DL (and reboot)

I don't know where did I see complaints about - to enable Configure DL while Enforce DL is disabled (mybe on TG channel - but since the ZH strict policy and pretty hostile atmosphere to all non-ZH participants I stopped reading TG Alpha channel because it is pointless to copy and translate 100+ posts where most of them contain no useful info)
[Magisk] ggkameleon:
Hi ! I have a mistake with my Pixel 4a 5g with the last Janv update.

I use magisk 23016 canary and before on Android 12 flash Vbmeta and disable verity & verification.

But with the last magisk update is until and update ota and flash boot img modified that work but when I restart my phone I loose the root ?
[Magisk] midgo12:
Yes device is A/B...

Thanks for the information so far.

I have solved this by the following method which may or may not be "the way" to do it but it worked for me.

I used Magisk v45ccfafd apk and installed it and used it to create a patched boot.img and flashed it.

I was then rooted with ramdisk yes.

I then flashed the maragisk ramdisk yes zip through modules in magisk.

I also flashed Universal safety net fix v 2.2.1 through modules in magisk.

After reboot I had zygisk yes ramdisk yes all superuser apps working and safetynet working.

These remained in place after several reboots so I'm calling that a win...
[Magisk] pndwal:
Sounds like a win. 🙂 ... What is v45ccfafd apk? Link? ... Guess you didn't try the fix for OnePlus / Android 12 from LoveSy... PW
[Magisk] pndwal:
Nb. Alpha zh only restriction is gone again. 🤪... I'm using Plus Messenger w/ translate for TG now. PW
[Magisk] midgo12:
Magisk v45ccfasfd is an alpha apk and the maragisk ramdisk yes zip were suggested on the Derpfest OnePlus 7 Telegram site as possible things to try. In this case they worked for me. They are both available as downloads on that Telegram page...
[Magisk] zgfg:
With Plus Messenger, Plus settings Translation, do I still have to tap a post by post to translate each of them?

So far I don't see how to set that all posts in the channel would be automatically translated - or am I missing something?

In that case it's not much better than the Translation option in Telegram itself (only that in Telegram, translation for a post closes when you move to another post, in Messenger translated posts stay translated but you still must translate one by one)
[Magisk] Lord Sithek:
Yea, what a pain is this, I also look for a way to automatic translation, this used to work in the past with AllTrans Xposed module, but the dev confirmed its broken now (maybe will be fixed in the future). If anybody knows other solution, I'm really curious 😁

PS. Sorry off-topic
[Magisk] pndwal:
Latest vvb2060 Alpha Magisk (Unofficial Build - for mavericks only!) Translated:​

alpha changelog​

Magisk (558710bb-alpha)​

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[App] Use local version when unable to download stub

[App] Modern time API using Java 8

[General] No longer automatically unlock device blocks

[General] Use MagiskHide to hide when Zygisk is closed

[App] Remove markdown rendering

[General] Do not execute scripts that ignore loaded modules

[App] Fix the second click of hide app button may be unresponsive

[App] Enhance the function of repairing environment

[App] Support setting PATCHVBMETAFLAG flag to handle vbmeta in boot image

[App] Adapt to Android 12L

[MagiskInit] Refactor the processing method of two-step startup

[General] Skip mirror overlayfs partition

[MagiskInit] Support handling force_debuggable flag

[App] Fix SnackBar popup position

[App] Experimental support for Pixel device OTA

how to install?​

Install and uninstall Magisk through the Magisk application. Generally, it should be done directly in the application. In special circumstances such as the first installation, the image should be patched and then flashed in with the fastboot/odin tool. Customizing Recovery is not a supported way.

Complete changelist incl. Upstream update log here:

https://github.com/vvb2060/Magisk/b...79818bd8198/app/src/main/res/raw/changelog.md

👀 PW
[Magisk] pndwal:
Good find. As I mentioned also, proper fix for OnePlus 7 (incl. Pro) / Android 12 (test build) has been available for a couple of weeks now and should be merged in Magisk master soon... PW
[Magisk] pndwal:
Yup, one by one... Does save copy / pasting... Can set Google translate or Yandex - Google translate is better; I imagine only Yandex is available in China... PW
[Magisk] Johnson_Ran:
only build on Linux · JohnsonRan/Magisk@c1c535b

A Magic Mask to Alter Android System Systemless-ly - only build on Linux · JohnsonRan/Magisk@c1c535b

github.com

try this,based on latest Magisk Alpha,i fixed ramdisk according main repo pr

steps:

flash stock boot>install app then patch boot>flash it
[Magisk] Johnson_Ran:
if u open magiskhide,then configure denylist is configure magiskhide
[Magisk] Johnson_Ran:
like i said , if u open magiskhide,then configure denylist button below is for magiskhide...do i need explain how magiskhide working?
[Magisk] Johnson_Ran:
magiskhide on Magisk Alpha is working exactly same as v23.0
[Magisk] pndwal:
If you have issues with his build on Sammy (I doubt there's issues however), try official Alpha (non-official) Magisk (that's confusing huh?) from here:

https://t.me/magiskalpha/400?single

or here:

https://github.com/vvb2060/magisk_files/tree/4144bd802ef2554f597c62eb97efae6faf113a86

🤠 PW
[Magisk] traversone:
hi,

has Zygisk ability to manage isolated process?

In my experience (Samsung S8, Hades ROM A10), although Zygisk/Shamiko is properly working, 1 APP detects root. With MagiskHide ON + Unshare module all is perfectly OK
[Magisk] pndwal:
Seems mileage varies per device; apparently Shamiko does hide (some) process leaks, however some users get entirely 'Happy Momo' on Realme for example, but MIUI users cannot hide some traces... And these seem to differ between Android 10 & 11 on MIUI also...

Some others report happy Momo on custom ROMs such as Dr. Ketans (heads-up for your Sammy 😉 ) PW
[Magisk] pndwal:
Now seems Canyie put ZH (Chinese) Only for Alpha group, but vvb2060 reverted it:

https://t.me/c/1414270883/33714 PW
[Magisk] lolvatveo:
i have a samsung j5 how to make it run with magisk, when i patch boot or flash magisk.zip after done i check magisk shows installed N/A. i can only root using supersu, supersu can take root via boot.img but it can't hide root
[Magisk] chrisc93:
Works great on my Nexus 5X running PureNexus. Awesome job!
[Magisk] aNYthing24:
Got it to work following your steps (besides #1), thanks a lot!
[Magisk] justmiike:
Did you get Xposed working?
[Magisk] zjbbhsso:
Sorry, there no need to sideload in #1, I've edited that.

In #5, that's my comment about custom_ramdisk_patch.sh.

Because if you want to do it again from #1, you have to overwrite it again.

Although they have the same file name, the content inside are different.
[Magisk] jcrompton:
This may be the dumbest question but why are you mixing the SuperSu with Magisk and all ...... Was it just an accidental way of getting things working or was it by design??
[Magisk] :
Only modules i have through magisk is phh superuser and viper4android. Took a break from messing with my phone for the weekend so i could pogo with the wife. I'm using adfree for my blocking needs. I will likely be trying more things this week. Lol especially Wednesday right..

But I'll give the emojis module a run now and report back

Edit: I installed emoji one and seems ok. Didn't affect safetynet.

I also didn't install busybox and just rely on magisk(built in). No issues yet.
[Magisk] zapahacks:
Thanks, so I will just do the first 2 adb commands.

So, the correct one that should make it work is the the "custom_ramdisk_patch.sh" in the patch zip, right?