yashsingh1/xdaforums huggingface dataset:
[Magisk] cridtohs:
On s7 edge here, Can you tell me how you know it works on Samsung Galaxy s7? Which rom? Your steps are also a little muddy around the flash/uninstall/reflash of 86.2 Xposed.

CAn you successfully recreate those same steps on your own device, try to format /data and complete format of every partition and reinstall from scratch. I see others have claimed success following your writeup but they are on less restrictive devices ( non samsung )

Is Xposed REQUIRED to get safteynet to pass? I have tried Hydra rom, Superman Rom, King Rom, all using Magisk methods to hide root. Hide root works to hide the root from applications, but I think saftey net is looking for other things besides root.

Magisk post also says it will not hide xposed or Supersu, so to use suhide for those. I have been able to use suhide to bypass root check on modded roms for other applications that check root, but Im really not 100% sure what Safteynet is looking for. Is it looking for a modified SystemUI? modified anything? Please explain [MENTION=4577747]zapahacks[/MENTION] what exactly you were doing and running in the alexis rom, what is modified in teh alexis rom? Are you running stock everything besides the arter97 kernel? Have you tweaked the UI or battery with 3minit?

Any help is greatly appreciated [MENTION=4577747]zapahacks[/MENTION]
[Magisk] Immortalis:
I was just writing the steps I took to fix my problem from my perspective as I had Magisk installed earlier, so that's why I had to remove stock-boot.img.
[Magisk] churchey360:
No root after flashing both files and installing magisk manager app?
[Magisk] churchey360:
It's my first time trying to use this root method i just wanna play Pokémon GO lol
[Magisk] bazantik:
touchscreen is not responding

The same problem with Motorola Moto X (XT1052, model 2013) with debloated stock ROM - my touchscreen is not responding after rebooting to the system. Logfile is attached. Thanks! :)

What I have done:

factory reset

reboot to recovery again

flash stock ROM (from XDA)

flash some mods (Modded Motorola Camera, Google Dialer, XT1052_Disable_Lockscreen_Rotation - from same XDA topic as downloaded ROM)

reboot to system

sign-in to Google account

reboot to recovery

flash Magisk v8 and phh's SuperUser r259

reboot to system

could not unlock lockscreen → turn off phone → boot into recovery → copy logfile
[Magisk] yochananmarqos:
What were "both files?" Did you install the phh superuser app from the Play Store?
[Magisk] churchey360:
I flashed magisk zip and phh superuser and i didn't read about that app but i installed magisk manager

---------- Post added at 10:11 PM ---------- Previous post was at 09:59 PM ----------

Idk i guess i just don't understand how this works I'll probably just use regular root for now on idc about pokemon go anyway
[Magisk] Has_anDroid:
nexus 4 androıd 7.1 work ?
[Magisk] SubZero5:
Why isn't the Magisk*.apk file zip -signed?
[Magisk] dedaol:
Thank you both @rodken and @zgfg for the reply. In my case the App Freezer disabled the hidden Magisk app, which I could reenable with adb shell pm enable <package name> . After that I confirmed that Magisk is still operational, and disabled the Magisk app again (to be able to use the banking app).
[Magisk] zgfg:
Do not keep that old Magisk app hidden and frozen - uninstall it , it will not affect Magisk (take its name, find it in Settings, Apps and uninstall that app)

After that when you reboot the new Magisk app will see Magisk, mldules, everything and then you can hide and/or freeze that new Magisk app

If the new Magisk app after reboot still does not see Magisk (assuming you correctly uninstalled the old app), then simply uninstall also the new app and then install again

App is only UI Manager for easier managing the Magisk. Everything (adding modules, managing DenyList, etc) can be done through Terminal by commands, but it's obviously easier to manage through the app

But only one app/mngr can communicate with Magisk at a time. As long as your old Magisk app is installed (even hidden and frozen) Magisk keeps its ID and think that one is the proper mngr, and does not allow new app to connect
[Magisk] pndwal:
It is.:

https://github.com/topjohnwu/Magisk#signing-and-distribution PW
[Magisk] Bkeinn_ll:
How do I enable Magisk again, after it disabled itself(N/A) in response to enabling Rooted debugging in the developer options.

This happened to me once before and the only option that did work back than was erasing the device back to firmware. I there a different way to enable Magisk again in the scenario.

I already tried disabling Rooted debugging -> patching magisk boot image -> flashing it.

Disabling developer options -> patching magisk boot image -> flashing it.

Reinstalling magisk manager -> patching magisk boot image -> flashing it.

Magisk Manager Log:
[Magisk] J.Michael:
I don't think Magisk ever disables itself.

I do not have "root debugging" in my developer options.

You have carefully avoided identifying your device and software versions.

How about that old standby, look for another manager app, with a different name, and uninstall that.
[Magisk] zgfg:
Magisk does not inject it's settings to Developer options.

You probably have a custom ROM, maybe of Debug build (there was recently a discussion here about LOS) and you enabled something that is in collision with Magisk

No idea why that debugging option in your ROM doesn't disable itself. Maybe you should consider dirty reflashing the ROM

Edit: Or by "rooted debugging" you mean "USB Debugging" (lost in translation)?

That should not affect/disable Magisk but when you connect by adb, on su, you will have to grant the root permissions
[Magisk] Bkeinn_ll:
Yea I am using LineageOs GSI.

I have an extra option for rooted debugging.
[Magisk] Bkeinn_ll:
Sony Xperia 1 with LineageOs 19.1 GSI.
[Magisk] zgfg:
See posts 52749 and 52750 about the LOS usersdebug builds (although it will probably not help you)

Sorry but next time you will probably either use the ROM's built-in root debugging capability xor (exclusive or) Magisk
[Magisk] zgfg:
New Monet UI is ugly, wasting real estate and does not work with Dark mode

Observe radio-buttons and Modules

Terrible
[Magisk] zyhk:
Hi, there. I don't know here is the right thread or not.

Is there anyone knowing how to write "sepolicy.rule" with respect to a property in a magisk module?

There is a bug only on A12 that "modules.usbaudio.audio_hal" via "AudioALSAHardware" cannot find a property "ro.audio.usb.period_us" (a tunable for the USB buffer size). I'm thinking a workaroud for this bug by writing a sepolicy.rule now. Although only for MTK Dimensity devices on A12 there is another way to reset the USB buffer size, i.e., by using a property "vendor.audio.usb.out.period_us", for other devices there isn't such a property.

Logcat output:

D/AudioALSAHardware(880): -setParameters(): card=1;connect=67108864;device=0
I/AudioFlinger(6037): openOutput() this 0x7d15455000, module 26 Device type:0x4000000,@:card=1;device=0;, SamplingRate 0, Format 00000000, Channels 0, flags 0
D/modules.usbaudio.audio_hal(880): [USB_AUD] adev_open_output_stream
W/libc (880): Access denied finding property "ro.audio.usb.period_us"
I/AudioFlinger(6037): HAL output buffer size 480 frames, normal sink buffer size 1920 frames
I/AudioFlinger(6037): AudioFlinger's thread 0x7d1160bd80 tid=8677 ready to run
D/modules.usbaudio.audio_hal(880): [USB_AUD] out_standby
[Magisk] zgfg:
Access denied looks for me as not running with root privileges

Official magiskpolicy documentation:

Magisk Tools

The Magic Mask for Android

topjohnwu.github.io

Sorry, cannot help more
[Magisk] zyhk:
Thanks for your reply. I had already read this document, but cannot understand that my attempt is even possible or not.

Um, I'll try replacing the property string in a USB audio related library with another allowed property string, say "vendor.audio.usb.perio" by a binary editor.
[Magisk] zgfg:
https://xdaforums.com/t/closed-disc...third-party-magisk-fork.4460555/post-87214847

Should I stay or should I go - probably will go☹️
[Magisk] martyfender:
I agree and with the new OneUI version, direct install is not working for me. I had to rename the apk to zip and flash it in TWRP. Then after rebooting I get the additional setup required message, after which the system reboots. However, this may be normal since I flashed it in TWRP, which, I believe, is no longer recommended. In doing this, apparently it installed the stub app instead. After that last reboot, everything is back to normal. I would be ok with the UI, if a normal UI version was also released or has the built in option to change it.

Thanks, @huskydg , for your continued efforts.

With these builds and using only magiskhide instead of zygisk, root is hidden from s-check when it is added to the hidelist. (denylist, actually).

On my other device with the official canary debug, with zygisk, shamiko, lsposed and and hide my applist and s-check added to the denylist and effective apps, root with s-check is not hidden.

Interestingly, on that official canary device, when I disable OEM unlock in developer options and reboot, root is hidden from s-check, with s-check removed from the effective apps in hide my applist. I still must have s-check in the denylist,though. The devices are Onn 8, 1st gen devices with Android 9, see my signature.
[Magisk] pndwal:
Did he get bored with the discussion?

Still pumping builds out but... +16hrs...

https://github.com/HuskyDG/magisk-files/commits/main 👀 PW
[Magisk] kostastnt:
After Google Pay became Google Wallet, I had trouble paying using NFC. Followed a guide here and installed shamiko. Shamiko disables Magisk's denylist. Wallet actually worked and everything is fine with payments.

Greek government created an app called gov.gr wallet. This app opens and instantly crashes. According to other users this happens because of root.

Is there anyway to "inform" shamiko to hide root from that specific app (like denylist)?

If that's not possible, can I use Magisk's denylist and uninstall shamiko and still have Google Wallet working? I am sure Magisk's denylist will prevent gov.gr wallet from detecting root.

Thank you!
[Magisk] zgfg:
When you use Shamiko, you have to disable Enforce DenyList

BUT STILL, you have to put apps like that one into DenyList (always reboot upon the changes)

It's been written here man times for various 'banking' apps

And for Wallet, consider using USNF v2.3.1-MOD that was posted last week in GPay thread
[Magisk] kostastnt:
Thank you for your time and your solution!

Actually I thought that using shamiko works like globally (for all the apps installed) and I thought since enforce denylist is off, denylist doesn't need to manually declare apps.

I declared gov.gr wallet at denylist and instantly worked!

I won't still use Displax's mod since my setup worked the whole week (more than 15 payments). Eventually will stop working and then I will try Displax's solution.
[Magisk] pndwal:
Shamiko hijacks denylist for convenience since it must be disabled anyway...

Nb. deny (reverts all modifications in a process) actually becomes hide (hides root/modification traces from a process) when Shamiko is used, ie. denylist is now really a hidelist. 🙂 PW
[Magisk] zgfg:
Btw, USNF does not come to replace Shamiko - you can install and use both modules together. With DenyList configured but not enforced (as dictated by Shamiko)

Then you can test the new Play Integrity API checker (USNF mod should help you to pass) - find it also in the GPay thread)

----

Since all changes are systemless, if you won't not like to stay with USNF:

- disable or uninstall USNF

- add Google Play Services aka GMS back to DenyList (USNF removes GMS from DenyList since USNF takes care of GMS in a different manner)

- reboot

Then you will have back your old configuration, Shamiko without USNF
[Magisk] pndwal:
Bit unsure why one would do this however...

While not sure which device is used but assuming later Mi 9T Pro or 10T Pro, kostastnt won't pass S/N this way even w/ needed gms processes in denylist!...

Did I miss that user had this config? I don't believe S/N can pass with this setup even with Shamiko!... PW
[Magisk] pndwal:
Thanks for MagiskKiller by Canyie (detector for pre Magisk 24) ...

... Interesting...

Passed on mine w/ 25201 as expected...

👍 PW
[Magisk] zgfg:
He did not mention GPay/Wallet. But he said he was happy with Shamiko only
[Magisk] pndwal:
🤔 No?... First words:

... You said:

Where did member say this was 'old configuration', and how did Wallet/payments work (or S/N pass) if originally had Shamiko without USNF?... Sorry if I've missed the real issue... 😬 PW
[Magisk] ipdev:
If your Magisk apk file is not signed..

You do not have a legitimate build.

Spoiler content hidden.

Spoiler content hidden.

Cheers. :cowboy:
[Magisk] m0han:
This app does not detect that my bootloader is actually unlocked. OK, it just wants to tell you that Magisk v23 was buggy; applications can easily detect it, so you should update it.
[Magisk] zgfg:
He reported a problem with certain app and that was solved, and he later wrote that he will take USNF if/when he would have problems with Wallet

I see no point that two of us discuss what he had/wrote/meant/wanted, etc (and clutter the thread). He can call 911 (112) when he needs help
[Magisk] titan-computer:
hi

i want to install custom kernel after magisk v25.2 but i get bootloop.

i can't do that before magisk because magisk won't be installed and it says boot image extra was patched by old unsupported

any fix for that?
[Magisk] pndwal:
So I don't why you haven't just said "Oh, right, adding Google Play Services (aka gms) back to DenyList with USNF disabled won't actually restore S/N", or simply "Oh, right, Shamiko without USNF won't actually work" rather than argue toss...

Correcting misconceptions here helps everyone.

You and I do it; you and I can take it. 😛 PW
[Magisk] pndwal:
The issue (1) here is probably 2SI refactoring (see below) making previous patched image incompatible. This means Direct install is broken, but uninstalling Magisk (or simply flashing unpatched ROM boot image) and doing initial patch/flash again will work to get you to 25+ Magisk, at least with stock kernels...

If custom kernel still causes bootloop, please say which custom kernel...

The issue (2) here is likely that Kirisakura and other custom configurations relied on Magisk to strip avb_key and avb flags for partitions... This function is no longer generally performed for 2SI devices in 25+ as magiskinit injection has been refactored; fstab is no longer patched, so AVB is now left intact...

You can try Magisk official instructions for patching vbmeta

https://topjohnwu.github.io/Magisk/install.html#patching-images

but this may not be enough to bypass AVB w/ some kernels / configurations... Check forums for your kernel for updates or config. methods...

Thing is, if you can get kernel to boot without Magisk, you should be able to root fine...

You'll find dev advice for custom kernels in GitHub issue comments I linked in several posts around the time of the 2SI changes in Magisk. See the end of this post:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87134821

this

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87068241

this

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87064251

this

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87061693

and other posts here around June 23.

🤠 PW
[Magisk] titan-computer:
i had galaxy note3 n9005 hlte with havoc os 3.5, magisk v23 and lolz v14 kernel.

now i have the same with stock boot and magisk v25.2 and i can't install lolz v14 or v17 after flashing magisk because of bootloop.

thanks for responding
[Magisk] pndwal:
Can I take it you did try w/ patched vbmeta? PW
[Magisk] titan-computer:
it doesn't support that i think, i can't find any vbmeta file a or b or something like that.
[Magisk] pndwal:
Latest Integrity Checker app (Play Integrity API Checker)

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87226157

Many thanks @1nikolas 👍 🎉 😛

Nb. There's an issue (known current):

Title text not shown on light mode (bug)

#2 opened 1 hour ago by 1nikolas

👀 PW
[Magisk] pndwal:
My result (expected):

Interestingly, devices w/ broken keymaster implementation may get this:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87226523

😛 PW
[Magisk] pndwal:
So seems device hasn't got separate vbmeta partition... So do you see this option?

If your device does NOT have a separate vbmeta partition, check the “Patch vbmeta in boot image” option

If not, you may be wrong... So you should try this:

(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

Nb. even vbmeta patching is not enough to disable AVB properly for some custom kernels... But worth a shot... PW
[Magisk] J.Michael:
No fastboot on Samsung.
[Magisk] pndwal:
Not for Galaxy Note 3, LV A 4.3 Jelly Bean?... I thought most legacy ramdisk Sammy's had fastboot... PW
[Magisk] J.Michael:
Have you checked to see if your custom ROM is pre-rooted? And check whether the pre-rooting involves Magisk.

I remember you explaining why you needed to install Magisk before installing the custom ROM, but I didn't understand. Could you try to explain that again?

If you have succeeded in installing Magisk on the stock ROM, I think the next step is to just install the custom ROM, accept that you will lose Magisk.

Do you have TWRP? Is Magisk installed in recovery? The problem might be the Magisk in TWRP trying to boot a custom ROM that has not been appropriately patched. Can you find anyone on the custom ROM thread who uses Magisk?
[Magisk] J.Michael:
Then you're way ahead of me. I saw "galaxy", thought "Samsung", thought "no fastboot".
[Magisk] pndwal:
But then you may be right... Seems Havock 3.5 is Android 10, so its supposedly converted from legacy ramdisk to 2SI now...

I did see some Sammy's have fastboot from userspace called fastbootd w/ A10 however (?)... But I'm not familiar... Not a Sammy user... 😛 PW
[Magisk] quadracer06:
Team Blind App has been notorious for detecting and blocking rooted devices, even blacklisting them for a week before allowing another attempt at opening. It had been working up until a recent update and now blind is looking for AND detecting "magisk" in the "system/xbin/su/" directory. Any help here on how to bypass?

Running latest magisk canary build on Android 13 beta 4. Magisk is hidden.
[Magisk] 73sydney:
I just test installed it

Same Canary as you, only using @Displax's latest Universal SafetyNet Fix (Mod) and Shamiko in terms of altering/hiding mods, app hidden on Deny List immediately on install, opened and registered with no issues, re-opened several times, rebooted, reopened several times.
[Magisk] quadracer06:
Awesome! Thanks for the quick response, I'll give it a go tonight....but I might have to wait a week given how they blacklist device ids :cautious: hopefully not
[Magisk] 73sydney:
Sorry, i forgot to also specify i have magisk hidden as well - i view that as a given, though just wanted to be clear :)
[Magisk] quadracer06:
It worked!! Thanks!!
[Magisk] zgfg:
Whoever remembers what it was (last time played here I think 12+ months ago), now the new version of Magisk Lite is released:

Magisk Lite

新版Magisk Lite已经开发完成，基于v25.2。 依赖logcat，日志系统不正常的设备禁止安装。 移除Zygisk功能。不支持模块功能，预期大部分模块会破坏系统。 移除隐藏应用功能，没有必要隐藏应用，直接卸载即可。 为避免滥用，仅内部发布，没有其它下载渠道，请寻找公开的进群链接，加群下载。

t.me

I didn't see the download but who is interested may take a better look (maybe search on GitHub, from vvb2060)
[Magisk] J.Michael:
If modules are not supported, why would modules break the system?
[Magisk] zgfg:
In June 2021 there was a similar warning about (potentially) not working/not supported modules in Lite but I did successfully test some modules:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85118965

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85130269

Observe that modules directory was lite_modules, not modules (at /data/adb).

Also database file was lite_magisk.db

How about the new version - IDK and I won't install/test
[Magisk] pndwal:
I think in Chinese parlance this just means 'don't expect modules to work / issues with modules won't be fixed / ... don't come crying to us... don't even think about mentioning it ... if you mention it, expect to be banned, mocked, derided, chewed up and spat out... Consider this brief note fair warning... idiots...'! 😜

Disclaimer: I won't be held liable for any perceived unfair treatment of any TG admins in this comment, and reserve the right to 'dish it out'... just as they (often) do...

Here's the original note on module issues in Lite from Lite TG (Chinese translated);

https://t.me/MagiskLite/4

👀 PW
[Magisk] maakosan:
I'm so sorry, I'm trying to use the search function for this thread, but for some reason, I'm getting results from the whole forum.

I got Magisk 24.1 installed (App is 25.2). I'm updating to 25.2 (Direct install), reboot and everything is fine. For a few days.

Then network services stop working requiring a reboot to get back up and running. And in return Magisk is back to 24.1..

I've tried to disable all the modules before updating = no difference.

Maybe one of the modules needs to be removed?

Modules:

ARCore/playground Patcher 2.1

Busybox for Android NDK 1.34.1

CloudflareNDS4Magisk IPv6 2.6

Debloater (Terminal Emulator) 17.3.3

F-Droid Privileged Extension2021-07-21

Terminal Modifications 1.4.6

Universal SafetyNet Fix 3.3.1

Or is there some known issue I don't know of?
[Magisk] IronTechmonkey:
Search is fubar and in many case automatically populates criteria with an asterisk signifying wildcard. Workaround in link in my signature. Web browser recommend for searching and for viewing signature.
[Magisk] Badger50:
Thread cleaned of OT "searching" posts. Please refer to the link in @IronTechmonkey signature for the appropriate workaround.

-Cheers: Badger50
[Magisk] IronTechmonkey:
As to your issue, I cant speak at depth to the technical details of Magisk and root but, approaching it logically, I would wonder about possibly competing SU eg from previous installation, or a damaged Magisk installation, or perhaps as you suspect some module or tweak (in particular regarding network). A test of a clean installation of Magisk (after uninstalling it) might be informative but is intrusive. That being said it might be wise to wait and see if some of the more knowledgeable people have any troubleshooting advice that would be less intrusive.
[Magisk] pndwal:
Is this OnePlus 7T? (2SI boot-type device).

I believe you'll find Magisk never successfully updated to 25.2 due to Magiskinit refactoring for 2SI which breaks Direct Install for many devices. (This has been deemed NOT a bug, but makes previous version patched images incompatible for re-patching w/ current magiskboot).

The solution for affected devices is simply to do initial patch (using unpatched boot image) and fastboot flash again...

Not sure about network issues, but it may be that something else is borked... Could be a module as mentioned, or could be something in Magisk config; deleting whole /data/adb directory before shutdown should fix this. - Magisk config incl. magisk.db will be rebuilt...

... I put a lot of information about the magiskinit refactoring here around June 23...

If you happen to use a custom kernel, you may have further issues due to this refactoring reverting verity disabling (AVB key/flag stripping); Check here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-87134821

Please give more device / environment details if this doesn't apply/fix your issue... Without this, my diagnosis here is largely guesswork...

🤠 PW
[Magisk] 13Sullo80:
1