yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
I didn´t realize it was a question. flashing the kernel should work fine according to the reports in this thread. :)

You can also use canary if you want to. But soon magisk stable will bumped anyway and then everything that´s currently canary will be in stable magisk.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I didn't realize it was a question either, although I did recognize that it could be taken as a statement and a question.

Should work 100%. I never do the --skip-reboot. I do a full flash, boot normally and log into the phone, let the update finish (see notification until it goes away), then I boot back into fastboot and manually flash the rooted kernel there. Then I boot and use my favorite kernel flashing tool to flash this kernel zip.

I'm still on Magisk Stable v24.3.
[Google Pixel 6 Pro] bleez99:
@Freak07 @roirraW "edor" ehT

Thank you for confirming. This device is touchy and I had that corruption issue back - I forget now :)
[Google Pixel 6 Pro] Freak07:
Hello everyone,

I just found a very small oversight regarding the powerhal, which I corrected in the kernel.zip now. The kernel itself hasn´t changed.

I re-uploaded the zips for 3.0.0. If you flashed them already prior to this post, feel free to reflash. It probably won´t hurt, that much to run the old zip, but it´s better to flash the new one. Just flash over 3.0.0 if you´re already running it.

You can grab the updated 3.0.0 zips from the release post by following this link.

Sorry for any inconvenience caused. I wish everyone a great day.
[Google Pixel 6 Pro] Nekromantik:
something odd happened.

updated to June firmware and used stock patched Magisk 24.3 boot and then flashed 3.0.0 and rebooted but then it lost root
[Google Pixel 6 Pro] roirraW "edor" ehT:
Every once in a while when I launch the Magisk app it claims I lost root and prompt me to reinstall. If I then swipe it away out of Recents and launch Magisk again, it works normally.

If this isn't the issue you had, ignore this.
[Google Pixel 6 Pro] Gytole:
On latest June Patch, rooted with Magisk 25 Beta, and reflashed Kiri 3.0, all gravy on my end!

Verity checks disabled on my end. Forgot to mention.
[Google Pixel 6 Pro] Nekromantik:
nope wasn't that
[Google Pixel 6 Pro] jcp2:
Just wanted to say, used Android flash tool (kept verity enabled / kept data / kept bootloader unlocked) rebooted, let phone finish android update, rebooted to fastboot (platform tools v33.0.2) and flashed patched boot.img (slot all) supplied here (big thank you to @Lycidias ) all went smooooth! Easy peasy, light and breazy :) :) Rooted Magsik 24.3 stable with new custom kernel. Thanks @Freak07 kirisakura kernel 3.0.0.
[Google Pixel 6 Pro] Admiral2145:
25 beta magisk with 3.0 kernel June ota... I'm back no bootloops... All of May I was rooted no kernel... Finally back 💪
[Google Pixel 6 Pro] stalls:
So how can I tell if I have verity enabled or not? I used android flash tool to update the last so many times and I am not sure if it switched from having it disabled when I first bought the phone and then I eventually had a issue so I used android flash tool.

Anyways I'm May update flashed with android flash tool, magisk 24.3 stable and 2.4 kernel. Thanks!
[Google Pixel 6 Pro] ttle54:
Flashed June update then flash Kiri Sakura kernel on it. Everything is running great.
[Google Pixel 6 Pro] prokiller1199:
There is an option in flash tool website under advanced options.
[Google Pixel 6 Pro] stalls:
I was talking about on my phone currently if the device itself is or not. I only wonder because it will wipe my device if I picked disable verity and it is enabled on the phone already right?
[Google Pixel 6 Pro] prokiller1199:
if you didnt disable before then it is enabled since the beginning. Disabling requires a full wipe.

It will show this image if you try to disable.

You can also verify it using adb shell with:

adb shell

su

avbctl get-verity

avbctl get-verification
[Google Pixel 6 Pro] Nightf0x_007:
Last month i wiped my device and installed may update with dm verity disabled now i want to update to june update should i tick dm verity disable too ? Or no, i dont want my device to get screwed up with corrupted device message
[Google Pixel 6 Pro] capntrips:
Too bad I didn't know about that last week.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I haven't disabled verity and verification since last December - as soon as it became unnecessary for Magisk purposes - although at first some custom kernels still needed them disabled. I've been 100% fine except for one month a few months back every time I rebooted I got the corruption screen and had to hit the power button for it to continue booting. When the next month's update came out, I flashed the full firmware image as normal, rooted, and flashed this custom kernel and the corruption message was gone - all with no data lost. Note that in my case, the corruption message didn't keep me from using my phone, just a little irritation every time I rebooted.
[Google Pixel 6 Pro] Gungrave223:
Heads up... The latest version seems to break Netflix.... The app loads fine however, video will not play after clicking.

I confirmed it was the kernel by restoring the stock kernel... Open and play a Netflix video no issue... Flash the kernel again via FXM open Netflix and click a video and it's stuck on loading the video... But doesn't error out.
[Google Pixel 6 Pro] Joelbrentbell:
What's the best way to sideload the OTA update when on a custom kernel?

Should I use the android flash tool?

Also they have a disable Vbmeta verification should I do that?
[Google Pixel 6 Pro] TotallyAnxious:
https://xdaforums.com/t/firmware-is-out-get-your-root-on.4353565/
[Google Pixel 6 Pro] Jiggs82:
Ok cool, I just side loaded the ota, fastboot disable-verity --disable-verification rebooted , then flashed the imgs from op and the patched boot.img /kernel and everything is all good so far 👌🏻
[Google Pixel 6 Pro] cosy6ay:
just install 1.0.5 on .37 release.

all working good.
[Google Pixel 6 Pro] Joelbrentbell:
Got it updated via adb sideload running very smooth

Do you think you will eventually increase the charging speed to the full spec 30 watts at some point?
[Google Pixel 6 Pro] gokart2:
Do you know the command to flash the vendor_boot.img?
[Google Pixel 6 Pro] ram4ufriends:
Font looks good, how did you change it?
[Google Pixel 6 Pro] ram4ufriends:
Is there anyway to get Double-tap to Wake/Unlock with this Kernel? I have EXKM installed as well, but I don't see the option to enable Double Tap to Wake/Unlock.
[Google Pixel 6 Pro] gokart2:
Should be active, is through stock kernel. In options its called "tap to check phone".
[Google Pixel 6 Pro] kimo1122:
That's a single tap, we want double tap 😅
[Google Pixel 6 Pro] ram4ufriends:
I am looking for a double tap to wake, not a single tap to wake.
[Google Pixel 6 Pro] Tomatot-:
I keep seeing results on jankbenchx.vercel.app from this kernel but with newer versions, e.g. https://jankbenchx.vercel.app/results/315669217840988737

Can we try it too or did I miss something and it's already available?
[Google Pixel 6 Pro] rav101:
It's internal testing which Freak always does with a small group of internal testers before anything is released to the public. In the past we have found issues that never make it to public builds so you get a more refined (less likely to crash build).

You saw the flipside of this with v1.02 I think it was which wasn't fully tested before release and had issues. Better to be safe and a little slower to release than sorry.
[Google Pixel 6 Pro] Tomatot-:
You don't have to be sorry, it makes perfect sense, thanks for the explanation. If you're interested in a Pixel 6 user, let me know. I have time to waste :) my username is the same as on XDA, without the hyphen.
[Google Pixel 6 Pro] nafi2000:
How to update phone with this kernel and root ?
[Google Pixel 6 Pro] craigacgomez:
It's all detailed in the first post
[Google Pixel 6 Pro] Freak07:
not included in the kernel and I don´t think it will be. the integration that´s in the rom has a few advantages. last time the touch driver the 6 pro is using, was made to work with dt2w driver, the device never entered deep sleep after dt2w was used once.

sorry about that.
[Google Pixel 6 Pro] Freak07:
follow one of the guides here in the forum to first update the firmware your device is on and then follow the instructions detailed in the first post to reflash the kernel.
[Google Pixel 6 Pro] Freak07:
probably a bit late, but here it is.

fastboot flash vendor_boot vendor_boot.img
[Google Pixel 6 Pro] Jon8RFC:
Pixel 6 Pro

June 2022 "Verizon" factory image dirty-flashed

verification & verity

enabled

Magisk 25000

Kirisakura 3.0.0 zip flashed via EXKM

Booted successfully!

Thank you!
[Google Pixel 6 Pro] Freak07:
thanks for the report :) I can reproduce it too.

Next time please include a logcat and a dmesg while you reproduce the issue then it´s easier for me :)

Managed to already fix it. I´ll update the thread with 3.0.1 soon.

I think the general recommendation should be to always disable the vbmeta flags if you want to flash non stock images to your phone as that´s "easier" and the way it is expected to be. Want to flash custom non stock images -> disable vbmeta flags.

That way there´s no dependency on magisk tricks or other tools that enable us to flash custom images on the Pixel 6 pro devices.

But of course I can see the aspect of users having to wipe the phone for that if not done initially when unlocking the bootloader. And the other negative aspect is that it needs to be done each time a vbmeta.img is flashed, that means every month when manually updating the phone via a full firmware that´s being flashed to the device. If forgotten once during updating and rebooting after the update vbmeta flags are re-enabled a wipe will be required to disable the flags again.

I´m very very grateful for everything @capntrips has done so far. The fact we can flash custom kernels that easily on the Pixel 6/pro devices at the moment with all the magisk changes and the way vendor_dlkm is handled during flashing is @capntrips merit alone.
[Google Pixel 6 Pro] Lughnasadh:
@capntrips I seem to recall you saying you did some testing and was able to work around the kernel flashing issue with the new Magisk versions by disabling verity but not verification and disabling verity alone didn't require a wipe. Am I recalling correctly?

If so, I'm also wondering if disabling verity alone would work for flashing other non-stock images? And would disabling verity alone still prevent getting the corruption messages people get from time to time when flashing various images?

Any thoughts you or @Freak07 have on this? Seems if disabling verity alone would accomplish the same thing as disabling both verity and verification does in terms of our needs, and if disabling only verity doesn't require a wipe, that this may be a bit of a game changer. Maybe wishful thinking on my part and am sure further testing would be required if any of this was a possibility.
[Google Pixel 6 Pro] Freak07:
Update to 3.0.1

Hey guys and girls,

Alright here´s a hotfix for 3.0.0 which had broken netflix, amazon prime video, HBO and other streaming apps playback that relies on a trusted secure connection to establish playback. (thanks to @Gungrave223 for the report)

The A12 hal is not yet ready for some driver changes introduced in the A13 kernel base. Those changes were identified and reverted. Thanks to @TotallyAnxious for providing me the logs via PM.

Playback for those services works fine again on 3.0.1.

Seems like during testing for just a little bit over the last two weeks no time was found to watch a single stream on the phone and that little bug slipped through. 🤠

I´ll include the changelog for 3.0.0 again in this post in hide tags as I´m sure not everyone has yet upgraded and that post contains a lot of vital info.

The original release post for 3.0.0 can be found following this link.

I wish everyone a nice day.

Spoiler content hidden.

If you´re one of the unfortunate ones that suffer from the device is corrupt bug on pixel 6 series please take a look at the FAQ at the beginning of this thread it contains a solution. The issue is probably caused by a bug that affects pixel 6 devices and has nothing to do with magisk or a kernel, it just happens to get triggered when using any of those.

Changelog:

- Rebase kernel on A13 branch and make it work on A12

- preserve all previous features and improvments

- Linux-stable merged to 5.10.120

- Use prebuilt Google Clang 14.0.7 for compilation

- Scheduler improvements from latest linux kernel

- BFQ improvements from latestlinux kernel

- LRNG bumped to V45

- use improved energy model for exynos cpu cooling/thermal control

- MGLRU changes and updates

- affine IRQS to CPU 7 during camera usage for improved performance as it tends to overload the little cores

- allow GPU to scale down to 150mhz, but boost to higher value in case of interaction via powerhal

- safetynet issues some users were experiencing while running 2.4.0 official release, but fixed later via the release here are solved and gone (if your app does not work due to root on stock kernel, the same will be the case here)

- updated anykernel3.zip (thanks to @osm0sis) -> allow flashing using latest canary with enabled vbmeta flags ( huge thanks to @capntrips )

- loads of other changes, please check github

Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.

I wish everybody a great day/evening!

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
[Google Pixel 6 Pro] capntrips:
Correct. I can flash freely between stock vbmeta and with --disable-verity without wiping data. It works in the case of vendor_dlkm (or any of the avb partitions in fstab) because the function in first stage mount that sets up the verity device returns if it encounters either flag. Anything beyond that, I couldn't say.
[Google Pixel 6 Pro] Paz9:
Not kernel related but since updating to June I've had random issues, first when updating kept boot looping even without magisk, then I managed to get it booting using the Google flasher website as opposed to using the flash-all.bat, now some of my apps just display a blank screen when opening, some apps refuse to open. Same thing happens on stock (flashing back to stock without wiping same issue)

So I'll be backing up what I can and performing a clean install of June.

My issues never persisted when upgrading from March to April to may and was able to do so with the batch file.
[Google Pixel 6 Pro] Utini:
Thanks, works fine as always :)

Flashed with latest stable magisk 24003.
[Google Pixel 6 Pro] Jerreth:
i know this is not the forum to do this but there has been a bunch of chatter about it and i am struggling, does anyone have a link to a simple forum for disabling vbmeta and verification on the p6p i found a few but they are not a this is how it is done its more of sifting through the thread looking for posts until i figure it out lol

Also thank you @Freak07 for all you do for us this kernel is super buttery and your attention to the thread is great! thanks keep up the good work.
[Google Pixel 6 Pro] Lughnasadh:
-Extrat the vbmeta image from the factory image and put it in your Platform Tools folder.

-Connect phone to computer

-Open up command prompt in Platform Tools folder

-Boot into bootloader/fastboot

adb reboot bootloader

-Issue this command to disable verity and verification:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

This will require you to wipe your device

If you just want to disable verity, a wipe isn't required as recently discovered by capntrips.
[Google Pixel 6 Pro] Jerreth:
is disabling verity the only thing required to use the canary magisk and not have the corrupted message?
[Google Pixel 6 Pro] Lughnasadh:
Well, getting a corrupted message is not just specific to Canary Magisk or the current Beta Magisk, or even Magisk itself. People have gotten it doing other things as well that are unrelated to Magisk.

But to answer your question, as far as I know, it's not known at this time whether disabling verity alone will help prevent getting the corrupt message.
[Google Pixel 6 Pro] Jerreth:
thank you so much for your info here i very much appreciate it have a great one :) ill go ahead and give this a try.
[Google Pixel 6 Pro] Israafil:
Quick question should we leave zram on??? I don't see the point leaving it on since the pixel has 12 gb of ram or am i missing something?
[Google Pixel 6 Pro] capntrips:
There was some talk about it a few months back:
[Google Pixel 6 Pro] slacker126:
First off...long time follower and have always loved your kernels!

I just picked up a p6 and am trying to get up to speed.

I was on may and rooted, tried to install 2.4 last week and bootlooped all to hell. Had to do a full wipe with flash tool. I am assuming Verity or verification got me.

Now to my question, if I am on June update, magisk 25 beta installed and rooted, should the 3.0.1 kernel install with FKM successfully even though I still have Verity and verification enabled?

I know it's been kinda covered and the hashtree patcher is included but again I just bought it and am kinda looking for a summary post if someone can do so. Thanks in advance!
[Google Pixel 6 Pro] TotallyAnxious:
If you want a laggy/stuttering piece of **** device then definitely disable it
[Google Pixel 6 Pro] Israafil:
Your comment makes no sense, zram is more cpu intensiv if you did not know.
[Google Pixel 6 Pro] TotallyAnxious:
The pixel 6 has a hw accelerator and as previously posted in the thread by freak, CPUs are so power efficient now it doesnt impact anything performance wise.

And also stated by freak07, parts of the firmware expect zram to be on and functional.

There's a search function, and all you need to type is zram, if you didn't know.

You're better off messing with swappiness than disabling zram. Which I'm in no way encouraging anyone to do.
[Google Pixel 6 Pro] capntrips:
The issue is Magisk 24303+ no longer strips avb from fstab, so when the phone boots, first stage mount looks at the fstab entry for vendor_dlkm, which references vbmeta, so it looks at the hashtree descriptor for vendor_dlkm in vbmeta and tries to setup a verity device using those values, but vendor_dlkm for the kernel is different from stock, so those values are incorrect, mounting fails, and the device bootloops.

If you have verity or verification disabled, first stage mount ignores avb in the fstab entry and mounts the partition directly.

When flashing the kernel with AK3, if you have verity or verification disabled, AK3 skips the patching step. If you have a stock vbmeta, then AK3 will run Hashtree Patcher on your vbmeta and vendor_dlkm partitions, updating the hashtree descriptor in vbmeta and appending the hashtree and FEC data to the vendor_dlkm partition.

tl;dr While the method differs slightly, 3.0.1 should flash and boot successfully with or without either of the disable flags.
[Google Pixel 6 Pro] Jon8RFC:
Magisk 24303+ causes issues with custom kernels.

capntrips figured out a workaround for Magisk 24303+

Their workaround is, currently, included in the kirisakura 3.0.1 implementation of AnyKernel3.

I successfully flashed with Magisk 25000 using EXKM with verity & verification enabled, thanks to capntrips's workaround. Others have successfully flashed with FKM, from posts I've read here.

If you get stuck bootlooping, you should be able to get back to normal without a wipe. You'll want to download the factory image and reflash four stock files (boot.img, dtbo.img, vendor_boot.img, vendor_dlkm.img) using the Android Platform Tools.

I've attached a zip file with some instructions and a batch file to do it all for you, but you can always manually run each command.

A good move is to patch a stock boot.img (from the factory image zip) in magisk ahead of time, using the "select and patch a file" method, and keep it handy for each month's update. Then, if you run in to an issue, you can flash back to rooted without extra steps.
[Google Pixel 6 Pro] slacker126:
Just wanted to follow up...flashed in FKM smooth as butter. Thanks everyone.

Magisk beta 25000 with Verity/verification enabled
[Google Pixel 6 Pro] Jerreth:
really what steps did you follow to do this work around? is it in this thread? i have been looking but well maybe i suck at searching or maybe its the damn covid brain fog :)
[Google Pixel 6 Pro] Utini:
Flashed 3.0.1. over 3.0.0 on latest stable magisk 24000. Worked fine!
[Google Pixel 6 Pro] slacker126:
1. Flashed June update, in my case was stock so took the OTA over the phone but you can update however you normally do.

2.reboot

3.let phone settle and finish update

4. Copied stock June boot.img to device

5. Patched boot via magisk 25000

5. Copied patched boot to computer

6. Reboot bootloader

7. Flashed patched boot via fastboot

8. Reboot and verified root

9. Flashed Kiri kernel via FKM.

10. Reboot

11. Profit

As easy as the old days pretty much...the hashtree patcher that's how embedded in the kernel seems to be the key ingredient as I bootlooped before educating myself on verity and verification.
[Google Pixel 6 Pro] Jerreth:
You had/have not disabled verity or verification?
[Google Pixel 6 Pro] roirraW "edor" ehT:
See their previous post (which you had quoted earlier) below:
[Google Pixel 6 Pro] slacker126:
No I haven't touched them, both are enabled. If you bootloop you can restore...or worst comes to worst you can disable them and wipe the slate clean.

But it should work fine for you as-is.
[Google Pixel 6 Pro] Jerreth:
you had mentioned "I successfully flashed with Magisk 25000 using EXKM with verity & verification enabled, thanks to capntrips's workaround." this is why i had asked so i think i understand now that the "workaround" is in the kernel now ok cool ill give it a try
[Google Pixel 6 Pro] Jerreth:
welp i decided to just install magisk 25 over 24.3 and just install it on to the existing kiri that was installed already and boom boots no issues what so ever google pay even works hooray :^)
[Google Pixel 6 Pro] Poesini:
Currently running ProtonAOSP 12.3.2 and when trying to patch 3.0.1, I get unsupported android security patch level... I guess I can't flash just yet, right?
[Google Pixel 6 Pro] stalls:
What is it supposed to say when I run those commands? Mine says inaccessible or not found for both and what does that mean?
[Google Pixel 6 Pro] Freak07:
The zip checks for June security patch state.

I guess it should work on May too, but you're on your own a bit on proton AOSP anyway.

You can get it to flash by opening the zip, open and edit the file anykernel.sh and change supported.patchlevels to "2022-05 -" (assuming proton is may security patch) or just remove everything past the "=".
[Google Pixel 6 Pro] Poesini:
Yes, I wanted to do that, but as it had security stuff I didn't want to meddle with it, but if you say it's "ok", yeah... I did it, flashed without issues :D

Thanks!
[Google Pixel 6 Pro] Schnedi:
v3.0.1 bootlooping for me: Custom rom, magisk 25000, june patch, fkm

v2.4.0 boots perfectly
[Google Pixel 6 Pro] prokiller1199:
https://xdaforums.com/t/how-to-check-status-of-dm-verity-to-make-sure-its-disabled.3398758/

17.63 MB file on MEGA

mega.nz

systemrw_1.32_flashable.zip/systemrw_1.32/tools/avbctl