SM-N910F - Stock Kernel
Root Android 5.1.1
We have here 2 kernel variants
Original Samsung SE enforced kernel, repacked with a patched sepolicy through SuperSU 2.50
- Recommended kernel as it runs in enforced mode if you are concerned about security
- Recommended method by Chainfire
- Supports only SuperSU 2.50 app for root
- You must update to SuperSU 2.50 before flashing kernel or you end up in a bootloop
- TIMA SecurityLogAgent service still needs to be freezed
- Selinux runs in enforced mode
- Private mode can be used
Click to expand...
Click to collapse
Compiled from stock sources permissive kernel, with NTFS support
- huge drop in security, as it runs in permissive mode
- will allow you to run any superuser app
- supports ntfs mount (needs NTFS helper for the mount ntfs binary or get them from xda or from download link
- selinux is forced to permissive because of new Android 5.1.1 restrictions
- Private mode relies on Selinux and can no more be enabled
- TIMA SecurityLogAgent service needs to be freezed as new Android 5.1.1 detects changes in kernel/SE and warns you about them
Click to expand...
Click to collapse
Why a custom kernel or a modified boot image will probably be needed to root ?
answered by the master: http://www.androidauthority.com/chainfire-rooting-android-lollipop-541458/
New selinux restrictions make it quiet hard for the su daemon to load at boot without exploiting some kernel vulnerabilities that google will patch asap any way.
It seems also that even if we only revert the selinux permissive/enforced toggle, set state to permissive at boot and then enforce security once SU daemon is loaded, many issues could still rise because of the new SE policies. Chainfire says himself that trying to do so will in any case need to drop even more the security level.
Furthermore, enabling toggling of selinux state is now more complicated since 5.0: enabling CONFIG_SECURITY_SELINUX_DEVELOP in defconfig needs androidboot.selinux=permissive in board kernel cmdline. However, this won't be processed in user builds, but only in eng and userdebug builds. This means you cannot expect any such fixes to work on a stock ROM. We now must hardcode the kernel into always permissive mode
In permissive mode, it is impossible to use any KNOX protected features and system will triggers kernel modification alarms by security TIMA agent:
http://www.samsung.com/hk_en/support/skp/faq/1028007. That's why those services must be disabled.
Seems it is not Samsung to blame, but really Google.
Chainfire came with a new approach to avoid compiling the kernel and to be able to run in enforced mode: patching the sepolicy in ramdisk to allow root while still running a stock enforced kernel. This needs version 2.50+ of SuperSU, and won't support, currently, any other root application. This needs a complex procedure documented by Chainfire. It needs rooting the reference device under 4.4 - 5.0.1 enforced mode, patching the 5.1.1 sepolicy under that reference device and export the patched sepolicy to the 5.5.1 boot image of the device. The good part is that we only need to repack boot image with a changed sepolicy, without modifying anything else, mainly the kernel.
Credits
@Chenglu
@Chainfire
Emotroid-Team
XDA:DevDB Information
Android 5.1.1 Kernel, Stock, Root, Enforced and Permissive, Kernel for the Samsung Galaxy Note 4
Contributors
Phil3759
Kernel Special Features: stock, enables root for 5.1.1
Version Information
Status: Stable
Created 2015-09-23
Last Updated 2015-10-30
Download + source diff
- flash kernel in recovery (zip) or odin (tar)
- flash SuperSU v2.50+ for enforced kernel or any root app for permissive kernel
Link:
https://mega.nz/#F!RV8wGT6C!rsfnBrjuqukBNLgLxIgNIA
More original third party releases by @_alexndr (untested by me): https://www.androidfilehost.com/?w=files&flid=45166
FAQ and fixes
How to fix the security notice popup for the permissive recompiled kernels ?
Using Titanium backup, freeze this service: SecurityLogAgent
How to fix Screen Mirroring after root for permissive kernels ?
This is not related to the kernel, but affects some Samsung devices with root
For the fix, check here: http://forum.xda-developers.com/showpost.php?p=63004244&postcount=11
How to fix my wifi passwords not saved on reboot / wifi disconnect for permissive kernels ?
Add this line in /system/build.prop
Code:
ro.securestorage.support=false
What changes are done to the permissive kernel before compiling?
selinux permissive to enable root
NTFS stock Samsung implementation enabled in kernel (needs OTG helper probably)
History changes for permissive kernels
v1.0
N910P-VPU4COG5 kernel sources + N910F-XXU1COH4 ramdisk
v1.1
revert properties to defaults: if you have issues saving wifi passwords, add this line to /system/build.prop or revert to 1.0
v2.0
N910-F latest stock sources
back to ro.securestorage.support=false for wifi password issues in permissive mode
Click to expand...
Click to collapse
Sources:
post 2 with download link
Than you. Could you make a flashable zip with your kernel?
"Somos dueños de nuestro silencio y esclavos de nuestras palabras"
antz_77 said:
Than you. Could you make a flashable zip with your kernel?
"Somos dueños de nuestro silencio y esclavos de nuestras palabras"
Click to expand...
Click to collapse
added a zip file
Which App for Root can i use for example?
Just use SuperSU, after installing kernel with TWRP use the option to add root when exiting from recovery. You'll be fine
Verstuurd vanaf mijn SM-N910F met Tapatalk
patensas said:
Just use SuperSU, after installing kernel with TWRP use the option to add root when exiting from recovery. You'll be fine
Verstuurd vanaf mijn SM-N910F met Tapatalk
Click to expand...
Click to collapse
PhilZ Touch 6.59.0 works perfectly with 5.1.1 by the way, even time with Time Daemon load
Why a custom kernel will probably be needed to root ?
answered by the master: http://www.androidauthority.com/chainfire-rooting-android-lollipop-541458/
New selinux restrictions make it quiet hard for the su daemon to load at boot without exploiting some kernel vulnerabilities that google will patch asap any way.
It seems also that even if we only revert the selinux permissive/enforced toggle, set state to permissive at boot and then enforce security once SU daemon is loaded, many issues could still rise because of the new SE policies. Chainfire says himself that trying to do so will in any case need to drop even more the security level.
So, for now, and maybe also in near future, no other way to root will be possible except using a custom kernel in a selinux permissive state. Sure some vulnerabilities could be found and used, but will probably be patched by Google.
Seems it is not Samsung to blame, but really Google.
Hello
i have installed the kernel, the TWRP and Super su and i have now root on my note 4.
But i always have in my notification bar a notification that says "security notification non authorized action have been made" (i translate from french so it is maybe not exactly what it write on english phones)
What can i do to don't have that anymore ?
Thank you
parisien99 said:
Hello
i have installed the kernel, the TWRP and Super su and i have now root on my note 4.
But i always have in my notification bar a notification that says "security notification non authorized action have been made" (i translate from french so it is maybe not exactly what it write on english phones)
What can i do to don't have that anymore ?
Thank you
Click to expand...
Click to collapse
You can freeze security log agent with TB and you're fine.
@topic screen mirroring is not working here on note 4. Must be kernel related. Stock rooted Rom.
Gesendet von meinem SM-N910F mit Tapatalk
robotnikz said:
You can freeze security log agent with TB and you're fine.
@topic screen mirroring is not working here on note 4. Must be kernel related. Stock rooted Rom.
Gesendet von meinem SM-N910F mit Tapatalk
Click to expand...
Click to collapse
Not related to the custom kernel
http://forum.xda-developers.com/showpost.php?p=61396065&postcount=66
Or just do this:
In build.prop, add this line and reboot device
Code:
wlan.wfd.hdcp=disable
It works perfectly with my Samsung Smart TV
[N910F][Kernel][Stock][Root] Android Stock 5.1.1 Kernel for root
Hi !
Thank you @Phil.
Could you tell me if it's works on the last germany firmware COI3 for N910F please ?
Guillaume59610 said:
Hi !
Thank you
Could you tell me if it's works on the last germany firmware COI3 for N910F please ?
Click to expand...
Click to collapse
I didn't test, but normally, there are no significant changes between those micro letters. Probably just the branded stuff
Can you upload stock boot.img from COI3 ? I will look at it then
Thanks for your answer.
I 've uploaded stock boot.img from COI3. Here is the link :
https: //mega.nz/#!wAlFBTQK!G2Y09HP2mYmtgQMo2PWUGYGPBlJkgyrMDLZpCnjCnqk
Guillaume59610 said:
Thanks for your answer.
I 've uploaded stock boot.img from COI3. Here is the link :
https: //mega.nz/#!wAlFBTQK!G2Y09HP2mYmtgQMo2PWUGYGPBlJkgyrMDLZpCnjCnqk
Click to expand...
Click to collapse
ramdisk changes don't seem relevant
Until we have new kernel sources for N910F, there is no need to recompile
I am using it heavily since a few days without any issue or bug I could spot
Ok, thanks @Phil !
only for F
cant't work on 910C ?
crazydeepman said:
only for F
cant't work on 910C ?
Click to expand...
Click to collapse
No way. The 910C use exynos chip. You have to request on exynos subforum.
"If it compiles, it is good, if it boots up it is perfect"
Best kernel I have seen, until now! - Works without any problems also with German (DBT) ROM: N910FXXU1COI3, that also contains final fixes for StageFright and a better fingerprint support.
THX Phil!
P.S.: Every update is welcome...
Added some info in post 1 on what changed in Android 5.0 that probably will make it near impossible to root a stock ROM while having even the option to run in enforced mode when needed. Any other way that could be found in the future will mean using kernel vulnerabilities. This obviously will be fixed asap by google. At the end, it will be probably simpler and safer (stability wise) to choose between root and a selinux enforced device, not both
This also makes it impossible to use any KNOX protected features and triggers kernel modification alarms by security TIMA agent:
http://www.samsung.com/hk_en/support/skp/faq/1028007
That's why those services must be disabled
Furthermore, enabling toggling of selinux state is now more complicated since 5.0: enabling CONFIG_SECURITY_SELINUX_DEVELOP in defconfig needs androidboot.selinux=permissive in board kernel cmdline. However, this won't be processed in user builds, but only in eng and userdebug builds. This means you cannot expect any such fixes to work on a stock ROM. We now must hardcode the kernel into always permissive mode
Click to expand...
Click to collapse
Related
So guys ive experimented a bit and found out how to compile a kernel from source. Some guys here are waiting for permissive kernel to install linux deploys etc. Here it is. Not perfect yet, but seems to work. Has nothing special features. Uses my ramdisk from my xKat Rom with init.d support. So please dont ask for more features!! Its mostly pure stock. When i try to build a custom kernel, i will make a new thread for it.
Download
Stock_KK_Permissive_Kernel_NG1-p605
Stock_KK_Permissive_Kernel_NJ1-p605
Stock_KK_Permissive_Kernel_OB1-p605
How to install
Download the file and place the Zip on your intern or extern memory.
boot into Recovery
go on install into TWRP
look for where you placed the Zip
click on the zip an slide to the right
after that go to reboot
How to set permissive?
Permissive is not activ on boot. So use the App "Terminal Emulator"
open it
type su
type setenforce 0
to check it type
getenforce
and you will see its permissive now. But only for this session. If you rebot your device it will enforcing again.
Better choice is the App "SElinux Mode Changer".
Install it from Play Store
and set on permissive
It works with any boot now.:good:
Troubleshooting
if you have trouble with WLAN, delete your connection onetime
reconnect to your accesspoint and WLAN will work again.
Picture
View attachment 2886592
Please hit "thanks" and rate this thread if you like my work or buy me a beer
Good, thanks a lot. Did you face problem like me - when compiled zImage, updated boot.img using abootimg -u -k ../../arch/arm/boot/zImage ...
I was flashed it and get into download mode. Tablet sayed - cannot boot os or something similar. Sorry for bad english.
Great job. Works fine. Thx
@Tautvaldas
Didnt tried it yet. Ive made it on windows cause my ramdisk of the NG1 kernel was there.
i made mine too, i did all the stuff like uv and zzmove gov added in,, but got problem during flash, sad
will test your thanks
Can someone build kernel with framebuffer console support - http://blackfin.uclinux.org/doku.php?id=linux-kernel:drivers:fbcon
@hanspampel
A noob question - but it's better to be sure before start doing something
Moreover - you are the only who made a custom kernel for this device :highfive:
So: is it true I should only replace boot.img with original one (from original tar.md5 package) and change "misc" file with "ro.securestorage.support=true" to obtain zip recovery for flashing original kernel back?
Hi
Yepp it should work this way.
So added to this kernel the latest NJ1 ramdisk. Download in OP.
hanspampel said:
So added to this kernel the latest NJ1 ramdisk. Download in OP.
Click to expand...
Click to collapse
Isn't NK1 the latest one? Or no difference as for kernel part?
Yepp your right. NK1 is the latest, but my rom uses the dbt where is NJ1 the latest. But the NG1 works on NJ1 FW too. So i think there is no real modification on samsung side. Beside there is no another update from sources for p605 available. So that means, is there a modification from samsungs side, then only in ramdisk. This is why i changed it to NJ1 one. Maybe there is one who knows.
hanspampel said:
Yepp your right. NK1 is the latest, but my rom uses the dbt where is NJ1 the latest. But the NG1 works on NJ1 FW too. So i think there is no real modification on samsung side. Beside there is no another update from sources for p605 available. So that means, is there a modification from samsungs side, then only in ramdisk. This is why i changed it to NJ1 one. Maybe there is one who knows.
Click to expand...
Click to collapse
OK, and what about latest P605XXUDOB1?
Hi, sorry for late reply. So there is no newer update of kernel sources available. Only changing of ramdisk of newer fws is possible. But nobody knows if there are changes between the fws.
So added to this kernel the latest OB1 ramdisk. Download in OP.
hanspampel said:
So added to this kernel the latest OB1 ramdisk. Download in OP.
Click to expand...
Click to collapse
Thank you very much for not forgetting this project!
Just installed it - works well!
Hi hanspampel....can you help me,to make usb otg and charge make possible on the p605. I have the lavalink adapter tl-002,but wont work. Must be a kernel thing......would be phantastic.....
Gesendet von meinem SM-N9005 mit Tapatalk
hanspampel,
are you going to continue your work for 5.1.1?
Official sources for the kernel are already published here.
Yes i know. But atm i have not a building system runnig. So maybe if i found some time to setup all the stuff, we can get a new kernel. maybe. Not now, not tomorrow.
Hi mates, after some testing i have made a patch to get working IR in roms wich doesnt have it included.
Need selinux permissive or Sepolicy exception with enforcing
ROM maintainers need to enable HSL in kernel
Installation:
-Flash with Twrp
-Nothing more
Download:
-Patch (Updated 26-05-2017)
I'm on Omni though, but still....the same as before, it crashes upon updating....sorry if not helpful, thanks for your effort
Just scanned through logcat, first sign of trouble is once again "no permission on read/write serial port".
I will enable the serial port in next build
Sent from my LEX720 using Tapatalk
It says: "Unable to Initialize" on AOKP how to do you about updating after flashing it through TWRP
Nice work! Thanks!
Installing on AOSPExtended with Black Screen 1.8.5 worked. But after doing the update of the app I had also "Unable to Initialize" and it was not possible to pair with any device. There is no option for it.
Hi,
I have installed it with your RR rom on my x720, but unfortunately it doesn't work and also I don't get any bug message at the first time.
It opens normally but at universal remote it doesn't record any data from IR sensor.
smae said:
Hi,
I have installed it with your RR rom on my x720, but unfortunately it doesn't work and also I don't get any bug message at the first time.
It opens normally but at universal remote it doesn't record any data from IR sensor.
Click to expand...
Click to collapse
Clean data and cache of the app and open again
Updated
villarleg said:
Updated
Click to expand...
Click to collapse
Now it is fully working...
Thanks a looot :good:
Hi. How do I move remote app data for other Rom?
Sorry for my bad English.
Tapatalkkal küldve az én LEX720 eszközömről
bankizsolt said:
Hi. How do I move remote app data for other Rom?
Sorry for my bad English.
Tapatalkkal küldve az én LEX720 eszközömről
Click to expand...
Click to collapse
Backup both Remote Control and UEI Android services SDK(LeTV) using Titanium backup and restore them (Data only) in the new rom (after installing the patch using twrp).
Any one test this patch on LineageOS 14.1 Rom?
How ti enable hsl in kernel?
I'm on LOS 14.1 and it says unable ti initialize
sweetboy02125 said:
Any one test this patch on LineageOS 14.1 Rom?
Click to expand...
Click to collapse
danielexda said:
How ti enable hsl in kernel?
I'm on LOS 14.1 and it says unable ti initialize
Click to expand...
Click to collapse
Enable HSL its for devs only, i think lineage doesnt have it enabled in kernel, so you need to flash another kernel and change selinux to permissive
Can I turn this to permissive by kernel audiutor?
villarleg said:
Enable HSL its for devs only, i think lineage doesnt have it enabled in kernel, so you need to flash another kernel and change selinux to permissive
Click to expand...
Click to collapse
danielexda said:
Can I turn this to permissive by kernel audiutor?
Click to expand...
Click to collapse
Flashing another kernel will change it to permissive (if it's a permissive kernel), and if it's an enforcing kernel it'll have the selinux patches so there's no need to change it to permissive yourself, just flashing the kernel is enough
I change ti permissive by an apk bit it doesn't funciton
danielexda said:
I change ti permissive by an apk bit it doesn't funciton
Click to expand...
Click to collapse
Your kernel needs to have the serial port patch
Can you tell me which kernel i have to install?
complied from https://github.com/therootlord/android_kernel_motorola_msm8953
not my code, just sharing because i keep seeing people complain about magisk mods
Features:
-F2FS bug fixed (can flash magisk modules on stock)
-not sure what else
Flash in twrp
TODO:
-kexec-hardboot
-disable force-decrypt
Stock NPS26.116-45 kernel zip: Link
This was my first kernel compilation, let me know if something isn't working
Extreme-Plus-Kernel-nrdgd-1.zip compiled on nov-18-2017 Link: Google Drive
UPDATE, just found out wifi doesnt work, sorry, been traveling and didnt think to test. everything else seems to work tho.
heres an older version of the kernel not compiled by me until i figure this out
UPDATE 2 - wifi fixed
Extreme-Plus-Kernel-nrdgd-2.zip compiled on nov-19-2017 Link: Google Drive
It boots with aex 7.x - to early to say more
Phazmos said:
It boots with aex 7.x - to early to say more
Click to expand...
Click to collapse
wifi doesnt work for me, let me know if its working on yours and which model you have if you can
until then check OP for older version of the same kernel
wifi fixed
Ae3NerdGod said:
wifi doesnt work for me, let me know if its working on yours and which model you have if you can
until then check OP for older version of the same kernel
wifi fixed
Click to expand...
Click to collapse
Didn't notice it was broken - us version here.
It booted, but was very slow and laggy, even did a system cache wipe....Then restoring the default boot.img had wifi not working....Just FYI for those who want to try...Do a backup
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Would you mind sharing the build sequence/commands?
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
Just a note on kernels
I've tested many many kernels on many devices. When they are configured the same, performance/battery is about the same. Any difference was slight enough to be considered noise in the test methods. I always suggest to learn about kernel parameters then tweak it to the way you want. Any kernel will give more performance, or battery life, or anything between - all depends on how you configure it.
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Phazmos said:
Just a note on kernels
I've tested many many kernels on many devices. When they are configured the same, performance/battery is about the same. Any difference was slight enough to be considered noise in the test methods. I always suggest to learn about kernel parameters then tweak it to the way you want. Any kernel will give more performance, or battery life, or anything between - all depends on how you configure it.
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Click to expand...
Click to collapse
EXKM seems to work fine on AEX rom using the butterfly governor good battery life and smooth.
revengineer said:
Would you mind sharing the build sequence/commands?
Click to expand...
Click to collapse
i had to use his toolchain, and fix a few includes for it to work. im going to try different ones to try and figure out the lag, maybe thats not whats causing it but im new at this . been reading logs all day
smokinjoe2122 said:
It booted, but was very slow and laggy, even did a system cache wipe....Then restoring the default boot.img had wifi not working....Just FYI for those who want to try...Do a backup
Click to expand...
Click to collapse
yeah, sorry. new at this. dont know if @geneticengineer wants me passing his old kernels he hasnt posted around either. if you can find his afh, he has a really old one on there thats way faster. im still learning, im working on pulling the stock modules and kernel to make a back to stock zip rn actually will post soon if you keep using it, it speeds up a tiny bit lol
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
planning kexec hardboot and disable force decrypt when i get the hang of this.
Phazmos said:
Just a note on kernels
Ps - same device, same twrp, supersu instead of magisc, no problems. Except seems not compatible with ex kernel manager - it doesn't apply settings. I believe it doesn't set proper permissions to be able to write. But hey, it's young and a stockish kernel, hope to see more.
Click to expand...
Click to collapse
actually i think i missed something in defconfig that enables the secondary processor, im also going to switch toolchains, expect a new kernel in a few days
Here's a link to GeneticEngineer's AFH-hosted original kernel from the TWRP thread. I don't think he'll mind it being reposted in this thread. This should tide people over until you can iron out the bugs in your build.
https://www.androidfilehost.com/?fid=745425885120765462
Thanks for picking up the baton and running with it, incidentally. I did ask GeneticEngineer to create a thread for his kernel but perhaps he missed the message.
THERAJ12 said:
Is the only benefit to have magisk modules on stock rom? I have XT1806 rooted TWRP r9 Gladius Magisk 14.3 flashed this kernel but kept booting straight to recovery...had to do a full restore. I'm looking for custom kernels that provide speed and power benefits. Thanks
Click to expand...
Click to collapse
i actually get those weird reboot to recovery bugs all the time on this device and 2 things fix it, booting to bootloader and picking "start" or a full restore
I tried version 2. I still couldn't get it to pass Magisk SafetyNet. I also noticed that this kernel breaks fingerprint gestures.
bishop0114 said:
I tried version 2. I still couldn't get it to pass Magisk SafetyNet. I also noticed that this kernel breaks fingerprint gestures.
Click to expand...
Click to collapse
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Loccy said:
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Click to expand...
Click to collapse
Thanks. I tried it and still wouldn't pass SafetyNet. The fingerprint gestures worked though. I am running it on a secondary ROM. Maybe that is causing the issue?
Loccy said:
GeneticEngineer's original both passes SafetyNet and leaves fingerprint gestures functional on my otherwise stock single Sim EU version:
https://www.androidfilehost.com/?fid=745425885120765462
Click to expand...
Click to collapse
I've built a fully working stock kernel which has the needed commits for Magisk modules to work correctly and passes SafetyNet [emoji6]. Need to do some more updating (upstream) but I plan on posting it soon, probably new thread (Resurrected Kernel).
bishop0114 said:
Thanks. I tried it and still wouldn't pass SafetyNet. The fingerprint gestures worked though. I am running it on a secondary ROM. Maybe that is causing the issue?
Click to expand...
Click to collapse
A stock based kernel isn't gonna play well with custom ROMs, unless your secondary ROM is a stock ROM? I plan on creating one for cm-14.1+ based ROMs too.
Jleeblanch said:
I've built a fully working stock kernel which has the needed commits for Magisk modules to work correctly and passes SafetyNet [emoji6]. Need to do some more updating (upstream) but I plan on posting it soon, probably new thread (Resurrected Kernel). A stock based kernel isn't gonna play well with custom ROMs, unless your secondary ROM is a stock ROM? I plan on creating one for cm-14.1+ based ROMs too.
Click to expand...
Click to collapse
If you need someone to beta test it, let me know. It is the only reason I am not running stock.
this is just a Full Stock Deodexed Oreo ROM of US Unlocked 2.42.617.1:
http://www.androidfilehost.com/?fid=817906626617957852 RE-Uploaded done
No root
No Aroma installer
No magisk by default
it will probably lag if not rooted you will need this module attached bellow also, once magisk is installed get it here
it is working fine for me so far so I decided to share it here since it is completely stock any bugs you might find beside the lag on no root, there are probably on stock also
Just curious, why would it lag?
@JEANRIVERA
THX!
Can you share full (including framework) deodex method?
I used Superr kitchen
Golv said:
@JEANRIVERA
THX!
Can you share full (including framework) deodex method?
Click to expand...
Click to collapse
All I did was use Superr kitchen
doyou37 said:
Just curious, why would it lag?
Click to expand...
Click to collapse
Suspect its the issue where the dalvik cache can't be built unless SELinux is permissive.
JEANRIVERA said:
this is just a Full Stock Deodexed Oreo ROM of US Unlocked 2.42.617.1:
http://www.androidfilehost.com/?fid=817906626617957852 RE-Uploaded done
No root
No Aroma installer
No magisk by default
it will probably lag if not rooted you will need this module attached bellow also, once magisk is installed get it here
it is working fine for me so far so I decided to share it here since it is completely stock any bugs you might find beside the lag on no root, there are probably on stock also
Click to expand...
Click to collapse
Sounds intriguing can you tell me what you removed to deox. I would be coming from another rom so I am un locked and rooted.
RKDxpress said:
Sounds intriguing can you tell me what you removed to deox. I would be coming from another rom so I am un locked and rooted.
Click to expand...
Click to collapse
I didn't do nothing special I just used Superr kitchen
Electronic Punk said:
Suspect its the issue where the dalvik cache can't be built unless SELinux is permissive.
Click to expand...
Click to collapse
yep...
from the magisk module:
# Enable SELinux Permissive Mode at Boot
setenforce 0
personally I'd rather stay odex than set SELinux to Permissive
Hi,This rom is full Deodexed .
Which perm type should I choose?
Here is a very brief summary of set_perm, set_metadata, sparse_dat, and raw_img.
Thank you for share.
Here are patch sets for speaker working on ze60xkl pie ROMs
<Link>
ZE600KL : http://www.mediafire.com/folder/5l0hwa9n7aice/ze600kl
ZE601KL : http://www.mediafire.com/folder/r8wbjbqjjh46j/ze601kl
<Notice>
These patch sets are only for ZE60xKL model on pie custom rom users.
DO NOT apply these for other models or Andoroid versions.
<Patch Files>
1) Kernel Packages (be careful for mistaking model).
- ze600kl-spk-pie-kernel-v1.zip (for ZE600KL(Z00L))
- ze601kl-spk-pie-kernel-v1.zip (for ZE601KL(Z00T))
2) ze60xkl-spk-pie-libs-v1-01.zip (for both ZE600KL and ZE601KL)
<Install Instructions>
1. Download 2 patches (#1 and #2) to any folder
2. Reboot recovery (TWRP)
3. Flash 2 files
4. Reboot system and you can fun sound from device
<Tested Roms>
- Lineage OS
- CrDroid
- AEX
<Features>
- Add speaker sound stream to your rom
- Stereo mic support
<Known Issue>
- Noisy sound with bluetooth and enabling reverb
<Source Code>
https://github.com/zekken1977?tab=repositories
<Change log>
[2019-05-05: v1.0]
- Add tfa9887 driver
[2019-05-26: v1.01]
- Rebased on firekernel r2.10
Finally thank you for helping to test my patch
@Rayonecma, @celtic1453, @fabricio6791 and @ndrancs
First Release On : 2019-05-05
Last Update On : 2019-05-26
Τhanks
Works ok for the ZE600KL
Sent from my MI PAD 4 using Tapatalk
test on ze601kl... working friend
And... For my ze601kl it's working too... ???
can i test the patch on other pie custom rom ?? RR, Cdroid...??
right now i have lineage pie
fabricio6791 said:
can i test the patch on other pie custom rom ?? RR, Cdroid...??
right now i have lineage pie
Click to expand...
Click to collapse
Please
I think this patch will be available for other pie roms unless modified audio HAL or enforced SElinux.
Ze60xkl sound patch
Thx a lot, i've made patch for oreo, but i didn't find any time to work on the pie version .
Great job !!!
You are awesome! Thank you for this work ^-^
zekken1977 said:
Please
I think this patch will be available for other pie roms unless modified audio HAL or enforced SElinux.
Click to expand...
Click to collapse
You are doing Gods work bro!
Hats off to you.
One question.
What about enforced SELinux? LOS will eventually get SELinux to enforcing. What after that? This won't work?
[email protected] said:
You are doing Gods work bro!
Hats off to you.
One question.
What about enforced SELinux? LOS will eventually get SELinux to enforcing. What after that? This won't work?
Click to expand...
Click to collapse
Enforcing SELinux is enabled in stock rom from Oreo (maybe... ) but most custom roms are disabled (permissive) like attached.
Exactly after enabled SELinux, this patch will not work because of enforcing SELinux.
If so, my ideas which we can choose are :
1. Add sepolicy file into patch to access driver
-> It seems to be good but we need to be aware differences of sepolicy between custom roms
2. Change patch design for hold all amp device (tfa9887) controls in userspace (this means kernel patch will be disappeared)
-> It also seems to be good but we need a new designed libs, and making completely independent module from SELinux is difficult, I think.
To be honest, I have no ieda for the best solution
zekken1977 said:
Enforcing SELinux is enabled in stock rom from Oreo (maybe... ) but most custom roms are disabled (permissive) like attached.
Exactly after enabled SELinux, this patch will not work because of enforcing SELinux.
If so, my ideas which we can choose are :
1. Add sepolicy file into patch to access driver
-> It seems to be good but we need to be aware differences of sepolicy between custom roms
2. Change patch design for hold all amp device (tfa9887) controls in userspace (this means kernel patch will be disappeared)
-> It also seems to be good but we need a new designed libs, and making completely independent module from SELinux is difficult, I think.
To be honest, I have no ieda for the best solution
Click to expand...
Click to collapse
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
[email protected] said:
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
Click to expand...
Click to collapse
And another idea is that custom rom maintainers implement tfa9887 driver and sepolicy.
The driver is disappeared without device tree because driver probing doesn't work, this means the driver will not affect to other models except ZE60xKL (strictly other models which are made dtb from not ZE60xKL's device tree).
Otherside we'll distribute patches including audio/amp HALs and audio routing cofigs.
I think this is the most reasonable idea like similar style until Oreo...
zekken1977 said:
And another idea is that custom rom maintainers implement tfa9887 driver and sepolicy.
The driver is disappeared without device tree because driver probing doesn't work, this means the driver will not affect to other models except ZE60xKL (strictly other models which are made dtb from not ZE60xKL's device tree).
Otherside we'll distribute patches including audio/amp HALs and audio routing cofigs.
I think this is the most reasonable idea like similar style until Oreo...
Click to expand...
Click to collapse
I guess, the Devs will implement this driver in to their ROM. But it is more prudent to have a Patch (Like we had upto Oreo). Reason being, there are tens of ROMS. Convincing each dev will be counter productive. The patch can be applied more efficiently.
We'll have to wait and see when the SEPolicy enforcement occurs.
About update patch
Hi patch users,
These patches are based on Firekernel r2.9, then already r2.10 is updated.
So if you'll need to update based on r2.10, pleaase let me know
Thanks
Workaround
[email protected] said:
We did not have Stock Oreo i guess (Only Custom).
I personally was checking things and found the kernel zip different. That was great thinking on your part though. I tried building this a long ago, but failed (I never thought about patching the kernel).
Hey @Superbezo, can you give some insights in this? What could be possible when we have SELinux as Enforcing on pie?
The LOS 16 has SELinux in bugs, The dev will eventually fix it and turn it to Enforcing.
Click to expand...
Click to collapse
Thé selinuxswitch from [email protected] will ne a working workaround to keep selinux disabled even on enforcing mode ROM...
---------- Post added at 05:44 AM ---------- Previous post was at 05:33 AM ----------
zekken1977 said:
Hi patch users,
These patches are based on Firekernel r2.9, then already r2.10 is updated.
So if you'll need to update based on r2.10, pleaase let me know
Thanks
Click to expand...
Click to collapse
Yes, i'm interrested in ...
Please zekken1977 , Can you made jour kernel patch code public ?
Thx a lot.
Superbezo said:
Thé selinuxswitch from [email protected] will ne a working workaround to keep selinux disabled even on enforcing mode ROM...
---------- Post added at 05:44 AM ---------- Previous post was at 05:33 AM ----------
Yes, i'm interrested in ...
Please zekken1977 , Can you made jour kernel patch code public ?
Thx a lot.
Click to expand...
Click to collapse
OK. I'll update but next version will be available on this weekend.
And about source code, please see the link in my 1st post
Thanks
Can you make sound patch for Zenfone Selfie Z00UD (Z00T)?
Because I will try this rom (https://forum.xda-developers.com/zenfone-2-laser/development/rom-prometheusoneui-z00t-t3929198) to my Zenfone Selfie Z00UD (Z00T), but the sound patch only for Zenfone 2 Laser ZE601KL (Z00T). Thanks in advance!
ManOfFeel said:
Zenfone Selfie did not have speaker issue lol
Click to expand...
Click to collapse
But, the prometheusoneui said that need to flash sound patch
fuady7 said:
But, the prometheusoneui said that need to flash sound patch
Click to expand...
Click to collapse
Hi, my patch made for drive spk amp device tfa9887 which mounts on only ZE600 or ZE601KL.
So I guess this patch isn't valuable for other zenfones.
I checked Z00UD schematic and I couldn't find tfa amp.
If you are facing sound issue, my patch can't improve your problem.
Hello, i'll glad to know if someone else encountered the same issue:
I have tested this patch with los ans crdroid with thé same results.
I flashed successfully the ROM & patch and all was working fine (sound ,data ans GSM connexion) for few hours. Then the phone freezes and after reboot,no GSM network détectéd at all... The only way to recover was to do a factory reset with twrp or revert back to oreo backup... Any idea?