yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Systemless changes are active only when Magisk was loaded with the module that makes that systemless change

If you do Factory reset you will remove /data/adb/ modules... hence also that module (but also all other modules, all user apps, all your settings, files)

It's much easier to disable or delete (toggles in Magisk app) the particular module (phone must be rebooted to complete the action) when you don't want it changes anymore - but not applicable when the module causes bootloop and you cannot run Magisk app

---

Bootloop protector module should find that certain module caused bootloop three times in a raw and then it disables that module
[Magisk] zgfg:
Of course RO not equals to SAR. My point was that not only the System is read-only but also the other 'system' partitions (SAR) either all being under / or all being under /system

You never have /system RO but not /vendor, /system-ext, etc - bcs, is SAR is RO, then all those partitions together are RO

And SAR filesystem is RO on all modern phones (and A9 certainly aren't modern phones)
[Magisk] pndwal:
Mmm... but I'm just pointing out that to state "since SAR is read-only ...you cannot write anything there" is not accurate and could confuse users with SAR ROMs and /System mounted RW... The statement '/system as rootdir (SAR) is read-only' is only as true as stating "Android is read-only". 😬

Sure, current stock Android (necessarily using /system as final rootdir) may be read-only as Google stipulates that all read-only AOSP partitions that aren't used by the bootloader must be dynamic (RO) apart from vendor-specific partitions in stock Android 10+ implementations, but it's beside the point; both Android (all generations) and SAR (A7.1 to 9.0) were not required to be locked RO, and non-stock SAR and 2SI "SAR" continues to be RW as does non-stock Android...

What is relevant to RO is whether shared blocks / dynamic (sub-super) partitioning is implemented... System as root simply isn't... PW
[Magisk] pndwal:
Latest Canary + Debug builds:

Magisk (d390ca2f) (26104)​

Lots of code is migrated over to Rust!

[App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

[MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation

Diffs to v26.1​

[MagiskBoot] Support extracting boot image from payload.bin

[MagiskBoot] Support cpio files containing character files

[MagiskBoot] Support listing cpio content

[MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

[App] Support patching boot image from ROM zips

[App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

https://github.com/topjohnwu/magisk-files/blob/cc3bbe7094928823c4d2f466ece8df72937068dd/notes.md

👍 PW
[Magisk] shoey63:
Still can't patch from payload.bin🤷
[Magisk] pndwal:
[App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

Fixes normal update Samsung A13 LV (S23 etc) devices by flashing Magisk patched AP binary... Thanks @dr.ketan, @BlackMesa123, @topjohnwu... 👍 PW
[Magisk] amk316:
hi

when using "Systemless hosts" model to mount "/etc/hosts" can i mod it to mount anther file ?
[Magisk] zgfg:
Structure of Magisk modules are described on the GitHub:

https://topjohnwu.github.io/Magisk/guides.html

In a nutshell, you can missuse Systemless hosts (or any other existing module).

Eg go to:

/data/adb/modules/hosts/system

Create a subfolder

system-ext/etc

And put some dummy test file there:

my_dummy_file.txt

Reboot and go to

/system/system-ext/etc

or equivalently to

/system-ext/etc

and find your dummy file mounted there my_dummy_file.txt

You will see it there only when booted with Magisk and when the module (Systemless hosts in this case) is enabled

Disable the module and reboot, dummy file won't be mounted. Also if you have TWRP, dummy file won't be there since the file is not hard-added
[Magisk] amk316:
will

i added the fallowing

/data/adb/modules/hosts/system/optics/configs/carriers/single/KSA/conf/system/cscfeature.xml

to run a modified version of cscfeature.xml but it did not work!!!
[Magisk] zgfg:
What is the System path of the file you want to modify, eg

/system/optics/configs/carriers/single/KSA/conf/system/cscfeature.xml

or what?

Be aware that Magisk mounts relatively late (at its post-fs-data script tine), ie, too late if you want to overwrite something like booting splash screens or so

Also, for some other changes, if you put too early the System will overwrite later while booting. Then you must use service.sh script to manually mount by

mount -o bind

and possibly by waiting until boot finishes:

until [ "$(getprop sys.boot_completed)" = 1 ]

do

sleep 1

done

You must play with. Study how the other modules work
[Magisk] amk316:
i want to mount this file

/optics/configs/carriers/single/KSA/conf/system/cscfeature.xml

i did it using "mount -o bind" script in post-fs-data.d and it work but i want to find a way the is not detected
[Magisk] zgfg:
I doubt that you have optics mounted to /system

If not, the way as with /system/etc/hosts will not work

Test in Terminal emulator (with su) like

ls /system/optics
[Magisk] amk316:
s23
[Magisk] zgfg:
As expected. Maybe with Magisk Delta (but it's outdated to 25210).it would work, eg Delta mounts and you have

/system/odm

but unfortunately not in Magisk (Canary 2610x), it's still only

/odm
[Magisk] pndwal:
Just in case, can we assume you had MemoryDetector in denylist and Shamiko active with that method? PW
[Magisk] Nergal di Cuthah:
Without knowing which apps the answer varies. For some it is enough for others it's a sign that root exists.
[Magisk] amk316:
yes and yes
[Magisk] J.Michael:
Is any of your reading in this thread? Have you noticed any of the posts where someone says "how can I hide this?", and then another post where says "I was able to do it this way"?
[Magisk] zgfg:
Long press on the notification and choose to snooze. Or go to Settings, Apps find the corresponding app, open Notifications and disable them

Generally it should work. I don't have Voicemail and don't know how Settings for the Apps are manageable on your ROM
[Magisk] J.Michael:
First, maybe I'm not using the right words -- I can't find anything called "Voice Mail" to look at the notification settings. I have gotten Voice Mail. I have seen indications that I have Voice Mail waiting. I just can't find corresponding settings. Or figure out which app is responsible.

What is it that bothers you? Having a notification in that pull-down window shade-like area? Having a visible mark on your lock screen? Or the noise when a new message is left?

If you can find the appropriate app, maybe you can set the notification to silent. If they won't tolerate that, maybe you can set a custom ringtone, and use an mpg of silence.
[Magisk] badabing2003:
Have you tried tasker?
[Magisk] JonnyG1980:
Hi all, I'm having some difficulty installing Magisk on my Xtrons (GS) IQ90MTVL headunit. From all the guides I've attempted to follow, none of them seem to cover the exact situation I have.

I've managed to extract and patch the boot.img from payload.bin, but my headunit seems to have a few quirks when it comes to issuing the command to flash it back from the PC. I can't access developer options in the usual way (via pressing the build number numerous times) instead I have to enter "ADBON" at the factory settings password prompt. I can then access dev options from the system tab and enable USB Debugging. However this does not persist after a reboot and I have to manually enable it again.

I get a USB connection sound and seemingly have connection via ADBlink and webADB.

As I understand it, once ADB connection is established, I need to enter fastboot and issue the command "fastboot flash boot c:\magisk_patched.img". However entering fastboot mode either seems to hang or has no ADB connectivity, entering bootloader mode results in a hang which I have to disconnect the power to my HU to resolve. Is there any way I can issue the command while the unit is booted or in recovery?

Any help hugely appreciated.
[Magisk] pndwal:
I doubt it without initial root...

Do you have instructions on flashing stock ROM/firmware?

Is bootloader unlocked?

Few devices will allow custom signed mods/images to flash without unlocking...

Some bootloaders, especially on hybrid equipment, will still allow you to flash custom images via fastboot or other 'download' mode, and possibly using EDL or equivalent (may need to research use of PCB test points etc to use this mode) without USB debugging set AFAIK... Could be worth a shot if you're B/L unlocked at least...

You may also be able to temp root by issuing fastboot boot magisk_patched.img... If it works and boots you can take Direct Install (requires root) from Magisk App to permanently root...

Others here may know more... Hope it helps... 🙂 PW
[Magisk] dr.ketan:
Try this

data/adb/modules/hosts/optics/configs/carriers/single/KSA/conf/system/cscfeature.xml
[Magisk] JonnyG1980:
Hey, thanks for the reply. I don't have any instructions on flashing ROMs on this device beyond just doing it via recovery, which I just did with a newer FW prior to attempting to root.

The bootloader is unlocked however, are you saying I should attempt to issue the commands to root while the HU is booted and android is running, then reboot?
[Magisk] zgfg:
Magisk mounts only /data/adb/modules/<module>/system/... to /system...

If you put to <module>/optics, no use, it will be fully ignored

But Magisk does not mount optics to /system hence even what he originally tried did not work (maybe with Delta it would mount)

He later tested instead by 'manually' mounting by use of service.sh script but then he had the other issues (timing, and so). That's the other problem - you successfully mount the change but system apps overwrite with their defaults
[Magisk] amk316:
not working

fyi: i tried mounting other files in /etc/ than "hosts" and it works !!
[Magisk] dr.ketan:
Apologies, Forgot to mention, you needs to bind omc path.

amk316​

here sample module for /optics/configs/carriers/single/KSA/ CSC

Simply push your contents to this zip inside KSA/conf/system folder (modified & unfodified)\, exact path to push your files at

DrKetan_Optics_Module.zip/optics/configs/carriers/single/KSA/conf/system/*

(you can see Test.txt there, remove it after push your files at same place)

and flash zip from magisk module installer

It should work. Indeed I have used this method earlier.
[Magisk] zgfg:
Of course. You can mount that way to /system, /etc, /product, /vendor, /system-ext

That's the way to debloat system apps. Mount a dummy apk over some unwanted apk on eg /system/vendor/priv-app/...
[Magisk] dr.ketan:
We can bind mount
[Magisk] CrossFire01:
https://xdaforums.com/t/help-me-wit...er-flashing-magisik-patched-boot-img.4608653/

appreciate help :(
[Magisk] amk316:
thank you ... it worked

i appreciate your efforts

and memory detector cant find the modification
[Magisk] Leovre:
Hi, is there a way to uninstall magisk without app and without custom recovery? I've got root via patched boot image so no twrp, I've unistall hidden magisk manager as normal android app, but it has remain active, so when I install magisk manager and patched image it can't find root and does not work, probably there is still the hidden magisk active ...

Thank you
[Magisk] badabing2003:
Flash the stock boot just like you flashed the patched boot.
[Magisk] J.Michael:
If you think you still have a Magisk manager app, there is no point in talking about uninstalling Magisk -- Magisk is not your problem, the hidden (or misplaced) Magisk manager app is the problem.

Read more of this thread. If Magisk is still installed, you might be able to use "su" in a terminal emulator, and then use "pm" to list all packages. You might be able to identify the hidden Magisk manager app by its especially random-looking package name.

You really should be able to go through your app drawer and pick it out.

There have been reports that at least one of the "root checker" apps (TBChecker?) will actually identify an instance of a "hidden" copy of the Magisk manager app.

As a last resort, factory reset / wipe data will eliminate any hidden apps.

You might get more useful advice if you would identify your device, the version of Android it is running, the version of Magisk you installed, and the version of Magisk manager you are trying to use now.
[Magisk] tisinamik:
hello i flashed anx camera and miui core via magisk. i got black screen and did dirty flash. when i install magisk again got black screen again. can anybody help me pls. (not bircked phone boots perfectly bu cant even see the lockscreen)
[Magisk] Lord Sithek:
go to your recovery, file manager, find the folder in /data/adb/modules which belongs to ANX and delete it alogether. Should help
[Magisk] tisinamik:
my recovery doesnt support that (using lineageos recovery) can we do this with adb orrr do i must do this?
[Magisk] pndwal:
Basic methods for disabling modules (to fix boot issues) are found in Magisk FAQs (GitHub)... 🤠 PW
[Magisk] AssoorA:
I have the exact same problem. Have you been able to fix it I even went back to stock rom and locked bootloader but still no help. Thanks anyway.
[Magisk] zgfg:
I have unlocked BL, custom ROM, Magisk, etc, but Momo not complaining about SElLnux (particularly not about Permissive mode) - Enforcing is properly set in the ROM (and I do have V4A but not running in Permissive mode)

Momo reports me other standard findings (Magisk, BL unlocked, Debugging mode and LSPosed) - see the screenshot

Btw, check both for ro.build.selinux and ro.boot.selinux, getenforce, and cat sys/fs/selinux/enforce (commands for Terminal emulator with su or adb shell su ...)

On the other side, who cares about Momo
[Magisk] Spartacus500:
Unfortunately, I did not find a solution 😔 My S7 edge Custom Pie 9.0 Rom NFE after a clean upload also informs that "selinux rules are modified"... After uploading Magisk 26.1, the only thing I was able to solve was to hide it in Momo_v4.4.1 "init.rc is modified", and change selinux rules are modified to permissive but i can't hide it 🤔
[Magisk] J.Michael:
Please confirm:

After installing a custom ROM

before installing Magisk

Momo reports "SELinux is permissive."
[Magisk] Spartacus500:
No, after installing custom Rom Momo shows "SELinux rules are modified"
[Magisk] J.Michael:
Sorry, I got it tangled.

My point was you seemed to be complaining about what Momo complained about immediately after installing the ROM. If there is really any reason to care what Momo reports, I think that particular complaint should be addressed to the producer of the ROM.
[Magisk] pndwal:
That's surprising... Do you mean selinux issues are detected when completely stock?...

If you have a(n irresponsible) ROM with security enhancements disabled (selinux permissive) you often can't switch it on... Even if you can, things often break as the ROM is half baked (permissive allows stuff to work for development/testing only before those functions become compatible with security features and such builds shouldn't be released publicly)... Users should always select a (responsible) ROM that boots w/ selinux enforcing by default.

The switch will work fine the other way (running permissive on a good selinux compatible ROM) for testing apps etc...

In the case of S7, I know there are LineageOS ROMs available (not sure if these are official) that fix broken Zygisk (by porting a kernel without the systemcall issue when executing an ELF from /proc)... Guessing these would properly implement selinux. 👀 PW
[Magisk] s--c:
Is this still working for anyone? I'm getting error when trying to uninstall magisk to restore images - saying no backup found? Using pixel 6 with latest stable stock android.Sorry if this is wrong thread to post
[Magisk] pndwal:
Installing Magisk (as .zip archive from modules page) to a previously patched boot image will generally be just a 'clean' as patching a 'stock' (unlatched) image... It's usually the Magisk config files in /data/adb that may get corrupted, so you can skip the 'restore images' step...

Not sure why original boot image backup is missing... Maybe you installed Magisk from a custom recovery and it wasn't created? (encryption issues, other?) 🤔

... You could also simply flash original boot image from fastboot (also vbmeta if you altered that)... I believe these are the only partitions flashed generally in recent Magisk... Or, to be more sure, dirty flash complete ROM... This is effectively the same as Magisk's 'Uninstall Magisk, restore images' function. 👀 PW
[Magisk] s--c:
Okay thanks will try skipping that step. I haven't used custom recovery.

Edit: it worked pndwal 👍
[Magisk] pndwal:
Latest Canary + Debug builds:

Magisk (ee34f775) (26105)​

[MagiskPolicy] Fix patching extended permissions

[MagiskPolicy] Support more syntax for extended permissions

[MagiskPolicy] Support print out the loaded sepolicy rules

Diffs to v26.1​

[MagiskBoot] Support extracting boot image from payload.bin

[MagiskBoot] Support cpio files containing character files

[MagiskBoot] Support listing cpio content

[MagiskBoot] Directly handle AVB 1.0 signing and verification without going through Java implementation

[Daemon] Make daemon socket a fixed path in MAGISKTMP

[resetprop] Support printing property context

[resetprop] Support only printing persistent properties from storage

[resetprop] Properly support setting persistent properties bypassing property_service

[MagiskSU] Support -g and -G options

[MagiskSU] Support switching mount namespace to PID with -t

[MagiskPolicy] Fix patching extended permissions

[MagiskPolicy] Support more syntax for extended permissions

[MagiskPolicy] Support print out the loaded sepolicy rules

[App] Support patching boot image from ROM zips

[App] Properly preserve boot.img when patching Samsung firmware with init_boot.img

https://github.com/topjohnwu/magisk-files/blob/5749c1d095d187b516dd4d10669fb905af0e134e/notes.md

👍 PW
[Magisk] carlese:
Hi guys, since I can't install Viper4Android with 26.1 (stuck at installing magisk module), did someone try with canary? The other option is downgrade but I don't want to do it..
[Magisk] zgfg:
Using V4A repackaged with Canary 26105 (and previously 26104, etc) with no problem.

If you refer about Stable v26, IDK (and I never use Stable - if it comes with a bug, you can waits for months until it would be solved)
[Magisk] carlese:
So to update do I just download the canary apk and overwrite? It should ask for direct install?
[Magisk] WhoIsJohnGalt1979:
Yes and Yes?
[Magisk] zgfg:
Canary is newer, direct install should work

But you should try with V4A Repackaged and 64-bit Beta (re-ingeneeered), and you must set Legacy mode

More details in V4A threads. Eg, if your ROM requires 64-bit drivers, only that 64-bit Beta will work. If not 64-bit but still drivers in other folders than in the old ROMs, you must use Repackaged. Old V4A-FX, three or for years old, does not support them
[Magisk] sawdoctor:
Not viper but have you thought about jamesdsp? It's very similar and compatible with viper DDC files
[Magisk] carlese:
I tried it now, still not working on my poco f5.. V4A Stuck at 2/9 installing magisk module..
[Magisk] user_hajime:
How install magisk 26.1 in LDPLAYER
[Magisk] J.Michael:
You probably can't.

Find out how to install a custom ROM in LDPlayer, then we'll talk.

Also, there are posts on Reddit saying LDPlayer contains malware.
[Magisk] user_hajime:
So I'm looking for another emulator custom rom?
[Magisk] J.Michael:
Try not to write inside a quoted post.

I don't understand "I already know by changing "vms" in the ldplayer folder".

From the little I just read about LDPlayer, I don't expect you to be able to pick an operating system -- the emulator comes with some version of Android. If you can't "install" a ROM in the emulator, you can't talk about installing Magisk -- Magisk is "installed" by modifying partitions so when the device boots, Magisk code gets control.

I am not recommending a ROM, and I was not saying that you need to use another ROM. I was saying that if you know how to install another ROM, then you know what kind of file you have to provide to "install" another ROM, and at that point we can talk about how you might be able to modify the ROM you are already using to include Magisk.

Maybe you should explain what you are really trying to do. Someone here might be able to explain how to do it. You might not have any use for Magisk.
[Magisk] tuxayo:
Hi :) About the Custom Recovery installation method :

Can we fear loosing data due to Android not booting? Or just magisk not working?

I need magisk to have root to use neobackup to make reasonably complete backups. But to have root I have to install magisk which looks risky (getting the wrong files to patch boot image, patching it wrong) the custom recovery method is much more fool proof. Then the question is what are the risks of the method itself?

I'm a bit in a catch 22, need root to make good backups, need good backups to have root.

Unfortunately TWRP can't decrypt data on a Fairphone 3 (and most other phones on recent Android) so AFAIK, I can't use TWRP to make a backup.
[Magisk] pndwal:
Matter of knowing your device rather than Magisk issues in most cases...

Since Magisk only normally patches boot image now it's generally very easy to fix a bad build or installation; simply flash unpatched boot image to restore boot... In some cases, flash vbmeta also, or simply dirty flash ROM...

Having said this, some devices are notoriously easy to brick or to require full data wipe to restore... Eg MediaTek based Xiaomi devices, but there are issues installing anything, even TWRP... I twice needed to pay someone with an 'authoeised account' to unbrick Redmi 6 devices after simply flashing compatible TWRP!... These devices were so bad many Devs stopped custom development support as they couldn't afford to pay for unbricking constantly either...

But many devices incl. Qualcomm based Xiaomi, are much more reliable and user can restore bad flashes in most cases...

Samsung devices have their own caveats, and if you don't take note you risk losing data... I believe there may be similar caveats even for modern Pixel users...

So it's really impossible to answer "Can we fear loosing data due to Android not booting?" with a NO... Modding is/has always been fraught... For many of us it's a relatively safe hobby though, although probably most have been burned getting to the point of understanding the pitfalls of most mods and being confident...

Magisk itself is pretty 'safe', especially being a systemless solution, but like any other mod you should do your due diligence; know how to restore images, recover your data (back up first somehow or other) as well as from bad module installations before you start...

🤠 PW
[Magisk] HippoMan:
I don't know much of anything about Xiaomi devices. Is anyone willing to suggest a Qualcomm based Xiaomi device (name, model number, etc.) which is likely the be one of the more reliable devices to root with Magisk nowadays?

... and would such a Xiaomi device be TWRP-able?

If this subject is considered to be OT, then feel free to take it to private messages.

Thank you very much.