-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
安卓14(coloros14)使用fastboot刷入android12-5.10.168_2023-05-boot.img无限重启 #1051
Comments
It may cause by your device. There might be some problems with GKI kernel. Check if you choose the correct kernel. Then, you can try AnyKernel. GKI的bug?是不是内核选错了,试试AnyKernel捏 具体给一下手机型号 如果都不行,尝试自己编译没有ksu的GKI内核看看开不开机,如果仍然不开机说明非ksu问题,开机说明是ksu的问题,请提供logcat |
遇到同样的问题,无论直接使用提供的内核刷入,还是提取卡刷包的boot用AnyKernel里的内核进行修补后刷入,都是无限重启,手机型号为一加ACE 2V,系统为coloros14。但用magisk delta修补boot刷入后magisk delta能正常工作。 |
https://source.android.com/docs/core/architecture/kernel/gki-android12-5_10-release-builds?hl=zh-cn 下载了这个版本,gki-certified-boot-android12-5.10-2023-04_r1-gz,刷入后同样无限重启。 |
那就说明是gki的bug关掉issue因为不关ksu的事 建议去问OPPO写的什么垃圾 |
ksu 启动失败后,刷回带有 magisk 的 boot 提供一下 pstore 日志。 |
pstore 日志怎么获取呢,查了半天没找到有用的信息,麻烦空了指导下 |
参考一下Linux |
/sys/fs/pstore 下的文件发出来 |
谢谢,这个目录我也查到了,里面是空的,所以才来请教怎么获取日志,明天要出差,下周回来试试先刷ksu启动失败后,再刷回带有 magisk 的 boot看看里面会不会有文件。 |
正常情况下这里就是空的,只有异常启动里面才会有日志 |
The same thing happens for Xiaomi 12 Pro. Rom: CRDroid Tried KSU - AnyKernel3-android13-5.10.168_2023-05.zip
|
We can do nothing without any logs |
The folder is empty |
进Recovery清除数据就可以开机了 |
刷入android12-5.10.168_2023-05-boot-gz启动失败后,重新刷入带有 magisk 的 boot,开机后/sys/fs/pstore目录还是空的 |
按照这个说法,可能是 dm-verity 的问题,建议你们关闭 dm-verity 或者清除数据再试。 |
并不能,关闭 dm-verity 没用 |
"进Recovery清除数据就可以开机了" 这样操作呢? |
这个我验证了,清除数据后正常开机,ksu也正常工作 |
但是我刷入的时候甚至没法进入rec,进入fastboot后一分钟左右不操作会自动重启 |
刷入magisk后偶尔会无法开机,报错zygote died,可能是zygisk的问题?因为我KernelSu也装了zygisk |
刷入0.7版本的boot后依旧如此,pstore文件夹也是空的 |
试过了不行,一加11 coloros 14 kernel 版本 5.15.94-android13-8-o-00689-g1457669e1c45,试了下面这些都不行 AnyKernel3-android13-5.15.94_2023-05.zip |
这个跟 GKI 无关吧?三星的设备,从官方刷第三方第一次也需要清数据。 |
我这边13不用格,都是直接刷,14的官方内核加了点料,不是纯粹的GKI |
So there is no perfect solution yet? |
@tiann Is this happening because source code not released for the kernel? |
I don't know, i don't have such devices. |
我与各位遇到了同样的情况,无论直接使用提供的内核刷入,还是提取卡刷包的boot用AnyKernel里的内核进行修补后刷入,都是无限重启,手机型号为一加ACE 2V,系统为coloros14。 |
在重启后会自动进入系统的rec,在系统rec中选择重启后进入循环,刷回官方boot后恢复正常。 |
目前未尝试在rec中选择清除数据是否能回复,依据此前的对话应该可以,明日尝试后回复。 |
你能尝试一下吗? |
我的一加ace2遇到了一摸一样的问题 |
Which kernel version you are using exactly? |
Tested on OnePlus 12 ColorOS 14 android14-6.1.25 . Device still got fastboot-loop after wipe data partition |
So kernelsu some how stopped working for Color OS 14 and OOS 14 |
try latest ci version |
If u meant by file in the CI group. It seems to have android 13 and 14 kernel versions |
try this :https://github.com/tiann/KernelSU/actions/runs/7180854283 AnyKernel3-android14-6.1.25_2023-10 and AnyKernel3-android14-6.1.25_2023-10 |
But I have a different version of Kernel, 5.10.168 Android12-9 |
@tiann no solution for this yet? |
怎么就closed了呢?还没解决呢 |
exactly my question. I don't know developer doesn't seem to care about this issue |
仔细阅读本 issue,你会找到解决方案。#1051 (comment) |
第一次刷入清空数据这都不是啥问题,现在有个问题是夜间充电手机会进入假死状态,必须强制重启,这个问题比较麻烦 |
+1,确实会假死,一加12,我还没确认是 ksu 的问题,这两天还在关各种模块尝试,如果能确认是 ksu 导致的建议重开一个 issue |
我换了magisk 再没出现过,主要是这个假死问题我没抓到过有效的log,没法开issue |
@tiann Sorry to say it may have worked on Oneplus 11. But it didn't worked on OnePlus 11R, also wiping data everytime after an update comes for kernelsu doesn't seem viable |
你是ace2v吗? 是否支持fastboot boot直接启动? |
Anyone tried the new LKM? Is device still freezeing on this mode? I can't test it because I've already returned my device due to this issue. |
with wipe data, kernelsu works. and freezeing at night when charging with smart charge on. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: