yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] DanielF50:
Thanks, I wasnt sure if it could be or not.

I have tried that a few times with no success, I even tried Android Flash Tool, but again no success.

I created a batch file to flash everything together between fastboot and fastbootd, and noticed that I'm getting the error "not enough space to resize partition" when flashing vendor, which leads me to think that super_empty isn't giving the partitions enough space, but I have been unable to remedy this at all as of yet, even after using fastboot to delete & reflash the partitions (including userdata).

Completely stumped on how this happened & how to fix it - Google's "recovery" website doesn't work for the Pixel 6 Pro yet, so that's no help, and there doesn't seem to be much info out there about automatic resizing of partitions on the Pixel A/B devices. Might just have to make do with one working partition until the website supports the 6/6 Pro.

edit: so, I can resize partitions with fastboot too obviously but have 0 idea of what they should be & apparently neither does the the install script. Anyone who can do a quick "fastboot getvar all" screenshot/printout for me would be much appreciated 😅
[Google Pixel 6 Pro] roirraW "edor" ehT:
Does

Official Google Android Flash Tool

help you? I know those with P6Ps have used it, but admittedly, I've never used it myself or the

Official Google Pixel Update and Software Repair

, if the latter is what you're referring to.
[Google Pixel 6 Pro] DanielF50:
Nope, first one just flashes one partition and leaves the other not working & the update/software repair doesn't support the P6P yet :/
[Google Pixel 6 Pro] ryandanger:
Receiving Flash Failed in EXKM, stating read-only file system, but I have Magisk Alpha installed with Riru and USNF. Root is working for EXKM. Pixel 6 Pro.

Tried manually flashing now and stuck in a boot-loop. Going to hopefully reflash stock images.

edit: stock images saved me, booting back up. any help? :)
[Google Pixel 6 Pro] Utini:
I am facing the same issue today again. Hard to say when it started since I updated to december android and also instantly flashed your kernel. But it is really annoying that the display suddenly doesn't turn off by itself :S
[Google Pixel 6 Pro] DanielF50:
Thanks dude! Oddly, everything is the same (except 128gb vs 256gb). Does booting to the opposite partition work for you?
[Google Pixel 6 Pro] Freak07:
Last advice I'm giving here. Don't switch slots manually. You're not really supposed to do that. It can cause all sorts of random issues. Especially if you don't know exactly what or why you're doing that.

The devices switch slots automatically on OTA. If you're flashing a factory image it won't switch slots as far as I'm aware. If you never did an OTA your original slot might not contain a firmware.

If you switch into a slot that has vbmeta enabled you're phone will stop booting. Lots of scenarios with no relation to the kernel.

Please move this discussiom out of this thread as it's going completely off topic, with no relation to the kernel and is derailing the topic confusing others.
[Google Pixel 6 Pro] Freak07:
It's not kernel related.

Edit: @Utini things like magisk mods of the system (systemui changes etc) , stuff that changes accessibility Services, app that provide additional functionality there etc might cause issues.

I checked again works fine on my end and I don't know how the kernel could prevent this.

You can always try to gather a logcat and a dmesg the moment the display is not turning off. It might provide you a clue.
[Google Pixel 6 Pro] Freak07:
Make sure you're exactly following the instructions as provided.

Make sure you're flashing images extracted from the correct zip to your device and not pixel 6 files on the pro or vice versa.
[Google Pixel 6 Pro] foobar66:
Don't know ... haven't tried ... and I don't want to try now ... don't want to risk bricking my device during the end of year holidays ;-)
[Google Pixel 6 Pro] DanielF50:
Thanks for the info - I've been switching/flashing slots every few months often for years and have never ran into issues, so just thought it was odd. Either way, sorry for going off topic - I only continued to reply here as originally thought it was kernel related & then for continuity purposes 👍

Hope you're enjoying the holidays 😊

edit:

I've noticed the same issue with the stock kernel, seems like a bug in the Dec update.
[Google Pixel 6 Pro] nguyenson91hp:
Are you guys able to change CPU frequency in FKM? I could change it but it does not stick.
[Google Pixel 6 Pro] Texan1:
So... getting back on track... what goodies are you looking to cook up for us next @Freak07 ?!

Is there anything from your previous kernels you would like to use/tweak in this kernel?

Do you see the possibility for continual improvement with this kernel?

Are some kernels better than others in what can be done with them or is it purely down to the skills of the kernel developer as to what is possible?

Cheers!
[Google Pixel 6 Pro] Lughnasadh:
As @Freak07 said, doesn't appear to be a kernel issue, but rather more likely an Android 12 December update bug.

Google Pixel screen timeout (attention) not working after December update

Some Google Pixel users are complaining that the screen timeout (attention) is not working on their smartphones after December update.

piunikaweb.com
[Google Pixel 6 Pro] manueltimz:
The issue still persists even after a reboot
[Google Pixel 6 Pro] john-aurelio:
o I flashed with exkm and gave me the loop and then flash with FKM and it worked for me FKM and it worked for me
[Google Pixel 6 Pro] lattosimbaste:
Sort of an odd use case but the ability to display only the red pixels on OLED displays is useful to preserve eyesight dark adaptation at night. Very handy for astronomy!

TIA for considering.
[Google Pixel 6 Pro] Freak07:
Not so odd at all. But it's already very easily doable with cf lumen and more customizable than "kcal". (y)
[Google Pixel 6 Pro] lattosimbaste:
Ah, thanks! I better get to rooting then.
[Google Pixel 6 Pro] jjblaster3:
thanks for the kernel! happy to report better than stock battery life for the past 2 days (straight after a factory reset due to unlocking bootloader). Can't wait to see how much improvement I get after the adaptive **** kicks in, since I was already enjoying my battery life on stock (granted I don't use 5G and barely use mobile data)
[Google Pixel 6 Pro] Freak07:
Yeah, that's the "downside" for having a lot of flexibility.

I stopped caring about passing safetynet when rooting somewhere a year or so ago when google started enforcing HW attestation, as most solutions relied on Xposed in some form.

But with zygisk/deny list and the universal safety net fix module I'm pretty happy right now. I even started to use gpay again. But we all know google can flip the next switch at any point.

Usually on other phones where I had a need for it I have setup cf lumen, so it's in sundown mode when ambient light is dim at the evening indoors, and have it fall back to sleep mode, if the room is totally dark, making the display even dimmer and more orangeish/redder then. Kcal doesn't allow for that kind of flexibility.

Glad to hear you're happy with it. I'm also very satisfied with how the kernel runs. Especially after the scheduler changes which are tied into the powerhalnow.

But I'm also very happy I took the risk and pre-ordered the P6 pro, despite being skeptical of Tensor and a few other things. :)
[Google Pixel 6 Pro] Freak07:
I wish those who celebrate it Merry Christmas!🎄⛄✨

I hope everybody has a nice time and is enjoying the holidays with their beloved ones.
[Google Pixel 6 Pro] Nekromantik:
Merry Xmas!
[Google Pixel 6 Pro] State.of.mind:
To confirm, it's now okay to flash the kernel via a kernel manager even on the December update?
[Google Pixel 6 Pro] Lughnasadh:
Yes, as long as you are on the latest Canary Magisk (23016)
[Google Pixel 6 Pro] State.of.mind:
Excellent. Thanks
[Google Pixel 6 Pro] shag_on_e:
Xmas is nothing! Merry Christmas!
[Google Pixel 6 Pro] Jerreth:
new to the pixel 6 pro but not flashing, i am having issues getting this kernel to boot i must be over looking a detail here, i have unlocked and rooted, i downloaded and flashed via exkm no luck just boot loop then i tried with fkm no luck same problem each time having to manually flash the boot and vendor images any ideas? what am i missing?
[Google Pixel 6 Pro] Mrcactuseater:
Did you disable Verity and vbmeta?
[Google Pixel 6 Pro] Jerreth:
no i did not but i did not see that it was a requirement for the kernel installation.
[Google Pixel 6 Pro] V0latyle:
I just wanted to pop in and say I got a good laugh from the kernel name. Well done!
[Google Pixel 6 Pro] roirraW "edor" ehT:
It depends on if the kernel has had the same fixes that were implemented in Magisk Canary build 23016. If not, then they still need disabled (which will require wiping your phone, at least if you've never disabled them before). If the kernel has had those fixes implemented, then you don't need to disable them as of that 23016 build of Magisk Canary (whether you're using Magisk and actually rooted or not).

I don't know if this kernel has that fix implemented or not.
[Google Pixel 6 Pro] Freak07:
It has nothing to do with the kernel itself. The anykernel.zip uses magiskboot to "repack" the kernel during the flashing kernel.

The magiskboot binary was updated to 23016, the magisk canary you mentioned, in the latest kernel update so the requirement for that was removed. (y)

The instructions provided in the OP should work fine if followed correctly. :)

The only thing that comes to my mind: are you on December firmware?

Otherwise flashing should just work fine if rooted with the latest official magisk canary 23016.
[Google Pixel 6 Pro] foobar66:
I flashed on December firmware without problem using EX.
[Google Pixel 6 Pro] Jerreth:
no i am on the November update fully rooted but get boot loop after flashing kernel.
[Google Pixel 6 Pro] Freak07:
Then you now know the reason. Kernel with Dec source can't boot on Nov firmware and vice versa.
[Google Pixel 6 Pro] :
Delete
[Google Pixel 6 Pro] Jerreth:
oh i understand thank you your kernel is dec source gotcha ok ill wait for the late jan update i suppose.
[Google Pixel 6 Pro] Freak07:
You can just flash 1.3.0 release on Nov firmware.

Manually patch boot.img via magisk, make sure you're using canary 23016 and flash the patched boot.img and the other provided images for 1.3.0 manually via fastboot.

You'll find instructions for flashing 1.3.0 release and older hidden behind a spoiler tag towards the end of the OP.

You'll find them in the download link provided in the OP.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ah, thank you for the details!
[Google Pixel 6 Pro] Jerreth:
ill do that thank you very much. correct me if im wrong but with android 10 and 11 i thought i could flash the kernel that works with 10 or 11 respectivly but any version of it and be pretty safe did something change in android 12?
[Google Pixel 6 Pro] Freak07:
There's no rule for this generally. On pixel 4 xl atm the android 12 kernel still works on Android 11.

But each month or update a kernel change can theoretically make the kernel unbootable on the previous firmware. It just depends on the nature of the change.

But as a rule of thumb it's always best to run exactly the firmware the kernel was built for.
[Google Pixel 6 Pro] Jerreth:
Well thank you very much! I really appreciate your envolvment and your willingness to answer silly questions for people again and again. :) love your work
[Google Pixel 6 Pro] jlokos:
@Freak07, I read the OP and the thread. I wasn't able to find a definitive answer: If you are on another custom kernel, can you just flash this kernel in fkm, or do you have to flash back to stock first? I used your kernel on my 3XL and it was always excellent. Thanks for the support of our device.
[Google Pixel 6 Pro] Freak07:
It's best to restore stock kernel, by flashing the four images as mentioned in the FAQ in the second post if you want to avoid any potential issues. I'd do this personally.

But I think if I'm not mistaken the zip should overwrite everything from the other available kernels right now.
[Google Pixel 6 Pro] Artemka2008:
Hi, I'm currently on SD1A.210817.036. What kernel version is compatible with this build version?
[Google Pixel 6 Pro] Texan1:
I've forgotten if I'm meant to be running both modules (AK3 and Powerhint) with latest Kirisakura?! (rooted, Dec build)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hello! The most recent one at the Download link that has the same month as in your update screen as below. Note, in my example, it's December's most recent release, but yours is not. Hopefully now you can tell on your own. If still have questions, don't hesitate to ask. Cheers.
[Google Pixel 6 Pro] Lughnasadh:
In the last changelog for 1.4 he stated:

"Alongside the kernel.zip a magisk module called AK3 Helper Module will be flashed. It will show up in magisk manager after the reboot following the flash of the kernel.zip. Do not delete this module, it ships a modified powerhal, which is an integral part to the changes in this release.

The powerhal will also restrict CPU-Freqs when the screen is off to save battery during e.g. music/podcast playback.l

If you used the old powerhint module, please remove that before flashing the kernel.zip."
[Google Pixel 6 Pro] Texan1:
Many thanks for that. I'd gone back to check instructions and post #4 mentioned flashing the powerhint module still. I'm sure Freak will edit that out if no longer needed :)
[Google Pixel 6 Pro] Artemka2008:
I installed the last available factory image(SD1A.210817.037). Then I tried to install kirisakura 1.3.0, but got a bootloop.

What I did:

- download files from 1.3.0 folder(boot.img, dtbo.img, vendor_dlkm.img)

- create patched boot.img via the latest Magisk

- flash vendor_dlkm.img via fastboot

- flash patched boot.img and dtbo.img via bootloader

Any help will be appreciated.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Specifically what latest Magisk? Latest Magisk Stable or Magisk Canary? Canary (latest at the time being 23016) is what you want.
[Google Pixel 6 Pro] Artemka2008:
Canary 23016
[Google Pixel 6 Pro] Texan1:
Did you follow these steps *exactly*...

https://xdaforums.com/t/kernel-16-1...pixel-6-pro-aka-raviole.4358435/post-85905455
[Google Pixel 6 Pro] Artemka2008:
Of course I did.

Do I need to flash vbmeta.img and disable dm verity?
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://xdaforums.com/t/kernel-16-1...pixel-6-pro-aka-raviole.4358435/post-86209325
[Google Pixel 6 Pro] Texan1:
Sounds like you have it all under control then... :rolleyes:
[Google Pixel 6 Pro] Lughnasadh:
Sounds like this is the correct answer, since he's on November.
[Google Pixel 6 Pro] Artemka2008:
So, what I should to do guys? I'm on November build
[Google Pixel 6 Pro] Golf c:
Patch the stock boot image with magisk and boot up. Flash the zip in a kernel manager. Exkm or fkm
[Google Pixel 6 Pro] roirraW "edor" ehT:
Actually, since you're on the November build and therefore flashing v1.3.0 of this kernel, then yes, you need verity and verification disabled first. Apologies that I didn't pay full attention to the situation.

If you haven't already disabled verity and verification, you will need a full factory reset after disabling them.

Your mileage may vary, but the only way you have now to keep from having to factory reset would be to manually update to the December full firmware zip, then you can use the December version of this kernel that doesn't need Verity and Verification disabled.
[Google Pixel 6 Pro] Artemka2008:
Thanks a lot. I'll try to install December update
[Google Pixel 6 Pro] Lughnasadh:
If memory serves, there wasn't a zip for the November build. But then again, I'm not an elephant 🙃🐘
[Google Pixel 6 Pro] Golf c:
You could be right. Good catch.Then he's screwed. He has to disable vbmeta or update to December
[Google Pixel 6 Pro] Freak07:
instructions in post #4 is if you decide to flash all four images from 1.4.0 manually, because for whatever reason exkm or fkm is not available to be used for flashing the kernel.zip.

That´s why the powerhal module needs to be flashed there separately as it´s otherwise just a part of the 1.4.0.zip.

I thought it was made clear in the OP, that post #4 is not suitable if you flash the kernel.zip, but I emphasized that in post #4 now too.

If you followed the instructions for 1.3.0 and older I don´t see why that would not work for you if you´re on november firmware.

Maybe a bad download, maybe platform tools are outdated. I don´t know.
[Google Pixel 6 Pro] edmondt:
I am on raven-sd1a.210817.036.a8-factory-7352ca24, I flashed the downloaded Kirisakura_Raven-1.4.0.zip but ended up not booting / boot loop.

I have the patched boot from magisk that has been working, right now I cannot get into fastboot reboot fastboot with the kernel flashed, tried manual flashing too, both not working.

Got fastboot reboot fastboot back by running the flash-all.bat in the factory raven-sd1a.210817.036.a8-factory-7352ca24.zip

...but stuck on the Google logo. On start, it says device currupted.... Any help would be apperciated :)

Can someone confirm that it works on their Verizon Pixel 6 Pro?
[Google Pixel 6 Pro] Lughnasadh:
1. You flashed the December kernel while being on the November build.

https://xdaforums.com/t/kernel-16-1...pro-aka-raviole.4358435/page-26#post-86209489

2. About the corrupted message, you'll likely have to use Android Flash Tool . See this thread
[Google Pixel 6 Pro] CrashTestDroid:
How did you unlock the bootloader on your Verizon 6Pro?
[Google Pixel 6 Pro] Artemka2008:
Thanks everyone for help. I flashed December build and all works fine right now
[Google Pixel 6 Pro] edmondt:
I think I bricked it... tried different firmware, flash in Ubuntu, Windows... Now I have a black screen that won't turn on' plugging into it under windows detacts the device with the chime sound. But overall, just black screen all the way.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Try pressing and holding the power button for more than 30 seconds? (that's how long it takes to force off now)
[Google Pixel 6 Pro] edmondt:
Thanks... I tried it, not working...
[Google Pixel 6 Pro] danw_oz:
Same here, flashed kernal via EXKM and phone boot looped, dirty flashed factory and all good. Not sure what the proper proceedure is as the info now seems to be on different pages, also not sure now which kernel suits which release(s) could not find any specific details in the op or release thread(s) which roms are supported, and google has now fully dropped all the December patches from the website for Pixel 6 and Pro
[Google Pixel 6 Pro] roirraW "edor" ehT:
Let it sit for a while and then try fooling with the phone again.
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://xdaforums.com/t/kernel-16-1...pixel-6-pro-aka-raviole.4358435/post-86213007
[Google Pixel 6 Pro] danw_oz:
delete
[Google Pixel 6 Pro] danw_oz:
Yeah on page 27, didn't exist when I was trying to do this. I have asked for clarification on this in the OP and release page to make it clear, since a lot of people are on november, and now december have been completely removed from google.

OK found a post on page 26 from yesterday version you need to use for November Build is 1.3.0.

Nevermind, I am not going to use this until Jan build
[Google Pixel 6 Pro] edmondt:
Update: Went to an authorized tech about my bricked Pixel 6 Pro, the tech plugged it in to the USB reader and it did not even register any current charging. They said the motherboard needs to be replaced....

This is my first time in 10 years LOL... Oh well... becareful flashing I guess....
[Google Pixel 6 Pro] danw_oz:
Others here have mentioned before google don't seem to care about unlocked phones voiding warranty, replace no problems no questions. And to be honest if you get to the point you can't flash or do anything, then 99% of the time neither can they tell what state it was in prior. Happened twice for me one other brand phones and swapped straight out
[Google Pixel 6 Pro] Freak07:
fastboot reboot fastboot is broken if you flashed 1.4.0 on november build as fastbootd (the mode you get into via fastboot reboot fastboot) "depends" on vendor_boot.img.

To get back to stock kernel it would have sufficed to flash the 4 images mentioned in the second post, "how to restore stock kernel".

First flash boot, dtbo and vendor_boot in bootloader, then vendor_dlkm in fastbootd.

But you essentially did the same by flashing the whole factory image.

I guess you disabled vbmeta flags earlier during rooting, that´s why you ran into the device is corrupted message as stock vbmeta was flashed during flashing the factory image.

To get back out of this you need to wipe the device.

Doesn´t sound like your device is bricked or takes no charge from the post from yesterday I quoted above, but I also don´t know what happened in between the two posts.

It´s very rare but can happen that a motherboard stops working randomly.

As another user mentioned above I´m also curious as how a verizon device was unlocked, as verizon pixels are not bootloader unlockable.

Sorry your device is dead. But it´s not due to flashing the kernel provided here.

As you mentioned google is in a kind of funky state right now with the pixel 6 devices. I´ll put a warning to the instructions in the OP to not flash Dec kernel on Nov firmware for now. I didn´t know google removed the december firmware images. As far as I was aware they just stopped roll-out.

I´ll also edited and re-uploaded the 1.4.0.zips so they can´t be flashed on november firmware and will abort there now.
[Google Pixel 6 Pro] Texan1:
Do you envision a new kernel update soon @Freak07 or are you waiting for the January update? Cheers.
[Google Pixel 6 Pro] Freak07:
I´m waiting for the January update :)
[Google Pixel 6 Pro] lattosimbaste:
Curious if there might be any issue with flashing the November radio only on a December 211205.017 build with the 1.4.0 kernel. Other than dropped calls everything is working well so maybe it's better to wait a few weeks.
[Google Pixel 6 Pro] Freak07:
Shouldn't make any difference flashing the nov radio on the December firmware with stock kernel or 1.4.0. Generally I wouldn't recommend to run frankenstein firmware configuration, but December update being screwed up for some users seems to be an exception to that rule.

Luckily I'm one of those that seem to be unaffected from the December issues so I didn't need to flash Nov radio and Dec firmware which means I can't give you first hand experience.
[Google Pixel 6 Pro] Zach Alt:
Been a long while since I have flashed a kernel. If I flash this will I have to do any extra steps when the January update drops?
[Google Pixel 6 Pro] NippleSauce:
I did exactly this, haha. The December image made my service horrible (I'm in the NE of the US on T-Mo). As @Freak07 mentioned, it doesn't affect the phone's software and should allow you to get better service, as that's what it did for me =).

Take care all! Enjoy the weekend!

**Edit** - It worked with this kernel and Despair kernel. I should've specified which kernels I flashed after being on the December factory image and the November radio image 😅
[Google Pixel 6 Pro] roirraW "edor" ehT:
You'll have to wait for the kernel to get updated, since the old one will be overwritten by the January full stock image, and then when the kernel gets updated you can flash it from scratch again.

I would just wait until the kernel gets updated, and then when it is, only then flash the January full firmware zip (with "-w " removed) and then after booting to ensure it works as is, follow the directions in the OP again to flash the new kernel.

Sometimes you get lucky and an old kernel works on a new update but it's hit and miss, just depends on the changes. November's doesn't work on the December update.
[Google Pixel 6 Pro] lattosimbaste:
Thanks for the reassurance guys, no problems reverting to the November radio and so far the fluctuating reception seems to be better but it's early on. Back to the kernel- working really well for me, no issues with stability, performance or battery. And the recommendation for CF Lumen really put me in a good place.

Thanks again!