yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Jerreth:
you absolute winner!!!!! thank you this worked brilliantly i just used the jan image and same exact outcome thank you so much!!!!
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
LoL had you posted an hour back, I wouldnt have re-discovered the wheel and flashed an earlier version of firmware as a wipe hahaha to get rid of the message.
[Google Pixel 6 Pro] Jerreth:
And of course thank you @Freak07 for all you do for us you rock!!!!
[Google Pixel 6 Pro] Sek0n:
Glad to see this is mostly figured out by the time I woke up (y)

Thanks for pointing this out. Worked for 12 Stable as well. Flashed the old Feb (.003) boot.img, booted(worked), then went back and flashed the current patched boot, and the msg was gone. All good now.
[Google Pixel 6 Pro] Freak07:
Was anyone able to boot one of the zips I uploaded yesterday? Be it on stable a12 or A12L.

The one I uploaded yesterday or earlier?
[Google Pixel 6 Pro] Freak07:
A12L QPR3 Beta Kernel

These zips will work using magisk stable 24300 on A12L QPR3 beta.

Do not upgrade magisk to 24303 or more recent prior to flashing the kernel or after flashing the kernel, as this will cause the device to not boot. At the moment of writing this only affects canary, but it might affect stable at one point.

These zips are provided as is. Feel free to report issues with proper bug reports (containing logs, steps to reproduce according to the guide linked in the FAQ, but they might remain unresolved if it´s not easy to fix without running A12L Beta on my own end.
[Google Pixel 6 Pro] krystiano:
Installed your zip without problems.

I'm with 24300 magisk (don't have any update 🤔)
[Google Pixel 6 Pro] Freak07:
Thanks for reporting back. Yes the problem seems to exist only for those on latest canary 24303. You're on stable/beta channel of magisk i guess :)
[Google Pixel 6 Pro] krystiano:
I'm on stable one.
[Google Pixel 6 Pro] fuarkgl3:
Latest zip worked for me on A12L but i use magisk stable
[Google Pixel 6 Pro] phaino00:
Latest one results in device corrupt message on cannary channel. I used Oriole 1.9 12 version. I have installed factory image with wiping date and still receiving device corrupt message. :unsure:
[Google Pixel 6 Pro] Freak07:
https://xdaforums.com/t/kernel-08-0...pixel-6-pro-aka-raviole.4358435/post-86600561

I guess the suggestion in the linked post might work for you too, to get rid of the corrupt message.

You're running stable A12, not the A12L feature drop correct?

Can you still boot or are you stuck in fastboot/device corrupted screen?

No clue what's happening as it's working fine on my end...
[Google Pixel 6 Pro] phaino00:
I am on stable A12. I can boot up after getting by device corrupt message. I reflashed the boot.img but it did nto resolve it. I have to run a quick errand, but I am going to try to flash an older version when I return to my pc. It should be a good day, but I do hope to resolve before the Chelsea game. Thanks for your feedback.
[Google Pixel 6 Pro] Freak07:
Alright, thanks for the feedback too! Thanks for taking the time as well.

Fingers crossed that method will get rid of the corrupt message for you as well.
[Google Pixel 6 Pro] phaino00:
Another bit of information. When installing factory image and phone reboots to fastbootd, the device corrupt message appears and you have to press power button to enter fastbootd mode to complete installation. Right now, I am installing the first Feb update (.003). I'll provide an update shortly.
[Google Pixel 6 Pro] phaino00:
Installing the first Feb update (.003) resolved the device corrupt message issue. Thanks again for the feedback. (y):cool:
[Google Pixel 6 Pro] Divine Bicycle:
It's happened again except this time I haven't been videoing. I have been watching a little YouTube and listening to Spotify but that's mostly it. The back of the phone is insanely hot. Here is the screenshot of FKM.
[Google Pixel 6 Pro] Lughnasadh:
.

Using:

Raven

QPR3 Beta 1

Was already on Canary 24303 (via patching stock boot image)

Flashed Latest Kiri Kernel 1.8.9_A12L for Raven (from Post #1,058) over stock kernel

All my mods work with stock kernel on Canary 24303. However, just to make sure I disabled all mods and flashed Kiri kernel again.

Same result as before (even with mods disabled). After flashing, go to reboot and get stuck in bootloader/fastboot. No corruption message but I still have verity and verification disabled
[Google Pixel 6 Pro] cmh714:
On Canary, just flashed the new A12.....Corrupt message came back and I am just stuck at the Google again.....argh what a PITA :) Again TY for the continued efforts!!!!

***EDIT: also, I am using the latest platform tools released the other day.....not sure thats an issue but......
[Google Pixel 6 Pro] arvylas:
For some reason 1.8.9 has significantly worse screen on battery drain compared to 1.8.4 using stock qpr beta. Anyone else?
[Google Pixel 6 Pro] felek73:
Had exactly the same setup and the same result with 1.9.0
[Google Pixel 6 Pro] Jiggs82:
Hey sorry if this has been asked already but there's no kernel for a13 dp2 correct? Thanks in advance
[Google Pixel 6 Pro] jac0b:
Should we stay on stable version of magisk if we are going to use your kernel?

Update:

Just flashed 1.90 and got the corrupt message again. :cry:

I am on magisk 24303
[Google Pixel 6 Pro] Freak07:
It seems A12L and the new magisk canary don't work for kernel flashing at all.

It's the same exact kernel that was working on previous canary.

Follow the instructions in the FAQ by restoring a boot.img from a previous firmware to get rid of the corrupted message.

No clue what goes wrong, but there's no problem for me on stable A12 (Feb 004) with canary 24303.

Thanks for reporting, though i don't know any good advice.
[Google Pixel 6 Pro] felek73:
I dirty reflashed whole 004 Feb ROM and this corrupted message is still there. Should I flash boot from previous firmware on 004 ROM? I'm confused a little bit
[Google Pixel 6 Pro] Freak07:
Yes. I'm as astonished as you why this seems to work for others too, you can check the original post here:

https://xdaforums.com/t/kernel-08-0...pixel-6-pro-aka-raviole.4358435/post-86600561
[Google Pixel 6 Pro] Lughnasadh:
Do you think it may be EXKM (didn't try with FKM) that needs updating? Or just a 24303 thing not being compatible with A12L?

Also curious what will happen on Monday when the stable March/A12L comes out. I'm assuming 24303 won't work with that either.

If these Magisk changes are incorporated into the next stable version, guess it may be best to stay on Stable 24.3 rather than updating to Stable 24.4 (if or when that happens) until things are figured out.

Guess we'll find out...
[Google Pixel 6 Pro] jac0b:
How did you flash 1.90? I am using EXKM. Can it be flashed via fastboot?
[Google Pixel 6 Pro] swieder711:
Flashing boot.img from February 003 got rid of the Corrupt device message for me. After the message went away I switched to Magisk Stable (24.301)and Kiris kernel 1.8.4. Everything is good now.
[Google Pixel 6 Pro] Nekromantik:
so people on stable magisk updating to latest stable causes corrupt message but phone boots?

only canary does not boot?
[Google Pixel 6 Pro] :
flashin 003 didnt work for me. phone isnt booting anymore lol

edit: works.
[Google Pixel 6 Pro] phaino00:
It appears that just the latest canary update is where the issue lies.
[Google Pixel 6 Pro] Nekromantik:
nope I just updated to latest non canary and got corrupt message and now phone stuck on google logo
[Google Pixel 6 Pro] Freak07:
I don´t know. Since exactly the same kernel works fine on the same firmware with previous magisk canary, some change doesn´t play well with flashing kernels. Don´t think this would be related to EXKM for FKM.

Patching stock kernel seems to work, which leaves me with no clue now that I´ve updated magiskboot (which is used to repack the kernel when flashing the kernel.zip, similar to what happens when patching a boot.img) to either the latest canary or latest stable, which both result in the same thing on A12L unfortunately.

Yes, we´ll see what happens with the march update on Pixel 6 once it drops. I´m not really familiar or involved in magisk development and I don´t have the time to flash 12L myself.

Did you check via top command if something hogs the CPU in background like I suggested earlier?

You can also try to take a dmesg and a logcat via exkm the moment it happens. Maybe there´s any clue if something goes wrong in the background.

Do you use any mods that alter the scheduler, changes CPUfreqs, other kernel tweaks via kernel managers, scripts etc?

I think there´s more than one issue to be frank.

It seems being rooted via latest canary on A12L QPR3 beta and flashing an anykernel.zip just does not work and sends people

Some users ran into the device is corrupted message for a quite a while now. It not only happens when flashing a kernel.zip, but in the end it seems related to a problem with verity/vbmeta and magisk. I think it´s related to keeping verity/verification enabled (not disabling the vbmeta flags via fastboot) and something just gets scrambled. Check the forums there are a few threads with plenty of cases.

To get rid of the corrupted message without a wipe check the FAQ of this thread. There´s a post with a method of flashing an "outdated" boot.img linked that seems to have worked for everyone so far to get rid of the corrupted message.

There´s no reason the 1.9.0 zip I posted yesterday wouldn´t work, if everything is "in order" on a device running stable A12. I can successfully flash it myself on latest canary, on outdated stable magisk, on latest stable magisk.
[Google Pixel 6 Pro] Nekromantik:
Yeah I had both issues. Im on A12 stock running Feb 04 and updated magisk stable while on 1.8.4 kernal and phone no longer boots plus the corrupt message. I had to re flash 004 update to get phone to boot again.
[Google Pixel 6 Pro] Jerreth:
Likewise I am on stable a12 004 works fine with Canary 24301 if I update 24303 I get the corruption and no boot. I do have verity enabled however. And if I root with 24303 on stock kernel it's fine also
[Google Pixel 6 Pro] DespairFactor:
@Freak07 the issue is tied to the do modules bit in AnyKer el3, you will have to disable this to use magisk 24303 on 12.1 and 13. Have some of your users give it a go to confirm.
[Google Pixel 6 Pro] Freak07:
The helper module itself that gets created (the contents of the module) or the mechanism that creates the module in anykernel3?

Manually patching a compiled boot.img and flashing it alongside the other images via fastboot failed as well, as somebody tested that on A12L. (but i had the tester flash the module separately).

Hence the question if it's the content of the module?
[Google Pixel 6 Pro] pyroelite:
Stock A12 Feb v2

v1.9 working. Flashed with FKM. Magisk 24.3 modules (universal safetynet fix & systemless hosts) disabled.

Was getting boot loops with 1.8.4. I didn't test 1.8.4 independently after disabling modules as I just went straight to 1.9.
[Google Pixel 6 Pro] DespairFactor:
Just the function within AK3, if you disable do modules it will flash fine and boot
[Google Pixel 6 Pro] Freak07:
Unfortunately it doesn't seem to help for my kernel. Thanks for the suggestion though.
[Google Pixel 6 Pro] Phascinate:
Very happy it worked! Tried everything to get rid of the corrupt message (excluding resetting my phone - that was NOT something I was willing to do). FIgured there must be something that tells Android that it has been updated (and therefore to get rid of the corrupt message) and decided to simply try seeing if the boot.img file was the trigger for it. Very happy I was right!
[Google Pixel 6 Pro] Phascinate:
Eventually Magisk Stable will switch to 24303, so again, if any of you need a Magisk 24300 Magisk boot.img for the Pixel 6 Pro, here's a download for before that happens. Only thing mofidied is that it is modded with Magisk 24300 (which works with this kernel - it worked perfectly for me on the newest Beta). Note that this boot.img is for QBPR3 and will only work on this version. This is a perfectly working modified version of the boot.img ftom QBPR3. Simply flash it using fastboot and then use EXKVM or another kernel flashing version with this and it should work with the Kirisakura kernel.
[Google Pixel 6 Pro] Jiggs82:
So guys i got the corrupt message as well with latest canary magisk after flashing despair kernel even tho my phone's boots back to a13 dp2 stock kernel after flashing back the a13 dp2 image. How can I get rid of that message without wiping my device?
[Google Pixel 6 Pro] vassosman:
Is there not a chance that due to the errors it's causing, it would get fixed in 24304(or whatever the next rev is)?
[Google Pixel 6 Pro] Phascinate:
I sure hope so. Maybe we should all open tickets on the official Magisk in hopes this gets fixed in the next Canary. Otherwise the only fix seems to be to disable verity (which will reset your device). I really hope this isn't the only way to flash kernels going forward. Would be quite a pain. This is my understanding at least.
[Google Pixel 6 Pro] Freak07:
Check #4. There´s a method linked that should help you out.

Lets hope so.
[Google Pixel 6 Pro] Nekromantik:
is this only on custom kernel this issue?

i see no bugs raised on magisk github
[Google Pixel 6 Pro] Homeboy76:
New - Magisk Canary 24304
[Google Pixel 6 Pro] Texan1:
So has this 'fixed' the issue with custom kernels?!
[Google Pixel 6 Pro] Homeboy76:
¯\_(ツ)_/¯
[Google Pixel 6 Pro] Texan1:
Fair enough, thought that was maybe why you posted it in the kernel thread...
[Google Pixel 6 Pro] Hecke92:
I tried to install the update a few hours ago and went to bootloop
[Google Pixel 6 Pro] Lughnasadh:
Do you mean you went into a bootloop when you updated Magisk to 24304 or when you tried to install this kernel after updating Magisk?

If the former, there are some mods that may make you bootloop with 24304. AML is one of them is appears.

If the latter, no, this kernel (12L version 1.8.9) still does not appear to be working with Canary 24304. Just tested.
[Google Pixel 6 Pro] Jiggs82:
Crazy this worked for me too lol but question does this mean we can flash custom kernel with latest canary magisk or should we use stable magisk for now to root/flash a custom kernel with a12L/a13? Thanks i
[Google Pixel 6 Pro] Freak07:
Use stable one.
[Google Pixel 6 Pro] Nekromantik:
even stable magisk has issues.

I had not booting issue on magisk sable.

we need to stay on 24102 otherwise it will show corrupt and not boot
[Google Pixel 6 Pro] Jiggs82:
Yup that's what i was gonna do anyways lol thanks, but hopefully this can be resolved soon from all resources:)
[Google Pixel 6 Pro] Lughnasadh:
I think the corruption issue is more related to vbmeta/verity. I have verity and verification disabled and have had no corruption issues throughout. Currently on Canary 24304.
[Google Pixel 6 Pro] Nekromantik:
yeah I was more worried about phone not booting as thats what happened to me
[Google Pixel 6 Pro] Freak07:
Like i said earlier. Something is borked unfortunately if the device is corrupted scenario happens.

I don't know what exactly, as I'm able to flash kernels on 23403 just fine. I never saw a corruption message on my phone running stable a12 since I got the phone. I kept verity disabled since I got the phone. Based from user reports i have no idea what actually triggers the corruption message to show.

I think it's related to keeping verity enabled and something going wrong, but i have no idea exactly.

Yes, those scenarios should be treated as separate issues as one exists for a long time now. As things usually go everything gets mixed up and there's a lot of chaos now.

Unfortunately I don't have the corruption issue myself, but at least there's a good workaround now that doesn't involve wiping.

I'm not on a12l myself and if the community wants the issue to be fixed, someone needs to take proper logs on a12l when flashing the anykernel zips via the file managers, vs just patching boot.imgs with also taking proper logs while patching, alongside full dumps of the changed partitions. This needs to be posted to magisk GitHub as an issue and I'm sure it will be looked into then by either topjohnwu or one of the other magisk contributors.
[Google Pixel 6 Pro] vassosman:
March update live, don't know if there's any kernel updates that weren't public already
[Google Pixel 6 Pro] Daenjel:
With the march update finally live, the 12L kernel from post #979 should be compatible?
[Google Pixel 6 Pro] swieder711:
Is it best to use the 1.8.4 or 1.9 kernel with the March update?
[Google Pixel 6 Pro] jcp2:
I'm thinking try 1.8.9 in post #1058

Edited to show proper post # as directed by @Freak07
[Google Pixel 6 Pro] Freak07:
There´s no kernel source yet for stable march 12.1.0, which dropped a few hours ago. They probably push it during night in my timezone. Not going to bother waiting.

It´s best to wait for me until I release an update once I the new source is uploaded and I was able to compile an update so you can be sure there are no issues.

Since I´m a bit impatient, I downgraded to stable magisk 24300 and was able to boot the A12L builds from the linked post on march stable update. So far no issues. Make sure you´re not on canary 24303 or later!

If you feel comfortable and don´t want to miss out on any features (sweep to sleep is in my muscle memory), at least it´s booting fine ;)
[Google Pixel 6 Pro] Ghisy:
Hey, how do you downgrade from canary to stable Magisk? I just switched back to the stable channel in the Magisk app but I'm sure there's more to do, right?
[Google Pixel 6 Pro] Freak07:
I uninstalled magisk app, reinstalled older magisk app, repatched boot.img, flashed repatched boot.img via fastboot. (if you're running a custom kernel you need to reflash completely to stock, by following the guide from the FAQ, before flashing "only" stock boot.img)
[Google Pixel 6 Pro] Homeboy76:
I posted it because members were saying the Magisk Canary might fix it.
[Google Pixel 6 Pro] Ghisy:
Worked like a charm! Thanks.

I'm just waiting for you to update Kirisakura in a few days now :)
[Google Pixel 6 Pro] irule311:
Is there some particular way to compile this? I'm just trying to compile with CONFIG_NETFILTER_XT_TARGET_HL=m to get xt_HL.ko. Just using build/build.sh gives mismatched symbols list so I used update_symbol_list.sh which compiled it. I just can't get the module to load due to unknown symbol.
[Google Pixel 6 Pro] :
There is a touch issue for me when I'm doing this.

Try to delete a text with holding the backspace button. It works only when you tap the left side of the button. Tapping to delete works good. I remember this issue was also present on first a13 build. Was fixed with despair kernel.
[Google Pixel 6 Pro] Freak07:
Thanks for the report. (y) Noticed it myself too by now. It will be fixed once there's a build with the official 12.1.0 stable source :)

A12L QPR3 beta needed more recent touch drivers (which 1.8.9 A12L was compiled for), while it seems that 12.1.0 uses slightly older touch drivers again.

I´m usually compiling via ./build/build_abi.sh --update.

The driver you want to compile is already enabled in the defconfig of this kernel to be built inside the zImage. So there´s no need to recompile if you´re already running this kernel.

If you change the defconfig to compile the driver as an external module while building my trees (I suppose for use on other kernels), you can only use this module with this kernel, as otherwise module verification will block loading the module. As a safety measure it checks the module is compiled against this tree, as incompatible modules lead to crashes and other issues.

In that case you need to do some research on how to disable module verification, so you can load out of tree compiled modules. As far as I´m aware this can be done for the modules, as well as the zImage.
[Google Pixel 6 Pro] zszmmm:
hello，Kirisakura-Kernel can not working for 12.1.0 (SP2A.220305.013.A3, Mar 2022) for 6pro, After flashing 1.84 Kernel, it will be stuck on the G screen.what is the problem？Magisk 24.3。thanks

but it work for 12.0.0 (SQ1D.220205.004, Feb 2022)
[Google Pixel 6 Pro] Freak07:
If you don´t want to run into troubles wait for me to update the kernel with the latest source code when a firmware update is available each month. Sometimes (like this month) there are updates in the source required, which will make the device bootloop, if they are not merged to the kernel.

Also read post #1118 on the last page. ;)
[Google Pixel 6 Pro] zszmmm:
ok。thanks very much
[Google Pixel 6 Pro] Freak07:
Update to 2.0.0

Hey guys and girls,

So here´s the next update for stable march 12.1.0 firmware! This kernel is not meant to be flashed on Android 12L QPR3 Beta firmware. (for QPR3 beta kernel check this link)

Important:

Make sure you´re being rooted with magisk 24300 stable before flashing the kernel. Any magisk version above 24303 will lead to a reboot back to bootloader since android 12.1.0 and A12L QPR3 Beta. At the moment this only affects canary, but I put the warning just in case this will not get resolved in upstream magisk in time until the next stable drops. I saw a post that some modules also have problems with latest canary, so there´s a lot going on at magisk´s side at the moment.

A post containing a short write-up how to "downgrade" magisk can be found following this link.

This update has stable march 12.1.0 firmware merged (we already had most of this code, but the device specific drivers needed to be adjusted properly) and some other small fixes.

In case you missed it, since most people update their device once a new firmware is out each month, the previous release had the dirty pipe exploit fixed. This exploit is not fixed in the stock kernel on march stable 12.1.0 yet.

I´ll attach a link to the release post of 1.8.4 with a detailed changelog again, so changes are not missed. This post also contains info and links regarding the dirty pipe exploit. Link to 1.8.4 release post

Changelog:

- linux-stable 5.10.107

- built with clang 14.0.3 prebuilt by google

- march stable source merged

- previous changelog from 1.8.4 with dirty pipe fixed can be found here

- other changes, please take a look at my 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

Instructions can be found in the OP! Please follow the instructions to avoid any issues and read this post carefully. Don´t use magisk canary 24303 or more recent!

If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
[Google Pixel 6 Pro] catseyenu:
FWIW https://support.google.com/pixelphone/thread/153884074/google-pixel-update-march-2022
[Google Pixel 6 Pro] Gordietm:
I've downgraded the Magisk to stable 24.3. Now some other magisk modules work that caused bootloops before on Magisk canary. Before I flash the kernel, will I have any issues since I haven't disabled verity?
[Google Pixel 6 Pro] Freak07:
You shouldn't have issues, but it's not really in my power or control if that corrupted issue appears.

Edit: looking at the last post it might be fixed on googles end.
[Google Pixel 6 Pro] Gordietm:
Flashed with EXKM, no problems, no corrupt message. Thanks for the kernel.
[Google Pixel 6 Pro] swieder711:
Flashed via FKM. I have March update with Magisk stable 24.301. Looks to be working nicely.

Thanks
[Google Pixel 6 Pro] nafi2000:
mine is bootlooping after flasing this kernal
[Google Pixel 6 Pro] Lycidias:
Thanks for the update!

Working good on raven march firmware.
[Google Pixel 6 Pro] nafi2000:
did u flash alongwith latest magisk update?
[Google Pixel 6 Pro] Lycidias:
No I used stable because newer ones have issues
[Google Pixel 6 Pro] nafi2000:
i had to start in safemode to avoid bootloop and change evrything again
[Google Pixel 6 Pro] cosy6ay:
where to download Magisk stable 24.301? my copy from git still showing 24300.
[Google Pixel 6 Pro] Lughnasadh:
Stable 24300 (aka 24.3) is the latest stable version. 24301 would be a Canary version. There is no 24.301 version.