yashsingh1/xdaforums huggingface dataset:
[Magisk] ctcx:
Need a bit of help...

Using LOS 20 ROM and Magisk 25.2. LOS updated, thus boot.img returned to non-patched; if this is what you'd call "Magisk uninstalled". However, Magisk app stills there, just with the limited/basic functionality of non-patched...

How can I update Magisk in the device, preferably without having to patch again?

Is it in Magisk home screen, with the "App Install" option (the one being below "Magisk Install" option used to patch...)

First, renaming to .zip and flashing from recovery is no longer recommended according to Magisk updated docs, although I once observed this was the only way for Magisk to show all functions as if patched boot.img, without actually patching...

Again with renaming to .zip... And if this were true then @badabing2003 's PixelFlasher would probably not have reason to be...
[Magisk] J.Michael:
You cannot update Magisk without patching again. Magisk only exists after you have patched your system. Changing what version of Magisk you have requires repatching your system.

I do not understand why people are so hung up on the "patching step".

When you use the Magisk manager app to patch an image, the hardest part is remembering which of the two "Install" buttons leads to patching an image, rather than installing/updating the Magisk manager app.

When you use a procedure that "skips the patching step", that just means that the patching occurs without you realizing when it happens, and without you ending up with a patched file you can use repeatedly.

Once you have a working Magisk you have more options. You can trigger a reinstallation/update from the app. You can feed a different Magisk APK to the app as if it were a module and it will change the Magisk that is installed.

Until you have a working Magisk, you have very few options. You need some way to flash partitions. You need to patch some image and flash it.

@badabing2003's PixelFlasher is an alternative UI to the process of patching and flashing. A lot of people find it easier than following the steps. Maybe you should try it.
[Magisk] badabing2003:
It looks like Magisk 26001 still has an issue with patching a stock boot.

Anyone else experiencing that with April firmware releases?

Tested it with March release, which I had successfully previously created a patch with 25206,

26001 couldn't.

I'm Reverting to using 25206 again.
[Magisk] Lughnasadh:
I was able to use Canary 26001 successfully on my Pixel 6 Pro running A14 DP2 (March security update). Since I was only updating I did do a direct install rather than patching and flashing, so maybe that's where the difference lies.
[Magisk] badabing2003:
Right,

Same with my P7P, I was on Magisk 25206, and did direct install to 26001 and that worked fine.

But with the April release, I had to patch the stock boot, and that failed.

Wanted to be sure it was an issue with 26001, tried to patch a stock March init_boot (that had worked with 25206), and that failed too.

I reverted to to 25206 and successfully patched April boot (to be precise, init_boot, since I'm on P7P)

Phone is now rooted and on April release.

I suppose I can reinstall / update to 26001 and do direct install, but I won't bother considering the next patch I would need to create it won't work.
[Magisk] Nergal di Cuthah:
What platform tools version? 3.40 (i think that's the number) and above are broken
[Magisk] badabing2003:
Yeah, I'm aware of that, I'm using 33.0.3
[Magisk] Lughnasadh:
For what it's worth, you can still flash boot images and init_boot images with Platform Tools 34+. But anything that needs flashing in fastbootd won't work with 34+.
[Magisk] ctcx:
While in non-patched system, I do have still the two "Install" buttons, and I already know first one is for patching image.

But then, what's the second one for, the one saying "App"?

If I try using it it asks for permissions for any 3rd apps to "install/make changes".
[Magisk] Nergal di Cuthah:
The magisk manager app litterally update this app
[Magisk] ctcx:
And isn't that the very thing I need now?

Or, what is the definition here of "updating Magisk" then?

I just wanted to go from one version to latest one, whatever it meant (I still cannot believe it has multiple meanings...)
[Magisk] badabing2003:
Magisk is two parts.

The core / daemon, this one provides the root functionality and is what boot image is running

The Manager / Application, this one is to manage the settings / modules ...

In this image, it is telling me that, I'm running core 25206, and manager 25206, but there is a newer manager version available to install (26001)

That update button will only install the manager. (I won't do it with 26001, because I don't like that version, see above if you want to know why)

To install any 3rd party app, you would need to grant permissions to the app that is installing it, in this case it would be Magisk.

Once you install the newer Manager,

The update button will shift from App to Magisk, that is because the manager is updated, but the boot image is not yet updated.

If you click the update button, you would be presented the options to update the boot,

Patch, direct install, Recovery (if your device supports it)

Hope this clarifies it.
[Magisk] mihir24:
Are you able to pass SafetyNet and use Google Wallet?
[Magisk] Lughnasadh:
I don't use Google Wallet or any other app that requires me to pass Play Integrity API so I don't even try.
[Magisk] ctcx:
@badabing2003 :

Thanks very much for your explanation; now everything finally got clearer.

Since I have not patched again since last system update, in my case there's really no running daemon to update; meaning for now I can only update just the "app" itself, also called "manager", as I read.

But, unlike your screenshots, for the "App" I still only get the "Install" button instead of "Update"; I don't know whether this is due to being on non-patched system or because Magisk app doesn't have appropriate "permissions"...

So in the end, for now I only seek to update Magisk manager/app.

Can I just use the "App Install" button there? Is it safe to give it the required permissions for the app?

And yes, I did read about current version's issues; but I'd like to be sure for when a new version is released.

Thanks again.
[Magisk] Nergal di Cuthah:
In that case you're already on that build's manager. That button (the one in "app")can be safely ignored. As long as latest and installed agree then leave the button until next it says update.
[Magisk] WislaHD:
I am delighted to say that flashing the boot image fixed my phone. Note to those who follow, I was still stuck in that frozen boot screen for a long time, I was even about to reboot into fastboot mode before the option menu loaded up. Afterwards, I selected Reboot and it booted quickly into my device.

I appreciate you breaking down the issue and the steps to resolve, even the steps for safely returning to root. I am going to take a moment to enjoy the return of my device and experience (the very flawed OOS update lol) Android 12 first and commit the necessary backups before attempting rooting with Magisk again. I'll be sure to follow your steps here given that there may still be legacy artifacts from the previously installed modules, which as I understand makes installing that special version of Magisk Manager important in my case. I'll provide an update on progress when I get around to it. Thanks again to all who contributed.
[Magisk] badabing2003:
Yes you can do the Install, it is safe, if you downloaded it from the official github link.

The bottom part which is the manager, should only be update, as the app can only be installed to show it.

The top part, which is the core, should be "Install" instead of update, to install the boot image.

Perhaps a screenshot would help.
[Magisk] ctcx:
I think it's due to the fact of not being in patched system that Magisk app doesn't show the full functions; for example, aside of not having the "Update" button and instead being just "Install", I also don't have the whole "Uninstall" button.

As far as I recall, the whole functions showed up only in two cases:

--When in patched system

--Changing Magisk apk's extension from .apk to .zip and flashing it through recovery mode when in not-patched system; though this process is no longer advised according to current Magisk docs

I wonder if it's fine to just hit "App Install" button, and letting it check/download latest apk version...

(Yes, when first installing Magisk, I did get the apk from Github).
[Magisk] badabing2003:
All three methods do the same thing, they rewrite the boot partition with patched image.

Whether you do it in recovery (not recommended anymore), or create a patch and flash it yourself or use direct Install (which is only available if you're already rooted).

If you install apk, assuming that what you're referring to is the bottom section as the top section is not about installing APK (that is why I asked for screenshot), then all you're doing is installing the manager, although I'd be surprised to see it say install instead of update, as you already have the manager installed.

I suspect you're referring to the top section, in which case install will take you the next screen to choose the method (one of the three) but that will rewrite the boot partition, and not install apk.
[Magisk] whitedavidp:
I have been having some major issues with my LG V40's VoLte mechanism. If the signal is lost in a dead zone or if flight mode is engaged/dis-engaged, the phone will simply NOT re-connect to the Volte leaving me in emergency call mode until I reboot. I have found, by accident, that these issues DO NOT occur if the phone is in Safe Mode. This makes me think that some mod I have done via magisk, LsPosed, etc is the source of my problem.

Sadly, I cannot get at anything while the phone is in safe mode. I would try to use adb but this damn phone (many LG models, in fact) has long had issues with USB connectivity - described elsewhere. I have tried to make my terminal emulator or rooted file manager into system apps hoping that if they were I could use them within safe mode. But that doesn't work either.

SO... I use Magisk all the time without, I must admit, understanding much of what it does or how it works. It just seems to... But now I really think I need to be able to get at files that Magisk seems to "protect" in the system as I suspect what I need might be in there. I have no idea where Magisk puts/keeps all this. I will post in the Magisk thread but thought I'd mention it here as well.

Thanks for any suggestions.
[Magisk] Nergal di Cuthah:
What lsposed modules do you use. Do you use a vpn and it's interfering maybe. What magisk mods?
[Magisk] ipdev:
No issues for me using a slightly newer version of Magisk 26001.

I run personal (snapshot) builds of Magisk, so I have all the commits from April 5th -> 8th.

I did not make a new build with with commits from the 9th since it was only translation.

---

I just updated my P7 to the current April build.

It was still on December 2022 build.

I updated Magisk with no issues from (what ever I was running back in Dec.) to my current version.

There was one issue but, that was same issue (more of an anyoance) that I had on other devices.

Becuase I have the app renamed, it gave warning about signature and triped Play Protect.

I had to go back and forth a little with restoring the app (undo the hide/rename) on some devices.

For me, it showed up with one of the commits shortly before Magisk bumped up to 26001.​

I update using the full factory images, and edit the flash-all script.

A little more than I did back in the Nexus days. 🙃

sleep 5
# fastboot -w update image-panther-tq2a.230405.003.e1.zip
fastboot --skip-reboot update image-panther-tq2a.230405.003.e1.zip
fastboot reboot bootloader

Note: The --skip-reboot option will leave you in fastboot_d mode after the update finishes.

I add the reboot to bootloader so I can just boot or flash my new patched Magisk image.

Except I forgot to patch the new init_boot image before I ran the update.

Instead I just booted (turned on airplane mode right away) and patched the new init_boot image.

Booted to bootloader and flashed the magisk patched init_boot and rebooted.

Magisk was installed and active so I turned off airplane mode.

---

I primaraly use Linux (fedora) and the current version (34.0.1) of platform tools.

From what I read, there are some issues with MacOS and Windows with v34.x.

I do not use Windows (only Win7 when I have to) and I have not used my older MacBook in a few years.

My new MacBook, I have not had time to setup (I charged it up about a year ago). 🙃

Cheers all. :cowboy:
[Magisk] whitedavidp:
Thanks. I guess I am pretty simple:

Magisk modules:

App Systemizer

Busybox

Debloater

Systemless Host

Viper4AndroidFX

ZYgygisk-LsPosed

LsPosed modules:

GravityBox

Untoaster

XDowngrader

XposedEdge

SecureSettings (not enabled) - but I do you it a small amount via Tasker

No VPN.

Thanks
[Magisk] pndwal:
Are you certain you have a patched boot image extracted from current downloaded ROM? (If took an OTA then re-rooted you'd need to download full ROM matching OTA version)...

These coms, bt and other hardware issues often result from users simply flashing a boot image patched using a previous ROM version again after an update...

Nb. Updates more often than not update both system and corresponding binary blobs etc in kernel, and kernel is in boot image. (With newer GKI builds kernel is now in a seperate boot image however)...

🤠 PW
[Magisk] J.Michael:
Magisk manager app is just an Android app, you can uninstall it using Android's app Settings (app info tooltip when long press icon, or crawl through Settings -> Apps) "Uninstall" button. You can update it by just installing a later APK. The only time you might have to dance is when you are trying to downgrade the Magisk manager app version -- it now has "protections" against rollback, so you have to work a little harder.
[Magisk] pndwal:
f2fs issue ->> bootloop

https://github.com/topjohnwu/Magisk/issues/6841 (fix merged)... A number of other issues w/ fixes too... 👀 PW
[Magisk] pndwal:
Latest Public Stable Magisk!!👍🎊🎉

Magisk Changelog​

v26.1​

[App] Fix crashing when revoking root permissions

[MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition

[General] Restore module files’ context/owner/group from mirror. This is a regression introduced in v26.0

Release Notes here:

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

👍 PW
[Magisk] pndwal:
Latest Canary (+Debug) Magisk:

Magisk (d0c93842) (26101)​

Sync with public v26.1 release

[App] Fix crashing when revoking root permissions

[MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition

[General] Restore module files' context/owner/group from mirror. This is a regression introduced in v26.0

Diffs to v26.1​

None

https://github.com/topjohnwu/magisk-files/blob/99853810619807f8b61c324fe70636a47e447419/notes.md

👍 PW
[Magisk] rogers11:
Hello, is it safe to upgrade from 25.2 to 26.1 using Magisk Manager on my Pixel 4a with LOS 20?

Last week I had to reinstall my tablet (Samsung Galaxy S5e) because something went wrong with 26.0, that's why I ask this time. 😬
[Magisk] Fishawy:
Already updated from 25.2 stable to 26.1 stable via app prompt (Pixel 7 Pro), then updated Magisk through direct install. No issues.
[Magisk] Spartacus500:
26.0 Beta to direct install 26.1 stable 👍
[Magisk] immortalwon:
I also upgraded to 26.1 and it seems stable. No more broken pipes, as was indicated in the magisk logs in 26.0
[Magisk] rogers11:
Yes, works. Thanks.
[Magisk] manjaroid:
FWIW, I was updating 26.0 to 26.1 when I'd get the 'Error downloading file' message as if there wasn't a connection or something was blocking the file. Last time this happened clearing the hosts file and pausing Adaway allowed the download. That didn't work this time but tapping install instead of cancel did the trick. Apparently the file was downloaded and ready despite the error and the update completed.
[Magisk] pndwal:
Here's the Latest Public Stable Magisk Release Notes (they're up, but not accessible via main link as index.md link is broken):

2023.4.11 Magisk v26.1​

Changes from v26.0​

[App] Fix crashing when revoking root permissions

[MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition

[General] Restore module files' context/owner/group from mirror. This is a regression introduced in v26.0

(The following is the same as v26.0 release notes)

Hey! Long time no see!

Bumping Minimum Android Version to 6.0​

Magisk's support for Android Lollipop has been pretty broken for a while without it being noticed. Also, none of the active developers of Magisk have actual hardware to run Android Lollipop. We rely on using the official Android emulator for regression testing on older platforms, however Google never shipped a Lollipop emulator image with SELinux support, leaving us with no option but to drop Lollipop support since we don't feel comfortable supporting Android Lollipop without adequate testing.

New Magic Mount Implementation​

Magic Mount, the feature that make modules modify partitions, has gone through a major rewrite. The existing implementation doesn't work well with OEMs injecting overlays into their system using overlayfs. The new implementation fundamentally changes how filesystem mirrors are created, giving us a more accurate clone of the unmodified filesystem.

New sepolicy.rule Implementation​

Magisk allows modules to provide custom SELinux patches by including the file sepolicy.rule. Due to the complicated nature of SELinux patching, the compatibility of this functionality has been pretty spotty; many devices are not supported. In this release, a brand new pre-init partition detection mechanism has been designed to support even more devices. Due to complicated reasons, this detection mechanism cannot be performed in a custom recovery environment.

This means that any installation of Magisk v26+ using custom recovery will be incomplete; a subsequent re-installation through the Magisk app after booting up is required.

Zygisk Updates​

The new Zygisk API v4 is now live! It comes with new features and a refined PLT function hook API. The implementaton of Zygisk has also gone through some major refactoring, including new code loading/unloading mechanisms and a new PLT function hook implementation.

Head over to the Zygisk Module Sample repository to check out the new API and documentation!

Full Changelog: here​

Link via View Code:

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

👍 PW
[Magisk] ctcx:
So Magisk 26.1 was just released, and the "App Install" button now went to "App Update" indeed...

Then I suppose authors had just "removed" the automatic update to 26.0 out of the reported issues?

But I think I'll first wait for your point of view regarding this new release sir.

Thanks again.
[Magisk] badabing2003:
I'm looking into this.

Creating a patch with boot_patch.sh is not generating a matching patch to the one created in the Manager UI.

Even 26.1 stable generates different RAMDISK than 26101
[Magisk] whitedavidp:
When I got this phone, I immediately updated to the latest (and last) Android LG released. Only then did I proceed to root following specific instructions here on XDA for this LG V40 phone (t wasn't easy). Other than that, I cannot say. But I do not think I am at risk of what you describe.

The really strange thing to me is that I have this trouble ONLY when NOT in Safe Mode. And wouldn't the same boot loader be used for both Safe and Normal modes? I would have thought Safe Mode only impacts Android once it starts booting.

Thanks
[Magisk] Th3 Ant:
Hi guys...

So I have a little problem and I have no idea how to tackle it - I tried flashing latest stable version (v26.1) but after that, I can't boot into system. Nothing helps - flashing stock boot.img without magisk, flashing magisk with recovery, uninstalling magisk using recovery, dirty flashing ROM... all my device does is rebooting itself to recovery.

Is there any way to boot into system without clearing data?

Thanks
[Magisk] zgfg:
Magisk also tries to detect if Android is booting to Safe Mode (successfully or not, depending on the phone/ROM), and it switches to the Core only mode (all module being blocked)

But Core only mode should remain then in the subsequent normal boot

Please consult (general advice) the official Magisk documentaition, available from the Magisk GitHub page - link to start from is in the Magisk app
[Magisk] jons99:
if you want to know the cause for your issue then grab a logcat (connect to a pc and type adb logcat > logcat.txt in power shell) but since you tried every solution possible (reflash the rom uninstall magisk and so on) it looks like you're only answer is to wipe data maybe even format if I had to guess I'd say you have an encryption problem
[Magisk] Th3 Ant:
The problem is I can't even get logcat - it just hangs at boot logo and then reboots itself to recovery...

If that helps, I'm attaching some log from /sys/fs/pstore

EDIT: Formatted data - still nothing... doing full wipe now...
[Magisk] 80s Baby:
does the latest build fix the r/w access on the samsung s23 series? i've tried rooting with the stable 26 build and i didnt have r/w so i werent able to debloat using root

can anyone help me with this please?
[Magisk] badabing2003:
if flashing stock boot.img without magisk is not working, stop looking at Magisk.

Something else is wrong.

I'd start with dirty flashing a factory image, making sure it does not wipe (for Pixel devices, remove -w)
[Magisk] zgfg:
Checj /data/cache/magisk.log from. TWRP (if TWRP available for your phone and ROM)
[Magisk] rogers11:
So, how should I update my Samsung Galaxy Tab S5e with LOS 20.0 from 25.2 to 26.1:

1. flash Magisk.zip from LOS Recovery (worked with 25.2 but caused a bootloop and data-loss with 26.0 last week)

2. flash a patched boot.img with adb

3. use direct install as recommended in Magisk Manager (recovery mode on/off?)

Thanks
[Magisk] Th3 Ant:
Already tried that like 20 times - nothing changed... same issue - stuck at boot logo -> reboots to recovery

There was no magisk.log anywhere...

I've managed to boot into system but the only solution there was left was factory resetting everything (which indeed worked)

Thanks for help :D
[Magisk] ctcx:
Excuse me, when on fully installed Magisk (this is, on patched system), if uninstalling only the manager (only the app itself), is there consequence? Or is it a matter of just downloading the apk and manually installing again? Does Magisk detect all full functions again?

Also, within Magisk manager scripts, is there a way to get installed Magisk's version?

Thanks again.
[Magisk] zgfg:
Run magisk -c in Terminal emulator to read the version

The app is only a user-friendly manager. You can uninstall (only the apk). However, you want be popped-up.if a new root app requests root grant

Otherwise, most of the functionalities can be managed manually via Terninal emulator (run magisk for help) or by a root explorer like MiXPlorer
[Magisk] whitedavidp:
Thanks! I had booted into safe mode, checked again that my issue(s) do not exist there and exited from safe mode to normal boot. You are right that all modules are disabled. Never noticed that before. So I checked for the issue(s) and they remain. Well, I learned something. Cheers
[Magisk] J.Michael:
I believe all of those are viable options. I quibble with the notion of flashing with adb -- I don't think anyone does that, I think people use fastboot to flash.
[Magisk] J.Michael:
For future reference, if flashing the stock boot image does not solve the problem, then I question whether you really flashed the stock boot image.

You do not mention what your device is, or whether you had a version of Magisk before trying to install v26.1.