Note: I have only tested this on Mate 10 Pro, so I don't know if it works on Mate 10. Title will stay until tested
Kernel downloads: https://github.com/Ante0/BKL_OREO_EMUI8/tree/master/releases
Source used: https://github.com/Ante0/BKL_OREO_EMUI8
Currently upstreamed to: 4.4.130
4.4.60 and above contains Blu_Active governor
Windows: https://mega.nz/#!NTgEFKiZ!4nB6QuznpI-Q4R8mtJENZ34KV4YNr6aUIlMTyTYOQcQ
Download Kernel_Pack_tool_windows.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_windows folder, open a command prompt in the extracted folder and run "pack_kernel.bat 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
Linux: https://mega.nz/#!Ne5mXATT!FXjWsnY61VewihTWagrJ09G6jv15_y4BlS_R0HDQ5UM
Download Kernel_Pack_tool_linux.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_linux folder, open a terminal in the extracted folder and run "./pack_kernel.sh 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
If you get permission errors you may have to chmod +x pack_kernel.sh and mkbootimg
UPDATE: I have changed sources to use Honor View 10 instead as camera works here (and everything else) and I'm also upstreaming it. Currently at 4.4.52: https://github.com/Ante0/BKL_OREO_EMUI8.0
Downloads will come soon. I will make a new script to change patch level instead of changing each image (from 2017-12 to 2018-09) as it takes time and space on my mega.
This does not set selinux to permissive all the time, you have to use 'setenforce 0' to enable permissive, this is to only enable it when you need it.
All this does is let us use 'setenforce' again, since Huawei decided to disable it in Oreo.
Could be useful for V4A and other sound mods, since they usually require permissive. Or anything else that could need permissive.
V4A still doesnt work with permissive, something else needs fixing
Note: This is for Security Patch level 2018-01. If yours is 2017-12 or 2018-02 you will bootloop.
This is because --os_patch_level must match ro.build.version.security_patch in /vendor/build.prop
If so you need to repack kernel and change --os_patch_level to match your version.
I will keep my github updated with security patches from Google, but if Huawei changes something in their own source it won't be in this kernel.
Mate 10/Mate 10 Pro downloads: https://mega.nz/#F!FbBBCaIS!YYH94l12su3HcsbwIqDygg
(Check Settings -> About - "Android security patch:" to get the correct patch level.
If it says 1 January 2018, download and flash 201801 kernel. 1 February 2018: 201802 and so on.)
Flash using: Fastboot flash kernel kernel.img
Mate 10 Kernel source: https://github.com/Ante0/ALP_OREO_EMUI8
Mate 10 Pro Kernel source: https://github.com/Ante0/BLA_OREO_EMUI8.0
Update 10/2: Added Wireguard support, for those who like to use VPNs.
Added some simple build scripts
Please note that portrait mode in camera has been broken with custom kernel since BLA-L29C432B137
Not working on BLA-L09, error mode boot image load failed.
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
smariob said:
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
Click to expand...
Click to collapse
Bordo_Bereli51 said:
Not working on BLA-L09, error mode boot image load failed.
Click to expand...
Click to collapse
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
ante0 said:
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
Click to expand...
Click to collapse
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
@ante0
Thank you for the new kernel!!!
Keep up the good work dev :good::good::good:
smariob said:
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
Click to expand...
Click to collapse
No. Kernel is separate. Magisk goes in ramdisk.
Before oreo ramdisk and kernel was merged in the boot partition, but now they're split into ramdisk and kernel partitions.
So you only need to flash kernel to kernel.
Congrats for the first Mate 10 kernel, mate![emoji482]
noob question here: setenforce 0 is written in terminal or adb? how to?
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Bordo_Bereli51 said:
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Click to expand...
Click to collapse
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Saadkhalid786 said:
noob question here: setenforce 0 is written in terminal or adb? how to?
Click to expand...
Click to collapse
terminal.
Or use the Magisk Module as Bordo_Bereli51 suggested.
Though if you don't have any app or something that needs permissive it's no use in running it at all times.
ante0 said:
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Click to expand...
Click to collapse
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Bordo_Bereli51 said:
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
Click to expand...
Click to collapse
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
I am already doing that but wanted to know if he had stock but I am almost finished getting stock kernel
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
ante0 said:
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
Click to expand...
Click to collapse
Yes, looks like that driver is disabled, but i still didn't found another vibrator/motor.
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Bordo_Bereli51 said:
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Click to expand...
Click to collapse
It's set to always permissive.
Edit: And for me it bootloops for some reason.
ante0 said:
It's set to always permissive.
Click to expand...
Click to collapse
Which is why I want it in order to get V4A working
I am on kangvip rom.
Bordo_Bereli51 said:
Which is why I want it in order to get V4A working
Click to expand...
Click to collapse
I've tried with permissive, doesn't work with the Magisk Modules...
You might have luck with installing to /system and /vendor manually.
Kangvip might be why the kernel is not working for you, they usually incorporate their own hacks.
Related
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r27. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
2015/04/01
please visit http://forum.xda-developers.com/showpost.php?p=59827552&postcount=8 to see more information:
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108/.157 or any ROM based on it.
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
sharonliu said:
This is an unofficial compiled from Xperia Z1 CoCore-Z Kernel sources. I like to share with you my modified version of CoCore-Z kernel r25. I'd like to credit @cocafe it wouldn't be possible without you. I'm not a developer so I cannot answer your question about any bugs for this kernel immediately.
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread. I will ask cocafe how to resolve bugs.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
Changelog:
1.Compiled using Linaro GCC 4.9.3 2015.03 toolchain with Cortex-A15 optimizations
2.Ramdisk adjusted for the Z1C
3.Updated PhilZ Touch recovery v6.59.0 & CWM v6.0.5.0 & TWRP v2.8.5.0
Requirements:
1. Unlocked Bootloader
2. Stock Sony KK firmware .757/.108 or any ROM based on it
Features:
Visit the CoCore-Z Original thread in the Z1 forum, and make sure you read all the instructions and features.
http://forum.xda-developers.com/xperia-z1/orig-development/kernel-cocore-z-r12-t2892310
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Kernel Source:
https://github.com/cocafe/c6902_kernel_CoCore-Z
Credits:
cocafe (for his kernel sources and letting me build this unofficial release)
[NUT] (for all recoveries & 14.4.A.0.157 kernel ramdisk & NDRUtils)
OmarEinea (for his great script of build tools letting me easy way to compile kernel)
Christopher83 (for Linaro cross compiler toolchains)
And for everyone who had a hand in making this kernel better
Click to expand...
Click to collapse
cocafe mentioned that the wifi modules has to be original from stock ROM, so i replaced them before flashing the kernel, but wifi does not turn on.
thank you for reporting this problem, it should be resolved next release.
Nice to see another stock based kernel around!
Only .108 or also .157?
Schlengge said:
Nice to see another stock based kernel around!
Only .108 or also .157?
Click to expand...
Click to collapse
from cocafe´s post:
ROM: Stock KitKat 4.4.4 14.4.A.0.108 +
Click to expand...
Click to collapse
so imho for .157 too
sharonliu said:
thank you for reporting this problem, it should be resolved next release.
Click to expand...
Click to collapse
i think this solves the problem: LINK
moonryder said:
i think this solves the problem: LINK
Click to expand...
Click to collapse
Thanks for the information. Just like DooMKernel, my goal is no need to compile wlan module. If I am not luck, I will build the wlan module in this weekend.
Changelog :
wlan is working
Download Links:
https://mega.co.nz/#F!ysRWkCQY!Hb9wssFCCpc9fCEhI4zFQQ
Insturaction:
If you want back to stock kernel, remember reboot to recovery and flash stock wife modules.
sharonliu said:
...flash stock wife modules.
Click to expand...
Click to collapse
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
moonryder said:
funny...
btw will check this kernel
checked your stock wlan zip file, there is something wrong.
the wlan file is wrong named (the right name is pronto_wlan) and would be flashed into /system/lib/modules
but it has to be flashed into /system/lib/modules/pronto
p.s. i replaced all files in the zip with the original from my ROM
Click to expand...
Click to collapse
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
sharonliu said:
In CoCore-Z-r27-wlan-modul, pronto_wlan is not included in the zip file, only customize prima's wlan.ko. So my stock wlan zip file, no need to re-flash pronto_wlan. cocafe will try to port new pronto_wlan in the next time.
Click to expand...
Click to collapse
ok
btw flashed new build from today and wifi works like a charm.
thx
Thanks for this kernel
The only thing I noticed is that the notification light turns white when the battery is full
Normal it's green
Don't know if it's I bug but I noticed it
It's not a bug. Cocafe made it so the led will notify you of the real eoc. You can change the led color though here I believe "/sys/kernel/qpnp-charger/eoc_led"
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
moonryder said:
i tried some scripts from cocafes original post HERE.
But none of the scripts work using SManager. Why?
always error: "No such file or directory ...."
but these files / directories are there (checked it with RootExporer) -DAMN
And if the scripts don´t work, there is no profit compared to DoomKernel...
Click to expand...
Click to collapse
get terminal emulator from the play store and type it in there
or use adb shell
adb shell
su
Click to expand...
Click to collapse
it should work if you type these scripts. In my opinion, DoomKernel is the best custom kernel, bu nice to see another stock based kernel around.
sharonliu said:
...DoomKernel is the best custom kernel....
Click to expand...
Click to collapse
you are so right bro
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
a1b2c3901 said:
I found this kernel seems not to support exFAT. May you fix that?
btw, thx for modifying this kernel for Z1C. It's amazing !!
Click to expand...
Click to collapse
why do you use exFAT format?
Do you have files > 4GB in use?
moonryder said:
why do you use exFAT format?
Do you have files > 4GB in use?
Click to expand...
Click to collapse
Sometimes I will watch movie in the journeys, and that files may be oversize.
a1b2c3901 said:
Sometimes I will watch movie in the journeys, and that files may be oversize.
Click to expand...
Click to collapse
get "MLUSB Mounter" from the play store, you can use the USB hard drive (formatted NTFS, exFAT).
Introduction
NOTE:
Hello everyone, this is my first kernel for the Moto G4 Plus. I will try to maintain a stable kernel however bugs might arise since I'm not a super star kernel developer. I hope you enjoy the releases.
Important information
I will not reply to complains that do not include clear steps to reproduce the bug, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
Features
Here are the major features of the kernel (feel free to explore Github)
Update to date with the latest Linux upstream version (3.10.108-EOL)
Westwood as the default congestion algorithm with many more to choose from
Several subsystems converted to use power efficient workqueues
Compiled with Google's arm-eabi 4.9 toolchain
Audio control from flar2
Downloads
Oreo 8.0 : https://sourceforge.net/projects/babyfish-kernel/files/athene/oreo_caf/
Nougat 7.1 : https://sourceforge.net/projects/babyfish-kernel/files/athene/nougat_caf/
Nougat 7.0 Stock :https://sourceforge.net/projects/babyfish-kernel/files/athene/stock_nougat/
Installation:
NOTE: Please make sure that you return to the stock kernel of the ROM before flashing this kernel. The kernel is unified for Moto G4 and the Plus variant so everything should be working fine.
Install the latest adb and fastboot: https://developer.android.com/studio/releases/platform-tools.html#download
Grab the boot image from the download links above
Method 1:
Using adb and fastboot
Reboot into the bootloader using either restart and hold power button and volume down or adb:
Code:
adb reboot bootloader
Flash the boot image. Run the following command in the folder with the boot image and ensure fastboot is in your PATH:
Code:
fastboot flash boot <boot_image_name>.img
Reboot and profit!
Method 2: TWRP
Keep the bootimage on your phone's storage and boot to TWRP.
Install > Select Install Image > Choose the image > Boot partition > Reboot
Changelog
28 November 2017
Oreo-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Nougat-CAF:
Code:
Initial Release
Introduce Tossug Baby Fish kernel
Add Sound Control
Add TCP congestion algos
Disable crc check for 30% performance improvement in I/O
Linux 3.10.108
Stock N:
Code:
FAQs
1.1 Q Can you help me I have this problem?
1.1 A I will surely try to help if proper bug reporting is done as per the fashion described above.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not add any useless governors or features that I don't find practical.
1.3 Q: How do I control the kernel?
1.3 A: I recommend using EX Kernel Manager or Kernel Auditor (Both need root)
1.4 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.4 A: The kernel doesn't drain any battery unless you have overclocked it, I have kept it at stock frequencies and voltages. Use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
The various other developers for their patches (if you want a specific mention, please let me know)
All of you guys for viewing the thread
Thiago Neves @lcrd512 and Abhijeet Bohra.
Kernel source links.
8.0.0 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/oreo_caf
7.1 CAF : https://github.com/tywinlannister7/android_kernel_motorola_msm8952/tree/nougat_caf
7.0 Stock :
If you like my work, buy me an Appy Fizz or whatever you like
https://www.paypal.me/tywinlannister7 :good:
XDA:DevDB Information
Reviver Kernel, Kernel for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: https://github.com/tywinlannister7/android_kernel_motorola_msm8952
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-28
Last Updated 2018-12-10
Screenshots
Some Screenshots
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing. ?
tywinlannister7 said:
Some Screenshots
Click to expand...
Click to collapse
Which ROM is this?
Ayan Uchiha Choudhury said:
Which ROM is this?
Click to expand...
Click to collapse
DU 12 oreo
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Thanks for the new addition in the family.
I hope this will be the favorite member of the family:laugh:
Where is the love for stock user?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
There is a link for stock rom in the op though?
thorin0815 said:
Where is the love for stock user?
Click to expand...
Click to collapse
Stock version won't be released any sooner. I don't have the time for it right now and compilation process of stock kernel is a bit different than CAF kernels. Maybe before the second week of January.
briatide said:
There is a link for stock rom in the op though?
Click to expand...
Click to collapse
Empty as of now
ganeshkmr21 said:
@tywinlannister7 Any plans on making some Device Specific ROM for Athene.? Since Invicta is out of scene now.
Click to expand...
Click to collapse
IDK I don't have the time, we already have so many ROMs available. Creating a new ROM will be adding it to the huge list already available, from AOSP to LineageOS to Dirty Unicorns. I would rather work on optimizing what we have. Quality > Quantity.
jyoti.id said:
Will work on LOS, right? Sorry for asking this nooby question. I just want to be confirm before flashing.
Click to expand...
Click to collapse
Yes. 7.1 version for all N custom ROMs and 8.0 for all the O custom ROMs
DU 12 oreo
Blueman1990 said:
DU 12 oreo
Click to expand...
Click to collapse
about DU 12 oreo where can i get it ?
many thanks
i love new system
Does not boot on LOS15. Can anyone else confirm? Cant do logs cause my data port on my phone is broken. It sits on the boot screen like its loading but never fully boots.
Thank you bro!! finally an oreo kernel!
Where I can get DU 12?
Does this have color management?
And which kennel manager should i use with this?
Thanks
harshal2234 said:
Where I can get DU 12?
Click to expand...
Click to collapse
Its not out yet I guess
---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------
Ashishliterally said:
Does this have color management?
And which kennel manager should i use with this?
Thanks
Click to expand...
Click to collapse
Bro its just a 2 page thread. At least read. That question has been answered, in the OP!
Can't I get the unofficial build?
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Same for me. On LOS 14.1, XT1643
---------- Post added at 05:17 PM ---------- Previous post was at 05:16 PM ----------
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
I don't think so. If magisk is installed/flashed once, then no need of flashing ever again until you freshly install the rom. (AFAIK)
ramansehra said:
Tried it but I got bootloop.
Using latest Resurrection Remix Rom With Stock kernel on XT-1643.
Missed the logcat.
Should I have to flash the magisk again after installing kernel?, may be this was the reaseon I got bootloop because boot.img was changed and again installing magisk could help with that.
Click to expand...
Click to collapse
Same happened with me I was on Invicta os 8.0
I will be posting my kernel builds here for convenience.
Pre-requisite
Unlocked bootloader with TWRP Recovery installed.
DRM fix must be in place before rebooting to avoid a soft brick.
This DRM patch which was available in sToRm//'s free Xperifix version still works
Features
- Stock based kernel with DT2W enabled.
- Forced encryption disabled.
- Passes Safetynet out of the box.
- Fully working camera (Pie kernel-no DRM fix needed for camera).
- Flashable zip with no need to extract boot.img
- Compatible with any version of Magisk.
Installation
Flash drmpatch.zip then kernel.zip.
You can then flash Magisk if you require it.
Camera doesn't depend on it though.
Flash zip in recovery (don't just extract boot.img as zip has system files to enable DT2W)
Kernel Sources
https://developer.sony.com/develop/open-devices/downloads/open-source-archives
Note. Kernel is compiled as per stock. DT2W is enabled in the DTB, the same parameters as used by the Loire platform.
Downloads
G8141_DT2W-41-kernel.zip
G8142_DT2W-41-kernel.zip
Kernel Requests.
Post the kernel.sin and I will patch it and add it to the OP.
Kernel Requests: View attachment kernel-G8142-205.zip thx !
oneheart said:
Kernel Requests: View attachment 4522264 thx !
Click to expand...
Click to collapse
Added, thanks. Please test and report back (I only own G8141).
shoey63 said:
Added, thanks. Please test and report back (I only own G8141).
Click to expand...
Click to collapse
if i need flash the drmpatch.zip ？
oneheart said:
if i need flash the drmpatch.zip ？
Click to expand...
Click to collapse
Yes, it's required.
it work on G8412 ， thx ！
How can I update to 205 without losing my data?
SilverGamer_YT said:
How can I update to 205 without losing my data?
Click to expand...
Click to collapse
Flash only system.sin - nothing else. Then boot to recovery and flash drmpatch.zip, kernel.zip and then Magisk if you need it.
Reboot and you are done.
@shoey63
dual sim kernel have a problem with wifi.
wifi is off didn't turn on
karrouma said:
@shoey63
dual sim kernel have a problem with wifi.
wifi is off didn't turn on
Click to expand...
Click to collapse
Kernel itself is unmodified, and ramdisk changes don't touch wifi settings at all. Seems to be a hardware or software problem with Sony sd835 as per various complaints here https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Wifi-connection-problem/td-p/1315030
Adding to the confusion is that the issue is sporadic, intermittent and apparently device specific. Some users suffer badly, whereas others have no problems.
At any rate, there is nothing I can do about it.
shoey63 said:
Kernel itself is unmodified, and ramdisk changes don't touch wifi settings at all. Seems to be a hardware or software problem with Sony sd835 as per various complaints here https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Wifi-connection-problem/td-p/1315030
Adding to the confusion is that the issue is sporadic, intermittent and apparently device specific. Some users suffer badly, whereas others have no problems.
At any rate, there is nothing I can do about it.
Click to expand...
Click to collapse
Thank you for you work.
One guy tell me to flash CE1 firmware
I will trt
Hi, thank you for time to do this kernel @shoey63 nice work
Just a little beginner's question ... what is the best kernel for my rom stock (yours ot androplus kernel),
from what I read your kernel is not changed at all ?
Castiglionais said:
Hi, thank you for time to do this kernel @shoey63 nice work
Just a little beginner's question ... what is the best kernel for my rom stock (yours ot androplus kernel),
from what I read your kernel is not changed at all ?
Click to expand...
Click to collapse
For tweaking and double tap to wake - Androplus. For the stability of stock - mine.
shoey63 said:
I will be posting my kernel repacks here for convenience.
Pre-requisite
DRM fix must be in place before rebooting to avoid a soft brick.
This DRM patch which was available in sToRm//'s free Xperifix version still works.
Features
- Pure stock kernel with only ramdisk changes to enable DRM fix plus solve SafetNet and Magisk issues.
- Passes Safetynet out of the box.
- Fully working camera (No green Pic's).
- Flashable zip with no need to extract boot.img
- Compatible with any version of Magisk.
Installation
Flash drmpatch.zip then kernel.zip.
You can then flash Magisk if you require it.
Camera doesn't depend on it though.
Downloads
drmpatch.zip
G8141-205
G8142-205dual
Click to expand...
Click to collapse
sir what extra this forbidden xperifix does?
i mean if i have maple kernel and those 3 files from system.sin, and using @serajr 's modified script of TOBIAS , I create one boot.img file and flash it and flash the drmpatch.zip (given) here by you via twrp...
WILL it work?
i don't have xzp
if okay, plz reply
YasuHamed said:
sir what extra this forbidden xperifix does?
i mean if i have maple kernel and those 3 files from system.sin, and using @serajr 's modified script of TOBIAS , I create one boot.img file and flash it and flash the drmpatch.zip (given) here by you via twrp...
WILL it work?
i don't have xzp
if okay, plz reply
Click to expand...
Click to collapse
Not quite OK. You also need to patch init.environ.rc as per this post https://forum.xda-developers.com/showpost.php?p=74310718&postcount=43
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
jianlin3062 said:
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
Click to expand...
Click to collapse
You could try this one. It is from M-ROM v1.5, a Chinese rom.
I would flash the kernel.zip again, then the SuperSU.zip then the drmpatch.zip and wipe cache and dalvik and see how you go.
jianlin3062 said:
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
Click to expand...
Click to collapse
You must try this version this is created for xperia phones:https://forum.xda-developers.com/attachment.php?attachmentid=4164510&d=1496008012
help
I can not understand the order in which I have to do things
Should I unlock the bootloader and then?
I must install the recovery by adb or first the kernel
I come from samsung and the difficulty here is greater and there is much less information, if someone could help me I would appreciate it. I have the latest version of oreo the .205
Kang kernel
By Sjll
Notice: Beware of bricking device!
This a new kernel for stock 10. It's aim to optimize the kernel and provide better user experience.
I had cherry-picked some commits from other SDM845 devices like M i8 and Oneplus 6T. So it's a fusion kernel, though I don't know whether these commits could improve our performance.
I share the source codes, so you could tweak the kernel by yourself. Ok, don't forget to share your work with us.
Download: Github
Note:
1. For XZ2, boot.img already included Magisk.
2 Internal problem is normal, ignore it.
CAF Version: LA.UM.8.3.r1-07600-sdm845.0.
Linux Version:4.9.206-r25-rel
Recommand to use EX kernel Manager
Feature:
1. GPU OC to 835 Mhz.
2. Thanks: Hide unlocked state from @j4nn
3. Qcacld wlan driver.
4. Remove useless drivers.
5. zram to lz4.
6. Increase priority of RT thread.
7. AVB flag removed.
8. WireGuard support.
9. Disabled some logs in kernel.
10. Newer CAF buff and Linux version.
11. Cpufreq and drm drivers optimization.
12. Schedutil optimization.
13. Energy model improved.
14. New I/O governor (Maple & Zen)
15. Blu_schedutil CPU governor( More Powersave ) Need to enable manually
16. IOsched optimization.
17. DTS eagle driver.
18. KLAPSE Color manager. Need EX kernel Manager
19. boeffla_wl_blocker supported.
20. adrenoboost supported, disable it by default.
21. etc..
How to flash:
HTML:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Vbmeta.img see Attach Files
If there is a dtbo.img, then:
HTML:
fastboot flash dtbo dtbo.img
I provide a new thermal configuration, see Attach Files, download it and replacing the same file in vendor/etc. You will get the full performance of SDM845.
Source code: Github
ROM OS Version: 10.0
ROM Kernel: Linux 4.9
Contributors
Sjll
Created 2020-02-26
FIRST! Muahahaha
Thank you like always.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Is it possible to port it on aosp10/los17 with osmosis anykernel?
thanks! can I flash on xz2 compact h8314?
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
It's the stock kernel
Completely incompatible with the SODP project
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
No, this kernel is only for stock, not SODP.
nikkdib said:
thanks! can I flash on xz2 compact h8314?
Click to expand...
Click to collapse
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Faruk.ErdaL said:
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
Click to expand...
Click to collapse
Thanks, if there is any bugs, feedback to me please. I will try to solve it.
Sjll said:
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
Click to expand...
Click to collapse
Yay
Nice, I wanted to look into TWRP at weekend
You could try to set
ro.debuggable=1
ro.adb.secure=0
Or build an -eng TWRP.
Sjll said:
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Click to expand...
Click to collapse
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
nikkdib said:
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
Click to expand...
Click to collapse
Done, try it and feedback, thanks.
Sjll said:
Done, try it and feedback, thanks.
Click to expand...
Click to collapse
i need to patch with magisk manager first if i want root yes?
nikkdib said:
i need to patch with magisk manager first if i want root yes?
Click to expand...
Click to collapse
Yes, you can. It should work fine with Magisk.
Sjll said:
Yes, you can. It should work fine with Magisk.
Click to expand...
Click to collapse
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
nikkdib said:
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
Click to expand...
Click to collapse
Done, try V1.5 please.
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
After first crash files in /sys/fs/pstore giving you the crash reason
MartinX3 said:
After first crash files in /sys/fs/pstore giving you the crash reason
Click to expand...
Click to collapse
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Faruk.ErdaL said:
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Click to expand...
Click to collapse
After crash go into Fastboot mode and flash the working kernel back (with magisk)
Then the device boots and you get the files
Just don't boot one time too much or the pstore will be wiped.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
For XZ2, it already included Magisk. Internal problem is normal, just ignore it. All works fine for me.
Provide your phone type please.
NOT RESPONSIBLE FOR ANY MALFUNCTIONS. MAKE BACKUPS BEFORE FLASHING!
Dirty flashing over previous OS version (~PE 12) may cause bootloop, clean flashing is recommended.
Formatting data partition to F2FS requires internal storage to be fully wiped!
Regarding KernelSU
- KernelSU module system is not (yet) fully compatable with Magisk's module.
- Installing Magisk over KernelSU-enabled boot image or vice-versa will make device not bootable. If it happens, just flash magisk uninstaller or reflash ROM.
- If you want to use KernelSU, flash boot-ksu_{ID}.img from the link below.
Unofficial Pixel Experience 13 Plus edition build for OnePlus 5/5T
Latest build date: 2023-05-09
Working:
Everything for now
Not working:
Let me know
Changelog
Code:
2023-05-09:
- DeviceSettings is back; DC-Dimming and vibration strength are now adjustable
- Deleted Active edge from settings menu
- Minor adjustment
2023-05-07:
- Revert KernelSU integration; KernelSU will be available for optional boot image
- Dropped cheeseburger build; Official build is available on PE homepage
- 2023-05 Security patch
- Based on AOSP 13_r43
2023-04-19:
- 2023-04 Security patch
- Based on AOSP 13_r41
2023-03-29:
- KernelSU integration
- 2023-03 Security patch
- Based on AOSP 13_r35
2023-02-19:
- 2023-02 Security patch
- Fixed SafetyNet fail issue
- Based on AOSP 13_r30
2023-02-15:
- Added anti-flicker driver to kernel
- Moved volume pannel to left side
- F2FS format support for /data and /cache partition
Changelog for KernelSU image
Code:
2023-06-16
- KernelSU version 11000
- Requires KernelSU Manager v0.6.0
2023-05-10
- KernelSU based on commit f69793d
- Module fix for kernel v4.4
- ksu version: 10852
- Requires KernelSU Manager v0.5.5 or above
2023-04-19:
- KernelSU based on commit 45c229d
- Requires KernelSU Manager v0.5.3 or above
Links:
Download for Dumpling (5T)
Download for Cheeseburger (5)
Download for boot image with KernelSU support (5/5T)
Sources:
msm8998-common
dumpling
Kernel
Known Issue:
- GCam and related patches are not included; No plans to add support in near future.
Original Post
Removed magisk and dirty flashed from previous build on dumpling but modules are not working with KernelSU. Installing them with KernelSU manager but module list remains empty even after rebooting. Tried with a clean flash and same result.
/data/adb/ksu/modules/ subdirectories only contains module.prop and an empty update file.
However, su and root privilege work as expected.
Is there something wrong with my device, KernelSU integration in this rom or KernelSU itself?
I can provide logs from KernelSU manager if needed.
Klbgr said:
Removed magisk and dirty flashed from previous build on dumpling but modules are not working with KernelSU. Installing them with KernelSU manager but module list remains empty even after rebooting. Tried with a clean flash and same result.
/data/adb/ksu/modules/ subdirectories only contains module.prop and an empty update file.
However, su and root privilege work as expected.
Is there something wrong with my device, KernelSU integration in this rom or KernelSU itself?
I can provide logs from KernelSU manager if needed.
Click to expand...
Click to collapse
KernelSU's module system is still in development, and it is changed to store modules in /data/adb/modules just like magisk. Each magisk module's install script might need to be altered a bit for KernelSU.
For more details of module system, check the wiki.
https://kernelsu.org/guide/module.html
Works very well, updating from pe13
KernelSu's module function didn't work, I hope you can fix that in next build
--4/4
I created a pull request from my fork, it fix the module function.
fprhqkrtk303 said:
KernelSU's module system is still in development, and it is changed to store modules in /data/adb/modules just like magisk. Each magisk module's install script might need to be altered a bit for KernelSU.
For more details of module system, check the wiki.
https://kernelsu.org/guide/module.html
Click to expand...
Click to collapse
For kernel <4.14, it requires additional patch for modules to work.
https://github.com/F-19-F/android_k...mmit/3df9df42a659f489091445d813b8c0477215ae3a
At what stage do we flash the flash boot-nksu.img file and how? I'm having some issues with the devices booting with the latest update and the latest magisk.
H1mJT said:
For kernel <4.14, it requires additional patch for modules to work.
https://github.com/F-19-F/android_k...mmit/3df9df42a659f489091445d813b8c0477215ae3a
Click to expand...
Click to collapse
Is this commit made by you or picked from someone else's?
totomo26 said:
At what stage do we flash the flash boot-nksu.img file and how? I'm having some issues with the devices booting with the latest update and the latest magisk.
Click to expand...
Click to collapse
If you want to use Magisk not KernelSU, then
1. Flash ROM zip
2. Flash boot-nksu.img
3. Flash Magisk zip
fprhqkrtk303 said:
Is this commit made by you or picked from someone else's?
Click to expand...
Click to collapse
The given link of F-19-F isn't my account, and yeah he is the author of that commit.
hey the fingerprint reader is not working ...
fprhqkrtk303 said:
KernelSU yerine Magisk kullanmak istiyorsanız, o zaman
1. Flash ROM zip'i
2. boot-nksu.img'yi flaşlayın
3. Magisk zipini flashlayın
Click to expand...
Click to collapse
which one should I choose ?
potatat0t0 said:
hey the fingerprint reader is not working ...
Click to expand...
Click to collapse
It works fine for me.
semaru_1988 said:
which one should I choose ?
Click to expand...
Click to collapse
choose boot
potatat0t0 said:
hey the fingerprint reader is not working ...
Click to expand...
Click to collapse
Me too
potatat0t0 said:
hey the fingerprint reader is not working ...
Click to expand...
Click to collapse
It works on mine.
aromanos2021 said:
It works on mine.
Click to expand...
Click to collapse
apparently it's working for some...
potatat0t0 said:
apparently it's working for some...
Click to expand...
Click to collapse
Does on 5t, doesnt on 5
Just upgraded from stock rom. So far, everything works fine and super fluid! Even the better compressed x265 video files plays smoothly on the phone, they was not with the stock rom.
But I have a problem with playing HDR video files. They are not bright enough even on 100% brightness and backlight, while the normal SDR videos are perfect. I used to play these video files from the internal memory with the stock rom, but they was enough bright. So this is something that the new rom changed.
*Tested with VLC and 2 other video players.
Kepszlok said:
Just upgraded from stock rom. So far, everything works fine and super fluid! Even the better compressed x265 video files plays smoothly on the phone, they was not with the stock rom.
But I have a problem with playing HDR video files. They are not bright enough even on 100% brightness and backlight, while the normal SDR videos are perfect. I used to play these video files from the internal memory with the stock rom, but they was enough bright. So this is something that the new rom changed.
*Tested with VLC and 2 other video players.
Click to expand...
Click to collapse
Solution: set HW acceleration in VLC from "full hardware" to "decode acceleration".
In this way the image brightness is perfect but the movie still fluent. On other players deactivating HW acceleration did result a not so fluent playback.