yashsingh1/xdaforums huggingface dataset:
[Magisk] robi54321:
Hello all,

I have 21.4 installed, but whenever I try to install any magisk module it fails and tells me to install Magisk X.Y+ where X.Y is an older version than mine. Also where it shows the latest Magisk version I get a forever "Loading..."

Any ideas how to fix this?

Thanks,

robi54321

Device: Exynos S10+ on Android 11

Magisk log:

02-20 09:45:27.364 5296 5296 I : Magisk 21.4(21400) daemon started
02-20 09:45:27.364 5296 5296 I : * Device API level: 30
02-20 09:45:27.428 5296 5297 I : ** post-fs-data mode running
02-20 09:45:27.436 5296 5297 I : * Mounting mirrors
02-20 09:45:27.436 5296 5297 I : mount: /dev/jaHx/.magisk/mirror/product
02-20 09:45:27.436 5296 5297 I : mount: /dev/jaHx/.magisk/mirror/vendor
02-20 09:45:27.436 5296 5297 I : link: /dev/jaHx/.magisk/mirror/cache
02-20 09:45:27.436 5296 5297 I : mount: /dev/jaHx/.magisk/mirror/data
02-20 09:45:27.436 5296 5297 I : link: /dev/jaHx/.magisk/mirror/system
02-20 09:45:27.437 5296 5297 I : mount: /dev/jaHx/.magisk/mirror/system_root
02-20 09:45:27.437 5296 5297 I : link: /dev/jaHx/.magisk/mirror/system_ext
02-20 09:45:27.438 5296 5297 I : * Initializing Magisk environment
02-20 09:45:27.454 5296 5297 E : * Magisk environment incomplete, abort
02-20 09:45:27.454 5296 5297 I : * Loading modules
02-20 10:45:28.589 5296 5605 I : ** late_start service mode running
02-20 10:45:28.590 5296 5605 I : * Running service.d scripts
02-20 10:45:28.602 5296 5605 I : * Running module service scripts
02-20 10:45:42.679 5296 7143 I : ** boot_complete triggered
[Magisk] Didgeridoohan:
That simply sounds like the module you're trying to install is using an outdated installer script.

https://www.didgeridoohan.com/magisk/Magisk#hn_Outdated_template

That could be caused by something on your device blocking internet access for the app. Firewall, hosts file, etc...
[Magisk] robi54321:
Thanks for the quick reply!

It happens with Magiskhide Props Config too, which I assume uses the correct template :/ and literally every module. Also this is a fresh install, there is no firewall or any change to the hosts file.
[Magisk] Didgeridoohan:
The only way for the install message to tell you to install an older release of Magisk is if it's using an outdated script. That can happen with MHPC too if you're not downloading it from within the Magisk app...
[Magisk] pndwal:
... And there you go! First issue fix committed post 21410! (replete w/ your code in green.) ... Guess you'll be able to run your mod in TWRP again when 21411 arrives shortly @BillGoss!

https://github.com/topjohnwu/Magisk/commit/9cc91b30b34729c8fe470a3f3a96c617347f585d

Great contribution (even though John didn't respond after previously fobbing it off: "This is a bug in many custom recoveries, no way around that"... At least he's up closing issues / committing fixes despite a demanding week at Apple, and itching to try A12 on Pixel! ...and I won't need to eat my hat.

See you in the Changelogs! PW
[Magisk] pndwal:
Not sure why your Manager version shows as 284. I thought it should report v 8.0.7... maybe someone on stable can confirm... I may have forgotten.

Perhaps you could confirm if actual version is 8.0.7, but looks strange to me. PW
[Magisk] Didgeridoohan:
Looks like an old Canary Manager...

Edit - looks like it matches this commit: https://github.com/topjohnwu/Magisk/commit/87de0e7a0e13bcbbc2491b158149c8dea3f77937
[Magisk] pndwal:
So it does, thanks.

... So the v204 Manager he's using is a May 2020 20400 series - compatible Canary Manager (pre canary channel cleanout) w/ latest stable 21.4 (21400 Jan 2021) Magisk? ...Why?...How?

This is surely incompatible! Oldest Canary Manager still archived is v303 for Magisk 21001!

Update Manager to 8.0.7 from Magisk main page here for starters:

https://github.com/topjohnwu/Magisk

PW
[Magisk] whoamanwtf:
Does hiding an app with Magisk hide use any system resources? If I have 5 hidden apps or 100 is there a difference in battery/cpu usage on my device?
[Magisk] pndwal:
You can likely hide root from only one component of apps that detect root to make them work, and it is recommended that you limit processes hidden for system stability reasons; I'm not sure of impact on system resources (- as a guess, I'd say this would be minimal, and stability is the real concern).

It is recommended NOT to add System apps and processes (especially) to Hide list for the same reasons. This can even prevent a device from booting.

For security centric apps (banking etc), I've hidden root from all components and not experienced problems, but I may be lazy; it's likely only one component actually detects root, and you could experiment to find (enable all services, get app working, then disable one at a time to identify) which that is. I also have G Pay working fine with root hidden from its two services fwiw.

See officially endorsed tips on hiding root from apps, including why you shouldn't simply hide everything, here:

Hiding root and passing Safety Net:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

Skip down to The Hide list.

See also System Instabilities here:

Magisk Issues:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

PW
[Magisk] ekowwillis:
CONFIRMED!

Latest Magisk Canary works on Pixel 3 XL running Android 12 DP1
[Magisk] Zirila:
has anybody managed to root a galaxy a41 with magisk? there is no information about this anywhere.
[Magisk] buzzywaw:
Hi all

I using latest magisk 2.1.400 just because i want to run banking app ( have to hide the magisk with magisk hide)

But since i use LOS 17 on my ether (nexbit) my phone got unlock issue, there is error when i got to unlock with patern, system ui crash and i have to do draw pattern over and over until my phone is unlock

I have uninstall the magisk, but weird the problem still persist

Clean install the room may help to run unlock pattern but i can run banking app

Any solutions for this

Thanks
[Magisk] snickle:
Lenovo t

b-x606f. Magical 21.4 loaded via twrp. Canary magisk manager.

magisk manager says needs to be updated. Try to do a direct update to boot image and fails due to read-only filesystem. Patch and flash zip via fastboot works.

any ideas?
[Magisk] miko12312:
Anyone get magisk to work on android 12 dev preview ,I was able to get the manager to flash the boot.img and successfuly flashed to phone ,after opening magisk I had root access until I installed modules and had to reboot , the boot.img was still patched ,just the manager was not able to do anything
[Magisk] pndwal:
New Public release! (Stable and Beta channels):

Magisk Changelog

v22.0

[General] Magisk and Magisk Manager is now merged into the same package!

[App] The term “Magisk Manager” is no longer used elsewhere. We refer it as the Magisk app.

[App] Support hiding the Magisk app with advanced technique (stub APK loading) on Android 5.0+ (it used to be 9.0+)

[App] Disallow re-packaging the Magisk app on devices lower than Android 5.0

[App] Detect and warn about multiple invalid states and provide instructions on how to resolve it

[MagiskHide] Fix a bug when stopping MagiskHide does not take effect

[MagiskBoot] Fix bug when unpacking lz4_lg compressed boot images

[MagiskInit] Support Galaxy S21 series

[MagiskSU] Fix incorrect APEX paths that caused libsqlite.so fail to load

PW
[Magisk] pndwal:
Release Notes up:

Magisk

2020.2.23 Magisk v22.0

RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!

Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the whole Magisk user experience.

Magisk Manager is dead.

Long live the Magisk app!

Ever since the first Magisk release, Magisk (the core components) and Magisk Manager (the companion app) are released separately and isn’t necessarily always in sync. This leads to some confusion and a lot of complexity when downloading/installing Magisk through the app. Starting from v22.0, the Magisk app (renamed from Magisk Manager) includes everything it needs within the APK itself, making installation a 100% offline process.

Custom recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC™🌈. Check out the updated installation guide for more info.

App Hiding

Another major breakthrough in this release is that devices lower than Android 9.0 can now also use the advanced app hiding technique to hide the Magisk app. Due to this incompatible change, RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!

Bug Fixes

[MagiskHide] Fix a bug when stopping MagiskHide does not take effect

[MagiskBoot] Fix bug when unpacking lz4_lg compressed boot images

[MagiskInit] Support Galaxy S21 series

[MagiskSU] Fix incorrect APEX paths that caused libsqlite.so fail to load

Full Changelog: here

This site is open source. Improve this page.

Many more Doc updates. 👍 PW
[Magisk] pndwal:
Latest Canary Changelog incl. Release Notes:

Magisk (79ee85c0) (22001)

Sync with public release

Diff from v22.0

None

👍 PW
[Magisk] pndwal:
Major release!

... thanks for the late nights, and for all the invitations and fast paced progress with this ultimate superuser utility! PW
[Magisk] HippoMan:
I very much appreicate and am sincerely grateful to John Wu for his work on this, which helps so many people.

Sadly, I will not be upgrading to this version, because it no longer supports the A/B OTA Retention Script. That module makes OS upgrades very simple on A/B devices such as mine, and I want to avoid the more complicated and therefore more error-prone method that I would now have to utilize in order to upgrade my OS under this new Magisk version.

Some day I might give in, but for the time being, I'm sticking with 21.4.
[Magisk] Aveon:
Hey guys,

I'm using OnePlus 3 with custom ROM(bootloader unlocked) after the new update.

Whenever I update through app and select the proper steps, the devices reboot to recovery, but mine doesn't it goes to bootloader instead.

After reading the guide what I came to conclusion is to have to patch my recovery img now, but I'm a little confused about how do I use custom recovery mode? And how do I update magisk now on?

Device- OnePlus 3

ramdisk - no

SAR- yes

SaftyNet Pass
[Magisk] pndwal:
Still clearly some issues to iron out.

I just tried direct update on Xiaomi RN8T (Magisk in boot.img despite ramdisk = no).

When clicking Lets Go, nothing seemed to be happening, and I eventually closed Magisk and rebooted, and next get 'the system has been destroyed' screen.

Simple matter to flash an earlier Magisk-patched image and up running again w/ root.

Next, tried patching a boot.img, and similarly, when clicking Lets Go, nothing seems to happen.

Gone back to 21410 for now, and all is working fine again. PW
[Magisk] Asia81:
I tried to update inside the app, but now it keep reboot to the download mode :unsure:
[Magisk] vip5912:
Automatic (recommended) update is fail.

It say OK but after reboot Magisk is not installed.

I rebooted to Recovery and installed Magisk.zip.

It's fine.

Ramdisk Yes, A/B No, SAR Yes, SafetyNet Pass
[Magisk] Aveon:
same and if you flash again, untick the recovery mode, and magisk doesn't update but you get your custom recovery back
[Magisk] zgfg:
Major release v22 (Stable, Beta and Canary).

Successfully updated Canary from 21410 to 22001
[Magisk] Asia81:
No I meant I still can reboot to twrp, but when I try to boot my system the "normal way", it just go to the download mode instead.

Same happen when I reboot to system from twrp reboot menu.
[Magisk] Icebullet99:
Weird that the recommended method (which the author stated that works 100% of the time) does not work at all, while the flash in recovery method, which is not recommended, seems to be working OK.
[Magisk] zgfg:
When posting such statements you have to precisely describe your model, firmware, error you have, etc

E.g., I'm updating Magisk by patching and flashing Magisk for two or three years (not on a single device) and it works.

It also works for many, many others here.

Hence it is not generally true that patching method does not work at all.

Make sure that you choose right img to patch, that you check in or not Recovery option (see Magisk docs) and that you properly flash the patched img
[Magisk] Didgeridoohan:
I saw something similar. The "Let's go" button didn't seem to do anything, but while trying to save a log I realised that there were several flashing instances running in the background. Completely destroyed my boot image... Had to restore it and flash in TWRP to get up and running again.

I think I managed to get a log of the issue and have given it to John, but could you grab one as well, just in case?
[Magisk] mrsdbskn:
Same thing happened to me. My phone keeps booting into download/fastboot mode or if I do the button-dance i get into TWRP.

How can I find the backedup boot.img from magisk?
[Magisk] Aveon:
Same on my OnePlus 3 device the patched img did nothing after flashing the update still goes back to bootloader for some reason.
[Magisk] zgfg:
Guys, did you try by first unhiding/restoring Magisk Manager (or Magisk app, if you were already on Canary).

That was the most common case/bug reappearing every so and often with (major) Magisk updates
[Magisk] Aveon:
(not on canary build)Already did and even tried the installation guide still same result and if I try to boot in recovery mode to boots up in fastboot/bootloader instead and after reboot viola!

Still not updated :(
[Magisk] 7wells:
Sorry, please ignore this.
[Magisk] svendsvin:
Very nice. Smooth update. Miss a colored icon though.
[Magisk] zgfg:
Hidden Magisk app?

In that case it replaces its standard Magisk icon with that one (with the 'wrong' size on some devices)
[Magisk] svendsvin:
That did the trick. Thanks.
[Magisk] Spartacus500:
Samsung Galaxy S7 Edge Custom Pie 9.0 Rom, upgrade to version 22000 passed without any errors, but am I okay? Now I have no information that the latest version of Magisk is installed, is it correct on the new version?

Opening the option what I marked does not work for me on the latest version of Magisk manager, is it supposed to be or is something wrong with me?
[Magisk] zgfg:
This is how it looks like once there is no more Magisk Manager but Magisk app (already in previous versions of Canary)

It clearly says what is the latest version of Magisk app (22000), hence that's also the version of latest Magisk
[Magisk] ssamurai:
the last update destroyed my phone REDMIN NOTE 8
[Magisk] zgfg:
The phone exploded?🤓

Flash the original/stock boot img or the one patched by your previous working Magisk

If you are not accustomed to patch&flash images, you might still have TWRP backup of the Boot with the previous Magisk
[Magisk] ssamurai:
I fixed it by installing a custom recovery
[Magisk] XtraWater:
I just updated the manager and magisk (stable). As advised I did unhide magisk. The update process was fine and the phone booted normally. Now, in the app drawer I see 3 magisk icon. One looks as the mask icon. The other one has the name I had masgik hidden before. And the 3rd has the name I just gave when I activate hide magisk again.

How to clean up those icons? Just uninstall?

Edit: restated phone again. The original magisk icon is gone. Then I deleted the old hidden app.

It seems everything fine now.
[Magisk] HippoMan:
I apologize for the above post. It is a false alarm.

I was going by an earlier message which stated that the A/B Retention Script for OTA is not supported under the latest Magisk version. However, some time after that earlier message was posted, it turns out that osm0sis fixed the A/B Retention Script, and it now does indeed work under Magisk 22.0.

He pointed that out to me, and so I tried upgrading to 22.0 (after backing everything up, of course), and his OTA utility is indeed available via that version of Magisk. I reinstalled my current OS via Local upgrade and the standard A/B Retention Script procedure, and everthing worked fine.

So, I am now successfully running Magisk 22.0 on my OnePlus 7Pro (GM-1917) with OOS 10.3.8.
[Magisk] pndwal:
Yes, intend to do this when I get a little time... precious little ATM! 😐

As it's a long time since I've grabbed logs, please point me to which / how. Also, I didn't see your issue on GitHub to append... Thanks, PW
[Magisk] Didgeridoohan:
A logcat would most likely be the most helpful:

https://www.didgeridoohan.com/magisk/MagiskHelp

And I didn't open a GitHub issue. I sent it to him directly since I'm active in the internal testing group... I would append a link to your post or issue there.
[Magisk] SonderTech:
So I updated to magisk 22 and it doesn't seem to recognize that it's rooted until I uninstall magisk the app and reinstall magisk 8.0.7
[Magisk] guhvanoh:
Poco F1 running PE11 20210207. Updated from Magisk v21.4 and Manager 8.0.7 via MagiskManager. I was prompted to update Manager first and then Magisk via direct install. All went smoothly without any problems at all.
[Magisk] Smil3yWulf:
Im having problem rooting with v22. I was fine rooted with 21.4 but the new update v22 doesnt rooted my tablet Samsung Galaxy a6 (SM-T280)it always says ramdisk yes. Installed no latest 22. Ive tried patching the boot and flash it with odin. Also twrp flash v22 zip and do all the process but i still get installed n/a on magisk app Any help or guide to be rooted with v22 on SM-T280
[Magisk] snickle:
Upgraded app to new version. Could not do a direct install if 22. Complained of read-only file system when try to write boot img. I used the patch and fastboot the patched boot.img and everything is fine.

Ideas on read-only filesystem?
[Magisk] ericotena:
It is a clean new stock boot and system.img. phh superuser & hidesu works fine. Only the supersu i can't make it work.

---------- Post added at 01:48 PM ---------- Previous post was at 01:47 PM ----------

Of course i said that on my previous posts. Just want to root w/ supersu and pass safetynet. Phh superuser works fine for me. Honor 4x device. Stock rom.
[Magisk] kUNwAH:
Everything working fine on v6

But when i update to v7, i faced a bootloop problem. Does anyone can help me about this?
[Magisk] grep_i:
So just for sports to see if you can do it.

If it's just about SuperSU + suhide combo why are you posting in Magisk thread ?

Please take your question to SuperSU or suhide thread.
[Magisk] jsaxon2:
It may be an incompatible module that is installed. Run the magisk uninstaller zip and then flash v7. Add your modules back one at a time rebooting between each and see which one is the problem. That is what I had to do.
[Magisk] ericotena:
Of course i posted there. And i posted here because it is basically the same process with or without magisk. Isn't it? You type something in the terminal. You flash supersu & suhide/superuser, magisk, xposed. You check if you bypassed safetynet. Right? I know someone can help me on my problem that is why i also posted it here.
[Magisk] Giblet-dono:
The way to do it (as far as I know)

Make sure you have no root (superSu OR superuser), No Magisk and no xposed installed (use the right "uninstallers")

Then install SuperSu SR1

Reboot your phone

Then install magisk, suhide and xposed (in that order)

Reboot and it should work =D
[Magisk] grep_i:
Yes sir, hope they give you right answer in the right thread were you already posted the same question.

It's quite possible your phone is not compatible this advanced stuff.

Have you also asked in phone specific thread.
[Magisk] ericotena:
Ha ha i dont see a problem posting the same question on different thread wherein your question is not really irrelevant. Thanks though.
[Magisk] alroger:
I see a problem.
[Magisk] ericotena:
:svetius:
[Magisk] kUNwAH:
I had done what you told, but i still facing the bootloop after flashing v7... Does it have other way to solve it?
[Magisk] knipp21:
If the end goal is to have magisk installed. Then I'm OK answer the question.

But your question was answered in both threads. I know because I asked them lol

You need to get rid of phh. Flash your Roms original boot.IMG and delete the phh app.

IF YOU ALREADY HAVE MAGISK ON YOUR PHONE!!

Type

echo SYSTEMLESS=true>>/data/.supersu

Flash 2.78 (should tell you it will do it systemless in the log)

Flash suhide 0.54

Download the suhide GUI app
[Magisk] Matt07211:
I have got that same error from the same app on my unrooted device. It requires internet access to use external API's to verify the safetynet API, as I can we on your screenshot that you where only on a 2g network, so try using when on WiFi or a better data network when trying to use the all to verify safety net.
[Magisk] ericotena:
New clean system. Already did that but with no magisk. I did type that then flashed supersu then after reboot the suhide. Does it mean it didn't bypass safetynet because i dont have magisk?

---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------

Lol im on wifi and not mobile data. That 2g only indicates the signal strength of my network.
[Magisk] Matt07211:
Hey just seeing if you've got all your based covered :p
[Magisk] knipp21:
Did the log say systemless mode detected when you flashed 2.78 ?
[Magisk] Frostbiter:
Magisk with suhide doesn't appear to work on the moto g4 plus unfortunately, unless I'm doing something wrong.

Flash systemless SuperSU properly

Installed Magisk

Installed suhide

safetynet fail

Install xposed 86.6, xposed doesn't work (says installed but not active).

Remove suhide, xposed 86.6 works.
[Magisk] ericotena:
No worries ????

---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------

I think so but i cant confirm. Maybe will try it again.
[Magisk] grep_i:
You can confirm by this if the option under system is grayed out like in this screenshot
[Magisk] gudenau:
Because that did not work, as I said.
[Magisk] zgfg:
You should report the issue to Github with logs

Btw, you can still try Direct install (to collect logs), even upon you already updated
[Magisk] snickle:
How do I collect the needed logs. Have not done it before
[Magisk] zgfg:
When finishing Install (update) you have diskette icon top-right to save the Install log

You have also a tab for logs (between the tabs for Superuser and Modules), wherefrom you can also save the logs
[Magisk] tom1807:
Tiny bit stuck now.

Magisk said "Update available" -> downloaded, tried to install but got the error message "Package didn't parse correctly" (sth. like that). So now when I want to try again and open "Manager" it says "Upgrade to full Magisk Manager to finish the setup. Download and install?" and nothing happens.

Uninstall Manager? Reinstall Manager 8.07 again and then try?

Cheers

Tom

Edit: Nvm, installed 8.0.7 again and then started the update, all fine
[Magisk] me_droid:
Same as tom1807 except I didn't install it because instructions indicate you have to unhide magisk first. Plus not sure I want to update anyway. This is on a Pixel 2, stock, rooted. I exited magisk manager but now every time I try to open it, it pops up this message. I never started to install it so not sure why it claims I need to finish the setup. If I select cancel and try to open manager it just pops up again and I can't get into it. Anyone else come across this? Any way around it? Even if I want to update I can't get into it to unhide it.
[Magisk] chavocarlos:
I solved my problem flashing stock boot.img again

Reboot in TWRP.

Flashed magisk patched boot img again.

Reboot in TWRP.

Flashing Magisk 21.4 again. (Finised OK)

Reboot in TWRP.

Unisntalling Magisk 21.4 (Finised OK)

Reboot in TWRP.

Flashing Magisk 22 (Finished OK)

Fixed

I have an OnePlus 6.

Hope helps.
[Magisk] John32145:
My j7 prime root is not working anymore with this new update, i updated it, reinstalled it, and the root is not working anymore on the latest update, only on the old magisk, also, theres no settings to config
[Magisk] kamiller42:
I have the issue w/my OnePlus 6T where it keeps booting to TWRP. This is after Magisk said it needed to reboot to make a modification to install.

Is this an issue of a Magisk module incompatibility? Does flashing boot.img erase everything on the phone, apps & data? Is Magisk booting to TWRP because it wants me to install something?