安卓14(coloros14）使用fastboot刷入android12-5.10.168_2023-05-boot.img无限重启 #1051

ConneRSama · 2023-10-18T03:04:13Z

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behaviour:

Go to '...'
Click on '....'
Scroll down to '....'
See the error

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):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Bot-wxt1221 · 2023-10-18T03:15:08Z

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捏

具体给一下手机型号

#1039

如果都不行，尝试自己编译没有ksu的GKI内核看看开不开机，如果仍然不开机说明非ksu问题，开机说明是ksu的问题，请提供logcat

fkueyu · 2023-10-18T03:23:59Z

遇到同样的问题，无论直接使用提供的内核刷入，还是提取卡刷包的boot用AnyKernel里的内核进行修补后刷入，都是无限重启，手机型号为一加ACE 2V，系统为coloros14。但用magisk delta修补boot刷入后magisk delta能正常工作。

Bot-wxt1221 · 2023-10-18T03:32:29Z

https://source.android.com/docs/core/architecture/kernel/gki-android12-5_10-release-builds?hl=zh-cn

这里面去下不带ksu的包试试呢

fkueyu · 2023-10-18T03:45:14Z

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，刷入后同样无限重启。

Bot-wxt1221 · 2023-10-18T06:43:10Z

那就说明是gki的bug关掉issue因为不关ksu的事

建议去问OPPO写的什么垃圾

tiann · 2023-10-18T06:53:48Z

ksu 启动失败后，刷回带有 magisk 的 boot 提供一下 pstore 日志。

fkueyu · 2023-10-18T08:52:07Z

pstore 日志怎么获取呢，查了半天没找到有用的信息，麻烦空了指导下

Bot-wxt1221 · 2023-10-18T08:56:40Z

参考一下Linux

tiann · 2023-10-18T12:19:01Z

/sys/fs/pstore 下的文件发出来

fkueyu · 2023-10-18T12:28:28Z

谢谢，这个目录我也查到了，里面是空的，所以才来请教怎么获取日志，明天要出差，下周回来试试先刷ksu启动失败后，再刷回带有 magisk 的 boot看看里面会不会有文件。

tiann · 2023-10-18T12:35:40Z

正常情况下这里就是空的，只有异常启动里面才会有日志

Quelaan1 · 2023-10-19T17:58:57Z

The same thing happens for Xiaomi 12 Pro.

Rom: CRDroid
Working Kernel (Not KSU): Linux version 5.10.168-android12-9-dirty (build-user@build-host) (Android (7284624, based on r416183b) clang version 12.0.5 (https://android.googlesource.com/toolchain/llvm-project c935d99d7cf2016289302412d708641d52d2f7ee), LLD 12.0.5 (/buildbot/src/android/llvm-toolchain/out/llvm-project/lld c935d99d7cf2016289302412d708641d52d2f7ee)) #1 SMP PREEMPT Thu Jul 13 05:31:46 UTC 2023

Tried KSU - AnyKernel3-android13-5.10.168_2023-05.zip
AnyKernel3-android12-5.10.168_2023-05.zip

               Through TWRP and Kernel Flasher

tiann · 2023-10-20T00:29:04Z

We can do nothing without any logs

Quelaan1 · 2023-10-20T03:58:11Z

The folder is empty

hamjin · 2023-10-20T09:26:51Z

进Recovery清除数据就可以开机了
补充：刷完ksu内核后再进recovery清
Tested on OnePlus PHK110 14.0.0.81

fkueyu · 2023-10-21T04:33:57Z

正常情况下这里就是空的，只有异常启动里面才会有日志

刷入android12-5.10.168_2023-05-boot-gz启动失败后，重新刷入带有 magisk 的 boot，开机后/sys/fs/pstore目录还是空的

tiann · 2023-10-21T05:29:14Z

进Recovery清除数据就可以开机了

按照这个说法，可能是 dm-verity 的问题，建议你们关闭 dm-verity 或者清除数据再试。

snipking · 2023-10-24T12:09:33Z

进Recovery清除数据就可以开机了

按照这个说法，可能是 dm-verity 的问题，建议你们关闭 dm-verity 或者清除数据再试。

并不能，关闭 dm-verity 没用

tiann · 2023-10-24T12:24:58Z

"进Recovery清除数据就可以开机了" 这样操作呢？

fkueyu · 2023-10-24T12:30:29Z

"进Recovery清除数据就可以开机了" 这样操作呢？

这个我验证了，清除数据后正常开机，ksu也正常工作

ConneRSama · 2023-10-24T12:34:44Z

"进Recovery清除数据就可以开机了" 这样操作呢？

这个我验证了，清除数据后正常开机，ksu也正常工作

但是我刷入的时候甚至没法进入rec，进入fastboot后一分钟左右不操作会自动重启

ConneRSama · 2023-10-24T12:38:35Z

"进Recovery清除数据就可以开机了" 这样操作呢？

这个我验证了，清除数据后正常开机，ksu也正常工作

但是我刷入的时候甚至没法进入rec，进入fastboot后一分钟左右不操作会自动重启

刷入magisk后偶尔会无法开机，报错zygote died，可能是zygisk的问题？因为我KernelSu也装了zygisk

ConneRSama · 2023-10-24T12:59:16Z

刷入0.7版本的boot后依旧如此，pstore文件夹也是空的

snipking · 2023-10-25T05:29:26Z

https://github.com/tiann/KernelSU/releases/download/v0.7.0/AnyKernel3-android12-5.10.185_2023-09.zip It is possible to use this kernel and it will work fine. Using the updated kernel from 2023-September will work normally.

试过了不行，一加11 coloros 14 kernel 版本 5.15.94-android13-8-o-00689-g1457669e1c45，试了下面这些都不行

AnyKernel3-android13-5.15.94_2023-05.zip
AnyKernel3-android13-5.15.104_2023-07.zip
AnyKernel3-android13-5.15.119_2023-09.zip
AnyKernel3-android13-5.15.123_2023-10.zip
android13-5.15.94_2023-05-boot.img.gz
android13-5.15.119_2023-09-boot.img.gz
android13-5.15.123_2023-10-boot.img.gz

bugme2 · 2023-10-25T06:32:41Z

黑厂往gki里加料了，不关ksu的事，目前的解决方式是用fastboot -w格式化，官方rec和twrp格式化不了，如果刷回官方内核，估计又得再格式化一遍才能用第三方内核了。

snipking · 2023-10-25T06:55:17Z

黑厂往gki里加料了，不关ksu的事，目前的解决方式是用fastboot -w格式化，官方rec和twrp格式化不了，如果刷回官方内核，估计又得再格式化一遍才能用第三方内核了。

诶，那岂不是以后每次升级都得格式化，WTF

tiann · 2023-10-25T06:59:26Z

这个跟 GKI 无关吧？三星的设备，从官方刷第三方第一次也需要清数据。
解锁清一次，刷 boot 还要再清一次。

bugme2 · 2023-10-25T08:25:26Z

跟这个GKI关联吧？三星的设备，从官方刷第三方第一次也需要清数据。解锁清一次，刷开机还要再清一次。

我这边13不用格，都是直接刷，14的官方内核加了点料，不是纯粹的GKI

ashoktvm · 2023-12-05T10:43:57Z

So there is no perfect solution yet?

ashoktvm · 2023-12-08T05:43:13Z

@tiann Is this happening because source code not released for the kernel?

tiann · 2023-12-08T08:46:05Z

I don't know, i don't have such devices.

weiwei-cool · 2023-12-09T15:47:18Z

我与各位遇到了同样的情况，无论直接使用提供的内核刷入，还是提取卡刷包的boot用AnyKernel里的内核进行修补后刷入，都是无限重启，手机型号为一加ACE 2V，系统为coloros14。

weiwei-cool · 2023-12-09T15:56:43Z

在重启后会自动进入系统的rec，在系统rec中选择重启后进入循环，刷回官方boot后恢复正常。

weiwei-cool · 2023-12-09T15:58:00Z

在重启后会自动进入系统的rec，在系统rec中选择重启后进入循环，刷回官方boot后恢复正常。

目前未尝试在rec中选择清除数据是否能回复，依据此前的对话应该可以，明日尝试后回复。

ashoktvm · 2023-12-10T12:52:36Z

After restarting, it will automatically enter the REC of the system, select Restart in the system REC to enter the loop, and return to normal after flashing back to the official BOOT.

At present, I have not tried to select whether I can reply to clear the data in the REC, but it should be possible based on the previous conversation, and I will reply after trying tomorrow.

你能尝试一下吗？

949331213 · 2023-12-11T11:54:08Z

遇到同样的问题，无论直接使用提供的内核刷入，还是提取卡刷包的boot用AnyKernel里的内核进行修补后刷入，都是无限重启，手机型号为一加ACE 2V，系统为coloros14。但用magisk delta修补boot刷入后magisk delta能正常工作。

我的一加ace2遇到了一摸一样的问题

ashoktvm · 2023-12-12T07:25:18Z

"Go to Recovery to clear the data and boot up" How about this operation?

I verified this, after clearing the data, it turned on normally, and KSU also worked normally

Which kernel version you are using exactly?

sky96111 · 2023-12-12T12:55:34Z

Tested on OnePlus 12 ColorOS 14 android14-6.1.25 . Device still got fastboot-loop after wipe data partition

ashoktvm · 2023-12-12T16:31:54Z

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

tiann · 2023-12-13T02:58:00Z

try latest ci version

snipking · 2023-12-13T03:02:24Z

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

@ashoktvm @sky96111 wipe data partiton works on oneplus 12 ColorOS 14 PJD110_14.0.0.232(CN01) with ak3-android14-6.1.25

ashoktvm · 2023-12-13T06:48:35Z

try latest ci version

If u meant by file in the CI group. It seems to have android 13 and 14 kernel versions

neoshui · 2023-12-15T06:19:13Z

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

ashoktvm · 2023-12-15T06:34:24Z

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

ashoktvm · 2023-12-18T05:19:34Z

@tiann no solution for this yet?

tufeigunchu · 2023-12-23T02:19:57Z

怎么就closed了呢？还没解决呢

ashoktvm · 2023-12-23T03:12:31Z

Why is it closed? It hasn't been solved yet

exactly my question. I don't know developer doesn't seem to care about this issue

tiann · 2023-12-23T03:27:06Z

仔细阅读本 issue，你会找到解决方案。#1051 (comment)

neoshui · 2023-12-23T04:16:41Z

仔细阅读本 issue，你会找到解决方案。#1051 (comment)

第一次刷入清空数据这都不是啥问题，现在有个问题是夜间充电手机会进入假死状态，必须强制重启，这个问题比较麻烦

snipking · 2023-12-23T05:49:14Z

仔细阅读本 issue，你会找到解决方案。#1051 (comment)

第一次刷入清空数据这都不是啥问题，现在有个问题是夜间充电手机会进入假死状态，必须强制重启，这个问题比较麻烦

+1，确实会假死，一加12，我还没确认是 ksu 的问题，这两天还在关各种模块尝试，如果能确认是 ksu 导致的建议重开一个 issue

neoshui · 2023-12-23T05:53:14Z

仔细阅读本 issue，你会找到解决方案。#1051 (comment)

第一次刷入清空数据这都不是啥问题，现在有个问题是夜间充电手机会进入假死状态，必须强制重启，这个问题比较麻烦

+1，确实会假死，一加12，我还没确认是 ksu 的问题，这两天还在关各种模块尝试，如果能确认是 ksu 导致的建议重开一个 issue

我换了magisk 再没出现过，主要是这个假死问题我没抓到过有效的log，没法开issue

ashoktvm · 2023-12-23T07:23:16Z

Read this issue carefully and you'll find a solution. #1051 (comment)

@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

tufeigunchu · 2023-12-27T02:41:07Z

跟这个GKI关联吧？三星的设备，从官方刷第三方第一次也需要清数据。解锁清一次，刷开机还要再清一次。

我这边13不用格，都是直接刷，14的官方内核加了点料，不是纯粹的GKI

你是ace2v吗？是否支持fastboot boot直接启动？

sky96111 · 2024-03-26T07:00:30Z

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.

snipking · 2024-03-26T07:47:52Z

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.

SK-415 · 2024-04-04T05:51:06Z

LKM works good. No wipe data needed. Charged whole last night and haven't met the freezing problem yet.

tiann closed this as completed Oct 21, 2023

tiann mentioned this issue Oct 24, 2023

Support for oxygen os 14 one plus #1081

Closed

tiann mentioned this issue Dec 5, 2023

OxygenOS 14 Not Supported? #1182

Closed

3 tasks

tiann mentioned this issue May 2, 2024

Failed to fastboot boot to the temp system with boot.img provided by KernelSU under Color OS 14 #1661

Closed

3 tasks

安卓14(coloros14）使用fastboot刷入android12-5.10.168_2023-05-boot.img无限重启 #1051

安卓14(coloros14）使用fastboot刷入android12-5.10.168_2023-05-boot.img无限重启 #1051

Comments

ConneRSama commented Oct 18, 2023

Bot-wxt1221 commented Oct 18, 2023 • edited

fkueyu commented Oct 18, 2023

Bot-wxt1221 commented Oct 18, 2023 • edited

fkueyu commented Oct 18, 2023

Bot-wxt1221 commented Oct 18, 2023 • edited

tiann commented Oct 18, 2023

fkueyu commented Oct 18, 2023

Bot-wxt1221 commented Oct 18, 2023

tiann commented Oct 18, 2023

fkueyu commented Oct 18, 2023

tiann commented Oct 18, 2023

Quelaan1 commented Oct 19, 2023

tiann commented Oct 20, 2023

Quelaan1 commented Oct 20, 2023

hamjin commented Oct 20, 2023 • edited

fkueyu commented Oct 21, 2023

tiann commented Oct 21, 2023

snipking commented Oct 24, 2023

tiann commented Oct 24, 2023

fkueyu commented Oct 24, 2023

ConneRSama commented Oct 24, 2023

ConneRSama commented Oct 24, 2023

ConneRSama commented Oct 24, 2023

snipking commented Oct 25, 2023

bugme2 commented Oct 25, 2023 • edited

snipking commented Oct 25, 2023

tiann commented Oct 25, 2023 • edited

bugme2 commented Oct 25, 2023

ashoktvm commented Dec 5, 2023

ashoktvm commented Dec 8, 2023

tiann commented Dec 8, 2023

weiwei-cool commented Dec 9, 2023

weiwei-cool commented Dec 9, 2023

weiwei-cool commented Dec 9, 2023

ashoktvm commented Dec 10, 2023

949331213 commented Dec 11, 2023

ashoktvm commented Dec 12, 2023

sky96111 commented Dec 12, 2023

ashoktvm commented Dec 12, 2023

tiann commented Dec 13, 2023

snipking commented Dec 13, 2023

ashoktvm commented Dec 13, 2023 • edited

neoshui commented Dec 15, 2023

ashoktvm commented Dec 15, 2023 • edited

ashoktvm commented Dec 18, 2023

tufeigunchu commented Dec 23, 2023

ashoktvm commented Dec 23, 2023

tiann commented Dec 23, 2023

neoshui commented Dec 23, 2023

snipking commented Dec 23, 2023 • edited

neoshui commented Dec 23, 2023

ashoktvm commented Dec 23, 2023 • edited

tufeigunchu commented Dec 27, 2023

sky96111 commented Mar 26, 2024 • edited

snipking commented Mar 26, 2024

SK-415 commented Apr 4, 2024

Bot-wxt1221 commented Oct 18, 2023 •

edited

Bot-wxt1221 commented Oct 18, 2023 •

edited

Bot-wxt1221 commented Oct 18, 2023 •

edited

hamjin commented Oct 20, 2023 •

edited

bugme2 commented Oct 25, 2023 •

edited

tiann commented Oct 25, 2023 •

edited

ashoktvm commented Dec 13, 2023 •

edited

ashoktvm commented Dec 15, 2023 •

edited

snipking commented Dec 23, 2023 •

edited

ashoktvm commented Dec 23, 2023 •

edited

sky96111 commented Mar 26, 2024 •

edited