Development [Kernel][20.06.2022][Android 12] Kirisakura 2.0.9 for Asus ROG Phone 5 aka "Anakin"

[RicoMartins]

If you want to return to stock conditions it´s mentioned in the OP and the second post which partitions to restore.
Flash boot.img, dtbo.img and vendor_boot.img of the exact firmware you´re on. If you don´t have those, use payload extractor tool to extract them from your firmware file.


I´m sorry A11 is no longer supported and there´s no way to test for me what exactly happened to you.
If you flash a kernel you need to make sure you´re flashing it to a compatible firmware. If you run one of the "older" A11 firmwares 1.4.1 should work.

If you run one of the more recent A11 versions take a look here:

[Kernel][20.06.2022][Android 12] Kirisakura 2.0.9 for Asus ROG Phone 5 aka "Anakin"

Kirisakura-Kernel for the ROG Phone 5 Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Asus ROG Phone 5 aka Anakin. The ROG Phone line-up internal codenames are traditionally derived from Yedi-Characters of the Star Wars...

forum.xda-developers.com

and try to flash the kernel from here:

[Kernel][20.06.2022][Android 12] Kirisakura 2.0.9 for Asus ROG Phone 5 aka "Anakin"

Kirisakura-Kernel for the ROG Phone 5 Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Asus ROG Phone 5 aka Anakin. The ROG Phone line-up internal codenames are traditionally derived from Yedi-Characters of the Star Wars...

forum.xda-developers.com

If you flash the older kernel to more recent firmware you´ll crash and vice versa as well.

Hello, thank you, I saw this later and maybe for many ways to try I ended up needing to pass some more images and in the end format via recovery (which was also something I managed to return to the device after trying to twrp), but in the end resolved (I was using my son's device and created this account with his email too... I'm using the version that the Asus firmware col puts when returning to 11 , they say that on the A12 it is better optimized, but not for me, now less heating and more battery life. Not to mention the triggers bug that I don't have them anymore. Anyway thanks again, and IF you can invoke which version I can use I'm grateful I'm in WW_18.1220.2201.192.

 

[Freak07]

Hello, I would like to test your kernel on my brand new ROG Phone 5S but I have a few questions. Rooting will make me lose fingerprint capabilities? I've heard of other phones losing fingerprint calibration after root. Will I lose anything else forever? Does safety net fix still work? Anything that is not working on root or your kernel?
Currently my phone has frame drops on Call of Duty Mobile even on medium settings, overheating is not an issue as it doesn't even pass 40°C so I hope your kernel smoothes everything on the system.
Thanks a lot !

Would this help in lag and performance ? I play Call of Duty Mobile and suddenly there's frame drops even though temp doesn't go above 39 ºC

5S is only compatible with Android 12. Just a reminder

I don´t personally own a 5S, but other users confirmed it working so you should have no problems flashing if you follow the instructions.

Rooting doesn´t impact fingerprint scanner. The problem arises when people buy CN devices that have been converted to WW and messed up in the process. If persist partition gets messed up, the calibration might get lost. So first thing I would do if you decide to root is backup the persist partition once you´re being rooted. Google around, you should find guides for that.
Safetynet fix works at the moment, but google can flip a switch and it will stop working on all devices. That´s nothing specific to ROG Phones.
The only thing that does not work on my kernel is connecting a storage device that´s formatted via NTFS. That driver is proprietary and there´s no way to build it from source.

The kernel hasn´t anything to do with how asus regulates thermals. You can change the thermal profile by playing with the temperature slider in armoury crate.
Keep also in mind, thermal throttling is probably the reason why the phone doesn´t cross 39°C. If you allow for more performance and a higher thermal floor via armoury crate it will get hotter.

Hello, thank you, I saw this later and maybe for many ways to try I ended up needing to pass some more images and in the end format via recovery (which was also something I managed to return to the device after trying to twrp), but in the end resolved (I was using my son's device and created this account with his email too... I'm using the version that the Asus firmware col puts when returning to 11 , they say that on the A12 it is better optimized, but not for me, now less heating and more battery life. Not to mention the triggers bug that I don't have them anymore. Anyway thanks again, and IF you can invoke which version I can use I'm grateful I'm in WW_18.1220.2201.192.

If you only flash the kernel, restoring the images I mentioned will be enough.
If something else got messed up, you might need to restore the phone to stock completely. But I´m glad you got it sorted.

My triggers work fine on A12.

If you used the firmware to return from A12 to A11 from the support page you´re on WW-18.0840.2201.226 though. You shouldn´t cross flash something from different firmwares, as that can lead to issues. So if you flashed parts of .226 A11 and parts of .192 A11 that´s not really good....

I think the kernel for .192 A11 firmware was 1.4.0. Keep in mind the A11 kernel is only working correctly on standard ROG 5. If I remember correctly 1.4.1 should have worked too.

 

[RicoMartins]

5S is only compatible with Android 12. Just a reminder

I don´t personally own a 5S, but other users confirmed it working so you should have no problems flashing if you follow the instructions.

Rooting doesn´t impact fingerprint scanner. The problem arises when people buy CN devices that have been converted to WW and messed up in the process. If persist partition gets messed up, the calibration might get lost. So first thing I would do if you decide to root is backup the persist partition once you´re being rooted. Google around, you should find guides for that.
Safetynet fix works at the moment, but google can flip a switch and it will stop working on all devices. That´s nothing specific to ROG Phones.
A única coisa que não funciona no meu kernel é conectar um dispositivo de armazenamento formatado via NTFS. Esse driver é proprietário e não há como construí-lo a partir do código-fonte.

O kernel não tem nada a ver com a forma como a asus regula as térmicas. Você pode alterar o perfil térmico brincando com o controle deslizante de temperatura na caixa do arsenal.
Lembre-se também de que a aceleração térmica é provavelmente a razão pela qual o telefone não ultrapassa os 39°C. Se você permitir mais desempenho e um piso térmico mais alto através da caixa do arsenal, ficará mais quente.



Se você apenas atualizar o kernel, restaurar as imagens que mencionei será suficiente.
Se algo mais deu errado, talvez seja necessário restaurar completamente o estoque do telefone. Mas fico feliz que tenha resolvido.

Meus gatilhos funcionam bem no A12.

Se você usou o firmware para retornar de A12 para A11 da página de suporte, você está no WW-18.0840.2201.226. Você não deve cruzar o flash de diferentes firmwares, pois isso pode levar a problemas. Então, se você exibiu partes de .226 A11 e partes de .192 A11, isso não é muito bom....

Acho que o kernel do firmware .192 A11 era 1.4.0. Tenha em mente que o kernel A11 está funcionando corretamente apenas no ROG 5 padrão. Se bem me lembro, o 1.4.1 deveria ter funcionado também.ok, thanks I really feel my 5S much better on the A11, apart from the appearance of the 12 that I didn't like at all... I'll stay like that for now, if a next update convinces me I'll do it.

 

[Lossani]

5S is only compatible with Android 12. Just a reminder

I don´t personally own a 5S, but other users confirmed it working so you should have no problems flashing if you follow the instructions.

Rooting doesn´t impact fingerprint scanner. The problem arises when people buy CN devices that have been converted to WW and messed up in the process. If persist partition gets messed up, the calibration might get lost. So first thing I would do if you decide to root is backup the persist partition once you´re being rooted. Google around, you should find guides for that.
Safetynet fix works at the moment, but google can flip a switch and it will stop working on all devices. That´s nothing specific to ROG Phones.
The only thing that does not work on my kernel is connecting a storage device that´s formatted via NTFS. That driver is proprietary and there´s no way to build it from source.

The kernel hasn´t anything to do with how asus regulates thermals. You can change the thermal profile by playing with the temperature slider in armoury crate.
Keep also in mind, thermal throttling is probably the reason why the phone doesn´t cross 39°C. If you allow for more performance and a higher thermal floor via armoury crate it will get hotter.



If you only flash the kernel, restoring the images I mentioned will be enough.
If something else got messed up, you might need to restore the phone to stock completely. But I´m glad you got it sorted.

My triggers work fine on A12.

If you used the firmware to return from A12 to A11 from the support page you´re on WW-18.0840.2201.226 though. You shouldn´t cross flash something from different firmwares, as that can lead to issues. So if you flashed parts of .226 A11 and parts of .192 A11 that´s not really good....

I think the kernel for .192 A11 firmware was 1.4.0. Keep in mind the A11 kernel is only working correctly on standard ROG 5. If I remember correctly 1.4.1 should have worked too.

Thanks I finally decided to root and install your kernel. I come from ASUS ROG Phone 3 with your kernel so I wanted to give it a try on this phone. So far everything seems ok, even more fluid than before apparently. Need to test more. Also 5S actually came with Android 11 so I don't know what you mean by only compatible with Android 12.
About the fingerprint sensor, thanks for reminding to make a backup. I owned a Red Magic phone and fingerprint calibration was lost when rooting but finally recovered it after "calibration tool" succeeded.
Do you know if there's a config option to make FPS fixed? I try to use GLTools for more FPS but system limits it on 60 FPS on some game modes while on others it's 120 FPS as expected. Is it something related to your kernel? Seems like the system limits to 60 FPS whenever it wants.

Thanks for your effort!

 

[Rom1995]

Does the kernel support overlayfs? Only using it cause i want to upgrade the stock graphics driver. Was working fine with zenfone 6 using your kernel just not working with ROG 5.

 

[Freak07]

Does the kernel support overlayfs? Only using it cause i want to upgrade the stock graphics driver. Was working fine with zenfone 6 using your kernel just not working with ROG 5.
View attachment 5653365

I just checked and overlayfs is enabled in the defconfig.
Does it work on the stock kernel?

 

[Rom1995]

I just checked and overlayfs is enabled in the defconfig.
Does it work on the stock kernel?

It doesnt work on stock kernel either but works on zenfone 6 stock kernel.

 

[Freak07]

It doesnt work on stock kernel either but works on zenfone 6 stock kernel.

Unfortunately that doesn't help me much. If i find time I'll look into it. Maybe that module needs to be updated for a12 or 5.4 based devices/kernels. I'll see if I find anything

 

[DjalilovSunnat]

ROG 5 A12 last version. I tried change the sound parameters but not working. After reboot it returns to standard parameters. May be my system not support rw/rw? Sorry for my bad English.

 

[Lossani]

Unfortunately that doesn't help me much. If i find time I'll look into it. Maybe that module needs to be updated for a12 or 5.4 based devices/kernels. I'll see if I find anything

Is there a config in your kernel to make FPS at a fixed number? Or is it already always at 120 FPS and not variable?

 

[Freak07]

ROG 5 A12 last version. I tried change the sound parameters but not working. After reboot it returns to standard parameters. May be my system not support rw/rw? Sorry for my bad English.

I just tried the feature and it works as expected for me.

The kernel has nothing to do with the values getting set on boot, what kernel manager app you´re using is responsible for this. You might need to set a longer timer for the values to get applied after boot. I tried with EXKM and the values stick after a reboot.

Is there a config in your kernel to make FPS at a fixed number? Or is it already always at 120 FPS and not variable?

Thanks I finally decided to root and install your kernel. I come from ASUS ROG Phone 3 with your kernel so I wanted to give it a try on this phone. So far everything seems ok, even more fluid than before apparently. Need to test more. Also 5S actually came with Android 11 so I don't know what you mean by only compatible with Android 12.
About the fingerprint sensor, thanks for reminding to make a backup. I owned a Red Magic phone and fingerprint calibration was lost when rooting but finally recovered it after "calibration tool" succeeded.
Do you know if there's a config option to make FPS fixed? I try to use GLTools for more FPS but system limits it on 60 FPS on some game modes while on others it's 120 FPS as expected. Is it something related to your kernel? Seems like the system limits to 60 FPS whenever it wants.

Thanks for your effort!

The kernel can´t change the FPS a game runs on. If a game falls back to 30fps or 60fps, it´s other parts of the system handling that. Some games are also hardcoded to run at 30 or 60fps.

The only thing I can change via kernel is providing an option so it´s possible to force the panel itself to refresh at 120FPS or 144FPS, but the game will still render at 60FPS or whatever the game decides to. So you gain nothing except waster power.

 

[Lossani]

I just tried the feature and it works as expected for me.

The kernel has nothing to do with the values getting set on boot, what kernel manager app you´re using is responsible for this. You might need to set a longer timer for the values to get applied after boot. I tried with EXKM and the values stick after a reboot.



The kernel can´t change the FPS a game runs on. If a game falls back to 30fps or 60fps, it´s other parts of the system handling that. Some games are also hardcoded to run at 30 or 60fps.

The only thing I can change via kernel is providing an option so it´s possible to force the panel itself to refresh at 120FPS or 144FPS, but the game will still render at 60FPS or whatever the game decides to. So you gain nothing except waster power.

Yes how can I force panel to refresh at always 120/144 FPS? Gltools is supposed to break the FPS limiter on game and it worked on Red Magic but now I think the panel is stopping it. Where can I force panel to fixed 120/144?

 

[Freak07]

Yes how can I force panel to refresh at always 120/144 FPS? Gltools is supposed to break the FPS limiter on game and it worked on Red Magic but now I think the panel is stopping it. Where can I force panel to fixed 120/144?

You can´t on your own. If game genie doesn´t work to set the refresh rate, I will need to implement an option to the kernel.
But why would you want that? It won´t make a difference if the game still renders at 60fps, just the panel refreshes higher. You won´t get more FPS in the game.

 

[Lossani]

You can´t on your own. If game genie doesn´t work to set the refresh rate, I will need to implement an option to the kernel.
But why would you want that? It won´t make a difference if the game still renders at 60fps, just the panel refreshes higher. You won´t get more FPS in the game.

I mean it works. Game is supposed to run at 90 FPS max on ROG Phone but with GLTools Root App it makes the game work on 120 FPS but thats somehow thats the new cap it is supposed to let it run on 144 but panel for some reason is stuck. On Nubia phone I was able to bypass game engine FPS limit and play at 165 Hz max (showed in FPS meter) but cant on ROG I thought it was something related to Kernel or Game Genie automatically limiting FPS even after GLTools disabled that limit in game.
I suspect that is the case because when I start a match of specific mode the game starts at 60 FPS and after a few seconds it suddenly jumps to 120 FPS but only at some game modes. On Battle Royale it would lock it back. Even on game lobby. Normally it would run only at 30 FPS on any phone in game lobby but with GLTools limit is removed but phone would still limit to 60 FPS somehow.

 

[Freak07]

I mean it works. Game is supposed to run at 90 FPS max on ROG Phone but with GLTools Root App it makes the game work on 120 FPS but thats somehow thats the new cap it is supposed to let it run on 144 but panel for some reason stuck. On Nubia phone I was able to bypass game engine FPS limit and play at 165 Hz max (showed in FPS meter) but cant on ROG I thought it was something related to Kernel or Game Genie automatically limiting FPS even after GLTools disabled that limit in game.
I suspect that is the case because when I start a match the game starts at 60 FPS and after a fer seconds it suddenly jumps to 120 FPS but only at some game modes. On Battle Royale it would lock it back. Even on game lobby. Normally it would run only at 30 FPS on any phone in game lobby but with GLTools limit is removed but phone would still limit to 60 FPS somehow.

I´ll see if I can implement an option to override the panel FPS. then you can try.

 

[Lossani]

I´ll see if I can implement an option to override the panel FPS. then you can try.

That would help a lot. Thank you!!

 

[mos28888]

Did anyone use version 2.0.9? is it lower what's the temperature of you phone if you use in idle,normal and x-mode?

 

[Lossani]

I´ll see if I can implement an option to override the panel FPS. then you can try.

Besides a switch to override panel FPS is there any line code to force it permanently? I would like to test around and compile your kernel but I don't know where I can change to force it at least for now.
Thanks!

 

[Freak07]

Besides a switch to override panel FPS is there any line code to force it permanently? I would like to test around and compile your kernel but I don't know where I can change to force it at least for now.
Thanks!

so I removed 60fps from the panel.

Flash this zip.
Afterwards the option for 60fps should disappear from settings. See if that makes a difference for what you´re trying to achieve.

 

[Lossani]

so I removed 60fps from the panel.

Flash this zip.
Afterwards the option for 60fps should disappear from settings. See if that makes a difference for what you´re trying to achieve.

Yes so that seems to be the problem:

The panel or software was limiting to 60 FPS, now it's limited to 120 FPS. Even though I override the limit up to 144 Hz should be allowed.
Is there any way to add a custom switch?

Thank you