Bootloop after Pixel March Update
Please check before submitting an issue/在提交 issue 前请检查
- [x] I have searched the issues and haven't found anything relevant/我已经搜索了 issues 列表,没有发现于本问题相关内容
- [x] If patch failed, root failed, or device unable to boot after flashing the new boot.img. Please goto KernelPatch/修复失败或刷入修补后镜像不能启动,请前往 KernelPatch 提问
- [x] I will upload bugreport file in APatch Manager - Settings - Report log/我会上传 bureport 文件从 APatch 管理器 - 设置 - 发送日志
- [x] I know how to reproduce the issue which may not be specific to my device/我知道如何重新复现这个问题
Version requirement/版本要求
- [x] I am using latest CI version of APatch/我正在使用最新 CI 版本
Describe the bug/描述 bug
Thank you very much for your app. I appreciate your hard work.
It seems that after the Android March Update for Pixel Devices, rooting no longer works. After flashing the patched boot.img I get a boot loop. My pixel 7 hangs at the google boot logo and then restarts.
Reproduce method/复现方法
Flash patched Bootimage
Expected behavior/预期行为
Normal Boot
Actual behaviour /实际行为
Bootloop
Screenshots/截图
No response
Logs/日志
No response
Device Name/设备名称
Pixel 7
OS Version/系统版本
Android 15 March Update
APatch Version/APatch 版本
11039
Kernel Version/内核版本
6.1.99-android14-11-gd6f926cfde54-ab12786694
KernelPatch Version/KernelPatch 版本
255.255.255
Additional context/其他信息
Same here, even after I flash the official boot.img, it still get boot loop.
Temporary solution: execute flash-all.sh to recover, but lose root.
The same. Pixel 7. Even when cleaning the device and deleting all the partitions, I have a bootloop. Recovery the default boot.img has restored the startup device.
Need any additional data/logs?
Pixel 7 Pro here with the same issue
Same issue with Pixel 7 Pro. Unfortunately had to revert to Magisk temporarily. I'm sure the team here will provide a solution. Thank you all for your work.
same issue with Pixel 7 pro as well.
Can confirm this issue, Pixel 7 Pro
same here with px6
Same with Pixel 7 Pro
Same issue Pixel 7
Same issue with Pixel 7 Pro
May I suggest that additional visitors make use of the 👍 function on the original post so that we can track impact without needing to trigger 10 emails for each new comment?
I have the exact same problem Google Pixel Android 15 Android 14-11 Kernel 6.1.99
I end up after losing everything to flash with KernelSU. Is there no fix for this problem?
Having the same issue on my Pixel 7a (March Update). I Had a successful first launch, but then phone proceeded with bootloop on the device's reboot.
KernelSU works great 😋
I had a similar bootloop with KernelSU trying to migrate to that, magisk is working ok however. Although I did try to switch to KernelSU while maintaining root with the OTA/second partition trick. It sounds like losing root and regaining it with flashboot flashing would have worked.
I guess at this point we are looking for an alternative rather than holding out for a fix.
I was able to switch to KernelSU-Next without losing any data using PixelFlasher. Works great on Pixel7, March 2025 patch.
For some reason, applying this patch to KernelPatch lets it boot up for me:
diff --git a/kernel/base/hook.c b/kernel/base/hook.c
index e23e60e..6a8904f 100644
--- a/kernel/base/hook.c
+++ b/kernel/base/hook.c
@@ -506,6 +506,8 @@ _transit12(uint64_t arg0, uint64_t arg1, uint64_t arg2, uint64_t arg3, uint64_t
extern void _transit12_end();
+#pragma GCC push_options
+#pragma GCC optimize ("O0")
static __noinline hook_err_t relocate_inst(hook_t *hook, uint64_t inst_addr, uint32_t inst)
{
hook_err_t rc = HOOK_NO_ERR;
@@ -557,6 +559,7 @@ static __noinline hook_err_t relocate_inst(hook_t *hook, uint64_t inst_addr, uin
return rc;
}
+#pragma GCC pop_options
hook_err_t hook_prepare(hook_t *hook)
{
diff --git a/kernel/patch/ksyms/task_cred.c b/kernel/patch/ksyms/task_cred.c
index d78ad80..ac64414 100644
--- a/kernel/patch/ksyms/task_cred.c
+++ b/kernel/patch/ksyms/task_cred.c
@@ -176,6 +176,8 @@ static void add_bll(int16_t off, int16_t size)
}
}
+#pragma GCC push_options
+#pragma GCC optimize ("O0")
int resolve_cred_offset()
{
log_boot("struct cred: \n");
@@ -373,6 +375,7 @@ int resolve_cred_offset()
uninit_bllist();
return 0;
}
+#pragma GCC pop_options
static int find_swapper_comm_offset(uint64_t start, int size)
{
This is on helluvaOS Android 15 (BP1A.250505.005, May security patch) running on a Pixel 7a with KernelPatch compiled with GCC 14.2.1 (aarch64-none-elf-gcc-bin on AUR). I have no idea why this lets it boot since I haven't inspected the codegen changes yet.
EDIT: Also fixes it on stock A16
Has this been fixed? I am new to rooting. I was considering rooting with APatch instead of magisk. If this is not fixed I will choose to go with magisk. ( I have Pixel 7 with Android 16, i.e the Pixel June Update)
Thank you for bringing up apatch version 11107 . After flashing the patched boot image with version 11107, the device reboots right after the lockscreen.
Pixel 7 Android 16 June 2025 Update Kernel: 6.1.124-android14-11-g8d713f9e8e7b-abi13202960
same here with a Pixel 8 on Android 15
same here in pixel6 with oriole-bp2a.250605.031.a5