KernelSU doesn't support ChromeOS ARM ARCVM

[YsLtr]

Please check before submitting an issue

• I have searched the issues and haven't found anything relevant
• I will upload bugreport file in KernelSU Manager - Settings - Report log
• I know how to reproduce the issue which may not be specific to my device

Describe the bug

I replaced the kernel this path /opt/google/vms/android/vmlinux in my devices with @iceyear 's PR here, it didm't work properly and cause the arcvm broken. No android application can start after reboot. We thought it's because kernelSU hasn't made a support to arm arcvm in ChromeOS.

To Reproduce

1. Download latest arm arcvm compiled file from ACTION
2. move the file to SD Card
3. Using Ctrl + Alt + F2 (Flashing button on Chromebook) to enter VT-2
4. log in and using sudo -i to ROOT
5. mv /opt/google/vms/android/vmlinux /opt/google/vms/android/vmlinux.bak to backup the kernel
6. cp /media/removavle/SD\ Card/Image /opt/google/vms/android/vmlinux
7. reboot

Expected behavior

After reboot, I can get root in android.

Screenshots

Logs

Here is my origin kernel

Device info

• Device: HP Chromebook x2 11
• OS Version: ChromeOS 123.0.6312.132 and Android 11 in ARCVM
• KernelSU Version: 0.9.2
• Kernel Version: 5.10.209

Additional context

I can supprt to test the new kernel on my device if ever.

[tiann]

We need the logs

[YsLtr]

We need the logs

But how? I can't get logs from KernelSU Manager after replaced the kernel. Because it couldn't open.😭

[YsLtr]

KernelSU_bugreport_2024-04-24_10_42.tar.gz
This is the only one I can get after replace the kernel and recover it. I don't know if it's helpful.

[tiann]

I have not used ChromeOS, so I do not know; perhaps you need to search for how to use adb to connect to the Android system inside ChromeOS, and then use ADB to obtain logs.

[YsLtr]

I have not used ChromeOS, so I do not know; perhaps you need to search for how to use adb to connect to the Android system inside ChromeOS, and then use ADB to obtain logs.

I tried.

However, it's useless. The Android system inside ChromeOS would not work with the kernel replaced with a wrong one. So adb couldn't found any devices if I want to connect android.

Maybe I should try to build and test a kernel myself. But before I am able to learn about it, I think its wiser to find another way to root the Android or wait for someone who can solve the problem.

[iceyear]

Crash Collectors
Maybe this would be helpful

[YsLtr]

Thank you.
Here are two logs I found in /var/log/ after replaced the kernel.
arc.log
arc.1.log

And these are logs collected with the origin kernel
arc.log
arc.1.log

[YsLtr]

With @iceyear 's help. I got dmesg logs from chrome://system/#arcvm_console_output
And here are two different logs collected.
This is the one with origin kernel:
arcvm_console_output_Origin.txt
This is the one with replaced kernel:
arcvm_console_output_After_Replace.txt

Wish it would be helpful.

[tiann]

I see no KernelSU related logs in dmesg, so it is possible that even without integrating KernelSU, the kernel compiled in this way may not work.

[tiann]

You should confirm that the kernel compiled from source code would work well without KernelSU.

[YsLtr]

Some problem has been found:
My device (HP Chromebook x2 11) only got Android 11 but most of ChromeOS had got Android 13, so the kernel may even not work on my device without KernelSU.

[zanjie1999]

Kernel imagecan boot but not working,
Kernel image能启动，但是kernelsu提示未安装，

现在的最新版本v0.9.3 使用 kernel-ARCVM-arm64-5.10.209.zip 中的Image替换vmlinux 可以正常启动，但是kernelsu管理器提示未安装，看内核版本确实已经替换成功了（我的是arm64 mt8183）

the latest version v0.9.3 use Image in kernel-ARCVM-arm64-5.10.209.zip to replacement vmlinux is working normally, but the kernelsu manager show not install , and the kernel version has been successfully updated (use arm64 mt8183 )

my logs
KernelSU_bugreport_2024-04-29_11_43.tar.gz

[tiann]

upload dmesg logs

[zanjie1999]

upload dmesg logs

chromeos-dmesg.txt
I have not adb access for arcvm, this log is outside of arcvm

[tiann]

No KernelSU related logs found. You can check the image to see if KernelSU is integrated correctly.

[zanjie1999]

Tips: enable chromeos arcvm adb without linux vm
settings->apps->google play store->manage android preferences->system->developer options

adb logcat of arcvm
arcvm-logcat.txt

I install KernelSU with this sh file
https://github.com/zanjie1999/ChromeOS-ARCVM-Root/blob/main/root.sh

[zanjie1999]

No KernelSU related logs found. You can check the image to see if KernelSU is integrated correctly.

I restored arcvm's default vmlinux:

kernel version is 5.10.209-997258

and I use Image in kernel-ARCVM-arm64-5.10.209.zip download from releases to replacement vmlinux file in /opt/google/vms/android :

kernel version is 5.10.209-android12-9

I think maybe kernel is OK, but KernelSU is not work

[tiann]

The fact is that there is no log for KernelSU in your log; even if it doesn't work, it will output at least one line of log during kernel module initialization.

[iceyear]

upload dmesg logs

chromeos-dmesg.txt I have not adb access for arcvm, this log is outside of arcvm

@zanjie1999 It seems like this is the chromeos's dmesg but not arcvm's. Try chrome://system/#arcvm_console_output to fetch arcvm dmesg logs.

[zanjie1999]

上传 dmesg 日志

chromeos-dmesg.txt我没有 arcvm 的 adb 访问权限，此日志位于 arcvm 之外

@zanjie1999看起来这是 chromeos 的 dmesg 而不是 arcvm 的。尝试使用 chrome://system/#arcvm_console_output 获取 arcvm dmesg 日志。

I've downgraded my system to ChromeOS 113 to use ARC++ (

因为经历了文章最后的事故 https://zyyme.com/arm-chromebook-cgpt.html
我已经用全盘dd镜像降级系统到113了，顺便用回ARC++，因为ARCVM的性能实在是太差了

[YsLtr]

Kernel imagecan boot but not working, Kernel image能启动，但是kernelsu提示未安装，

现在的最新版本v0.9.3 使用 kernel-ARCVM-arm64-5.10.209.zip 中的Image替换vmlinux 可以正常启动，但是kernelsu管理器提示未安装，看内核版本确实已经替换成功了（我的是arm64 mt8183）

the latest version v0.9.3 use Image in kernel-ARCVM-arm64-5.10.209.zip to replacement vmlinux is working normally, but the kernelsu manager show not install , and the kernel version has been successfully updated (use arm64 mt8183 )

my logs KernelSU_bugreport_2024-04-29_11_43.tar.gz

It seems that your Android version is 12. It's different from mine (Android 11). So maybe only Android 12 can boot with this vmlinux.

[iceyear]

Kernel imagecan boot but not working, Kernel image能启动，但是kernelsu提示未安装，
现在的最新版本v0.9.3 使用 kernel-ARCVM-arm64-5.10.209.zip 中的Image替换vmlinux 可以正常启动，但是kernelsu管理器提示未安装，看内核版本确实已经替换成功了（我的是arm64 mt8183）
the latest version v0.9.3 use Image in kernel-ARCVM-arm64-5.10.209.zip to replacement vmlinux is working normally, but the kernelsu manager show not install , and the kernel version has been successfully updated (use arm64 mt8183 )
my logs KernelSU_bugreport_2024-04-29_11_43.tar.gz

It seems that your Android version is 12. It's different from mine (Android 11). So maybe only Android 12 can boot with this vmlinux.

[zanjie1999]

Kernel imagecan boot but not working, Kernel image能启动，但是kernelsu提示未安装，
现在的最新版本v0.9.3 使用 kernel-ARCVM-arm64-5.10.209.zip 中的Image替换vmlinux 可以正常启动，但是kernelsu管理器提示未安装，看内核版本确实已经替换成功了（我的是arm64 mt8183）
the latest version v0.9.3 use Image in kernel-ARCVM-arm64-5.10.209.zip to replacement vmlinux is working normally, but the kernelsu manager show not install , and the kernel version has been successfully updated (use arm64 mt8183 )
my logs KernelSU_bugreport_2024-04-29_11_43.tar.gz

It seems that your Android version is 12. It's different from mine (Android 11). So maybe only Android 12 can boot with this vmlinux.

my Android version is 11, this image(kernel version is 5.10.209-android12-9) was taken after use KernelSU vmlinux imagel, maybe KernelSU only work on Android 12 arcvm : )
but this vmlinux image can boot Android 11 arcvm XD

[tiann]

The concept of GKI only applies to devices such as smartphones, other devices like simulators, watches, and virtual machines do not follow KMI.

[tiann]

So, what's the issue now?

[YsLtr]

So, what's the issue now?

The origin. No more progress.

More clearer, KernelSU doesn't work on arm64 chromebook. Maybe we need another different people to test it and give a feedback.

Make a conclusion. @zanjie1999 could boot it after replace the kernel but faild in root and mine couldn't even boot XD.

[tiann]

But i did't see any logs related with KernelSU.

[YsLtr]

But i did't see any logs related with KernelSU.

It's exactlly a serious problem. So we need more difference devices to break the deadlock.