yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] chewy74:
I can't seem to maintain root after flashing. I've tried flashing with EXKM, FKM, and kernel flasher and I always lose root after reboot

Am I missing a step? I'm on A13 ricedroid 7 for oriole.
[Google Pixel 6 Pro] Freak07:
No you're not missing anything. That just happens on most custom roms unfortunately.

You can ask the maintainer of the ROM to look into the issue, but sometimes they don't want to support mods/kernels.

I can't look into it more than I already did, as I don't have the time to wipe for cross flashing between custom ROM/stock firmware. The logs I received from users didn't show anything that would tell me the issue.

It's most likely that custom roms treat ramdisk/boot differently to the stock firmware.
[Google Pixel 6 Pro] chewy74:
Thanks for the response and great work.
[Google Pixel 6 Pro] amritpal2489:
Your work is really appreciated.. Thanks for the clarification..
[Google Pixel 6 Pro] HeeroML:
This doesn't work with grapheneOs or?
[Google Pixel 6 Pro] capntrips:
I won't say it won't out of hand, as I haven't specifically seen success or failure reported with that specific ROM, but as noted with RiceDroid earlier today, it may work, but likely without root.

If you try it out, be sure to let us know.
[Google Pixel 6 Pro] chewy74:
Question, after rebooting and losing root.. Can I manually extract the boot.img and patching it through magisk and flashing in fastboot? Will that give me root on this this kernel?
[Google Pixel 6 Pro] Freak07:
manually extract boot.img from your rom.zip.

unpack extracted boot.img via magiskboot, replace zImage with the one from my kernel.zip (Image.lz4), repack back to the now modified_boot.img, patch the repacked modified_boot.img via magisk app, flash patched modified_boot.img via fastboot and check for root.
[Google Pixel 6 Pro] HeeroML:
it did bootloop, though i needed root for flashing it in the first place :D
[Google Pixel 6 Pro] ada12:
I have did your tutorial seriously :

- I take boot.img of ROM

-I unpack using Android boot image editor ( cfig github ).

-I replace zimage from kirisakura zip

-I repack to boot.img.signed

-in fastboot I flash all img from kernel kirisakura + boot.img.signed

Reboot , its boot normally in kirisakura kernel without root

In magisk v25.2 I patch boot.img.signed

Fastboot

I flash magisk img generated

Reboot

Its boot but magisk still no working

For me now :

I prefer use kirisakura kernel without root as its work great to stock a13 kernel used in lineage actually. ( since I no use app root despite no module kirisakura then ).
[Google Pixel 6 Pro] Rachid.Ala:
If you have Kirisakura installed but you don't have root try this :

1- Take boot.img of ROM and patch it with magisk app.

2- fastboot boot patched-boot.img

3- Direct install root from magisk App

4- Reboot
[Google Pixel 6 Pro] ada12:
So Everyones I have find solution for have magisk in custom rom witch kirisakura kernel ( Also you keep your custom recovery in rom )

Tools used for unpack / repack :

GitHub - cfig/Android_boot_image_editor: Parsing and re-packing Android boot.img/vbmeta.img/payload.bin, supporting Android 15

Parsing and re-packing Android boot.img/vbmeta.img/payload.bin, supporting Android 15 - cfig/Android_boot_image_editor

github.com

Edit vendor_boot.img =

Unpack vendor_boot.img of kirisakura

Copy all module of root.2/lib/modules

Unpack vendor_boot.img of custom rom

Replace from kirisakura all modules here root.2/lib/modules

Repack it & rename vendor_boot.img.signed to vendor_boot.img

Replace img vendor_boot inside zip kirisakura kernel

Flash , done & enjoy you have your recovery no replaced & Root magisk is Still working 😎

Edit : its only vendor_boot.img for the issue recovery & Root magisk no working !
[Google Pixel 6 Pro] dangambino:
wrong theead
[Google Pixel 6 Pro] w_tapper:
i think it works. thank you!

edit: ITS BOOTLOOPING HELP
[Google Pixel 6 Pro] Riccardo Portas:
Thanks for this amazing kernel!

I have only one question, i'ts possible to update the gpu driver to the latest r40p0 version?

Thanks for your hard work, it's really appreciate!
[Google Pixel 6 Pro] gnabtib8:
Was 4.3.0 pulled? I cant download this release, is there issues with it
[Google Pixel 6 Pro] phaino00:
Here you go. Post in thread '[Kernel][08.11.2022][Android 13.0.0]Kirisakura 4.3.0 for Pixel 6/Pro aka "RAVIOLE"' https://xdaforums.com/t/kernel-08-1...pixel-6-pro-aka-raviole.4358435/post-87697425
[Google Pixel 6 Pro] MidnightDevil:
This may be a silly question, but may I flash this on t1b3 release? it's the latest factory release available.
[Google Pixel 6 Pro] phaino00:
It is a silly question...lol. It's not supported on betas per OP. It may work, but at one's own risk.
[Google Pixel 6 Pro] boxemall:
I hope this isn't too off-topic, so I'll ask it real quick:

I decided to go back to stock (OFW) but dunno how to do it without losing all my data. Can anyone point me to a guide how to make a proper app/data backup so that I don't have to reinstall all apps and stuff after going back to stock? it's a giant pita having to install everything by hand. I know you can't backup and reinstall google account data, but that's okay as long as it's not every darn app I had installed. Been a while since I've done that, so I wonder what's the best way to do it nowadays.

Sorry again if it's the wrong place to ask, but it's all "kiri" related (for me anyway) :-)

regards
[Google Pixel 6 Pro] phaino00:
Flash the appropriate factory image without wiping data (remove -w from flash all file).
[Google Pixel 6 Pro] boxemall:
I

I should have mentioned I'm on protonaosp. Guess that changes things? Also I'd prolly brick the phone due to the sec counter google introduced with A13?
[Google Pixel 6 Pro] phaino00:
Yeah, if you are flashing stock from custom rom, you will have to wipe/format data. Some use swift backup for apps and data.
[Google Pixel 6 Pro] Paz9:
Is it still a requirement to disable verity/verification?
[Google Pixel 6 Pro] Freak07:
Don't i remember seeing you post on the pixel 7 forums?

In case you just mixed up the threads:

It's not a requirement for pixel 6 devices, it is a requirement for pixel 7 devices.
[Google Pixel 6 Pro] Paz9:
Oops I got the forum's mixed up! My mistake!
[Google Pixel 6 Pro] ahoslc:
Just flashed stock A13 on pixel 6 then rooted and patched with Magisk and flash Kernel. All is working great but I can't pass safety net anyone know a easy fix?
[Google Pixel 6 Pro] phaino00:
Flash the the Universal Safetynet module from this thread.

Thread '[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet' https://xdaforums.com/t/guide-pixel-6-oriole-unlock-bootloader-update-root-pass-safetynet.4356233/
[Google Pixel 6 Pro] mohamed.sakhiri:
The only way to keep root is to flash the stock rom's patched boot.img (yes it works)
[Google Pixel 6 Pro] mohamed.sakhiri:
@Freak07 can you pleeeeease support Kali-nethunter in next kirisakura update?
[Google Pixel 6 Pro] w_tapper:
I doubt that would happen...
[Google Pixel 6 Pro] mohamed.sakhiri:
That's sad, can't even use a USB wifi dongle on P6P.
[Google Pixel 6 Pro] kootik:
Can you please enable the DisplayPort function USB-C DisplayPort video output DP Alt Mode ?

https://android.googlesource.com/kernel/msm/+/184170bea097dec34b9871fc724dcac9b5989427^!/#F0

more info here

seems found it here

Kirisakura_Raviole/arch/arm64/boot/dts/google/gs101.dtsi at 00b3ea5046e72bbf89482f99dbbce9c222e3e75e · freak07/Kirisakura_Raviole

Contribute to freak07/Kirisakura_Raviole development by creating an account on GitHub.

github.com

Kirisakura_Raviole/arch/arm64/boot/dts/google/gs101-drm-dpu.dtsi at 00b3ea5046e72bbf89482f99dbbce9c222e3e75e · freak07/Kirisakura_Raviole

Contribute to freak07/Kirisakura_Raviole development by creating an account on GitHub.

github.com

and info for samsung USB DP https://github.com/freak07/Kirisaku...f89482f99dbbce9c222e3e75e/drivers/phy/samsung
[Google Pixel 6 Pro] kootik:
it seems kernel bult without USB Type-C Alternate Mode drivers

current config on last kernel 4,3

Spoiler content hidden.

as i see in here its need to add to enable support

arch/arm64/configs/stock_defconfig​

maybe good will be look in samsung kernel sources

GitHub - jgudec/android_kernel_samsung_exynos2200: Loki Kernel for the Exynos variants of Samsung Galaxy S22, S22 Plus and S22 Ultra. Telegram chat: https://t.me/+Ehf3IgzJw0k0NmE8

Loki Kernel for the Exynos variants of Samsung Galaxy S22, S22 Plus and S22 Ultra. Telegram chat: https://t.me/+Ehf3IgzJw0k0NmE8 - jgudec/android_kernel_samsung_exynos2200

github.com

much more config paramets for type-c and dp port in /arch/arm64/configs/exynos2200_r0s_defconfig
[Google Pixel 6 Pro] Freak07:
"enabling" it on the QCOM based devices that are linked in the first two commits crashes those devices, as the panel firmware does not support it.

Thanks for the effort, but it´s not as as simple as enabling a few configs for generic drivers that don´t match the actual hardware.

Even if support for the usb c out "alone" would be added, the display driver needs to be adjusted as well. If support can be added there without proper documentation of the panel and ddic we get to the bigger problem: the firmware of the panel needs to support it as well, just like on pixel 4/pixel 5.

Additionally USB connections go through the AOC driver on Pixel 6/7. That driver is also paired with a special firmware on vendor partition, that needs to match the kernel driver exactly.

If anyone knows how to do all that (especially the part about reverse engineering the firmware, hals etc) it might be possible.
[Google Pixel 6 Pro] NonStickAtom785:
Hm who better than to ask you... So many Pixel devices and such good development. I'm sure you know about the infamous un-fixable ARB Brick on the Pixel 6, 6 Pro, 6a, 7, and 7 Pro... I've been doing some hard research and I finally figured out what the phones are asking for upon initial connection. URB (USB Request Block) is the baseline for the Pixel ROM Recovery. It's basically the same thing that was used to create the HSUSB Qualcomm 9008 device drivers with the exception that it's definitely branded differently. I know this may not be your cup of tea, but as you seem to know how Google's Build System works more than I I was wondering if you wouldn't mind giving me a hand. My DM's are open and you're definitely more than welcome to decline. I'm just so close to solving this but I could use someone else to help with this too. Thanks in advance. Oh and sorry for the thread hijack...
[Google Pixel 6 Pro] Freak07:
Important

Just a heads up for everyone:

If the firmware update that's going to drop most likely today contains the QPR (=quarterly platform release, so the changes currently tested in the QPR A13 Beta) amongst the pixel feature drop, don't flash the current release of the kernel until I update the kernel with the new sources!

Otherwise there might be issues or the device refuses to boot due to the new firmware requiring the necessary kernel changes as well!

I'll try to update as fast as possible, but depending on how much conflicts there are and how fast google pushes the new source, merging the new source it might take a bit.
[Google Pixel 6 Pro] AlDollaz:
And wait we shall. ❤️
[Google Pixel 6 Pro] hanschke:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

and the phone is corupt. can you explain me my mistake?
[Google Pixel 6 Pro] prokiller1199:
verity disable do need to wipe before disabling right if not mistaken, Im using this kernel with verity enable since day one. Dont quite have the time to wipe and setup everything. So can I continue to use this kernel like before?
[Google Pixel 6 Pro] Psfanboy88:
Where exactly to we must disable verity/verification flag in the process? Or is it only relevant for someone who wants to flash the kernel first time? I’m not sure I’ve done it when I started to use this kernel. I used to update like shown below and just flash the kernel afterwards:

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
[Google Pixel 6 Pro] AlDollaz:
I'm using a P6P and have never had to do this. I just flash with EXKM. 🤷🏻‍♂️
[Google Pixel 6 Pro] w_tapper:
exactly the same here
[Google Pixel 6 Pro] Freak07:
Disabling those flags requires an initial wipe if done for the first time unfortunately.

Was my mistake to post that last bit, copy and paste error from Pixel 7 devices.

Did you try to flash back vbmeta.img without the flag disable part? Maybe that can still prevent the wipe. But I'm not 100% sure.

That was my mistake. Copy and paste error from the pixel 7/pro thread, where this is necessary and can't be circumvented.

So yes, unnecessary and you can use it like before (y)
[Google Pixel 6 Pro] Utini:
This is how I do it since the release of Android 12:

Initial, first time ever, unlock & root:

Monthly update & root:

Also useful:
[Google Pixel 6 Pro] hanschke:
flashed without disabling the vbmeta and all work fine ;)
[Google Pixel 6 Pro] Admiral2145:
Updated from Nov to Dec with root and flashed kernel... No issues thx again!
[Google Pixel 6 Pro] Utini:
Flashed. Everything smooth so far :)
[Google Pixel 6 Pro] Suavie103:
Hey freak just a question off topic I know it's early. But.. Could it be possible to port clear calling feature to older pixels? The same way adaptive sound was ported a few years back using magisk?

https://xdaforums.com/t/guide-enable-adaptive-audio-on-pixel-4-xl.4203781/
[Google Pixel 6 Pro] cosy6ay:
any link to download updated powerhint module files?
[Google Pixel 6 Pro] Freak07:
the module gets installed automatically while flashing the kernel.zip

maybe, I don´t know. :)
[Google Pixel 6 Pro] Admiral2145:
Had to donate... My battery life on p6 has improved dramatically... This is a massive update and now I'm really lovin my phone. 5g UC used to kill my battery now it's almost like having on 4g lte drainage. I almost want to switch back to lte to see how crazy the battery life is there now however, I'ma leave it on 5g from now on. Really appreciate the time and effort.
[Google Pixel 6 Pro] w_tapper:
same here, used to end a day of light usage on like 15% but now it's more like 60-70%
[Google Pixel 6 Pro] ChongoDroid:
edit: nvm I figured it out
[Google Pixel 6 Pro] ada12:
Compared to stock kernel need to admit I see difference too
[Google Pixel 6 Pro] ChongoDroid:
Latest kernel on December is noticeably cooler on setup and 0 lag in Gboard and recents. Sometimes it takes a big bump to notice how much micro jitter it had before.
[Google Pixel 6 Pro] ahoslc:
What's easiest way to go from Nov update to Dec and use your newer kernel?
[Google Pixel 6 Pro] simonk206:
- download Dec base

- extract boot.img, patch it in magisk and copy patched img to PC

- flash Dec base and patched img

- flash Kiri kernel with exkm or any other app
[Google Pixel 6 Pro] TULOA:
Has anyone tried this yet for the LineageOS Unofficial rom for the P6P by chance?

I would like to try it but I have factory reset my phone enough times now lol.
[Google Pixel 6 Pro] sille:
Hey @Freak07

I dont know If it's kernel related but I hope u can tell me at least. The last months the Google timeline worked perfectly, but in the mid of October it completely stopped working. That's the time I flashed the October update and flashed back your kernel. Including my drive backup.

Yesterday I checked and just wondered why jts broken and checked my settings, that were still the same.

Today I flashed the Dec update and with stock kernel, the timeline is working again. After having flashed your kernel, its broken again. I did a clean flash with no backup.

Has something changed in the last revisions that could affect that?

I don't want to say it has something to do with your kernel, im just asking.

Best regards
[Google Pixel 6 Pro] Freak07:
No, doesn´t sound like a kernel issue.

The timeline accessible in google maps? If you tap on the top right corner on your profile picture, then my timeline?

I can´t spot anything broken on my end there. What exactly do you mean by it´s broken?
[Google Pixel 6 Pro] minhgi:
Phone actually run cooler than stock with this kernel. Think the battery should also last longer.
[Google Pixel 6 Pro] sille:
thx for the quick answer.

if i go on the timeline its just tells me for the last two months, that there isnt enough data / information to show me something on the timeline. like i was dead the last two months :)

then i have to investigate further, why the heck it isnt working :( now im losing my bet, because im not the guy who spent the most hours in one bar :(
[Google Pixel 6 Pro] Freak07:
I guess google handles that with google play services, just like everything else in that regard. It might be that you use any magisk modules or other tweaks/apps that somehow alter or spoof your device either to another model or mess something up with play services so it can´t be accessed properly.

You´re also able to access the timeline via PC if you follow instructions there, maybe that shows something:

Google Maps Timeline - Computer - Google Maps Help

Manage your Timeline Google Maps Timeline is a personal map that helps you remember routes and trips you've t

support.google.com

But I guess it gets a bit off-topic here. Maybe just open a thread here on the forums with a question tag. Might be that someone else ran into the same issue or knows something. :)
[Google Pixel 6 Pro] exile1ck:
Anyone know why when I flash the newest version of the kernel (from 4.3.0 to 4.4.0), its saying "Unsupported Android security patch level. Aborting. . ."
[Google Pixel 6 Pro] thesnappa:
I'm on BlissRom at the moment, and I've updated to 7th Dec build OTA and had the same issue. Even though it's Dec build, the security patch is still showing November, so I am still having to run 4.3.0 for the moment. So if you are using BlissRom perhaps that's why?
[Google Pixel 6 Pro] digger16309:
Did you apply the December update of the P6 ROM first?
[Google Pixel 6 Pro] chewy74:
Anyone on blissrom using Kirisakura? Thoughts?
[Google Pixel 6 Pro] w_tapper:
crdroid using kirisakura, didn't lose root when flashed and battery has been terrific
[Google Pixel 6 Pro] chewy74:
I'm on blissrom right now and gpay is working on the rom for me
[Google Pixel 6 Pro] Wh1t3Rose:
I can't get 4.4.0 to flash on Blissrom. Says Android version mismatch. Are you on 4.3.0?
[Google Pixel 6 Pro] w_tapper:
haven't tested gpay on crdroid however safetynet is passing
[Google Pixel 6 Pro] Adviesa:
4.4.0 is for December builds, Bliss rom is on November build.
[Google Pixel 6 Pro] cbomb1337:
Hey guys when running this do I disable adaptive battery in the stock settings and also if running the battery saver in that clean slate config does that mean we also shouldn't use the stock battery saver ? Thanks for this.
[Google Pixel 6 Pro] chewy74:
That's disappointing to know
[Google Pixel 6 Pro] ppog:
I feel very foolish, but I am new to this Pixel 6.... How do I use the sweep to sleep function in this kernel? What's the gesture?
[Google Pixel 6 Pro] kpirnie:
As always big time kudos to @Freak07 for another killer kernel :)

One question, and my apologies if its already been asked/answered (im on mobile, amd search is a p.i.t.a. with my old eyes)

If I switch to 1080 in display settings, works great... until I reboot. Once I reboot it reverts back to 1440... is there a way I can get it to stick on reboot??
[Google Pixel 6 Pro] Freak07:
I didn't disable adaptive battery on my end. But it doesn't matter, the kernel is independent of this setting.

The cleanslate battery saver is purely restricting max CPU freqs to 3 predefined levels you can check here.

You can combine it with the system battery saver as they both work independently. However I like to use the Cleanslate one, rather than the system one as it doesn't restrict background activity, which can cause delayed notifications etc.

You can set it up with the CleanSlate config app, which you can find on the Cleanslate thread here on XDA.

You can adjust a ton of settings and also choose from presets there. Just tap on compact/advanced/presets to cycle through there.

Not as far as I know. You need to wait for the next QPR update to properly add full support to the framework for the 1080p setting. :)

Maybe someone knows how to maybe call it with a script and some command/intent during boot though.
[Google Pixel 6 Pro] kpirnie:
lol thought I was losin my marbles for a bit ;)

no biggie mate, on Kiri Im getting just over 2 days on one charge. Loving it!
[Google Pixel 6 Pro] w_tapper:
oh damn, I only get 7 hours of screen on time, on 4g (mostly) without Bluetooth
[Google Pixel 6 Pro] kpirnie:
not sure how much sot i get... probably not that much. tomorrow and thurs should be normal days for me so I'll check close to dull drain :)
[Google Pixel 6 Pro] dyval:
Do I need to flash stock kernel if updating to a new ROM build? Thanks
[Google Pixel 6 Pro] Druboo666:
Is CleanSlate config app a paid app?
[Google Pixel 6 Pro] linus207:
You mean stock rom? The kernel is included in the update package, so you don't need to do anything before installing the rom. After installation, however, you need to reinstall Kirisakura.
[Google Pixel 6 Pro] dyval:
So if OTA update comes, I just need to restore factory image from Magisk, install update, and then install magisk on inactive slot and reboot to keep root. Is that right? Thank you.
[Google Pixel 6 Pro] linus207:
That's a lot more than I do. I disable the magisk modules, install the already magisk-patched system image via pixel flasher (no wipe) and then enable the modules and install Kirisakura. All in the active slot
[Google Pixel 6 Pro] dyval:
Alright. But I mean will my steps above work too?
[Google Pixel 6 Pro] 73sydney:
Similar here, i use the full rode warrior method though, for extra checking, before flashing the kernel:

https://xdaforums.com/t/december-5-...aven-all-relevant-links.4352027/post-86622159
[Google Pixel 6 Pro] linus207:
I don't see any reason why it wouldn't work ;)
[Google Pixel 6 Pro] abalam:
A question, when I wanna flash this kernel can this just be done or do I have to start clean and start with disable-verity
[Google Pixel 6 Pro] w_tapper:
not on pixel 6/6 pro
[Google Pixel 6 Pro] amritpal2489:
Is this kernel working on QPR2 now??
[Google Pixel 6 Pro] pakin1:
Can someone explain me how single developer is achieving better results with his kernel than entire google company?

What's pushing Google's back? I'm getting way way better thermals with this kernel, better battery life, faster charging, more responsive phone and more reliable notifications.

I bought my Pixel 6 on preorder( very bad idea btw) because I smashed my previous phone. I hated it since first(feeling like I was a free beta tester) week, but this kernel is changing everything.