yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] russian392:
I have been out of the rooting/flashing loop for some time now (since my nexus 6 as I felt no need to root my 6p and onwards).

I just want to confirm a somethings that I couldn't find online (and if I did were simply speculation by people who have no idea what they are talking about).

Can I flash this kernel boot.img without magisk patching it, or rooting in general? I like the changes it implements under the hood but don't need root.

Anything else I need to flash after the boot.img (like vendor, modems, etc)?

Or is it impossible to run the kernel without patching/flashing magisk bs?

Thanks.
[Google Pixel 6 Pro] Freak07:
Magisk root and the functionality magisk provides to systemlessly replace files during bootup is crucial for this kernel to work.

Being rooted with magisk is mandatory as it's not possible otherwise to modify the phone in any way on the last few gens of devices. (dynamic partitions etc)

If you decide to root via magisk at one point in the future and don't want to use any kernel manager apps like exkm or fkm to flash the kernel.zip, you'll find the instructions for manually installing this kernel in post #4, otherwise how to flash kernel.zip is described in the OP as well as the requirements.
[Google Pixel 6 Pro] Nightf0x_007:
Whenever i flash the kernel using exkm my device bootloops (pixel 6 here), i know i need to format my device (something related to dm-verity) and start from scratch but its a major headache, my question is if i flashed the kernel manually using the images will it also likely bootloops or it might work ? Cuz if there is a chance it will work i will give it a try otherwise save the time
[Google Pixel 6 Pro] Freak07:
I never ran into any of those issues so unfortunately I can't answer your question.

Make sure you're using magisk stable (24300) and you shouldn't run into a bootloop. If you do run into issues, something is wrong, but that's not related to the kernel and unfortunately I don't know what.

If flashing the zip on magisk 24300 doesn't work, i think manually installing shouldn't make a difference either.

There's an issue opened on magisk GitHub regarding canary magisk and some unfortunate users running into issues. It seems to be actively being investigated, so fingers crossed a fix can be found there. Maybe that related to your issue too.
[Google Pixel 6 Pro] Freak07:
May update is out. :)

no source update pushed from google yet. I guess it´ll happen in a few hours when I´ll be asleep.

I went ahead and flashed the latest release for stable 12.1.0 without any issues so far.

If you can´t wait, it should be fine to flash based on that short experience.

If you want to be absolutely sure there will be no issues due to incompatible source/firmware, I´ll try to update the kernel with any new potential changes in the source for May as soon as I find time, which will hopefully/probably be tomorrow if everything goes as expected. :)

I wish everybody a great day/evening.
[Google Pixel 6 Pro] scloutkst:
@Freak07 hopefully this dmesg will still be useful to you.

dmesg.txt

drive.google.com
[Google Pixel 6 Pro] Freak07:
This one is mine too :)
[Google Pixel 6 Pro] bush911:
Thanks for the outstanding work! I am the 2nd to download, will keep posted after using for a while.
[Google Pixel 6 Pro] scott.hart.bti:
The speed at which you get your updates out blows my mind. You sir, are a machine! Thanks for the quick update!

Any chance you're going to revisit the DAMON and DAMON-Reclaim features? Sounds interesting and was looking forward to playing around with it a bit.
[Google Pixel 6 Pro] swieder711:
Some folks are saying that Magisk 24306 is needed to root the May update. I see that Freak is using it too.

However, the release notes for 2.4 say "Make sure you´re being rooted with magisk 24300 stable before flashing the kernel if you´re unsure"

I am not sure which Magisk to use for the May update. Any more color to add?

thanks,
[Google Pixel 6 Pro] bleez99:
I'm on 24.3 stable, works fine. Listen to the OP.
[Google Pixel 6 Pro] russian392:
So I went from 13 beta 1 to 12.1 may update today, factory reset.

Skipped setting up my phone, installed magisk latest, patched the factory boot.img, flashed it, rebooted, installed the power zip thingy as a module through magisk, rebooted, then patched the kernel, downloaded the files and followed the manual install. After everything went through and I double checked my work, when rebooting the phone told me that the system won't boot and I need to do a factory reset. So I did, I assume this wiped the magisk module because although the phone reached the google loading screen with the sliding bar, it would never boot up. Trying a redo this time with --slot=all this time around. Not sure what is up, but if refuses to boot repeatedly even following the instructions, something is up.

EDIT: using --slot=all on either dtbo or vendor_boot breaks fastboot period and won't boot into fastbootd.

EDIT2: flashed stock dtbo and vendor boot, fastbootd worked, reflashed the custom dtbo and vendoor boot to slot b (that is what it defaulted to) and fastboot d is broken, again. What the actual F.

EDIT3: do people just not know how to write instructions these days? being vague and hoping people "just know" what to do is kind of stupid.

EDIT4: Flashed stock dtbo, patched stock boot, and stock vendor boot, phone boots.

EDIT5: Flashed without any modifications (fastboot flash xyz xyz.img) the kernel, dtbo, vendoor boot, and dlkm in d mode. Still pretty much useless. Loads recovery and says data may be corrupt try again/factory reset.

So in otherwords, 2 attempts, same problem using different methods. Looks like modern flashing has become such a sh*tshow that this is why no one roots anymore. Literally reflashed to full stock TWICE and redid the instructions TWICE and once using plain old logic, still bunk.

Flashing back to stock YET patched bootimg and stock vendor files boots fine...

So the problem is either A) magisk (which I made sure to not use the version listed, I have actually tried 1 version lower the first time), B) the power zip thingy...or C) the instructions.

EDIT6: After flashing back stock files, magisk still sees the power zip module no problem. I reinstalled it just incase.

EDIT7: Downloaded the latest magisk canary, we will see because 23000 only boots the stock kernel but not kiri.

EDIT8: Nope, latest magisk didn't work either, auto boots into bootloader mode.

EDIT9: I said screw it and got EXKM (I bought it long ago, thank goodness) and it won't work thorugh that either. Bootloops.

This release is botched if you are coming from stock and weren't running this before. What a freaking joke.

I kid you not I have been at this for 3 and a half hours and its all BS lmfao.

EDIT10: trying one more thing, installed the feb bootimg and letting it essentially try to boot after kiri bootloops with the exkm install. Then I will try to flash back to kiri

Yeah that didn't work, worse it just goes to bootloader and gives up
[Google Pixel 6 Pro] roirraW "edor" ehT:
There is a disconnect and confusion between those talking about using 24306 and those who use 24300. The use of 24306 is related to updating using the OTA sideload method (not related to any kernel). I always flash the full factory image without the -w, so I just stick with Magisk Stable v24.3.
[Google Pixel 6 Pro] Lughnasadh:
Thanks so much for the update! Really appreciate the time you spend as well to provide such detailed information on various aspects of the kernel and kernel related things 👍

As a side note, Canary Magisk was updated to 24307 and the latest version of this kernel (2.4) is working fine with it on the May firmware update....for me.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Try

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). You can deselect any option to wipe and see if you can at least get the phone working without losing any data first.

Then, I always use the flash-all.bat from the full factory image with the -w removed, I boot into Android without root, let the system finish the update, then I use fastboot to flash the Magisk'd (Stable v24.3) stock boot.img, then boot up. Finally, if everything is good so far I use ExKM to flash the all-in-one zip package of the kernel.
[Google Pixel 6 Pro] russian392:
I flashed to stock just fine, I know what I am doing.

Doesn't work with EXKM. LMFAO what a waste of time.
[Google Pixel 6 Pro] shiftr182:
I flashed may firmware on both partitions yesterday and the phone booted fine. Flashed rooted stock kernel, got to the "g" with the progress bar, then looped. Tried rebooting again, looped, got the message that my phone might be corrupt. Flashed stock unrooted boot img and it booted fine, repatched the boot and flashed, looped all over again. I ended up booting to safemode, then rebooting. I deleted every magisk module that I had installed, and reinstalled the ones I wanted. Phone worked fine. I installed kirisakura kernel this morning and haven't had a problem since.
[Google Pixel 6 Pro] cmh714:
Worked just fine in EXKM.....keep drinking the vodka!
[Google Pixel 6 Pro] russian392:
I have been at this for 4 hours now. I have tried all sorts of things, what works for sure is the stock bootimg with stock vendor files (but patched). magisk version seems to not matter at all, as long as its the stock patched bootimg. It boots fine with the powerzip, I don't need root, nor do I use any modules. This is a full clean install from factory, there should be no issues but obviously this isn't the case.

As I said above, I have been using the manual install, and also tried EXKM, both fail but in different ways. The manual gives me corrupt device, where as EXKM straight up gets stuck in bootloader.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's not the kernel that's the problem. These Pixel 6's have some oddities from time to time. I've experienced them too. One particular month I had trouble using a custom kernel. I stuck with stock rooted kernel until the following month - then I updated and was able to use the new month's rooted custom kernel perfectly. There's no rhyme or reason that we can determine what causes these issues. It's not related to the kernel, however.

I use ExKM every month to flash this custom kernel zip.
[Google Pixel 6 Pro] russian392:
That is bizzare. Never had this issue with a single previous device. But whatevs.

With EXKM it gets to the google logo, flashes green then bootloops. GG's.
[Google Pixel 6 Pro] roirraW "edor" ehT:
There was never a Samsung Exynos-based Pixel before. There have been many unexplained issues on these phones. Some of us, like me, have been lucky to only experience a few minor oddities.

I believe you - that just doesn't happen for most of us most of the time. It won't surprise me if for next month's update you're able to use next month's kernel without any issue. Good luck to you.
[Google Pixel 6 Pro] russian392:
We shall see. Ill keep my bootloader unlocked and maybe give it another go later. I am pretty sure I can dust off the old notes from the good old days and see what I can do. Root was the way for me up until the 2016/2017 era, heck I didn't even have this many issues with Kiri on my p4...absolutely nuts.

EDIT: Tried one more thing, but in the end, same issue. EXKM flashes, then when it reboots, the google screen flashes green and bootloops. Guess I have tried everything.
[Google Pixel 6 Pro] scloutkst:
@Freak07 Whatever voodoo ritual you performed to finally tame the heat in this phone is absolutely amazing! I'm assuming this is the pmu limiter you described in the latest update, that throttles all the cores until actually needing the performance...

I've been lounging in bed browsing reddit and YouTube, etc like I usually do on lazy days off. I've been using the phone for two hours now and the battery temperature has never gone over 31 Celsius. It now hovers between 29 and 30 C. Previously my phone battery temp would reach 36-39 Celsius doing the exact same thing. Just light usage on reddit and YouTube.

The phone is completely cool to the touch, as if I had just picked it up off the table after not using it all night. This is after two hours of use. I haven't used the phone long enough to have any hard info on battery life, but I can already tell it's light years ahead of where it has been.

This pretty much confirms what I had been thinking since launch with all the reports of heat and issues. Especially with some people having no issues and some having all of them. Seems to me Google decided to go extremely fast and loose with the binning of the tensor soc. Basically passing anything that remotely resembles a functional soc. Ultimately I think the practically non existent binning lead to lots of chips getting through that were actually partially defective.

My launch day unit had severe connectivity issues, and nothing could fix them. Ended up doing an RMA because of overheating, especially while charging. Refurbished replacement had zero connectivity issues, however still ran incredibly hot. Not as hot, but similar to my older phones that had hot inefficient chips in them.

Anyhow.... Sorry for the rambling. Thank you so much for your hard work. You have consistently put out amazing work for as long as I've seen you here on XDA. You're an invaluable part of the community. And thank you for making me actually enjoy using this device. Something I thought was impossible at this point.
[Google Pixel 6 Pro] Utini:
Works fine as always.

Friendly reminder: Reboot in airplane mode due to ProxyHandler bug.
[Google Pixel 6 Pro] russian392:
So on CLEAN may factory image, with magisk 24300, only the Previous build of kiri will boot (2.3) 2.4 fails to boot when flashed over the stock bootimage. 2.4 will only boot by flashing 2.3 first then 2.4 on top. Looks like I am not so rusty after all at troubleshooting these BS electronics.

I understand that it is customary to upvote everyone who says "works fine for me get over it" but thanks for the help roirra, you got me thinking, and I got it working :)

Freak, just fyi about this, anyone dirty flashing may not have issues but a clean install may not work for some like it didn't for me.

@roirraW "edor" ehT @Freak07
[Google Pixel 6 Pro] roirraW "edor" ehT:
That happened to me one month as well - sometime in the last couple of months.
[Google Pixel 6 Pro] Freak07:
manual installation or kernel.zip?

edit: well I can´t start from a wiped factory image as I don´t have the time to setup my phone fresh every month. I updated by flashing the factory image each month without wiping userdata, since I got the phone.

I flashed back to stock may images on my end, so I started from a stock May firmware without userdata wiped and tried both methods and everything worked without problems on my end flashing the 2.4.0 release.

Sounds like another funky magisk/verity issue. Did you use magisk stable or magisk canary?

edit2: I really wonder if whatever was wrong for you did get fixed by essentially flashing an older boot.img to reset something verity related.

similar to how one can get rid of the device is corrupted message by flashing/booting an older boot.img and then the correct current one as described here.

It sounds oddly similar.
[Google Pixel 6 Pro] a g bell:
Just flashed 2.4 after flashing may factory image no issues But l do suffer from device is corrupt issue after flashing. So after flashing factory image l again flash vbmeta --disable-verity --disable-verification.
[Google Pixel 6 Pro] capntrips:
I'll add that simply booting it is enough, no need to flash it.
[Google Pixel 6 Pro] Poesini:
Hey @Freak07 , is there a tutorial I can read somewhere on how to compile myself the kernel? Currently running Gentoo on amd64
[Google Pixel 6 Pro] roirraW "edor" ehT:
Post #3 might help you.
[Google Pixel 6 Pro] russian392:
I tried manual first. Wouldn't boot. Wiped completely (since it was already wiped) and same issue. Tried canary after stable. Both boot stock image but not kiri. Then tried the zip after yet another wipe. Different issue but still wouldn't boot. The manual method yielded a never booting google logo where as the zip would bootloop. Both stable and canary magisk.

After I tried the 2.3 zip, it worked and then I flashed 2.4 kn top and it worked. Using stable magisk.

No joke I tried every combination (24200, 24300, 24307) on all stock and kirisakura images, and the only thing that worked was flashing 2.3 on top of android 12.1 May and then flashing 2.4 using zip
[Google Pixel 6 Pro] Freak07:
Unfortunately I don´t know what could be the issue on your end as I can flash zip or images manually just fine over the stock may firmware.

The only thing that comes to my mind is yet another verity related issue, but that´s really out of my control.

I assume you didn´t disable verity/verification for vbmeta on your end since that´s no longer strictly necessary as long as you´re using magisk to patch the boot.img or flash when magisk is installed on a device.

I think they way magisk handles that is not totally failsafe. It works for most, but doesn´t for some.

I kept verity/verification disabled since I got the phone as I want to be able to flash non magisk patched non stock images for development purposes to my device. But I know there are enough people running with verity enabled without any problems.
[Google Pixel 6 Pro] Freak07:
Thanks for the kind words, I really appreciate it.

Well it was all prepared before. So not much machine :)

Yes it´s definitely interesting, but unfortunately I wasn´t able to solve the panic so far. :( But it´s definitely still on the to-do or revisit list.

Thanks for the report and the kind words. It´s really appreciated! :)

As usual thermals, temps, power draw etc is very much based on the usage. But it seems unfortunately the few last gens of SoCs have all a similar problem. They can deliver more and more peak perf, but also emit more and more heat. This heat can´t get anywhere on a mobile device, so it´s just all circling around how much of those perf is actually available to be spent. Might be a bit simplified, but it essentially boils down to that. Exynos, Snapdragon, Tensor (exynos) it´s all very similar.

I don´t think the binning has much to do with the heat. The voltages are quiet close in the different binnings as you´ll see when I finish up all the graphs. :) But it could just be that a few devices of the first few batches have problems that went unnoticed.

excellent remark I adjusted the FAQ! Thank you.

Essentially sync kernel build environment as in the post @roirraW "edor" ehT already linked. (make sure tag is correct)

Get familar with the kernel build environment. If you want to build this kernel you need to clone all the repos I uploaded to my github to the correct place in the kernel build environment. (main kernel, vibration, camera, touch etc)

You can build this kernel with build/build_abi.sh --update
[Google Pixel 6 Pro] Jon8RFC:
I just want to have it documented here for future reference if we both had a similar issue. Did your phone power up but just sit there, seemingly frozen, at the full "Google" logo, or did you get to the "G" animated logo and it sat there.

Ah, doing a working 2.3 and then 2.4 is something I'll need to try when I'm up for tinkering again. Thanks for sharing that. I don't think 2.3 booted for me though :/ It's hard to remember all I went through yesterday.

2.3.0 (both old and new) patched with 24300 crashes as well. Bummer.
[Google Pixel 6 Pro] ttle54:
Does anybody have problems updating to May patch on Pixel 6 Pro? I attempted to sideload it from Recovery Mode but no lucks either.
[Google Pixel 6 Pro] Vman006:
Its ok to flash on april security?
[Google Pixel 6 Pro] Texan1:
I thought this was fixed/we didn't have to do this anymore??
[Google Pixel 6 Pro] Daenjel:
Experienced the same issue but on the Pixel 6, I always flash everything back to stock just to update via OTA, rooted my device successfully and then I attempted to flash the kernel, got the "device is corrupted" message, it was a PITA to get rid of the message, I need to use the method where you flash the boot.img from the february image, then flashed the boot, dtbo, vendor_boot and vendor_dlkm from the May update, after attempting this for 3 times the device finally booted, seems weird to me that I needed to repeat the process 3 times for it to work, but heck, at least it booted, I've never done a clean flash of my device since I purchased it, first time that I've encountered this issue.
[Google Pixel 6 Pro] Utini:
Nope, still not fixed.
[Google Pixel 6 Pro] Texan1:
So *every* time we reboot our phones we need to do this?!
[Google Pixel 6 Pro] nafi2000:
@Freak07 Is your helper module still needed for this?... thanks for your work.
[Google Pixel 6 Pro] Utini:
Exactly :S
[Google Pixel 6 Pro] bush911:
May I know to do what?
[Google Pixel 6 Pro] roirraW "edor" ehT:
This isn't related to this custom kernel. Please take this to one of the relevant How To Guide threads in this section. But no, no trouble here at all, but I always use the full factory image method. That's all I'll say in this thread.
[Google Pixel 6 Pro] Texan1:
Reddit thread says this was fixed in the second Feb patch (which I remember reading at that time).
[Google Pixel 6 Pro] Utini:
Reddit is wrong. Check the bug tracker of google/android.
[Google Pixel 6 Pro] Freak07:
While I appreciate the pointer for others @Utini ( I know you did this only with the best intentions here) this does not really belong to this thread here. It also started to derail the thread quite a bit in a complete off-topic direction.

I don´t mind occasional off-topic as I always like to see the community work together and help each other, but it should always be kept or at least linked to the correct threads where discussion belongs once a topic is initiated here. :)

Some thoughts. I think generalizing, that everyone should always reboot with airplane mode, is a bit much.

I never booted with airplane mode enabled (and sometimes I reboot a lot :D), but I also never suffered from any problem caused by the proxy-handler bug.

yes as per the insturctions it´s crucial for the kernel to work and even boot.
[Google Pixel 6 Pro] russian392:
Google logo. Never got to the G nor the loading bar under it. Just frozen on the Google.
[Google Pixel 6 Pro] russian392:
This isn't the same. The message is just a splash screen. For me it said my system was corrupted and I needed a mandatory factory reset. Rebooting would bootloop a few times and then reach the same recovery screen.
[Google Pixel 6 Pro] anko184:
Hey guys, is their anyway to flash this kernel on custom unrooted rom? Or it's only for rooted roms?

Thanks in advance!!
[Google Pixel 6 Pro] Freak07:
Please read the requirements in the OP.

Magisk root is mandatory, otherwise the kernel can't work.
[Google Pixel 6 Pro] anko184:
Too bad for me.. Thanks anyway, i'll return to this if i root my phone again.
[Google Pixel 6 Pro] Freak07:
If the phone can´t boot and crashes pretty early during boot a few times consecutively or crashes a few times in very short succession this mode will be entered called recovery rescue party as the current slot will be marked unbootable.

Sometimes the phone tries to switch slots and recover that way, but that doesn´t always happen.

It´s just a mode that´s entered if the phone crashes a few times consecutively to prompt users to wipe the device so OEMs reduce warranty and support cases. (on a locked phone that have not been modified)

Sometimes one can get out of there by restoring a working condition and forcing the device to boot in the unbootable slot, but sometimes a wipe is the only option if the slots or something else is messed up enough.
[Google Pixel 6 Pro] russian392:
I See. Thanks for that info, is there a fastboot command that can force boot another slot?
[Google Pixel 6 Pro] shiftr182:
When you are in the bootloader you can see the current active slot. To change the slot you can run fastboot --set-active=a or fastboot --set-active=b (whichever is opposite the current slot)