yashsingh1/xdaforums huggingface dataset:
[Magisk] dr4go:
Thank you. I also gave it a try and now everything works.

What bugs me, though, is, that people still haven't understood what version numbers are for. Afaict, there are three different versions of 4c808089, where the first one is crap, I don't know anything about #2 and #3 again works flawlessly like any other alpha build before.

Especially with git it shouldn't be too hard to commit it another time or even reset hard and re-commit it with a different hash. Anyhow... complaining at a high level... I'm very grateful what the people behind the scenes do for us every day. 🙏🏻
[Magisk] requiiiem:
Thank you!
[Magisk] ChanceGPM:
I have a problem. After I install systemless xposed 86.6 i lose root access. How do I fix this?
[Magisk] dreamland2000:
For those wondering why even after using the hide gesture in this app, I've read in a couple of other forums that safetynet is now detecting unlocked bootloader's so even if the various root apps are hidden if you have your bootloader unlocked then that will likely cause the fail.

I may be wrong but I'm just going on the info I've found from around XDA.
[Magisk] Captain_Throwback:
There's already a Magisk module to get around that. You should probably catch up in the thread ;).
[Magisk] dreamland2000:
I've tried that and still doesn't work. I'm running stock 7.1.1 with magisk & the magisk phh su, with the hidesu option enabled and the module installed with the terminal every done.
[Magisk] Nekromantik:
I flashed magisk 8 and phh superuser but how adaway says it can't find root. Any suggestions?
[Magisk] Captain_Throwback:
There is no "hidesu" option, so not sure what you mean by that.

On a related note, I just updated the xSetProp module to only change the prop if it exists on the device, and I added in the ro.boot.flash.locked prop and as a bonus (especially for my HTC 10 peeps - I'm looking at you [MENTION=5957136]jollywhitefoot[/MENTION]) it also sets ro.boot.veritymode to "enforcing" as that prevents OTAs from being downloaded on some newer HTC devices.

I only tested it on my 10 and my A9, but it does appear to be working. I added logging into the Magisk log as well to track the progress, so you should be able to see what props existed and got set and which ones didn't.

So this may help for the people having issues manually setting the props. Or, it may do nothing, lol. So, try it or don't - up to you. I was having issues trying to get the module to install/update through the app, so you *may* have to flash it in recovery.

EDIT: Oh, it also includes a slightly updated version of the binary, thanks of course to [MENTION=2605798]nkk71[/MENTION] for his hard work on this!! Be sure to thank his posts!! :)

EDIT 2: Also, the next version will likely rename the binary, since "xsetprop" already exists. I think we're just going with "ro_setprop" for the new name/command.

EDIT 3: Seems the zip signing is breaking things, so replaced the zip with unsigned version. I don't understand the problem, but whatever :rolleyes:.
[Magisk] dreamland2000:
I'm mean the option in settings for hide magisk.
[Magisk] westeight:
How to install it? Magisk won't recognise it, and flashing gives an Error 1:
[Magisk] Captain_Throwback:
Log?

Flashed fine on my devices - you should even be able to enable zip verification.
[Magisk] :
6incher incoming. :silly:
[Magisk] westeight:
I:operation_start: 'Flashing' Installing zip file '/external_sd/HTC 10/Magisk/MAGISK-xSetProp-arm-v0.2.1-CPTB-signed.zip' Checking for MD5 file... Skipping MD5 check: no MD5 file found I:Zip does not contain SELinux file_contexts file in its root. I:Legacy property environment initialized. unzip: can't open /external_sd/HTC[.zip] ! Failed: Unable to extract zip file! Updater process ended with ERROR: 1 I:Legacy property environment disabled. Error installing zip file '/external_sd/HTC 10/Magisk/MAGISK-xSetProp-arm-v0.2.1-CPTB-signed.zip' Updating partition details... I:Data backup size is 11139MB, free: 9936MB. I:Unable to mount '/usb_otg' I:Actual block device: '', current file system: 'vfat' ...done I:Set page: 'flash_done' I:operation_end - status=1 I:Set page: 'clear_vars' I:Set page: 'install' I:Set page: 'main' I:Set page: 'clear_vars' I:Set page: 'main2' I:Set page: 'advanced' I:Set page: 'confirm_action' I:Set page: 'action_page' I:operation_start: 'Copy Log' I:Copying file /tmp/recovery.log to /external_sd/recovery.log
[Magisk] Captain_Throwback:
I attached an unsigned zip to the post. Flash that one instead (it might work through the app).
[Magisk] westeight:
Thank you. Installs fine through Magisk:
[Magisk] kraz01:
Anyone get this to work on t-mobile Note 5
[Magisk] Ninoh-FOX:
I am back XD

Xperia M5

unlock bootloader

custom kernel

/system partition clean, only edit host file and erase factories apk.

Magisk v8 (setxprop 0,2 module (ro.boot.verifiedbootstate green, ro.boot.flash.locked 1, ro.bootmode mfg), hidemagisk, ramdisk patch in data)

luckypatch google play mod in data.

systemless >> supersu 2.78 (.supersu > systemless=true, bindsystemxbin=true)

suhide 0.55 (no 06suhide)

xposed 86.6 (no check device module, rootcloak)

rootswitch 1.3 (stop all su services + ramdisk patch in su.d)

busybox 1.5

Enviado desde mi E5603 mediante Tapatalk
[Magisk] Captain_Throwback:
No, mine has always said unknown. That shouldn't trip anything, as all my devices say that stock.
[Magisk] yochananmarqos:
Same here. I noticed /data/magisk/.core/busybox is mounted to /data/busybox, but attempting to run any busybox command yields, sh: busybox: not found.

bullhead:/ $ su
bullhead:/data/data # echo $PATH
/magisk/.core/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin:/magisk/.core/busybox

I tried installing the BusyBox Magisk module from the collection thread, but Magisk did not recognize it as a valid module. Is it now depreciated in Magisk v8?
[Magisk] Captain_Throwback:
You should be able to run Busybox commands as long as you don't preface them with "busybox". All of the applets are visible in PATH when you check the box in Magisk Manager settings; however the busybox binary itself isn't there. If you want to be able to call busybox (and not just the applets), just copy (or symlink) the busybox binary from /data/magisk to /data/busybox.

From a root shell:

ln -s /data/magisk/busybox /data/busybox

And yes, old modules are likely deprecated if they haven't been updated to the new template or been posted to the module repo.
[Magisk] grep_i:
My mistake I meant Magisk obviously, sometimes I lost track in which thread I'm answering because a lot of people off topic or cross posting.

So you think the reason I could set it was that I didn't had the property at all ?
[Magisk] zgfg:
And new package name
[Magisk] baris7264:
Hi. can you help me ? I am using g710em v30h version. I patched the original boot_a.img file with magisk 24.1, but when I load it with fastboot, the phone bootloop every time. when i reload the original boot_a.img file it is fixed. I installed Ofox recovery, still the result did not change. can you help me ?
[Magisk] casouzaj:
Wow, this is something: I was running Magik Alpha. When it was renamed to Alpha, Zygisk was broken, for what I switched to TJW's Canary build. All that time, there was a banking app which refused to run ever since I unlocked the bootloader. But, the day after, when Alpha had Zygist fixed, I switched back to it, and, surprisingly, that banking app is running again.

Just my 2 cents!
[Magisk] zgfg:
Alpha changed the package name for the app

Just curious:

Did you try with Hide Magisk App on Canary - it randomizes the package name
[Magisk] casouzaj:
Thanks, Yes, I know it. Nevertheless, I won`t change things now, just for test purposes, since everything is working! Besides, I had faced trouble some time ago after hiding (renaming) Magisk Manager (can`t remember with which build, though) . After a reboot, it claimed that Magisk was not installed.
[Magisk] pndwal:
Very interesting issue / PR for fix merge from Juhyung Park, @arter97 (experienced arter97-Kernel / ArkTube dev) here:

Add f2fs tuning for unencrypted devices #5462​

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

Thanks @Stillhard for the heads-up!

The problem:

"f2fs being a LFS file-system, needs to perform GC [Garbage Collection] periodically...

Unfortunately, due to how Android init works, the logic to write [Timing for] gc_urgent_sleep_time breaks when the device is unencrypted. [As a result it] takes too long to GC all invalid segments in time, which results in long-term performance degradation.

(The fix for this is expected to ship with Android 13.) Moreover, f2fs-specific optimizations such as cp_interval and discard limit also breaks.

When Android added support for f2fs platform-wise, encryption was enforced to OEMs, so while this isn't a problem for production devices running unmodified OS, it is for rooted users."

Sadly, LSPosed ladies seem to have squashed this PR for now, but fix has been produced as a module by another dev:

https://github.com/topjohnwu/Magisk/pull/5462#issuecomment-1040950366

Interestingly however, the linked notes appended to the issue indicate that 10+ kernel / rom Devs have begun integrating the same code / fix in their kernels in the last few hours!

Those with ROMs (can include stock) running Magisk / unencrypted still experiencing long-term performance degradation may want to try the module.

Many thanks for the heads-up / research / code for fix / PR @arter97! 😀 PW
[Magisk] [Lemmy]:
I'm trying to upgrade MAgisk on an older Samsung S8+. I've already upgraded the manager app, which now shows me that it "thinks" magisk isnt installed, and when I try to install the latest version it complains "unable to check signature".

Any indeas for me?
[Magisk] pndwal:
Yup. You have this issue:

Magisk 24.1 Showing Installed N/A - Root Functions Intact #5339

This was fixed very recently by same commit that fixed this longstanding issue for older Samsung and other devices:

Magisk 22101 (22.+) not detected by Manager ("N/A"), but SU still working on Android 6.0 (+) Marshmallow with Samsung Note 4 SM-N910F TouchWiz, armeabi-v7a and other devices #4174

Problem was with busybox. Fix:

Make sure busybox can be executed recursively …

Busybox will execute itself. On some older Samsung devices, when it is located in /data, it will not have rights to execute other programs including itself. We should also relocate busybox in this case to workaround Samsung bull****.

See topjohnwu/ndk-busybox@bdc8655

Fix the "app doesn't detect installed Magisk" issue in #4174

canyie authored and topjohnwu committed 18 days ago

Fix is merged in Magisk master branch and already build in latest Canary Magisk, so download Canary from Magisk GitHub home page (or wait for next public Stable / Beta). 😛 PW
[Magisk] pndwal:
Latest Unofficial vvb2060 Alpha Magisk

"3rd party version of Magisk with telemetry and signature verification, less stable than Canary channels, no security guarantees, no availability guarantees, no privacy protocols."

Chinese translated:

alpha changelog​

Magic (e7c82f20-alpha)​

[App] Support SharedUserId

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

[App] Built-in current version update log

[General] No longer automatically unlock device blocks

[App] Adapt to Android 12L

[MagiskInit] Refactor the processing method of two-step startup

[App] Add crash statistics

[Script] Support init_boot partition

[App] Allow loading zygisk modules

[App] Delete unsuccessful install session files

[App] Front-end interface tracking ignores root pop-up interface

[App] Directly forward file stream when installing

[App] The update completion notification is also displayed when the stub is normally updated to the full version

[App] First try root installation

https://github.com/vvb2060/Magisk/b...3e79b3d147a/app/src/main/res/raw/changelog.md

Download:

https://github.com/vvb2060/magisk_files/tree/8d3a891c49cc727c6f369cc33aea30b70cce7a51

😬 PW
[Magisk] Stillhard:
Should make it bigger and in bold :LOL:
[Magisk] zgfg:
And something else - did anybody here have problem with the non-silent installation, regarding to their change

>> [App] First try root installation
[Magisk] alecxs:
I am facing strange issue with Magisk v23 on Android 10 - has anybody ever experienced avc denied for u:r:magisk:s0 secontext?

(kindly check my history for details)
[Magisk] ashish1989:
Looking for best method to block ads on my device, specially which can work on youtube

Anything available through magisk which we can check
[Magisk] Lord Sithek:
For YouTube - YouTube Vanced definitely. Other ads - AdAway maybe. Personally I use AdGuard which does not require root
[Magisk] ashish1989:
Using youtube vanced too, looking for options other than adaway and adguard
[Magisk] rodken:
You can try 'Energized Protection - Magisk'.
[Magisk] dr4go:
I believe (check yourself though, that's just out of my mind) that this was a problem of 23, which was fixed in 23.1.

If that doesn't work out, I'd suggest to try the last alpha build, which still includes MagiskHide - shouldn't be too hard to find in their changelogs. Then simply disable Zygisk and use it like you would on your 23 build.
[Magisk] alecxs:
I can't find download link v23.1 23015 is there any archive for old versions? the project link for stable + canary is the same, where can I find canary github page?
[Magisk] J.Michael:
topjohnwu/magisk-files

There's a dropdown that says "Master" -- you can change it to canary.
[Magisk] pndwal:
Afraid there was no 23.1...

Good tip of it's confirmed MagiskHide is retained... Some say it is, others say not... Some may be confusing Hide the Magisk app function and whether it is working...

Never existed as mentioned.

Not sure why you ask about Canary 23015. The last pre Zygisk Canary (w/ MagiskHide/ was 23001, and that was synced w/ 23.0 in any case... Next Canary was 23010 which was the first official Zygisk build and first to drop Magiskhide. PW
[Magisk] alecxs:
thx, it's a bit tricky but I figured it out :)

1. select branch canary, click on history (clock icon) on the right

https://github.com/topjohnwu/magisk-files/commits/canary

2. choose any commit, click on more... (three dots icon) next to app-debug.apk and select "View file"

3. click on more... next to file size 16.4 MB and tap on "Download"

23015 just guesswork. I will make some tests and try to track it down to specific version on weekend, thx
[Magisk] pndwal:
What specifically are you after? 🤔

Nb. Re. broken Hide the Magisk app (due to use of latest JSON pointing to newer incompatible stub):

- I believe from 23010 'Use local stub if unable to download' was integrated, so you should be able to get this function working in these builds simply by disabling network connections.

- With 23001 and earlier you will need to use the correct corresponding URL for raw JSON file as Custom Channel to get this working. PW
[Magisk] alecxs:
seriously idk just looking for a version without selinux errors. maybe just usage problem or maybe not related to Magisk at all, but lack of ideas where to start, so my first suspect is magiskpolicy for now
[Magisk] lcsboy:
When 23.1, we can see google play service/google play store, but 24.1 Zygisk can not see in denylist.

Are them set in DenyList by default or NOT?

In HMA, I need to turun system option to set the setting for google play serice/google play store.
[Magisk] pndwal:
Where did you get 23.1? - sounds fishy to me! 😬😜

Twy 23.6 😛 ... It's vely vely good!

Well they are there, same as in old hidelist; when you first enable them you need to select "show system apps' from menu to see them...

Nb. You don't need to hide root from Play Sore, and if using USNF, Play Services will be removed at bootup as this solution does its own targeted hiding for these processes.

Why? PW
[Magisk] VD171:
You can hide root totally from play store or any other app using SHAMIKO and XPRIVACYLUA.

Shamiko requires disabled enforcing denylist.

XPrivacyLua requires xposed.
[Magisk] pndwal:
But why hide root from Play Store at all?

Bank apps call SafetyNet API in Play Services, and this passed (for now) with USNF wizardry... Play Store calls the same API to provide Play Protect certification status.

Shamiko hides traces of 'root' (incl. Zygisk injection) that banks may or may not look for in addition to Google's SafetyNet / Play Protect status. XPrivacyLua may be useful for this also where 'suspicious' apps are installed etc... PW
[Magisk] VD171:
I did not say with exact intentions.

Only if one day is necessary.

But by "default", I hide too all traces of Magisk/Xposed for all applications that I don't use root, like google stuff.

Just for privacy.
[Magisk] pndwal:
Ok... but be careful; you can't deny root access to some Google services, eg if you indiscriminately hide Chrome processes in Magisk, you'll break webview... 😬 PW
[Magisk] VD171:
Yes, I can.

Apps contents and libraries, like webview can be whitelisted easily to be accessed and keep hiding.

Google services and other processes are really invasive and need to be controlled too.
[Magisk] Pippolepippa:
Use dns.adguard.com?
[Magisk] zgfg:
You tube streams ads inside the video - therefore the DNS based or firewall like blockers cannot help you.

Use Vanced YT app (root version, since you have root) - find the Vanced YT thread on XDA

For Google ads and similar, you can use AdAway app, root mode (you need to enable Systemless hosts in Magisk).

Alternatively, you can use private DNS like dns.adguard.com - but you don't need root here, you need Android 9 or higher (Settings, search for Private DNS)
[Magisk] trentini:
Hello, after a week testing, the problem still persists. Installed multidisabler , disabled automatic updates, but once I connect to the internet after a while magisk loses root and everything rolls back... any clues ?
[Magisk] Philnicolls89:
What method did you use to root your phone? What exactly rolls back? Does it only happen after reboots? What automatic updates did you disable?
[Magisk] MarkusMor:
Hi!

Has anyone tried to build Magisk (master branch - e7c82f2) on Apple M1?

I did the following:

./build.py ndk - success

./build emulator - error (after some changes in scripts, NDK issue):

❯ ./build.py emulator

* Building binaries: magisk magiskinit magiskboot busybox

/Users/markus/Library/Android/sdk/ndk/magisk/ndk-build B_MAGISK=1 -j8
In file included from jni/external/libcxx/src/algorithm.cpp:9:
In file included from jni/external/libcxx/include/algorithm:642:
In file included from jni/external/libcxx/include/utility:206:
In file included from jni/external/libcxx/include/__debug:14:
In file included from jni/external/libcxx/include/iosfwd:95:
In file included from jni/external/libcxx/include/wchar.h:118:
In file included from /Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/local/include/wchar.h:31:
In file included from /Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/wchar.h:37:
In file included from /Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/time.h:33:
In file included from /Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/sys/time.h:37:
In file included from /Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/sys/select.h:40:
In file included from /Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/signal.h:207:
/Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/android/legacy_signal_inlines.h:138:10: error: 'bsd_signal' is unavailable: obsoleted in Android 21
return bsd_signal(s, f);
^
/Users/markus/Library/Android/sdk/ndk/magisk/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/android/legacy_signal_inlines.h:41:14: note: 'bsd_signal' has been explicitly marked unavailable here
sighandler_t bsd_signal(int __signal, sighandler_t __handler) __REMOVED_IN(21);
^
1 error generated.
make: *** [/Users/markus/Library/Android/sdk/ndk/magisk/build/core/build-binary.mk:478: obj/local/armeabi-v7a/objs/cxx/src/algorithm.o] Error 1

Build binary failed!
[Magisk] trentini:
1 - Rooted phone using magisk method with stock ROM

2 - Installed TWRP

3 - Applied multi-disabler

when I meant rolls back I was meaning that root is lost and disabled, eg: no more magisk acting
[Magisk] martyfender:
The most frequent cause of this is having 2 magisk apps installed, one hidden, one not hidden.
[Magisk] General_Mayhem:
Trying to get the 2nd Feb update on Pixel 6 Pro. Attempting to uninstall Magisk (Beta 24100), I get "Stock backup does not exist!" when trying Uninstall > Restore Images.

Has anyone run into this and know how to fix it without nuking everything and starting over?

And if that's the only way, should I use fastboot flash boot --slot=inactive instead of --slot=all like every guide I've seen says?

(I really don't want to have to nuke it again.....)
[Magisk] guhvanoh:
I doubt it but read the error message. bsd_signal is not supported anymore. You need to figure out what replaces it and most likely update your Android SDK. I guess you've a nice weekend ahead sorting that out.
[Magisk] pndwal:
/data/magisk_backup_xxxxxx may be missing, or Magisk db file may be messed up...

I'm not familiar with Pixel or A/B devices, but it will likely be enough to flash unpatched stock boot image to restore for OTA. (Unless Magisk alters vbmeta or other participants in addition on your device)... I suspect you can just do normal flash to active partition, but I'm only guessing here.

A dirty flash of stock ROM should also restore images.

Also, restoring images is only needed for delta OTA updates due to their incremental nature. (Bit perfect images are required as only altered code in each partition is included in the update / flashed in order to produce a very small download package). If you can download the update as a complete ROM package you should be able to flash it over rooted ROM...

Here John's OTA notes:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md

👍 PW
[Magisk] MarkusMor:
Seems to have been fixed. Magisk successfully installed on the emulator.

Just replaced ~/Library/Android/sdk/ndk/magisk/ndk-build:

#!/bin/sh
DIR="$(cd "$(dirname "$0")" && pwd)"
arch -x86_64 /bin/bash $DIR/build/ndk-build "$@"

with

#!/bin/sh
DIR="$(cd "$(dirname "$0")" && pwd)"
arch -x86_64 /bin/bash "$DIR/build/ndk-build" "$@"
[Magisk] Lughnasadh:
Since you're having trouble using the "Install to inactive slot" method, you may want to just sideload the OTA and then re-root afterwards. Sideloading will preserve your data. Your stock backup boot image(s) are likely missing or corrupt.

Some people on the Pixel 6 Pro have updated via the "Install to inactive slot" just fine, while others have had problems, possibly due to the fact that they were not completely stock (e.g. custom kernel, modified /system or /vender, vbmeta). Sideloading will also take much less time than updating via "system update" method. Alternatively you can also fastboot flash the factory image with the -w removed from the flash-all.bat file to preserve data.
[Magisk] trentini:
Not in this case. Im coming from a fresh install. Following exactly these tutorials:

1 - https://www.thecustomdroid.com/samsung-galaxy-s10-root-guide/

2 - https://www.thecustomdroid.com/samsung-galaxy-s10-twrp-magisk-root-guide/
[Magisk] plusminus_:
Finally moved to 24.1 tonight and... it was painless. My previously MagiskHidden apps are working fine with Zygisk (including one that also needed Riru Unshare). Thank you once again Mr. Wu (and LSPosed devs 😘)!

edit: (and kdrag0n - I just installed USNF to pass SF in YASNAC again :P)
[Magisk] General_Mayhem:
Well since every guide for the Pixel I've seen says to flash vbmeta along with the patched boot... But that's stock so I'm unsure.

Trying the OTA without removing fails. I assume because both A&B contain the altered boot img.

I'll probably flash stock boot, OTA and flash again. Just last update I couldn't get into fastboot. Kept getting No Command and had to reflash using Google's online flash.