yashsingh1/xdaforums huggingface dataset:
[Magisk] KalayZ:
Just updated from v8 to v9 via recovery.

Can't pass safetynet and my magisk log says this :

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Enabling systemless hosts file support

Mount: /magisk/.core/hosts

Enabling BusyBox

Mount: /magisk/.core/busybox

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

service: /magisk/phh/service.sh

phh: Live patching sepolicy

phh: Mounting supath

phh: Starting su daemon

** Removing tampered read-only system props

** Starting Magisk Hide

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

MagiskHide: Error occurred...

Did I do something wrong please help me.
[Magisk] westeight:
Started from scratch and can pass SafetyNet with the latest SuperSu (SR4), Magisk v9 and Root Switch. Xposed is enabled.

1. Uninstall SuperSu, Magisk, Xposed

2. Install SuperSu v2.78-SR3

3. Install Magisk v9, enable Magisk Hide

4. Install SuHide, SuHide GUI

5. Install Xposed 86.6

Reboot :cowboy:
[Magisk] Hammerhead2502:
Can you tell me how? What all did you flash? I have a nexus 5 by the way.
[Magisk] htb2050:
I am passing it on nitrogen os 7.1. All you gotta do is just remove root completely first. Search on how to do that. After that just flash magisk, phh super user and then enable magisk hide and reboot.
[Magisk] Hammerhead2502:
Thanks man! :D
[Magisk] Captain_Throwback:
You have to also hide Settings in Magisk Hide for AirWatch Agent to complete setup. When enabling Device Administrator, Settings is called, and will detect Magisk/root if you haven't hidden it from Settings during setup. After hiding Settings, I'm able to set up AirWatch, and my device doesn't show as compromised.
[Magisk] cherylbaker:
Sent from my SM-N910P using Xparent Purple Tapatalk 2
[Magisk] andrew2432:
Su hide only hides rotx not xposed. Rootswitch is all I know of that hides xposed correctly
[Magisk] Basic11:
Oh I'm not trying to hide xposed with SuHide. I'm figuring out how to disable xposed or hide because of snapchat and etc.
[Magisk] westeight:
Seems that passing SafetyNet is no guarantee of Android Pay functionality:
[Magisk] dimm0k:
any suggestions on why I'm not able to install ANY module? I've enabled both logging options in Magisk v9 and when I go to install any module from the Downloads or even custom ones created, none of them install... any suggestions? I've tried wiping my device and installing Magisk v9 from scratch, but no luck on my LGV10...
[Magisk] ghbuur:
thx for helping. but weird, just tried again and it still detects root. even airwatch agent. you mean just normal "settings" which has to be hidden? or what else did you hide? maybe there's something more. safetynet i pass (except cts profile), pogo is playable, so magisk seems to works..
[Magisk] fmotta:
I have the same exact problem/error

S7 edge sm-g935f
[Magisk] KalayZ:
Using the same phone thats why haha :p

So if anybody can help us I would be happy.
[Magisk] NYZack:
In other similar situations, this has been solvable by trying to add a credit card in Android Pay (click "Add a card," but don't actually one) before trying to use AP to make a payment.
[Magisk] thomasswan5547:
If Anyone could help that would be great, i'm running both suhide 0.55 and magisk v9, on fakenexus rom android 7.1.1 with the bluspark kernel.

Whatever i do it seems like I'm unable to pass safetynet, login to snapchat etc. Here's my magisk log, if you need anymore info please ask

** Magisk post-fs mode running...

** Magisk post-fs-data mode running...

Preparing modules

Bind mount dummy system

Bind mount module items

Bind mount system mirror

Mount: /system

Bind mount mirror items

** Magisk late_start service mode running...

** Removing tampered read-only system props

** Starting Magisk Hide

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

MagiskHide: [com.snapchat.android]

MagiskHide: [com.google.android.gms]

MagiskHide: [com.scottyab.safetynet.sample]

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

MagiskHide: [com.snapchat.android]

MagiskHide: [com.google.android.gms]

MagiskHide: [com.scottyab.safetynet.sample]

MagiskHide: [com.android.settings]

MagiskHide: Update process/package list:

MagiskHide: [com.google.android.gms.unstable]

MagiskHide: [com.snapchat.android]

MagiskHide: [com.google.android.gms]

MagiskHide: [com.android.settings]
[Magisk] psychatog64:
Will this work on the Google pixel XL now that we have root and twrp? Cause I saw in the guide that you have to use phh superuser so I'm curious to if this works or not
[Magisk] Nomelas:
Could someone walk me through creating a module for Magisk that does the following:

_build.prop changes_

change the following line:

ro.qc.sdk.audio.fluencetype=fluence

to

#ro.qc.sdk.audio.fluencetype=fluence

Then, add the following:

persist.audio.fluence.voicerec=true

persist.audio.fluence.speaker=false

use.voice.path.for.pcm.voip=true
[Magisk] HamsterHam:
I didn't realise that selinux permissive on 6P would stop safetynet from passing. Thought I would share that for anyone else troubleshooting. I either pass safetynet or use viper4android; dilemma.
[Magisk] J.Michael:
@badabing2003 saw an instance where the bootloop protector module was the one causing the bootloop.

If when you say "all modules were disabled" you meant "all modules other than bootloop protector", I think it would be worth trying disabling the bootloop protector module, as well as all other modules, and then installing 26.4 again.

(@pndwal swears by "direct install". I don't remember him describing situations where it doesn't work, unless there was a really big change to Magisk. Still, "manual patch and flash" is expected to always work, provided you are patching and flashing the right partition image.)
[Magisk] pndwal:
I've had difficulties with boot loop protector, particularly uninstalling it as it persists (or used to at least) after uninstall... Found that it actually patches boot image too, so isn't removed simply by uninstalling module... Had to fully remove module as well as start again with clean boot image...

I've never used it since especially as there was no clear documentation on how/what it actually patches and I was already concerned about the Devs highly experimental code in modules and Delta Magisk builds... Didn't want extra boot image patching without description and potential incompatibilities... I just ensured I can boot to safe mode on my devices to fix bootloops caused by modules if I need to.

Anyway, it does generally work to disable modules after several attempts to reboot so bootloop can be bypassed if modules were the cause... Bootloops can be the result of Magisk regressions or other issues at times, and Bootloop Protector won't help in those cases...

Direct install generally works, but there have been times when regressions or major refactoring (eg for 2SI fix that removed fstab and vbmeta patching; modern device users couldn't Direct Install to update but initial/fresh patching worked fine) where users have needed to patch stock/unpatched boot image fresh. (Patching previously patched images, eg using Direct Install, could result in bootloop.)

To be sure some module does not causing bootloop, it's a good idea to disable them before updates... Generally modules becoming incompatible occurs with ROM updates however.

🤠 PW
[Magisk] HippoMan:
Just a quick, tangential question: I assume that in this case, "disable modules" simply means to slide each module's upper-right button in Magisk to the left, thereby greying out each module's entry, and that it isn't necessary in this case to also click the "remove" button for each module ... correct?
[Magisk] DougMG:
Correct.
[Magisk] pndwal:
Disabling module leaves it's folder intact but prevents it loading simply by placing an empty file named 'disable' in the module's folder... Bootloop Protector does this as does sliding toggle, and you can also add this manually to disable, eg when have bootloop issue by using TWRP file manager etc.

FWIW, If you have USB debugging enabled in developer options you can alternatively connect your phone to your PC and if your device is detected (check by adb devices), enter ADB shell and run the command magisk --remove-modules. This will remove all your modules and automatically reboot the device.

👀 PW
[Magisk] ZG_DEV:
I gonna try disabling every module and try "direct install" but what if the method worked, will I be able to enable the modules again ?
[Magisk] ZG_DEV:
The module asks you during installation whether you want to patch the boot image or not, I choose "not to patch"

Thanks for the advice:)
[Magisk] pndwal:
Yes.

Glad to hear it became optional, but I wasn't offered options in older versions...

Welcome. 👍 PW
[Magisk] J.Michael:
If the only module that wasn't disabled when you got the bootloop was the bootloop protector, and disabling that as well eliminates the bootloop, then it is likely that re-enabling it will re-produce the bootloop.

Each of the other modules could also cause a problem. Be prepared to disable them. (Like @pndwal said, learn to boot to safe mode, or learn to use the file manager in TWRP, or learn to do it with adb.)
[Magisk] ZG_DEV:
All modules were enabled

There is no safemode in oppo devices:(

But okay I will try the file manager trick, but first I will have to flash "fix encrypted.zip" file because my data partition does not show up in twrp ( I am using unofficial one)
[Magisk] DougMG:
KernelSU repo is back up. Hopefully LSPosed and Shamiko are next.
[Magisk] zgfg:
OT here but since the app's thread is (temporarily) closed

Although expired, previously published versions of the app can still be used (writing this from v14):

- as suggested by developer, block appilix.com in eg AdAway (and make sure to accept Apply new configuration and reboot if necessary [for root mode]

- Settings, Apps, XDA Forum app, Clean Data

Then login again (in fact, I restored my Swift Backup for the app from the time before its expiration)

Btw don't let your old phones end like on the photo
[Magisk] m0han:
Wonder what is happening with the 'review' of that app. Like you mentioned earlier, the bar at the bottom (whatever that is called) is quite handy.

BTW, Would you happen to have that picture without the phones and the person's shadow in it? I think it would make a good wallpaper.

1 - Watched Threads, 2 - Watched Forums, 3 - Alerts, 4 - Home, 5 - Conversations, 6 - Bookmarks
[Magisk] zgfg:
Isn't this too trivial for detection?

:/ $ whoami
u0_a240
:/ $ id
uid=10240(u0_a240) gid=10240(u0_a240) groups=10240(u0_a240),3003(inet),9997(everybody),20240(u0_a240_cache),50240(all_a240) context=u:r:untrusted_app_29:s0:c240,c256,c512,c768
:/ $ ls -l /debug_ramdisk
ls: /debug_ramdisk: Permission denied
:/ $
:/ $
:/ $ cat /proc/mounts | grep magisk
magisk /debug_ramdisk tmpfs rw,seclabel,relatime,size=3685124k,nr_inodes=921281,mode=755 0 0
magisk /data/adb/modules/zygisk_shamiko/module.prop tmpfs rw,seclabel,relatime,size=3685124k,nr_inodes=921281,mode=755 0 0
magisk /system/bin/magisk tmpfs ro,seclabel,relatime,size=3685124k,nr_inodes=921281,mode=755 0 0
magisk /system/bin/magiskpolicy tmpfs ro,seclabel,relatime,size=3685124k,nr_inodes=921281,mode=755 0 0
magisk /system/lib/libzygisk.so tmpfs ro,seclabel,relatime,size=3685124k,nr_inodes=921281,mode=755 0 0
magisk /system/lib64/libzygisk.so tmpfs ro,seclabel,relatime,size=3685124k,nr_inodes=921281,mode=755 0 0

Or the other way (that will apparently also detect for KSU)

:/ $ cat /proc/mounts | grep debug_ramdisk
magisk /debug_ramdisk tmpfs rw,seclabel,relatime,size=3685124k,nr_inodes=921281,mode=755 0 0
[Magisk] Fredator:
Hello everyone,

i need some help, i probably did a mistake. Coming form a oneplus 8T to a oneplus 11 5G, i have rooted and setup everything but i realized that my Gcam was not working normally and Gcamator showed a message "Camlera2Api module is disabled on your device"

So i found a magisk module which was supposed to do that for me, jhangyu/magisk-Camera2-API

I flashed it with magisk, nothing happened, nothing new in modules, no change in Gcamator message.

i assumed it didn't work, so i searched Something more recent and found Camera2Api Enabler Magisk Module for All Android Devices. Same thing i flashed it, nothing changed nowhere, no new module in magisk either.

Now my phone has new unrelated problems, for example the apps usage time is now empty for all apps...

As they don't show up in magisk modules, how can i "unflash" those modules? Or undo what they did?

thanks a lot, any help appreciated 🙏

PS: From what i read these modules only add or modify one line in build-prop: “persist.camera.HAL3.enabled=1”.

But my build prop does not have this, neither modified or not

If i posted this in the wrong place, please let me know
[Magisk] x751sa:
Is this really?
[Magisk] HippoMan:
People who don't like devs who are "very emotional" should stop taking free software from those devs.

Or they should take it upon themselves to perform that development work and offer the fruits of their labor for free, irrespective of the way that other people might respond to them.
[Magisk] x751sa:
Well, is this true or not, I don't care about the rest. It is said to have been hacked and data protection.

It's bad right now anyway, so LsPosed, now this... or
[Magisk] HippoMan:
The reasons for the current removal of support for one software package (LSPosed) has been clearly explained. The reasons for the current removal of support for Magisk Delta (aka Kitsune Mask) are still fairly opaque, however.

... although I will make a guess that one factor (out of probably several) might be related to the flood of disapproval that the Kitsune developer seems to have garnered in response to some sexually vulgar, insulting comments he made to other developers.

I read somewhere (I don't recall where, unfortunately) that one of the people familiar with the LSPosed development effort supposedly said that LSPosed support might resume after the lunar new year celebrations.
[Magisk] x751sa:
okay, so argue among yourselves.

which magisk do you recommend? it should have zygisk and su-list...

my english is not so good. sorry
[Magisk] HippoMan:
If I'm not mistaken, the only Magisk version that offers SuList is Kitsune.

I've had success both with Magisk Alpha and TJW Magisk (latest versions of both).
[Magisk] J.Michael:
If all those "modules" did was try to edit build.prop, and they failed, you don't need to undo anything.

Have you looked at the modules? Maybe they are nothing but a "startup" or "install" script. You would be able to see what they were trying to do. You might be able to see why they failed to edit build.prop.

Where is build.prop? If you have a working Magisk, you can make your own module, putting a modified build.prop in the right path under your module's directory.

To completely undo what you have done, try reflashing the original ROM.
[Magisk] Fredator:
Thank you J.Michael,

Do you know how can i find if there is a "startup" or "install" script that is setup please?

I need to know how to proceed for that first. Modifying the build.prop is not a high priority thing for me, a stable system yes.

Then eventually reflash, it makes sense 👍
[Magisk] pndwal:
'Magisk Delta is dead' comment may just relate to confusion about the forks name...

People had been arguing that Delta became Kitsune, but just days ago it was still using this logo:

Now the logo seems to be gone from GitHub and any references to Delta, so maybe it's really now Magisk Kitsune?... And 'Magisk Delta is dead'?... PW
[Magisk] J.Michael:
First, maybe related to why it didn't work: I don't remember reading what happens if two "modules" replace the same file. So, in a terminal, with root privilege, try

find /data/adb/modules -iname build.prop

just to see if any module is replacing build.prop.

(I have a lot of trouble using "find". Do an "ls" of a module directory and repeat the "find" using a name you know is there to make sure I got the syntax right. Of course, if you type what I said and it lists any file, it's a safe bet that it's working like I want.)

As for digging into what a module does: As I understand it, a module is typically delivered as a ZIP archive, although it may have an extension other than "zip".

unzip -l somefilename

will list the contents of a zip file, no matter what extension is being used.

You might prefer making a copy of the file, changing the extension to (or just appending) ".zip", and then using a file manager like Mixplorer -- if you click on a zip file in Mixplorer (or in Windows Explorer on a PC), it will display the contents, and might even let you "open" text files.

It might be easier in the long run to make a new directory and extract the zip file to that directory, then just look around. When I said "startup" and "install", I was guessing at filenames. If you read the "notes for module developers" (name approximate, look at John Wu's github) you will probably find the real names. Or you can just see what names are provided by the module zip file.
[Magisk] Nergal di Cuthah:
Maybe to end the confusion of "delta" sounding too much like a form of tjw, though that's much more an argument for "Alpha" to change their name.
[Magisk] Fredator:
Answer:

# find /data/adb/modules -iname bu...

#[x] 0

It seems not

I've attached the 2 zips that i flashed in my 1st message (2 x 10kb). Maybe you can take a quick look. I'm far from an expert but I already checked their files, that's why i deduced they should hopefully only attempt to add a line in the build.prop config 🫣

No idea why they didn't...

Anyway, thanks a lot for your kind help 👍

Btw i have cleared data in the "digital wellbeing" app (I guess it's its English name) and the usage app list is working again 🤷

At least it seems that the damage is not dramatic
[Magisk] J.Michael:
Nothing I recognize as an attached file.
[Magisk] Nergal di Cuthah:
Zips in this post
[Magisk] DougMG:
FYI for anyone interested MRepo repository is back open.
[Magisk] fbirraque:
Do you mean https://github.com/MRepoApp/MRepo?tab=readme-ov-file ?
[Magisk] DougMG:
Yes
[Magisk] trivarialthea:
Hi.

I am trying to develop a module, and I have a few questions...

Is it possible during the post-fs-data phase to extract a file inside the module's zip to a system directory? If so, could anyone provide an example? Tried this one below, but that did not work.

extract "$ZIPFILE" 'filename in the zip file' "$MODDIR/path/to/an/folder/inside/the/phone"

Also, is there a way to show debug information in this phase, so I can trace what I did wrong?

Thank you.
[Magisk] osm0sis:
👀

From January 17th.

Looks like Alpha is going full fork. 😯
[Magisk] ihavenolifee:
It seems with all the new issues with play integrity I downloaded the FP downloader and PIF and play URL, but it loads a fingerprint that does not work with some apps. When I open them, such as my Amex app, it instantly crashes.

Is there a way to choose a different fingerprint or completely revert what I did?
[Magisk] J.Michael:
Why not just put the file in the module's "system" subdirectory?

There is probably a log file, and a way to write messages to it, but if you are providing a script which gets run, then you could redirect output (stdout and stderr) to a file of your choice.
[Magisk] aorifan:
Guys, I updated my mgisk to canary and installed below modules plus hide app list. But my tb checker failed for root detection. Device integrity is fine and wallet works. But all banking apps not. Can someone give some suggestions? Thanks.
[Magisk] sawdoctor:
What are you using to hide root detection and what magisk version? You have shamiko but it's not enabled so can't work but also says unsupported environment as well. So you may need to downgrade shamiko depending on your magisk version
[Magisk] aorifan:
I only used hide my app list to hide the root detection, nothing else. https://github.com/mModule/guide_hma#hide-my-applist-guide
[Magisk] Nergal di Cuthah:
Add tbchecker to deny list to get rid of su binary detected (since your shamiko doesn't work not sure if you have denylist enforced or not)
[Magisk] J.Michael:
Should Shamiko be listed as a Magisk module? Shouldn't it be installed under LSposed?
[Magisk] pndwal:
It's a Zygisk module. PW
[Magisk] aorifan:
I've managed to fix it by removing the last module. Everything is working fine now. Thanks!
[Magisk] aorifan:
Thanks, I removed the last module and it's working fine now.
[Magisk] Mitezuss:
Hi, how to add (for example)

my.prop.test u:object_r:exported_system_prop:s0 exact string

to

\system\system_ext\etc\selinux\system_ext_property_contexts

using magisk ?
[Magisk] J.Michael:
Are you trying to set the SELinux context of a particular system file?

Have you tried making a module that will overlay the file and setting the context of the file in the module directory?
[Magisk] amajamar:
I am attempting to install the latest canary build on my P8, as Shamiko won't update on the latest stable build. I have downloaded and installed (at least the notification says that it installed), but it opens only to the stable installed version, not the canary build. Am I not installing this correctly?
[Magisk] trivarialthea:
Thank you, that did it! I did not realise I can put files in the directories itself; I thought it was only for mapping.

As for debugging I found out you can click the diskette after the module is installed to get the full log (even with errors).

Have a great rest of the day!

@trivarialthea
[Magisk] Mitezuss:
1 . Wanna set a property contexts (on system_ext_property_contexts) (file context [for example on system_ext_file_contexts] is not same than property context [for example on system_ext_property_contexts])

Note both files can be found on= system\system_ext\etc\selinux

2. Is not working

Any idea? =/
[Magisk] J.Michael:
I don't understand what you are doing, and my tablet doesn't have the path you cite (no /system/system_ext), but I did find a /system/etc/selinux/plat_property_contexts, and it has lines like the one you wrote, so I'm going to say the same thing I said before: if you want to edit a system file, make enough of a Magisk module so you can copy the file to the proper place in the module's directory, edit the copy, reboot.

Just be prepared to be disappointed if it turns out that the system does not get the information from that file, but rather is just displaying it.

Also, backward slashes ("\") are DOS/Windows; UNIX/Linux uses regular, forward, slashes ("/").
[Magisk] Mitezuss:
1. About the / or \ (i quoted from windows... that is all)

2. You can find the file on \system\etc\selinux or ...\product\etc\selinux\ or ...\system_ext\etc\selinux\ (dont complain about the \ or / ... just copy&paste from windows)

3. I think magisk overlay the file after the file is read, so the changes are not applied

4. do you know about magiskpolicy ? maybe should use ? (i dont know really... maybe is just for sepolicy and not for set property context ? idk... just asking)

should be exist some solution on magisk... i think xd
[Magisk] HippoMan:
Please forgive me if what I'm about to write is already obvious to you. What follows is not a complaint about pathname separators. I just want to make sure that there is no confusion among any people reading these messages.

It's understandable that the \ ("backslash") convention for pathname separators might be used in documentation that's related to Windows.

Just know that Android uses the / ("forward slash") convention for pathname separators, so if you write commands that are meant to be run under Android, the following will not be properly recognized under Android:

\system\etc\selinux ... etc.

Under Android, you would have to write such pathnames as follows, irrespective of what might be written in Windows-centric documentation:

/system/etc/selinux ... etc.

Again, please forgive me if you already know this. Many people read these messages, and I want to make sure that this pathname-separator fact is clear to everyone.