yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Come on mate... That's not what it's about. It's the page after page of off-topic social media/Telegram style posting, that clutters the thread so much that discussions about actual Magisk stuff gets even harder to find (in this impossible to search mammoth of a thread), that is the problem.

I'll keep an eye on things (since I pretty much live in the Magisk forum anyway) and let you guys know if it starts getting out of hand.

Nice try at satire though... It baited me hook line and sinker. :ROFLMAO:
[Magisk] rodken:
Which device are you successfully running this on?
[Magisk] Eng.Raman:
The latest alpha 61783ffc is running well also on my device ( Realme X2 Pro - android 10 ).
[Magisk] zgfg:
So far so good

However, I cannot be happy that Zygisk cannot be hidden (it acts like a time bomb)
[Magisk] mikwii2000:
Hi everyone, and thanks the developers for this great app. I need help because I can't hide the magisk app, the option isn't available/clickable in the Magisk settings as I show in the screenshot. I'm running an Android 11-based AOSP custom rom (Derpfest).

Thanks to anyone that can help ;)
[Magisk] 73sydney:
Answered in private, cheers
[Magisk] jons99:
on the pixel 5 it's running very well so far
[Magisk] rodken:
Can you elaborate as to why you need to hide Zygisk?
[Magisk] zgfg:
Any banking app etc can exploit that way to detect root in the future (not saying that there were not other ways to do it, but now it will be one more way, and the source code how to do that is also publicly available)
[Magisk] J.Michael:
If you mean, make the bootloader have no interest in booting recovery, that wouldn't help you. Magisk hijacked recovery, Magisk *needs* the bootloader to load "recovery", which is now really Magisk. Once Magisk gets control, Magisk chooses whether to keep control or to turn control over to the original "recovery".

If you mean, make Magisk *always* keep control when booted as part of recovery, in theory it would be trivial: just change the "if" test. I keep hearing that Magisk is open source, so all you need to do is checkout a copy and make the change.

In practice, I don't like my odds. I don't know your background, so I can't guess your chances. Rotsa ruck!
[Magisk] zgfg:
And WebView works (again) fine with 61783ffc
[Magisk] ipdev:
Requires the Update Channel to be accessible.

(You have to be online to hide the Magisk app. 😞)

The update channel has to be set to the Magisk app version you want to install.

Using vvb2060's alpha builds, it will be pointing the the version released to github.

vvb2060 [magisk_files] - GitHub - alpha - Link​

From the screenshot, it appears you set the Update Channel to Custom Channel.

The Custom Channel is not set so no online version can be found.

Cheers. :cowboy:
[Magisk] pndwal:
(Alpha is for mavericks only! 😬 )

As already mentioned, it's fine at present w/ caveats mentioned re. ease of Zygisk detection which vvb2060 has stated is impossible to hide, at least at present.

I changed back to USNF 2.1.1 & Riru (last build didn't like Riru for me), enabled LSPosed too, updated Magisk / rebooted and all seemed good; SafetyNet pass, stable etc.

On next reboot SafetyNet failed inexplicably however. --> disabled Riru and USNF, rebooted, Reinstalled USNF 2.1.1 for good measure, enabled Riru, rebooted...

--> SafetyNet passing, system stable, SafetyNet survives reboots even with LSPosed, webview fine, no further issues.

@vvb2060 seems to be restoring just enough of the revoked MagiskHide commits to allow SafetyNet pass ATM, and there do seem to be more mod traces being detected. I can't even seem to hide 'MagiskHide' (aka MagiskDeny) any longer. See screenshots.

I'm guessing others may need to supply modules (made more powerful by Zygisk at least) or other solutions for hiding these, and I don't assume even SafetyNet will pass without at least an updated USNF in future TJW builds. Hiding Zygisk itself may be a tall order...

😜 PW
[Magisk] mikwii2000:
Thank you for your time man, that solved my problem!
[Magisk] Lefteris Fragiadakis (Frago):
News! Just created twrp, all night was working and now is ready, let's see now what I can do with magisk!
[Magisk] Stillhard:
Tried newest alpha, zygisk = No, ramdisk = yes, denylist(s) active and running (weird)

Reverted to 0ab31ab0-alpha, zygisk = Yes...

For now i'm happy with 9bf835e8-alpha
[Magisk] Lefteris Fragiadakis (Frago):
So guys after tests I have to find out how I add squashfs support on twrp, cause I can't do much, what I saw is that when I rebooted to system magisk was not working like the first place, tried to boot to twrp and guess what, it booted to stock recovery, how? I didn't flash the stock recovery, I searched and I find out that when it booting to system everything I has flash goes back to stock, for this magisk don't work when I trying to boot with combo key, everything goes back to stock without flashing, so the patched recovery from magisk goes back to stock while booting, I will make more research!
[Magisk] pndwal:
Behaviour is pretty standard w/ stock ROMs (eg MIUI):

https://twrp.me/xiaomi/xiaomimi9tpro.html

Nb. as mentioned, installing Magisk zip installer from TWRP will only succeed if bootloader contains 'boot' ramdisk support to allow basic ramdisk added by Magisk to be utilised... Of course you may be considering other custom recovery tricks. 😛 PW
[Magisk] pndwal:
Interestingly, I had such issues with 0ab31ab0-alpha with Riru enabled, but issue is gone for me in 61783ffc-alpha...

You could try disabling Riru & USNF 2.x, rebooting, checking Zygisk status / settings, then enabling again; I needed this initially - actually uninstalled USNF, disabled Riru and rebooted before installing again... No issue since on RN8T.

Of course this may be a per device issue.

John and vvb2060 are still busy with implementation of Zygisk; this may help in next builds:

https://github.com/topjohnwu/Magisk/pull/4720

... merged with Commits on Sep 24, 2021:

https://github.com/vvb2060/Magisk/commits/app_zygote

... there'll be more too. PW
[Magisk] J.Michael:
...running weirdly? or it is weird that they are running?
[Magisk] J.Michael:
He showed us a screenshot of TWRP running.

Does he have to tell TWRP to protect itself?
[Magisk] J.Michael:
Please put more space between thoughts. Maybe an occasional period or carriage return.

What happens if you

fastboot boot magisk-patched-recovery.img

?
[Magisk] Lefteris Fragiadakis (Frago):
nothing,i have to find a way to convert SquashFS partitions to ext4
[Magisk] pndwal:
I guess if he already booted to recovery using key combo such ROM patching is not working / occurring.

There may be a number of issues:

Enabling 'Keep system read only' prevents such patching. (I guess there may be additional issues w/ modern shared-blocks filesystem too.)

ROM may also have harder verified-image-protection to defeat. Some who found twrp fails to patch simply flashed Magisk which also prevents overwriting recovery. (Likely won't help here.)

I suspect he may also simply have booted using 'fastboot boot twrp.img'. PW
[Magisk] jons99:
tried the new alpha and it broke riru which broke lsposed and safetynet not recommended at least if you want to use riru I went back to previous one for now
[Magisk] PokemonTotalWar:
That's because they toggled a switch to stop Riru from working with Zygisk in the latest build. Apparently it causes issues
[Magisk] zgfg:
You mean a0fe78a7-alpha that was released about an hour ago
[Magisk] PokemonTotalWar:
Yes
[Magisk] zgfg:
For me everything ok (I don't use and need riru): root, SN, V4A, WebView, you name it
[Magisk] PokemonTotalWar:
I'm not noticing any problems either. Was just making a PSA for anybody who does use Riru that it's not going to work anymore, and it's not a bug -- it was intentionally disabled. People are freaking out in the alpha Telegram over the "bug," and I wanted to head that off over here
[Magisk] rodken:
Could potentially become an issue for folks that rely on LSPosed?
[Magisk] PokemonTotalWar:
Yeah, if you use LSposed you're not going to be able to use it if you update
[Magisk] J.Michael:
Could you describe "nothing" in more detail? Does fastboot ignore the command? Does the device seem to try to reboot? Do you end up in recovery? Do you end up in Android with no sign of Magisk?

Why do you need to convert squashfs partitions to ext4?

Can you boot a Linux on a desktop computer? I would expect it to be straightforward to mount a squashfs image, create a new ext4 image, copy all the files. Maybe have to run as root to preserve all permissions and ownership.

If the problem is packaging the partition image, maybe you should look into Android Image Kitchen (AKA AIK).
[Magisk] Lefteris Fragiadakis (Frago):
Device try to reboot in recovery using the command, i unpack the system using macos, when i repacked was 900mb and didn't boot, the original is 2 gb, the twrp can mount system or vendor, i think something is hidden on kernel or bootloader, pioneer has done very clever system to keep the system closed
[Magisk] pndwal:
Yup, looks like w/ a0fe78a7-alpha (maverick 😜) users needing any Riru solutions are out of luck.

I'm guessing many of these modules will move to Zygisk base in due course.

Those using needing USNF 2.x for September Google server end change can move back to 1.2.0 and older fixes changing model props. MagiskHide Props Config module Force Basic attestation option with similar late 'device selected from list' matching OEM configured is probably the best of these option. PW
[Magisk] 73sydney:
Not being able to use Riru-Momohider is a complete non-starter for me :(

Ill be using Alpha 31 for some time to come it looks like
[Magisk] Stillhard:
I have tried w/o any modules

Toggled the zygisk button to enable, reboot, zygisk = No, but the button in settings stayed as toggled on, checked the logs, no trace of zygisk

Tried toggled on and added denylist, reboot, zygisk = No, checked the logs, still no trace of zygisk, but the denylist ran and active.

Reverting to 0ab31ab0-alpha, boom!!! zygisk = Yes, checked the logs, zygisk xhook was there.

Tried all alpha before 0ab31ab0-alpha too (with zygisk in it), all the same result with zygisk xhook ran.

It was weird they were running but with no zygisk
[Magisk] pndwal:
Seems mileage differs per build, per device, likely per ROM....

When I had conflict between Riru / Zygisk I had Zygisk option in settings disappear, but Enforce DenyList remained checked. PW
[Magisk] J.Michael:
I don't think you should be fiddling with "system" as part of trying to install Magisk.

Please confirm: You use Magisk app, with "Recovery" checkbox checked, to patch stock "recovery.img"; you "flash" the magisk-patched-recovery.img to the recovery partition; you try to boot towards recovery; Android comes up; the next time you check, the recovery partition contains the stock, unpatched, recovery.img?
[Magisk] Lefteris Fragiadakis (Frago):
Yes everything you said is correct, in twrp I spell it wrong, can't mount system or vendor
[Magisk] adehade1983:
I have problem with magisk 23.

I try install magisk many times before root checker show me "phone is rooted".

1. All YouTube video about install magisk showing installed magisk with modules to download.

My menu/options don't show modules to download.

2. Buttons for reboot not working.

3. On device settings/security/device administrator can't see Magisk icon.

4. When I use all apks root 3-5 times ask me about permissions and I need to click again allow (I have set always).

BUT ROOT IS WORKING

Samsung j3 sm-320fn
[Magisk] zgfg:
Please attach your screenshot from Magisk
[Magisk] adehade1983:
Do you want screenshots with English language?
[Magisk] DiamondJohn:
and what you are trying to show by each image. ie what you think we should be focusing on
[Magisk] Didgeridoohan:
Not necessary... It's quite clear that the last screenshot shows that the Magisk app doesn't recognise that Magisk is installed. So, something's wrong somewhere.

Generally that could mean that the Magisk app is installed to external/adoptable storage (it needs to be installed to the internal storage or stuff like this happens), or you previously had Magisk installed with the Magisk app repackaged with a random name and now the regular app isn't recognised as a trusted root manager, or something else...
[Magisk] adehade1983:
Previously safetynet not working and I installed magisk again. After second installation was something wrong with boot.img and installation any apk (from twrp. magisk. and system) was stopped. Now after third installation safetynet and root start working after fixing boot.img. But magisk not working correctly. Please help me. How to fix it?
[Magisk] jons99:
new alpha also don't work with riru I'll skip this one too
[Magisk] jons99:
you need to patch your boot img
[Magisk] pndwal:
Just uninstall Magisk App, then go to phone settings, apps, and check list there for another Magisk App instance, likely with custom name you assigned, or simply named "settings" etc. Uninstall this also. (Superuser and hidelist settings / modules are not stored in app data and will remain.) Reinstall current APK version... PW
[Magisk] hfam:
@Didgeridoohan, @pndwal, and all the rest, THANKS for all the help!!

It was as straightforward as indicated, and my Pixel 5a 5G is fully rooted on Magisk v23, SafetyNet fully functioning with riru+drag0n SafetyNet fix+MagiskHide. ALL banking apps work perfect, SN check passes, a rooted apps are perfect, I am SOOO happy, it went absolutely perfectly. No WAY I could have (or would have) tackled this cold on my own!

In a P5 thread, @jcmm11 was answering some concerns and I posted that I'd post a step by step over there for any help it may provide for the new 5a 5G users, so I'll come back and update this post with a link to that when it's ready (later tonight, UFC 266 main card is just kicking off, so later tonight for sure).

Cheers and mad respect to all you awesome selfless folks who make the Magisk world spin round, I'm so grateful.
[Magisk] eeeemc:
My Samsung A71 BANKING APPS not allowing me said my device detected rooted.

I have modules in Magisk such as : Magiskhide Props Config/Riru/Riru Enhanced mode for Magisk Hide/Riru LSposed/Systemless Hosts/Universial SafetyNet Fix.

I've properly installed <> restart device <> installed <> restart device.

I've turn Magisk Hide & hide Magisk with new apps new to the hide magisk. I've put BANKING APPS to the hide list.

Check Safety Net shows all PASSED in Blue color.

So I do not understand until which methods I can use in order to avoid BANKING APPS kicks me. ( used to be okay before Aug-2021 that I can use simple Magisk hide and BANKING APPS working without kick me )

Thank you very much., edmond
[Magisk] pndwal:
New Alpha w/ same TJW commit code (ie. doesn't merge new TJW code) out on Telegram channel.

Seems it includes new vvb2060 commit:

Allow fallback to /dev/pts · vvb2060/Magisk@45cc956

A Magic Mask to Alter Android System Systemless-ly - Allow fallback to /dev/pts · vvb2060/Magisk@45cc956

github.com

Would appreciate explanation from someone au fait with such commits; I'm not. 👍

I see devpts is a linux virtual filesystem directory used for terminal emulators. Is this a fix for TE? PW
[Magisk] zgfg:
I don't know more but AFAIK, it was related to the discussion on TG as on the screenshot
[Magisk] Didgeridoohan:
Try uninstalling the Magisk app. That's a very popular way of detecting Magisk, and even repackaging the app with a random name doesn't fully prevent it.

More:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] pndwal:
Yup, that's what tipped me to latest Alpha having merged commits from new https://github.com/vvb2060/Magisk/commits/pts branch.

It's hard to follow now that actual build release commits no longer appear in his Magisk repo.

I just wondered what that commit did, but it seems to be related to his other one there (already merged by TJW): Fix terminal on android 8 …

"No need to handle untrusted_app_all_devpts on modern devices, but devpts policy is different for older devices."

https://github.com/topjohnwu/Magisk/commits/master PW
[Magisk] pndwal:
And just in case you haven't cleared bank apps data, you need to do this after every failure / new countermeasure (eg added app to hidelist) is introduced.

... Also, you could give Riru-MomoHider a crack (replace Riru-Unshare):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85125319 PW
[Magisk] pndwal:
Latest Alpha Magisk cb4361b7-alpha

*** For Mavericks only! ***

Riru / Zygisk coexistence seems to be back!

🎉🎊⚡🥝🧀

Chinese Translated:

alpha update log

Magisk (cb4361b7-alpha)

● [General] Based on cb4361 b7, the content that has been merged upstream is no longer listed

● [App] Correctly process any data from magiskd

● [App] Support SharedUserld

● [App] Delete the backup file after restoring the boot image

● [App] Built-in current version update log

● [App] Use the local version when the stub cannot be downloaded, now it can be used completely offline

● [App] Switch to the modern time API of Java 8

● [DenyList] handle suspicious props

● [App] Update SafetyNet extension, update snet.jar version to 18

● [General] Add an obsolete cgroup v2 path

● [Sepolicy] Add execmem to allow zygote and system_server Hook

● [MagiskSU] If necessary, fall back to /dev/pts

● [Zygisk] Fix Circumstances that may not take effect

● [Busybox] Cancel optimization based on undefined behavior

● [General] No longer automatically unlock the device block

● [Zygisk] From the current situation, there is no crash report to prove zygisk and riru

Incompatible, temporarily cancel the restriction, observe the situation

Upstream update log

From 23.0 to cb4361b7

● [General] supports pure 64-bit devices

● [General] Support Android 12 emulator

● [Zygisk] Code Injection Framework

● [General] Remove MagiskHide

● [General] Support special simulator loading module

● [MagiskBoot] Support zImage format

● [MagiskBoot] Add zopfli encoder

● [Magisklnit] Support bootconfig

● [App] Repair installation function will now check the script under /data/adb/magisk/ is not updated

● [MagiskInit] Support some Meizu devices

● [MagiskSU] If the kernel supports it, use isolated devpts

● [MagiskSU] Fix the pts configuration code, now no extra sepolicy rules

●[MagiskBoot] Support v4 boot image header format

● [MagiskInit] Support opltus.fstab for some OnePlus and Opal devices

● [App] Update modules to be restarted, not allowed to be marked as pending deletion

● [App] Delete online warehouse

● [App] Add mounting information to the saved log file

● [App] Adapt to Android 12 API level

● [App] Display the waiting pop-up window when the app is hidden/restored

● [Stub] Open source obfuscation function

● [Script] Check and display the sepolicy rule folder of the module

● [App] Hide screen overlay for pop-up window, Android 12+ is required

● [App] Delete the floating bottom bar and change it to the general bottom operation bar

● [General] Support special compilation cache

● [General] Add rejection list function

● [App]Delete DOH

● [App]Delete SafetyNet

● [App] Allow the log page to be opened when Magisk is not installed

● [App] Display Zygisk status, add restart reminder

● [Zygisk] Correctly handle child zygote

● [Zygisk] Disable conflicting riru modules

● [Sepolicy] Fix Android 8 terminal cannot get root

👍 PW
[Magisk] pndwal:
cb4361b7-alpha report:

w/ RN8T, Stock MIUI, Android 10

Two reboots needed initially.

Zygisk & Riru w/ Universal SafetyNet Fix 2.1.1, LSPosed, Un-Share all working fine.

SafetyNet passing w/ SafetyNet Google Play Services process denied.

ViPER4Android FX Neon driver status normal.

With Zygisk enabled Riru-MomoHider causes instability / system crashes even when only app_zygote_magic hiding is configured. 😕

Great progress! 👍 PW
[Magisk] zgfg:
Webview also ok?

Edit:

Yes, it is, tested myself (see the next post)
[Magisk] zgfg:
Btw, I needed only one reboot (to system):

-updated apk

-patched the boot.img

-rebooted to TWRP to flash the patched boot img (leaving zygisk and denylist enabled)

-rebooted to system

And everything was ok, incl. the Webview
[Magisk] hfam:
Hey all,

As promised, I wrote up a step-by-step tutorial for the Pixel 5a (though it applies to about all the Pixels, much of it I used on my Pixel 2 over the past 4+ years):

https://xdaforums.com/t/system-root-passed-safety-net-pixel-5a.4335721/#post-85688427

I know it's a book, but I wanted to make sure I put it in everyday language and tried to make it so even a first timer could go through it and feel confident moving forward and getting root, passing SafetyNet, and update with system updates in the future with confidence.

Anyhow, it's my attempt to give something back to the community I've gained so much from and leaned on so many times for help. If it helps even one person I'll be happy.

Thanks again to the entire community, and particularly the folks who have been here helping tirelessly and without reserve to get everyone up and going. You all know who you are and I gave proper name attribution in the tutorial thread. I'm exhausted, so I'm gonna go grab some dinner, that took hours to write! hahahahaah!!

Be well everyone, SO happy my P5a is fully functioning, you folks are just amazing.

hfam
[Magisk] ipdev:
Some have been waiting..

Some have been using vvb2060's alpha builds..

I have been sneaking a peak by running personal builds from John's master branch. :sneaky:

Magisk - GitHub - Building and Development - Link​

A few days ago (23.Sep.2021), I was surprised when my OnePlus 6T passed SafetyNet. o_O

It has been about three or four weeks since it passed SafetyNet.

Problems I have run into..

Every now and then, something misfires on boot and Magisk is not active (Installed N/A).

Normally a reboot is all that is needed, occasionally I have to re-install magisk.

I ran into an old issue on my 6T (clean install) installing Magisk.

I had to flash a magisk patched image to both the active and inactive boot slot.

Need to test again with another clean install.​

​

Currently I have a few devices running these (sneak peak) build(s) and passing SafetyNet.

OnePlus 5T

Older device, does not have the hardware for hardware attestation.

Stock OnePlus OS 10.0.1 (SDK29)

Magisk (snapshot build)

MagiskHidePropsConf (Magisk Module)

Enable Zygisk

Enable DenyList

add com.google.android.gms.unstable to the DenyList.

Magisk is in /sbin so only needed to Deny .unstable​

Enable the MagiskHide props. option in the MagiskHidePropsConf module.

Reboot in between steps as needed.

OnePlus 6T

Stock OnePlus OS 11.0.0 (SDK30)

Magisk (snapshot build)

Universal SafetyNet Fix (Magisk Module)

Enable Zygisk

Enable DenyList

add com.google.android.gms.unstable to the DenyList.

add com.google.android.gms to the DenyList.

Reboot in between steps as needed.

Pixel 3a

Custom rom that passes SafetyNet on it own.

Installing Magisk breaks SafetyNet.

ABC Rom 11 (SDK30)

Magisk (snapshot build)

Enable Zygisk

Enable DenyList

add com.google.android.gms.unstable to the DenyList.

add com.google.android.gms to the DenyList.

Reboot in between steps as needed.

Earlier today, I setup an update channel so I could test a few more things.

Install update from online.

Repack (Hide/Restore) the Magisk app.

All worked. :)

Note:

I will have to wait until the next commit(s) to see if I can update while the Magisk app is hidden. 🙃​

---

So far The next step of growth and development of Magisk is looking great. :)

I am excited and eagerly waiting for the next canary build for proper testing. :D

Cheers all. :cowboy:

PS.

Some screenshots from my 6T. ;)

Edit (5.Oct.2021):

Please see my follow up post.

Post 48,294 - Link