yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
1. This will only partially install Magisk now anyway; you'll get a message to reinstall from App when you open it...

2. This is generally for initial Magisk setup, but some Huawei (and other?) devices require it for updates also as boot can't be written to while system is booted...

3. This is generally used for Magisk updates unless you have reason to believe it won't work on your device...

Hope it helps... 🙂 PW
[Magisk] rogers11:
I will try after work. Thanks a lot.
[Magisk] nicky-xda:
Xiaomi mi9, crDroid9.3 / android 13: after uninstall Magisk phone only boots into recovery

I completely uninstalled Magisk from the magisk app. After that it boots only into recovery.

Installing the ROM again, flashing boot.img from the ROM does not solve it.

What happend with it and how can i try to correct that?
[Magisk] rogers11:
Just to confirm: it worked with direct install. I did not notice any progressbar or something else but after reboot it shows 26.1. Thanks again for your help.
[Magisk] wyt18:
I updated to 26.1 but now google play services keeps force closing, and some apps like my browser won't work properly. Anyone has a similar issue?
[Magisk] pndwal:
Folks, I know most of us loved the Magisk Manager, but I think John burried it with good reason... https://topjohnwu.github.io/Magisk/...agisk-manager-is-deadlong-live-the-magisk-app

The last Magisk Manager was v8.0.7... That was "just an Android app", and with that "all you're doing is installing the manager"...

The new Magisk App is a different beast altogether, and I'm sure John discontinued the old 'Manager' designation to avoid confusion...

While the Manager and Magisk core used to be independent and updated independently also (these were both called from an online JSON with URLs for latest versions for both), now the Magisk App is not 'just a Manager', it's the complete offline Magisk package...

Key differences between old Magisk combo (Magisk Manager 'companion app' .apk and core Magisk binary .zip) and new Magisk App:

- The App now includes Magisk core binaries for offline installation as well as zip install/uninstallers and stub apk. (Previously we had discrete Manager and stub apps as well as zip installer for core binaries and zip uninstaller.)

- App Install itself (incl binary package etc) still updates from online JSON's URL, and will match 'App; Latest'

- Magisk core/binaries now update/install from the App package as an offline process...

- Seperate app version scheme is abandoned as new App is tied to (synced with) the core binaries contained in the .apk package and App version now aligned with Magisk core components

- 'Magisk; Latest' is no longer displayed in App as this will now always be the same as 'App; Latest'*

- Magisk Install will now always match 'App; Installed'.

*Nb. This will depend on Channel setting; If custom channel is set with no properly configured URL, user will see 'App; Latest = N/A' and won't receive any Update notification

So clearly Magisk App is not 'just an Android app', and you're not simply 'installing the manager'... It's the complete Magisk Package incl. core binaries (not to be confusd with the long "dead" but simple Manager), and installing the correct version impacts (determines) the core Magisk components installed (unlike the abandoned Manager app)!

I'd be happy to see members here using John's considered new nomenclature because it's his choice as Magisk project's leader, it distinguishes new single-package Magisk App from the old Magisk companion Manager app and it reduces confusion about it's functions (especially how it's binary package function actually impacts Magisk core installation).

Magisk Manager is dead.

RIP Magisk Manager 😢 ...

Long live the Magisk app! 😀

👀 PW
[Magisk] pndwal:
What have you put in denylist?

What modules are installed? ... PW
[Magisk] zgfg:
All that is true, but:

- First, when you install Magisk app, you don't have Magisk (core) installed yet. I know that you know that very well but every week comes somebody who doesn't understand the difference and from his posts and questions is not clear did he install/update only the Magisk app or also Magisk (core), etc, and what is he asking and how to help him

- Second, once you install Magisk (not the Magisk app only - and installing/updating the Magisk is recommended through Magisk app, sic), then you can even uninstall Magisk app - if you, ie, particular user is good in using Magisk command-line-interface through Terminal emulator, since he could do practically everything (managing the modules, etc) through CLI, by hsving the Magisk app uninstalled (Magisk app lets you manage all that more easily)

- Third, most users are then also confused what does it mean to 'uninstall Magisk'. Eg, would just uninstalling Magisk app also uninstall Magisk (core) - definitely not, but still many users are confused about. Or they uninstall Magisk app and then they ask why they still have root (Magisk), modules working, etc

Hence one way or another, that 'new' (actually, not that much new) terminology is confusing

And even with all that, the app is really a 'manager' that lets you install the Magisk, update the Magisk, manage the modules, DenyList, etc

The apk does come with all you need to INSTALL Magisk (in the apk package), but just by installing the app Magisk is NOT INSTALLED YET (yelling for some others, not for you)...

---

IMO, it's something like 'banking' apps - we all know that not only banking apps seek for 'root' (and not only for root, again a common term) but also some games, e-citizen apps, rewarding/loyalty apps, etc - but we still use the common term 'banking' apps

Similarly, when trying to help to the newbies here it makes it easier to emphasize that just by installing/updating/uninstalling the 'manager' they did/will not install/update/uninstall the Magisk

My two cents
[Magisk] wyt18:
Denylist: Banking apps, Payment apps (e.g. GPay), Google, NFC, Zoom

Magisk modules: Bluetooth library patcher, GMS Doze, NoStorageRedirect, Shamiko 0.7, Sqlite, Systemless Hosts, USNF v2.4.0 Mod 1.2, Zygisk - Lsposed 1.8.6

Lsposed modules: Core patch 4.2, Fermata Auto 1.9.1, Firefds Kit 12.0, Hide My Applist 3.1.1, Kill Domain Verification, TSBattery 4.2, Xposed edge pro 8.0.1
[Magisk] badabing2003:
Thank you @zgfg

You took the word out of my mind.

I think this bundling the two into one app added more confusion, of course not to the seasoned veterans but rather to newcomers or infrequent users.

Although the two are bundled together, they are still too distinct components that do totally different things and understanding the subtleties is critical, which is not very obvious at a glance.

I was trying to explain that, and even with my attempts it was still a bit confusing (expectedly so).

@pndwal what you said is very accurate and too clear to me, but is it to the next reader that was not exposed to the past versions of Magisk?
[Magisk] pndwal:
@zgfg, @badabing2003, others

Re. Magisk Manager is dead...

Long live the Magisk app!

Folks, I knew that that post would not be popular, and I know the views (many intrinsically valid) you both expressed are held by more than 3 members... That's in part why I posted it...

Personally I think to keep resurrecting the old Manager can be equally confusing however...

Calling it 'just a manager' or 'android app' fails to account for what core Magisk build will be installed, and I recall much confusion when v22.0 arrived; many simply hadn't connected the fact that the App installed now determined the Magisk build used for patching or updating... It was many months before we all got our heads around the App also being the binary package/installer. And this despite John spelling it out as clearly as can be expected...

Mainly though, John made these changes / announcements as the project author/lead dev, and they seem to be being conveniently forgotten...

We now formally have the Magisk App (all-in-one package for Magisk) and the Magisk Manager is long gone whether we like it or not.

I've tried to understand John's rationale and the reasons why all mention of 'Magisk Manager' has been expunged from official docs, and I think the change can really be viewed as timely, marking a significant change/milestone for Magisk... So I'll admit that it's not just for practical reasons that I avoid referring to the Magisk App as the Manager; it's also because I believe that it's creator's wishes and roadmap for future Magisk, including minor and major changes, should be respected, especially in his own General Support / Discussion thread...

And it doesn't hurt to try to be accurate... 😬 PW
[Magisk] pndwal:
I know it's a fine point, but maybe stating "installing the App will not install core Magisk but is vital before flashing if you want the latest build because the core binaries for patching are embedded in the App" (instead of "all you're doing is installing the manager...") might actually clarify things even for readers who were not exposed to the past versions of Magisk?

Again, I mean no disrespect and love your work (making Magisk more accessible to many)... It's just my 2 cents also, and plenty of room here for dissenting views... After all if we take 'Hide the Magisk app', we actually get to call it whatever we like!...

Personally, I hate "Settings", but I'll keep mum re. my choice...

Some might go with M Dashboard, Module Mayhem, Superuser Access, Superman's Car, Poweruser Primary Kit, Android Modifier, Magical Mask, Alternative Overlays, Magic Mounter, Magical Mystery Tour, My Little Pony...

... Or M Manager if you like... 😜 PW
[Magisk] Peter770:
What is the correct way to install Magisk? Currently i am installing Magisk by flashing it from TWRP, but in Magisk wiki i see installing from custom recovery is not recommended. Instead it say i have to extract boot.img from stock rom and use it during Magisk installation, which makes things more complicated.
[Magisk] tangcla:
I've just got notification of an OTA update and when I try to install it, TWRP gives me error 7 (i.e. system has been modified).

I haven't done any modifications to the system partition, I've got Magisk v8 plus Xposed and phh's Superuser (all done systemless) so I was wondering what else could possibly cause Error 7.

Phone is a Samsung Galaxy S7.
[Magisk] WarMiguel:
Is possible instaled magisk v8 with superSu?
[Magisk] Didgeridoohan:
I'd say TWRP is the cause. Usually you need stock recovery to install an OTA.

---------- Post added at 06:18 ---------- Previous post was at 06:16 ----------

Yes, read the installation instructions (official Magisk announcement thread).
[Magisk] WarMiguel:
Link plis and how funtion magisk v8 for desactive the root?
[Magisk] smohanv:
What does xSetprop v0. 2 do. I read in one of the threads in this topic. I do not see link for this module. Also I tried Google and could not find it anywhere. Can anyone share if this helps to work with SuperSu as helper. Thanks.

Sent from my EVA-L09
[Magisk] Fild5x:
I managed to install magisk on galaxy a500h. Is this only for debs or I can use it. I installed module viper4andriodFX v2.5 0.5 but when I rechecked version from the app it was still showing v2.4.0.1.
[Magisk] Rhoban:
Viper4Android was never updated past 2.4.0.1.

What you are using is just a modified version, not an actual updated one.
[Magisk] tangcla:
I flashed my stock ROM and have only just realised that when I do that, it encrypts my storage.

With the encrypted storage, I am unable to install Magisk and other modules (systemless Xposed, phh's Superuser) although I have got an external SD card (which TWRP can access).

Is there any way which the modules can be installed, even though the partitions are encrypted?
[Magisk] Artim_96:
First link in first post, learn to read and search for yourself.

And "deactivating" root isn't possible anymore due a while now, you need to use suhide (respectively phh's pendant when using his SuperUser) but for all I know you can't pass SafetyNet at the moment with XPosed installed or on using suhide (not sure if it's working with phh's version)
[Magisk] andrew2432:
System less 2.78 sr1, 2, 3 + root switch + xposed has been reported reported to have luck. Easiest on 6.0 plus. Lollipop is halting my attempts right now

Edit: some need system'ful' xposed ad not the systemless versions
[Magisk] topjohnwu:
Just get back from the exams... time for some goodies to show up :)
[Magisk] ss4rob:
This is why I keep hitting the refresh button - patience is rewarded.
[Magisk] andrew2432:
Make it work!!!! Open source is so user friendly
[Magisk] mada2485:
Guys, please help me.. i can't install magisk whatever way i try. flashing the zip gives me : "! Image mount failed. . . abort

E:Error executing updater binary in zip ... What to do?
[Magisk] SDMU:
Did you completely unroot your phone and restore your boot.img ? SuperSU does give an option to restore boot image while unrooting
[Magisk] topjohnwu:
First bullet: phh's superuser update

Please check [Magisk] [2016.11.9] phh's SuperUser r266 for more info.

Also live in Magisk Manager now!! Directly upgrade phh's superuser within the app

Just a small note, old phh root (r259) will NOT work on Magisk v9 (not released yet). However the new phh root (r266) is backward compatible to v7
[Magisk] shukyuen:
Thanks for hard work, v9 will pass android pay?
[Magisk] Captain_Throwback:
If you mean SafetyNet, then the answer is yes.
[Magisk] shukyuen:
Thank you sir [emoji1]
[Magisk] Donut_Man:
Hello, I have a pixel 7 pro on the march update, planning to update to the April update with the excellent pixel flasher. I downgraded my Magisk to 25206 a couple of weeks ago due to the broken module loading with recent versions. I wanted to know if the module loading is fixed on stable 26100 and if it would be fine to update Magisk, or if I'll have to stay with 25206.
[Magisk] badabing2003:
I still think it is fundamentally two distinct components that work hand in hand, hence why I say it is a packaging / bundling matter.

This was my best attempt at explaining the subtlety which I probably failed.

You know how much respect I have for you, and appreciate all your in-depth contributions, a true asset to XDA, however on this point I would say.

If so many people are tripping on this, then there's something not right about it.
[Magisk] badabing2003:
I believe it is fixed, but I'm staying with 25206 on my main driver until I figure this out, which is turning out to be challenging.

If it ain't broken don't fix it.
[Magisk] pndwal:
By wiki do you mean GitHub Installation Instruction page?...

Both are correct methods; Installation as zip installer from custom recovery is deprecated and affected by many 3rd party custom factors, eg TWRP build used, compatibility issues, bugs, availability of custom recovery for device (especially when little customer support/development occurs) etc... If you have no issues with this on your device so far you can keep installing Magisk this way, but it is really recommended/was designed for legacy (pre SAR) devices and you may experience issues any time you update OS/ROM...

The new method is pretty much universally compatible and avoids the issues of other 3rd party custom solutions... It is also plum necessary on some devices (eg. .zip recovery installation cannot be used for many 2018, 2019 devices that require Magisk in recovery ramdisk).

🤠 PW
[Magisk] Donut_Man:
Thank you, I agree with the if it ain't broken don't fix it. I'll stay with 25206 until I start experiencing problems. It's on my only phone so I don't want any weird issues popping up with the new version.
[Magisk] pndwal:
No disagreement with that or linked explanation... It is two distinct but now more intertwined / synchronised / codependent parts... But the 'packaging / bundling matter' is largely the point; it's essentially why John discarded the Magisk Manager for Magisk App...

Thank you...

The whole change (to single package Magisk/installation) was hard for users to get used to initially, and me included... The blurring of the app / Magisk distinctions hasn't helped, but I think that 'tripping' is inherent in the solution that Magisk and it's App have become...

My technical point was that it's not simply a Manager app anymore... It's a parcel, and what Magisk you get depends on the App installed... (Eg the Channel setting now determines the App to be installed whereas previously it did actually managed the Magisk download).

The non-technical one is simply that it's creator has expunged the references to 'Manager' and whatever we call it, it is now the Magisk App... John ostensibly made this change to allay confusion also (and he surely had the new App/Magisk relationship clear in mind before we as users did)... His reasoning doesn't really seem to hard to grasp either:

Personally I'm happy to use the official parlance and feel it actually reduces confusion also... But hey, it's a free world, modders are non-comformist people by nature and Magisk is the mod for the people! 😜

... And you can only please some of the people some of the time... PW
[Magisk] ctcx:
First of all, thanks very much @pndwal and @zgfg for your complete explanations.

I know I previously sounded kind of desperate and I apologize for that. But now I finally was able to understand how it works.

With this said, I think the "new" Magisk Manager, all bundled in a single apk, is better at least for my case.

If I understand correctly, the overall concept has not actually changed: two components, the core, and the manager/app.

The fact that it's now bundled into one single apk makes it easier to install/update; yet one must still learn how it actually has worked since the beginning.

Just my 2 cents. Thanks again.

And I think I'm as well sticking with 25.2 for the time being...
[Magisk] zgfg:
Yeah. New times, new technologies (and now the older Julia Louis-Dreyfus):

Sorry for OT, but it made my day👻
[Magisk] badabing2003:
That looks a lot more that 9648 batteries
[Magisk] gallegonovato:
Good afternoon:

After upgrading Magisk to version 26.1

I look at the main screen of Magisk and I see that where it says App. In last it says unavailable. And it does not come out install as the previous version. When in the previous version if it came out. I tried in the beta channel and stable.

I attach a screenshot of the screen: https://ibb.co/kh4s3yg

A hug and thanks for your time and help.

Pd: and a question, what would be or what do you use the stub-release.apk for?
[Magisk] bnsmb:
from the docs for Magisk 26.x

:

Is it possible trigger this "re-installation through Magisk app" via an CLI command in a script to complete the installation of Magisk without manual tasks in the Magisk App?

regards

Bernd
[Magisk] badabing2003:
I looked into this and I want to pose this question to the group before I log a ticket, as you know how that goes logging Magisk tickets.

It appears that 26101 or 26.1 is always creating a patch assuming SAR (System as root)

Can any knowledgeable veteran confirm this hypothesis?

1- Create a patch using the UI (I tested this on redfin, Pixel 5, which is NOT SAR)

2- Create a patch using patch_boot.sh, and set the following flags.

export KEEPVERITY=true

export KEEPFORCEENCRYPT=true

export SYSTEM_ROOT=true

Compare the two generated patch files.

The only differences.

RANDOMSEED value (this seems to be new, or at least changing now on each run, but this is not a concern)

generating a patch as SAR is the concern.
[Magisk] pndwal:
... Because it really is SAR; system runs as root except at boot time. 🙃

2SI is actually a form of SAR even in some Google docs despite Google generally calling A10+ LV devices 2SI and differentiating this from SAR...

Actually, 2SI can properly be called "2SI ramdisk SAR" as only initial rootdir is changed back to rootfs; final rootdir remains system... So the first SAR implementation where rootdir is always system can be called "Legacy SAR"....

In any case, Google’s definition in most docs differs from 'Magisk’s definition', (really John's?) per:

https://topjohnwu.github.io/Magisk/boot.html

Of course Magisk needed major refactoring to cope w/ system as rootdir, and, apart from booting, this refactoring is still needed for '2SI ramsisk SAR'... I think that would account for patching as SAR...

Further changes in Magisk were also made to accommodate shared blocks, dynamic partitions and other Treble/Mainline initiatives (architectural changes)...

👀 PW
[Magisk] Lord Sithek:
Is it possible for Magisk to update automatically? :unsure: I just went back home after few hours and to my surprise, Magisk is updated to 26.1 although I could swear I deliberatly stayed on previous stable...

By the way, 26.1 breaks screen rotation on my Samsung Galaxy Tab S5e
[Magisk] pndwal:
Don't think so...

Assume device is A-Only legacy SAR?... Is Magisk in boot or recovery ramdisk? PW
[Magisk] Lord Sithek:
Recovery indeed
[Magisk] pndwal:
... So must have flashed recovery somehow... PW
[Magisk] Lord Sithek:
I started to suspect ghost/random touch on the notification about Magisk update since I don't use lockscreen on my tab
[Magisk] badabing2003:
Thank you again for the excellent reference and your input.

I was indeed going by the Google documentation and I had not seen John's excellent document (mea culpa).

Having said all that, something definitely changed in regards to the flags between 25206 and 26101

While I try to look at Magisk code to identify exactly where and how it is determining which method to apply and why it changed between versions, let me summarize my observations.

Magisk 25206

Creating a patch from UI, and creating a patch through patch_boot.sh with the following flags set to true KEEPVERITY, KEEPFORCEENCRYPT (notice the absence of SYSTEM_ROOT produce binary identical patches. (Incidentally for the life of PF, those were the only two flags used to create a patch in PF)

Same as case 1, but adding the SYSTEM_ROOT flag, still produces binary identical patch, which suggests that either patch_boot process was buggy and enforcing the flag, or was dynamically figuring it out and adding it when creating the patch.

Patching through UI or through patch_boot.sh on multiple runs (attempts) always produces the same exact binary.

Magisk 26101

Creating a patch from UI, and creating a patch through patch_boot.sh with the following flags set to true KEEPVERITY, KEEPFORCEENCRYPT (notice the absence of SYSTEM_ROOT does NOT produce binary identical patches. The differences are in the kernel (major) and in the Ramdisk (Just the RANDOMSEED being different, more about RANDOMSEED further below).

Same as case 1, but adding the SYSTEM_ROOT flag, produces binary identical kernel, and again, Ramdisk differs only by RANDOMSEED.

Patching through UI or through patch_boot.sh on multiple runs always produces a patch whose RANDOMSEED only changes.

RANDOMSEED

Probably there was a good reason to introduce this, which means that no two patches would be identical (have the same SHA1), I kind of liked the older behavior, it was an easy way to check if users were creating a good patch by just comparing SHA1 to others who created the same patch. I suppose this helps in identifying if a patch is being shared or not.

Summary

Based on the above, I would say that either Magisk versions prior to 26 were not behaving exactly as designed.

Case 2 of Magisk 25206, which would generate identical binary with or without the flag SYSTEM_ROOT which would render the flag useless.

Or if the detection of SAR was dynamic in patch_boot process prior to v26, , it is no longer the case in v26 or newer which would be a fix for the above.

Interesting observation: Creating a patch without SYSTEM_ROOT flag, which obviously has a different Kernel generated, still makes the system rooted and functional. Why would that be?