yashsingh1/xdaforums huggingface dataset:
[Magisk] Legitsu:
the problem I have atm is certain apps require. the https://github.com/Xposed-Modules-Repo/xyz.xfqlittlefan.notdeveloper to hide dev options/adb status

but this module doesn't apper to work with enforce denylist

so I am back to using shamiko ...

again I firmly belive kernelsu is the way as its elimiates the issue of user-space apps detecting the presence of various root traces by nature instend engieering ever more complicated ways of hiding root traces its best to just elimitate them entirely

yes I am aware you will still need some clever hacks to hide any modules you might want to use or if you are using Zygisk On kernelSU but I think its easier
[Magisk] WoolfishStrives:
Has anyone got a copy of the June 30th apk? I'd like to try that and see if it's just the latest version that doesn't work for me

Edit, never mind I just figured out how to get it off github 🙃
[Magisk] intel_core_i7:
Do you know anything like this but to hide accessibility services? Much appreciated, since banks here decided to implement checks on this
[Magisk] zgfg:
Just my two cents about

I'm also frustrated with that - I need Accessibility for AndroidAuto and some tweaks there. And I have also two loyalty apps that warn (but they don't block) about the Accessibility switched on

Checking for Accessibility has really nothing to do with root. Accessibility is just a legit Android functionality (provided by Google) that can be switched on by an average Joe user

Moreover, it could be even escalated (for blocking on Accessibility) as discrimination against users with disabilities. I'd like to know if American apps would do that, they have pretty stiff regulations about violating ADA (Americans with Disabilities Act) in the States.

And Wallet does not discriminate about

On the other side, I may understand that eg, TalkBack can pose a security risk for 'banking' apps
[Magisk] intel_core_i7:
As I have told before, the issue of people granting rights to random malicious apps and then lose money has become so popular (according to the central news) that banks are implement this

And this is a developing country, the infrastructure for the fully able isn't even up there yet, so don't expect legislation for the disabled.
[Magisk] pndwal:
Latest Alpha (GitHub) is now f2e109ad-alpha 26104

LSPosed/Magisk/commits/fba58d630197a8fca43d69c18fcf7430aedd0de9

... Got some fixes...

👀 PW
[Magisk] ahpekriderzbmx:
Nice..
[Magisk] rodken:
The latest Magisk Alpha Release

-- 82903582-alpha-26105.
[Magisk] ahpekriderzbmx:
Still Problem Cannot Open Magisk After Install It..Huhu
[Magisk] rodken:
I hope that you had a backup of your boot file and/or a recent patched version of your boot file to fall back on assuming that you were already on a recent version of Magisk Alpha.

-- Can you expound on your post regarding 'still problem' as though you've experienced this before.
[Magisk] Legitsu:
no problems installing it here

if you repackaged the magisk app. you need to restore the orginal before upgrading or you will break stuff

_________

the lack of transparency with commits and updates on alpha is concerning
[Magisk] ahpekriderzbmx:
I already backup my boot.img..How To Fix This Issue..Magisk-alpha(26103) Work Great..Magisk-alpha(26105) Cannot Open Magisk After Install It.
[Magisk] ahpekriderzbmx:
I Not Repackaged It..Huhu
[Magisk] rodken:
Disable any and all modules, uninstall Magisk Manager then boot into recovery and wipe cache and Dalvik again then reboot into system and reinstall Magisk Manager assuming that you did or did not use the option to hide the app and renamed it in settings.

Consider yourself lucky that your device is still in working condition because there are cases where users completely bricked there device playing around with Magisk.
[Magisk] pndwal:
Might want to watch this space:

Magisk Manager freezes after upgrading to 26105

#7214 opened 8 hours ago by humbleoxygen12

Maybe general 26105 issue...

Report for OnePlus 8T. 👀 PW
[Magisk] ahpekriderzbmx:
Who Successful Install Magisk Latest? SCREENSHOT PLS?
[Magisk] ahpekriderzbmx:
Same On Me To
[Magisk] ahpekriderzbmx:
Already Try This..Not Solve My Problem..Thanks Bro
[Magisk] Elsrougy:
I have same issue as this. 26103 works fine, but 26104 onwards Manager freezes on logo upon opening, so it is something they changed between 103 & 104.

My phone is OP8 Pro so maybe it is OnePlus related too
[Magisk] ahpekriderzbmx:
Just Waiting For Dev To Fix It..Hehe
[Magisk] rodken:
It's not a OnePlus issue because all is well on my OnePlus 8 going forward.

-- I suggest that you reevaluate how you flashed Magisk.

-- Consider removing Magisk completely and utilize the fastboot method after repatching your boot file.

-- You might also want to consider reflashing your ROM and starting from scratch.
[Magisk] rodken:
Don't count on it, especially if it's not a widespread problem.
[Magisk] Elsrougy:
I said it is OP because all the posts I found online regarding this is on OnePlus phones. maybe it is OnePlus + other factor that we do not know now (version/rom/region etc.)

I am not really planning on trying to fix the problem soon because I do not see any significate upgrade in the recent versions so I will just keep using 26103 for now and when needed will investigate later. Maybe it will be fixed in later versions anyway
[Magisk] Lughnasadh:
No problems for me using Canary 26105 on my Pixel 2 XL (A11) and my Pixel 6 Pro (A14 Beta 4.1), so may not be a "widespread" general issue.
[Magisk] pndwal:
Just meant general Magisk as in not confined to Alpha fork... Sorry to confuse...

So far reports are mainly for various OnePlus devices, maybe a Realme device...

Not sure if all these sport dedicated recovery A/B partitions unlike Pixels (which set BOARD_USES_RECOVERY_AS_BOOT for first stage init before GKI), but ramdisk used will be different if that's the case (I know OP 7 and 8 series do have/recovery_a and /recovery_b) so this may be a clue.

Seems widespread... Several users commented in issue now... And 1st report includes log, although maybe only w/ Canary build, so will get attention...

Interesting... Must be some factor we're missing... Waiting for dev comments on logs...

Incidentally, I noticed that Recovery Mode was checked again for my A-only legacy SAR device w/ 26105 update; I had to uncheck it, but normally the setting is retained... I wonder if anyone is seeing that setting erroneously on 2SI (LV A10+) devices?

🤠 PW
[Magisk] rodken:
+1

It would be nice if other users who were to flash successfully chime in on whether 26015 is not detected in Momo and/or AppList Detector.
[Magisk] rodken:
I've just noticed as of this writing concerning both older and newer versions of OP devices running OOS even after reformatting data to no avail.

-- Running OnePlus with a Custom ROM yields no issues.
[Magisk] pndwal:
So a factor is stock vs custom ROM(?). PW
[Magisk] rodken:
Quite possibly but would need further evaluation.

-- Seems to be freezing/misbehaving on folks still running OOS 11 versus OOS 13?

-- Possible workaround is to 'nuke' everything in data/adb > boot in bootloader > reflash patched boot.img
[Magisk] pndwal:
... Were there issues for you? 👍 PW
[Magisk] first_damned:
I've installed 26105, but when I install a magisk module and reboot it goes to recovery, I then reboot system and it's fine and module is working. It does this on any module I install. Is this a known bug?
[Magisk] pndwal:
Not that I know of... Please say device... (Older S10 etc by any chance?) PW
[Magisk] ahpekriderzbmx:
How To Remove Magisk Alpha? Rename Magisk Alpha.apk To Disabler.zip N Flash It Through Recovery Right?
[Magisk] first_damned:
It didn't do it on previous versions.

Xiaomi pocophone F1 (Beryllium)
[Magisk] pndwal:
Strange symptom but may be linked to issue discussed above:

https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-88846643

Can you open a GitHub issue (meet to install Debug build and supply logs) or at least comment in the open one?...

Just curious though, you don't (erroneously) see Recovery mode (with check mark) in Magisk, Install in Magisk App do you? (Shouldn't show on device launched with Android 8, only on A-only A9, but strangely, on my A9 device it keeps getting checked/doesn't retain setting w/ 26105... This anomaly makes me suspicious about your issue.) PW
[Magisk] pndwal:
You mean to install TJW Magisk? I'd use root to install to install that...

Assuming device is not A-only legacy SAR ((launched with Android 9), just rename chosen magisk.apk to magisk.zip and flash in App from modules page (as a module)... Before you reboot, use root explorer to remove magisk directory and magisk.db file, and uninstall Alpha app... Reboot, open Magisk App (install if missing) and follow prompts to complete setup...

🤠 PW
[Magisk] first_damned:
I'd have to open the issue another time when I get chance.

Yes I have recovery mode ticked and no ramdisk either.

What rom are you using?
[Magisk] pndwal:
Oh!... I thought all A-only legacy SAR launched with Android 9!... But had suspicions about your LV A8 device when I saw your issue... Just updated my knowledge!

Anyway, HaHa... Your problem is simply having Recovery mode checked... It'll (try to) reboot via recovery to Magisk System as if you patched ramdisk in recovery.img... Uncheck it and try...

But (erroneously) flashing boot.img with Recovery mode selected may also have produced differences to boot.img although it works (being Xiaomi, Magisk adding a basic ramdisk and inexplicably having bootloader compatibility for ramdisk in /boot despite OEM not launching device with one)... It does produce flashed differences on Sammy A-only legacy SAR devices, just not sure about others...

If rebooting doesn't work properly after unchecking Recovery mode, I'd patch stock.boot.img again with app set for Boot mode Magisk...

Don't worry about issue as seems it's only the check box not retaining setting... I might open an issue for that myself...

🤠 PW
[Magisk] first_damned:
It did come with A9 but I've flashed a custom rom Lineage 18.1, but I have to use root to pass safety net. I may just use Arrow OS instead as that already passes and no need for root, but comes with older security patch. Not that that maybe matters really?

When I first patched the boot.img recovery mode wasn't ticked, it must of ticked itself after this. Makes sense as when I installed a module and pressed reboot, it went to recovery and then I rebooted to system. Will this make any difference to my system? Or has it interrupted the module installation somehow?

As a security risk, is it better to use a outdated security patch on arrow os, or latest security patch on lineage but be rooted to pass safety net?
[Magisk] rodken:
I was curious more than annoyed.
[Magisk] pndwal:
Ah... I would have twigged to this sooner if GSM Arena didn't give 8.1 as launch version and only one model variant (M1805E10A)...

🤷 Depends on your concerns...

Yup, that's the anomaly as I said...

I answered these questions to the best of my knowledge above...

If you're sure you didn't patch in boot mode, it may be fine just to uncheck it now... If you're unsure, test or restore unpatched boot.img and re-flash in Boot mode (ie. Recovery mode unchecked)... PW
[Magisk] first_damned:
Which is more of a security concern? Rooted or outdated security patch? As I prefer arrow os as it has not features and already passes safety net but older security patch
[Magisk] rodken:
Outdated security patch is a more significant security concern than being rooted.

Rooting a device just gives you administrator-level access where outdated security patches leaves the device vulnerable to known security vulnerabilities.
[Magisk] zgfg:
Rooting device JUST gives YOU administrator level access...?!

You = not 'you' but any wannabe hacker/rooter:

You install eg, a 'cool' 3G/4G/5G network analyzer

You grant it root privileges since it asks to access certain 'GSM' data about the towers, frequencies, who knows

However, you didn't mind to investigate its thousands lines of source code (hundreds of classes, etc), or you're not a programmer, or source code was not even published - but, you're a 'hacker' who read on Telegram or watched on TikTok from a 'cool' influencer you're following that having a root and that root network analyzer is very 'cool'

However, this is not KSU where administrative rights are classified to groups, so that network analyzer can have admin rights but only on Networking, hence not on Filesystem, Contacts, etc

Now, suppose that your 'cool' network analyzer has actually a root-bomb built-in, ie it missuses the granted root to mine your data, contacts, etc and sends somewhere out your sensitive data

That 'cool' root network analyzer does not need any 'known security vulnerability' , and no Security patch would ever fix it protect you from that app

And it would be too late when you discover that your eg passwords are selling on the black market and that you realize that the 'root cause' was a 'cool' root app to whom you granted the root rights

You never use the root privileges yourself only - you always need an app that will do something cool for you with the root grant, but how are you sure that that same app does not missuse the granted root privileges for some criminal work behind the scene
[Magisk] rodken:
Pretty much falls into the same line of defense regarding malware that can take advantage of the root privileges to gain access to said device's data.
[Magisk] zgfg:
Yeah, but that's the point - in my view, rooting devices is absolutely no less risky from the security point of view (and specially for the financial institutions you have your account and you use their apps to manage your assets) than the outdated Security patch level - exactly opposite than what you stated in the post I originally quoted

Hence again, you and others here like it or not, they have full rights to protect themselves from the rooted devices

Or corporations you work for and you have Outlook, Teams, SharePoint, etc - apps that access the sensitive business data. Btw, if that 'cool' network analyzer sends out sensitive business data - would you have money for the lawyers when the Legal dept accuses and charges you for the leak?

I'm also a rooter (you know) but I firmly stay on that side
[Magisk] HippoMan:
A lot of that can also be done by a similarly "cool" app that doesn't make use of root.
[Magisk] pndwal:
I have to agree with examples above that illustrate how root privilege can be far more dangerous than outdated security patch level.

Spoiler content hidden.

Rooters and custom ROM users MUST take care and know and manage the risks... 👀 PW
[Magisk] HippoMan:
The same is true on pretty much each and every Linux desktop/laptop machine that exists.

All we have to do is su or sudo to root and then modify the sepolicy settings via various sepolicy-related utilities.

Anyone who is willing and able to manage the risks of running a linux box can use the same knowledge and skills to manage sepolicy-related security on a rooted Android device.

And yes, I agree that a ROM which is SE-permissive by default is indeed a greater risk.
[Magisk] immortalwon:
Did anyone figure out how to fix the magisk alpha manager freezing upon opening on latest 26105 version? It seems it effects people on oneplus devices, maybe android 11 firmware?
[Magisk] underpass:
So, do you guys trust this fork since it's closed source? I am currently using it and it's the only thing that works for me for some bank apps, but it does seem sketchy and makes me feel concerned about my security. Is there any real alternative that can hide root just as good?
[Magisk] pndwal:
Granted, experienced Linux users will have the advantage of understanding risks, dangers and precautions to take much better...

Spoiler content hidden.
[Magisk] pndwal:
It's only for testing ground breaking commits... It used to be Nangong Xueshan's ( @vvb2060 ) personal fork, but recent Alpha builds are no longer from her GitHub; they build from https://github.com/LSPosed/Magisk/commits/ which is not public... You can see the LSP / Shana's ( @yujincheng08 ) Metagisk test branches where commits originate however and of course if you don't trust Alpha you could fork a Metagisk test branch and build from source yourself... Eg for current WIP native bridge loaded Zygisk (with PR in official Magisk also from this Metagisk branch), see:

https://github.com/LSPosed/Metagisk/commits/zygisk

Commits on Jun 13, 2023

Fix zygisk when LoadNativeBridge is inlined

yujincheng08 committed on Jun 13

Refactor hookJniNativeMethods

yujincheng08 committed on Jun 13

Refactor zygisk to use native bridge to inject

yujincheng08 committed on Jun 13

Clean up codes

yujincheng08 committed on Jun 13

Inject zygisk.rc for sync --zygisk-restart

yujincheng08 committed on Jun 13

Use Metadata instead of direct stat syscall

topjohnwu committed on Jun 13

Replace all CStr usage to Utf8CStr

topjohnwu committed on Jun 13

Remove unnecessary lifetime markers

topjohnwu committed on Jun 13

Fix map_file

yujincheng08 authored and topjohnwu committed on Jun 13

Of course the top LSPosed Devs are the principal Magisk collaborators, clearly trusted by John...

But you could simply wait for TJW Magisk 27.0 which was supposed to include the NBZygisk milestone...

Nb. Most apps needing the greatest level of trust are closed source incl. your bank and Google GMS (GApps).

TJW decided to break the mould for root, but the biggest advantage in open sourcing it seems to be the freedom outside Devs have to contribute in its source, and the contributions have been prolific! (Some non-dev modders like me have even contributed a couple of ideas which are now incorporated in Magisk!) Chainfire's SuperSU was closed source, and pretty much a one man show...

@canyie's Shamiko root hiding module, also now a joint LSP project, is also closed source, but she too is a prolific Magisk contributor... There are alternative hiding root modules but they are definitely not as good.

🤠 PW
[Magisk] pndwal:
OnePlus, Android 10 and 11...

Keep watching this space:

Magisk Manager freezes after upgrading to 26105

@osm0sis has already done preliminary diagnosis... 👍 PW
[Magisk] Lubo99:
hi mate. I have magisk26.1 lsposed and shamiko modules 3 banking apps which were working fine untill today one of them after update refuses to run. says most hated word which users with rooted device can see : phone is rooted .... I consider to use alpha. the phone is rooted and also tool to mount partitions as RW and I dont want to lose it I would like to avoid flashing. ii heard about alpha today so sorry for asking stupid question. can this be installed from TJW magisk? motorola 30 android 12.
[Magisk] amk316:
is there a way to disable magisk in the next boot(only once)?
[Magisk] rodken:
#!/bin/bash

# Create a file called .disable_magisk in the /data and /cache directories
mkdir -p /data/magisk
mkdir -p /cache/magisk
touch /data/magisk/.disable_magisk
touch /cache/magisk/.disable_magisk

This script will create two files, one in the /data directory and one in the /cache directory, called .disable_magisk. These files will tell Magisk to disable itself on the next boot.

To run this script, you can save it as a file called disable_magisk.sh and then execute it using the following command:

adb shell sh disable_magisk.sh

Once you have run this script, Magisk will be disabled on the next boot. To re-enable Magisk, you can delete the .disable_magisk files.

Here are some additional things that you might want to keep in mind:

This script will only disable Magisk for the next boot. If you want to disable Magisk permanently, you will need to uninstall it using the Magisk app or the ADB command magisk --uninstall.

This script will not affect any modules that you have installed. If you want to disable a specific module, you can do so in the Magisk app.

This script is not guaranteed to work on all devices. If you have any problems, you can always try searching for help on other Magisk forums.
[Magisk] rodken:
The latest Magisk Alpha Release

-- ae9d270a-alpha-26201.
[Magisk] immortalwon:
Still not working on A11, oneplus pro 9
[Magisk] rodken:
Have you attempted to delete everything in data/adb > boot in bootloader > reflash patched boot.img?

-- There is that possibility that all versions since v.26105 going forward might be incompatible with OOS

+1

+1

-- Utilize a script to remove Magisk and all of its modules

#!/bin/bash

# Check if Magisk is installed
if [ ! -d /magisk ]; then
echo "Magisk is not installed."
exit 1
fi

# Remove Magisk and all of its modules
rm -rf /magisk

# Reboot the device
reboot

To use this script, you will need to save it as a file called magisk-uninstall.sh and then run it from a CLI.

Try with the Magisk uninstall.sh script:

Open a command-line interface.

Navigate to the directory where the Magisk uninstall.sh script is located.

Run the following command:

bash magisk-uninstall.sh

The first line defines the shell that the script will be run in. In this case, we are using the bash shell.

The second line checks if Magisk is installed. If it is not installed, the script will exit.

The third line removes the /magisk directory. This directory contains all of the files and folders that are used by Magisk.

The fourth line reboots the device. This is necessary to ensure that Magisk is completely removed.

If successful, you can reattempt with the newest version of Alpha via fastboot method

There are discussions on TG regarding the issue and whether or not the issue can be resolved or addressed remains to be seen.
[Magisk] pndwal:
FWIW, Magisk compatibility issues for stock ROMs generally get fixed except where OEMs simply don't comply with Google/Android requirements... Custom ROM/kernel issues are considered but are more likely to be WontFix... 😜 PW
[Magisk] Abdel1993:
Don't listen to @rodken guys. He doesn't know what he's talking about. I had a bootloop on version 26.2.1. I'm back on version 26.1.5, having restored the patched boot image on LineageOS 20. Be warned and save yourself the headache.
[Magisk] agraceful:
What are you referring to "not knowing what he's talking about"? You cannot make a blanket statement against someone without proof of your claim. I'm personally running the latest alpha on 5 different devices all running different ROMs and Android versions. They all work. So, explain.
[Magisk] mihalis1983:
Hello,

I'm trying to install Alpha, but everytime i'm getting a bootloop.

Poco F1 - A10 - miui12

I tried everything: 26201, 26105, 26103. Installed directly from the app or flash through twrp, or patch vbmeta, all causing bootloop.

Magisk 26.1 is working ok, but i need Alpha...

Any help ?
[Magisk] pndwal:
Did you have root before?... Did you happen to see Ramdisk= No,, or checkbox for Recovery mode in Install menu? (Nb. Neither should occur on your device)... PW
[Magisk] mihalis1983:
Rooted with Magisk 26.1.

Ramdisl= No

How should i flash Alpha correctly?
[Magisk] pndwal:
So you have Magisk misidentification of your device as legacy SAR and probably have messed up /recovery partition...

See my comment in this issue:

https://github.com/topjohnwu/Magisk/issues/7254#issuecomment-1702573893

👀 PW
[Magisk] mihalis1983:
Yes,

It shows that couldn't identify device and that recovery method didn't work. Also saying to flash Alpha through the app.

But that also gives me bootloop...

Then i'm recovering boot.img (26.1 rooted) through twrp and phone boots normally.

Also tried:

Extract boot.img from rom, flash it with Alpha through app, then flash it via twrp --> bootloop