[Google Pixel 6 Pro] Freak07:
F.A.Q:

Question: How do I update my phone to a new monthly update if this kernel is installed?

Answer: The easiest solution is to just use any full firmware package to update your phone to the new stock firmware. You can do so with the android web flash tool, a factory image or a full OTA image.

An excellent guide on how to use the factory image to do so was posted by @roirraW "edor" ehT on this thread. Feel free to use this as a reference.

This also serves as the easiest way to return back to stock, if you don´t like the kernel and feel not comfortable flashing anything via fastboot.

Question: How do I return back to stock?

Answer: Extract boot.img, dtbo.img, vendor_boot.img, vbmeta.img and vendor_dlkm.img from the matching factory image provided on googles download page.

If you disabled verity/verification previously there´s no need to flash the vbmeta.img when restoring.

If you want to stay rooted make sure to flash a boot.img that has been patched with magisk.

Flash those images via fastboot/fastbootd and you will be back on stock kernel. If you don't know the fastboot commands to flash the images, check the instructions how to flash those images in post #4.

Alternatively dirty flash the whole firmware without wiping by using either the android web flash tool, a factory image or a full OTA image. If you disabled the vbmeta flags, don't forget to disable them again (or tick the correct options on the web flash tool) after flashing a full firmware package and re-root.

Question: How to report bugs properly?

Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.

Before reporting any bug make sure you´re running on a supported firmware. Usually I'm announcing in the release post, the firmware the kernel.zip is compatible with, but most of the time the kernel is updated when a firmware update drops.

Please make also sure you're running a stock configuration.

That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.

Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.

Is the issue reproducible? Does it happen frequently?

Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. (kernel flashing apps usually support exporting logs of flashes too) If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself, reports might just be ignored. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.

Question: What about unlocking, rooting, passing safetynet, apps detecting root/modifications and other topics that are vaguely related, but not really subject of this thread?

Answer: If you want to modify your phone via root/magisk in any way you need to unlock the bootloader. Unlocking will result in safetynet not passing. This has nothing to do with the kernel. At the moment of writing this, safetynet not passing can be worked around with a magisk module called "Universal SafetyNet Fix".

Not passing safetynet is unrelated to the kernel since hardware attestation is enforced on nearly all newly released devices now.

If you´re not passing safetynet banking apps might for example be detecting root. There are various tricks to hide root/modifications to the phone from banking apps or others but that´s not really subject of this thread.

I recommend taking a look at this excellent collection of helpful threads from @roirraW "edor" ehT!

It can be found following this link!

Question: I get a device corrupted message after flashing the kernel or just reboot to bootloader. How to get rid of it?

Answer:

There seems to be an issue with verity on Pixel devices that can trigger randomly. That means even if the expected hashes match the device refuses to boot due to this bug.

A workaround for A12 has been shared in the following post linked here. It seems this issue happens randomly on devices without the vbmeta flags for verity/verification disabled.

Essentially flashing/booting (booting should be enough) a boot.img from an older firmware, letting it attempt to boot but fail, and then restore boot.img from the matching firmware clears the message.

If you´re doing this while having the kernel installed don´t forget to flash back to stock completely, which is also described in the FAQ.

There seem to be cases on A13, where this verity bug is still triggered during some flashes, essentially booting straight back to bootloader. It seems all cases reported here were solved by reflashing the firmware via the web flash tool from google, without wiping data. Interestingly flashing back an older boot.img was not needed there.