[Kernel][10.06.2022][4.9.317][Android 12]Kirisakura_S 5.1.1 for Pixel 3/XL aka Bluecross

[Freak07]

I'm using Pixel Experience June patch. Even with a completely stock PE boot image (no magisk), flashing 5.1.1_S causes the bootloop immediately.

Unfortunately I don't know what can be the cause, but it seems something is not right when flashing on source built custom Roms.

The reports started when magisk 25 dropped though even with zips that previously worked. So it might not be the kernel, but rather down to magisk and/or something the custom roms changed.

 

[nldxda]

You are right, it was still in beta!

Actual stable magisk 25.1 has been released - did anyone try to update on latest krisakura?

Working for me with the stock ROM

 

[justDave]

I'm on blueline, 5.1.1_S, LineageOS 19.1 (June 14), Magisk 24.3. No issues to report.
I haven't tried updating Magisk yet.
Might be time to start a spreadsheet of what's working and not.
Would logs help?

 

[Ashwin Kale]

I'm using Pixel Experience June patch. Even with a completely stock PE boot image (no magisk), flashing 5.1.1_S causes the bootloop immediately.

You need to be rooted to flash kirisakura

 

[CRCinAU]

Also, boot into recovery and disable your Magisk modules. Check to see what is causing the bootloop - because it likely isn't the kernel or Magisk...

 

[justDave]

You need to be rooted to flash kirisakura

Are you sure? Can't you flash it from TWRP?

 

[mgp53]

Are you sure? Can't you flash it from TWRAL

Are you sure? Can't you flash it from TWRP?

Always, to flash a custom kernel!

 

[Ashwin Kale]

Are you sure? Can't you flash it from TWRP?

I flashed through twrp and caught myself in bootloop

 

[justDave]

I flashed through twrp and caught myself in bootloop

Interesting. And it did work ok when you were rooted first?

 

[Ashwin Kale]

Interesting. And it did work ok when you were rooted first?

I flashed using ex kernel manager and everything works grt

 

[justDave]

I flashed using ex kernel manager and everything works grt

I've had successful flashes both ways /shrug

I really should try the latest Magisk - I haven't bootlooped in a while ;-)

 

[Ashwin Kale]

I've had successful flashes both ways /shrug

I really should try the latest Magisk - I haven't bootlooped in a while ;-)

Try out 24.3 V as 25 is not stable yet

 

[justDave]

Try out 24.3 V as 25 is not stable yet

I'm already on 24.3. 25.1 is listed as the current stable

 

[Ashwin Kale]

I'm already on 24.3. 25.1 is listed as the current stable

Okay I'm still on 24.3 bcoz of unstable 25 v

 

[agraceful]

Okay I'm still on 24.3 bcoz of unstable 25 v

Have you gotten freak any logs? As far as boot looping, it started back with an alpha when John made a commit for legacy devices. Or it could possibly something similar to what those are experiencing on the p6pro.

 

[newkydawg]

Okay I'm still on 24.3 bcoz of unstable 25 v

Magisk 25.1 is stable. Stock ROM, Kiri 5.1.1 and Magisk 25.1 here and running great!

 

[justDave]

Magisk 25.1 is stable. Stock ROM, Kiri 5.1.1 and Magisk 25.1 here and running great!

LineageOS 19.1, Kiri 5.1.1 and Magisk 25.1 here and also running great!

 

[Ashwin Kale]

LineageOS 19.1, Kiri 5.1.1 and Magisk 25.1 here and also running great!

Ohh okay then I guess I will finally update magisk... Thanks

 

[dcarvil]

LineageOS 19.1, Kiri 5.1.1 and Magisk 25.1 here and also running great!

Do you have module "Magisk Bootloop Protector" version 1.8 installed? I ask because I went straight to bootloader mode when I updated Magisk to 25.1. I was on LineageOS 19.1 June update, and Kiri 5.1.1. The new version of Magisk Bootloop Protector repacks boot.img, so maybe there are just too many apps changing boot.img.

The only way I was able to recover was flash the stock LineageOS boot.img, remove the Magisk 25.1 apk, then reroot with Magisk 24.3.

 

[justDave]

Do you have module "Magisk Bootloop Protector" version 1.8 installed? I ask because I went straight to bootloader mode when I updated Magisk to 25.1. I was on LineageOS 19.1 June update, and Kiri 5.1.1. The new version of Magisk Bootloop Protector repacks boot.img, so maybe there are just too many apps changing boot.img.

The only way I was able to recover was flash the stock LineageOS boot.img, remove the Magisk 25.1 apk, then reroot with Magisk 24.3.

Nope. I don't use Magisk Bootloop Protector. (Sounds like the module description might be inaccurate.)