[KERNEL][G8231][G8232] Custom Kernel for Android Oreo build 41.3.A.2.234 - Sony Xperia XZs ROMs, Kernels, Recoveries, & Other

Alright, I just made a custom kernel based on current Android Oreo build 41.3.A.2.234 which enabled root properties and you can flash it by using fastboot method and then, you can install Magisk and also drmfix on TWRP after flashing the custom kernel. Just got an idea to create this custom kernel by editing the rootkernel script and this custom kernel might fix some issues especially the chrome browser turned into "Android Go" mode due to tiny swap partition.
Before installing, make sure that you have current Android Oreo build 41.3.A.2.234 installed on Xperia XZs G8231 or G8232 model and the bootloader must be unlocked first (you will need to perform backup on TA partition first before doing so - I'm really didn't noticed about that part before unlocking my device so don't follow my mistakes by not performing TA partition backup before unlock the bootloader!)
One more thing to remember - DO IT AT YOUR OWN RISK!!!
Download it here:
G8231: [Google Drive link]
G8232: [Google Drive link]
Note: If you did not have current firmware build installed, you can install it by using Xperia Flashtool program. Make sure that you are flashing the right kernel for your device model. You will be not entertained if you ask on how to unlock bootloader and even flashing the custom kernel. You should know the risk of flashing the wrong kernel and you should know how to handle it.
UPDATE: Adding the G8232 custom kernel as requested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

great work sir :good:

---

great work for this and is able to dual sim version ??

---

Dark Pwince said:
great work for this and is able to dual sim version ??
Click to expand...
Click to collapse
Not tested yet on dual-sim version because I don't have that device. You may want to try it out but at your own risk.

---

amirzaim said:
Not tested yet on dual-sim version because I don't have that device. You may want to try it out but at your own risk.
Click to expand...
Click to collapse
Can anybody confirm whether this works on dual sim?
Does both SIM get recognised in the phone using this boot.img kernel?

---

QPR_FC said:
Can anybody confirm whether this works on dual sim?
Does both SIM get recognised in the phone using this boot.img kernel?
Click to expand...
Click to collapse
Ok...just flash the G8232 custom kernel which I posted here recently.

---

amirzaim said:
Ok...just flash the G8232 custom kernel which I posted here recently.
Click to expand...
Click to collapse
Thanks, because I tried to create my own using Rootkernal v5.23 and the tool kept bombing out....
[email protected]:~/Documents/SONY/rootkernel$ ./rootkernel.sh kernel.elf boot.img
================================================================================
-------------------ROOTKERNEL V5.23 FOR XPERIA DEVICES--------------------------
================================================================================
-e Rootkernel V5.23
kernel.elf: kernel.elf: cannot execute binary file

---

QPR_FC said:
Thanks, because I tried to create my own using Rootkernal v5.23 and the tool kept bombing out....
[email protected]:~/Documents/SONY/rootkernel$ ./rootkernel.sh kernel.elf boot.img
================================================================================
-------------------ROOTKERNEL V5.23 FOR XPERIA DEVICES--------------------------
================================================================================
-e Rootkernel V5.23
kernel.elf: kernel.elf: cannot execute binary file
Click to expand...
Click to collapse
Probably a few of x-executable files which didn't set its permission for executable: bootimg, busybox, init and even rootkernel.sh itself