Related
Hi all,
I want to install a kernel module on Galaxy S. My kernel version is 2.6.35.7-I9000XXJVP. Am not sure if this is a stock kernel/ rom. Is it a stock?
I think the problem is module loading/ unloading is not enabled in the default kernel, how to enable this option? will puling the current .config, enabling module support option and pushing back will work? can this harm the device?
what is the best(easiest) way to achieve kernel module installing support?
So I decided to release a kernel I did for the Telegram group. It's based on Nougat latest CAF May Updated, and is Oreo ready.
It will auto install magisk so you are rooted.
Jason_Miui_Nougat_Kernel: https://www.androidfilehost.com/?fid=818222786056029778
Jason_Nougat_Anykernell: https://www.androidfilehost.com/?fid=962339331458992566 (Use Anykernel for AOSP or MIUI Install)
Kernel Sources
https://github.com/travismills82/android_kernel_xiaomi_sdm660/commits/miui-oreo
Bugs:
You tell me
Features:
Enable CIFS/SMB support
Enable F2FS support
Enable NTFS support
Added fsync on/off support.
+ many more changes check commits on github
Your kernel is for:
Miui?
Custom Rom?
Has it
KCal support?
ExFat/NTFS support? @travis82
telegram group link please?
What additional features do you provide? Apart from May security patches, of course. I don't see many commits from the base, but still I'm currently too lazy to browse and understand the diff
dissidius said:
telegram group link please?
Click to expand...
Click to collapse
there you go
https://t.me/joinchat/GJTWU0faKQew7fwn37Y1fw
It does not work for miui8.4.26 dev，device always boots into twrp。
Flashed at Mi-Globe 8.4.26 without problems.
No kcal support.:crying::crying::crying: @travis82
dzidexx said:
Flashed at Mi-Globe 8.4.26 without problems.
No kcal support.:crying::crying::crying: @travis82
Click to expand...
Click to collapse
Why do you need KCAL so bad why is this life or death for you? Doesn't your display show colors correctly?
I love Vomer DeepReach.
https://forum.xda-developers.com/oneplus-2/general/kernel-adiutor-kcal-color-profiles-t3382086
But I can live without it.
:laugh:
device always boots into twrp
please add kcal profiles. It is making screen a lot better, also rom is not booting, bootlop into twrp - lastest miglobe
Whats the tested MIUI version?
it works with Xiaomi.Eu 9.5 stable?
Can't boot after flashing kernel#2, booting only to twrp.
(all methods tried, reboot system in twrp, power off & on).
Kernel#1 didn't try today.
Miui.eu stable 9.5.8.0 NCHCNFA. @travis82
Added anykernel install so you MIUI and AOSP users can use the same kernel.
Installed the anykernel version, but I can't get that high mem score (roughly the same as stock). This is on MIUI EU dev 8.4.26. And oh, at the end of installation I get "unable to unmount" error but I think that's fine.
leledumbo said:
Installed the anykernel version, but I can't get that high mem score (roughly the same as stock). This is on MIUI EU dev 8.4.26. And oh, at the end of installation I get "unable to unmount" error but I think that's fine.
View attachment 4502767
Click to expand...
Click to collapse
Did you stick at this kernel? How is the battery and daily usage?
Dan_Jacques said:
Did you stick at this kernel? How is the battery and daily usage?
Click to expand...
Click to collapse
No, I'm back to stock with MIUI EU 8.10.11.
lowspecmoto
G-Drive Downloads Portal: [Downloads]
Modified Kernel Source: [Source Code]
Stock ROM also supported!
Decrypting /data not required
Install:
Unlock Bootloader: [Guide]
Flash TWRP: [TWRP 3.2.0]
TWRP -> Install -> Flash Zip-> Select ZIP
Supported Devices
XT1924-3 Moto E5 Play (James)
XT1924-4 Moto E5 (Nora)
XT1924-7 Moto E5 Plus (Hannah)
Features:
Qualcomm QHMP Enabled
One kernel for Stock & ROMs
Supports Treble-based ROMs
WireGuard VPN Support
Custom Wakelock Blockers
Added Dynamic Fsync
Added Frandom Support
Added Zen IO Scheduler
Added UKSM
Disabled DM_VERITY
Disabled Forced File Encryption
Disabled RKP
Enabled CIFS Filesystem Support
Enabled ISO9660 Filesystem Support
Enabled JOLIET Filesystem Support
Enabled Lockup Detector
Enabled LZ4 support
Enabled NFS Filesystem Support
Enabled NTFS Support
Enabled UDF Filesystem Support
Bugs:
None
BUILD INFORMATION
Built with: Linaro GCC 7.1.1 Toolchain [2017.05.10]
Installer Base: AnyKernel2 [Github]
Kernel Base: pie-9.0.0-release-ppk [Pie]
Linux Version: 3.18.115 [Experimental]
XDA:DevDB Information
lowspecmoto, Kernel for the Moto E5
Contributors
rbheromax
Kernel Special Features:
Version Information
Status: Stable
Created 2018-12-24
Last Updated 2018-12-31
Changelog::
r8 - Rebase kernel using Moto Pie Release kernel
r6 - Bug fixes, Hannah Configuration only [XT1924-7]
r4 - Support James/Nora Configurations
and this one ??
I'll go to the moon with ya OP. Fire that B up and pass it my way. Still use my v20s as my daily phones plus my moto e5 plus has a cracked screen glass so it's the perfect experimental piece.
Sent from my Motorola moto e5 plus using XDA Labs
dropped the alpha! happy holidays guys ???
I have MetroPCS version and I can't get this to work. I was hoping it would help with my encryption issue I can decrypt my phone but it always encrypts itself afterwards.. anyone else get this to work?
foszuled said:
I have MetroPCS version and I can't get this to work. I was hoping it would help with my encryption issue I can decrypt my phone but it always encrypts itself afterwards.. anyone else get this to work?
Click to expand...
Click to collapse
I wasn't aware of how it runs on stock w encrypt. I'll do some testing and make it compatible. ?
rbheromax said:
I wasn't aware of how it runs on stock w encrypt. I'll do some testing and make it compatible.
Click to expand...
Click to collapse
Sorry I should've been clearer.. I'm on metro PC's I have the play version I'm running resurrection remix. I'm rooted obviously.. when I flash the kernel with twrp it's successful but when I reboot it fails..
foszuled said:
Sorry I should've been clearer.. I'm on metro PC's I have the play version I'm running resurrection remix. I'm rooted obviously.. when I flash the kernel with twrp it's successful but when I reboot it fails..
Click to expand...
Click to collapse
okay if you have the e5 play, thats a msm8917 (sd425) soc. the device-tree files in the boot.img i posted renders it incompatible because it expects msm8937 (sd430). the kernel is compatible, the extra "meta"-ish data isnt.
can you pm me ? i want to send you a test zip that'll be configured for e5 play also
Support added for James (Moto E5 Play). If your device doesn't work, mention here, I'll post a new zip supporting your device. All Moto E5 devices WILL be supported in the end. Also, Please report bugs, I'll be ironing out everything asap
https://drive.google.com/file/d/1nqk9MxysKmhgsS9WK6BRw9XeTZNAlC7o/view?usp=drivesdk
Bug with video play
I have a E5 Plus Hannah m8917_06.10.05.43r hannah_Latam_cust , Oreo 8.0 stock , opp27.91-25, when i tryed to watch video they dont play, every apk with have video dont work and when i tried to uninstall app it fails.
Blackteus said:
I have a E5 Plus Hannah m8917_06.10.05.43r hannah_Latam_cust , Oreo 8.0 stock , opp27.91-25, when i tryed to watch video they dont play, every apk with have video dont work and when i tried to uninstall app it fails.
Click to expand...
Click to collapse
can you provide any logs? A logcat can usually help me pinpoint an issue
After installing this kernel camera app says not enough space or storage after taking a picture even tho I have 4 gigs left, any fix?
SOU55 said:
After installing this kernel camera app says not enough space or storage after taking a picture even tho I have 4 gigs left, any fix?
Click to expand...
Click to collapse
currently looking into this. it seems to be a stock rom issue and pixel experience p does it too. can you collect logs? this will help me narrow down things really fast
rbheromax said:
currently looking into this. it seems to be a stock rom issue and pixel experience p does it too. can you collect logs? this will help me narrow down things really fast
Click to expand...
Click to collapse
I dont think i can collect logs, i did a factory reset not sure if theyre saved still and keeps doing the same thing, all apps say no space no enough memory, if i flash the original kernel would that help ?
I installed your James compatible kernel on.my xt1921-5 Moto E5 Play and everything is working fine. The Zen I/O Scheduler is a nice addition and seems to provide some noticeable improvements in responsiveness. I am using Kernel Adiutor-Mod for my kernel control app.
Nice work OP. Thank you. :good:
LenovoTech said:
I installed your James compatible kernel on.my xt1921-5 Moto E5 Play and everything is working fine. The Zen I/O Scheduler is a nice addition and seems to provide some noticeable improvements in responsiveness. I am using Kernel Adiutor-Mod for my kernel control app.
Nice work OP. Thank you. :good:
Click to expand...
Click to collapse
let me know of any bugs or feature requests
updates are going up today
rbheromax said:
let me know of any bugs or feature requests
updates are going up today
Click to expand...
Click to collapse
Cool. Thank you @rbheromax. I'm very happy to see a dev dedicated to this device & its variable chipsets. Great work. I love the Zen i/o scheduler.
LenovoTech said:
Cool. Thank you @rbheromax. I'm very happy to see a dev dedicated to this device & its variable chipsets. Great work. I love the Zen i/o scheduler.
Click to expand...
Click to collapse
New links up, enjoy ?
rbheromax said:
New links up, enjoy ?
Click to expand...
Click to collapse
Nice. I'm flashing now
This is the stock kernel that ships with glassrom (or will ship with it)
5g variants are not yet supported
It is based off kirisakura kernel with additional hardening from my side.
You get this:
All the features from kirisakura kernel
Removed qualcomm's rmnet drivers
COMPAT_VDSO is disabled to enable full vDSO ASLR
KSPP patches have been applied
Clang control flow integrity (https://source.android.com/devices/tech/debug/cfi)
Backward edged control flow integrity:
Strong protections enforced by shadowcallstack (https://source.android.com/devices/tech/debug/shadow-call-stack)
Weak protections enforced by adding stack canaries to everything and ensuring ASLR is of a decent enough quality
Compiled with -O3 and Polly for maximum performance
Wireguard driver has been removed
AVB depends on the ROM. Flashing it on glassrom/oxygenos will definitely cause it to boot with enforcing AVB. On other ROMs this shouldn't happen
Selinux forced enforcing patch from Samsung
Yama is enabled and set to SCOPE_NO_ATTACH
Uses sdfat driver to provide vfat and exfat drivers
Todo:
Port Linux-hardened patch
fix fingerprint on oos
Notes:
Flashing it on oxygenos will break dt2w
Flashing the kernel regardless of ROM or device combination will break twrp ramdisk boot. The only way to boot twrp is using fastboot boot, installing it to the ramdisk will always lead to a kernel panic. This is not a bug and will not be fixed
Download: see release post https://forum.xda-developers.com/showpost.php?p=81105101&postcount=8
Source:
https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
Donations:
Most of the hard work was done by @Freak07 so check out his thread and buy him a coffee
anupritaisno1 said:
This is the stock kernel that ships with glassrom (or will ship with it)
5g variants are not yet supported
It is based off kirisakura kernel with additional hardening from my side.
You get this:
All the features from kirisakura kernel
Removed qualcomm's rmnet drivers
COMPAT_VDSO is disabled to enable full vDSO ASLR
KSPP patches have been applied
Clang control flow integrity (https://source.android.com/devices/tech/debug/cfi)
Backward edged control flow integrity:
Strong protections enforced by shadowcallstack (https://source.android.com/devices/tech/debug/shadow-call-stack)
Weak protections enforced by adding stack canaries to everything and ensuring ASLR is of a decent enough quality
Compiled with -O3 and Polly for maximum performance
Wireguard driver has been removed
AVB depends on the ROM. Flashing it on glassrom/oxygenos will definitely cause it to boot with enforcing AVB. On other ROMs this shouldn't happen
Selinux forced enforcing patch from Samsung
Yama is enabled (does nothing significant for now)
Todo:
Set Yama to level 3 (breaks magisk)
Port Linux-hardened patch
Notes:
Flashing it on oxygenos will break dt2w
Flashing the kernel regardless of ROM or device combination will break twrp ramdisk boot. The only way to boot twrp is using fastboot boot, installing it to the ramdisk will always lead to a kernel panic. This is not a bug and will not be fixed
Download:
https://mirror.apexcdn.net/files/glassrom/unsigned.zip
Source:
https://github.com/GlassROM-devices/android_kernel_oneplus_sm8150
Click to expand...
Click to collapse
Fingerprint is broken on oos
Kaz205 said:
Fingerprint is broken on oos
Click to expand...
Click to collapse
Yeah sorry about that. I'll make a version for oos soon
I did test it for a short while on oos but did not test it enough
Merged in the latest kernel from kirisakura git and also merged in 4.14.156
It boots fine but I don't have a good internet connection to be able to upload it
Will do so soon
anupritaisno1 said:
Merged in the latest kernel from kirisakura git and also merged in 4.14.156
It boots fine but I don't have a good internet connection to be able to upload it
Will do so soon
Click to expand...
Click to collapse
Thanks! Does this one work with OOS?
MrGimpGrumble said:
Thanks! Does this one work with OOS?
Click to expand...
Click to collapse
I eventually plan to stop supporting oos
OOS is proprietary for one and such a system is almost never secure. And if you don't believe me just look at their past vulnerability announcements. Almost all oxygenos vulnerabilities come from the fact that oneplus finds loopholes around Google's CTS. Who knows what other holes they've opened up that Google forgot to add checks for
Further, oos has many "memory optimisation" drivers that directly try to access ram and break most of the security features I'm implementing. Most custom ROMs do not have these and the drivers can be safely disabled
I will also add that this kernel is almost functionally identical with kirisakura kernel. Yes I might merge upstream slightly faster but other than that there is no difference that you would notice. The only difference is that I'm enabling all the security features that must be enabled - especially CFI and shadowcallstack which come standard on any Google pixel device
As for wireguard I just think running a VPN in kernel space is a very bad idea. Not to mention I have confirmed that on Android the tunnel leaks ipv6 traffic if you're not careful and no, disabling ipv6 is not the solution. The userspace go implementation is much safer and I mean it. The userspace implementation almost never leaks ipv6 traffic. Not to mention Go is a much safer language than C
okay new update is in the attachments
changes: linux 4.14.156
upstreamed to oos open beta 6 (doesn't mean fixed fingerprint yet)
upstreamed wifi driver and audio driver to latest caf tag (LA.UM.8.1.r1-12200-sm8150.0)
yama is now at level 3
all upstream changes from kirisakura. except for wake gestures as lineagehw seems to already have those
oos users should disable smart boost from settings
okay new build is here
changelog:
linux 4.14.157
upstreamed sdfat driver
fixed a weird kernel panic that happened on anything other than oxygenos when the device was fast charging from a very low battery
anupritaisno1 said:
okay new build is here
changelog:
linux 4.14.157
upstreamed sdfat driver
fixed a weird kernel panic that happened on anything other than oxygenos when the device was fast charging from a very low battery
Click to expand...
Click to collapse
work on pa?
ryshd296 said:
work on pa?
Click to expand...
Click to collapse
Please test it and let me know
It should boot on any ROM that can enforce selinux
anupritaisno1 said:
Please test it and let me know
It should boot on any ROM that can enforce selinux
Click to expand...
Click to collapse
This sent me into an immediate Qualcomm crash dump upon booting on both stock OOS and Omni for OnePlus 7t global variant.
Previous releases as well, not just the newer release.
scott.hart.bti said:
This sent me into an immediate Qualcomm crash dump upon booting on both stock OOS and Omni for OnePlus 7t global variant.
Previous releases as well, not just the newer release.
Click to expand...
Click to collapse
Please duplicate the crashdump message exactly
Especially send the "PC at" line and the error message if present
If the error message is blank please mention that it is
If you get a PC at __cfi_check_fail message please mention this
@scott.hart.bti still waiting for your response
Please send the crash log if possible
Do i need ma
gisk companion for this?
psychemisha said:
Do i need ma
gisk companion for this?
Click to expand...
Click to collapse
No you don't
However somewhere around ob4 maintaining compatibility with oxygenos became next to impossible without breaking custom ROMs
I think most users are still on OOS. If not I can just release builds for custom ROMs
Costum plz
is the development stopped?
Kirisakura-Kernel for the Asus Rog Phone 2
Hello everyone,
I proudly present Kirisakura-Kernel made for the Asus Rog Phone 2 aka Yoda!
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this may be one of the only 4.14 msm kernels with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
If that got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 855+ that´s built into the Asus Rog Phone 2.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use to build their own kernel additions on top, for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst others to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 11 and intended for use on Asus Stock Rom
- compiled with Clang 13.0.1 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.14.243
- CAF-Upstream merged
- Link the kernel with LLD and use KASLR
- include all important fixes/improvements from kernel/common
- F2FS implementation updated to latest state of kernel/common and kernel.org maintained by Jaegeuk Kim.
- Safety Net patches are included -> Kernel passes Safety Net
- Flashing the kernel will keep root!
- Sweep to sleep functionality
- Flashable via EXKM and FKM on a rooted system!
- specifically tuned EAS for the Asus Rog Phone 2
- removed nolog usage, remove rtb logging from the kernel
- remove selinux auditing from kernel for lower overhead
- remove IPC logging from the kernel
- Anykernel zip is based on the all new Anykernel3 release from @osm0sis
- option for 144hz refresh rate (Android 10 only)
- option to improve visibility in dark scenes
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- Dynamic Stune Boost to inflate task utilization and not overload cores on interaction (thanks to @RenderBroken and @joshuous )
- improved schedutil governor
- updates from kernel/common
CPU related features:
- Power saving workingqueues enabled by default
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- vDSO 32 patches to improve 32-bit performance
- arm64: lse: Prefetch operands to speed up atomic operations (thanks to @kdrag0n )
File System related features:
- F2FS implementation updated to latest state of kernel/common and F2FS-Mainline on kernel.org maintained by Jaegeuk Kim.
- Include rapid GC by @arter97 ( best thing is to read the commit description linked here. I compared GC on stock google f2fs, upstreamed f2fs and f2fs with rapid GC. Rapid GC is the most effective, followed by upstreamed f2fs.)
- adapt F2FS to be inline with Pixel 4s code from Google, which is also directly maintained by Jaegeuk Kim
- include a few F2FS fixes from the Pixel 4 kernel
- include optimizations to UFS-Driver from Pixel 4
- various improvements to FS-Performance from the Pixel 4
- f2fs fix to prevent data loss in case of sudden power failure
GPU related features:
- Update GPU driver to latest CAF state
- remove debugging and non-sd855+ specific code from the GPU driver
- introduce low priority worker thread to improve performance in UI-critical situations
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
Memory related features:
- Speculative Page Faults (1. 2) (CAF default)
- enabled per process reclaim (CAF default)
- Fix various memory leaks in different subsystems
- improved mm with patches from latest mainline
- various other changes from mainline
- included zstd and lz0-rle as options for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- allow swappiness up to a value of 200
- remove unused mem regions to free more RAM (thanks to @kdrag0n )
Security related features:
- Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.14 kernel/common and Pixel 4 Kernel
- Shadow Call Stack ported from 4.14 kernel/common and Pixel 4 Kernel
- enable init_on_alloc for even more security, more information can be found in the commit message
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled
- includes new bbr2
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
Other features:
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- remove VLAs from the kernel (more info)
- add support for steam controller
- add support for nintendo switch controller
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
- fix CFI violations
- add ramoops/pstore support (thanks @luca020400)
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- a backup of boot.img and dtbo.img to be able to restore to stock. you should be able to do this easily via TWRP.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest Asus Firmware
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img and dtbo.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to use latest Magisk stable. (not the latest canary!)
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP (haven´t tested TWRP myself as I don´t need it) and do a full reboot.
4. Flash the kernel again. This step is needed because flashing the kernel disables verity on vendor in order to modify two files. Disabling verity takes a reboot. Flashing the second time allows the two files to be changed correctly. This step is necessary if you flashed a firmware update. (This step should not be necessary when updating my kernel, if you are already running it, but if you want to be on the safe side just flash it twice)
5. Reboot and profit. It will take around 15 seconds for the kernel and the system to execute all changes done by flashing the kernel.zip. After 15 seconds 120fps will kick in, if you use 120fps setting!
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=303784
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9
1.0.0 Initial Release
1.0.2 https://forum.xda-developers.com/showpost.php?p=81389411&postcount=33
Android 10
2.0.0 https://forum.xda-developers.com/showpost.php?p=82238713&postcount=141
2.1.0 https://forum.xda-developers.com/showpost.php?p=82317211&postcount=191
2.6.0 https://forum.xda-developers.com/showpost.php?p=82495531&postcount=252
2.6.2 https://forum.xda-developers.com/showpost.php?p=82560081&postcount=261
2.6.4 https://forum.xda-developers.com/showpost.php?p=82602927&postcount=267
2.7.2 https://forum.xda-developers.com/showpost.php?p=82834055&postcount=281
2.7.5 https://forum.xda-developers.com/showpost.php?p=82837791&postcount=285
2.9.0 https://forum.xda-developers.com/showpost.php?p=83100663&postcount=306
3.0.6 https://forum.xda-developers.com/showpost.php?p=83526987&postcount=391
3.1.0 https://forum.xda-developers.com/showpost.php?p=83606511&postcount=406
3.1.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84124933
3.1.5 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84617449
3.2.0 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84717691
3.2.1 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-84799241
3.2.2 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85145887
3.2.3 https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-85431627
Android 11
1.0.0_R https://forum.xda-developers.com/t/...us-rog-phone-2-aka-yoda.4028237/post-86201183
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee
If you like my work: http://paypal.me/freak07
Credits:
Asus for the Rog Phone 2
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help too
@topjohnwu for magisk!
@osm0sis for anykernel!
XDA:DevDB Information
Kirisakura Kernel, Kernel for the ASUS ROG Phone II
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_Yoda
F.A.Q:
Question: Why does the kernel version show as "unavailable" in settings after flashing it.
Answer: Asus does not allow for custom kernel names in their settings. Use a kernel manager to check the kernel version.
Question: Is root preserved when flashing this kernel?
Answer: Yes the Anykernel Zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img as well as dtbo.img from matching firmware you are on and flash the extracted boot.img via fastboot.
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
android-tools/guides/proper_bug_reporting.txt at main · nathanchance/android-tools
Publicly available Android stuff. Contribute to nathanchance/android-tools development by creating an account on GitHub.
github.com
and one more for me
Wow!!! Awesome! Plans for kcal in the future?
Thank you so much for giving me a reason to unlock the bootloader. Finally am happy to see development for the device and that too from a well known developer ???? cheers mate and a very happy new year.
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
I love your work bro keep this devlopment continue
All rog2 user support your hardwork ,
And more developer will come after seeing your hardwork
a5he said:
Can I flash Android 10 beta fota file to my cn version phone using this recovery?
Click to expand...
Click to collapse
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
flash the boot.img extracted from the android 10 beta firmware via fastboot.
Kernel is made for Android Pie as stated in the OP.
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
mohammed510 said:
Welcome bro and thanks for the first rog 2 custom kernel.. ?
After flashing in twrp it says i should flash companion magisk module. Is there one yet?
Click to expand...
Click to collapse
Oh that’s a remnant of another kernel in the flashing script.
No there is none needed. I’ll remove that message in the next release!
thanks for the hint!
You just gave me a reason to unlock my bootloader and go back to Pie
What a day! Thanks a lot @Freak07! I'm happy for you being around!
Cheers,
anthonws.
sakamaki izayoi said:
please help..now my device stuck and keep looping in bootloader mode after trying to flash this kernel on Android 10 beta fota..and i cant reboot into twrp recovery and system..
Click to expand...
Click to collapse
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Very thanks
Please work on power saving and governor
Thank you for joining the ROG 2 Forums @Freak07
apollo3x said:
Extract the boot.img from Update and flash it under .img in twrp.
Goodluck
Click to expand...
Click to collapse
How to extract the Payload file of Android 10 FOTA?
The current Payload dumper doesn't support it.
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Mohamad313 said:
Very thanks
Please work on power saving and governor
Click to expand...
Click to collapse
avivv said:
Thank you so much for your hard work, I can't wait for you to make an version for Android 10 , hopefully once we have a custom kernel we can finally enjoy the 6000 mah battery
Click to expand...
Click to collapse
No idea about Android 10, but I’m enjoying the 6000mah on Pie already. That Android 10 build floating around is no finished or final piece of software.
I’ll attach my current stats from this morning.
No extensive gaming, mainly browsing, exploring the phone, massaging, videos, some calls etc.
but all on constant 120hz.
Wow that's great stats, when I had android 9 I the battery life was worst than I expected, if there was a way to rollback to android 9 without wiping the data I would have done it just to try this kernel.
would it be possible to add battery charge limiting support? currently apps like ACC don't work with this phone.