Related
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
So today with some testers i managed to make root on OnePlus 8 Pro, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator).
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
TIPS:
You can get the stock boot images from the fastboot rom: Fastboot ROMs
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use the latest stable Magisk
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images:
https://www.androidfilehost.com/?w=files&flid=308380
or
https://sourceforge.net/projects/fastbootroms/files/OnePlus 8 Pro/Patched-Stock-Boot/
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
I want to specify somethings:
Codename:
OnePlus 8: instantnoodle
OnePlus 8 Pro: instantnoodlep
OnePlus 8 Pro 10.5.4BA (Europe) stock rom link: https://otafsg1.h2os.com/patch/amaz...ygen_15.E.13_OTA_013_all_2004111446_df409.zip
First of all, thank you for the awesome work!
Could you explain a bit what are the modifications made to boot.img?
pijiman said:
First of all, thank you for the awesome work!
Could you explain a bit what are the modifications made to boot.img?
Click to expand...
Click to collapse
I just patched it with magisk, so it only contains in addition magisk
Wow, that was fast, thanks a lot guys
Before flashing the patched_boot.img you need to unlock the bootloader.
Tick the "Advanced reboot" under Developer options
Then reboot your device in bootloader-fastboot mode
fastboot oem unlock
Many thanks for the quick Root my Device
mauronofrio said:
I just patched it with magisk, so it only contains in addition magisk
Click to expand...
Click to collapse
Do you know if it passes SafteyNet with Magisk Hide enabled? Assuming not since Google now uses hardware signatures vs spoofable software ones.
Awesome, I had a bit of a struggle trying to find the full stock ROM link, thanks.
I have a follow up question: what are the features needed from Magisk and Magisk Manager that require the Canary release? I can't find anything in their changelog and my curiosity is getting the best of me
pijiman said:
I have a follow up question: what are the features needed from Magisk and Magisk Manager that require the Canary release? I can't find anything in their changelog and my curiosity is getting the best of me
Click to expand...
Click to collapse
Canary builds are not needed.
xocomaox said:
Do you know if it passes SafteyNet with Magisk Hide enabled? Assuming not since Google now uses hardware signatures vs spoofable software ones.
Click to expand...
Click to collapse
Sure does
xByt3z said:
Sure does
Click to expand...
Click to collapse
That's interesting. Thanks!
Does this mean Google Pay still works? Thanks
l_p_4_7 said:
Does this mean Google Pay still works? Thanks
Click to expand...
Click to collapse
Yes.
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Nekromantik said:
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Click to expand...
Click to collapse
SkyDragon dev is awesome! I had that on my LG G3!
xocomaox said:
SkyDragon dev is awesome! I had that on my LG G3!
Click to expand...
Click to collapse
Yeah due to increased price I am worried we wont get as much development on 8 Pro. I might get back into situation I was in on 7 pro 5g which had non existent development
Nekromantik said:
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Click to expand...
Click to collapse
feel free to compile them for us
I have a patched img for the global AA device! Would you like to add it to your post?
Into my Magisk Manager App the modules have gone. Is that kinda normal and I have to download and install modules from other sources or is there something wrong? In earlier Magisk builds I was used to find some modules into the app.
Thx in advance
Since you're on the Canary builds (necessary for the Pixel 6) you won't be seeing any modules to download. That was removed in build 23010, and you'll find the explanation here:
https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458
Ok, thank you
This is a guide to install mods for OP8 Pro that improves the stereo speaker setup. I have helped many OP8 Pro users to achieve this. Some other OP users as well.
Custom ROMs that work with this mod (TESTED):
Stock Oxygen OS 11 (not 12/13)
CrDroid
Evolution X
*I am not responsible for bricked devices, damage to your device*
I am here to post my method for anyone who is interested. I have tested this myself and helped others to do this.
Issues:
IMPORTANT:
Setting SElinux can have security issues noted by @topjohnwu.
Viper4Android can be installed with SElinux Enforcing and Permissive. Choose SElinux Enforcing not Permissive
Installation Method:
With new Viper4Android Repackaged module
If you have other audio mods
Download Audio Modification Library from the links section
Install Audio Modification Library, reboot and disable it
Otherwise, skip to the next step
Download the latest Viper4Android Repackaged module from the links section
If you want to use the extra V4A features...
Download and extract all the guide setup or the other .zip file I attached below on your device. You need the DDC, Kernel and Preset folders.
If you downloaded and extracted on a separate device: Connect your device, copy and paste the folders into your internal storage.
Otherwise, skip to the next step
Install the Viper4Android Repackaged module.
Reboot.
Open the app and grant root
DISCLAIMER: On custom ROMs or certain devices, the drivers are installed, but NOT working properly after reboot. Just continue the method and comment if there are issues once u have finished the method.
If you have Audio Modification Library installed
Now go into magisk manager, go into modules and enable AML.
Reboot
Otherwise, skip to the next step
If u used the guide setup.zip file: in V4A app just press the file icon for presets and choose the preset.
Now make sure V4A driver is running (read Notes) and go into convolver -> impulse response. Choose any kernel, and done. OR choose the preset for that and done. If you have issues, make sure legacy mode is on but it is on by default.
Choose to your heart's desire if you downloaded all the V4A DDC and kernel files.
I personally use Dolby Digital Plus - Centre kernel
Done, also post the settings or kernels and your thoughts.
I also attached a screenshot of my configuration
Also, for new users if u connect your earphones like via headphone jack, USB-C or Bluetooth. You can tweak those as well. Not just your SPEAKERS! BUT some earphones can be damaged as well, so tweak them at your own risk.
After much tweaking myself. I think I have made my speakers much better on my 8 Pro.
I have attached a screenshot to the thread at the bottom. I have attached a screenshot for my headphones too!
I have added the individual settings as well. If u want to tweak them just press the text and it should expand.
The toggles I have on are for my speakers:
Master Limiter
Playback gain Control: Strength: 2, Maximum gain: 3X, Output threshold: -1.9dB
Convolver: Dolby Digital Plus - Centre, Cross Channel 100%
Speaker optimization
I have also tweaked my Bluetooth earphones as well with a DDC and the screenshot is attached below. I recommend Dolby headphone Live, but that's up to you.
U can add files in the DDC folders in the Android folder, but reboot and then tweak to see the difference. U CAN RISK DAMAGE IF U TWEAK TOO MUCH
You have completed the guide and can now experience dual/stereo-like speakers on your OP6/6T.
Enjoy
If anyone has any issues with this guide. Post a message and I'll get back to you
Notes:
Viper4Android sometimes doesn't turn on properly. So, play music and open the app to check the driver. The Driver status if it's working (NEON enable: yes, Enabled: yes, Status: Normal) and turn on the master limiter to see if there's an effect. This should give you an indication if V4A is working or not
I have attached DDC files below and you do the same thing with kernel files, but they are used for headphones.
You can try and use the preset (profiles). You don't have to use the preset files, they are there to make the setup easier for those who don't want to tweak too much.
If u want to add the custom presets:
Choose the specific presets u want
Transfer them into Android -> data -> com.pittvandewitt.viperfx -> files -> presets
Transfer the V4A.zip in internal storage
Reflash the V4A.zip again and reboot
Install the V4A driver again and reboot
V4A driver should be working, check the presets and it should be there
Enjoy having your presets
Fix for V4A:
There has been noted issues during the installation with V4A. If you experienced a bootloop after installing V4A in magisk...
Boot into OrangeFox, -> advanced -> file manager -> data/abd/magisk/modules and delete the V4A folder.
Reboot to system, install the module in magisk again and reboot. It should install.
Another issue was that V4A driver is installed properly, but there are no enhancements to the sound. To fix this, go into settings -> turn on and off the legacy mode toggle. This should restart the effect and make it stay on.
Links:
Modules required
Audio Modification Library Link
Download Viper4Android and one of the preset files if u want Viper4Android installed
Viper4Android Module Link
Viper4Android Repackaged Module Link
All Viper4Android preset files Link
Viper4Android files for this guide is attached below
All DDC, Kernel, and Presets in one zip is attached below
Threads where the modules are from
Audio Modification Library Thread Here
Credits:
@Zackptg5 for his Audio Modification Library and Viper4Android module
@Vimal Vinz for the V4A DDC + Kernel + profiles
Reserved
Updates
10/9/22 - Removed step for the option to choose Enforcing or Permissive for SElinux during Viper4Android module install. It has been removed
15/1/22 - Released the XDA thread that is a guide to install Viper4Android for the OP8 Pro
Not sure about the OP8 sadly as I don't own one and this guide could be used for other android devices too
This guide is a duplicate from my previous dual speaker guide for the OnePlus 6/6T. But this guide can be used for other android devices or users who just want to install Viper4Android
2/11/22 - Updated the Installation method as I found a new updated version of Viper4Android (Repackaged)
Tested the module and it works on Android 12 and Android 13
AML does work on Android 13 as well
3/2/23 - Updated the method Viper4Android method as repackaged installs the DDC, Kernel and preset files during installation.
So, u can just download and extract the compressed .zip file into internal storage and V4A will install the files for you during installation.
Extreme_Ninja2099 said:
Issues:
IMPORTANT:
Setting SElinux can have security issues noted by @topjohnwu.
Viper4Android can be installed with SElinux Enforcing and Permissive. Choose SElinux Enforcing not Permissive
Installation Method:
Install Audio Modification Library, reboot and disable it
Install the viper4Android module.
Choose the option to install with SElinux Enforcing not SElinux Permissive
If a new version of viper4Android module is available, install that
Reboot.
Open the app and grant root
Install drivers in the app and it will reboot automatically
Click to expand...
Click to collapse
Hello! Can't install on OnePlus Nord 2. SElinux Enforcing.
You are describing a method here with 'not SElinux Permissive'
Help me please.
2. Choose the option to install with SElinux Enforcing. When installing the module, there is no such preset. Basically, I've tried everything. It doesn't work... you need to somehow change SElinux
DeMiane said:
Hello! Can't install on OnePlus Nord 2. SElinux Enforcing.
You are describing a method here with 'not SElinux Permissive'
Help me please.
2. Choose the option to install with SElinux Enforcing. When installing the module, there is no such preset. Basically, I've tried everything. It doesn't work... you need to somehow change SElinux
Click to expand...
Click to collapse
U could just uninstall the v4A module in magisk manager. Then try again and choose SElinux enforcing. Also, this guide is for the 8 pro not nord 2. I don't own a nord 2 and only tested on the 8 pro
Extreme_Ninja2099 said:
U could just uninstall the v4A module in magisk manager. Then try again and choose SElinux enforcing. Also, this guide is for the 8 pro not nord 2. I don't own a nord 2 and only tested on the 8 pro
Click to expand...
Click to collapse
oxygen is the same. And when does he suggest choosing SELinux? It installs automatically and that's it.
Works great on the OP8 (crDroid). Thanks a lot for the guide!
DeMiane said:
oxygen is the same. And when does he suggest choosing SELinux? It installs automatically and that's it.
Click to expand...
Click to collapse
First of, what version of magisk are u using? I only use stable (V23), where are u getting the viper4android .zip file/module? I have added the download link in the thread. If ur getting it from magisk manager, the one to use is the viper4android FX (Not legacy and not XHiFi)
laurentlbm said:
Works great on the OP8 (crDroid). Thanks a lot for the guide!
Click to expand...
Click to collapse
That's great. I don't own an OP8 so idk if it works. Hopefully, u used the kernel and DDC files too as they make a difference in my experience. Thanks for your feedback
Extreme_Ninja2099 said:
That's great. I don't own an OP8 so idk if it works. Hopefully, u used the kernel and DDC files too as they make a difference in my experience. Thanks for your feedback
Click to expand...
Click to collapse
Yes, I'm using the file and the difference is quite impressive!
Extreme_Ninja2099 said:
First of, what version of magisk are u using? I only use stable (V23), where are u getting the viper4android .zip file/module? I have added the download link in the thread. If ur getting it from magisk manager, the one to use is the viper4android FX (Not legacy and not XHiFi)
Click to expand...
Click to collapse
Yes, I'm using version 23 of Magisk. I tried to install viper4android FX (Not legacy and not XHiFi) from the Magisk repository, as well as separately downloaded zip viper4android FX v2,7,2,1. But it doesn’t give a choice in which mode to put it, it just puts it all. Android 11. My English is bad, maybe I'm not expressing myself accurately, sorry. Also install the AML library. I saw how they put it on Pixel 3 / 4a, but the version of magisk is exactly 21.1. I can't downgrade.
DeMiane said:
Yes, I'm using version 23 of Magisk. I tried to install viper4android FX (Not legacy and not XHiFi) from the Magisk repository, as well as separately downloaded zip viper4android FX v2,7,2,1. But it doesn’t give a choice in which mode to put it, it just puts it all. Android 11. My English is bad, maybe I'm not expressing myself accurately, sorry. Also install the AML library. I saw how they put it on Pixel 3 / 4a, but the version of magisk is exactly 21.1. I can't downgrade.
Click to expand...
Click to collapse
Do u install it in magisk manager? if u installed it properly (without the magisk manager crashing) and leave it to install... The install terminal should show a question + options for u to choose if u want SElinux enforcing or permissive. U choose by pressing volum up or down. Up for enforcing and down for permissive. The the reboot button should show up. Maybe take a screen shot and show it here
( Нет выбора и app faled
Extreme_Ninja2099 said:
Do u install it in magisk manager? if u installed it properly (without the magisk manager crashing) and leave it to install... The install terminal should show a question + options for u to choose if u want SElinux enforcing or permissive. U choose by pressing volum up or down. Up for enforcing and down for permissive. The the reboot button should show up. Maybe take a screen shot and show it here
Click to expand...
Click to collapse
(No choice and app failed
DeMiane said:
(No choice and app failed
Click to expand...
Click to collapse
Then idk. This guide is for the 8 Pro not Nord 2...
Extreme_Ninja2099 said:
Then idk. This guide is for the 8 Pro not Nord 2...
Click to expand...
Click to collapse
Unfortunately... but https://forum.xda-developers.com/t/app-all-root-solutions-6-0-viper4android-fx-2-7.3774651/page-275
they even launched it on pixel 6. and it didn’t work for me either. I will look into it, thanks
Nice guide.
DeMiane said:
(No choice and app failed
Click to expand...
Click to collapse
I previously checked my comments and found that V4A can cause SElinux to be permissive on some OSs. There's a magisk module that will set your SElinux back to Enforcing with no app needed and it's a just a command that will set your SELinux back to enforcing during every boot. https://forum.xda-developers.com/t/...b-root-selinux-permissive-enable-eng.4050041/
Extreme_Ninja2099 said:
I previously checked my comments and found that V4A can cause SElinux to be permissive on some OSs. There's a magisk module that will set your SElinux back to Enforcing with no app needed and it's a just a command that will set your SELinux back to enforcing during every boot. https://forum.xda-developers.com/t/...b-root-selinux-permissive-enable-eng.4050041/
Click to expand...
Click to collapse
I'll test ... this post also interested me, by the way, changing boot.img did not help, is the phone bootlop. This is what I experimented with.
ps000000 said:
May I add Android 12 instruction to this thread.
(Only custom 12 ROMs since ColorOS12 I cant enable permissive.)
You should goto app settings Unrestrict battery usage for both SELinux and Viper.
1. Install SELinux apk enable permissive on boot.
2. Magisk install Viper 12 Fix module no reboot
3. Magisk install Viper
4. Open Viper grant root and then press ok phone will auto reboot.
5. After rebooot pen Viper setting enable Lagacy mode .... done.
Click to expand...
Click to collapse
on 11 did not roll ... (
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.