Development [Kernel][06.03.2024][Android 14.0.0]Kirisakura 2.2.0_Raviantah for Pixel 6/Pro aka "RAVIOLE"

[Freak07]

To be sure: it only concerns those who haven't disabled verity and such? Although I'm not entirely sure what this hashtree patching does...

Yes the issue with magisk canary only affects those that run with verity/verification enabled and did not disable those flags.

Can I use this kernel with the newest update released today? Thanks

No source pushed yet from googles side. If you don´t want to face any issue wait until I updated the kernel for June stable release

 

[Ghisy]

Yes the issue with magisk canary only affects those that run with verity/verification enabled and did not disable those flags.

Gotcha, thanks! My 6 Pro is on Magisk stable and has had verity/verification disabled since the beginning.

 

[Freak07]

I assume the touchscreen will need the updated drivers that were needed for QPR beta builds before.

It´s getting late here and usually google is pushing the source somewhere during nighttime in my timezone. I´ll try to get the kernel updated as soon as possible once I know it´s stable.

I wish everybody a great day/evening.

 

[Jerreth]

i have been reading over all the info in here about the canary magisk issues, is there any big reason to be on canary? i am confused i suppose by all the info in here about it, i do understand how to get my phone on canary successfully but should i is the second question lol

thanks in advance.

 

[Lughnasadh]

i have been reading over all the info in here about the canary magisk issues, is there any big reason to be on canary? i am confused i suppose by all the info in here about it, i do understand how to get my phone on canary successfully but should i is the second question lol

thanks in advance.

I don't see a reason (unless you are on the A13 betas) and it sounds like John will update Magisk to Stable 25 in the near future. However, if some of the Canary changes are incorporated in Stable 25, users of custom kernels may want to be wary of that unless using the Hashtree Patcher or disabling verity & verification. See this thread and Hashtree Patcher thread for more info on that.

 

[prokiller1199]

Just now I tried disable verity & verification flags, it then requires full wipe. Luckily dirty flash back without disable those flags works. My files is safe. Thank god!
For now, I cant do full wipe yet. Will do in future.

 

[Freak07]

Update to 3.0.0

Hey guys and girls,

Alright here´s the next update and it´s a very big one that´s why I decided to bump the kernel version to 3.0.0.

I decided to rebase the kernel ahead of time. The base kernel is now build upon the Android 13 branch, but made to work on A12 by reverting a few changes that depend on too much firmware updates outside the kernel. That will also ease the transition for me once A13 stable is dropped.
Thanks to the way the kernel is build the GKI way, the rest of the device specific drivers could be adjusted to work on A12 as well.
There are quite a few improvements overall on the A13 branch and now we can take advantage of them before A13 drops as stable. Please note this kernel is made to work on A12 stable June firmware, not A13 beta.

Thanks to @capntrips and all his hard work on hashtree patcher, there should be no problems flashing the updated kernel.zip on latest magisk canary (which some users may want to use to fix certain apps otherwise detection root) while leaving the verity/verification flags enabled when updating the phone as it´s integrated in the kernel.zip now. A huge thanks to @capntrips at this point.

I will also stop distributing the files for the manual install as flashing via @capntrips kernel flasher app, which can be found here, is open source and free, works perfectly fine for me and that spares me a lot of work for each release.

Now to the actual kernel changes:

The kernel was rebased on the A13 branch for the Pixel 6 Pro but made to work on A12, which brings a lot of improvements all around.

There´s a PMU limiting feature introduced in the A13 kernel. It was imported in the previous 2.4.0 release too and configured to try to reduce heat, reduce the usage of high cpu freqs when it isn´t needed. The explanation can be found in the release post of 2.4.0.
I went ahead and refined the implementation and usage of that feature again.
Short explanation: The PMU limiter can cut back max cpu freq if the PMU (performance monitoring unit) doesn´t cross a certain threshold. If that threshold is crossed the limit is lifted and the phone is allowed to use peak performance.
While the previous approach restricted the cores just to a single limit of 1,4GHZ/1,6GHZ/2,4GHZ (for little/mid/big cores), the new approach restricts to different limits based on interaction and scenario what´s happening.
That means there are different limits and thresholds for app launches, interaction (tapping the screen, scrolling), display idle (no movement on screen content, nothing interactions with the display, no tapping the screen etc).

If none of the conditions below are met the limits are 1,19GHZ/1,32GHZ/1,42GHZ (for little/mid/big cores) if the performance threshold is not crossed.
During app launches we keep the limit of 1,4GHZ/1,6GHZ/2,4GHZ (for little/mid/big cores) if the performance threshold is not crossed. (that´s useful to not boost too much if an app is already in memory)
During scrolling limits of 1,4GHZ/1,6GHZ/1,8GHZ (for little/mid/big cores) will be set. The reason for that I will explain later.
During idle screen limits of 1,19GHZ/1,0GHZ/1,1GHZ (for little/mid/big cores) will be set if the threshold is not crossed.

If the device really needs max perf, the limits will be crossed and it will also perform to its max. The performance impact by the PMU limiter is minimal to negligible/non-existent.

Uclamp value of top-app tasks, rt-tasks and sf-tasks are raised during interaction. This improves scrolling performance as it biases tasks to start on a mid or big CPU rather than a small one. By restricting the maxfreq of mid and big cores via the PMU limiter during scrolling/interaction we do not generate additional heat by doing that. The threshold was specifically tuned by doing a lot of tracing to achieve not crossing the PMU limit during scrolling. For example gmail scrolls a lot smoother now. Some apps like twitter just need to fix scrolling on their own end.

BFQ improvements from linux-main were backported.
Scheduler updates for pelt, load, tasks placement were backported from linux-main.
LRNG was bumped to V45.
An improved energy model for thermal control is used.

And a huge bunch of additional changes.

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

 

[Lughnasadh]

Update to 3.0.0

Hey guys and girls,

Alright here´s the next update and it´s a very big one that´s why I decided to bump the kernel version to 3.0.0.

I decided to rebase the kernel ahead of time. The base kernel is now build upon the Android 13 branch, but made to work on A12 by reverting a few changes that depend on too much firmware updates outside the kernel. That will also ease the transition for me once A13 stable is dropped.
Thanks to the way the kernel is build the GKI way, the rest of the device specific drivers could be adjusted to work on A12 as well.
There are quite a few improvements overall on the A13 branch and now we can take advantage of them before A13 drops as stable. Please note this kernel is made to work on A12 stable June firmware, not A13 beta.

Thanks to @capntrips and all his hard work on hashtree patcher, there should be no problems flashing the updated kernel.zip on latest magisk canary (which some users may want to use to fix certain apps otherwise detection root) while leaving the verity/verification flags enabled when updating the phone as it´s integrated in the kernel.zip now. A huge thanks to @capntrips at this point.

I will also stop distributing the files for the manual install as flashing via @capntrips kernel flasher app, which can be found here, is open source and free, works perfectly fine for me and that spares me a lot of work for each release.

Now to the actual kernel changes:

The kernel was rebased on the A13 branch for the Pixel 6 Pro but made to work on A12, which brings a lot of improvements all around.

There´s a PMU limiting feature introduced in the A13 kernel. It was imported in the previous 2.4.0 release too and configured to try to reduce heat, reduce the usage of high cpu freqs when it isn´t needed. The explanation can be found in the release post of 2.4.0.
I went ahead and refined the implementation and usage of that feature again.
Short explanation: The PMU limiter can cut back max cpu freq if the PMU (performance monitoring unit) doesn´t cross a certain threshold. If that threshold is crossed the limit is lifted and the phone is allowed to use peak performance.
While the previous approach restricted the cores just to a single limit of 1,4GHZ/1,6GHZ/2,4GHZ (for little/mid/big cores), the new approach restricts to different limits based on interaction and scenario what´s happening.
That means there are different limits and thresholds for app launches, interaction (tapping the screen, scrolling), display idle (no movement on screen content, nothing interactions with the display, no tapping the screen etc).

If none of the conditions below are met the limits are 1,19GHZ/1,32GHZ/1,42GHZ (for little/mid/big cores) if the performance threshold is not crossed.
During app launches we keep the limit of 1,4GHZ/1,6GHZ/2,4GHZ (for little/mid/big cores) if the performance threshold is not crossed. (that´s useful to not boost too much if an app is already in memory)
During scrolling limits of 1,4GHZ/1,6GHZ/1,8GHZ (for little/mid/big cores) will be set. The reason for that I will explain later.
During idle screen limits of 1,19GHZ/1,0GHZ/1,1GHZ (for little/mid/big cores) will be set if the threshold is not crossed.

If the device really needs max perf, the limits will be crossed and it will also perform to its max. The performance impact by the PMU limiter is minimal to negligible/non-existent.

Uclamp value of top-app tasks, rt-tasks and sf-tasks are raised during interaction. This improves scrolling performance as it biases tasks to start on a mid or big CPU rather than a small one. By restricting the maxfreq of mid and big cores via the PMU limiter during scrolling/interaction we do not generate additional heat by doing that. The threshold was specifically tuned by doing a lot of tracing to achieve not crossing the PMU limit during scrolling. For example gmail scrolls a lot smoother now. Some apps like twitter just need to fix scrolling on their own end.

BFQ improvements from linux-main were backported.
Scheduler updates for pelt, load, tasks placement were backported from linux-main.
LRNG was bumped to V45.
An improved energy model for thermal control is used.

And a huge bunch of additional changes.

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

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 to avoid potential issues!
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

Excellent work by both you and @capntrips

PSA: Magisk 25 has been released to the pubic Beta channel and Canary channel.

Of note and particular interest to this discussion, the changelog includes this...

"Magisk no longer patches fstabs in most scenarios, which means AVB will remain intact; some custom kernels rely on AVB being stripped out for them by Magisk."

This new kernel release couldn't have come at a better time (of course heed @Freak07 note about not using Canary 24303/Beta 25 and later at this time to avoid potential issues... until tested).

 

[scott.hart.bti]

@Freak07 you spoil us! Freaking legend!

 

[russian392]

Just to confirm a few things:
1) Should we use magisk 25? Or is 24 still working fine?
2) For the OTA update method, magisk uninstall, restore images, ota update, then should I install magisk or install kernel 3.0? I am assuming that After the ota installs we can just flash the kernel in a EXKM or whatever and be done with the update process right?

 

[xflowy]

getting a bootloop on v3 with magisk 24.3 stable. anyone else?

 

[scloutkst]

Running a 6 pro with 24.3 stable. No issues so far. Flashed with no problem.

 

[Freak07]

getting a bootloop on v3 with magisk 24.3 stable. anyone else?

I don't have problems using latest canary.

Might be that you need to use canary or beta if you keep verity/verification enabled with the updated zip. I don't have the possibility to test all conditions on my own end.
I know it works fine with latest canary with vbmeta flags disabled on own end.
A tester flashed on latest canary 24316 with vbmeta flags enabled as well without issues.

Do you have vbmeta flags for verity/verification disabled or enabled running magisk stable?

Running a 6 pro with 24.3 stable. No issues so far. Flashed with no problem.

Nice, thanks for the reports. Verity/verification flags enabled or disabled?

 

[shizonic]

Just flashed 3.0.0 and magisk 25001. Everything works fine, including my banking apps. Great work. Thank you.

 

[scloutkst]

I don't have problems using latest canary.

Might be that you need to use canary or beta if you keep verity/verification enabled with the updated zip. I don't have the possibility to test all conditions on my own end.
I know it works fine with latest canary with vbmeta flags disabled on own end.
A tester flashed on latest canary 24316 with vbmeta flags enabled as well without issues.

Do you have vbmeta flags for verity/verification disabled or enabled running magisk stable?


Nice, thanks for the reports. Verity/verification flags enabled or disabled?

Apologies. Im not sure. Been so long since we had to manually mess with this since android 12 launched.
All I have done is patch the boot file, and flashed it via fastboot. Rebooted and flashed the kernel. So whichever way it turns out without any extra intervention.

Is it enabled then? Again my apologies.

 

[xflowy]

Do you have vbmeta flags for verity/verification disabled or enabled running magisk stable?

sorry im a little noobish but thats the thing you (can) disable when rooting the first time, right? and if you disable it, it wipes the phone. but you only have to do it once and it stays that way, right? that i did, when i rooted month ago.
or do i need to redo it every time i upgrade flash a new factory image? :/

edit: everything worked with magisk beta 25.

 

[Lughnasadh]

Just to confirm a few things:
1) Should we use magisk 25? Or is 24 still working fine?
2) For the OTA update method, magisk uninstall, restore images, ota update, then should I install magisk or install kernel 3.0? I am assuming that After the ota installs we can just flash the kernel in a EXKM or whatever and be done with the update process right?

For OTA updates, if you are running a custom kernel you will have to manually restore all 4 of the stock mages the kernel modifies because Magisk won't restore all of them. If you don't you will fail the PRE-OTA verification checks and the update will fail.

So first you would want to manually flash the 4 stock images, then go through the Install to inactive slot procedure (make sure you read instructions on how to properly do that). After that you should be updated and rooted and then you can flash the kernel.

But honestly, the Install to Inactive slot method can be hit or miss. Better off updating via flash-all in my opinion.

 

[Psfanboy88]

Updated this way to retain root and my data. Flashed the Kernel afterward with FKM. I didn’t disable any Magisk Modules. Works fine.

• Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
• Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
• Extracted the new boot.img
• Copied new boot.img to the phone
• Patched the new boot.img with Magisk Stable
• Renamed Magisk'd boot.img so I know what version of firmware it's for
• Copied the Magisk'd boot.img back to the computer
• Disabled all my Magisk Modules
• Removed the "-w " from the flash-all.bat
• Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
• Open a Command Prompt, navigated to S:\platform-tools
• adb reboot bootloader
• flash-all.bat
• Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
• adb reboot bootloader
• fastboot flash boot kernel.img (renamed Magisk'd boot.img)
• fastboot reboot
• Unlock, check everything's working
• Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
• Reboot, unlock, made sure everything's working

Source: https://xdaforums.com/t/june-2022-u...central-repository-of-relevant-links.4352027/

 

[russian392]

Updated this way to retain root and my data. Flashed the Kernel afterward with FKM. I didn’t disable any Magisk Modules. Works fine.

• Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
• Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
• Extracted the new boot.img
• Copied new boot.img to the phone
• Patched the new boot.img with Magisk Stable
• Renamed Magisk'd boot.img so I know what version of firmware it's for
• Copied the Magisk'd boot.img back to the computer
• Disabled all my Magisk Modules
• Removed the "-w " from the flash-all.bat
• Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
• Open a Command Prompt, navigated to S:\platform-tools
• adb reboot bootloader
• flash-all.bat
• Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
• adb reboot bootloader
• fastboot flash boot kernel.img (renamed Magisk'd boot.img)
• fastboot reboot
• Unlock, check everything's working
• Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
• Reboot, unlock, made sure everything's working

Source: https://xdaforums.com/t/june-2022-u...central-repository-of-relevant-links.4352027/

Did you reflash the manual install required dtbo/vendor_boot and vendor_dlkm?
NVM. This is the guide to do it all, thanks.

@Freak07
Did this list. Using old magisk 24.3 24300. No issues.

 

[swieder711]

Another success story. Dirty flashed the June update. Installed Magisk v25.0 and then used FKM to install Kiri 3.0 stable. Took 15 minutes for the whole process. Everything went as smooth as butter.

Also, Root not detected by any of my apps.