yashsingh1/xdaforums huggingface dataset:
[Magisk] TheEpicFlame:
I've never rooted before so I used the newest version of Magisk as it seemed the safest, but I'm not happy with it and want to use an older version. Installing the APKs is simple and works fine, but for some reason I can't uninstall Magisk without flashing stock boot, and when I do, the only boot .img of Magisk I can get to work is 24.1.
[Magisk] pndwal:
So Magisk to install is predicated by App installed... If you're downgrading to public 24.1, can I assume you now have Canary 24102 etc?

Have you downloaded earlier app from 'releases', uninstalled Canary version then installed 24.1? Next, just selecting Magisk, Install will offer patching images w/ 24.1 mask/core... PW
[Magisk] TheEpicFlame:
I installed the official 24.1 update, used it for a bit realised I'd rather have an older version, and tried to install 22.1, that didn't work and neither did 23. I haven't used Canary at all.
[Magisk] pndwal:
Sorry I'm confused... Though you said above you have latest (24102) and wanted to downgrade to public 24.1 as that works... Seems now you're trying to upgrade, but same principles apply.

If you've had issues, I'd be trying latest Canary anyway; it has a number of recent fixes for Samsung, old armeabi-v7a devices etc. Nb. there are still some serious issues outstanding (Samsung issues etc), but rapid progress is being made!... PW
[Magisk] Cyndaquissshhh:
Maybe this problem occurs on most (if not all) Samsung phones? If that's the case it's better if Samsung users stay on v23 for now.
[Magisk] lcsboy:
When Magisk 23.0, some bank apps can NOT work, but game is no issue.

After I upgrade Magisk 24.1 zygisk + shamiko + usnf + LSPosed, all bank apps are no issue.

But the game of "WOTV FFBE" always can NOT login and shows the error message that it can NOT connect to the server.

I reinstall/install this game again, but it still doesn't work.

If add the game in Denylist and HideMyAppList (LSPosed module), it still doesn't work.

My cell phone is ASUS ZenFone 6, Android 9
[Magisk] ahpekriderzbmx:
U Use HMA Right?
[Magisk] TheEpicFlame:
How am I trying to upgrade? I want to go from Magisk 24.1 to 22.1.
[Magisk] supermaus100:
Hello, is it possible to get root for the SM-N986B with the new firmware Android 12? Unfortunately Magisk doesn't work anymore.
[Magisk] pndwal:
Misread.

Try canary as suggested, or

Downgrade issue may be recent fixes needed, but if this is Redmi Note 9 I think older is ok...

Nb. For Xiaomi, if you see Recovery Mode selected, un-select it regardless of Ramdisk result shown.

Uninstall App and install chosen version from Magisk main GitHub page, releases, or enter URL for Custom Channel from here:

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

(select Custom in Update Channel) and downgrade App, then Magisk from current App. Nb. Latter method will fix 'Hide the Magisk app' issues. PW
[Magisk] pndwal:
Latest 0.4.3-100

# Shamiko

こっっ…　これで勝ったと思うなよ―――!!​

### Introduction

Shamiko is a Zygisk module to hide Magisk root, Zygisk itself and Zygisk modules like riru hide.

Shamiko read the denylist from Magisk for simplicity but it requires denylist enforcement to be disabled first.

_Currently, system apps (with uid%100000=1000) cannot be hidden even it's in the denylist. This issue comes from Magisk._

### Usage

1. Install Shamiko and enable Zygisk and reboot

1. Configure denylist to add processes for hiding

1. *DO NOT* turn on denylist enforcement

#### Whitelist

- You can create an empty file `/data/adb/shamiko/whitelist` to turn on whitelist mode and it can be triggered without reboot

- Whitelist has significant performance and memory consumption issue, please use it only for testing

- Only apps that was previously granted root from Magisk can access root

- If you need to grant a new app root access, disable whitelist first

### Changelog

#### 0.2.0

1. Support font modules since Android S

1. Fix module's description

#### 0.3.0

1. Support whitelist (enable by creating an empty file `/data/adb/shamiko/whitelist`)

1. Always unshare (useful for old platforms and isolated processes in new platforms)

1. Request Magisk 23017+, which allows us to strip Java daemon and change denylist regardless of enforcement status

1. Temporarily disable showing status in module description (need to find a new way for it)

1. Support module update since Magisk 23017

#### 0.4.0

1. Add module files checksum

1. Bring status show back

1. Add running status file at `/data/adb/shamiko/.tmp/status`

### 0.4.1

1. Add more hide mechanisms

### 0.4.2

1. Fix app zygote crash on Android 10-

### 0.4.3

1. Fix tmp mount being detected

https://github.com/LSPosed/LSPosed.github.io/releases

👍 PW
[Magisk] eXtremeDevil:
Sorry if this has been answered before, but what is the meaning of "Restriction on non-SDK interfaces is not working" and "permission system is abnormal" in Momo app? I've tried the in thread search but it is not working for me.
[Magisk] dohanin:
There is actually one more change for 0.4.3 in the webpage (although missing in README.md):

2. Hide modified traces of init.rc

I checked the code (service.sh) which is almost identical to InitRcHider (which in turn is from riru-momohider). So I guess from this version onwards we don't need InitRcHider anymore.
[Magisk] TheEpicFlame:
I don't quite understand, could you explain more clearly? How do I upgrade to Canary or donwgrade as you suggested?
[Magisk] Spartacus500:
0.4.3

Fix tmp mount being detected - Perfect work

Hide modified traces of init.rc - not working
[Magisk] rodken:
1. Wipe everything through TWRP

2. Reboot to recovery

3. Reflash ROM

4. Format data partition (format, no wipe, if mke2fs doesn't work, try with rm-f)

5. Reboot system.

NB: Usually it takes two attempts to hit paydirt.
[Magisk] kaneda656:
Hello, i just updated my app to 24.1, and i noticed that the "hide magisk" option doesn't appear anymore, Can you tell me how to find it again? I need it for bank apps, Netflix, and ID app
[Magisk] Lord Sithek:
https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/
[Magisk] szazs89:
I think it was my mistake. OEM unlock MUST NOT be disabled once enabled and custom boot, etc. binary images flashed. Otherwise you have to re-flash the stock binaries via ODIN.
[Magisk] kaneda656:
Thanks, now i see.

it's a little less convenient than before, but it Works !
[Magisk] Lord Sithek:
to know more about the reasons for those changes, look here: https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458
[Magisk] c3k:
Do you know what "Workaround Samsung's early zygote" is? Can't find how to reach canary commits...
[Magisk] pndwal:
Yup, fixes Zygisk not functioning for Samsung devices:

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

Co-authored-by: LoveSy <shana@zju.edu.cn>

canyie and yujincheng08 committed 4 days ago

Canary commits are in Magisk master branch... 👀 PW
[Magisk] PaY87:
Is it possible for Shamiko to hide the Magisk app like its frozen? I have an bank app which does not work when Magisk is installed (even when you hide it with different name) as soon as I freeze Magisk in TitaniumBackup the banking app works fine... Would be a great feature!
[Magisk] Lord Sithek:
Try with LSPosed and Hide My Applist module. Mentioned many times here in the thread
[Magisk] zgfg:
Shamiko does not hide applications

Please scroll through the posts older posts (it was a lot just a day or two ago) and find/read about HMA=Hide My Apps
[Magisk] zulu88:
Check out these topics:

https://xdaforums.com/t/guide-how-to-root-n20-ultra-n986b-n9860.4147023/

https://xdaforums.com/t/07-02-22-n986b-i-n985f-ds-i-dr-ketan-rom-i-oneui-4-0-i-oneui-3-1.4154487/
[Magisk] TheEpicFlame:
When flashing patched boot.img 22.1 or 23 it shows root status as n/a. Only working root is 24.1 but I want 22.1. I don't have TWRP as I can't install it.
[Magisk] pndwal:
Are you talking to me? (If you don't ping members they won't know. 😜)

I described downgrade to you:

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

and bit more here:

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

Canary use starts by clicking GitHub Magisk main page, Downloads, Magisk Canary button... PW
[Magisk] lcsboy:
Yes.

But no matter HMA, the game of WOTV always show the error message that it can NOT connect to the server.

Some bank apps if can NOT login, HMA let this kind of bank apps login successfully.

I have no idea what setting/app/module cause this game can not login (If I reinstall/install, the game can download DLC from the server)
[Magisk] m0han:
removed init.rc module. shamiko latest through in-app update.

things look good. tried payment thro' gpay once; worked for me.
[Magisk] TheEpicFlame:
I meant to reply to your message.

As I said, I didn't understand you're instructions for the downgrade.

I also can not figure out how to get an older version of Canary. Is it only possible to get the newest?
[Magisk] pndwal:
That's why I pointed to another post w/ more details...

There are 2 archived sets of old canary on John's GitHub... Not hard to find

Please say what you want w/ old canary builds when you have Stable builds listed? -Do you understand the advantages of using Canary? PW
[Magisk] c3k:
Has been reported from users with Android 10 only and on my device (S21, android 11, 12 soon) "getprop persist.sys.zygote.early" gives null result. I think I'll try with 24.1 stable and then switch to canary in case. Thank you.
[Magisk] TheEpicFlame:
I dont but I heard that it was an alternative and sometimes works when Stable doesnt.

You say not hard to find but I cant find johns github.

I also dont see how the post w/ more details could help me.
[Magisk] J.Michael:
At a given moment, the latest canary includes patches not yet incorporated into the stable. It is available to see if these patches fix more than they break. It is un-stable -- it could blow up in your face. But it also has more debug output to help identify problems.

I think it is unlikely that an old canary will be of any use to you. If a developer were to ask you to use an old canary to gather information, that would be the time to use one. Otherwise, stick to the stable releases. Or the latest canary, to test and maybe report problems.
[Magisk] TheEpicFlame:
Thanks for the advice!

So am I out of options since I can't install via fastboot and can't install a custom recovery?
[Magisk] J.Michael:
What options are you out of?

Earlier, you reported installing a version of Magisk. Whatever procedure you used will probably work with any version.

What problem are you trying to solve?
[Magisk] ahpekriderzbmx:
How To Settle This? What Other Apps Should I Hide?
[Magisk] TheEpicFlame:
I installed root for the first time recently. I installed Magisk 24.1 and it rooted and worked fine. I didn't like the removal of online module downloads and it also just doesn't work with some root apps and modules, so I tried to install 22.1, same procedure as the first time, except now, the root shows up as n/a. This happened to version 23 as well. The only version that works is 24.1 and it even shows as working in the older apks.

I haven't been able to install TWRP and it looks like I'm at a dead end.
[Magisk] zgfg:
Do you have XLua installed, use HMA to hide.

If not, go to XLua Git page and find the info about the folder it installs to (Readme), and delete that folder by root explorer like MiXPlorer

Anyway, the same was asked and answered (in some more details) two days ago, so it's worth to go through the older posts
[Magisk] ahpekriderzbmx:
Already Hide It.. Nothing Change.. Huhu
[Magisk] Sid220:
Hi everyone, that's my situation: i own a Lenovo Tablet Tab2-X30L that i want to install Magisk on it.

Unfortunately TWRP install does not work (only old TWRPs are available and flashing it ends with errors).

I'd like to install it patching boot.img but i can only find official firmwares (with boot.img) of old Android 5 version, but now it has Android 6 on board.

What can i do? Is it safe to patch "old" boot.img then flash it? It could brick it?

Or i can patch old recovery.img?

Any help appreciated
[Magisk] pndwal:
Does TWRP work enough to use backup (NANDroid) function?

Little trick to get unpatched (stock) boot.img:

- Take backup of boot partition

- Find boot.emmc.win in backup folder and rename it to boot.img.

(Magisk may even recognize .win file)

Tip: Many Lenovo device resources / firmware links can be found on XDA. More are to be found on Russian 4PDA; Russian Devs do much ground-breaking custom development for Lenovo.

👍 PW
[Magisk] zgfg:
No need to rename, Magisk app will recognize boot.emmc.win backup as the boot img

Btw, with root, you can disk-dump boot.img to Internal memory:

adb wait-for-device devices
adb shell
su
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img

You can similarly do from Terminal emulator (use the last two commands)
[Magisk] pndwal:
Canary is basically where new commits are tested before public release. Latest Canary may well benefit you as it builds latest fixes; eg. currently many Samsung devices only have proper working debug Canary Magisk, several fixes being downstream from last public Stable/Beta build.

So Stable releases are less frequent and more fully tested. Debug Canary builds prior to last public build will necessarily have less fixes and will often be less stable.

The Canary build following any public release is synced, ie. it is essentially the same build, the difference being the addition of verbose logging. The extra debug logging is the reason John stipulates Canary use or issue (bug) reports. He also wants only the latest so issues are never reported that have already fixed.

So while latest Canary (always available from Magisk main page) may well be better for users, older Canary will generally have no value other than bug regression testing etc.

If your device doesn't behave properly w/ latest builds, using stable builds is advisable (eg some Samsung users needed / were doing this from last April till just a week ago!). Thats why these are listed in 'releases' page. Old canary is only really for Devs, reverse engineers and mavericks. 😜

In your Magisk app, just click GitHub 'OctoCat' symbol at the bottom!...

Sigh... Then please say what details you need or need clarifying... I'm no mind-reader. 🙄

PW
[Magisk] nasch007:
So in Magisk I made a bonehead move and now my phone is stuck at the Lineage loading screen. Asking for help... please. I know what I did wrong just not sure how to fix it.

Running a Google Pixel 3 unlocked bootloader on Lineage 18.1-20210518-NIGHTLY-blueline. Have Magisk v23 and MagiskHide installed (so certain apps like Chase work correctly-- is there a better way to do this?). Everything has been working perfectly for months up until tonight...

Tonight I installed the wrong module in Magisk and now I am stuck with the Lineage logo loading screen. It won't go past it. I was trying to install a module for MiraCast since my TV supports that and I wanted to play around with it... it wasn't until after I clicked install I realized it said for Android Q (Android 10) and obviously I'm on Android 11.

So now when I boot up the phone it gets to the Lineage logo and just keeps playing the logo. I'm not sure what to do. I have images and audio that I cannot lose. Most images should be backed up to the cloud, but there is one audio piece very important to my work that I need.

I can access the Lineage Recovery, and adb. I was able to pull a test file off using adb pull (recovery.log, not sure how old it is) but I don't know how I would do this to save my images/audio or if that's even feasible.

Is there a way to see what I did by installing that MiraCast module? Some way I can undo the changes?

If not, what should I do? How to remove changes made by Magisk when I can't boot to the OS? Will a reinstall of Lineage fix it? Is there a way to install a newer build of Lineage over the current setup, and keep Magisk and everything as it was before, without losing all my apps, data, and settings?

Any help would be appreciated!
[Magisk] szazs89:
How did you install Magisk v24 for the first time to get rooted?

Doesn't the apk show uninstall option (with red)?
[Magisk] Sid220:
@pndwal that recovery barely works for flashing SuperSU. I tried to nandroid backup boot partition, it says success but no file on internal storage.

I've searched FWs for the tablet in russian forums and there are new recoveries (TWRP version 3) but most links are dead

@zgfg i've read it but my doubt is: if i have root it means that boot.img is patched by SuperSU. If i dump it then i patch it with Magisk will it work?
[Magisk] zgfg:
It will dump your current Boot.

The same like TWRP - it will backup the current Boot.

One can compare the checksums and they must be the same

It's useful if e.g. you updated Magisk by Direct method, but you then still want to save your new, working patched-boot.img.

And by disk-dumping, it can be done even on the phones without TWRP
[Magisk] Sid220:
@zgfg up to now the tablet has no root. Luckily i've found a TWRP version 3 recovery.img. I'll try flashing it and check if i can flash Magisk zip or do a Nandroid backup to dump boot.img
[Magisk] TheEpicFlame:
I flashed the patched boot image from fastboot.

And yes it does.
[Magisk] szazs89:
So, I would

* Patch a boot.img with pre 24 zip(?)

* uninstall Magisk from the app,

* flash the patched boot.img

* reboot without Internet connection

* finalize the install of the apk

* pin the custom update channel URL to the same version (see earlier posts about it)

Uninstalling Magisk and flash a new boot.img can be tricky (if the stock boot.img doesn't like custom binaries). Maybe the uninstallation isn't really necessary, just reboot into ADB load to flash the patched boot.img. And have a copy of the current boot.img if the new one would not wanna boot.
[Magisk] Sid220:
@pndwal @zgfg thanks for help, i've flashed TWRP 3.0 on my tablet and managed to flash Magisk 24.1 zip

But now i face this problem: when i try to hide Magisk app, i get "error parsing package" so the app could not be hidden, how can i solve it?
[Magisk] ahpekriderzbmx:
How To Hide Xprivacy?
[Magisk] szazs89:
Shamiko or LSPosed? (see post #9 or this)
[Magisk] TheEpicFlame:
I've done all of these already. The whole point of my post is it doesnt work.
[Magisk] TheEpicFlame:
You may not be able to mind read but you seem perfectly capable of reading normally. I need a way to downgrade magisk that actually works, I would know it but I'm no omnipotent being.🙄
[Magisk] J.Michael:
How do you plan to recover from a disastrous mis-flash if you do not have a flashable copy of the "original" firmware?
[Magisk] szazs89:
Some more info is needed about how it doesn't work.. :)

Have you got an original boot.img patched with v22.1 zip?

Have you removed / uninstalled apk v24.1?

Have you flashed the patched boot.img via fastboot?

After booting what Magisk apk do you see (version)?

(Do not finalize the setup with internet connection!)

sz@zs
[Magisk] pndwal:
So 1) -

Nb. For Xiaomi, if you see Recovery Mode selected, un-select it regardless of Ramdisk result shown.

Uninstall App and install chosen version from Magisk main GitHub page, releases, or enter URL for Custom Channel from here:

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

(select Custom in Update Channel) and downgrade App, then Magisk from current App. Nb. Latter method will fix 'Hide the Magisk app' issues. PW

So 2) - If you really want to downgrade, you can simply use the app if you wish. Follow instructions for Custom Channel here:

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

- Ensure app is restored (not hidden).

- Take Install App (Latest should now show 23.0) first. Downgrades will likely fail, but you will find apk in Download folder set in Magisk app. Just uninstall current app then install APK manually.

- Take Install Magisk. You will have Patch file option, and Direct install if you have existing root available.

Putting proper JSON URL in Custom Channel allows 'Hide the Magisk app' to work as it calls compatible (matched) older stub file instead of latest version. 🤠 PW

That's what I gave you. Twice. Method actually works whether you follow 1) or 2) above. 😁 ...

🤔 I read, I obliged, I already gave "a way to downgrade magisk that actually works" x2...

You said "I didn't understand you're [your] instructions for the downgrade" and "I also dont see how the post w/ more details could help me"...

I asked politely "please say what details you need or need clarifying... I'm no mind-reader".

You replied ”I need a way to downgrade magisk that actually works"

Huh? I know this!! - what didn't I read?! Where did you say what details you need / need clarifying / don't understand?... Are you asking me to cover everything again? A third time? 😳 ... Sorry, won't.

I think I'm being reasonable... I'm very happy to help / clarify aspects of method if you'll just answer my question and say which aspect... I quite understand you're "no omnipotent being", but none of us are. PW
[Magisk] pndwal:
Check Update Channel is set to Stable and have network connection.

Try with no network connection (forces 'Use local stub').

Ensure you don't have any old hidden Magisk App / Manager installed (named "Settings" or custom choice).

Check tips here:

https://www.didgeridoohan.com/magisk/Magisk#hn_Problem_parsing_the_package PW
[Magisk] pndwal:
Please note I said earlier

It seems very likely you need the myriad recent fixes in 24.1 (more in Canary 24102) if 23.0 failed for you.

I think you will find my 'way' actually does works fine, for you at least with 24.x +, but that device / ROM (Android version etc) incompatibility with older Magisk are the real reason "it doesnt work".

In short, you may not be able to downgrade Magisk to pre-Zygisk era builds with your device and current ROM (OS).

🤠 PW
[Magisk] pndwal:
Latest unofficial vvb2060 Alpha Magisk:

# alpha changelog

## Magisk (12093a3d-alpha)

- [App] Support SharedUserId

- [App] Delete backup file after restoring boot image

- [App] Built-in current version update log

- [General] no longer automatically unlock device blocks

- [App] Compatible with Android 12L

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

- [App] Added crash statistics

- [Script] Support init_boot partition

- [App] Root request popup always uses independent task stack

- [App] Show notification instead of automatically reopening when app update is complete

### how to install?

Install and uninstall Magisk through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, you should use the fastboot/odin tool to flash it after patching the image.

By customizing Recovery is not a supported way.

# Upstream changelog

## Magisk (1a1b346c) (24102)

## Diffs to v24.1

- [MagiskSU] Fix buffer overflow

- [MagiskSU] Fix owner managed multiuser superuser settings

- [DenyList] Allow targeting processes running as system UID

- [Zygisk] Workaround Samsung's "early zygote"

- [Zygisk] Improved Zygisk loading mechanism

- [App] Fix BusyBox execution test

- [App] Improve stub loading mechanism

- [App] Improve stub upgrade flow

👍 PW