IF YOU FLASH CUSTOM KERNEL, YOU WILL LOSE YOUR WARRANTY, KNOX WILL TRIGGER TO 0x1, I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE.
FEATURES:
Based on G95XFXXU1AQF7 source
Compiled with Linaro GCC 6.3
Ofast and some GCC optimizations
Some architecture optimizations
Many kernel debug options debloated
Memory management improvement
NOTICE:
Make sure your DATA partition is not encrypted,
this kernel do not support F2FS,
and integrated SuperSU, do not support magisk.
DOWNLOAD:
https://drive.google.com/file/d/0BzF1xgn4nprrOWRVRkdYRWhlbXc/view?usp=sharing
SUPPORT:
If you like my work, feel free to click thanks button, reply this thread about your experience,
or give me a small donation: https://www.paypal.me/devriesl
Thanks/Credits:
jesec for his patch to fix fingerprint problem
Tkkg1994 for his flash script via TWRP
XDA:DevDB Information
ImageBreaker Kernel, Kernel for the Samsung Galaxy S8
Contributors
Devries, jesec, Tkkg1994
Source Code: https://github.com/DevriesL/SM-G950F_ImageBreaker
Version Information
Status: Stable
Current Stable Version: v0.5
Created 2017-07-05
Last Updated 2017-07-13
reserved
reserved~
Thank you very much for our galaxy s8+. Kindly provide the changelogs too for further updates. Thank you.
I tried but after flashing im unable to flash any of magisk root. It shows error in twrp.
mrjoy said:
I tried but after flashing im unable to flash any of magisk root. It shows error in twrp.
Click to expand...
Click to collapse
It support SuperSU root by default.
Devries said:
It support SuperSU root by default.
Click to expand...
Click to collapse
But im using magisk from long time. Could you not give support to magisk?
mrjoy said:
But im using magisk from long time. Could you not give support to magisk?
Click to expand...
Click to collapse
Could you please give me a magisk flash package download link?
I will try.
Devries said:
Could you please give me a magisk flash package download link?
I will try.
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You can download from here.
Thank you for try.
mrjoy said:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You can download from here.
Thank you for try.
Click to expand...
Click to collapse
I checked the flash script,
because this kernel support SuperSU by default,
magisk not compatible with it.
Devries said:
I checked the flash script,
because this kernel support SuperSU by default,
magisk not compatible with it.
Click to expand...
Click to collapse
Then how we can flash your kernel with magisk?
mrjoy said:
Then how we can flash your kernel with magisk?
Click to expand...
Click to collapse
I will consider add magisk and superSU support in the next version.
Devries said:
I will consider add magisk and superSU support in the next version.
Click to expand...
Click to collapse
thanx & will wait for next version. Thank you.
mrjoy said:
thanx & will wait for next version. Thank you.
Click to expand...
Click to collapse
Finally I found that integrated both SuperSU and magisk is impossible,
the only one way to support magisk is removing SuperSU support in ramdisk,
but I do not want to other flash script change my ramdisk especially fstab,
so I consider do not support magisk, sorry.
Devries said:
Finally I found that integrated both SuperSU and magisk is impossible,
the only one way to support magisk is removing SuperSU support in ramdisk,
but I do not want to other flash script change my ramdisk especially fstab,
so I consider do not support magisk, sorry.
Click to expand...
Click to collapse
but all of other kernels supported by both SuperSu & Magisk. Even you can take help from them.
Else you want to make it only with SuperSu then its ok. But thanx for your response. Good day.
mrjoy said:
but all of other kernels supported by both SuperSu & Magisk. Even you can take help from them.
Else you want to make it only with SuperSu then its ok. But thanx for your response. Good day.
Click to expand...
Click to collapse
They support both SuperSu & Magisk because they do not integrated anything in their kernel, you can flash SuperSu & Magisk manually,
But I integrated SuperSU because I do not want other flash script change fstab.
微博观光团?
Sent from my Sony Xperia Z3 using XDA Labs
Devries said:
They support both SuperSu & Magisk because they do not integrated anything in their kernel, you can flash SuperSu & Magisk manually,
But I integrated SuperSU because I do not want other flash script change fstab.
Click to expand...
Click to collapse
you mean if i flash magisk manually then will it support with your kernel? Because last time i tried to install magisk manully after flashing your kernel but it was giving error in TWRP.
F2FS is not perform good as EXT4 on S8, Is this true? And does AQF7 kernel can flash with older version rom and boot loader? Thanks a lot!
jasonce said:
F2FS is not perform good as EXT4 on S8, Is this true? And does AQF7 kernel can flash with older version rom and boot loader? Thanks a lot!
Click to expand...
Click to collapse
It's not the main reason that my kernel do not support F2FS. S8 TouchWiz HAL layer do not compatible with F2FS, enable it in userdata will introduce some stability issue.
It's no problem and I will update kernel to QG5.
Related
Just for fun, I compiled an optimized version of stock kernel for Marshmallow 6.0
It works with stock ROM for Moto X Pure XT1575, not tested with anything else.
Current features:
Compiled with O3
Uber toolchain
misc gcc optimization flags
KCAL
TCP congestions
Source code:
https://github.com/vadimtk/moto-x-kernel-6.0
Based on source
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-MPH24.49-18
Download link
V5:
Changes:
Updated to Kernel 3.10.94, thanks to https://github.com/Nimrodsv
XT1575:
https://www.androidfilehost.com/?fid=24345424848487596
XT1572:
https://www.androidfilehost.com/?fid=24345424848487595
V3:
Changes:
Couple SSD/flash related optimizations
XT1575:
https://www.androidfilehost.com/?fid=24343351889232014
XT1572:
https://www.androidfilehost.com/?fid=24343351889232056
V2:
https://www.androidfilehost.com/?fid=24341993505161414
How to use:
1. Download and unpack
2. Reboot to bootloader:
Code:
adb reboot bootloader
3. Boot temporary with new kernel (active till next reboot):
Code:
fastboot boot v4tk-opt-V2.img
or flash permanently:
Code:
fastboot flash boot v4tk-opt-V2.img
XDA:DevDB Information
V4TK Kernel, Kernel for the Moto X Style (Pure)
Contributors
VadimTk
Kernel Special Features:
Version Information
Status: Beta
Created 2015-12-24
Last Updated 2015-12-23
Damn that was fast okay I'm installing it now. I'll be the test dummy for TruPureX users. Thanks for your hardwork its very appreciated
also OT. woot 123 posts
---------- Post added at 02:09 AM ---------- Previous post was at 02:02 AM ----------
Works great on TruPureX it's just very bare bones at the moment. Still great job! I can not wait to see more from you tanks again for being awesome
Thank you for this!
sweet! vadim is back will flash later
patt2k said:
sweet! vadim is back will flash later
Click to expand...
Click to collapse
If your running TruPureX your going to be happy by the speed up
I tried flashing this in TWRP and get a failed message. md5 checks out. Any suggestions?
btafoya said:
I tried flashing this in TWRP and get a failed message. md5 checks out. Any suggestions?
Click to expand...
Click to collapse
Its not a flashable zip. You need to extract it before flashing. Flash as an image file in TWRP and select boot
^^^ yes, and/or try using flashify or rashr after unzipping
I have the traditional root using rooted boot and super SU in system. Is this boot.img pre rooted?
countryfolk07 said:
I have the traditional root using rooted boot and super SU in system. Is this boot.img pre rooted?
Click to expand...
Click to collapse
the boot.img does not control root. The only thing that would effect this for would maybe be the SR build as that hooks into the kernal. traditional dosent hook into the kernal. He is reverting to traditional soon.
WelcomeToTheSkye said:
If your running TruPureX your going to be happy by the speed up
Click to expand...
Click to collapse
I had it,using Sabissimos rom and so far so good.
Sent from my XT1575 using Tapatalk
I flashed this on a rooted, deodoxed 6.0 and dang.. My phone is so snappy now. Thank you!
WelcomeToTheSkye said:
the boot.img does not control root. The only thing that would effect this for would maybe be the SR build as that hooks into the kernal. traditional dosent hook into the kernal. He is reverting to traditional soon.
Click to expand...
Click to collapse
If the boot partition isn't flashed as rooted you will bootloop if superSU is installed. When I first took OTA I had to flash a rooted boot.img to get root without bootlooping. I can remember off hand who created the image, but this is why I ask.
VadimTk said:
Source code:
https://github.com/vadimtk/moto-x-kernel-6.0
Click to expand...
Click to collapse
Very nice Vadim
Please remove the "http://" on the url part for this link.
Might be a good idea to note that in the OP @VadimTk. Thanks!
Sent from my XT1575 using Tapatalk
Sir can i install this kernel on non rooted pure style
@VadimTk
please make an xt1572 version compatible, this version don't work on style, every app FC at start.
thanks
happy xmas
fdc77 said:
@VadimTk
please make an xt1572 version compatible, this version don't work on style, every app FC at start.
thanks
happy xmas
Click to expand...
Click to collapse
Did you wipe dalvik/cache?if it truly didn't work on the xt1572 either WiFi or RIL would be broken.
yes, wiped cache and dalvik but no luck, wifi and ril seems to be broken but i don't know for certain because phone was unusable
fdc77 said:
yes, wiped cache and dalvik but no luck, wifi and ril seems to be broken but i don't know for certain because phone was unusable
Click to expand...
Click to collapse
Ah okay then yes it is incompatible lol sorry for doubting
Hi guys.
In what order do I have to install these items from twrp recovery?
- Rom
- Gapps
- Zip magisk
- Custom kernel
- Titanium Zip (To install titanium backuo from recovery)
?
ROM kernel magisk
Other apps don't interfer with each other so you don't have to care about the order.
Your order is almost fine. Just install magisk after the kernel, not before, since Magisk patches the installed kernel. In the same way, if you install another kernel in the future, you should lash Magisk again.
andrea0807 said:
Hi guys.
In what order do I have to install these items from twrp recovery?
- Rom
- Gapps
- Zip magisk
- Custom kernel
- Titanium Zip (To install titanium backuo from recovery)
?
Click to expand...
Click to collapse
if you ask like that i would spare the part with the custom kernel
and titanium zip i ask myself - what is it good for?
naja-okay ^^
NMir01 said:
ROM kernel magisk
Other apps don't interfer with each other so you don't have to care about the order.
Click to expand...
Click to collapse
jman0 said:
Your order is almost fine. Just install magisk after the kernel, not before, since Magisk patches the installed kernel. In the same way, if you install another kernel in the future, you should lash Magisk again.
Click to expand...
Click to collapse
In the magisk installation instructions, however, topjohnwu says to install the custom kernel after installing magisk.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
jman0 said:
Your order is almost fine. Just install magisk after the kernel, not before, since Magisk patches the installed kernel. In the same way, if you install another kernel in the future, you should lash Magisk again.
Click to expand...
Click to collapse
What happen if I install slim7 without installing kernel?
kkcheong said:
What happen if I install slim7 without installing kernel?
Click to expand...
Click to collapse
Heyyo, every ROM has a kernel included so it's very optional to flash a custom kernel. Even so, some custom kernels require a certain ramdisk to work properly.
For example, using BS Kernel 3 series on LineageOS 14.1 won't work properly.
ThE_MarD said:
Heyyo, every ROM has a kernel included so it's very optional to flash a custom kernel. Even so, some custom kernels require a certain ramdisk to work properly.
For example, using BS Kernel 3 series on LineageOS 14.1 won't work properly.
Click to expand...
Click to collapse
Thanks yo
BASE CRB7.
STOCK DEODEX VERSION.
ANDROID SECURITY PATCH LEVEL 01 FEBRUARY 2018.
ROOT WITH MAGISK.
SINGLE CSC ZTO.
CSC TWEAKS.
BUILD.PROP TWEAKS.
DEPLOATED.
KNOX REMOVED.
NEW FONTS.
NO ADS WITH ADAWAY APP.
EXCELLENT BATTERY AUTONOMY.
RMM STATE LOCK FIX.
INSTALLATION:
WIPE DALVIK.
WIPE SYSTEM.
WIPE DATE.
WIPE CACHE.
INSTALL ROM.
RESTART THE SYSTEM AND ENJOY.
ROM:
https://goo.gl/riwEHA
THANK YOU:
@SuperR.
Excellent kitchen.
@topjohnwu
Magisk
@Winb33
New fonts.
@yash92duster
Kernel Fix Data Magisk.
rom works ?
9/10
Working
not work man dont flash error status twrp
i hope your rom is deBloated ?
hasanben35 said:
not work man dont flash error status twrp
Click to expand...
Click to collapse
Only with you such a mistake friend.
marcel112 said:
i hope your rom is deBloated ?
Click to expand...
Click to collapse
Yes!
Plz magisk root
magisk gives a lot of trouble with oreo.
Ifezzzy said:
Plz magisk root
Click to expand...
Click to collapse
I'll see how it stays with the magisk if it stays stable I put with the magisk.
kleidione said:
I'll see how it stays with the magisk if it stays stable I put with the magisk.
Click to expand...
Click to collapse
Thanks buddy!
Ifezzzy said:
Thanks buddy!
Click to expand...
Click to collapse
Magisk leaves the rom very unstable friend can not leave it by default.
sorry.
I'm uploading an update right now I added the hidesu will help regarding the apps that do root verification.
thanks no problems thus far. clean install and everything appears to work.
install parellel space and tell me if whats app works
I will remove the link until removing SysScope.apk on request the @SoLdieR9312 the same asked to remove the apk edited by him.
I already did the removal and I started the rom again.
maurce249 said:
install parellel space and tell me if whats app works
Click to expand...
Click to collapse
Oreo has dual native messenger.
kleidione said:
Oreo has dual native messenger.
Click to expand...
Click to collapse
i know but cant back up whats app in dual messenger to gte back your chats f u wipe or install a next rom
maurce249 said:
i know but cant back up whats app in dual messenger to gte back your chats f u wipe or install a next rom
Click to expand...
Click to collapse
ever tried the titanium backup?
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.
Update: NFC payments has been fixed in Los 17.1 (and probably in all other ROMs) so this module is no longer required.
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Havoc OS added it in the latest build (20202602) too I think in the future all ROMs will include the fix from NOS sources.
Thanks to NOS devs and to you guys! :good:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Great! But... Where is the module?
mvalda01 said:
Great! But... Where is the module?
Click to expand...
Click to collapse
Lol!
I accidentally created a duplicate thread and the attachment was in the other thread.
I've now added to the OP.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
uutucherenz said:
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
Check out the threads in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development and make sure you read the first post (OP - original post) in the thread your interested in.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
I've always flashed it using the TWRP mentioned in the OP of the Los 17.1 thread (aka SAR TWRP) https://forum.xda-developers.com/on...ageos-17-0-oneplus-3-3t-t3990061/post80652281
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
Joshmccullough said:
BillGoss said:
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
I've updated the OP to say that the module is no longer needed.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse