yashsingh1/xdaforums huggingface dataset:
[Magisk] daddylonglegs:
Thanks! I take it this means this systemless hosts issue will not be resolved with Magisk and to use it from now on will require a custom kernel?

Unfortunately no Kirisakura for my phone. I appreciate the help though.

It kinda seems like Elemental X is working, kinda?? My phone stutters like crazy but doesn't outright crash like it did with Systemless hosts enabled on the stock kernel.
[Magisk] curiousrom:
@ipdev says here in the Open GApps thread that TWRP 3.5.0 does not support Android 11 on several devices.

***
[Magisk] zgfg:
Remove (Riru and) EdXposed and try again. Check a day or two ago, if I recall correctly, it was mentioned that TJW removed EdXposed from the Repo, since not updated to be compatible with the latest Magisk
[Magisk] zgfg:
I say here that TWRP 3.0 supports A11 on my device 😎

I didn't say in my post it will work for every device (and specially not for whatever custom ROM on the whatever device)

There is a TWRP thread and official TWRP site (link was also in my post) - please read there officially about TWRP support for A11
[Magisk] zgfg:
Instead of flashing Magisk from TWRP/OF Magisk, did you (method is described in Magisk Docs and Wiki, available from Github), patch your stock boot img and flash by Fastboot.

Since it is boot img, it must be patched with Recovery option disablef, and once patched, flashed to the boot partition.

(You don't need TWRP or OF to install Magisk)

Use the latest Stable, Beta or Canary Magisk v21.4

That way it should properly install to MIUI (I'm also on MIUI, currently on Xiaomi.eu MIUI 12.5, but installing and updating Magisk that way since MIUI 10)
[Magisk] curiousrom:
Obviously & it's in the post I linked to. ;)

***
[Magisk] zgfg:
You also installed EdXposed?

I'm pretty sure I read in this thread two or three days ago that EdExposed is not compatible with latest Magisk - but if you want to look for troubles...🤩
[Magisk] zgfg:
In the first post you claimed that you tested modules separately and found that it definitely worked for you with Systemless hosts but blocks with SafetNet Fix, now you claim the opposite?!
[Magisk] daddylonglegs:
EdExposed is working just fine for me now. I have the latest Gravitbox [R] and it's awesome! Finally can have more than 4 notification icons and the ever-useful lock screen torch via power button!

I think I got mixed up because I forgot "Systemless hosts" is something you enable in settings, and doesn't show up in module downloads. So I probably thought I didn't have it when I did.

Systemless hosts was the issue, 100%. My Pixel 3A is now working wonderfully on the latest Android 11 release, with Gravitybox, and my phone passes safteynet too.

It was a hellish 2 days but the aggravation came from the Command Prompt not flashing the magisk boot properly for some reason (which PowerShell was able to do properly) and then the bonus surprise that Systemless hosts no longer works with Magisk on many phones.

I can't exactly say why but my phone stopped hardlocking when I installed Elemental X. I have Systemless hosts enabled and my phone hasn't hardlocked once all day. Without Elemental X, it would hardlock within seconds of booting Android!
[Magisk] Didgeridoohan:
It's not an issue with a specific module. Magisk itself without modules can most likely trigger this f2fs bug, but it's sometimes more like to happen with modules installed (doesn't really matter which one, but systemless hosts have likely been deemed a culprit in many cases since it's such a common module).
[Magisk] zgfg:
Ok, Systemless hosts is not downloadable, it is built-in

Nevertheless, once you install it from Magisk Manager settings, you can enable/disable/remove it from the Modules tab like any other (downloadable) module
[Magisk] daddylonglegs:
Is it a bug in android itself? Or magisk? Or systemless hosts?

Just wondering if/when I can ditch Elemental X since I don't really like using custom kernels when possible.
[Magisk] Didgeridoohan:
It's actually in the Linux kernel... So unless that particular commit gets fixed or reverted upstream (or by the individual kernel developers) it'll find it's way into more and more kernels...

You'll find lots of details if you check the Github issue I linked and then follow the link chain starting with @topjohnwu's message at the top.
[Magisk] J.Michael:
When you were using Command Prompt, did you Run as Administrator?

When you switched to PowerShell, did you Run as Administrator?
[Magisk] daddylonglegs:
Funnily enough now that you mention it, I ran command prompt as an administrator, but NOT PowerShell. You'd think it would be the opposite, right!?
[Magisk] pewe:
I installed Magisk and using it I successfully rooted my Xiaomi Redmi Note 9 phone.

All is working but I keep getting notification of an update for Magisk and in the program screen I get

I select 'Install' and use the option to 'Direct Install'. The download starts followed by the install process then I get this

The end of the log file reports

- Flashing new boot image

blockdev: /dev/block/mmcblk0p34: Permission denied

! /dev/block/mmcblk0p34 is read only

! Installation failed

Can anyone tell me why the update is failing?
[Magisk] Didgeridoohan:
Most likely because your device is using a Mediatek chipset. You'll probably need to either install Magisk from a custom recovery or by patching the boot image and flashing it manually. It's been brought up already on Github (just a few days ago), and this was the reply:

https://github.com/topjohnwu/Magisk/issues/3724
[Magisk] pewe:
Thank you - very prompt response and very helpful.

I guess I'll just ignore it and disable update check. I only rooted to have the facility for call recorder, and as long as that works I don't think I need to update - or do I ???
[Magisk] Didgeridoohan:
No... There's no need to update if things work as you want them to.
[Magisk] daddylonglegs:
I installed Magisk and now my Google Pixel 3A's camera app closes as soon as I open it. I know that Samsung and Sony phones used to block you from using the camera app if you were rooted, but I never heard of Google doing that with the Pixel phones. Is that something new Google is now doing or is it something else causing it? Is there any way around it?
[Magisk] Didgeridoohan:
You just have a never-ending stream of issues, don't you? :ROFLMAO:

Most of the times stuff like this is caused by modules, so that would be the first place I would look.
[Magisk] DiamondJohn:
FYI I have a rooted 4a, and the stock ROM camera works without a problem.
[Magisk] nowster:
Rooted Pixel 3a here. Magisk 21.4 + Safetynet fix 1.1.1. No problems with stock camera app.
[Magisk] daddylonglegs:
haha I know right!

The difference with my phone though is I don't pass safetynet because I have edXposed installed. The reason I am asking is because Google never cared to disable the camera app for rooted users before. So I was wondering if it's a thing they are doing now out of spite for rooted users.

FWIW I uninstalled the camera app updates so now it's on the original release and it no longer force closes. So it does seem that on newer versions of the Pixel camera app, it won't run if it detects root. :(
[Magisk] BrimoFan123:
What is Safetynet fix 1.1.1 ?

I don't see such module.

ctsProfile attestation result is failed on my phone. Is that Safetynet fix a fix for this issue?
[Magisk] Lughnasadh:
https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
[Magisk] wars54:
Hello, I have a problem with magisk.

This one has mysteriously disappeared, so I wanted to reinstall this one but I can not at all.

He doesn't want to settle down

My phone is the xiaomi redmi 5 plus

And I have orange fox (twrp)

Would you have a solution thank you
[Magisk] J.Michael:
Have you tried disabling edXposed?

(and updating camera app)
[Magisk] Homeboy76:
@ughnasadh

OP

...Downloads and changelogs can be found on GitHub...

Maybe, depends on other factors: device, rom, etc.
[Magisk] bartleby999:
Have you installed a custom Kernel? That's the exact same thing my Tab did when the custom Kernel was borked.
[Magisk] FourSilver:
I'm new here, and would appreciate suggestions on how to get feedback on my question about how to troubleshoot the bootloop issue after installing Magisk.

I did additional research, and learned that providing logcat data would be helpful. However, none of the information I found helps when the device is stuck in a bootloop.

Please help.
[Magisk] kevk60:
Just updated from canary to beta 21.4 and magisk manager 8.0.7. All went well. All root apps are good and safety net is all good also. Systemless hosts is working also after enabling again in magisk and a reboot. This is on a one plus 8t running Android 11 stock rom.
[Magisk] J.Michael:
I was curious why you started with Magisk Manager 8.0.0 when that was not the latest version, but you said you let the Manager update itself, so it probably doesn't matter.

When you're in the endless reboot state, do you still have adb access? Can you use adb to get to what you called the bootloader?

Did you see the discussion in the installation document about whether Magisk had to be installed in recovery?

Have you gone through this thread to see if there are comments about Android 10 only working with an older version of Magisk?

It seems to be a fussy matter to use not-the-latest Magisk. There is a place in the Manager where you have to specify the "update channel". You have to choose from {stable, beta, canary}. You might have to put a json file on an http server. (I'm just repeating words. I've never done these things.)

Is there a forum, or at least a thread, dedicated to your device? Someone there may have been through this.
[Magisk] shorbah:
I did that before but didn't work I will try again
[Magisk] FourSilver:
Once the device is stuck in the bootloop state, adb access is lost and unable to get to the bootloader. The only solution I am aware of at that point is to use the SP Flash Tool to interrupt the process and return device to the factory state.

According to what I read in the Magisk Installation, using a custom recovery is discouraged; patching the boot image is the recommended course.

I am still trawling through this thread; however, I have yet to see any information on Android 10 working with older versions of Magisk. (Assuming that is the case, how can I get older versions of Magisk?)

Seeing that I am working on a Windows 10 machine without network connectivity, so I am moving all the necessary files via removable storage. Magisk 8.0.0 was the latest at the time I started working on installing Magisk, so I have been working with that. It didn't seem to make any difference, since it appears that I have to update before doing anything else.

I did a search on this forum for threads about this device, and came up empty. I created a post, and got no responses (save my own.)
[Magisk] pndwal:
As per advice above, read installation instructions in GitHub link from Magisk Manager homepage, especially info on what to do if Ramdisk = no. Generally, these will require Magisk in recovery (flash recovery image, NOT boot image). More below.

Previously channel selected was important, but presently Stable / Beta / Canary channels are practically the same (Synced); all using latest 21.4.

Nb. Often there is no need to change Install options automatically selected in Magisk Manager. If 'recovery' option is selected (and you confirm ramdisk = no) in most cases (Xiaomi and some other devices are sometimes exceptions) you will need to patch and flash recovery image, not boot image, and this would also explain bootloop.

To recover from your bootloop, enter Fastboot and flash unpatched boot image. 👍 PW

Edit: you can often enter Fastboot mode by pressing button combo at just the right Instant; may take many tries, or figure out if you can power device down to try.
[Magisk] J.Michael:
re: "custom recovery"

That's different.

Some Android systems will not support Magisk installing itself in the boot image. On those systems, you let Magisk patch the recovery image. It's still mostly the "stock" recovery image.

On my Samsung, I handed Magisk a tar file with a flock of images. Magisk Manager patched several images, apparently recognizing that most of the work needed to be done on the recovery image.

I'm not sure whether Samsung is the only case where Magisk has to be installed in the recovery partition. In the "pick and patch an image" option, there used to be a checkbox "Recovery", like, in the absence of any other context, the Manager had to be told it was being handed a recovery image.

If you do patch a eecovery image, you have to modify the fastboot command accordingly, saying "recovery" instead of "boot" where that is specifying a partition. (I don't know if anyone would ever "fastboot boot magisk_patched_recovery.img".)

A custom recovery is a replacement for the recovery partition. At the lowest level, it would be a way to boot an alternate system, using the device's established mechanism to "boot to recovery". If it didn't provide recovery-type functions, that's just the way it would be. TWRP is a custom recovery, and *does* provide recovery-type functions. It's conceivable that you could install Magisk *in* a custom recovery. Somebody would have to establish the protocol so you could control which program gets control when you boot a funny way.

Try this: If your device is back to working, try "fastboot flash boot boot.img", using the original, unpatched, "boot.img". If that does not leave you with a working device, I'd say that's the first puzzle to solve. If it *does* leave you with a working device, you can focus on which Magisk, if any, is right for you.

Search this thread for MediaTek, I've seen mentions of special problems. I don't remember if there are solutions.
[Magisk] pndwal:
You can often enter Fastboot mode by pressing button combo at just the right Instant; may take many tries, or figure out if you can power device down to try.

Android 10 was good w/ Magisk 20.4 etc, and you can get earlier versions by clicking 'releases' in GitHub; point custom channel to corresponding json file if using flash patched image method... But I don't think you have any need to downgrade.

Yeah, John prefers flashing image method except for legacy devices, as TWRP method introduces many incompatibility issues. However, twrp was just recently made compatible w/ devices shipping with Android 10 (previously only devices updated from 9 etc supported), ie with new dynamic / logical partition scheme, so if newest twrp is available for your device it should work fine. PW

Very recently, MediaTek has been made basically compatible w/ Magisk, but there still may be issues. A current problem is inability to update Magisk using direct method from Manager (due to (security?) changes made by MTK); you will likely need to use flashing patched image or custom recovery Install methods to update each time. PW
[Magisk] pndwal:
Please see my first reply above re devices w/ ramdisk = no... Yes, there are many other than Sammy! PW
[Magisk] DiamondJohn:
i have the latest Pixel 4a firmware, obviouusly I am rooted, I do not pass safety net (never have since rooting, but I dont do banking etc so no issue), I am not running Xposed, yet my camera app works without issue. Take a logcat of the crash. Your are guessing, and guessing incorrectly.
[Magisk] BrimoFan123:
I was searching and found nothing about why root is lost when boot image is patched.

I tried also the following:

- remove only one module I use: NFC4PRA-GSI

- uninstall Magisk 20.4 using Magisk-uninstaller-20200323.zip

- flash stock RAMDISK.img

- flash latest Magisk 21.4

No root after the reboot.

Don't know even how to troubleshoot.

So I'm back rooted with Magisk 20.4, installed back NFC4PRA-GSI and additionally installed safetynet-fix-v1.1.1 - now I have even ctsProfile attestation successfully passed (of course basicIntegrity as well)

It looks I will stay with 20.4 even if I would like to be up to date withe latest version :-(
[Magisk] zgfg:
E.g. all Huawei phones with EMUI 9.1 (Pie) had to be patched to Recovery.

Probably also for EMUI 10 and higher but I don't follow anymore (besides, Huawei made it very, very hard to unlock Bootloaders, hence they are no more popular for rooting)

"Recovery mode" option is still present in Magisk Manager - see the screenshot
[Magisk] FourSilver:
It turns out that Ramdisk = yes is what is reported on the home screen for Magisk Manager. According to the installation instructions, the device "...is perfect for installing Magisk!" I read that as meaning that I can just patch the stock boot image, copy it into the platform-tools folder that holds the adb and fastboot packages. What about my interpretation needs updating?

Regarding entering Fastboot mode: I've been doing a fair amount of button mashing to see what options would take me to that mode once the bootloop is triggered; I've yet to find out what button combo works...
[Magisk] ndd53:
this is the same problem that I'm having with my Pixel 3XL: the manager always thinks it needs updating and I can't patch a file to get root. the option to do the direct install isn't listed. I'm pretty sure that the Pixel doesn't have the mediatek chip; any thoughts as to why this would happen?
[Magisk] Slim2none4u:
Not knowing what version you are running I can't say for sure but for me on my pixel 3xl, I have no issues with direct install, any of my 3 banking apps and I pass safety net. Gotta be something on your end.

I'm using the latest canary magisk on android 11 with edxposed 5.1.4_4669 yahfa master and riru core v23.3.
[Magisk] FourSilver:
Thanks for the information on how to retrieve earlier versions of Magisk. While I was able to install a copy of Magisk Manager 7.5.1, it seems that the package requires network connectivity to be used. Once I establish network connectivity, I am prompted to update to Magisk Manager 8.0.7 (which I guess defeats the purpose.)

Seeing that this is a brand new device and I have no personal data on it, how can I "downgrade" to ensure that I can root the device?
[Magisk] x.trinity:
Check if Hide Magisk Manager/MagiskHide is enabled.

Try with this little tool..Entering EDL mode from fastboot mode.
[Magisk] FourSilver:
According to the supported devices list on twrp.me, it appears that there is yet to be a TWRP package for the Atom XL (one is available for the Unihertz Jelly, though.)

I downloaded an earlier version of the Magisk package, and I noticed the "recovery" option you referenced. However, seeing that I did not have Magisk, installed, it didn't seem to be available for me to actually use to create an image. How can I use an earlier version of Magisk without TWRP installed?

I performed the ".\fastboot flash boot .\boot.img" test you suggested, and the device was able to return to a working state -- for the most part (wi-fi is suspect; no network connectivity.) Better than being stuck in a bootloop, I guess...

You mentioned that you were able to hand "Magisk a tar file..." for use in creating a recovery image. How exactly did you pass the file to Magisk?
[Magisk] FourSilver:
I think a link is missing... What is the tool?
[Magisk] x.trinity:
No ,its not a link, its a hint actually..

Google is your friend.
[Magisk] pndwal:
Then patching boot image is the correct method. 👍 ... Nothing above needs updating (unless, of course, it can't be made to work!)... But those helping didn't have this info, therefore asked you to check as this would possibly cause bootloop in case of no Ramdisk in boot image (but I think generally system would still boot without Magisk root).

There are various ways to enter Fastboot. You'd have to do research for you / similar device.I know some report Fastboot connection with completely blank screen under some circumstances. Some devices need a button/ buttons pressed when plugging in pc usb.

Of course, Fastboot could be broken, but what you described doesn't generally cause this. PW
[Magisk] pndwal:
As you said, using latest manager w/ channel set to Beta / Stable / Canary will always use latest Magisk available for each of these respectively if patching image.

Custom channel, However, is not limited to latest. It is just that, 'customisable', and by pointing it to json associated with any public releases (stable or beta), it WILL use the older version you specify as I mentioned. Using older Canary builds is more involved; you need to download, edit and privately host the json to make this work, but downgrading to Canary builds is not generally recommended in any case. PW

Edit: keeping latest manager will ensure greatest compatibility. I doubt there's any need to downgrade Manager to patch images w/ older Magisk unless using extremely old versions which may not be compatible.
[Magisk] pndwal:
Point to json in custom channel as I described

I'm guessing you have / can use Fastboot then?

As seen in installation instructions, this is the method for Samsung devices. I'm unaware of other OEMs packaging boot / recovery images this way. PW
[Magisk] ndd53:
hmmm. I uninstalled what appeared to be 8.07, rebooted the phone and installed the lastest canary app (downloaded from github). when I run it, it says

latest: f5593e05 (4835)(15)

installed: f5593e05 (4835)

and the install button is there. repeated attempts to install result in the same thing: the manager doesn't think it's up-to-date. I'm hesitant to do a clean reinstall of the factory image; does anyone know of any steps I can take to get past this? I've lost root, so I can't do any further cleaning behind the scenes. and, as the earlier poster said, I'm not able to patch boot.img any more.
[Magisk] Lughnasadh:
I believe that is the latest Canary manager. If there is an update there will be an "update" button. The install button there is normal.
[Magisk] J.Michael:
In the "pick and patch a file" option, you can "pick" a tar file. As @pndwal said, only Samsung seems to deliver software that way, so it's not useful to you. I only mentioned it in passing, because when I used it, I did *not* select the recovery option -- Magisk Manager was fiddling with several images at once, and seemed to know what it was doing. In your case, *if* you were trying to install in recovery, it might be important to check the option when handing Magisk the recovery.img file. Since you have since informed us that your device does *not* require Magisk to be installed in recovery, none of this applies to you.

re: EDL tool: I think he was saying that ADB or fastboot has some option to "boot" into Emergency Download Mode. As someone else mentioned, this might be one of those cases where you have to hold a dead chicken in one hand while connecting a powered down phone to the USB cable already connected to a PC running ADB (or fastboot). If you can find the right ritual, it's probably less frustrating than the "hold three buttons until precisely half-a-second *before* a certain message shows on the screen, at which point switch to four other buttons".
[Magisk] J.Michael:
Please clarify: Are you saying that it is possible to patch images with an older version of Magisk *without* using an older version of Magisk Manager?

Or were you saying that you did not think he would need to use an older version of Magisk, and so would not need an older version of Magisk Manager?

Like @FourSilver, I had been assuming that if I wanted to use an older version of Magisk, I would have to install an older version of Magisk Manager.
[Magisk] Didgeridoohan:
No. Any older version of the Manager will still use the same update channel as a new version, so it makes no difference. To downgrade Magisk using the Manager you'll have to use a custom update channel (or flash the zip manually as you would a module zip, I'd forgotten about this possibility), and then it doesn't really matter what version of the Manager you use (unless we're talking very old releases of Magisk or Manager).