Flash the latest module, unable to boot

[MobInfinity]

Xiaomi 13 Pro
HyperoOS v816.0.2.3.25.DEV
KernelSU v0.9.2-74(11756) LKM
After the module is swiped in, it is stuck in the last interface before the System Desktop.Not working properly.
After a few minutes, the system reboots again and successfully powers on, but the module is not available.

[symbuzzer]

which module manager to use for installing?

[MobInfinity]

KernelSU Manager ci v0.9.2-74(11756)

https://github.com/tiann/KernelSU/actions/runs/8534287704

[MobInfinity]

Xiaomi Mi 10
MIUI-V14.0.4.0.TJBCNXM
APatch v0.10.5(10657)
The same problem was found with the latest version of the module.
Is there a conflict with the module I installed?

[symbuzzer]

what are your installed modules?

[MobInfinity]

These modules

[symbuzzer]

I really dont know sir, there isn't any feedback like this before. But I thinks there is conflicts with other modules

[MobInfinity]

I think it should be the same problem as this one.
#15

[MobInfinity]

On my other device(Xiaomi Pad 5 Pro 5G), it was the same problem.I think I should give you the feedback of the log.
APatch_bugreport_2024-04-12_14_57.tar.gz

[MobInfinity]

Although the module manager shows that the installation is successful, the module does not work properly.And still have the same problem.After the installation of the module, the first restart, can not enter the desktop.Restart for the second time to enter the desktop.

[MobInfinity]

Even if I just open the "Zygisk-Next-1.0.4-292-b36a0ad-release" module,Install the "systemless-hosts-KernelSU-module" module again, and the same problem occurs.
Now I think it may not be a conflict with other modules.

[MobInfinity]

The interesting thing is that when I use the oldest version of the module v1.0.0,everything works.Magisk will be detected by momo.
This version v1.1.0 also works(The shamiko module needs to be closed.),but magisk is detected by momo.
Modules after v1.1.1 have the problem I described.

[symbuzzer]

The interesting thing is that when I use the oldest version of the module v1.0.0,everything works.Magisk will be detected by momo. This version v1.1.0 also works(The shamiko module needs to be closed.),but magisk is detected by momo. Modules after v1.1.1 have the problem I described.

just feedback latest version, sir. These informations dont gives any information about issue, even log :(

[MobInfinity]

在我的另一台设备（小米Pad 5 Pro 5G）上，也是同样的问题。我想我应该给你日志的反馈。 APatch_bugreport_2024-04-12_14_57.tar.gz

This is the latest version of the feedback log.

[symbuzzer]

在我的另一台设备（小米Pad 5 Pro 5G）上，也是同样的问题。我想我应该给你日志的反馈。 APatch_bugreport_2024-04-12_14_57.tar.gz

This is the latest version of the feedback log.

Still cant see any suspcious thing

[MobInfinity]

Xiaomi 13 Pro HyperoOS v816.0.2.4.8.DEV KernelSU v0.9.2-104(11786) LKM After the module is swiped in, it is stuck in the last interface before the System Desktop.Not working properly. After a few minutes, the system reboots again and successfully powers on, but the module is not available.

Can you look at the log of this again?
KernelSU_bugreport_2024-04-16_23_31.tar.gz

[MobInfinity]

There is only one file under this path /data/adb/modules/systemless-hosts-KernelSU-module/

[kb8023]

在我的另一台设备（小米Pad 5 Pro 5G）上，也是同样的问题。我想我应该给你日志的反馈。APatch_bugreport_2024-04-12_14_57.tar.gz

这是反馈日志的最新版本。

仍然看不到任何可疑的东西

在我的另一台设备（小米Pad 5 Pro 5G）上，也是同样的问题。我想我应该给你日志的反馈。APatch_bugreport_2024-04-12_14_57.tar.gz

这是反馈日志的最新版本。

仍然看不到任何可疑的东西

Hello, I also encountered the same problem. At first, I thought it was a problem with my phone. The last two phones were like this, one was the Xiaomi 10 Ultimate version OS 1.0.4.0 a13, which used Apatch 0.10.7 10736 version, and the other was the k70pro OS 1.0.15.0 a14, which used kernelsu 11874 lkm mode to flash in the 1.14 version module. After restarting the second interface, the module did not take effect and has been flashed in. Both phones have the same zygisk next LSP framework. Other modules are different from those of the owner

[lovelyelfpop]

我的手机是 k70 pro hyperos 1.0.18.0，用的 kernelSU 1.0.0。
安装了这个模块后，我本想利用工作资料多开App，于是使用以下命令先解除多开限制：

adb -d shell
su

  resetprop ro.debuggable 1
  setprop persist.sys.max_profiles 10
  am restart

但是 am restart 执行后重启会卡在 xiaomi hyperos 界面。过了很久进不去系统，此时手机自动再重启了一次，才进入系统，但是此时多开限制没有解除。（多开限制只有在 am restart 那一次重启成功后才会暂时解除）

我把手机三清，重复测试了很多次，都是这个现象。不装或者卸载掉这个模块，解除多开限制就非常顺利。

测试了1.1.2, 1.1.3, 1.1.4 都是一样的现象

[MobInfinity]

有没有可能是因为我已经双开了应用，开机才卡系统界面哦

[lovelyelfpop]

有没有可能是因为我已经双开了应用，开机才卡系统界面哦

很有可能。我有一次就是利用工作资料多开了之后，重启就卡开机界面了，同样之前装了这个模块。

另外还有个System false encryption 模块也是在hyperos上用不了，开机到桌面后就会动重启，重启后数据全部丢失。

我最后用 爱玩机工具箱 代替这个systemless-hosts-KernelSU-module 和 Ad Away了。爱玩机工具箱 - 系统相关 - hosts管理 可以订阅屏蔽广告源

[Gleb2372372]

Try this module I got it working https://github.com/dchristl/KernelSU-systemless-hosts?tab=readme-ov-file or https://github.com/backslashxx/bindhosts

[MobInfinity]

Try this module I got it working https://github.com/dchristl/KernelSU-systemless-hosts?tab=readme-ov-file

谢谢，我用另外的模块（bindhosts）和方法解决问题了。