Development [Kernel][12.08.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.1.4 for Pixel 7/Pro aka "Pantah"

[reg66]

Bit of an odd one here, well it is for me...



I unlocked bl this morning, flashed EvoX rom, followed by magisk alpha, then kiri kernel. All went fine, and seems fine still. However, this is my 1st pixel and I just assumed that I could flash kiri in the normal way with fkm, apart from requiring a magisk module alongside it. But after reading through faq's for the kernel I see I should have disabled verity and verification at the time of flashing...

The odd part comes here; using the avbctl module it tells me both are disabled already (note: I haven't manually disabled anything myself or used pixel flasher/android tools etc for it to happen). See screenshot. So, my query is, do I still need to start a fresh, wipe everything and disable both at the start OR am I good to go and the terminal output is correct?

Also, if I am definitely disabled on both, any info on how this can be without my doing would be greatly appreciated!

I have only;
Unlocked bl
Flashed vendor_boot.img
Wiped
Sideloaded rom and magisk alpha
Booted
Got up n running with all apps etc etc then flashed powerhint and kiri.

No idea how verity and verification are automatically disabled

 

[ffuser1]

Bit of an odd one here, well it is for me...



I unlocked bl this morning, flashed EvoX rom, followed by magisk alpha, then kiri kernel. All went fine, and seems fine still. However, this is my 1st pixel and I just assumed that I could flash kiri in the normal way with fkm, apart from requiring a magisk module alongside it. But after reading through faq's for the kernel I see I should have disabled verity and verification at the time of flashing...

The odd part comes here; using the avbctl module it tells me both are disabled already (note: I haven't manually disabled anything myself or used pixel flasher/android tools etc for it to happen). See screenshot. So, my query is, do I still need to start a fresh, wipe everything and disable both at the start OR am I good to go and the terminal output is correct?

Also, if I am definitely disabled on both, any info on how this can be without my doing would be greatly appreciated!

I have only;
Unlocked bl
Flashed vendor_boot.img
Wiped
Sideloaded rom and magisk alpha
Booted
Got up n running with all apps etc etc then flashed powerhint and kiri.

No idea how verity and verification are automatically disabled

It's possible the rom disabled them. Custom roms are not supported so you're probably on your own. You should be able to flash stock kernel if you run into trouble, unless your rom has its own custom kernel.

 

[LimitsX]

@Freak07 , can I flash this kernel on Pixel 7a phone?

 

[Freak07]

Bit of an odd one here, well it is for me...



I unlocked bl this morning, flashed EvoX rom, followed by magisk alpha, then kiri kernel. All went fine, and seems fine still. However, this is my 1st pixel and I just assumed that I could flash kiri in the normal way with fkm, apart from requiring a magisk module alongside it. But after reading through faq's for the kernel I see I should have disabled verity and verification at the time of flashing...

At least you read at one point through the requirements and instructions, although too late

The odd part comes here; using the avbctl module it tells me both are disabled already (note: I haven't manually disabled anything myself or used pixel flasher/android tools etc for it to happen). See screenshot. So, my query is, do I still need to start a fresh, wipe everything and disable both at the start OR am I good to go and the terminal output is correct?

Also, if I am definitely disabled on both, any info on how this can be without my doing would be greatly appreciated!

I have only;
Unlocked bl
Flashed vendor_boot.img
Wiped
Sideloaded rom and magisk alpha
Booted
Got up n running with all apps etc etc then flashed powerhint and kiri.

No idea how verity and verification are automatically disabled

It's possible the rom disabled them. Custom roms are not supported so you're probably on your own. You should be able to flash stock kernel if you run into trouble, unless your rom has its own custom kernel.

Like @ffuser1 said custom roms are not really supported and that's one of the reasons. I can't control what each custom ROM does and there's no way for me to track.

It seems to me the custom ROM might either disable avb protection or it's broken.
If it would be enabled, you would not be able to boot. So you should be fine for the moment.

If flashing the next update for the custom ROM triggers avb to be enabled again you might run into a problem. So I'd probably pass the flags to disable verity/verification.

If you want to restore your ROM to stock condition, you need to flash the images, that flashing the kernel changes, specified in the FAQ.
Since most custom roms ship a payload.bin you might need to extract (plenty of tools on XDA for that) those images if you haven't backed them up before.

Now I went a bit off-topic myself, but I think this will point you in a good direction

 

[reg66]

Thanks a lot for your responses guys. I normally read up tons and then read again before flashing anything. I just assumed in haste flashing the kernel would be the same as before... That'll teach me! I guess I got lucky. Will for sure take it on board and read up more again before I bork a device. Guess I got lazy, for once! Cheers again, and for the great work @Freak07

 

[xxqxpxx]

Would this fix the overheating problem?

 

[ffuser1]

Would this fix the overheating problem?

you need to give a lot more detail as to what you're talking about. overheating is likely related to your own personal use and background app activities. or give any details for troubleshooting

 

[xxqxpxx]

you need to give a lot more detail as to what you're talking about. overheating is likely related to your own personal use and background app activities. or give any details for troubleshooting

well, currently I'm on the stock Android latest build. what I find during my usage especially when video calls or something the device would get pretty hot. my question is if this kernel would perform better in terms of heat management compared to stock

 

[lesafijndt]

well, currently I'm on the stock Android latest build. what I find during my usage especially when video calls or something the device would get pretty hot. my question is if this kernel would perform better in terms of heat management compared to stock

Yeah, it will, mine was getting warm in normal tasks too, but this kernel fixed it and it's not getting hot at all, however battery life seems to be worse for me.

 

[djcsurf]

I get a weird random issue which I have no idea how to try and log. What seems like purely random but maybe only once a week the phone will sort of freeze where I can't unlock it. The screen will come on when I touch it but it's not responsive as in I can't use the fp reader or swipe up to prompt the pattern. If I push power button the power menu comes up but same thing, pressing restart does nothing. Only thing I can do is wait, then after 30-60 seconds it's ok again. It was happening on April and now May updates using this kernel. That aside it runs perfectly fine.

 

[TotallyAnxious]

I get a weird random issue which I have no idea how to try and log. What seems like purely random but maybe only once a week the phone will sort of freeze where I can't unlock it. The screen will come on when I touch it but it's not responsive as in I can't use the fp reader or swipe up to prompt the pattern. If I push power button the power menu comes up but same thing, pressing restart does nothing. Only thing I can do is wait, then after 30-60 seconds it's ok again. It was happening on April and now May updates using this kernel. That aside it runs perfectly fine.

Get a log after the 30-60 seconds.

 

[djcsurf]

Get a log after the 30-60 seconds.

I used logcat app many years ago, in this case would adb be best and what would be correct command?

 

[TotallyAnxious]

I used logcat app many years ago, in this case would adb be best and what would be correct command?

Use kernel flasher and do a logcat. More modern app and the preferred app for flashing kernel, if you're not already using.

Edit: I should have said dmesg, not logcat.

 

[djcsurf]

Use kernel flasher and do a logcat. More modern app and the preferred app for flashing kernel, if you're not already using.

Edit: I should have said dmesg, not logcat.

Yeah, I use kernel flasher anyway, will grab a dmesg next time which will hopefully be of use.

 

[Freak07]

I get a weird random issue which I have no idea how to try and log. What seems like purely random but maybe only once a week the phone will sort of freeze where I can't unlock it. The screen will come on when I touch it but it's not responsive as in I can't use the fp reader or swipe up to prompt the pattern. If I push power button the power menu comes up but same thing, pressing restart does nothing. Only thing I can do is wait, then after 30-60 seconds it's ok again. It was happening on April and now May updates using this kernel. That aside it runs perfectly fine.

Like @TotallyAnxious said please get me logs after the issue happened.

In that case preferably both, a logcat and a dmesg you can take both via kernel flasher app

 

[mohammed510]

Stupid question but will this kernel work on the pixel 7a?
Asking for a friend.

I guess not but it would be really nice if the dev could support the 7a as well @Freak07

 

[Annie the Eagle]

Installed this on my new Pixel 7 Pro (stock rooted ROM) on May 2023 Firmware.

Used Pixel Flasher to update to May 2023 with dm-verity and verification disabled.

Used EXKM to flash this kernel.

No issues during installation and no kernel issues yet to report

 

[Bxperiaz3]

Just a quick one before I flash, if I make a back up in kernel flasher can I use this to get back to stock or do I need to flash factory img with the laptop?

Also when I do my monthly update I usually disable all magisk modules and then reboot, flash new factory image with pixel flasher and then re root from magisk afterwards .Will this process make my phone crash/brick if I have a custom kernel installed? Looking forward to trying this out on my p7p!

 

[TotallyAnxious]

Just a quick one before I flash, if I make a back up in kernel flasher can I use this to get back to stock or do I need to flash factory img with the laptop?

Also when I do my monthly update I usually disable all magisk modules and then reboot, flash new factory image with pixel flasher and then re root from magisk afterwards .Will this process make my phone crash/brick if I have a custom kernel installed? Looking forward to trying this out on my p7p!

The FAQ answers the first question. But you need more than just one img file backed up to restore to stock. These are also available in factory image zip.

And no, nothing will crash.

 

[Bxperiaz3]

The FAQ answers the first question. But you need more than just one than one img file backed up to restore to stock. These are also available in factory image zip.

And no, nothing will crash.

Great, Thank you!