Many different root-only actions involve mounting and editing files in the Android /system directory. Because there have been so many types of Android OSes, rooting techniques, and actual root solutions from the last decade, it has made it difficult to confidently determine if this is possible with my current root solution: Magisk with locked bootloader. From my understanding, Magisk is a completely "systemless" root solution, so by simply disabling Magisk and rebooting, *all actions performed as root are reverted.* This is important for me because I have verified boot with a locked bootloader via [avbroot](https://github.com/chenxiaolong/avbroot/) , so if there is any change to the system partition then it will fail to boot and the device will be bricked. So, with Magisk, is there a specific module that is required in order to "write" to the system partition systemlessly, so that it's not actually changing anything in the real system directory? Or does Magisk do this by default, and all I have to do is make my file edits from a shell like ADB root or Termux su, and they will be applied systemlessly?

My device is **Hometech Alfa 7LM Plus**. I made a mistake while rooting my device and now I can't boot it. I tried rooting my device, but TWRP did not support it, so I tried rooting without TWRP. I downloaded my device's stock ROM (not sure if it was safe or the right ROM, just the label was true) and copied boot.img (I don't remember the device's CPU model, so I am not sure I must copy boot.img or recovery.img or anything else) file to the device. Then I patched the stock ROM with Magisk in the device itself and flashed to the device patched_boot.img with fastboot. It flashed, but now I can't boot my device nor access recovery with power + volume keys or adb/fastboot (even if they don't connect or list the device). How can I fix that situation?

How to emulate binary program that reading port 53 will be redirected to another port such as port 10053. So the binary program still sees it as 53 but the actual port at top layer will be redirected to 10053. I'm using android non-root, the binary program is reading port 53 which it doesn't have DNS server installed and not permitted to listen such port (port 0-1023 is not allowed for non-root user) Is there any idea? Can proot handle that? Or is there another approach? Specifically, the binary program I mean is cloudflared. I downloaded cloudflared for aarch64 instead of from termux repository because cloudflared at termux is obselete, (it was working fine previously). That downloaded binary is trying to read port 53 for local dns server which it's not possible in android non root. Perhaps proot can do that?

I'm using Frida over USB debug and when I run frida-ps -U, I see zygiskd64, zygiskd32 and zygote appearing in the process list. This alarms me as some of my apps might be detecting those as an anti-root measure. Obviously, I'm rooted on Android 12 with Magisk, and modules Play Integrity, Shamiko and Lsposed installed. Is it possible that it's only me seeing the zygisk process but Magisk effectively filtered out (hidden) those from the apps are can apps see the same thing when they emulate running process? If so, is there a way to hide (or at least rename) those processes? Of course apps have very diverse range of anti-root measures, some are easily bypassed some are stronger, but I'm sure this is one of them.

This question is an [extension of this question where I want to perform the nfc checking part at the embassy](https://android.stackexchange.com/q/251982) . Which files do I need to change in the filesystem using root so I can download apps marked as incompatible on the Google Play Store because my phone lack nfc sensors ?

In order to get a specific visa, I need to verify my ɪᴅ using a government official app. I went on the play store and it first showed as not being compatible [because it requires ɴꜰᴄ which my phone doesn’t have](https://android.stackexchange.com/q/251483/87784) . So I manually downloaded the app and obtained an xapk because the single app consists of several .apk. So far no problems using adb install-multiple. I then launched that app to verify my ɪᴅ and then the app complained it wasn’t installed from the Google’s play store. The solution to this situation is normally to simply install the apk using pm -i com.android.vending apk. But how do that when the same app ɪᴅ consist of several .apk ? Please also note it uses com.android.vending.CHECK_LICENSE for the same purpose so that setting the installer after isn’t enough.

[Magisk](https://github.com/topjohnwu/Magisk) is known as a “systemless” root method. It’s essentially a way to modify the system without actually modifying it. Modifications are stored safely in the boot partition instead of modifying the real system files. I have looked around but did not find a sufficient explanation as to how it actually works. How is the root access gained and maintained? What exactly is the role of the boot partition and if it integrates with the system partition how it does it? A really detailed description of how it works lacks from everywhere I searched so it would be really highly appreciated.

I'm trying to mount a MicroSD. As I understand it, this should be done in the global namespace. Root - Magisk. I tried: - su --mm -c mount -t sdfat /dev/block/mmcblk0p1 /storage/0123-4567 - nsenter -t 1 -m mount -t sdfat /dev/block/mmcblk0p1 /storage/0123-4567 As a result, the root namespace is mounted, but nothing is mounted in other applications. How to mount to all namespaces?

Essentially, I have a Samsung Tab A7 that I rooted with Magisk, and it got damaged due to me dropping it, however, I have warranty and they will fix it for me. I was wondering if there is a way to save all the data into a single file, the csc one used when flashing the firmware, so that I can flash it to the new device after unlocking the bootloader and easily keep all data and root, without having to go through the hassle of rooting reinstalling and restoring data. Also, I do not have a custom ROM, only magisk.

Once every few weeks, I get this notification to update the device after unlocking my phone. I have automatic updates disabled in system settings as well. Hoping there is a service that a "root service disabler" app could disable to put an end to these notifications. My device is rooted and on Android 11.

on a magisk rooted Android 10 device com.whatsapp_preferences.xml ( /data/data/com.whatsapp ? ... can't remember that path now ) has been updated with non default parameters as I needed but it periodically gets overwritten *how to prevent that from happening.*
**what I did so far** even if reMount the partition as read write ( for my convenience I do it using total commander with root though I haven't tried I would assume it would end up the same way if I did it on command line ) it will not let me overwrite the original file with my modifications & but if I delete the original and copy the modified file that is allowed. funny...why 🤔 ? I did this and then chown ( to root ) & chmod ed it to 444 then force stopped the app cleared cache .new settings were working until next day I landed up with the same old file that it overwrote
**question**
now I am aware that for WhatsApp or any app to be able to write it should be the owner or maybe the owner should be everyone .. that is the case here as well but the issue is *how can I selectively prevent it from overwriting just one file* - implement this at file level ? alternatively how do I conceive a method that periodically overwrites the the original file with the one I have... after detecting that it has changed.
btw : my APK and data is linked to to second partition which is ext4 via apps2SD

If a systemless root is done, will software updates still appear in settings/show up as a notification that there is a new update available? In case it does show up, can you download and install the update directly from the settings app even though the phone is rooted? From what I read, systemless roots are great because they allow you to update a rooted Android without unrooting it. Is this the case or have I misread something? Another thing I was curious about is if you root your Android via systemless root, would the phone status stay "official" or will it be "modified"/"custom"? And would a factory reset unroot a phone that has been rooted via systemless root?

Chainfire (the developer of SuperSU), has come up with a new style of rooting devices on Android 6.0 Marshmallow and above. This is "**systemless**" root, and is all the rage right now. So, just in case anyone feels curious, I thought there should be some information about "systemless" root here for future reference. **The main question:** What is "**systemless**" root, exactly? This question has 2 ancillary questions, which are: 1. Where is it more applicable over traditional "**system-based**" root, and how is it different from it? 2. Is it better than traditional root? If so, how? A comprehensive answer to the main question along with the ancillary questions will be preferred.

My phone is HTC One M8 on Marshmallow stock ROM, rooted with Magisk. I've installed Orbot and noticed it doesn't work in transparent proxying mode when proxying all apps. It requires manual proxy settings in Wi-Fi or mobile network. If I proxy only selected apps, it works. I suspect it's due to DNS requests being blocked by iptables rules set by Orbot. They're trying to be sent directly, not respecting Orbot's proxy. How can I verify it and possibly fix it?

My phone broke just a bit too early. I am currently waiting for a Fairphone 4, but the delivery time is quite long, so I am stuck with an old Honor 9 Lite which we had lying around. But EMUI is really annoying, especially the systemui. Is there a way to replace the systemui with the AOSP version of that? I have root (Magisk), but since I won't be using this phone for too long, I wouldn't want to flash a custom rom.

As I understand I can get root access without installing a custom recovery with fastboot commands as described in the [Magisk Installation Instructions](https://topjohnwu.github.io/Magisk/install.html) . I have downloaded the Magisk app and under Ramdisk I do get a yes. The name of the device is indeed cattail which I have confirmed by running >adb shell in my terminal, screenshot posted: However I came across [this XDA forum post](https://forum.xda-developers.com/t/root-via-magisk-doesnt-work.4168263/) where it wasn't possible to get root access with Magisk and fastboot. [This post](https://forum.xda-developers.com/t/how-to-root-xiaomi-redmi-9c-functional.4200183/) appears to offer a solution but upon a little digging it seems that the instruction provided here cater to the device "angelica" but not cattail. Here is how I found out it was angelica: In the screenshot provided in the forum, you can see model name of the device is: >M2006C3MG while the model name of my phone is: >M2006C3MII Upon searching the different model names on the internet, it is quite obvious that device is different from mine. So here are my questions: # 1. Where should I download the firmware from to extract the relevant boot.img file? [1. This link](https://xiaomistockrom.com/xiaomi-redmi-9) or [2. This one](https://xiaomistockrom.com/xiaomi-redmi-9c) . I am confused because I had bought the Redmi 9 India (from Amazon) but apparently cattail is Redmi 9C. The first link(for Redmi 9) has an option having India while the second one(for Redmi 9C) doesn't. # 2. How do I even root this device? I'm unable to properly piece together all the info online and would greatly appreciate any pointers or guides. Searching for "how to root redmi 9 india" gives weird results asking to use Kingo Root and the like.

John Wu, developer of Magisk, published a blog [State of Magisk:2021](https://twitter.com/topjohnwu/status/1431889845199147008) , a couple of days ago which led to some confusion as to what is to be expected. Can the changes be explained in *non-technical* language? **Note**: This is a self-answered question as a reference, consolidating from various sources. Moderators are welcome to convert this into a wiki in case future developments are added by other users.

I don't have a pc and I want to root my motorola one fusion+ I've tried kingroot farmaroot

I have a rooted Lenovo Vibe K5 Plus running TWRP+Magisk+OpenGApps+ArrowOS(android v10).No MicroG. I installed Vanced Manager and Youtube Vanced in it(sometime after the February update) and it was working perfectly. I had given Vanced Manager superuser permission. Recently there was an update with 5 March 2021 security patch which I applied yesterday, since then Vanced seems to have completely broken while everthing else runs fine. Things I have tried - 1. Uninstalling Youtube Vanced from Vanced Manager, uninstalling Vanced Manager then re-downloading Vanced Manager from their GitHub releases page and reinstalling Youtube Vanced with SuperUser permission granted to Vanced Manager. 2. Re-Installing ArrowOs update from TWRP install and then wiping Cache/Dalvik. Trying same thing again but without wipping Cache/Dalvik. 3. Booting to TWRP and selecting Wipe > Advanced Wipe > selecting only Cache I open the App, click on a video and Youtube crashes. Here is the log - time: 1615626523312 msg: Native crash: Segmentation fault stacktrace: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint: 'Lenovo/A6020a46/A6020a46:5.1.1/LMY47V/A6020a46_S105_161124_ROW:user/release-keys' Revision: '0' ABI: 'arm64' Timestamp: 2021-03-13 14:38:41+0530 pid: 9210, tid: 9233, name: yt-critical3-1 >>> com.google.android.youtube )+128) (BuildId: 5048733c629f4c47102dc6d3e92b512f) #01 pc 00000000000400e8 /system/lib64/libmedia_jni.so (getCodecList(_JNIEnv*)+152) (BuildId: 5048733c629f4c47102dc6d3e92b512f) #02 pc 000000000003f4ec /system/lib64/libmedia_jni.so (android_media_MediaCodecList_getCodecCount(_JNIEnv*, _jobject*)+8) (BuildId: 5048733c629f4c47102dc6d3e92b512f) #03 pc 00000000002818c0 /system/framework/arm64/boot-framework.oat (BuildId: ba17fdaa4953a5a20b9a87065f5c2176fd5803b1) I got it when a notif like "Youtube keeps stopping" showed up and there was an option called 'Copy crash log URL'(del.dog/futhypock). Going to the URL on my phone showed this output.However typing it in my pc yielded nothing. The strangest thing is that uninstalling youtube vanced and then installing the official youtube app from the play store yields the exact same behaviour. Here is the log (del.dog/anothyfutt)- time: 1615627396186 msg: Native crash: Segmentation fault stacktrace: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint: 'Lenovo/A6020a46/A6020a46:5.1.1/LMY47V/A6020a46_S105_161124_ROW:user/release-keys' Revision: '0' ABI: 'arm64' Timestamp: 2021-03-13 14:53:15+0530 pid: 11931, tid: 11964, name: yt-critical2-5 >>> com.google.android.youtube )+128) (BuildId: 5048733c629f4c47102dc6d3e92b512f) #01 pc 00000000000400e8 /system/lib64/libmedia_jni.so (getCodecList(_JNIEnv*)+152) (BuildId: 5048733c629f4c47102dc6d3e92b512f) #02 pc 000000000003f4ec /system/lib64/libmedia_jni.so (android_media_MediaCodecList_getCodecCount(_JNIEnv*, _jobject*)+8) (BuildId: 5048733c629f4c47102dc6d3e92b512f) #03 pc 00000000002818c0 /system/framework/arm64/boot-framework.oat (BuildId: ba17fdaa4953a5a20b9a87065f5c2176fd5803b1) I couldn't make head or tail of what this log means. I tried searching for "msg: Native crash: Segmentation fault" and found this but I couldn't understand that either and the links they provided are Greek and Latin to me. I also found this but again understood nothing. How do I get Youtube Vanced to work again? Please help a newbie here who really loves Youtube Vanced. I will be happy to provide any further logs should you require them, but I don't know how to collect logs and would appreciate it greatly if you could point me in the right direction.

Device: itel A11, Android 6 Before the installation of magisk v22, my magisk installation was working fine, so I updated the magisk through direct installation and rebooted my phone but magisk manager wasn't detecting magisk. I tried flashing magisk on my boot image and flashed the patched image with fastboot and spd flash tool but magisk manager wasn't still detecting magisk. I updated to the latest canary version and tried the same thing but to no avail, so I tried flashing my stock ROM but replaced my boot image with the patched boot image still nothing. Today I came across this thread https://android.stackexchange.com/questions/231184/magisk-issue-device-rooted-but-magisk-not-installed?newreg=60441132722b41c0ae20cf4474d5477c that shows exactly the problem I have and he solved the problem by uninstalling the repackaged magisk manager, but now my problem is I flashed my phone and I doubt if the repackaged magisk manager will still be in the phone but why is magisk manager not still detecting magisk