Development [Kernel][21.03.2023][Android 13.0.0]Kirisakura 1.0.0_Raviantah for Pixel 6/Pro aka "RAVIOLE"

[amritpal2489]

There are sources for QPR Beta available, that´s not the problem.

Copy paste from another post in this thread where I already answered the question, why I don´t support dev-previews/betas:

No, I have no plans to support A13 beta or any dev-preview or beta firmware. It will be supported once it´s stable. I don´t have the time, desire and motivation to support it.
It all boils down to the fact that I enjoy doing what I´m doing here, I do it in my free time and share what I´m using myself with others so they can enjoy it with me and I want to release something that´s polished, extensively tested and stable.

Since that questions comes up from time to time:

I´m not comfortable releasing something I´m not running/testing extensively myself with loads of changes compared to the stock base.
I never felt the urge to do beta testing for companies just to run more recent software too.

I don´t have time to test, maintain and build that many compilations, let alone switching between Beta Firmware and Stable firmware on my phone for testing. It´s simply not possible, and I don´t want to release something that´s not extensively tested.
I think sometimes people don´t realize how much time goes into this aspect of my kernels projects alone.

Also try to see it that way:
Merging code updates takes time. Be it linux-stable, f2fs-stable, kernel/common, lrng updates, updates directly from Google or a lot of the features that are descrbied in the OP. Sometimes longer, sometimes shorter.
This kernel is now very very far from the stock base (compared to the other kernels available) as is also reflected in the OP. So while merging code updates will take time as there are many conflicts that need to be solved on my kernel. Even if the branches are somewhat similar I still need a lot of additional time to manage this aspect alone, not to speak of testing on my device to make sure nothing is broken.

There´s no longer just the kernel repo itself to manage. With the introduction of GKI, the kernel is split in several sub repos for different device specific drivers, touchscreen, wifi, uwb, nfc, bt, etc etc. Those needs to be managed too, as well as other repos from the build environment as they´re different between stable and beta.
Powerhal changes need to be monitored and adjusted each month too, as there might be differences between stable and beta as well.

Building takes time. Every compilation, for testing or release purposes takes about 15 minutes. Only building, not adjusting the code. Every release here needs 2 different builds for oriole/raven. Yes I can do something else during the compilation, but it´s still time I need to spend.



No there´s no telegram group. Everything you need is here on XDA. All information is in the first few posts. If you use the search function you´ll find even more I guess.

Your work is really appreciated.. Thanks for the clarification..

 

[HeeroML]

This doesn't work with grapheneOs or?

 

[capntrips]

This doesn't work with grapheneOs or?

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.

 

[chewy74]

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.

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?

 

[Freak07]

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?

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.

 

[HeeroML]

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.

it did bootloop, though i needed root for flashing it in the first place

 

[ada12]

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.

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 ).

 

[Rachid.Ala]

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 ).

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

 

[ada12]

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.

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 13

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

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 !

 

[dangambino]

wrong theead

 

[w_tapper]

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 13

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

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 !

i think it works. thank you!

edit: ITS BOOTLOOPING HELP

 

[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!

 

[gnabtib8]

Was 4.3.0 pulled? I cant download this release, is there issues with it

 

[phaino00]

Was 4.3.0 pulled? I cant download this release, is there issues with it

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://forum.xda-developers.com/t/...pixel-6-pro-aka-raviole.4358435/post-87697425

 

[MidnightDevil]

This may be a silly question, but may I flash this on t1b3 release? it's the latest factory release available.

 

[phaino00]

This may be a silly question, but may I flash this on t1b3 release? it's the latest factory release available.

It is a silly question...lol. It's not supported on betas per OP. It may work, but at one's own risk.

 

[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

 

[phaino00]

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

Flash the appropriate factory image without wiping data (remove -w from flash all file).

 

[boxemall]

I

Flash the appropriate factory image without wiping data (remove -w from flash all file).

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?

 

[phaino00]

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?

Yeah, if you are flashing stock from custom rom, you will have to wipe/format data. Some use swift backup for apps and data.