rikkaapps / sui Goto Github PK

能否支持kernelsu zygisk模块

Im facing settings force close on s10+ beyondrom after flashing the module. Got no problem with any otger module installed till now.

There is no zygsik version that can be considered

• 系统：Android 11 (ArrowOS)
• 设备：小米 6X (wayne)
• Magisk: v24.3
• Sui: 当前 CI 最新版 (f8eee8c) v12.6.1-release

在手机上创建 enable_adb_root 文件并重启后，adb root 仍然提示 adbd cannot run as root in production builds。

日志关键部分：

01-08 07:03:35.164   704   704 I Sui     : Setup adb root support: /dev/PwR6B9/.magisk/modules/zygisk-sui
01-08 07:03:35.168   704   704 I Sui     : Use adbd from /apex
01-08 07:03:35.169   704   704 I Sui     : /apex/com.android.adbd/bin/adbd is dynamically linked
01-08 07:03:35.170   704   704 V Sui     : /apex/com.android.adbd/bin/adbd: uid=0, gid=2000, mode=100755, context=u:object_r:adbd_exec:s0
01-08 07:03:35.170   704   704 V Sui     : /apex/com.android.adbd/bin: uid=0, gid=2000, mode=40751, context=u:object_r:system_file:s0
01-08 07:03:35.180   704   704 E Sui     : Cannot find versioned apex
01-08 07:03:35.195   706   706 I Sui     : Exited with 13

完整开机日志：logcat-coldboot.txt

通过 adb 检查 /apex 发现所有项目都不带版本号：

wayne:/ # ls /apex
com.android.adbd           com.android.i18n           com.android.neuralnetworks  com.android.sdkext
com.android.art            com.android.ipsec          com.android.os.statsd       com.android.tethering
com.android.cellbroadcast  com.android.media          com.android.permission      com.android.tzdata
com.android.conscrypt      com.android.media.swcodec  com.android.resolv          com.android.vndk.v30
com.android.extservices    com.android.mediaprovider  com.android.runtime         com.android.wifi
wayne:/ #

检查 /system/apex 发现所有 apex 都是未压缩的「扁平化 apex」，不是 .capex 格式的压缩包：

wayne:/ # ls -l /system/apex
total 80
drwxr-xr-x 6 root root 4096 2009-01-01 08:00 com.android.adbd
drwxr-xr-x 7 root root 4096 2009-01-01 08:00 com.android.art.release
drwxr-xr-x 3 root root 4096 2009-01-01 08:00 com.android.cellbroadcast
...
wayne:/ # ls -la /system/apex/com.android.adbd/
total 32
drwxr-xr-x  6 root root  4096 2009-01-01 08:00 .
drwxr-xr-x 22 root root  4096 2009-01-01 08:00 ..
-rw-r--r--  1 root root   218 2009-01-01 08:00 apex_manifest.pb
-rw-r--r--  1 root root  1032 2009-01-01 08:00 apex_pubkey
drwxr-x--x  2 root shell 4096 2009-01-01 08:00 bin
drwxr-xr-x  2 root root  4096 2009-01-01 08:00 etc
drwxr-xr-x  2 root root  4096 2009-01-01 08:00 lib
drwxr-xr-x  2 root root  4096 2009-01-01 08:00 lib64

Windows Subsystem for Android
Windows 11 (10.0.22000 Build 22000)
Sui v12.6.1 (Zygisk version)
Magisk v24.1 (Zygisk)

When using "App Ops", the little pop-up window that is supposed to ask for elevated permission simply does not show on WSA. The only way around this issue is to install a launcher (WSA does not come with one), and go into the Sui settings through the shortcut on the Settings app. In addition, entering "Developer options" in system settings does not prompt a Sui shortcut on desktop either.

使用“App Ops”的时候，要求提升权限的小弹窗在WSA上完全不显示。曲线救国的办法只有安装一个launcher（WSA不自带launcher），然后通过设置app上的快捷方式进入Sui设置界面。另外还有一点，进入“开发者选项”也并不会提示创建Sui桌面快捷方式。

Redmi 10X Pro
MIUI V11.0.5
Magisk21.4
Riru v25.4.4
Redownloaded many times but still failed

The magisk installation log is as follow

• Copying zip to temp directory
• Installing sui-v12.2.1-release.zip
• Device is system-as-root
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: module.prop
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: customize.sh
  mkdir: can't create directory '/data/adb/sui': File exists

Sui
by Rikka

Powered by Magisk

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: verify.sh
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: riru.sh
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: riru.sh.sha256sum
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: module.prop
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: module.prop.sha256sum
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: post-fs-data.sh
Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
inflating: post-fs-data.sh.sha256sum

• Device platform: arm64
• Extracting verify.sh
• Verified riru.sh
• Load /sbin/.magisk/modules/riru-core/util_functions.sh
• Riru: v25.4.4.r426.05efc94 (API 25)
• Installing from Magisk app
• Extracting module files
• Verified module.prop
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: uninstall.sh
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: uninstall.sh.sha256sum
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: sepolicy.rule
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: sepolicy.rule.sha256sum
• Verified post-fs-data.sh
• Verified uninstall.sh
• Verified sepolicy.rule
• Extracting arm libraries
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libsui.so
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libsui.so.sha256sum
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libsui.so
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libsui.so.sha256sum
• Verified lib/armeabi-v7a/libsui.so
• Extracting arm64 libraries
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libmain.so
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libmain.so.sha256sum
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libadbd_wrapper.so
  Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip
  inflating: libadbd_wrapper.so.sha256sum
• Verified lib/arm64-v8a/libsui.so
• Verified lib/arm64-v8a/libmain.so
• Verified lib/arm64-v8a/libadbd_wrapper.so
  unzip: can't change directory to '/data/adb/modules_update/riru-sui/lib': No such file or directory

! lib/arm64-v8a/libadbd_preload.so not exists
! This zip may be corrupted, please try downloading again

! Installation failed

topjohnwu/Magisk@cacf873

200多个APP里找东西还蛮困难的。

magisk_module/customize.sh
`
#45 - 51 :
system_x86/.../

`

目前的体验，ShizukuAPI系列的产品碎片化是很严重的，严重影响了使用体验。很遗憾这么一个年轻的项目早早的出现了历史负担，于是有了Shizuku桥的想法

现在高权限应用分出了好几个阵营：
1.仅支持ShizukuAPI的Rikka系：nopopping、AppOps
2.仅支持Shizuku，不支持Sui：年久失修的「冰箱」「安装狮」、认为root用户就该用libsu的「DarkQ」
3.仅支持Sui，不支持Shizuku的（不包括因为shell权限不足而无法实现某些功能故不支持Shizuku的应用）「Material Files」（这里认为文件管理器支持shell权限的Shizuku是有意义的：可以优雅地读写Android/data文件夹）
4.API已经满足支持Sui和Shizuku，但是需要明确拒绝su权限才进入ShizukuAPI权限判断，甚至硬编码了包名判断，只有安装了Shizuku才能调用Sui的「DarkQ」

ShizukuAPI在一些软件中极大地加快了软件速度，但是一些极端的想要尽量让app有就用ShizukuAPI的场景，可能需要同时拥有Shizuku和Sui才能正常工作

于是我想能不能通过一个极小的同名Shizuku的安装包，桥接一些对Shizuku的调用到Sui上，或者Sui的调用到Root Shizuku，帮助一些古老的设计不佳的应用保持兼容，同时也减少用户安装软件数量？

虽然按照标准，这些行为都应该是能被避免的，纵容这些不规范可能会让以后的生态更糟糕，但作为用户…我真的不想装那么多软件实现同一个功能😭

开启 adbd root 并 adb root 后，Android Studio 无法找到任何可调试的 app ，一些调试功能无法正常使用。

原因似乎是 app 无法连接到 jdwp-control ，推测是 adbd root 后位于 magisk domain ，而 appdomain 无法连接 magisk 的 socket 。

参考修复实现：hook selinux_android_setcon ，在其后向 /proc/self/attr/sockcreate 写入 u:r:adbd:s0

5ec1cff@a81035b

Suppose, I've granted full device access using Sui, but now I want to change my decision. I don't see any GUI app to achieve this?

Running 276479e (https://github.com/RikkaApps/Sui/actions/runs/1421584576)

The "Sui" entry in the system settings, long-press menu just takes me to Internet properties.

#

I can see that Sui's post-fs-data.sh has ran from the magisk log.

Apps that use Shizuku (WADB in this case) prompt me using the usual MagiskSU prompt and not Sui's.

/data/adb/sui exists and there are two files that are in it (sui.db & sui.db-journal), sui.db-journal is blank.

Magisk log: https://github.com/RikkaApps/Sui/files/7481161/magisk_log_2021-11-05T07_46_24Z.log

如图所示，SR仅安装于 User 0 却在 User 10 也被显示，微信仅安装于 User 10 却同样显示在 User 0。

There is no zygsik version that can be considered

With Magisk v24, Modules Repo is dead, making harder to find and update our favorite modules.

Fortunately, topjohnwu introduced a new way to update Magisk Modules using Magisk App. But the developers need to add this individually for each module.

Could you add support to this to Sui?

本人是韩版U+的LG V50 ThinQ，面具版本为25.1，LSPose版本为1.8.3 (6581) - Zygisk，安卓10。在安装了sui-zygisk-v12.6.3模块后，无法正常进入管理界面，但可以对App Ops等进行授权。 通过拨号和快捷方式进入的是关于手机页面。
PS：这里附上开机日志文件（不知道对不对）
[email protected]

• 设备：小米平板 5 (nabu)
• 系统：MIUI 13.0.5, Android 11
• Sui: v12.4.0 release + Zygisk
• Magisk: 24.1

在 WADB 中点击启动「无线 adb」之后，对应菜单项置灰，但是授权弹窗不显示。必须手动在 Sui 管理器中设置成「允许」之后才能授权成功。

MaterialFiles 同理，打开「根目录」之后无限转圈，需要手动授权。

相关日志：

02-15 13:41:48.406  4083  4328 E Logger  : No available log folder
02-15 13:41:48.691  2784  3102 D GestureInputHelper: onInputEvent action=0
02-15 13:41:48.691  2784  3102 W RecentsModel: getRunningTaskContainHome
02-15 13:41:48.699  2784  3102 D GestureInputHelper: onInputEvent, lastGestureMode=com.miui.home.recents.GestureModeHome@dc36ea8, newGestureMode=com.miui.home.recents.GestureModeApp@2887be0
02-15 13:41:48.700  2784  3073 E StateBroadcastUtils: sendFsStateBroadCast state=taskSnapshot   channel=gesture
02-15 13:41:48.722  2784  3102 D GestureInputHelper: onInputEvent action=1
02-15 13:41:48.722  2784  3102 D GestureTouchEventTracker: stopTailCatcher
02-15 13:41:48.722  2784  3102 D GestureTouchEventTracker: mUpType=10
02-15 13:41:48.733   820  1212 E Service : manager is null

查看 PID 820 的命令行，可以确认是 Sui 守护进程：

nabu:/ $ cat /proc/820/cmdline
sui

Would I benefit from using it? How do I exactly use it? What are the benefits to the user if any?

Probar

When i install the sui.zip over magisk and reboot the device,my settings force close every time when i want to open it.
Whats the problem?

Hey @RikkaW thanks for such amazing project. Everything works perfectly on my device.
Just a question, can I delete the SU binary to avoid detection? Many apps trying to detect root by executing "which su" command - and instead of renaming it I would like to delete the executable entirely to avoid detection.

What do you think?

如题，安装sui后删除，长按设置的快速菜单里的sui依然存在

My 6127I is not rooted and running Android 12. http://bit.ly/amirooted #android

It took me a long time to find out that it was Sui was causing this problem, and it's even a little tricky to explain...
With Sui module enable/installed, opening Settings intents is buggy on tablets running A12L+.

In the screen recording below, when opening App Info page without Sui, "Settings dual panel" opens normally with App Info on the right and Settings categories on the left.

But notice what happens when Sui is enabled: Settings is opened completely with the first category selected (Network and Internet) and using back gesture is displayed App Info page stretched.

This happens with literally any shortcut that launches some page in the settings. App Info from launcher was just the example used in the video.

目前系统版本是安卓10，magisk版本24，zygisk-sui12.4.0，设置appops始终允许完全访问权限后，重启设备后再次打开appops又会再次提示索要权限，并且存储空间隔离也有相同的问题

Moto G Power 2020 (sofia) running android 10 magisk with riru and edxposed (latest magisk repo versions). Upon installing the version found here sui-v11.6.0.zip or the newer version from the magisk repo the phone will not boot past the motorolla logo, I am unable to capture any debug info or logcat with the debug version of sui. I have to delete the module from recovery to boot again.

Any ideas what could be wrong and how to further investigate the issue? Thanks.

Hello. I've updated to the latest Sui version from Magisk Manager and noticed that everytime i enter dev settings it always asks to add a home screen shortcut. I understand that this is intentional design but it does get annoying to always have to cancel it. I'd rather just hold my settings app and enter Sui from there. I personally found the previous method of entering dev options and taping the notification better so I don't understand this change... Is there a way to disable the pop up?

Thank you for your time.

FATAL EXCEPTION: main
Process: com.android.settings, PID: 22758
java.lang.IllegalArgumentException: Wrong number of arguments; expected 2, got 3
 at java.lang.reflect.Method.invoke(Native Method)
 at rikka.sui.settings.SettingsInstrumentation.callActivityOnNewIntent(SourceFile:7)
 at android.app.ActivityThread.deliverNewIntents(ActivityThread.java:4317)
 at android.app.ActivityThread.handleNewIntent(ActivityThread.java:4324)
 at android.app.servertransaction.NewIntentItem.execute(NewIntentItem.java:56)
 at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
 at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
 at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
 at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2443)
 at android.os.Handler.dispatchMessage(Handler.java:106)
 at android.os.Looper.loopOnce(Looper.java:226)
 at android.os.Looper.loop(Looper.java:313)
 at android.app.ActivityThread.main(ActivityThread.java:8751)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

One UI 4.1, Android 12, Magisk 25205
Previous version of Sui (v12.6.3) doesn't cause such problems for me

打开任何一个应用设置都会闪退，降级为11.6版本后问题没有复现

坚果r1 SmartisanOS 7.2.0.3 安卓8.1.0
riru 最新版 magisk最新版
模块列表
sui从12.0.0之后的版本都会出现这个问题

开发者设置闪退 且没有发送快捷方式提示
另外长按设置也不行，可能是因为锤子不支持shortcut
按*#组合键打开的是WiFi

12.0.0版本是可以正常使用的

希望大佬看下，闪退log已经附上

模块列表:

on op6t with latest os, magisk, latest riru core + some other modules installed, updating sui to v. 11.6.0 causes reproducable bootloops.
reinstalling v11.5.0 solved the problem

Cf

Hello, there were problems after updating to version 11.6.0
The device freezes on the lock screen and does not even allow the device to be unlocked, but not the whole system is just the lock screen interface. Sometimes it allows you to unlock, but it still does not allow you to enter the system settings.

Latest working version 11.5.0
Android 11 Samsung OneUI 3.1

I also have a samsung device with android 10 and OneUI 2.5 and 11.6.0 works fine there.
If you need any logs tell me how to get them without unlocking since device cannot be unlocked due to a bug.

It would help narrowing down to the app in interest quicker.

Should I uninstall shizuku if I installed sui (and vice versa) or they can safely run together on the same device? If not, is it recommended to use one over another?

My 6127I is not rooted and running Android 12. http://bit.ly/amirooted #android

• PoC

  该 Demo 的功能是设置 MIUI 的进程白名单，成功时会输出如下日志：

D/ProcessManager: update CL:[com.netease.cloudmusic]

  使用 Shizuku 时功能正常，输出如下日志：

D/Service: transact: uid=10527, descriptor=miui.IProcessManager, code=8

  使用 Sui 时发生鉴权错误，找到如下日志：

W/Service: Permission Denial: transactRemote from pid=0 is not an attached client

  已在多台设备上进行测试，均产生此问题。

  定位到打日志的位置，发现该错误由 clientRecord == null 引起，向上继续定位到 ClientManager#findClient(int uid, int pid)：

public ClientRecord findClient(int uid, int pid) {
    for (ClientRecord clientRecord : clientRecords) {
        if (clientRecord.pid == pid && clientRecord.uid == uid) {
            return clientRecord;
        }
    }
    return null;
}

  可能是由于 oneway 导致此处 获取到的 pid 为 0，导致没有匹配到正确的 clientRecord

  不知道我的猜想是否正确，还请开发者帮忙看看。

已按照post-install.example.sh的说明，导出sui.dex/librish.so/rish三个文件到其他终端(例如Termux)的数据目录中，并移动到环境变量中，同时Sui给予授权，但此时运行"rish"仍然不起作用，返回"killed"。

Adding version number required for installation in the error message: V22 or above.(see attached images).

Also, need detecting the version number installed and display it (For versions < 22).
Specify in the README.md file (by adding a Section REQUIRED):Need (version >= 22).

opens wifi settings when I touch the shortcut and even when I use the dialer, module works properly regardless

1.有更加规范的开发环境。
2.舍去了更加复杂的安装方式。
3.杜绝了不可控的bug产生。

Root itself is a concept in Linux, coincidentally, Android is running on Linux.

The goal of this project is to replace the "su" executable and call for the root community to switch to the correct way.

The purpose of this project seems to be to call system APIs in an efficient way.

It is not related to su, no need to replace it.

The result is, everyone suffers from "su".

「su」 is very convenient in some simple scenarios, such as move or delete certain files, set permissions

By the way, this is a very interesting project, I love it. It can be of great help in complicated situations.😉