yashsingh1/xdaforums huggingface dataset:
[Magisk] fobtob387:
After installing the update, is it normal for the "Install" buttons to still appear?
[Magisk] wfred:
Same question. I've installed on 3 times and it still says install. Should it?

Edit: never mind. It does the correct version and doesn't say Update like it did before. Don't know why the Install was confusing me. :sneaky:
[Magisk] Eedo:
Yup it's normal buddy.
[Magisk] H4X0R46:
So I'm seeing that Magisk 22 is not a zip? It's an apk only? Why is this different now?
[Magisk] Eedo:
It's normal.
[Magisk] heithered:
You can rename it from apk to zip and flash from recovery. It's in the new installation guide.
[Magisk] H4X0R46:
Oh thanks! Okay that solves any other questions I was gonna ask 😆 Thank you!
[Magisk] amityg:
im also looking for twrp install .zip of v22 magisk...it has been a few years since i read the installations guide
[Magisk] fobtob387:
Please read the installation guide: https://topjohnwu.github.io/Magisk/install.html#custom-recovery

"

Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.

Flash the zip just like any other ordinary flashable zip.

"
[Magisk] amityg:
yes thank you...
[Magisk] Icebullet99:
Ah yes, sorry for being vague.

I did not intend to imply that the method generally does not work.

This is actually the first time that I tried that method, since there's a new installation guide and only now that I know it is the recommended one. I have always been flashing the zip in TWRP.

Anyway, I read the wiki carefully and tried not to make a mistake, but to no avail.
[Magisk] rafu997:
Looks like there might be some issue with OnePlust 6t and 22 version. It hard bricked my phone. I did unhide manager first and then tried to flash magisk (direct) and got unsupported image error. After reboot it went straight to fastboot mode and I had to flash whole rom from there. I'm not the only one, I saw someone in 6t forum reported the same. So just a warning
[Magisk] z1022:
how can I extract the boot.img from phone which patched by Magisk ?

Thanks
[Magisk] martyfender:
I had the same issue on my Onn 8, Android 9 tablets until I u-hid Magisk Manager, then the boot.img patched fine. However, when I once again tried to hide MM after flashing the patched boot.img and rebooting, I received a new, never before seen error dialog, that I had lost root, which was true.
[Magisk] altwu:
it looks other oneplus phones are having trouble with magisk 22. @Aveon experienced problems with a oneplus 3. i have a oneplus 7 pro and ran into issues. i upgraded magisk manager to v22 and then tried to update magisk to v22. when i tapped on "let's go," nothing happened. i rebooted and ended up in the bootloader. multiple reboot attempts kept sending me to the bootloader. i flashed the stock boot image and was able to reboot. i uninstalled magisk and then reinstalled 21.4 by flashing the zip in twrp. i'm going to stick with 21.4 and wait for the next magisk update before i try updating again.

as always, thanks @topjohnwu for all your work!
[Magisk] Xyphoseos:
Same as you but with a Samsung Galaxy S10, hopefully I managed with odin and my twrp backup. It seems that I can't update for now or it will brick
[Magisk] z1022:
Download the Magisk APK

Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.

Flash the zip just like any other ordinary flashable zip.

Check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.
[Magisk] dl200010:
I have the OnePlus 6T, and I unhide manager first. I flashed direct and had no issues. I do have TWRP and ElementalX installed. No issues. I have rebooted a few times.
[Magisk] dl200010:
The question I have is when updating the ROM from OTA, full of course, will I need to uninstall Magisk like before?
[Magisk] ineedroot69:
somebody help me i can't update my magisk to version 22.0

https://xdaforums.com/t/magisk-v22-0-update-confusion.4238355/
[Magisk] me_droid:
Well, decided to uninstall manager from the app tray then reinstalled 8.0.7 and that seems to have fixed it for me. Still not sure why this happened. Wild guess it had something to do with the "hide magisk manager" utility. After reinstall my previous settings were intact except for that. Still don't understand why the process of automatically downloading the update triggered this pop up without my clicking on the update button.
[Magisk] ineedroot69:
what? that look like alot of work so that i can update my Magisk to 22.0 . Is flashing stock boot.img safe while you are rooted?
[Magisk] kiwigi:
I've looked for the new installation manual though haven't seen on GitHub what you are quoting. 🤓🤓
[Magisk] BrikHaus:
Pixel 2XL user here. I was having issues after the Magisk Manager had an 'Update' (my Magisk was hidden...)

Update failed. Subsequent patching methods (Magisk 22 patching stock boot img) failed.

Even after flashing fresh OS image...

Ended up fastbooting to TWRP, Flashing TWRP to recovery, Then flashing Magisk22 as a .zip. (ie pre 10 method)

So far seems to have worked. Magisk 22 installed.

FYI only, take with a grain of salt.
[Magisk] BrikHaus:
Installation

The Magic Mask for Android

topjohnwu.github.io
[Magisk] zgfg:
Of course. Please follow the conversation, what others ask and what is answered/commented, the same was asked and answered (how, why) few weeks ago

It is also possible to search through the thread from the Web (not from XDA app)
[Magisk] zgfg:
Please read the Changelog. Exactly that is described there.

And the Changelog was also posted in this thread
[Magisk] zgfg:
A question to be searched/consulted/asked through your device forum - how your firmwares are distributed, how to extract, etc

Usually it is a zip file that can be simply unzipped. For Samsung a little bit more complicated but even discribed in Magisk docs on Github. For Huawei one must use Hiawei Update Extractor app, etc
[Magisk] Oliie23:
Can you please give more instructions on how to get the stock boot.img and flash it?
[Magisk] cognitivedissonance:
Same exact issue. Pixel 2XL Android 9.0. Any solution been figured out?
[Magisk] Oliie23:
Okay I need help now. I'm on OnePlus 6 and I also got the fastboot bootloop. I've found the stock boot.img online and installed it. Next I booted from adb into the TWRP 3.5.0 recovery and installed a regular bluspark recovery via ZIP. I did the usual "reboot into recovery" but now it just doesn't boot and hangs up at blu_spark logo. Regular booting up doesn't work either - just hangs up at the "This booloader is unlocked" message. I don't know what else can I do.

EDIT:

Flashing boot.img lets me boot into TWRP from adb at least. Should I just flash android now?
[Magisk] c3k:
Same here. Samsung S10. Old Magisk was hidden.

I click the update notification, now:

- old Magisk manager won't open ("update to full version..." popup that does nothing)

- installed new Magisk APK but Magisk not detected and no direct install method

- installed old Magisk manager APK same results

Should I restore my Magisk Manager Titanium backup?
[Magisk] cognitivedissonance:
Alright so I've tried uninstalling the Magisk app, reinstalling it, wiping the app data, rebooting, installing again and so on. The Magisk app with run again when I do that stuff, but when I try to hide it, it clocks and clocks and creates another Manager app without the name I've specified and without an icon. The one with the Magisk logo is also still showing too, so then I'm seeing two apps.
[Magisk] akxak:
Issues with a OP 7 Pro here, force close of Magisk Manager after update to the latest version.
[Magisk] cognitivedissonance:
For the love of.... nothing is fixing this.

1. Turned on airplane mode

2. Force closed Magisk app, wiped data, uninstalled

3. Booted to bootloader, flashed factory image w/ -w flag removed to avoid wiping data

4. Booted system, noticed somehow there was still a Magisk app that had re-appeared. Repeated step 2.

5. Booted to TWRP image and flashed TWRP

6. Booted system, then back to the now-flashed TWRP and flashed the Magisk 21.4 zip

7. Booted system, and the Magisk app was back - repeated step 2

8. Installed Magisk Manager 8.0.7 apk, opened it and checked Magisk Hide apps -- all the ones I previously had checked were still there.

Whatever the hell happened broke the hell out of Magisk Manager, and I have had no luck trying to find where it's kept with a file manager. If I did, I would delete it all and just start over, but at this point I cannot afford to do a full data-delete-factory-reset, so I'm screwed.

If anyone knows where the heck Magisk stashes it's data, please let me know so I can manually delete it all and install it fresh. I thought this stuff wasn't supposed to happen on the "Stable" channel...
[Magisk] zgfg:
See /data/adb, there you can find the database magisk.db - if you delete you will loose Magisk hide and other settings
[Magisk] Oliie23:
have you tried the magisk uninstall zip?
[Magisk] cognitivedissonance:
I just added that step. While it did seem to prevent Magisk Manager from reappearing, once I reflashed Magisk in TWRP, and reinstalled Magisk Manager, Hiding Magisk Manager still doesn't work. It just clocks forever and creates another app called Magisk in addition to Magisk Manager.
[Magisk] Oliie23:
I hate bumping my posts but would someone be so kind to help? I'm kind of desperate since I have no working phone right now. I just can't figure out how to make it boot.
[Magisk] z1022:
Installation

The Magic Mask for Android

topjohnwu.github.io
[Magisk] cyril'u:
Hello

(my phone Galaxy S7, G930F, Custom Rom Pie, Migrated from Magisk 21.4/ Magisk Manager 8.0.7)

In my case, automatic update through Magisk Manager was fine : I did 1. APP then 2. Magisk

(One comment : Magisk update log screen was hidden (another screen))

But when I launch magisk app now I have this message. Neverteheless root seems to run fine.

I didn't have it with magisk manager before...

Do you have an idea ?

Thanks
[Magisk] ineedroot69:
Magisk v22.0 update destroy my Phone :cry::cry:
[Magisk] pollazht:
I installed magisk app through the popup notification without un-hiding magisk first and as a result I couldn't launch the app (root was functional though).

I followed the following steps to solve it:

1) Uninstalled the newest app

2) Installed previous magisk manager ( 8.0.7) from github

3) Installed newest magisk app from inside manager 8.0.7

(Redmi Note 4, Resurrection remix, Nougat)
[Magisk] ineedroot69:
what? you need to unhide Magisk first? thats provably the reason why it destroy my device :oops:
[Magisk] Oliie23:
I un-hid it and it still got messed up
[Magisk] c3k:
works for me too

thank you
[Magisk] HippoMan:
I'm running on the same device -- OP 7 Pro (GM-1917) 12/256 -- and I have no problem with 22.0. But I'm running OOS 10.3.8, while in your signature, you have posted that you're on OOS 10.0.10.GM21BA. I'm wondering if your problem is related to some sort of interaction between Magisk 22.0 and OOS 10.0.10.
[Magisk] rafu997:
OP6T. I've flashed clean newset stock rom (full wipe) and everything worked until I flashed Magisk v22 (from TWRP). After Magisk WiFi won't turn on and I cannot make any phone calls. Uninstalling magisk and flashing rom again fixes that. I tried Magisk v22 again but same issue. I guess I need to try older version.

UPDATE!

Wifi and phone calls issues were caused by TWRP 3.5. I used 3.4 and now it works fine.
[Magisk] Oliie23:
Did you flash a full stock rom because it bootlooped?
[Magisk] rafu997:
Yeah, I was stuck in fastboot mode after trying to update magisk to v22. I think it would also work to just flash stock boot.img.
[Magisk] SirElectro:
Since I updated Magisk Manger via update notification on my MI 10 without seeing the message disbale Magisk Hide first, I did a full uninstall via the Magisk Manager App v22 without updating my magisk 21.4 installation. So far no issue, phone works and is now unrooted. Does anybody know how to install Magisk 21.4 via Magisk Manager v8.0.7? It only shows me v22.0 now.
[Magisk] akxak:
It's 10.0.11 but that's the European equivalent.

I tried it again, same result... I created a logcat and amend that later here.

Later...

02-24 12:09:57.489 6474 6474 E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate application com.Q3AHqaD.X6Ko24Rr.core.App: java.lang.ClassNotFoundException: Didn't find class "com.Q3AHqaD.X6Ko24Rr.core.App" on path: DexPathList[[zip file "/data/app/com.Q3AHqaD.X6Ko24Rr-Tiiovb9jqAo9-cLL4I6xQA==/base.apk"],nativeLibraryDirectories=[/data/app/com.Q3AHqaD.X6Ko24Rr-Tiiovb9jqAo9-cLL4I6xQA==/lib/arm64, /data/app/com.Q3AHqaD.X6Ko24Rr-Tiiovb9jqAo9-cLL4I6xQA==/base.apk!/lib/arm64-v8a, /system/lib64, /system/product/lib64]]
[Magisk] Oliie23:
So if I get it correctly - you got into a recovery via ADB and just flashed the ROM from there?
[Magisk] ineedroot69:
they decided merge Magisk Manager and Magisk in just one app now and it's called Magisk read the changelog
[Magisk] Frank_071:
Okay... something is terribly wrong with Magisk (Manager) 22.0 - at least for some users. I unhid MM and updated it. That went without problems. Then I wanted to update Magisk itself from 20.x to 22.0. So I choose 'Update', 'Direct Install' and pressed the blue "Let's go" (well the Dutch translation). Nothing happened. So I pressed it again. Nothing happened. I went back into the main screen, forward to update, chose Direct install and pressed it again. Nothing happened. At some point when returning to the main screen I saw a log that read something like "Extracting boot image" followed by "Unrecognised boot image". Uh oh...

So I went into this forum, did not really find what I was looking for, but for some hints. One user reported seeing a number of concurrent flashing threads. I didn't see that (didn't look) but what I did noticed was that when going back to the main screen I had to pass different log screens all showing errors. Uh oh...

Without wasting too much time I took the latest full OTA (which fortunately I still had), extracted the boot.img from it (this is a OnePlus 6 and there is some great payload-extraction tool). I then used the Magisk Manager to patch that boot.img - that was succesful without hassle. Got the patched image from my device, booted the device and - as expected - it went straight into the bootloader. No chance to boot the device anymore. So then I flashed to patched boot.img and, hurray, the phone booted with root restored.

The adventure didn't end there, because I had to update the phone. So I did what I normally do (I do not use TWRP): update the phone with full OTA, launched Magisk Manager and chose 'installation in inactive slot'. It failed the same way the 'direct install' failed: nothing was shown and after a few tries I got that 'unrecognised again'. So I retrieved the boot.img from the new OTA, patched it, rebooted in the bootloader, checked if the slot changed (it had), flashed the patched boot.img from the OTA and, hurray again, it worked.

So there are three problems currently. The first being that the flash thread is not shown (and blocking what one is doing). The second being that multiple flash threads are allowed to run in parallel, effectively destroying the partition. The last thing is not certain, but I have the impression that the first flash doesn't really succeed at all.

If you are in doubt and you need to update Magisk, then to spare your nerves you should make sure that you have an unpatched boot.img from stock or OTA and that you make sure you properly patch that and have it at the ready on your laptop so you can adb/fastboot the image yourself.
[Magisk] rafu997:
Actually I couldn't boot into recovery. Only fastboot was working so I flashed all partitions using fastboot zip stock rom but I do not recommend that as you will get everything wiped. Now I would try flashing just stock boot.img in fastboot and then boot into recovery to flash rom. This way I wouldn't wipe everything...
[Magisk] SirElectro:
This does not answer my question at all. I want to install version 21.4 again via the old manager app , since 22 seems to cause problems on many devices.
[Magisk] Oliie23:
Is it possible to flash ZIPs from Fastboot?
[Magisk] Oblias:
I have a OP6T and have been looking for such a tool. Would you mind pointing me in the right direction to get that tool, because all my custom roms just have a payload.bin file inside the rom.zip. A name of the tool, and even a link would be excellent!! TIA
[Magisk] Didgeridoohan:
I saw this exact same behaviour yesterday, when updating on my OP3T (maybe it was my and @pndwal's posts you saw on this?), and on that device (and likely on most devices) it's easy to fix: Just boot into TWRP (no need to install), flash the stock boot image and then the Magisk v22.0 zip (renamed from the apk). If there's no TWRP, your way of patching and flashing the image manually also works.

But, I haven't Managed to recreate it yet (haven't had much time for testing though). Don't know why the flash thread (as you call it) wouldn't show when pressing "Let's go", but the parallel installations should hopefully already be fixed:

https://github.com/topjohnwu/Magisk/commit/803982a271c311231a05c08c96f498fe6e4246c0

Hopefully it was just this issue that has been causing all these non-booting devices stuck in bootloader (or similar).
[Magisk] rafu997:
Yep:

https://xdaforums.com/t/rom-stock-fastboot-op6t-stock-fastboot-roms-for-oneplus-6t.3862516/
[Magisk] ineedroot69:
look like everyone who tried updating Magisk from 21.4 to 22.0 experience can't access recovery mode?? :oops::oops: geez its quite scary experience
[Magisk] -earth-:
#oneplus

Hello, i use a OnePlus 6.

Have problems too.

I rename magisk from .apk to .zip, install it in twrp, but after reboot, root is gone.

App under Os is installed, but the is no Magisk installed.
[Magisk] ineedroot69:
you could also flash the partition that got corrupted one by one like this

fastboot flash boot C:\boot.img
fastboot flash recovery C:\recovery.img
fastboot flash vendor C:\vendor.img
fastboot flash system C:\system.img
[Magisk] Oliie23:
I could, but I can't figure out how to obtain these files yet
[Magisk] Lord Sithek:
Naah, just people with troubles posting here. On my three devices update without any problem 😁
[Magisk] Oliie23:
The new update seems to not play nice with OnePlus phones from what I can tell
[Magisk] Frank_071:
Try googling for "oneplus payload dumper". Not sure if I am allowed to post links: https://androidfilehost.com/?w=profile&uid=890129502657599833

Yes it is, if you are prepared. But if you are not and, for instance, you have all OTA's on your device (which is pretty normal if you use the OnePlus Updater tool) and boot unknowingly, then you can loose your cool... My post was meant more or less to avoid that ;-)

Well... I have managed, because it went wrong in both the Direct Install and (after restarting the whole lot and doing that flashing) the parallel install.

It is, under all circumstances, interesting to know why it works for some and fails for others...
[Magisk] zigbye82:
hey, i just updated to 22.0 now when i open magisk i get a warning that says - abnormal state running this app as system app is not supported, please revert the app to a user app.

The thing is magisk came built-in in my rom. Should i revert older version?

Is there a flashable zip for the new version? - ok rename new version apk file to zip. gonna try flashing, maybe it would fix my problem.

No luck, same error but it seems to be working though.

Edit-

my rom has been abandoned for some time now.

So i booted in recovery and deleted the magisk folder from system/app. i reflash magisk 22.0 and booted. the error is gone now and magisk "seems" to be working as normal. Could it be that simple or do you think ill encounter problems later on?
[Magisk] kouzelnik3:
If only people could read requirements and that highlighted sentences when prompted to update. Everything is written in that update notes, called changelog...
[Magisk] guhvanoh:
I'm on Poco F1 so YMMV. Before installing ROMs, Magisk etc I download the zips, apks etc to my PC. Next

I transfer them to the external sdcard in my Poco using adb. This way I always have a copy and a backup.

I use TWRP 3.4.0something, I've 3.5.something but 3.4.0something works... So if I was you and in your predicament I would flash the uninstaller, then flash the v21.4 zip.

Having said that, most likely none of this is going to help you...
[Magisk] cognitivedissonance:
What in the world is that stub apk? Are we supposed to download and install that too?
[Magisk] rwio:
Seems many have problems with the latest Magisk update... as do I.

I have an older rooted Moto X Force with android 7, TWRP and Magisk. Installed the latest Magisk App 22.0 which seemed to work, but updating Magisk itself failed. Did the mistake and rebooted my phone, and now my bootloader seems broken. Phone starts into Fastboot mode and I get the message:

Invalid boot image header!

Error: failed to load kernel!

I can still enter recovery mode and TWRP, so I made a backup of everything and also saved dmesg.log and recovery.log. But I'm kind of at a loss what to do next. I don't wan't to mess with things and risk wiping everything. Any help would be much appreciated!
[Magisk] Didgeridoohan:
It's been said many times before, but it never hurts to say it again...

If someone tinkers with their device like we do here and aren't prepared for complete and utter failure, their data will be lost sooner or later (often sooner)...
[Magisk] akxak:
I got this message only AFTER naming Magisk Manager back to original. Before no popup appeared so I was not aware of that, but saw it here by chance... so pls don't blame people.
[Magisk] zgfg:
It will ask you to automatically download/install if you go for hiding/restoring Magisk apk - don't install manually
[Magisk] Didgeridoohan:
If the Magisk app came preinstalled as a system app on your ROM you need to have a serious talk with that ROM creator... That's always a bad idea. Try removing it from /system and start over.
[Magisk] Didgeridoohan:
Check my post here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84550015
[Magisk] pndwal:
This involves pasting a link to a hosted json file containing the proper file links for legacy build into Custom Channel in Magisk Manager. Method here:

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

Nb, you may be able to paste this directly into your current manager, but, to avoid problems due to recent changes and to get access to Magisk (mask) via custom channel (only available in pre 22.0 public releases) you'll need to hit 'install App' button to downgrade Manager (Should now be showing legacy Manager as 'latest' for channel set) before doing the same for Magisk.

Nb 2, The method linked above works for archived public (Stable/Beta) builds as these contain preset links set to the location of the specific build files, but it's more tricky for a debug (Canary) build as the corresponding json file is set to the location of the latest build, not the specific archived build. (This is ikely because John Wu is only interested in receiving debug logs from latest Canary, so he has never seen a need to make jsons build specific because older builds are effectively redundant as they no longer achieve their intended purpose). To patch images using old Canary build, a user must therefore download the associated json, edit it's link to the Canary Magisk file at the very least, then rehost the file on a server before it will properly point to his selected build. Cases where archived debug Canary builds will be of more use than an older public release will be rare in any case. PW
[Magisk] the00guy:
I just went through this process myself. Note that if you're on a Mac, Mac has native python that you can't really mess with, so install the latest version from the website and reference that via terminal instead, e.g. command becomes python3.9 instead of python.