yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Yes

No, although he probably doesn't need to. (May be useful to eliminate new commits causing his issue(s) however.)

No, older manager still won't work as it will also show only latest for either Stable, Beta or Canary channels (as per Settings selection). These channels are set to latest builds at server end. Patching function uses this same set channel, assuming it will even allow this to be done before updating Manager. As stated, selecting Custom channel is the way users can set a selected older build, achieved by pointing to a hosted json file containing links to the desired buid. This is easy in the case of archived public (Stable/Beta) builds as these contain preset links set to the location of the specific build files, but 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 (Likely because John Wu is only interested in receiving debug logs from latest Canary so has never seen a need to make jsons build specific as older builds are effectively redundant as they no longer achieve their intended purpose in any case). 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.

Nb. Cases where archived debug Canary builds will be of more use than an older public release will be rare in any case. PW
[Magisk] zgfg:
About preparing a json pointing to an older Canary Magisk versions, to be able to set it up in Custom Update channel has been discussed in this thread several times.

It's possible but it takes time and one must be familiar with e.g. Github

I think it was the last time as below, see my posts when I did it to be able to test some older Canary versions (20422-20427)

Sorry, I'm really not going to write instructions now, but you can rewind back to those posts and go through the conversation (my posts, answers I was given to my questions, my comments, etc), and you will find all ingredients you need for cooking:
[Magisk] Sideburnt:
Magisk manager after updating through the app now hangs at the loading flash screen. I've uninstalled a few times and tried re-install but that didn't work.

It worked before, strange. I'm using a LEMFO LEM4 PRO which has a really old stripped back 5.1 OS so no option to clear data.

It's there anything I can try? I'd like to root again.
[Magisk] daddylonglegs:
So since it took me 4 days of research and investigating, I finally got Magisk working properly on my Pixel 3A . Not only that, but i got it working with SystemlessHosts without crashes. Also edXposed is installed, and I am using GravityBox and my phone is passing SafetyNet! So here is a guide in case it helps someone else:

1) Update OS via flash-all.bat with -w removed if you aren't on the newest Android release.
2) patch boot created by magisk via Powershell and not Command Prompt.
2b) you might have to have a kernel like EX Kernel installed because of a glitch, Systemless Hosts enabled causes Android 11+ to crash. EX Kernel prevents Android from crashing with Systemless Hosts enabled.
3) Enable Maigsk Hide and hide the Magisk Manager app itself. Rename it to something like MnM instead of the default "Manager" it tries to rename itself. Nintendo app is detecting the name "Manager".
3b) make sure you have this Magisk module installed: https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
4) Inside of edXposed, enable "pass safetynet option". The option should be third from the bottom or so.
5) To be able to do number 4, you will have to enable "App list mode". Enable it, and then also enable right below it "white list mode".
6) Then in EdXposed, go back to main screen and press the hamburger menu and choose "Applications".
7) This is the white list. For Gravitybox to work, enable the following:

- Android System (android)
- System UI (com.android.systemui)
- Call Management (com.android.server.telecom)
- Download Manager (com.android.providers.downloads)
- Phone (com.android.dialer or com.google.android.dialer)
- Phone Services (com.android.phone)

8) Go into settings in Android and Clear the play store and play services cache and data and reboot.

Device should now pass safetynet while rooted and with edXposed/Gravitybox installed :)

Apps such as "Netflix" should finally show up in search again, too. To be sure, check the following:

Open the Google Play Store app.

Select the Menu icon.

Select Settings.

Under Play Protect certification, you'll see if your device is Play Protect certified.

Hope this helps anyone else out there!!
[Magisk] ndd53:
oh. okay. that's embarrassing. somehow I thought that was different behavior.

but that still leaves me unable to patch boot.img: I try to use 'select and patch a file' and get

Process error

Installation failed

does anyone know how I can move on from that?

never mind, I figured it out. I was trying to select the boot.img file through the Astro file manager; for some reason that didn't work. once I found boot.img through the magisk manager, it patched it just fine and I have root back. I think that what helped was changing the timestamp on boot.img so magisk manager could find it in 'recent files'. thanks for the help.
[Magisk] matth76:
Hi,

I'm with manager 8.0.7 and magisk 21.4 on a mi8 // android 11 evolution rom

I can't find where to instal modules nor where i gave root access, i only see the frontpage and the settings icon .. can someone tell me what i'm missing ?
[Magisk] Didgeridoohan:
The navigation bar at the bottom. Four icons, left to right - home, superuser/MagiskHide, logs, modules.
[Magisk] matth76:
Than you, i don't have this menu (?)
[Magisk] matth76:
Finally it works,

I installed again 21.2 from a .zip i had and the menu and all settings are back (i had nothing after the doanlod path option in the settings)

updated to 21.4 and it's ok

Thanks for help :)
[Magisk] MoL_82:
It says Magisk is not installed. You do not have all the options when it is not installed.

I am not a dev, but my guess is you should flash Magisk again in TWRP.

EDIT: Ah, you already solved it.
[Magisk] regularmen:
hello, I have an odd issue in my Nokia 5 running Magisk 21.4 .

Everything is fine and working, I have added some module to suit my needs, no problem.

Then, some times later, every apps would cease to open at all. it would stuck at the apps splash screen and never goes beyond it. at this point I can't do anything, I can't open magisk manager or even the android settings. what's weird is that its still responding well, not like it hangs or lags or something. I can swipe down status bar and turn some stuff, I can still reboot the phone normally and this is the only thing I can do at that point. to fix this all I need is just to reboot, but it would happen again later. I wondered what's going on? also this has happened way back since magisk 18.0. and thanks for the help!
[Magisk] nowster:
I think this is related to the f2fs problem. I've had this a few times with my Pixel 3a.
[Magisk] CSX321:
Me, too, with my Pixel 3. I wonder is this something we can expect to be fixed in a future Android update, or are we going to have to fix it ourselves with a patched or custom kernel? I hate that my phone feels unstable now, after years of being rock solid with A10 and Magisk.

Edit...I just installed the ElementalX kernel. Seems stable so far with systemless hosts enabled. I used to use it with my old Nexus 5, but this is the first time I've used it with the Pixel 3.
[Magisk] uvzen:
My device:

Name: Huawei P10

Model: VTR-L29

Build: 8.0.0.386(C432)

I have unlocked bootloader and root magisk in version 20.4. When I want to update magisk to higher version 21.x, then I lose root. I tried update in magisk manager app or flash update magisk in TWRP and neither of these methods work. What is wrong?
[Magisk] nowster:
I'm trying out the MVK kernel at the moment for the same reason.
[Magisk] oollee:
Hey folks,

I am not able to root the Sony Xperia Z3 Compact (z3c) running LineageOS17.1.

## How I recognized the problem:

- The Card "Magisk" in MagiskManager is showing the following:

- A/B: No

- Installed: n/a <---------

- SAR: Yes

- Ramdisk: Yes

- Crypto: n/a

- MagiskManager has no bottom menu

## How I flashed Magisk (also tried flashing multiple times)

- Lineage Recovery 17.1-20210117 > Apply Update

- sideloading fails: "serving: 'Magisk-v21.1.zip' (~47%) adb: failed to read command: Success"

- TWRP 3.0.2 > ADB Sideload

- sideloading succeeds

- fastboot flash boot patched_boot.img

- fastboot fails: "fastboot: error: Couldn’t parse partition size ‘0x’"

- fastboot flash:raw boot patched_boot.img

- fastboot succeeds

Is there a way to flash Magisk with debugging output or even install Magisk by hand?
[Magisk] iamrance.asa:
Have you tried flashing the zip via twrp or other recovery? It seems like when you try to flash it, it's trying to flash a broken img.
[Magisk] FourSilver:
Correct... Only after I have done a factory reset to get rid of the bootloop.

That makes sense. Thanks for the clarification.
[Magisk] FourSilver:
It seems an even less frustrating approach would be to use the SP Flash Tool's Download feature to restore the device to the factory configuration.:)
[Magisk] nowster:
Nope! The current MVK kernel doesn't stop the f2fs lockups. In fact, it might be worse than stock!
[Magisk] FourSilver:
This is a really interesting approach. Last weekend, @a-dead-trousers posted information on the forum about a TWRP release for the Atom XL. I wonder if I could use that to flash a zipped version of Magisk that apparently worked (i.e. prior to v8.0.0) for the device.

Is this still considered a "downgrade", since installing TWRP requires installation of a non-stock ROM? (According to the install docs for the TWRP release, "booting into stock ROM will replace TWRP with the stock recovery.")
[Magisk] x.trinity:
Ive tried A11 but Magisk is not working as it supposed to ..Back to A10 and it works properly.

Ive checked Installation guide from Magisk GitHub, but its confused..its not possible to install Magisk through Magisk Manager anymore, nor flashing magisk.zip from recovery?
[Magisk] regularmen:
Hi, thanks for the response, at least I'm getting somewhere.

So what can we do about this issue. Several google searches shows dead end and it seems a recurring issue to some hardware.
[Magisk] pndwal:
Yes, flashing w/ custom recovery achieves the same thing if it works / can be done, so it will be a downgrade if using earlier version.

There are also usually ways to make a custom recovery stick w/ stock rom. Often simply booting immediately to recovery after install does this, or simlply having Magisk root installed, but but it may be more difficult for some devices.

Of course, you can keep stock recovery and still boot / use custom recovery from PC using Fastboot (fastboot boot recovery.img). PW
[Magisk] pndwal:
QCom Emergency Download mode and MTKs similar 'Emergency' mode is generally for when bootloader is corrupt / Fastboot function is broken. I think he suggested this as an alternative option because you indicated you couldn't use Fastboot initially. PW
[Magisk] Didgeridoohan:
Just to be clear (since I was a little unclear when I said "flash the zip manually as you would a module zip"), what I meant was that you can take a Magisk zip and install it from the modules section of the Manager (as long as you're already rooted). I haven't tried that in a while though (actually forgot about it), but it has worked perfectly in the past.
[Magisk] nowster:
For anyone with AdAway problems with Amazon "sad dog pages", make sure you've enabled IPv6 support in AdAway, then pause and turn on AdAway again.
[Magisk] BHUSHAN7988:
Myjio app still does not work for me. Safety net passes every time for me.

Op6t

Stock oos

Have edxposed white list mode

Any solution?
[Magisk] WilliWonka1987:
Cant install magisk 21.4. cant install any of the versions. at the reboot, bootloop, stock on Fastboot. Xiaomi Mi 10 Android 11 MIUI 12.2.4.0.RJBEUXM.
[Magisk] zgfg:
How are you installing Magisk - flashing through TWRP or by patching?

Try:

- extract boot.img from your recovery/zip or fastboit/tgz firmware

- install Magisk Manager app from Github

- patch from Magisk Manager, leave Recovery option disabled (if not familiar with patching, check Magisk Docs and Wiki on Github)

- check in the window does it report errors when patching

- flash the patched img from Fastboot to boot

If it won't boot, just flash from Fastboot the original boot.img to boot
[Magisk] WilliWonka1987:
Dont Work. Stuck on bootloop in Fastboot Mode.
[Magisk] zgfg:
Ok, but then flash your original boot.img to recover

Was there any error when you were patching?
[Magisk] WilliWonka1987:
No Errors. I've Tried four Times the Same way but the bootloop stay.

I've Set the original boot.img

I cant root It by this way.
[Magisk] dipseeet:
hello thread (:

my phone:

samsung galaxy note4 n910f trlte

resurrection remix oreo

magisk

xposed framework

termux

problem:

i do a fresh magisk install with twrp and zip file ... after reboot i get prompt to grant certain apps root ... with termux my .sh files are working ... thats fine everyting is good.

after the next reboot i lost some kind of root access

how to explain: i dont get any prompts to grant new apps root ... those apps i already granted they are still working and termux is working but myandroidtools is not working.

i can't get any components disabled or enabled ... wtf?

in my magisk manager all my granted apps are still listed (when i did my first boot after magisk install)

but

its not possible to add another app to grant root

AND

when i delete one of my granted apps iam not able to get prompt or to grant this app anymore again

ok i tried several versions (19.4 - 21.4)

only 21.3 i dont have this issue

everythings perfect except 1 thing: termux is not working (i can't get my .sh files executed correctly bcoz it says "...sh not found")

:(
[Magisk] J.Michael:
When you run termux, do you get a command prompt?

Can you type "ls" and see anything?

Does "ls" show the ".sh" file you are trying to run?
[Magisk] J.Michael:
How are you recovering from the boot loop?

Are you sure you are patching the same software that is installed on your phone?
[Magisk] Jeffnoisette45:
I'm having the same issue too. I'm on Huawei Mate 10 (not pro) ver:8.0. I was already rooted and as soon as I updated to 21.4 through the manager, I lost root! I uninstall Magisk and tried to install through TWRP, even though TWRP said I installed it successfully, I still was not rooted. I just went back to version 16.0.
[Magisk] zgfg:
Some time ago there was a problem (bootloop) with installing Magisk to MIUI A11 systems - it worked only with Magisk v20 but up to Canary 20422

Around NY it was fixed (at least I know for sure for my Mi 9T using Xiaomi A11 beta).

Nevertheless, can you try patching and flashing that older Magisk Canary v20422, maybe it will work for you:

- In Magisk Manager, select Update Channel: Custom

- Open Custom field and paste in the following URL (I made it at that time for myself when experimented with) pointing to Canary 20422:

https://github.com/zgfg/Magisk-Module-SystemlessDebloater-REPLACE-/raw/main/debug-20422.json

Go back to Manager main screen, Latest should show you now Magisk 20422 as the 'latest' available version (although in my case it shows that I have much newer 21401 installed)

See the screenshots

Then go to Install Magisk, leave Recovery option disabled (since you're patching boot not recovery img), Select and patch a file (not 'Pick' and patch a file - some will know why I mention that🤩).

Select your original boot.img and Let's go.

In the window you will see that it will be flashing target version 20422

Observe that patched img will be smaller than when patching with 21401

Try flashing that patched image:

fastboot flash boot patched_image_*.img

Again, if it doesn't work you can recover again by reflashing your original boot.img

But if it would work with 20422, you can try updating to the latest 21401 by patching over the boot img already patched by 20422 (not by patching your original boot.img) - revert Update channel back to Stable or Canary

---

@J.Michael - I think you were asking how to install an older Canary version (?). The above is an example for

You can open in browser that URL for Custom channel as above, it will open my json file and you will see how the json file have to be prepared

Btw, I didn't bother to adjust Notes - it will show Chngelog for 20401, not for 20422 but who cares

Json file must be put somewhere - lazy solution is to put to your Github if you have Github account (neccessary for everybody to be able to report issues for Magisk, AdAway, etc). Hence that URL as above
[Magisk] dipseeet:
yes i get a command prompt ... with ls i can see everything and my .sh file

with all magisk installer versions termux is working but then i have trouble with other root apps ... only with 21.3 i don't have any problems with other root apps but termux is not working

"system/bin/sh not found"

changelog:

v21.4

[MagiskSU] Fix su -c behavior that broke many root apps

[General] Properly handle read/write over sockets (the broken pipe issue)

with 21.3 i get termux working again but like i said some other root apps get trouble to work properly ... i will try now 21.4 again

magisk manager iam using 8.0.7

should i also test older releases (of magisk manager)?
[Magisk] DiamondJohn:
The path to sh is missing the leading slash.
[Magisk] contaoxxx:
Hi

Yesterday Magisk sent me a push notification that an update is available. So I updated Magisk (patch directly> restart) and no my phone (Pixel 2) has no internet connection anymore. When turn on WiFi Android 11 is restarting. Turn on mobile data phone is freezing.

What I've tried:

uninstall Magisk > not working

flash Android 11 again (without -w wiping) > not working

Does anyone have any ideas what else I could try?
[Magisk] zgfg:
You have no Internet anymore (WLAN and Mobile) or Magisk Manager complins that?

In the first case disable or even uninstall all modules, reboot and check again

In the second case u i uninstall Magisk Manager, reinstall it and try again
[Magisk] contaoxxx:
If I turn on WiFi or mobile data Android 11 freezes and restarting after a few seconds. Uninstall Magisk has no effect.

Flashing Android 11 again > no effects.

Android 11 RP1A.201005.004
[Magisk] dipseeet:
my .sh files begin with this line:

#!/system/bin/sh

i tried now 21.4 again but i flashed 21.3 back ...

on 21.4 termux is working but (almost) nothing else.

on 21.3 termux is not working (it's working but no root even if i grant root access) but everything else is working perfect.
[Magisk] Ventus32X:
I have a problem with the most recent version which is 21.4 the problem is that when installing the vanced youtube for some reason it returns to the normal youtube not only that, when installing viper4android legacy it does not really install it if it was never installed I have installed the previous version of magisk and everything is fine for me but in the new version it has bugs like these I don't know if it is incompatibility
[Magisk] zgfg:
Just please: which phone, Android version and to which Magisk version you revert to get it working?
[Magisk] Ventus32X:
J2 Prime with AetherOS Rom and Android 6.0.1 I have tried with half of the 21 versions because I wanted to test to see if the same thing happened with viper4android FX and if the same happened but with the problem that the driver module was not installed, I tried version 20.1 and it was fixed the problem with viper4android legacy installs fine in 21.3 but already in 21.4 the apk of viper4android legacy disappears
[Magisk] J.Michael:
What happens if you disable all Magisk modules?

Use a file manager and check /bin (should be a link to /system/bin), and see if you have any of {ash, bash, bsh, csh, ksh, mksh, sh}. (Really anything ending in "sh".) Note whether a file or a link.

I know it is a lot of flashing, but I think you should try in an unmodified system, and again in the two versions of Magisk.

Maybe you should try another terminal emulator.
[Magisk] dipseeet:
i only have

systemless hosts and busybox for android ndk

activated as modules.

is sumthing wrong wit my busybox install?

in system/bin i HAVE

ash (link to busybox)

sh (no link, just a file)

in system/bin i DON'T have

bash

bsh

csh

ksh

mksh

i do also have a

system/xbin folder

and a

system/vendor/bin folder

i've tested a script manager app and i could execute my .sh files correctly ... i needed to change

from

su -c "COMMAND"

to

su -c COMMAND (without " ")

i thought k cool this will work now in termux ... still not working :(

iam about to uninstall termux completely now and fresh install it again
[Magisk] DiamondJohn:
And THERE'S the missing slash :)

I don't use termux, and am assuming it is basically a highly featured shell app.

It would appear that your location of the sh binary (ie the shell interpreter) is located somewhere else, or possibly even missing. Try the following, and let me know the results. Althogh it may be obvious where I am heading ;) I have given my results to help you with an example of a working env.

$ which sh
/system/bin/sh

$ echo $PATH
/product/bin:/apex/com.android.runtime/bin:/apex/com.android.art/bin:/system_ext/bin:/system/bin:/system/xbin:/odm/bin:/vendor/bin:/vendor/xbin

Basiclaly, the binary sh is in the PATH.
[Magisk] BillGoss:
There's currently a bug in Termux 105: it won't start on a clean install. See https://github.com/termux/termux-app/issues/1896

Do a clean install of Termux 104 which is working fine.

And don't use Magisk 21.3 as su commands won't work on it. Magisk 21.4 fixes that problem.
[Magisk] J.Michael:
You don't say which version of Magisk you have when you are reporting "/bin/*sh".

I don't care which modules you have, I think you should try disabling all modules and see if that affects whether "sh" is in "/bin", and whether that is enough to get termux to "work". (I need help here. I don't know what termux is. I also thought it was just another terminal emulator. Then I Googled it and a snippet said it installs a linux-like environment on a (not necessarily rooted) device. I don't know what that says about what normal things get hidden/replaced.)

What is your busybox install? I mean, did you do something to deliberately install busybox? Or do you just know you have busybox installed? (I had busybox in Kitkat; in Android 9, it's using toybox.)

I was flailing when I suggested looking for every shell I could remember. It's not important that you don't have most of them. What *is* important is that you *do* have "sh". Confirm or deny: You found "sh" in "/bin", but when you run termux and try to run a script, something says you do *not* have "/bin/sh"?

What is a script manager app? How is it different from a terminal emulator? Are the "su" commands you needed to change inside the script you are executing? Or is the "su" command the way you run the script?

Just as a test, if termux is "not working", and is saying "sh not found": Try deleting the line "#!/system/bin/sh" from the beginning of one script file. Whether it works or not, try replacing that line with "#!/bin/sh". (I assume you have a link "/bin" pointing to "/system/bin".)
[Magisk] FourSilver:
This method worked! In fact, I discovered that downgrading was unnecessary; using the latest zip with this method successfully rooted the device without causing any issues. Of course, many thanks to @a-dead-trousers for providing instructions for installing LineageOS on the Atom XL, which also specified exactly how to disable AVB (this is key to avoiding bootloops.)

I hope that LineageOS will continue to evolve for the device, so that the audio jack will be functional, and VoLTE will work without issues as well. Then, I can make the switch from the stock ROM without reservations.