-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Boot failure after installing December 2023 update on my Google Pixel 6 Pro #1195
Comments
I have this issue too! |
Which factory image do you use? it works well on my Pixel 6. |
https://developers.google.com/android/images#ravenuq1a.231205.015 The international version (14.0.0 (UQ1A.231205.015, Dec 2023), so not the AT&T image. |
me too. how you solve this issue? |
same problem also but on pixel 7 pro, before update to dec patch, restoring november boot.img using fastboot flash boot boot.img, then update using system update direct from the phone. for dec boot.img grab from downloaded factory image from google. 14.0.0 (UQ1A.231205.015, Dec 2023) non verizon version. |
Nevermind just solve my problem using image 5.10.189-android13. The image from 5.10.177-android13 not working for me |
will try that later. thanks. |
Interesting, that worked for me on a Pixel 7 Pro, thanks! |
The security patch level must not less than the stock image's security patch level. |
Doesn't seem to work on pixel 7 (panther) , neither 5.10.177 nor 5.10.189 works |
Same (on Pixel7 panther). |
Please check before submitting an issue
Describe the bug
I have installed the December 2023 update for my phone, but can't get KernelSU working anymore. I have tried to patch the boot.img using magiskboot, Android-Image-Kitchen and Kernel Flasher (by installing Magisk first), but it always boots back into the bootloader and shows reason "boot failure". The kernel version has increased from 5.10.157 to 5.10.177.
To Reproduce
No response
Expected behavior
No response
Screenshots
No response
Logs
KernelSU_bugreport_2023-12-08_12_58.tar.gz
Device info
Additional context
No response
The text was updated successfully, but these errors were encountered: