yashsingh1/xdaforums huggingface dataset:
[Magisk] ineedroot69:
read the changelog which can be found here https://topjohnwu.github.io/Magisk/releases/22000.html
[Magisk] der-seemann:
where can i find the latest magisk.zip for the samsung a530f?
[Magisk] ieio:
I'm sorry to report that Magisk v22.0 (22000 build) isn't able to correctly patch vbmeta img leading to a boot loop into download mode

SM-A307FN

ITV_A307FNXXU2BTG1

people online were able for sure to correctly root this model with previous releases of magisk
[Magisk] pndwal:
I had same corrupted boot.img thru update (froze during direct update, looped to fastboot after I restarted phone) fixed by fastboot flashing working boot image previously patched w/ earlier Magisk.

Next, I tried patching boot image, and gave up as Magisk app 'froze' again, and nothing happened.

The next day, I tried to reproduce issue with Logcat Reader running, first by patching image only again, and this time it patched fine w/ dialogue ->> 'all done', so (happily) I couldn't reproduce issue.

I may have restarted phone again, but otherwise did nothing differently, so seems problem is a fickle one.

I'd extract boot image from currently used ROM package (assuming ramdisk = no (in Magisk app) for your device), ensure you unhid Manager and have no hidden Manager app / stub left over if you previously hid it, reinstall Magisk 22.0 app (with or without root), then see if patching boot image dialogue completes for you. If so, fastboot flash should work fine!

If not, I'd keep 21.4, at least till next Canary fixes... PW
[Magisk] asripath:
After reading all adventurous stories with trepidation

I ventured by

- Backing up (Swift/Migrate)

- Extracting & Patching boot image (as a backup)

Magisk Manager was not hidden.

Well, it went smoothly without any issues.

Upgraded Magisk Manager to now App and

Magisk to now Magisk (from 21.4 -> 22)

Maybe it would be better if

MagiskHide and

Hide Magisk Manager

changed to

Stealth/Camouflage Magisk and

MagiskHide
[Magisk] TormentedHeart:
I honestly prefer magisk as a system app. Guess i wont be updating magisk for a while
[Magisk] pndwal:
It's now Magisk-v22.0.apk, not zip unless renamed.

It's on Magisk main GitHub page as always. 💪

Access from Magisk app main page (GitHub 'cat' symbol), or check OP (ALWAYS check OP) here, click Announcement Thread, and wallah!... first link is to Magisk main page on GitHub! PW
[Magisk] Zoki88:
Yep, i was using that one, and it made apps recognise root(btw i'm using mcdonald's app for testing hiding root from apps which detects it, as i was suprised that trivial app for some reason is that complexed and made to search for anything like bank apps, even for busybox as i now found out), so i hope magisk module busybox will hide it better, now will wipe phone and put everything again, and test it with module xD
[Magisk] klv22071957:
SuperSu+pro версия,не запустится Magisk.Пишет ошибка при загрузки файла,любого.SuperSu затребовал обновления что и сделал,потом сам перезагрузил.сторонний канал невкючать написано.загружать файлы по другим каналам.
[Magisk] ineedroot69:
Если у вас установлен magisk, вам больше не нужен SuperSu + pro. вы можете управлять рутированным приложением внутри magisk
[Magisk] Didgeridoohan:
Guys.... While you are allowed to post in other languages on XDA, the post also need to be translated to English (see forum rule #4).
[Magisk] Oliie23:
Would anyone be so kind to point me to a procedure to install the newest Magisk? The way I always did it was to install it from TWRP custom recovery after a ROM update, and then every subsequent one I'd install via the app. However this time app update has failed and left me with a broken boot.img so I had to reflash the stock boot.img and then custom recovery.

So again - how do I install the newest Magisk without getting any corruption? OnePlus 6 here.

EDIT: Okay nevermind. It worked via the app now. So turns out the main issue as to why it failed the first time was probably the MagiskHide being enabled (which I thought I disabled, but I just mistook it for hiding the app - NOT THE SAME THING!).
[Magisk] pndwal:
Thats a useful option I haven't considered for some time!

Been checking on flashing boot.emmc.win and there's some confusion, but generally people are reporting this can simply be renamed boot.img and flashed. (system.ext4.win etc may need to be unpacked and repacked due to compression/encryption).

I haven't flashed yet, but can confirm Magisk recognises my backup renamed boot.img as 'Magisk patched boot image', and re-patches this fine!

Thanks for the useful heads-up. 👍
[Magisk] Zoki88:
After wipe out, putting twrp and magisk, now play store isn't working for some reason to download or update any app, neither play store itself doesn't wana update, what to do?

Edit: nvm, after more times rebooting, now it works xD
[Magisk] cispinox:
Followed the guide on github on patching the recovery . It kinda works but the system it's very unresponsive,crash and just give me random bugs as wifi not working. Plus now you need to boot each time with power+ volume up .

I think i will just stick to 21.4 for the meantime , this update gave me more problems than pros.
[Magisk] Fil76:
Well maybe i Lost something in translation or i'm too old

I don't get what i do wrong

Twrp 3.40

Magisk Hide disabled

Magisk app updated to 22

Setup is :

If you already have Magisk installed, it is strongly recommended to upgrade directly via the Magisk app using its “Direct Install” method. The following tutorial is only for the initial installation.

I do it and Lost everything because direct install give me error

Isn't there a solution to update via twrp ?
[Magisk] Fil76:
i followed the guide and direct install give me error = result boot.img and recovery lost

The guide say:

If you already have Magisk installed, it is strongly recommended to upgrade directly via the Magisk app using its “Direct Install” method.

(maybe i'm too newbie but also sideload of twrp didn't work ..lost twrp every restart)

Only tool

BUT what about if

Uninstall Magisk manager

Uninstall Magisk via twrp

Restart to OS

Install Magisk app 22

?
[Magisk] Fil76:
Yes i will wait it's better cause i followed the guide and boom :D
[Magisk] Toonlinkmaster25:
Hi, I just updated my phone to the latest magisk from the normal setup to the app only. All I did was update the app then the manager, rebooted, installed the app again because it showed "install" next to both of them. I then cleared my app data for magisk. That didn't really change anything so I thought I'd reboot again but now I'm caught in a boot loop and can't even get into recovery (TWRP) anymore. Adb won't show but fastboot still works so I'm assuming USB debugging is broken. I tried flashing a fresh boot image like suggested but that didn't help. Could someone help? I really don't want to lose data.

Update: So I was able to Fastboot the current image I was on then I had a working system so I could boot into TWRP by fastboot boot TWRP.img. When I opened TWRP it acted as if my phone was wiped but I installed my ROM and booted up. After the longer boot sequence everything appeared as normal with all my data and settings intact but Magisk only had the App installed. I then booted back into TWRP and flashed the latest Magisk after turning it into Uninstall.zip. After it booted I renamed that file to Magisk.apk and after the install everything is right. I'm getting all necessary backups in case I need to just wipe my phone for better performance and to fix potential crashes (none yet, fingers crossed).

Just wanted to help someone out who ran into the same issue as me. Btw people mentioned that TWRP doesn't play well with Google phones so that's why I booted into it from Fastboot instead of installing.

Device: Pixel 2XL

Version: Android 10
[Magisk] Zoki88:
I succeed to have root, busybox as module for magisk and apps don't recognise rooted device, but now i have 2 new problems, which maybe aren't for this thread(and aren't that important i think), and i'm sorry for that, but maybe someone here had same issues. 1st is about play protect certification, which says in play store that isn't certified, idk if that's important to fix or not, will that causing some new problems in future? And 2nd problem is just this pop up message when i click any apk file to install, if that can stop popping up every time? I checked and was enabled unknown sources apps thing if that helps. If there isn't solution, no need to fix, but would prefer to not have that message every time i click apk files. Thanks in advance!
[Magisk] DiamondJohn:
But why?

For starters, there are two parts to Magisk. Magisk itself is baked into your boot image, not an app. So, you must be talking about you the manager app. This app simply copnfigures things (although I think it is also responsible for popping up root requests). If you / when you update a system app, the system installation is left and a new nstallation goes to your data (ie non system). So, after any update, you are basically running a non system app that is flagged as being a system app.

As for not installing for a while, I dont think it will ever go back, especially now that android is moving to read-only system partitions.
[Magisk] pndwal:
Problem 1: Do you have full SafetyNet pass in Magisk app? (Assume you have enabled MagiskHide in setting.) If not, you likely need new Universal SafetyNet Fix module to get ctsProfile pass. If you do, just clear PlayStore Data and Google Play Services cache, toggle MagiskHide off and on again in Magisk app Settings (re-adds Google Play Services to MagiskHide list), reboot and check certification.

Problem 2: Don't know. Likely not - may be an LG stock thing... PW
[Magisk] Shady88:
If i'm changing the rom (from example, from lineageos to resurrection remix), can i patch the boot image of the new system in magisk BEFORE changing the rom (so patching it on a different rom), or do i necessarily need to install app on new system and flash the patched image on pc?
[Magisk] ineedroot69:
do a complete uninstall of magisk on lineageos (safe path no bootloop)

then install resurrection remix

then install magisk and flash resurrection remix boot.img patched via magisk
[Magisk] VelvetB:
I'm having problems trying to upgrade to 22, SAR on unlocked moto E6 which ran like a champ on previous versions. I figure whatever's the issue will be corrected by topjohnwu so restored to stock and installed MagiskManager-v8.0.7, but it won't let me install Magisk-v21.4, only allows upgrade to 22. Any easy way to install 21.4?
[Magisk] ineedroot69:
download it on GitHub?
[Magisk] me_droid:
Well, I never attempted to update to v22. However, the update downloaded on it's own without my intervention. Initially after that I couldn't open manager without a nag appearing to please download update and complete the install. Resolved that by uninstalling from the app drawer and reinstalling 8.0.7. Everything works fine now except that I can't hide magisk anymore. It stalls so I have to force close it. Then I see in app drawer manager with the icon it uses for the hidden app but still named magisk. Clicking it produces an error and won't open. I long press it to uninstall manager but then the actual icon re-appears and I can run manager again but not hide it. How can just downloading the update cause all this? Forgive my ignorance if this is something simple. But I know I never chose to update and magisk reports I'm still on previous versions.
[Magisk] pndwal:
Thats a new one... Never heard of that happening... You must have a Magic auto-update!

Well, a warning to restore unhidden App before updating appears right at top of Release Notes that pop up when one selects update Manager/App! Not sure what happened in your case... Explained in text further down:

I've also posted Release Notes here (Changelog in post above):

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

To fix, simply identify any Hidden Manager/App or stub that still exists and uninstall, then reinstall Manager/App you choose. Magisk setup (modules, hide list, root permissions etc) will remain. PW
[Magisk] VelvetB:
I have, when I open manager 8.07 only option is to update to 22, can't do anythig but. I usually wait to update all apps, as me_droid mentioned, yesterday with Manager 8.07 starting perfectly, it was locked. Only option was to downloaded update. it would be wonderful if topjohnwu would allow a previous version to be installed. I'm incapable of building apps
[Magisk] pndwal:
Previously you needed to set custom channel, but new releases incl. 21402 / public 22.0 are stand-alone. (Simply turn off mobile data or network connection, and Manager / App should allow update to its corresponding Magisk root version.)

For 21.4, you still need to set custom channel. Method:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84550467 PW
[Magisk] ineedroot69:
all previous version can still be found on github

https://github.com/topjohnwu/Magisk/releases/tag/manager-v8.0.7 Magisk Manager 8.0.7

https://github.com/topjohnwu/Magisk/releases/tag/v21.4 Magisk 21.4

nvm they are not stand alone?
[Magisk] pndwal:
Sorry, corrected info in my post above... See there for Custom Channel use. 👍 PW
[Magisk] pndwal:
John needs help!...

Any Sammy Experts?:

PW
[Magisk] ApoMiro:
so i have an old android there are many app data and it have lived for more than a years than i want to install magisk through fastboot with a patched boot.img that taken from that android zip rom, can it work? or i can only patch it after fresh install? will it cause problem if i flash the patched boot.img in not fresh install rom? thanks
[Magisk] pndwal:
Should work fine, but backup just in case!

If using latest 22.0 / 22001, note that many have had 'corrupt system' issues (meaning corrupted boot.img actually.

Symptoms are direct or patching methods seem to freeze w/ no progress dialogue. After reboot (direct Installation) or patched image flash, device won't boot system and defaults to fastboot mode.

To avoid this, avoid direct update. Test safety by patching image. If you get freeze / no "all done", don't flash any resulting image. PW
[Magisk] mr nick:
I have an issue I can't seem to resolve so hoping someone can help?

I recently upgraded to v22 but when I rebooted I went into a bootloop. After a bit of reading I saw this was a fairly common occurrence so decided to downgrade to 21.4 which had been working perfectly.

I reflashed a clean boot image, re-installed 21.4 and installed the corresponding manager, rebooted and all OK. But whenever I toggle ANY setting in the manager and then reboot I go into a bootloop. I can break the loop by holding VOL- during boot and then the system boots but I always find that USB debugging is disabled and all installed modules have disappeared.

If I reboot again, it reboots OK, USB debugging is enabled and all modules are visible (but disabled). If I enable any module or toggle any setting and reboot I go back into a bootloop and the whole thing goes around like this forever.

I have tried removing Magisk completely and then starting again from scratch but no matter what I do I can't get this cycle of behaviour to stop.

Any ideas what's going on?
[Magisk] ineedroot69:
1. i would recommend to uninstall all the modules while you troubleshoot this issue

2. if you press VOL- what made you decide to press it does it show anything on screen?
[Magisk] ApoMiro:
found, the answer thanks anyway
[Magisk] J.Michael:
@mr nick You say you tried removing Magisk completely. Does this include checking every app in drawer to see if there are other copies of Magisk? (Possibly with different names.)
[Magisk] J.Michael:
What is important is that the image you patch be the one currently running.

What was the answer you found?
[Magisk] RealYoti:
del
[Magisk] Didgeridoohan:
No, it isn't actually....

https://topjohnwu.github.io/Magisk/install.html#uninstallation
[Magisk] Shady88:
I know that. I was asking if i necessarly need to patch the image on the system i'm supposed to use it with or if i can do it into another system. Cause if i can do it on another system, then when i clean flash another rom i can install patched boot image directly from twrp
[Magisk] mr nick:
Definitely removed all instances - checked and double checked. When I rename it, I always use the same name so I'm certain that it is definitely removed.

I have removed all modules but I find that the behaviour still happens if I toggle the Magiskhide option in settings and then reboot. Doesn't seem to be restricted to any one thing, just changing and setting and then rebooting.

As for the VOL-, I found this by trial and error just trying any keypress at various times to try and get into fastboot or recovery. If I press and hold VOL- just after the phone vibrates it boots but I find USB debugging is turned off and any installed modules have disappeared.
[Magisk] VelvetB:
Just what I needed! Thank you very much! After a virgin install of 21.4, updated to 22 without issue. Must have had something hidden before. I suggest to anyone else having problems that the 1st thing to do is a clean Manager/Magisk install of your previous version and try again.
[Magisk] Ghisy:
Hey guys,

I'm having a brain fart here: I just updated Magisk to v22 (patching the boot.img on a Pixel 4 XL). Now I've lost my custom kernel (ElementalX).

If I flash the kernel again, I'm losing root. Can anyone remind me how to have both root and a custom kernel please? (I know there's a flash order but forgot...)

Thanks!

Edit: Magisk needs to be flashed first! Then custom kernel. I tried again and it worked, phew!
[Magisk] pndwal:
Isn't custom kernel a boot image?... Could have just patched that! 🙃 PW

Edit: I see it's a zip installer.

FWIW, you could also flash custom kernel, do TWRP backup of boot image, rename resulting boot.emmc.win file to boot.img and patch that.

Since you've already got root, if you want to save your Magisk-patched boot image (to easily restore boot with Magisk 22.0 if needed using TWRP flash or Fastboot), you could do TWRP backup of current boot image, rename resulting boot.emmc.win file to Magisk 22Patchedboot.img and keep it for emergencies. PW
[Magisk] Sizzlechest:
Just a FYI, I have a Moto e4 Plus and had the issue described where the only option on boot was the bootloader after upgrading to 21.4. Thankfully I was able to find an original boot image to get it to work again. Some people are claiming success with 21.4, but that was the first one to cause the issue for me. 20.4 is working fine.
[Magisk] ineedroot69:
On my phone holding Vol- while it's booting actually goes to Safe Mode perhaps you found how to put your phone on Safe Mode by accident 😂

Here's what topjohnwu said "

https://twitter.com/i/web/status/1262714547950899202

"

Then this only means if you can break your bootloop by entering Safe Mode an applications or Module is causing your issue
[Magisk] mr nick:
I reckon that's exactly what I've done. Safe mode would explain the modules not being available when I look for them.

Looking at the post above that mentions 20.4 working, if I remember correctly, that was the version I was in prior to upgrading to 22.0 so I think my next approach will be to revert to 20.4 and see if that gets things working again.

For reference, the only modules I have loaded are Magiskhide Props Config and Universal SafetyNet Fix both of which have been working without issue for a long time so not sure why they would suddenly start playing up.
[Magisk] Ghisy:
The Pixel 4 XL on Android 11 doesn't have TWRP.

But I figured it out, see my edit.
[Magisk] mr nick:
Tried reverting back to 20.4 but the same problem persists.

I have since used the magisk uninstaller from TWRP to try and get things cleaned up properly. With everything removed I then did a fresh install of 22. This time, it booted up so I thought things were solved.

I applied the systemless hosts, rebooted and again the phone started no issues - still looking good.

I then toggled Magiskhide on but did not hide any apps in a bid to keep the steps to a minimum. Rebooted and ... Bootloop. Only way to start is via safe mode. So that's as far as I can get - as soon as I try and apply Magiskhide everything goes wrong.

I'm now out of ideas as to how to get this fixed.
[Magisk] artlan:
Going to go out on a limb and post this before calling it a night.

Am having similar issues - not a stranger to magisk/roms/etc... - did spend the evening reading & trying various things.

Hoping it's something simple I am missing - but I am seeing others with my device/update having the same problem too. May just be too tired - but was unable to get any safe-mode to work.

Device - Google Pixel 4a 5G

OS - Stock Rom, running the March 1 2021 update (Android 11 - RQ2A.210305.006)

Prior OS - Stock Rom, running the Feb 1st Update

Had been on Magisk 21.4 without issues - and had been updated to/running v22 without issues as well since release

Since applying the March update, any version of Magisk I try (21.4, 22, 22 Canary) cause bootloops and require the stock boot.img to be reflashed.

Magisk App / Manager have been completely uninstalled and were also removed prior to flashing the patched boot.img - just in case anything was lingering in the background.
[Magisk] M47Z:
Need some help installing Magisk on an ancient Rockchip tablet. It's the Medion Lifetab E7312, based on Rockchip RK3066 SoC, running Cyanogenmod 12.1 (Android 5.1). This device got its own seperate kernel.img, instead of the kernel being part of boot.img. I tried to patch the kernel.img (and also boot.img and recovery.img, just to be sure) in Magisk 22, but always get the "Unsupported/Unknown image format" error message.

Any idea how I can get it to work? Maybe manually patch the image?

Here are the images:
[Magisk] Zincoshine:
My phone prompted me to update the manager to v22.0. now the manager crashes every time I try to open it. I still have root access apparently. I'm not sure what to do here. I haven't had a problem with magisk in years, the last time I had a problem was when magisk 17.0 bricked my phone. My phone is a oneplus 5t with Android 8.1.0 and oxygen OS 5.1.7.

Edit: is there any way to downgrade the manager to 21.4 without touching magisk itself?
[Magisk] Homeboy76:
Update

SDK Platform-Tools: r31.0.0
[Magisk] CSX321:
Edit...still froze...see later post below

FWIW, the new kernel in the Pixel 3 March update hasn't frozen on me yet. I've tried to look up in which kernel version the f2fs deadlock bug was patched (if it has been), but I haven't had any luck finding the info yet. I'm currently using Magisk 21.4 with systemless hosts and the USF module, and everything is perfect.
[Magisk] nowster:
I had a freeze two minutes after booting March 2021 update with Magisk patch. :(
[Magisk] CSX321:
Yeah, I guess I cursed myself with that post. Mine just froze. Back to ElementalX, I guess!

Edit...Man, it's weird how it worked fine for more than 24 hours, and now it freezes almost immediately when I reboot! What a pain that was to fix. Safety mode didn't seem to disable the Magisk modules; it still would freeze. I had to remove all modules with the adb command, then set everything back up.
[Magisk] Sizzlechest:
If you updated Manager App to v22 and it now crashes, just uninstall the app and reinstall it. It should work even if you didn't update (or remove) Magisk.
[Magisk] Fil76:
Last time i try to update 21.4 to 22 i bricked my op6t (direct install error)

Lost boot IMG and also twrp so only hard reset was in my skill with Mauronofrio tool

I'dont speak english well could someone check if this procedure Is correct

https://i.postimg.cc/9XdCg6zz/Screenshot-20210302-185827.jpg

Update magisk manager (app to 22)

Unhide magisk and restore magisk original name

Click update and do direct install ?

Is correct ? What about if i Lost again boot.img ? Push original boot.img via fastboot ?
[Magisk] Zincoshine:
Thanks for the help and thanks to my phone for saving me from a Magisk 22.0 brick via this minor problem with the manager.