yashsingh1/xdaforums huggingface dataset:
[Magisk] contwerper:
Alright I got it to work in the end just by re-doing the whole thing step-by-step. Fastboot into recovery, flash stock ROM, format and wipe, reboot into recovery and ADB sideload Lineage OS + Magisk (with renaming apk to zip - although I have no idea why this has to be done instead of the developer just making it a .zip in the first place. But whatever haha, if it works it works.)

I have a new problem... that i kind of created for myself. I installed Lineage with microg, since my intention was to "de-google", but I realized that a number of apps that I wanted to use are paid ones and I couldn't download them or buy them directly from Aurora Store.

So now I'm trying to figure out how to remove microg and re-install the real Google Services Framework and Google Play Store, without having to re-do and clean flash everything again. When I download the raw apk file for GSF and Playstore, I just get the "incompatible" error message. No doubt caused by microG. I tried deleting microG itself although I don't really know how to.... Anyone got any ideas? I know there are workarounds like buying it on another device or PC, then downloading it via Aurora by logging into my Google account. But that's troublesome...
[Magisk] zgfg:
Officially recommend method (by 'developer' himself, on his official Github page in his official documentation) to install Magisk is to install Magisk apk, then patch and flash the img.

Therefore, for that method, 'developer' provides apk (not zip)

However, his Installation guide also describes that (for those who still want and can on their phones) to flash Magisk through TWRP, users should just rename apk to zip and flash

Even more, for TWRP 3.6 you don't need to rename apk to zip but flash directly as apk file (TWRP would recognize that file can be 'interpreted' as the zip file for TWRP)

Also, if you rename that Magisk apk to uninstall.zip, then the same file will serve for uninstalling Magisk through TWRP

All together there is no need for 'developer' to build as zip (officially recommended method requires apk, and it would be stupid to put the same file with three names: apk, zip and uninstall.zip)

Instead, users should read and be up-to-date with the official Magisk Installation instructions, where all the details are described
[Magisk] nostupidthing:
los 18.1... last time there was no direct install option but it's there now,

last time after i updated los, there is no such option, i had to unpack the boot.img and flash manually.

i was using lineage recovery btw, does that make a difference with twrp?
[Magisk] zgfg:
As the name says, LOS Recovery is not TWRP

I never use LOS ROM, I once tried LOS recovery but didn't like it (new device, there is no TWRP yet and I was so despeate that I even tried LOS recovery😁 but fortunately I found then better recovery, SHRP working for that device) - hence I really don't know, cannot help about

---

Btw, and independently of LOS or any Recovery:

In Magisk app, on the nain screen, top, there is Install.ootion

Upon ckicking to Install, you can choose between the methods:

- Patch the img

or

- Direct update

However, Direct install IS NOT available if the phone is not already rooted by Magisk

In some cases (most often: uers did not unhide their old Magisk app/mngr before updating to the new Magisk app):

- then, the phone is usually already rooted by previous version of Magisk

- but becsuse of that old, still hidden Magisk app/mngr, the new Magisk app does not see Magisk, hence it 'thinks' that Magisk is not installed and therefore Direct update option is (obviously) not available

But that's not related to this or that custom recovery
[Magisk] pndwal:
Magisk supports a number of scripts incl. addon.d ver. 2, a 'Magisk Survival Script for ROMs with addon.d support # by @topjohnwu and @osm0sis'.

https://github.com/topjohnwu/Magisk/blob/master/scripts/addon.d.sh

Only custom ROMs are supported; addon.d was a LineageOS innovation originally.

I believe this only worked w/ Magisk flashed as zip installer, but it may also work w/ fastboot flashed Magisk now... I don't know.

I believe later TWRP builds also implement addon.d survival for supported-ROM updates.

I put some notes here:

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

Re. your comment, Direct Install in Magisk is simply root dependant, meaning that initial manual patch file / flash is needed whenever root is lost. So seems addon.d script was originally preserving Magisk root through custom ROM updates for you...

So what's changed? - I'm not 100% sure... Since it's actually an LOS innovation I'm guessing it would be supported by LOS Recovery as it was in TWRP, but maybe it's not... Perhaps it's broken in LOS 18 / Android 11?... Perhaps you no longer use install from zip-installer in custom recovery; might want to try that again...

@osm0sis may kindly clarify this further... 🤠 PW
[Magisk] maniacbb:
Does anyone know how to restore screenshot 3 finger swipe? Any magisk mode?

I have POCO F3 with Lineageos 18.1. Thanks
[Magisk] osm0sis:
TWRP addon.d-v2 is mine, and may be found in my Odds thread.

I noticed Magisk addon.d and Magisk zip install failed on my flox the other day, but haven't had any time to look into it (since I've got a 3 week old daughter now! 🤯). So if someone wants to debug that using recovery.log and TWRP adb shell and submit a patch to Magisk's GitHub that would be great. 😘
[Magisk] pndwal:
Because you're too modest:

https://xdaforums.com/t/tools-zips-...tiple-devices-platforms.2239421/post-40409361

Congrats! 👏🎉🥳🍼😴

Thanks for heads up. PW
[Magisk] Lughnasadh:
Congrats on the birth of your daughter! 🙌👏
[Magisk] Einsteindks:
Aw super-crud. My Droid Turbo is now without root. An update to magisk is causing me, somehow, to not be able to successfully flash magisk in twrp. Changing the apk to zip will flash successfully, but upon reboot, looking in the app, it just isn't there, but the app is fine. Running LineageOS 18.1 ROM.
[Magisk] J.Michael:
Any chance you have a renamed Magisk app in addition to the newly installed Magisk app?
[Magisk] Einsteindks:
Nope. Even started from no Magisk installed for no conflict with flashing zip in TWRP.
[Magisk] pndwal:
This?:

... Could be Magisk addon.d related:

😬 PW
[Magisk] pndwal:
... Could also still be this... Uninstalling Magisk will often not uninstall a hidden app... If you actually started from clean ROM install (didn't restore /data), a hidden app will have been removed however...

Hidden app ('settings', other name) may only be found after searching in device settings, apps... PW
[Magisk] NeoNecOP6:
I was lazy with my phone Oneplus 6.

I have magisk 20.1 installed and since 2-3 week magisk dont Start, but works. It give me a crash message.

My question is, how install magisk 20.3?

Via recovery or can I install like every other app?
[Magisk] guhvanoh:
Best to ask in your fone's Q&A forum.
[Magisk] NeoNecOP6:
Why? My question is the right way to install magisk, because I cant start it, but it works.

Via Android or recovery?

Because magisk install the update in Android, if it works.
[Magisk] martyfender:
https://topjohnwu.github.io/Magisk/install.html

https://www.didgeridoohan.com/magisk/HomePage
[Magisk] pndwal:
Why don't you want late or latest? ... Any particular need for 26 Month old Magisk? PW
[Magisk] NeoNecOP6:
Because I didnt check the newest version number, only remember the .3 😅
[Magisk] pndwal:
🤔... Well, the most recent xx.3 version other than 20.3 is 19.3... even older!? 🤪😂

How about selecting your horse from here:

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

... Wouldn't want you to keep flogging a dead one...

You're not hoping for 24.3 are you?...

😜 PW
[Magisk] NeoNecOP6:
Because I didnt check the newest version number, only remember the .3 😅

True, I thought there is a mini Update to 24.3

I installed the app now directly in android and now I can start it, but cant install the update
[Magisk] zgfg:
You have Magisk app 24200, but your latest shows 24100 - seems you are running Magisk Beta (24200) but your Update channel is set to Stable (24100) - better adjust the Update channel to be Beta or Canary (to be the same as your installed Magisk app)

[

Also, seems that the img file you tried to patch is not a proper one (it wasn't recognized).

I'm not familiar with your device and how you extracted the boot (?) img - double-check are you using the proper img file.

Eg, if you have TWRP, backup the Boot and try patching boot.emmc.win (it should work)

] - actually see my later PS below

Btw, you are already rooted by Magisk v23 - why don't you go with Direct install (instead of Select and patch).

But also adjust the Update channel first

PS: Now I intentionally tried to patch a wrong img file - but observe that my screenshot looks very different.

Magisk displays the target version to be installed, it copies img file to cache and unpacks the img, and then it "does not recognize the img format" (screenshot)

In your case all that is missing and it "does not detect target img" immediately - I don't know is that error due to the missmatch in Update channel (adjust and try again) or something else (like a problem with file explorer you are navigting to the img file you want to patch - I still think it would print different in that case)
[Magisk] Cman1468:
Hi everyone,

I'm trying to figure out how to disable force encrypt on a Pixel 3 XL running LineageOS 18. I've tried everything that I could find at this point. Disable forceencrypt (https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt) bootloops my phone, and adding .magisk with KEEPFORCEENCRYPT=false to /system, /data, or /data/cache has done nothing when reflashing magisk before or after formatting data (reflashing before format logs say "Encrypted data, keep forceencrypt", reflashing after format logs say nothing about forceencrypt).

I need encryption disabled because I'm trying to get nethunter to work, and as it says on the nethunter site:

As I've said before, "Universal DM-Verity, ForceEncrypt Disabler" bootloops my phone no matter which way I flash it, its also been deprecated since 2020. Also, I've tried running nethunter on an encrypted system and I got the “Required key not available” error. Is disabling forceencrypt something that is even possible on Android 11? If so, how can I disable it? Or does someone know a workaround for running nethunter on an encrypted system?

EDIT: I never figured out how to disable encryption, but I did get nethunter working on an encrypted system. Edit these files:

/etc/pam.d/su-l

/etc/pam.d/login

/etc/pam.d/runuser-l

/etc/pam.d/ssh

and comment out

# session optional pam_keyinit.so force revoke
[Magisk] regularmen:
I cannot hide my magisk manager. there's no toast or anything as documented in troubleshoot page, after a few moments it closes the manager to launcher and stops here not doing anything instead of restarting to the new manager. there i found two installed manager which when I open it, it doesn't response at all. I'm running AOSP Pie in Nokia 5 with Magisk 23, it was Magisk 24 last week but I deemed it wasn't feasible in my device so I downgraded it.
[Magisk] zgfg:
It's a known problem and discussed here. Unfortunately, it won't be fixed, Magisk dev(s) said they don't support the v23 and older

Actually, when hiding, v23 app looks for the stub at the wrong place (v24 from Github) and cannot complete

I don't recall was it confirmed would it work or not if you switch to Airplane mode before hiding - you could easily test

Otherwise, you need to set Update channel to Custom, pointing to the json for v23.

You could go back and look for a post from pndwal, maybe 3 weeks or so ago, he provided the exact URL for that Custom channel you would need to point to v23

Good luck
[Magisk] pndwal:
Likely it is not possible w/ your current configuration, but you can do such things using Magisk Tools from CLI.

magiskboot binary allows ramdisk patching with env variables KEEPVERITY, KEEPFORCEENCRYPT and PATCHVBMETAFLAG configured...

https://topjohnwu.github.io/Magisk/tools.html#magiskboot

John removed such options from Magisk App a while back now as too many people were breaking their devices... You'll need to research further what is safe / what works on Pixel 3 XL, LOS, Android 11 etc, but John addressed changes / problems re. disabling force encryption, dm-verity and AVB 2.0 and other requirements like patching DTB back in 2020:

www.twitter.com/topjohnwu/status/1297833910320021504

👀 PW
[Magisk] Stillhard:
Commited
[Magisk] pndwal:
No; only for 24.0+ when the same issue occurs...

Info & URLs here:

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

🤠 PW
[Magisk] pndwal:
Latest Official TJW Stable Magisk:

Magisk​

2022.3.10 Magisk v24.3​

For those coming from v24.1, check the full changelog for changes introduced in v24.2.

[General] Stop using getrandom syscall

[Zygisk] Update API to v3, adding new fields to AppSpecializeArgs

[App] Improve app repackaging installation workflow

Full Changelog: here​

😛🎉🥳

... That's the way to move appartments John!...

Push out some furniture, then push Stable Magisk... We coulda waited till you put your feet up mate! 😜

👍 PW
[Magisk] pndwal:
Latest Official TJW debug Canary Magisk:

Magisk (2c092ffd) (24301)​

Sync with public release

Diffs to v24.3​

None

https://github.com/topjohnwu/magisk-files/blob/1fc36f6fba998d8f84d749881dfd7fb7012b9d29/notes.md

👍 PW
[Magisk] visa91:
I've got a bootloop with this update, be careful. SOlved installing the previous version.

My phone: Poco F2 Pro MIUI 12.5.6 for information
[Magisk] rzapf:
Hi - just updated to Magisk 24.3 on Android 12 (herolte / lineageOS) - now zygisk seem not to be recognized anymore (Zygisk = no on main page).

Zygisk use is not activateable in config page

- slider moves to on,

- reboot

- slider is on "on"

- main page shows "no"

- sub-packages not running

Had no trouble with preliminary version.

Any advice?

Thanks in advance

RUE
[Magisk] Spartacus500:
Samsung Galaxy S7 Edge 9.0 Pie NFE, after updating Magisk to the latest version 24.3, the Bank mandiri online application stopped working, the application cannot be opened, the application is stopped all the time 🤔
[Magisk] knojap:
G930f

magis 24.2 and 24.3 installed fine.

but Zygisk won't start.

Module not activated.

Is there a way to fix it?

Thx
[Magisk] dobi3:
I would toggle Zygisk on/off in Magisk app and reboot device.. You

have a Zygisk module.. None of my phones have any Zygisk module
[Magisk] knojap:
I have tried to do that. Not working.

I#m talked abot the zygis function not another module-
[Magisk] regularmen:
awesome, hiding works now. thanks guys
[Magisk] Kurt Krummbein:
Hi guys,

i recently installed LineageOS18.1 on my gauguin and have a problem after installing Magisk (currently tried v24.3).

On boot, i seen adsprpcd, sscrpcd and cdsrpcd crashing in a loop, being restarted after 25 ms. This not only slows the device down, it also prevents WiFi to come up (and probably more) ... but i think that's just the end, errors start in logcat earlier ... zip attached.

Googled around ... tried to disable it in /vendor/etc/init-rc script ... no way :-(.

Any ideas who this could be fixed?

Greetz

Kurt
[Magisk] rogers11:
On my Pixel 4a with LOS 18.1 the update from 24.1 to 24.3 went fine.

Thanks a lot.
[Magisk] ashish1989:
I am unable to update to 24.3, currently I am on 24.1 stable channel. I am getting the update within the app and after downloading the update nothing is happening
[Magisk] zgfg:
Probably the permission to install (from unknown source) is missing or so

Why don't you download the apk directly from Github and install (one way or another, this is still only updating the Magisk apk, not yet the Magisk itself)
[Magisk] ashish1989:
I think you are right, maybe it was a permission error

However I have downloaded and installed the apk and its working f9

1 more thing with new update is USNF not required if it had got the workaround
[Magisk] zgfg:
Looking into the Changelog, I don't see any difference regarding the use of USNF

If your ROM needed USNF to pass SafetyNet, you should still need.

Btw, you can disable USNF, reboot, test and decide

Anyway, TJW had distanced himself (for the well known and understood reasons) from anything related to SN - hence, don't expect he would change the policy and put 'back' anything to spoof his employer (that's also about the architectural difference between the old MagiskHide and new DenyList)
[Magisk] pndwal:
Latest Unofficial vvb2060 Alpha (For mavericks only); Chinese translated:

# alpha changelog

## Magisk (2c092ffd-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] Allow loading zygisk modules

### how to install?

Magisk is installed and uninstalled through the Magisk application. Generally, it should be done directly in the application. In special cases such as the first installation, the image should be patched and then flashed using the fastboot/odin tool.

By customizing Recovery is not a supported way.

# Upstream changelog

## 2022.3.10 Magisk v24.3

For those coming from v24.1, check the full changelog for changes introduced in v24.2.

- [General] Stop using `getrandom` syscall

- [Zygisk] Update API to v3, adding new fields to `AppSpecializeArgs`

- [App] Improve app repackaging installation workflow

### v24.2

- [MagiskSU] Fix buffer overflow

- [MagiskSU] Fix owner managed multiuser superuser settings

- [MagiskSU] Fix command logging when using `su -c <cmd>`

- [MagiskSU] Prevent su request indefinite blocking

- [MagiskBoot] Support `lz4_legacy` archive with multiple magic

- [MagiskBoot] Fix `lz4_lg` compression

- [DenyList] Allow targeting processes running as system UID

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

- [Zygisk] Improved Zygisk loading mechanism

- [Zygisk] Fix application UID tracking

- [Zygisk] Fix improper `umask` being set in zygote

- [App] Fix BusyBox execution test

- [App] Improve stub loading mechanism

- [App] Major app upgrade flow improvements

- [General] Improve commandline error handling and messaging

(Changelog from source .zip.)

👍 PW
[Magisk] dr4go:
Upgrade worked flawlessly on a Galaxy S10 running on A12.
[Magisk] prot0byte:
Hi. I have a OnePlus 7 Pro in which I had Android 10 and LineageOS 17 with microG and magisk (sorry I didn't take note of the version, I believe it was 21) installed on it and it worked with no issues.

I just upgraded it to Android 11 (requirement for LineageOS upgrade) and LineageOS 18. Things seemed to go ok. Everything worked at first. Even the wifi. But then I went to play Vanced YT and noticed it was no longer installed. So I went to install magisk the latest which is 24. I followed the instructions of patching the boot.img and then flashing the magisk_patched-whatever.img.

Ever since then, my wifi stopped working, and while troubleshooting, I noticed that my LineasgeOS Recovery no longer boots. And I get this strange flicker when it first boots followed by an error message saying the System UI crashed. I hit ok and continue running the device just fine with the exception of the wifi.

I've re-flashed the original boot.img and nothing changed. I still can't turn on wifi, I still get the system ui crash error message on boot, I still can't get into recovery. I re-flashed recovery too, that still didn't change anything. I also un-installed magisk. Nothing changed.

I also tried re-flashing the other images like I did when I upgraded using commands such as `fastboot flash --slot=all <img> <img>.img` but no matter what image I chose I always get `fastboot: error: Could not check if partition <img> has slot all`. I don't know what this means. I can't get any logs because I can't boot to recovery.

Any idea where to go from here?
[Magisk] pndwal:
LV is A9. Is this an A/B device? Ramdisk (in boot) = Yes or No?

Do you mean stock Android upgrade required first?...

So Magisk root gone entirely? (My guess.)

So you patched / flashed boot image extracted from current ROM, ie. LOS 18.x (18.1)? Guess you needed a payload dumper tool to extract it? Or were you able to use a TWRP backup?

I'm guessing you have A/B device w/ a recovery type ramdisk in boot partition (ie. no boot.img in ROM)?... Or is it A-only w/ Magisk installed in Recovery (ie. w/ Recovery mode on)?

However this is sounding very like you have a mismatched kernel. This is why I'm guessing you have an A/B device and are patching boot.img, not recovery.img, and used wrong image. Since Magisk is actually in recovery's ramdisk (which is in boot partition), recovery may likely also be affected...

Kernel must be matched with ROM. As this resides in boot.img, using (patching/flashing) wrong (mismatched) boot.img will result in many issues, especially comms and other hardware issues.

So did you use unpatched current boot.img, ie. extracted / sourced from current LOS 18 ROM?

By 'Original', do you mean old LOS 17, later stock, or unpatched LOS 18.x? ... If not LOS 18.x it's wrong (unless you changed OS)...

Nb. When John says 'stock image' in Installation Instruction page, he doesn't account for custom ROMs an really means 'unpatched image'.

So this is confusing; do you actually have a recovery image / partition?

If you flashed stock boot.img over custom LOS, that would make sense...

So you may restore by flashing LOS 18.x boot.img (assuming it's A/B and LOS 18.x OS is current)... But you may need to reflash stock A11 ROM first as you indicated was an initial requirement... Also, I'm not experienced w/ A/B devices...

As above... All best... PW
[Magisk] onesolo:
Does the update OTA method works with 24.3 ??
[Magisk] pndwal:
Magisk is in fact an asset for Android security research and development... 😛

www.twitter.com/topjohnwu/status/1502026971957530639

CVE (Common Vulnerabilities and Exposures) is a system that facilitates the Security Content Automation Protocol and provides a reference-method for publicly known information-security vulnerabilities and exposures. The United States' National Cybersecurity FFRDC, operated by The Mitre Corporation, maintains the system, with funding from the US National Cyber Security Division of the US Department of Homeland Security.

https://en.m.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures

👀 PW
[Magisk] pndwal:
Do you mean Enable installation to inactive slot on A/B devices in order to preserve Magisk after OTA installation as described here?:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md

Apparently it should work since this PR was merged:

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

However a PR to adjust notes is pending:

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

👀 PW
[Magisk] Lughnasadh:
I can confirm it has worked for several people using Pixels. You must, however, make sure you are not on a custom kernel or have modified /system, /vendor, vbmeta, etc in any way or you will fail the pre-OTA verification check.

That PR is just to remove the note saying the option has been removed, since it is no longer removed.
[Magisk] traversone:
hi all,

I am getting aware that, starting from 24.2 release (and parallel Canary and Alpha derived), the ZIP installation from TWRP fails (rom is LOS 18.1).

Error is "cannot mount /system"..

till 24.1 official no issue

of course, patching the boot and flashing it in TWRP is successfull but this behaviour makes LOS frequent updates time consuming...

thank you